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.
@Scroll_ZKP is a EVM-equivalent ZK-Rollup with the goal of scaling @ethereum. @Scroll_ZKP uses ZK-EVM as its core component to prove the native #EVM execution traces, and utilizes a decentralized proof network to solve the efficiency problem of the prover.
2) Technical Architecture
The current @Scroll_ZKP architecture consists of three main components:
@Scroll_ZKP node:@Scroll_ZKP node is the main approach for applications and users to interact with the @Scroll_ZKP network, and the @Scroll_ZKP node consists of three modules: Sequencer, Coordinator and Relayer.
Roller network: Rollers act as provers in the network and are responsible for generating validity proofs for #zkRollup.
#Rollup contract and Bridge contract: @Scroll_ZKP connects the @ethereum mainnet and @Scroll_ZKP network through #Rollup and bridge contracts, ensuring the data availability of #L2 transactions and enabling users to transfer assets between L1 and #L2.
3) Closing
ZK-EVM is the key to scaling @ethereum in the near future, and @Scroll_ZKP starts with an EVM-equivalent solution, allowing existing applications and developer tools to migrate from @ethereum to @Scroll_ZKP without deep adjustment or rewriting.
Moreover, @Scroll_ZKP sticks to its vision of achieving the same-leveldecentralization and censorship resistance as @ethereum itself. Hopefully, @Scroll_ZKP Tech could realize these goals step by step.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
#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.
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.
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.