EIP-8250 Keyed Nonces for Frame Transactions announced
Vitalik calls keyed nonces a first foray into a new state scaling strategy
native proof verification proposal
EL reorg state retention window EIP
ERC-7943 goes Final
soispoke announced EIP-8250 (Keyed Nonces for Frame Transactions), authored by soispoke, nero_eth, lightclient and Vitalik. Vitalik said keyed nonces are not only in protocol support for privacy solutions but possibly a first step toward a new state scaling strategy. donnoh proposed native proof verification, opening the CL proof verification stack to all rollups and ZK apps. nerolation submitted an EL reorg state retention window EIP.
18:59; Magicians discussion, 15:38: nonce_key 0 aliases the legacy account nonce, and each non zero key selects an independent sequence stored in a NONCE_MANAGER system contract.
Soispoke: new EIP-8250, Keyed Nonces for Frame Transactions, replacing the single sender nonce with (nonce_key, nonce_seq) to give frame transactions independent replay domains, 18:59; Magicians discussion, 15:38: nonce_key 0 aliases the legacy account nonce, and each non zero key selects an independent sequence stored in a NONCE_MANAGER system contract.
Soispoke: privacy protocols will become first class citizens on Ethereum, with a Dune dashboard of nullifier state growth for planning, 14:32; nero_eth: privacy and 2D nonces, 21:49; lightclients: privacy is good, 22:13.
Soispoke: privacy protocols will become first class citizens on Ethereum, with a Dune dashboard of nullifier state growth for planning, 14:32; nero_eth: privacy and 2D nonces, 21:49; lightclients: privacy is good, 22:13.
21:27: generalizes EIP-8025 so CL proof verification is program agnostic, and exposes it to contracts through a proof carrying transaction type and three opcodes (PROGRAMHASH, PUBVALUESHASH, PROOFCOUNT), so zkVM fixes ship with client releases instead of per project governance upgrades; donnoh_eth's intro, 21:35.
Ethresear.ch: Native proof verification, 21:27: generalizes EIP-8025 so CL proof verification is program agnostic, and exposes it to contracts through a proof carrying transaction type and three opcodes (PROGRAMHASH, PUBVALUESHASH, PROOFCOUNT), so zkVM fixes ship with client releases instead of per project governance upgrades; donnoh_eth's intro, 21:35.
(nerolation), submitted: EL clients keep state for at least 262,144 blocks (about 36.4 days) so they can process any reorg locally without resyncing, covering leak scenarios with up to about 79% of stake offline.