# Retroactive Grant Application - ZAP1 Attestation Protocol and Verification Too…ling
## Terms And Conditions
- [x] I agree to the Grant Agreement terms if funded.
- [x] I agree to provide KYC information if funded above `$50,000` USD.
- [x] I agree to disclose conflicts of interest.
- [x] I understand this program is only for fully completed work.
- [x] I understand applications for planned or partially finished work will not be considered.
- [x] I understand all completed work must be publicly verifiable and accepted by intended users or their representatives.
- [x] I agree that for new open-source software, I will maintain a `CONTRIBUTING.md` file that reflects high Zcash development standards.
- [x] I understand that when contributing to existing Zcash code, I am required to adhere to the project-specific contribution guidelines.
- [x] I understand I must copy this proposal into a separate Community Forum thread in the Retroactive Grants category.
- [x] I understand grants are valued in USD but disbursed in shielded ZEC, and disbursement amounts may fluctuate with the ZEC/USD exchange rate.
## Application Owners
`@Zk-nd3r`
## Organization Or Individual Name
Frontier Compute LLC
## Additional Team Members
```yaml
team_members: []
```
## How Did You Learn About This Program?
Zcash Community Forum / FPF Coinholder-Directed Retroactive Grants Q2 2026 announcement.
This application is retroactive and limited to completed public work. It does not request funding for future hardening, third-party integrations, adoption work, or new milestones.
## Requested Grant Amount
`$28,000`
This reflects completed open-source infrastructure, public Zcash mainnet anchoring, protocol documentation, verification tooling, and public package distribution.
## Category
Infrastructure
## Project Summary
ZAP1 is an open-source application-layer attestation protocol for Zcash that provides BLAKE2b Merkle commitments, Orchard shielded memo anchoring, standalone verification tooling, public API endpoints, and package distribution. It lets applications prove completed lifecycle events through public commitments without exposing customer rows, private payment data, custody, or a centralized attestation service.
## Project Description
The work completed from March 2026 through May 2026 delivered a public, MIT-licensed reference implementation and live Zcash mainnet deployment of the ZAP1 attestation protocol.
Completed deliverables include:
- ZAP1 reference implementation in Rust.
- BLAKE2b Merkle commitment scheme for lifecycle events.
- Orchard shielded memo anchoring on Zcash mainnet.
- Public API for stats, scanner health, anchor status, anchor history, protocol info, and verification surfaces.
- Standalone verification crate and memo decoder crate.
- JavaScript/NPM distribution for client-side verification tooling.
- Structured memo / ZIP draft work for broader ecosystem review.
- Public protocol documentation and contribution guidance.
- CI-backed repository with test coverage and automated checks.
- Live scanner state with current mainnet sync and anchor history.
The work is completed and public. Future work, integrations, or product-specific deployments are not part of this retroactive request.
## Technical Approach
ZAP1 uses application-level event commitments rather than exposing application records directly. Events are hashed into a Merkle tree. The Merkle root is anchored to Zcash using shielded Orchard memo data. Reviewers can verify public anchor history and proof material without requiring private user records, spending keys, viewing keys, customer rows, balances, addresses, or raw transaction data.
The technical stack includes:
- `zap1`: core Rust implementation, protocol documentation, tests, and conformance tooling.
- `zap1-verify`: standalone Rust verification crate.
- `zcash-memo-decode`: universal decoder for Zcash shielded memo formats, including ZAP1 attestation identification.
- `@frontiercompute/zap1`: JavaScript package for verification clients.
- Live API endpoints for public stats, health, anchor status, anchor history, and protocol info.
The protocol is designed to be independent of any one hosted service. Hosted APIs make verification easier, but the repository and package artifacts are open source and self-verifiable.
## Time Period Of Work Completion
March 2026 through May 2026.
## Total Budget
`$28,000`
## Budget Breakdown
```yaml
total_requested_usd: 28000
items:
- category: protocol_implementation_and_verification_tooling
amount_usd: 22000
description: Rust implementation, BLAKE2b Merkle commitments, Orchard memo anchoring, verification crate, memo decoder, API verification surfaces, tests, CI, and release work.
- category: infrastructure_and_operations
amount_usd: 4000
description: Mainnet scanner/API hosting, monitoring, domains, CI runs, and operational support during the completed work window.
- category: documentation_and_release
amount_usd: 2000
description: Public protocol docs, contribution guide, ZIP draft work, package release notes, and reviewer-verification materials.
```
## Previous Funding
No.
## Previous Funding Details
The earlier proactive ZCG application for ZAP1 was closed without funding:
- https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/258
No funds were received from that application.
## Other Funding Sources
No.
## Other Funding Sources Details
N/A.
## Success Metrics
Publicly verifiable metrics observed on 2026-05-12:
- ZAP1 repository is public and MIT licensed: https://github.com/Frontier-Compute/zap1
- Public reference commit: `59279222584e490f099a2f358c248cab5e800466`
- CI success for the public reference commit: https://github.com/Frontier-Compute/zap1/actions/runs/25327861079
- Live Zcash mainnet scanner health: `scanner_operational=true`, `rpc_reachable=true`, `sync_lag=0`, `network=MainNetwork`, `chain_tip=3339962`.
- Live ZAP1 stats: `29` anchors, `327` leaves, `9` event types.
- First observed anchor block: `3301151`.
- Last observed anchor block in stats: `3317133`.
- Anchor status: `needs_anchor=false`, `unanchored_leaves=0`, `recommendation="up to date"`.
- Current ZAP1 root: `3703f07ee72df334a447a1d7dc37bdefcfe5b2b469ec3d6f6868f7ca8c6e5485`.
- Last mainnet anchor txid: `77ba0fe519c24d8153df2d890e6186405678847c09ee34cfe3520f29afa8c463`.
- Protocol info reports `version=3.0.0`, `hash_function=BLAKE2b-256`, and `zip_status=draft`.
- Public README reports `118` tests and `60` automated checks.
- `zap1-verify` crate published on crates.io.
- `zcash-memo-decode` crate published on crates.io.
- `@frontiercompute/zap1` package published on npm.
- ZIP draft opened for ecosystem review: https://github.com/zcash/zips/pull/1243
These metrics are intended as verification anchors, not as a claim of final ZIP acceptance, third-party integration, broad ecosystem adoption, or formal protocol adoption.
## Proof Of Completion
Primary source links:
- ZAP1 repository: https://github.com/Frontier-Compute/zap1
- Public reference commit: https://github.com/Frontier-Compute/zap1/commit/59279222584e490f099a2f358c248cab5e800466
- Protocol documentation: https://github.com/Frontier-Compute/zap1/blob/main/ONCHAIN_PROTOCOL.md
- Contribution guide: https://github.com/Frontier-Compute/zap1/blob/main/CONTRIBUTING.md
- CI run: https://github.com/Frontier-Compute/zap1/actions/runs/25327861079
- Live stats endpoint: https://api.frontiercompute.cash/stats
- Live health endpoint: https://api.frontiercompute.cash/health
- Anchor status endpoint: https://api.frontiercompute.cash/anchor/status
- Anchor history endpoint: https://api.frontiercompute.cash/anchor/history
- Protocol info endpoint: https://api.frontiercompute.cash/protocol/info
- `zap1-verify` crate: https://crates.io/crates/zap1-verify
- `zcash-memo-decode` crate: https://crates.io/crates/zcash-memo-decode
- `@frontiercompute/zap1` package: https://www.npmjs.com/package/@frontiercompute/zap1
- ZAP1 ZIP draft: https://github.com/zcash/zips/pull/1243
## Conflict Of Interest Disclosure
The applicant is the operator of Frontier Compute and author/operator of the ZAP1 work described here.
Frontier Compute submitted a separate proactive Zush application, which was closed without funding. That application is separate from this retroactive request, and no funds were received from it.
No other conflict is being used as evidence for this request. The proposal should be evaluated on the completed ZAP1 public work and proof links above.
## Community Forum Posting
Posted in Community Grants | Retroactive Grants:
https://forum.zcashcommunity.com/t/retroactive-grant-application-zap1-attestation-protocol-and-verification-tooling/55664