zx402 Dey Test Private Funding for AI Agents for Cardano

zx402 don document two service purchases for Cardano Preprod using one pool wey dem design to separate AI agent spending from the original wallet. The October 7 tests dey address one privacy wahala for automated commerce: public payment histories fit reveal the agent suppliers, how often e dey buy, and im operating budget.

Two Purchases Through x402 and Masumi

The first demonstration pay one weather service through x402, wey dey use HTTP 402 to request payment. The response cost 2 tUSDM, with separate fee for the relayer wey submit the pool transaction.

Using funds wey dem don deposit before, the pool finance one fresh one time address wey complete standard x402 payment. The service return weather response, while the remaining balance remain inside the pool for another purchase.

The second test pay the Masumi agent “Expose: Web Single Answer” 0.01 tUSDM to explain zero knowledge proof for one sentence. For here, the pool fund the purchasing wallet of one Masumi payment node. Funds then enter Masumi escrow, and the published log record the task as completed.

The difference matter for the payment flow: the x402 test use one one time address, while the Masumi test fund existing purchasing wallet. The team publish terminal logs and transaction links for both runs, and dem use test tokens instead of mainnet funds.

How the Cardano Privacy Pool Works

Agent go deposit funds publicly and keep one private note wey record im claim to the funds. Once dem approve the deposit, the agent go generate zero knowledge proof locally to show say e own approved, unspent funds without revealing which deposit dey behind the purchase.

Relayer go submit the proof and the transaction. For standard x402 flow, the pool go fund new one time address before payment reach the seller. According to the documentation, sellers fit accept these payments without integrating zx402 specific code. Unspent funds go turn new private note wey go dey available for later purchases.

Privacy get defined limits. Amounts, timing, and outgoing pool payments still dey visible. If pool small or amounts match, e fit easy to correlate transactions, and if person withdraw the remaining balance publicly, e fit expose connection to earlier purchases.

The agent blockchain infrastructure provider fit still observe the addresses and requests. So the design target the public link between funding and spending, and extra privacy go depend on how the agent take access the network.

What Remains Before Mainnet

The source code, SDK, and testing instructions dey available to developers. The public website provide documentation but e no connect wallets or execute transactions.

Deposit approval don implement, but external screening never dey. The current service dey approve deposits unless one configured denial function reject them; no screening data source connect.

Costs still shape how dem intend make people use am. Cardano outputs must contain minimum amount of ADA, so the team position the pool for bigger payments, escrow funding, and payment channels instead of individual blockchain transactions for every cheap API request.

Mainnet deployment still dey pending, and nobody outside the project don review the design or the code. Before dem accept outside funds, zx402 list multiparty cryptographic setup and external security audit as part of wetin dem require. E still need new pool with blockchain checks wey go enforce correct starting state, to replace the current reliance on the deployer to initialize am correctly.