zkAPI Launches on Ethereum Mainnet with Escape Withdrawal Feature

zkAPI, which separates AI API payments from user identity verification, has begun operations on the Ethereum mainnet. Users can request escape withdrawals without server approval, but if the payment status has already been used for an API transaction, the payout may be canceled. If active deposit notes are not settled within their deadline, all funds will transfer to a treasury.
Ethereum Foundation announced zkAPI's operation on Ethereum mainnet as of October 1, 2026. The system was developed in collaboration with Open Anonymity project and is based on API credit design published by Davide Crapis and Vitalik Buterin on February 11.
Users deposit ETH to create private notes, then approve API usage via zero-knowledge proofs generated in the browser without sending Ethereum transactions for each request. Payment servers verify proofs but cannot see which deposits were used. This structure aims to make linking payment records with API usage difficult. However, prompts are shared with inference providers and network information like IP addresses and timestamps may still be exposed. Full anonymity of requests or network details is not achieved.
Withdrawal options include server-approved mutual termination or user-initiated escape withdrawals. The current public configuration sets a 24-hour dispute window (86,400 seconds) for escape withdrawals. After this period, pending payments become final. If the payment status has already been approved for API usage, a disputing party can prove their claim to cancel the withdrawal and reactivate the note.
Active notes have expiration conditions. Protocol documentation states that unprocessed expired notes trigger a claimExpired procedure transferring all funds to treasury. Note lifespan is 30 days with rounding up at day boundaries, meaning actual expiration may be slightly later than exactly 30 days. Treasury owners can pause deposits, mutual terminations, and new escape withdrawal requests but not final payments for pending withdrawals or disputes.
The project repository marks zkAPI as experimental. Documentation notes that Groth16 setup is single-participant only with no multi-party setup in progress. Mainnet operation indicates deployment completion but does not guarantee full fund recovery in all scenarios. Thus, escape withdrawals allow initiation without server cooperation but require preservation of latest payment status and wallet recovery information for potential refunds, along with dispute procedures and note expiration timing.
Current protocol documentation specifies that native ETH is the only supported deposit asset via SDK and treasury.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: zkAPI, 24시간 이의 제기 뒤 탈출 출금…노트 만료 땐 예치금 귀속