Compiled by Alex Liu, Foresight News
Ethereum has successfully brought a thriving decentralized application ecosystem, but its scalability challenges are becoming increasingly severe. Developers face a difficult choice: limit the functionality and data richness of their applications, or tolerate high gas fees and gas usage limits. What if developers had a way to bypass these restrictions?
RISC Zero is one of the major zkVM developers. If you often hear zkEVM in your ears, but don’t know the difference between it and What is zkVM? You can refer to this article. RISC Zero’s latest launch is Steel, a view call proof library based on Alloy that brings a sea change to the way developers interact with Ethereum L1 or other EVM chains. Leveraging zero-knowledge proofs and RISC Zero zkVM, Steel enables developers to perform view calls and provably read and compute Ethereum's state in a scalable, secure, and cost-effective manner.
Steel bridges the gap between Ethereum application development and zero-knowledge technology, making it easier for developers to leverage the power of ZK in their smart contracts. Combined with the capabilities of RISC Zero zkVM, Steel enables developers to build more secure, scalable and efficient applications on Ethereum L1 or any EVM equivalent chain.
With Steel, developers can:
Preparing to call
Next, set up the call by instantiating the balanceOfCall structure with the target account address. At the same time, define constants for the contract address you want to query and the caller's address.
Execute the call in Main
The main function is executed in zkVM and generates zero-knowledge proof. It first reads the input environment and then constructs a ViewCallEnv object, ensuring that the current state matches the expected state root. After submitting the relevant block hash and number, perform a view call and print the balance.
How it works
Steel proves Solidity code in RISC Zero zkVM in three steps, simplifying the execution process:
Storage verification: Perform a storage integrity check to ensure that the data in the EVM database is aligned with the state root of the blockchain to confirm its legitimacy.
When using the blockhash opcode for verification in an Ethereum smart contract, the verified commitment must reference a block hash no more than 256 blocks old. Considering the average block time is 12 seconds, this sets a narrow time frame of approximately 50 minutes for complete proof generation and confirmation that the validated transaction has been included in a block.
When you need to obtain a verified block hash on the chain that is older than 256 blocks, you can use one of the following strategies:
Envision a future where off-chain computation will be seamlessly integrated with on-chain verification. Steel contributes to this vision by enabling developers to reliably access and compute the complete history of Ethereum within zkVM, allowing them to create the next generation of data-rich and more powerful on-chain applications.
The above is the detailed content of How does RISC Zero Steel accelerate Ethereum's ZK adoption?. For more information, please follow other related articles on the PHP Chinese website!