Vitalik responded to bunker mode: he does not recommend scrambling to move funds today, but the risks to cryptography from AI-accelerated math should be taken seriously. soispoke explained how EIP-8288 lets privacy apps generate post-quantum proofs on user devices while nodes verify them outside the EVM. Account abstraction specs were reshaped: EIP-8130 is narrowed to the Keystore with its transaction type moved to a new EIP, and several frame-related PRs to EIP-8141, EIP-7906 and EIP-8250 were merged. ACDE #247 met in the evening.
06:28, but the risks to cryptography from AI-accelerated math deserve serious attention, not just quantum. Correction: for multisigs, the ideal "safe" rule is that each signer changes their key after each operation, 11:07.
Vitalik: I don't recommend anyone scramble to move their funds to new wallets today, 06:28, but the risks to cryptography from AI-accelerated math deserve serious attention, not just quantum. Correction: for multisigs, the ideal "safe" rule is that each signer changes their key after each operation, 11:07.
22:34 (soispoke, post at 22:59). EIP-8288 lets transactions depend on leanSPHINCS signatures and leanSTARK proofs declared in the dependency frame of an EIP-8141 frame transaction. Nodes check them before forwarding, and each block carries one recursive STARK proving all its dependencies valid. Today's privacy pools verify Groth16 proofs in-contract with the BN254 pairing precompile, which a quantum computer that breaks BN254 could forge. With EIP-8288, the pool contract only checks that the transaction depends on a proof for its own circuit with the expected public inputs. The post compares the EVM, RISC-V and an eISA designed for proving.
Ethresear.ch: exposing an ISA for post-quantum proofs on Ethereum, 22:34 (soispoke, post at 22:59). EIP-8288 lets transactions depend on leanSPHINCS signatures and leanSTARK proofs declared in the dependency frame of an EIP-8141 frame transaction. Nodes check them before forwarding, and each block carries one recursive STARK proving all its dependencies valid. Today's privacy pools verify Groth16 proofs in-contract with the BN254 pairing precompile, which a quantum computer that breaks BN254 could forge. With EIP-8288, the pool contract only checks that the transaction depends on a proof for its own circuit with the expected public inputs. The post compares the EVM, RISC-V and an eISA designed for proving.
Was merged (chunter-cb). Ethereal news's roundup, 02:44, lists the new EIP-8430 account abstraction transaction type (split out from EIP-8130) and EIP-8425, quantum freeze and account recovery.
EIP-8130 PR: scope to the Keystore and move the transaction type to a new EIP was merged (chunter-cb). Ethereal news's roundup, 02:44, lists the new EIP-8430 account abstraction transaction type (split out from EIP-8130) and EIP-8425, quantum freeze and account recovery.
EIP-8141 (frame transactions): frame modes checked against a set of valid values was merged (lightclient); roll back the approval context when a call reverts was submitted (soispoke).
EIP-8141 (frame transactions): frame modes checked against a set of valid values was merged (lightclient); roll back the approval context when a call reverts was submitted (soispoke).
EIP-8250: record keyed nonces in the block access list was merged (nerolation); EIP-3298: remove the refund cap from frame transaction settlement was merged.
Met at 21:00. Topics included Glamsterdam and Hegotá progress, Sepolia fork scheduling, gas limit changes and complexity assessments. EIP-8081 records the ACDE247 decisions, merged.
ACDE #247 met at 21:00. Topics included Glamsterdam and Hegotá progress, Sepolia fork scheduling, gas limit changes and complexity assessments. EIP-8081 records the ACDE247 decisions, merged.
StarkWare: seriously considering becoming an independent L1 to complete the transition to post-quantum and AI security, 21:58; Eli Ben-Sasson opened the debate, 15:19.