Skip to content
FORENSIAWeb3 forensicsOpen workspace
FORENSIAOpen workspace
Menu
← All news & explanations
Infrastructure / Explained

A deposit does not reveal every request it paid for.

zkAPI separates Ethereum payment records from API usage, with limits on network and content privacy.

Publisher date Forensia brief · 26 Oct 20262 min read
Original conceptual illustration. Not a photograph or incident evidence.
Reading history stays in this browser. Manage it in My Explore.

What changed

The Ethereum Foundation describes zkAPI, a system that funds private usage credits through an Ethereum vault and authorizes API spending with proofs. Public deposits and withdrawals do not expose the individual requests paid for.

Why it matters

Payment privacy does not make request contents or network metadata private. A provider may still observe the request and correlate timing; a chain transfer alone cannot establish which conversation or API call followed.

Take it into Forensia

Keep the transaction separate from the story.

Read the transaction guide before opening a supported Ethereum record. Record what the source shows and leave off-chain service usage unproven unless separate evidence supports it.

Read a transaction ↗

Forensia is not integrated with zkAPI and cannot link its private credits to individual requests. This is an explanation of the published design, not a new launch alert.

Keep the thread going.

All briefs ↗