The Ethereum Foundation and Open Anonymity have launched zkAPI on mainnet, bringing an AI-payment architecture co-authored by Davide Crapis and Vitalik Buterin into a live financial environment. Etherscan records show the system's core vault was created on Sept. 30, one day before the Oct. 1 announcement, with the current mainnet manifest using native ETH accounted in whole gwei rather than the USDC credits described in initial announcement materials.
Dual Withdrawal Routes and 24-Hour Challenge Windows
The zkAPI protocol allows users to fund metered API requests using zero-knowledge proofs while maintaining their private spending state locally in a digital wallet. Individual requests do not execute onchain transactions; instead, the billing server signs successor states indicating remaining balances. Users seeking to withdraw funds have two available pathways: a cooperative mutual close requiring a server signature, or an uncooperative escape withdrawal.
If a billing server goes offline or fails to respond, a user can initiate an escape withdrawal without server authorization. The protocol removes the note from the active set and enforces an 86,400-second (24-hour) challenge period. During this window, a challenger can submit an original request proof bearing the same cryptographic nullifier to prove prior state usage, which cancels the pending payout and restores the note to the active set without imposing a monetary penalty. If no valid challenge occurs within 24 hours, finalization pays the recorded balance to the user and sends any unspent share to the treasury.
Owner Pause Controls and 30-Day Expiry Limits
The vault smart contract grants the owner administrative pause powers that affect deposits, mutual close attempts, and the initiation of new escape withdrawals. However, pausing the contract does not freeze already-pending escape finalizations, active challenges, or expiry claims. The setup ensures that while new exits can be halted during an administrative pause, existing escape processes continue uninterrupted.
Additionally, the mainnet manifest specifies a 30-day note lifetime, with expiry timestamps rounded upward to a one-day boundary. Unclaimed balances from expired notes can be directed to the treasury, establishing explicit timelines for balance recovery. This balance protection framework mirrors broader efforts to manage risks across smart contract infrastructure, such as recent security precautions taken in Ethereum smart contract environments.
Key Takeaways
- zkAPI was co-authored by Vitalik Buterin and Davide Crapis and built by Open Anonymity with the Ethereum Foundation.
- Core vault contracts created on Sept. 30 operate using native ETH accounted in whole gwei.
- Users can trigger an escape withdrawal without server approval, subject to a 24-hour (86,400-second) challenge window using cryptographic nullifiers.
- Contract owners possess a pause switch that prevents new escape initiations but cannot stop pending finalizations.
- Notes carry a 30-day expiration lifetime before remaining funds are transferred to the treasury.
Why It Matters
The mainnet deployment of zkAPI provides a practical test for privacy-preserving micro-payments in autonomous AI services. By establishing an uncooperative exit route that bypasses server permission, the architecture solves a key trust problem in prepaid API infrastructure. If successful, this design could set a new benchmark for metered billing models across decentralized networks and layer-2 scaling solutions.
