Skip to content

Ethereum Foundation Blog

feed🛡️ Securityblog.ethereum.org ↗

2 posts in the catalog

Each feed is checked for new posts. Every post is read, and those that belong here join the catalog. What Trove read and did not keep stays on file, not shown.

blog.ethereum.orgarticle

Introducing zkAPI: private usage credits for any API

zkAPI, built by the Open Anonymity Project with the Ethereum Foundation, lets users deposit credits into an Ethereum vault contract once and then authorize bounded, metered API usage via zero-knowledge proofs instead of an API key tied to identity. The scheme uses Groth16 proofs over BN254, Poseidon-hashed note commitments in a 32-level Merkle tree, and one-way nullifiers to prevent double-spend while keeping spends unlinkable to deposits; a client mints short-lived, capped API keys locally and the server settles against the private balance via signed usage receipts. The post also candidly documents the system's limits: it doesn't anonymize network metadata/IP (mitigated by Tor) and doesn't prevent re-linking via prompt-content fingerprinting across sessions.

zkAPIEthereumOpenAI+3
Open Anonymity ProjectDavide CrapisVitalik Buterin+1

Blockchain· 2026-10-01T00:00:00+00:00

blog.ethereum.orgarticle

EF Protocol: Current and Emerging Priorities

The Ethereum Foundation Protocol cluster lays out its security-driven roadmap through 2029, centered on making Ethereum L1 quantum-resistant across execution, consensus, and data layers by December 2029 (planning for Q-day as early as 2030). It details the fork sequence delivering a minimum-viable post-quantum milestone, cryptographic agility via native account abstraction (Frame transactions, EIP-8141), retirement of vulnerable BLS withdrawal credentials (EIP-8365), and censorship-resistance and privacy work via FOCIL (EIP-7805), EIP-8369, EIP-8250 and EIP-8272.

Ethereum
EIP-7805EIP-8141EIP-8369+9

Blockchain· 2026-09-07T00:00:00+00:00