#DVT provides an open infrastructure for splitting and distributing validator keys into multiple KeyShares in order to run @ethereum validators on a cluster of nodes, allowing individuals, groups, or communities of operator to form as a single validator.
In the view of technology, #DVT consists of 4 key components: Distributed Key Generation, Shamir Secret Sharing of BLS Signatures, Secure Multi-Party Computation and the #DVT BFT Consensus Layer.
Among them, Multi-Party Computation is the most critical part for #DVT, which allows operators to share private key to sign transactions and perform computations without rebuilding on any other device.
First of all, #DVT introduces nodes of multiple parties to increase the robustness of the system and ensure that the system will not stagnate and the user's principal will not be slashed when some nodes go offline or misbehave.
In a #DVT cluster, even if some participating nodes go offline(<33%), the remaining nodes can still reach a consensus on what is signed.
Secondly, with the help of #DVT, individuals or groups can participate in staking, making it possible to distribute the operations of @ethereum validators, improve security, increase inclusiveness, and decentralize the network.
Some popular Liquid Staking service providers such as @LidoFinance can also option #DVT as the bottom layer of their protocol to reduce the community's concerns over centralization.
Finally, under the mounting regulatory pressures, #DVT can make the @ethereum network more censorship-resistant.
@ssv_network is a decentralized @ethereum Liquid Staking network developed based on #DVT. It provides an open infrastructure for anyone who wants to run an @ethereum validator, with a range from DIY users to staking pools or even staking institutions.
Obol Network is another #DVT pioneer. @ObolNetwork launched the plug-in client Charon to enable #DVT and ensure that the staking system can run in a decentralized way. Its ultimate goal is to build a "trust-minimized" @ethereum staking protocol.
diva is also an @ethereum Liquid Staking protocol developed based on #DVT. Specifically, @divalabs is an ultra-light client that connects to existing @ethereum execution and consensus clients via standard API.
Stakers can stake any amount of $ETH without a minimum requirement, and they don't need to run any nodes.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Ethereum will launch the "Shanghai Network Upgrade" in March 2023. What will be changed on @ethereum or, more generally, the #crypto ecosystem with this coming upgrade?
1) What is Shanghai Upgrade?
Conventionally, the upgrade of the @ethereum mainnet is named after the city, such as "London upgrade", "Paris upgrade", etc. The Shanghai upgrade will be another major update of @ethereum.
First, EIP 3540 will be introduced in the Shanghai upgrade will. EIP 3540 is an improved protocol designed to address changes in the Ethereum Virtual Machine Object Format (EOF) separating code from data, which is greatly beneficial to validators on the @ethereum network.
#stETH is a tokenized deposit of staking that can be freely held, traded or sold. Its amount equals to the total amount of staked #ETH plus the total staking rewards and minus service fees.
Cryptoeconomic security has always been a critical challenge for #Web3. As the trailblazer of #crypto, Bitcoin's security model is application-specific, which means any new #dApp needs to build a #blockchain to maintain its own trust network.
@ethereum solves this problem to a certain extent through its modular design. Specifically, the EVM enables #dApps to be built permissionlessly on the @ethereum network by leveraging the underlying security of @ethereum itself, without the need for rebuilding a new trust network
At present, however, middleware and non-EVM applications built on the @ethereum network still need to create their own trust network, but bootstrapping and maintaining the security is expensive and time-consuming, which slows down the speed of potential innovation.
An Ethereum-equivalent ZK-Rollup, also called ZK-EVM, is the holy grail of #L2 scaling solutions because they do not compromise on security or compatibility. Among the many ZK-EVM projects, @Scroll_ZKP is the one that cannot be ignored.
In the current ZK-Rollups technology practices, this solution has an Achilles' heel, which is the lack of #EVM compatibility, causing that all ZK-Rollups have to build unique developer tools and infrastructure from scratch.
In this context, ZK-EVM is considered by many to be the "ultimate game" of #L2 scaling, because it allows ZK-Rollups to integrate the network effects of #EVM while exerting its own performance advantages.
1) #Layer2 separates some functions from #Layer1, which keeps the consensus mechanism that provides security guarantees in #Layer1 and distributes the functions of computation and execution to #Layer2, thus achieving the goal for scaling on the premise of decentralization.
But #Layer2 cannot provide highly customized application scenarios, so here comes #Layer3 which can make up this through customized scaling.
Look forward to the application scenarios of #DID in the future, it can be simply divided into two categories: Reputation and Relationship.
Reputation can evaluate and classify users by simplifying digital identities into some explicit and trusty labels, so as to do rapid screening. Reputation includes the following application scenarios:
1) #Web3 credit loan: User's address is given a "credit score" which is used to calculate the deductible staking quota in a credit loan.