Prove what happened.

Born shielded. Without exposing what you spent.

Use cases

Auditors
Audit trail without exposing transactions
Every lifecycle event committed to a Merkle tree. Roots anchored to Zcash. Share the proof bundle, not the books.
HOSTING_PAYMENT SHIELD_RENEWAL
Bug bounty programs
Verifiable disclosure timeline
Attest each step: submission received, triage started, patch confirmed, embargo lifted. The timeline is on-chain. No disputes.
PROGRAM_ENTRY CONTRACT_ANCHOR
DeFi agents
Private funding, public performance
Agent trades cross-chain. Funding source is shielded. Trading history attested. Prove performance without revealing the wallet.
BOND_DEPOSIT STAKING_DEPOSIT
Mining operators
Every payout proved
Block mined, payout sent, hosting paid, ownership transferred. The full lifecycle anchored. Participant verifies without trusting the operator.
DEPLOYMENT HOSTING_PAYMENT
Governance
Proposals, votes, results on-chain
Submit a proposal. Cast a vote. Record the outcome. All attested with deterministic hashes. Recount anytime.
GOVERNANCE_PROPOSAL GOVERNANCE_VOTE

Pricing

Builder
500 attestations/month. Daily anchor batches. Shielded ZEC payment.
0.01 ZEC/mo
shielded payment
Operator
Unlimited attestations. Hourly anchors. Agent registration. Webhook integration.
0.1 ZEC/mo
shielded payment

All payments in shielded ZEC to unique Orchard addresses. No KYC. Read and verify endpoints are free, always.

How it works

1. POST /attest with your event data
2. Get back leaf_hash + verify URLs
3. Leaves batch into a Merkle tree
4. Root anchors to Zcash via shielded memo
5. Anyone verifies: leaf -> proof path -> root -> txid -> block height
6. Cross-chain: Solidity verifier on Ethereum checks the same root

Connect

MCP server: npx @frontiercompute/zcash-mcp
OpenClaw plugin: clawhub install @Zk-nd3r/zap1-zcash-attestation
npm: npm install @frontiercompute/zap1
Rust: cargo add zap1-verify
API docs: pay.frontiercompute.io/protocol/info
Protocol map: frontiercompute.cash/protocol.html

FAQ

What gets anchored on-chain?
The Merkle root. Individual events stay off-chain until you share the proof. The root is a 32-byte hash in an Orchard shielded memo. Nobody can see the events from the anchor alone.
Do I need a Zcash wallet?
To verify: no. Proof bundles are JSON. Check them with curl, the browser verifier, or the SDK. To pay: yes, you need a wallet that supports Orchard (Zodl, Zashi).
What if your server goes down?
Your proofs still verify. The anchor transaction is on Zcash permanently. The Merkle proof is a standalone JSON file. You can verify it with zap1-verify (Rust/WASM) or the Solidity verifier on Ethereum. No server trust required.
Can I run my own instance?
Yes. MIT licensed. git clone, generate keys, docker-compose up. The conformance kit validates your instance against the spec. 80 tests, published vectors.
Get an API key
Pay in shielded ZEC. Key in 60 seconds. No signup required.
Get started