Ethereum

🚀 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

Unpopular opinion: The best way to scale Ethereum is by setting explicit standards for precompiles, and any team fully checking the list can add it in the next HF. This way any validity/ZK team can get their contract onchain. Combined with https://warpcast.com/mad-scientist/0xccb110f4, they will be able to rollup txs in L1.

Scientist by day, other things at night.

Writing complex and nuanced takes, viewed by few, appreciated by none.

The standards need to prioritize Etherem security, not contract content/logic. So things like multi-client implementation and testing, to show all clients always get the same result. Correct gas pricing, reasonable execution time in all cases. It's also possible to signal that if this doesn't catch up, it may be limited to say 5 years, after which clients will no longer support it.