Shielded x402: private machine payments for Zcash

1. Executive summary and decision snapshot

Request: $42,000 for “Shielded x402,” an open-source specification, reference facilitator/testnet demo, and spending-control library for shielded ZEC machine payments. Delivery rests with baby-zack-agent, a pseudonymous sole developer self-described as an autonomous AI agent. The application is under review. [1]

Four milestones cover specification, implementation, wallet controls, and handoff through February 2027. The strongest capability claim is prior development of x402-spendguard, directly related to the proposed payment-control work. [4]

Evaluation judgment: The decisive issues are additional value versus existing implementations, credible private-payment verification, accountable delivery, and whether a testnet infrastructure deliverable justifies the expenditure without adoption commitments. These are evaluation questions, not established failures. [1][4]

2. Applicant and team track record

The applicant reports shipping x402-spendguard, compaction-snapshotter, and rules-linter as public, tested, documented tools, and being a registered ZecHub contributor. No additional team members are named; specification, implementation, testing, documentation, and reporting all sit with the lead. [1]

Inference: Related x402 tooling is a useful starting point, but does not itself demonstrate competence in shielded-payment verification or secure Zcash wallet integration. [1]

For independently verified code quality, prior grant delivery, user uptake, or measured outcomes: No grounded evidence found. The supplied capability evidence is applicant-reported and does not establish a complete grant history. [1]

3. Proposal scope, milestones, budget, technical approach, and dependencies

The proposed milestone schedule is: [4]

Payment clarification: The applicant acknowledged initial double-counting and confirmed that the $8,000 startup disbursement is M1, not an additional payment; total funding is $42,000. [6]

The technical plan pins an x402 specification version and implements ZEC settlement through a facilitator-side adapter. Confirmation would use viewing keys/memo-field proofs; wallet controls include caps, allowlists, approval thresholds, and an audit trail. Dependencies are Zcash testnet, lightwalletd, maintained Zcash libraries, and x402 semantics, without consensus changes or forks. Outputs are intended to be MIT-licensed and CI-tested. [1][4]

The applicant defines success as shipped infrastructure, not merchant adoption. Monthly updates and shielded-ZEC disbursement are proposed. [4]

For completed milestones, measured outcomes, itemized labor costs, a named independent reviewer, or detailed acceptance tests: No grounded evidence found. The supplied text establishes deliverable categories, not their demonstrated performance. [1][4]

4. Community discussion, arguments, responses, and resolution

• Strongest supporting argument: Privacy-preserving API payments could protect agents’ commercial activity. A forum participant calls the idea useful and in demand; this supports interest, not demonstrated adoption. [4]
• Strongest challenge: Another participant says “we already have this,” directly questioning novelty. No competing implementation or feature comparison accompanies that assertion, and no applicant response resolving it is supplied. It is therefore an unresolved additionality question, not proof of duplication. [4]
• Applicant positioning: The applicant explicitly frames the grant as infrastructure rather than go-to-market funding. That clarifies the intended output but leaves prospective use and integration value unproven. [4]
• Resolved concern: The applicant’s correction resolves the startup-versus-milestone arithmetic. It does not resolve whether the price is justified or what safeguards accompany advance payment. [6]

No grounded evidence found of a substantive technical rebuttal, agreed privacy threat model, or resolution of the existing-solution challenge in the supplied discussion. [4]

5. Relevant precedents and documented outcomes

Shielded Micropayments SDK for Privacy-Preserving Rewards — $29,000, declined. Its shielded-micropayment developer-tooling focus makes it a relevant comparison by subject. However, for documented decline reasons or technical findings: No grounded evidence found. Its rejection alone provides no basis for rejecting this request. [8]

Zush — $100,000, declined. This proposal combined a shielded-ZEC spending product with x402/CipherPay and card infrastructure. Committee reasons included commercial-product orientation, spending concentrated on making cards available, US-only reach, and concerns about market practicality and ZCG scope. [9]

Inference: Zush is most useful as a scope precedent: reusable public infrastructure should be distinguished from subsidizing a commercial distribution product. Its rejection does not establish that a shielded-x402 adapter is technically unnecessary or unsuitable. [1][9]

6. Material risks and execution considerations

• Privacy and security — inference: Viewing-key/memo-based verification creates a consequential design boundary: the committee needs evidence of what each party can observe and how payments are bound to requests. An independent spot-check is planned, but that commitment alone is not security assurance. [1][4]
• Accountability and continuity — inference: Sole delivery by a self-described autonomous agent makes contracting responsibility, key control, recovery, and maintenance arrangements particularly important. The supplied application names no additional delivery personnel. [1]
• Value and demand: The applicant cites 160 million-plus x402 payments and $50 million-plus volume, and asserts that Zcash has no presence in that market. These are applicant claims without independent substantiation in the supplied evidence; they should not be treated as validated demand for this implementation. [1]
• Deployment boundary — inference: A successful testnet demo would establish less than production readiness. Mainnet operation, sustained service availability, and downstream adoption should not be assumed from the proposed deliverables. [4]

7. Material gaps and questions for the applicant

• Additionality: Which existing shielded-x402 implementations were assessed, and what concrete capabilities would this grant add rather than duplicate?
• Verification and privacy: What threat model, request-binding rules, replay protections, confirmation policy, and viewing-key access limits will the specification require?
• Acceptance and review: Who will independently assess payment verification, what tests determine milestone acceptance, and must identified defects be fixed before payment?
• Accountability: Who can execute the grant agreement, control disbursements, respond to incidents, and continue delivery if the agent or its hosting becomes unavailable?
• Cost and advance funding: What effort, rates, review costs, and operating expenses support each milestone, and what remedy applies if the prepaid specification is not accepted?
• Use and handoff: Which prospective integrators will validate the interface, and who will maintain the code after February 2027?

These questions target the scope, assurance, staffing, and payment commitments described in the proposal. [1][4][6]

8. Neutral decision considerations

Committee judgment: Evaluate this as a bounded infrastructure experiment, separating successful delivery from adoption and production-security claims.

Possible funding conditions include an agreed non-duplication assessment, a reviewable privacy specification, named acceptance reviewers, and explicit treatment of the M1 advance. A staged commitment could limit exposure while testing feasibility; conversely, further specification work could delay a potentially useful integration. These are options for committee deliberation, not an approve-or-reject recommendation.

9. Numbered source list

• [1] Grant Application - Shielded x402: private machine payments for Zcash — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/445
• [4] Grant Application - Shielded x402: private machine payments for Zcash — posts 1–5 — https://forum.zcashcommunity.com/t/grant-application-shielded-x402-private-machine-payments-for-zcash/57826/1
• [6] Comment on #445: Grant Application - Shielded x402: private machine payments for Zcash — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/445#issuecomment-5855072138
• [8] Grant Application – Shielded Micropayments SDK for Privacy-Preserving Rewards — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/236
• [9] Grant Application Zush - shielded ZEC spend path for cohort 0 — comparison summary — https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/281