Content
@
https://ethereum.org
0 reply
0 recast
0 reaction
Danny
@mad-scientist
🚀 Scaling Ethereum L1 via tx-level Validity Proofs We're proposing EIP-TBD, an optional extension to Ethereum's transaction model that allows txs to include consent for validity proof generation and verification within a single transaction. This approach enables: Atomic Multi-Account Updates: A single transaction can update the state of multiple EOAs and smart contracts simultaneously, provided it results in a valid proof through the consent-based proof system. Enhanced Scalability: By verifying state transitions through succinct proofs, Ethereum can process more transactions with less computational overhead, akin to the benefits seen in Layer 2 validity rollups. Optional Privacy: Users can choose to enable zero-knowledge proofs, allowing for a new privacy primitive while still maintaining the integrity and security of the network. 🔧 How It Works Transaction Structure: An EOA can opt-in by including a consentData field containing: 1/3
1 reply
0 recast
0 reaction
Danny
@mad-scientist
Explicit consent for proof generation List of acceptable prover systems (e.g., STARK, Plonky2, HyperPlonk) N of M threshold requirements specifying that N out of M listed provers must validate the transaction Verification Mechanism: A new precompile, SupplyCheck, ensures that the total ETH and token supply remains consistent post-transaction, preventing unauthorized minting or burning. Proof Generation: Selected provers generate the state diff and validity proofs off-chain, which are then aggregated to a single proof and submitted on-chain. 📈 Benefits Scalability: Reduces the computational load on the Ethereum network by verifying state transitions through succinct proofs rather than executing each transaction individually. User Control: Provides users with explicit control over which proving systems they trust. Efficiency: Minimizes on-chain data by including only the aggregated proof. 2/3
1 reply
0 recast
0 reaction
Danny
@mad-scientist
Privacy: Enables confidential transactions through zero-knowledge proofs, allowing users to hide specific transaction details while maintaining overall network integrity. 🧪 Next Steps We're seeking feedback from the community to refine this proposal. Your insights on consent mechanisms, N-of-M threshold implementation, gas cost targets, privacy modes, and implementation strategies are invaluable. 3/3
0 reply
0 recast
0 reaction
