research solutions

Elevating blockchain applications with tailored solutions

We partner with industry leaders, pioneering protocols, and forward-thinking funds to elevate the potential of blockchain applications, via applied research tailored to meet the diverse needs of our clients. We enhance their solutions by leveraging the latest developments in zk-proofs, consensus protocols, and other schemes.

The problem

Lido is a liquid staking protocol that converts ETH to a liquid token and stakes the funds on the Beacon Chain. It relies on external parties, called operators, for validators. Operator candidates must currently be approved by the Lido DAO through a voting process, granting the DAO a great deal of power. Ideally, the onboarding process should be permissionless without input from the DAO, while remaining as capital-efficient as possible.

The solution

As part of our collaboration with Lido, we engaged in a multi-phase research project spanning the following subjects:

Phase 1 of our project focused on systematizing knowledge for decentralized identity and verifiable credential schemes, intending to utilize these to facilitate Sybil resistance. We looked at classical results, academic research, and projects that aim to implement these primitives, with special attention given to projects from the Web3 space.

Phase 2 of our project explored the research and design considerations behind a decentralized dispute resolution mechanism for the Lido protocol, created to punish misbehaving operators. The mechanism focused on achieving white-labeling resistance—that is, preventing node operators from delegating their duties to a third party without the protocol’s knowledge, thus impeding the centralization of stake or protocol takeover by a third party. To this end, we first conducted a systematization of knowledge on decentralized justice protocols, which we leverage in our design of the dispute resolution mechanism.

Future research directions may involve further analysis and design of a Sybil-resistant mechanism, as well as utilizing reputation systems for permissionless operators and their performance.

The problem

Lido is a liquid staking protocol that converts ETH to a liquid token and stakes the funds on the Beacon Chain. It relies on external parties, called operators, for validators. Operator candidates must currently be approved by the Lido DAO through a voting process, granting the DAO a great deal of power. Ideally, the onboarding process should be permissionless without input from the DAO.

The solution

As part of our collaboration with Lido, we engaged in a multi-phase research project spanning the following subjects:

Phase 1 of our project focused on systematizing knowledge for decentralized identity and verifiable credential schemes, intending to utilize these to facilitate Sybil resistance. We looked at classical results, academic research, and projects that aim to implement these primitives, with special attention given to projects from the Web3 space.

Phase 2 of our project explored the research and design considerations behind a decentralized dispute resolution mechanism for the Lido protocol, created to punish misbehaving operators. The mechanism focused on achieving white-labeling resistance—that is, preventing node operators from delegating their duties to a third party without the protocol’s knowledge, thus impeding the centralization of stake or protocol takeover by a third party. To this end, we first conducted a systematization of knowledge on decentralized justice protocols, which we leverage in our design of the dispute resolution mechanism.

Future research directions may involve further analysis and design of a Sybil-resistant mechanism, as well as utilizing reputation systems for permissionless operators and their performance.

Phase 2 results

Distributed Key Generation (DKG) protocols

Allow mutually distrusting parties to jointly generate a signing key. Each party holds only a share of the key, and at least t out of n parties are needed to sign a message.

Threshold Signature Schemes (TSS)

Allow parties to perform the signing operation without revealing the secret signing key.

Consensus algorithms

Enable parties to agree on the block they will sign.

Distributed Key Generation (DKG) protocols

Allow mutually distrusting parties to jointly generate a signing key. Each party holds only a share of the key, and at least t out of n parties are needed to sign a message.

Threshold Signature Schemes (TSS)

Allow parties to perform the signing operation without revealing the secret signing key.

Consensus algorithms

Enable parties to agree on the block they will sign.