# Call For Proposals: Coinholder-Directed Retroactive Grants Program Q3 **URL:** \ **Category:** Retroactive Grants\ **Created:** [August 2, 2026, 11:29pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885 "2026-08-02T23:29:25Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![FPF](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/fpf/32/30829_2.png) [@FPF](https://forum.zcashcommunity.com/u/FPF)\ **Post date:** [August 2, 2026, 11:29pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/1 "2026-08-02T23:29:25Z")
**Call for proposals** The Coinholder-Directed Retroactive Grants Program is now accepting proposals for the Q3 2026 round. You can submit a proposal for your own completed work or nominate an individual, company, or project you believe should receive funding to apply for a grant. Retroactive grants provide funding for work that has already been completed and can be publicly verified. Coinholders will decide which proposals to fund through a coinholder vote scheduled for September. **Deadline to submit a proposal:** August 14th at 20:00 UTC After the submission deadline, there will be a mandatory 30-day review period from Monday, August 17 to Wednesday, September 16. The coinholder poll will then run from Thursday, September 17 through Tuesday September 29. How to Submit: 1. Complete the [proposal template on GitHub](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/new?template=grant_application.yaml). 2. Copy and paste your completed proposal into a new separate thread in the [Community Grants | Retroactive Grants](https://forum.zcashcommunity.com/t/about-the-retroactive-grants-category/52106) section of the Zcash Community Forum so the community can provide feedback on each proposal. If you already submitted a proposal for the canceled Q2 vote then no further action is needed, your proposal will be included for Q3. If adjustments are required for your proposal please update both GitHub and your forum post. If you have any questions about the process or your submission, please post them in this thread. Thanks! **Current Q3 submissions:** - Expanding Zcash In Unstoppable Wallet, [Forum Post](https://forum.zcashcommunity.com/t/expanding-zcash-in-unstoppable-wallet-liquidity-swaps-distribution-retroactive-grant/55529), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/25) - Open-Source Zcash Hardware-Wallet SDK, [Forum Post](https://forum.zcashcommunity.com/t/application-for-coinholder-directed-retroactive-grants-program-q2-2026-open-source-zcash-hardware-wallet-sdk/55550), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/28) - Zafu Wallet, [Forum Post](https://forum.zcashcommunity.com/t/zafu-wallet-retroactive-grant-application/55551), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/29) - CipherPay, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-cipherpay/55612), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/30) - ZAP1 Attestation Protocol and Verification Tooling, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zap1-attestation-protocol-and-verification-tooling/55664), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/31) - THORSwap/Metro, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-thorswap-metro/55675), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/32) - ZODL Q1 2026 Core Protocol Development, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zodl-q1-q2-2026-core-protocol-development/57027), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/33) - Zcash Grants Hub, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zcash-grants-hub-coinholder-program/55372), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/24) - ZcashNames, [Forum Post](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/9), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/34) - ZecBooks, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zecbooks/56914), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/38) - Blindvault, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-blindvault/56932), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/39) - Nozy Wallet, [Forum Post](https://forum.zcashcommunity.com/t/nozy-wallet-retroactive-grant/52417/26), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/37) - Zapp, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zapp/56937), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/40) - lightwalletd-rs, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-lightwalletd-rs/56955), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/41) - Zecledger, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-zecledger/56969), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/42) - Gleyo, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-gleyo/56977), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/43) - Zallet RPC Parity Harness, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zallet-rpc-parity-harness/56993), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/45) - ZecKit Post-M3 Stabilization and Developer Adoption, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zeckit-post-m3-stabilization-and-developer-adoption-work/56992), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/44) - Zec-ironwood-reconcile, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zec-ironwood-reconcile-reproducible-orchard-ironwood-value-pool-reconciliation/56998), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/46) - CipherScan, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-cipherscan/56997), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/47) - Zecmap, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zecmap/56999), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/48) - Self-Sovereign Zcash Testnet Faucet, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-self-sovereign-zcash-testnet-faucet/57002), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/49) - Ironwood zk-SNARK Formal Verification (Project Tachyon), [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-ironwood-zk-snark-formal-verification-project-tachyon/57007/1), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/50) - Orchard Counterfeiting Vulnerability Bug Bounty, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-orchard-counterfeiting-vulnerability-bug-bounty/57008), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/51) - Bonus Grant for Ironwood zk-SNARK Formal Verification, [Forum Post](https://forum.zcashcommunity.com/t/project-tachyon-bonus-grant-for-ironwood-zk-snark-formal-verification/57021), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/52) - Zebra Critical Vulnerability Bug Bounty (CVE-2026-34202), [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-cve-2026-34202-zebra-remote-denial-of-service-critical/57024), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/54) - Bonus Grant for Orchard Counterfeiting Vulnerability Bug Bounty, [Forum Post](https://forum.zcashcommunity.com/t/taylor-hornby-bonus-grant-for-orchard-counterfeiting-vulnerability-bug-bounty/57025), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/53) - Connaugh Zcash Videos, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zkmarketer-videos/57031), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/55) - Ironwood external audit reimbursement, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-ironwood-external-audits/57032), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/56) - Temporary Detectable Unlimited mint and sell Exploit, [Forum Post,](https://forum.zcashcommunity.com/t/retroactive-grant-application-temporary-detectable-unlimited-mint-and-sell-bug-bount/57033) [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/57) - Five Critical Zebra Consensus Divergence Vulnerabilities, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-five-critical-zebra-consensus-divergence-vulnerabilities/57034), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/58) - [CyphZec.com](http://cyphzec.com), [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-cyphzec-com/57035), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/59) - zcashtocash via ZcashLabs, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-zcash-labs-for-zcashto-cash/57047), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/60) - Zec.rocks (16 months of uptime for Zcash wallets), [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-16-months-of-uptime-for-zcash-wallets-zec-rocks/57048), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/61) - ShieldedScan, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-shieldedscan/57051), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/62) - Valargroup Ironwood work, [Forum Post](https://forum.zcashcommunity.com/t/retroactive-grant-application-valargroup-ironwood-work/57053), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/64) - Frontier Compute Zcash Security Research and Remediation Pack, [Forum Post](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/29), [GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/63) ---
**Author:** ![Alex\_ZF](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/alex_zf/32/18974_2.png) [@Alex\_ZF](https://forum.zcashcommunity.com/u/Alex_ZF)\ **Post date:** [August 2, 2026, 11:29pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/2 "2026-08-02T23:29:40Z")
---
**Author:** ![aryaethn](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/aryaethn/32/46620_2.png) [@aryaethn](https://forum.zcashcommunity.com/u/aryaethn)\ **Post date:** [August 3, 2026, 7:17am UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/3 "2026-08-03T07:17:28Z")
Hey there, Is this program just for those projects that are completed? Or can someone with a “good enough” idea request a grant to start their work right away? Thanks ---
**Author:** ![strahncryptography](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/strahncryptography/32/46464_2.png) [@strahncryptography](https://forum.zcashcommunity.com/u/strahncryptography)\ **Post date:** [August 3, 2026, 11:26am UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/4 "2026-08-03T11:26:08Z")
Retroactive grants are only for completed work and the community votes on it by using the finished product. ---
**Author:** ![FPF](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/fpf/32/30829_2.png) [@FPF](https://forum.zcashcommunity.com/u/FPF)\ **Post date:** [August 3, 2026, 11:58am UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/5 "2026-08-03T11:58:29Z")
**Understanding the Coinholder-Directed Retroactive Grants Program (CDRGP)** The Coinholder-Directed Retroactive Grants Program (CDRGP) is one of three Zcash grant programs, alongside [Zcash Community Grants](https://zcashcommunitygrants.org/) (ZCG) and the [ZecHub Bounty Program](https://bounties.zechub.wiki/). It’s funded by 12% of block rewards (per ZIP 1016, in effect from November 2025 through Zcash’s third halving in 2028) plus initial capital from the Deferred Dev Fund Lockbox. Funds are held in a legally binding multisig wallet managed by Keyholder Organizations and FPF administers the program’s submission and reporting process. ## Who can apply - **Anyone** can submit a proposal — for their own completed work, or to nominate another individual, company, or project. - Grants are **retroactive only** : the work must already be fully completed and publicly verifiable at the time of submission. This program does not fund proposed or in-progress work. - There’s no fixed cap on request size, but grants above **$50,000** require FPF to perform KYC checks before disbursement. - If a proposal is rejected by coinholders, the applicant can still resubmit it for consideration through ZCG’s milestone-based model instead. ## Process 1. **Call for Proposals** — Announced each quarter via the forum, GitHub, and social channels. 2. **Submission** — Complete the [proposal template on GitHub](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/new?template=grant_application.yaml), then mirror it as a new thread in the forum’s Retroactive Grants category so the community can give feedback. 3. **Mandatory 30-day Review Period** — Proposals are discussed publicly; anyone can ask questions or raise concerns directly in the applicant’s thread. 4. **Proposal Summary** — FPF publishes a summary of all proposals before polling opens (total requested funding, treasury impact, historical outcomes). 5. **Coinholder Poll** — Each proposal is voted Yes/No individually. A minimum participation threshold of ~420,000 ZEC (~2% of supply) per proposal is required for the vote to count, and a simple majority passes. 6. **Funding & Disbursement** — Proposals are approved by total “Yes” votes. Payments come directly from the multisig wallet in ZEC (requests are denominated in USD). [Keyholders retain veto authority pre- and post-approval for legal, regulatory, or community-harm concerns](https://zips.z.cash/zip-1016). **Current cycle (Q3 2026):** - Call for Proposals: through August 14 @ 20:00 UTC - Review Period: August 17 – September 16 - Coinholder Poll: September 17 – September 29 _(Proposals already submitted for the canceled Q2 round carry over automatically — no resubmission needed unless changes are required.)_ ---
**Author:** ![paperX](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/paperx/32/44919_2.png) [@paperX](https://forum.zcashcommunity.com/u/paperX)\ **Post date:** [August 3, 2026, 4:56pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/6 "2026-08-03T16:56:50Z")
Thank you for allowing us ([THORSwap](https://thorswap.finance/)/[Metro](http://metro.exchange/)) to qualify for this round of retroactive grants after Q2 round was cancelled. We’re still hard at work expanding support for ZEC and features (looking at expanding integration for more hardware+software wallets at the moment). Quick update: We just launched [THORSwap’s big V3 overhaul](https://medium.com/@thorswap/thorswap-v3-is-live-8041df43cfa5) update which includes our native in-app Metro wallet (with Zcash support), on/off ramps for ZEC and portfolio view to management multichain assets including ZEC. Our ZEC volume in July was ~$13M ($12,935,027) representing significant marketshare and usage amongst our users. Thank you for this opportunity and we look forward to the results! 🫡 Link to our application: [Retroactive Grant Application: THORSwap/Metro](https://forum.zcashcommunity.com/t/retroactive-grant-application-thorswap-metro/55675) ---
**Author:** ![CryptoEpoch](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/cryptoepoch/32/45606_2.png) [@CryptoEpoch](https://forum.zcashcommunity.com/u/CryptoEpoch)\ **Post date:** [August 4, 2026, 6:48pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/7 "2026-08-04T18:48:36Z")
Thanks for sharing this I really like the idea of retroactive grants because it rewards people who have already proven their contribution to the ecosystem Looking forward to seeing the Q3 submissions and the community discussion around them ---
**Author:** ![MrSane](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/mrsane/32/45598_2.png) [@MrSane](https://forum.zcashcommunity.com/u/MrSane)\ **Post date:** [August 5, 2026, 9:46pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/8 "2026-08-05T21:46:56Z")
## ZecBooks — Retroactive Grant Application (Q3 2026) **Ask:** $32,000 USD **FPF GitHub issue:** Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram #38 **Product:** zecbooks.app **Download:** zecbooks.app/download (notarized ZecBooks 0.1.1) **Source repo:** [GitHub - sane-apps/SaneBooks: Mac-native view-only Zcash books: import UFVK, classify notes, export scoped proof packs. Cannot spend. · GitHub](http://github.com/sane-apps/SaneBooks) (MIT) **Provenance:** docs/ZecBooks-0.1.1-PROVENANCE.md on that repo **SHA-256:** 25578ef64874705f2f73ca9f23193a6ddd873a33a05339b284b0af1bec243308 ### Why this exists A lot of people assume privacy coins are about hiding from taxes. That is not why I built this, and it is not why most Zcash users care about shielded money. I believe people have a right to financial privacy and still want to keep clean books. ZecBooks is the Mac layer for that: import a view-only key, classify income and change honestly, then send your accountant a locked package of the rows they need — without giving them lasting access to your wallet. **Private money, kept with honest books.** CipherPay gets you paid privately. ZBooks runs team treasury. ZecBooks is the Mac bookkeeping layer after money arrives. ### What shipped - Notarized ZecBooks 0.1.1 (Developer ID) - View-only UFVK/UIVK import; refuses seeds/spend keys - Live lightwalletd sync (ZcashLightClientKit 2.7.0-rc.4) - Classification + encrypted proof packs + Reader - Settings → About → Report Public Issue ### Verify in five minutes 1. Download ZecBooks-0.1.1.zip from zecbooks.app/download and check SHA-256 matches the provenance doc 2. Unzip → `spctl -a -vv -t exec ZecBooks.app` (expect Notarized Developer ID) 3. Read MIT LICENSE + CONTRIBUTING.md on the GitHub repo Note: brand-new forum account (trust level 0) cannot create a category topic or post raw URLs yet. Full clickable links are in FPF issue #38. Happy to answer questions here or there during review. Happy to answer questions in this thread during the review period. ---
**Author:** ![Lowo88](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/lowo88/32/37996_2.png) [@Lowo88](https://forum.zcashcommunity.com/u/Lowo88)\ **Post date:** [August 7, 2026, 6:23pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/10 "2026-08-07T18:23:37Z")
> > > \### Terms and Conditions > > \- \[x\] I agree to the \[Grant Agreement\](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_6ff6db4095fd4c4ba21babec361e927e.pdf) terms if funded > \- \[x\] I agree to \[Provide KYC information\](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_7d9e73d16b584a61bae92282b208efc4.pdf) if funded above $50,000 USD > \- \[x\] I agree to disclose conflicts of interest > \- \[x\] I understand that this grant program is only eligible for completed work, as it is a retroactive grant program. Applications for planned or partially completed work will not be considered. All completed work will be verified and accepted by its intended users or their representatives, who will confirm that the outputs meet the required quality, functionality, and usability before the work is listed as an option for Coinholder voting. > \- \[x\] I agree that for any new open-source software, I will create a CONTRIBUTING.md file that reflects the high standards of Zcash development, using the \[\`librustzcash\` style guides\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#styleguides) as a primary reference. > \- \[x\] I understand when contributing to existing Zcash code, I am required to adhere to the project specific contribution guidelines, paying close attention to any \[merge\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#merge-workflow), \[branch\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#branch-history), \[pull request\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#pull-request-review), and \[commit\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#commit-messages) guidelines as exemplified in the librustzcash repository. > \- \[x\] I understand all grants are valued in USD but will be disbursed in Shielded ZEC. I acknowledge and accept that disbursement amounts may fluctuate based on the ZEC/USD exchange rate at the time of payment. > > \### Application Owners (@octocat, @octocat1) > > @Lowo88 > > \### Organization or Individual Name > > Leonine DAO > > \### Additional Team Members > > \`\`\`team-members.yaml > \- Name: Lowo88 / LEONINE DAO > Role: Lead maintainer (NozyWallet) > Background: Orchard-first Zcash wallet engineering on Zebrad + lightwalletd > Responsibilities: CLI, desktop, shared core, releases, evidence docs > \`\`\` > > \### How did you learn about the Lockbox: Coinholder Retroactive Grants Program? > > Zcash Community Forum > > \### Requested Grant Amount (USD) > > $60,000 > > \### Category > > Wallets > > \### Project Summary > > \### NozyWallet is Zcash privacy you run yourself > > Shielded-first on your Zebrad/Zakura + lightwalletd, with local witnesses, not a hosted light wallet that sees your sync graph. > > Most wallets trade convenience for someone else’s infrastructure. Nozy is built the other way: you self-host the node stack, keep keys on your machine, and sync/send over Zebrad/Zakura + lightwalletd with local Orchard/Ironwood proofs. Privacy at full strength for people who refuse to outsource the chain CLI, Desktop, and companion API on the same core. > > \### Project Description > > \## Overview and goals > > NozyWallet (https://github.com/LEONINE-DAO/Nozy-wallet) is a shielded-first Zcash wallet stack for people and businesses who want privacy without outsourcing the chain to someone else’s node. It is a wallet + companion services not a consensus node. Users run (or point at) their own Zebrad/Zakura + lightwalletd; Orchard/Ironwood proofs use local witness derivation. > > \### Privacy = your node, not someone else’s > > The privacy hole is not “who holds the seed phrase in a slogan.” It is what you give away when you connect a wallet to other people’s nodes hosted light servers, remote WalletConnect-style backends, or any third-party sync path that sees your IP, compact-block requests, and usage pattern. Shielded on-chain still leaks if the sync and broadcast path is someone else’s. > > NozyWallet is built the other way: > > \- Default product path: self-host Zebrad/Zakura + lightwalletd (or infra you operate). > \- Local witness derivation proofs do not depend on a remote prove/sync provider seeing your wallet graph. > \- Companion API defaults to localhost (127.0.0.1); remote bind is explicit. > \- Merchants who choose privacy settle shielded on infra they run; business payment/wallet operational data stays on that stack. > \- Network privacy for sensitive flows prefers loopback and supports Tor/I2P / opt-in Nym not silent clearnet when policy says otherwise. > > \### Developers — build on nozywallet-api > > The companion HTTP API (\`nozywallet-api\`) is a first-class surface for builders. Apps can sync, read balances, send shielded ZEC, estimate ZIP-317 fees, track history/confirmations, and use Business/invoice helpers without embedding the full Desktop UI. Production integrators already run the API headlessly on VPS (Gleyo-style withdrawal / product backends and similar). Goal: “build a Zcash app” means “talk to a self-hosted Nozy companion,” not invent a new wallet stack or route users through a third-party node. > > \### Merchants — run a business on Nozy > > Desktop and API expose Business profile / invoice-oriented flows so merchants can accept shielded ZEC on their own node stack. Invoices and Business wallet tooling live in-repo on a native path not a third-party payment processor or someone else’s light wallet. Merchants who want privacy keep operational control of node + wallet/business data. > > \### Ecosystem goal — more Zcash nodes > > Nozy’s default product path assumes Zebrad/Zakura + lightwalletd. When more people adopt NozyWallet for personal use, merchant ops, or API-backed apps, more operators stand up or keep. Zcash nodes instead of concentrating sync on a few hosted light servers. Wallet growth and node growth move together. > > > > \### Technical Approach (how you did it) > > \*\*Architecture:\*\* > > \- Shared Rust core (\`nozy\`) + CLI; Desktop Tauri and api-server reuse the library. > \- api-server: Axum HTTP companion (loopback by default) exposing wallet/sync/send/fee/history and related routes for GUI and headless integrators. > \- Sync: lightwalletd compact blocks + Zebrad JSON-RPC; local witness derivation. > \- Fees: client-side ZIP-317 with Nozy mandatory priority ×4 on send surfaces. > \- Ironwood: ZIP 318–shaped migrate path; network privacy gate for broadcast. > \- Releases: CLI via GitHub Actions; desktop under desktop-v\* tags; api-server as workspace package. > > \*\*Reviewer verification:\*\* > > \- Public repo + CLI/Desktop release artifacts. > \- api-server source and docs under api-server/. > \- Mainnet TXID evidence for send + Ironwood turnstile. > > \### Time Period of Work Completion > > June 2025 – August 2026 (CLI/Desktop production path and Ironwood mainnet migration evidence; releases through v2.4.4 / desktop-v1.0.0-beta.5) > > \### Total Budget (USD) > > $60,000 > > \### Budget Breakdown > > \- Compensation: > - $(USD): 60000 > - Justification: Retroactive recognition for completed CLI + Desktop + companion API engineering (~600h blended at ~$100/hr narrative). > \- Technology/Software: > - $(USD): 0 > - Justification: Covered under compensation. > \- Infrastructure/Hosting: > - $(USD): 0 > - Justification: Operator-run Zebrad/LWD; not requesting hosted node funding. > \- Services/Contractors: > - $(USD): 0 > - Justification: No third-party audit engagement in this ask. > \- Other: > - $(USD): 0 > - Justification: N/A > \- Total $(USD): 60000 > > Split (informational): > \- CLI (\`nozy\`): $25,000 > \- Desktop (Tauri): $25,000 > \- Companion API (\`nozywallet-api\`): $10,000 > > \### Previous Funding > > No > > \### Previous Funding Details > > N/A > > \### Other Funding Sources > > No > > \### Other Funding Sources Details > > N/A > > \### Success Metrics > > \- Verifiable mainnet Orchard send + Ironwood turnstile TXIDs (published evidence docs). > \- Public CLI + Desktop releases on GitHub (v2.4.x / desktop-v\*). > \- Companion API (\`nozywallet-api\`) used in production by headless VPS integrators (Gleyo-style apps) and merchant/Business flows — not GUI-only. > \- Product path couples wallet adoption to self-hosted Zebrad + lightwalletd (more Nozy users → more Zcash nodes) instead of third-party node / WalletConnect-style sync. > \- Localhost-default companion API; privacy posture is “your node,” not “someone else’s light server.” > \- Zcash Names (ZNS) resolve shipped across CLI, Desktop Send, and companion API — recipients by name, not raw address-only. > \- Opt-in Nym network privacy shipped in Desktop (Settings → Network privacy) for sensitive broadcast/submit paths — Tor/I2P-friendly posture, not silent clearnet-only. > \- Ironwood readiness + migrate path (ZIP 318–shaped) on CLI/Desktop with mainnet turnstile confirmation. > \- ZIP-317 priority ×4 fee policy on send surfaces; fee-estimate on API. > \- Business profile + invoice flows on Desktop/API for merchants who choose shielded settle on self-hosted infra. > > \### Proof of completion > > Repository: https://github.com/LEONINE-DAO/Nozy-wallet > \- CLI releases: https://github.com/LEONINE-DAO/Nozy-wallet/releases (e.g. v2.4.4 / v2.4.5) > \- Desktop releases: desktop-v\* tags (e.g. desktop-v1.0.0-beta.5 / beta.6) > \- Companion API source: https://github.com/LEONINE-DAO/Nozy-wallet/tree/master/api-server > \- https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/api-server/scripts/companion-api-smoke-proof.png > \- API docs: https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/api-server/README.md > \- Mainnet send evidence: https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/docs/reference/MAINNET\_SEND\_READINESS\_EVIDENCE.md > - TXID: ecbd068880e9512983f9ec36a1014c84ed51065886b0bcc657415feaccd4016b > \- Ironwood migration evidence: https://github.com/LEONINE-DAO/Nozy-wallet/blob/master/docs/reference/MAINNET\_IRONWOOD\_MIGRATION\_EVIDENCE.md > - TXID: ea2fa4e64a5ca3f588dea58f38feb2a72a8d4e30292ac012d983e23bde7048fd @ 3430663 > \- Security self-review (not LA cert): https://github.com/LEONINE-DAO/Nozy-wallet/tree/master/docs/reference/security-audit > \- Prior rejected application: https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/6 > > > \Image > > \Image > > \### Conflict of Interest Disclosure > > None known beyond being the maintainers of NozyWallet. > > \### Community Forum Posting > > \- \[x\] I understand it is my responsibility to post a link to this issue on the \[Zcash Community Forums\](https://forum.zcashcommunity.com/t/about-the-retroactive-grants-category/52106) after this application has been submitted so the community can give input. I understand this is required in order for the community to discuss and vote on this grant application. Note: If you are unable to post on the forum (for example, due to new user restrictions), please leave a comment below, and we will adjust your posting permissions. ---
**Author:** ![Dadybayo](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dadybayo/32/36628_2.png) [@Dadybayo](https://forum.zcashcommunity.com/u/Dadybayo)\ **Post date:** [August 12, 2026, 12:22pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/11 "2026-08-12T12:22:09Z")
We appreciate the opportunity for proposals from the canceled Q2 round to be carried forward and considered in this round of retroactive grants. We’ve updated our Unstoppable Wallet proposal to include the additional Zcash work completed since the original submission, including the successful NU6.3 / Ironwood migration, Zcash SDK updates, server selection and other improvements. We’re especially glad that the Ironwood transition was completed successfully and that Unstoppable Wallet users were able to remain fully supported through this major Zcash network upgrade. We’ve also updated the scope and requested amount to reflect the additional completed work. Updated proposal: > [@Expanding Zcash in Unstoppable Wallet: Liquidity, Swaps & Distribution (Retroactive Grant)](https://forum.zcashcommunity.com/t/expanding-zcash-in-unstoppable-wallet-liquidity-swaps-distribution-retroactive-grant/55529/3): > > Hi folks! Since the original proposal was submitted for the Q2 round, we continued working on Zcash and completed another substantial set of improvements. As the Q2 vote was moved to Q3, we have now updated our grant application to include this additional completed work. Since the original submission, we: Migrated the Zcash integration to the official Zcash SDK stack Continued updating Zcash SDK dependencies Added the ability to select a Zcash server on Android and iOS Added Zcash … Thank you, and we’re happy to be part of the Q3 round! ---
**Author:** ![vancube](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/vancube/32/45262_2.png) [@vancube](https://forum.zcashcommunity.com/u/vancube)\ **Post date:** [August 12, 2026, 10:37pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/12 "2026-08-12T22:37:50Z")
> > > \# Retroactive Grant Application: ZecLedger > > \*Matched to the Coinholder-Directed …Retroactive Grants Program (Q3 2026) template. Fill in any remaining brackets, then copy into the GitHub issue template and mirror as a new forum thread.\* > > \--- > > \### 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 (not applicable at this request size) > \- \[x\] I agree to disclose conflicts of interest > \- \[x\] I understand this grant program is only eligible for completed work > \- \[x\] I agree to maintain a CONTRIBUTING.md reflecting the librustzcash style guides for any new open-source software > \- \[x\] I understand all grants are valued in USD but disbursed in shielded ZEC > > \### Application Owners > @vancube2 > > \### Organization or Individual Name > Zecledger > > \### Additional Team Members > None. Solo project. > > \### How did you learn about the Lockbox: Coinholder Retroactive Grants Program? > Zcash Community Forum / ZecHub > > \### Requested Grant Amount (USD) > $10,000 > > \### Category > Tools (Accounting) > > \### Project Summary > > Zcash's shielded pools hide transaction details by design, which is exactly what makes them private, and exactly what makes them impossible to audit with ordinary tools. ZecLedger solves that problem. It is a read-only accounting tool built entirely around a viewing key rather than a spending key: it can see a wallet's shielded activity but can never move a single zatoshi. From that read-only view it produces real books, balances, transaction history, cost-basis and gain/loss reports, payment reconciliation, and privacy checks, verified against a real mainnet wallet spanning 108 transactions and tested independently by a third party. It ships as an open-source Rust CLI, alongside a companion public dashboard, ZecLedger Web, that shows network-wide shielding statistics without ever touching a private key. > > \### Project Description > > \*\*The problem.\*\* Zcash's shielded pools hide transaction details by design, which is the whole point of the privacy, but it creates a real bookkeeping problem. Most crypto accounting tools assume a public, transparent ledger to read from. Shielded ZEC gives third-party tools nothing to read by default, so shielded users have had no honest way to produce a cost-basis report, reconcile payments, or audit their own activity without exposing a spend key to some outside service. > > \*\*The approach.\*\* ZecLedger takes a Unified Full Viewing Key, which can see incoming and outgoing shielded activity but cannot authorize a spend. The key never leaves the user's machine and is encrypted at rest with a user-chosen passphrase. From that read-only view it produces: > \- Balances per pool (transparent, Sapling, Orchard) > \- Full transaction history with decoded memos > \- Cost-basis and realized gain/loss reports under FIFO, LIFO, or average-cost methods, with holding period in days and an optional historical price fetch > \- Reconciliation of expected payments against what was actually received, flagging partial matches instead of silently accepting them > \- A privacy check that flags pool-usage and amount patterns that could weaken privacy > \- ZIP-321 payment request generation, so payments are requested, never sent, by the tool itself > > An optional copilot feature lets a user query their own wallet in plain language. It only ever sends aggregate totals off the local machine, and only after the user explicitly confirms what will be shared. > > \*\*Verified in production.\*\* ZecLedger's cost-basis engine has been run against a real mainnet wallet spanning 108 transactions from September 2025 through July 2026, correctly computing per-lot gain and loss under FIFO with holding periods in days. This is not a synthetic demo, it is the actual output the tool produces against a real transaction history. > > \*\*Engineering discipline.\*\* Every release ships with SHA256 checksums and public GitHub Actions build provenance, so anyone can verify a binary was built from the published source rather than trusting a download blindly. The README is explicit about where the tool's current limits are. The Ironwood network upgrade (NU6.3, activated July 28, 2026) introduced a new shielded pool and transaction format that the initial v0.1.x releases cannot yet see, and the README says so plainly rather than letting the tool silently misreport. That fix, v0.2.0, is in active development now and is expected to land within the current review window, ahead of the coinholder vote. > > \*\*ZecLedger Web\*\* is a separate, complementary public dashboard at zecledger-web.vercel.app, built to serve a different purpose than the CLI. Where the CLI is for a single wallet holder auditing their own shielded activity with a key, ZecLedger Web is for anyone who wants a public window into the network with no key of any kind. It offers three real, working views: > > \- \*\*Shield rate\*\*: a live, classified sample of recent chain activity, sorted into shielding, deshielding, fully private, transparent, and coinbase transactions, using a corrected classification method > \- \*\*Network and fees\*\*: live block height, price, market cap, node count, fees, and chain size > \- \*\*Address lookup\*\*: full public balance and history for any transparent address. Shielded addresses are deliberately declined, with an explanation shown instead of a fake or partial result, respecting the privacy that shielded addresses are built to have rather than working around it > > The app touches only public data, fetched server-side through a single data-source module, and never asks for or handles a private key or viewing key of any kind. Its own documentation is candid about its limits in the same spirit as the CLI: shield-rate figures are explicitly labeled as a floor, not a total, since fully private shielded-to-shielded transactions cannot be observed from outside the pool by any tool, a limitation stated plainly rather than glossed over. The data layer is deliberately isolated in one file specifically so a public Zaino or lightwalletd source can replace the current third-party data provider later without any change to the interface, a real piece of forward planning already built into the architecture. > > \*\*External testing.\*\* On July 24, 2026, dismad, an active ZecHub and Zcash ecosystem contributor, tested ZecLedger directly against a real mainnet wallet, running the wallet sync, the FIFO cost-basis report, and the monthly wallet-report command. The session surfaced a genuine bug: holding-period values in the cost-basis report appeared incorrect on repeated runs. That issue is acknowledged and is being fixed alongside the Ironwood work. In the same session, the wallet-report command, which produces a monthly received/sent/net summary and exports a CSV, was confirmed working correctly against real transaction data ("looks good here"). This is disclosed here in the same spirit as the tool's own README: real testing surfaces real issues, and reporting them plainly is more valuable than hiding them. > > \### Time Period of Work Completion > > Development began full time around May 18, 2026, roughly a week ahead of the official ZecHub Hackathon 3.0 kickoff on May 25, 2026, and continued full time through the hackathon submission window, which closed July 15, 2026. The CLI's first public release shipped July 16, 2026, followed by three further releases on July 18, 2026. Development has continued part time since, including the external testing session on July 24, 2026, and Ironwood support now in progress. > > \### Total Budget (USD) > $10,000 > > \### Budget Breakdown > > \- Compensation: $10,000, retroactive recognition for two shipped products. The CLI accounting engine (sync, balances, history, cost-basis under three methods, reconciliation, privacy checks, ZIP-321 requests, encrypted key storage, release engineering with checksums and build provenance), and ZecLedger Web, a separate public dashboard with its own three working views (shield rate classification, network and fee statistics, transparent address lookup), its own honest data-limitation notes, and an architecture deliberately built to swap in a public Zcash-native data source later without a UI rewrite. Justification: approximately 8 weeks of full-time solo development (May 18 to July 15, 2026, roughly 320 hours at 40 hours per week) covering the core build through hackathon submission, plus continued part-time work since (releases, documentation, external-testing follow-up, ongoing Ironwood support), estimated at roughly 40 to 60 additional hours. Against a conservative total of roughly 360 to 380 hours across both products, this ask prices the work at approximately $26 to $28 per hour, below typical market rates for systems-level Rust and cryptography development, reflecting the retroactive, already-completed nature of the request. > \- Technology/Software: $0, no paid infrastructure required for the CLI; the web dashboard runs on Vercel's free tier. > \- Infrastructure/Hosting: $0, user-run tool; no hosted service to fund. > \- Services/Contractors: $0, solo project, no contractors. > \- Other: $0 > \- Total: $10,000 > > \### Previous Funding > No > > \### Previous Funding Details > N/A > > \### Other Funding Sources > No > > \### Other Funding Sources Details > N/A > > \### Success Metrics > > \- Built for and submitted to the Accounting track of ZecHub Hackathon 3.0, a real deadline that forced a working, shippable tool rather than a slide deck > \- Four public, versioned releases (v0.1.0 through v0.1.3) in nine days, each with reproducible builds, SHA256 checksums, and cryptographic build provenance so anyone can verify what they downloaded > \- A cost-basis engine verified against 108 real mainnet transactions spanning eleven months, correctly computing FIFO gain and loss with per-lot holding periods, not a synthetic test case > \- Independently tested against a real mainnet wallet by dismad, an active ZecHub and Zcash ecosystem contributor, on July 24, 2026, exercising wallet sync, cost-basis reporting, and the monthly wallet-report command, with real feedback that surfaced and is now driving a fix to a holding-period calculation bug > \- A README that discloses the tool's current limits plainly, including the Ironwood coverage gap and its fix timeline, instead of overstating what it does > \- A live, publicly reachable companion dashboard with three working views and zero key collection of any kind, whose own documentation honestly labels its shield-rate figures as a floor rather than a total, and whose data layer is architected to swap in a public Zcash-native source later without a UI rewrite > \- Zero incidents of fund loss or key exposure, guaranteed structurally by the read-only, viewing-key-only design, not by policy alone > \- v0.2.0 Ironwood support targeted within the review period, independently checkable before the coinholder vote closes > > \### Proof of completion > > \- CLI repository: https://github.com/vancube2/zecledger > \- CLI releases with checksums and build provenance: https://github.com/vancube2/zecledger/releases > \- Web dashboard repository: https://github.com/vancube2/zecledger-web > \- Live web dashboard: https://zecledger-web.vercel.app/ > \- Demo video: https://youtu.be/7emZKHAH7TQ > \- Real cost-basis report generated from actual mainnet wallet history (108 transactions, September 2025 to July 2026), available on request or postable in the review thread > \- README, design, and security documentation: https://github.com/vancube2/zecledger/blob/master/README.md, /DESIGN.md, /SECURITY.md > > \### Conflict of Interest Disclosure > > None known beyond being the sole author and maintainer of ZecLedger and ZecLedger Web. > > \### Community Forum Posting > \- \[x\] I understand it is my responsibility to post a link to this issue on the Zcash Community Forums after this application has been submitted so the community can give input. ---
**Author:** ![craftsoldier](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/craftsoldier/32/43096_2.png) [@craftsoldier](https://forum.zcashcommunity.com/u/craftsoldier)\ **Post date:** [August 13, 2026, 10:14am UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/13 "2026-08-13T10:14:11Z")
**Grant amendment update** Greetings, fellow Zcashers! As our project grew, we built infrastructure needed to operate ZcashMe and ZcashNames and released components that can be useful outside our own applications. So we’re updating our retrospective grant to include work that fell outside the original submission and was not covered by our recent Zcash Community Grant (still uncollected). We did not increase the requested amount. Here are the additions: 1. We built seer-sync, a standalone Rust chain-sync engine for applications that need to observe Zcash activity without implementing a wallet stack. [crates.io: Rust Package Registry](https://crates.io/crates/seer-sync) 2. We built a service that watches Zcash activity for multiple configured viewing keys and writes both mempool and confirmed transactions into Postgres automatically. [GitHub - zcashme/zns-mempool · GitHub](https://github.com/zcashme/zns-mempool) 3. We built **zebra-indexer-proto** , a Rust crate containing bindings for Zebra’s indexer gRPC interface. [crates.io: Rust Package Registry](https://crates.io/crates/zebra-indexer-proto) 4. We built a “Sign in with Zcash” flow using OAuth2/OpenID Connect. [GitHub - zcashme/zns-login: Zcash-based authentication: pay to log in · GitHub](https://github.com/zcashme/zns-login) Together, this work reduces several barriers to building on Zcash. So thank you to everyone who supports ZcashMe and ZcashNames. It is an honor to contribute to the ecosystem. By the way, did you know: since the original application, our waitlist crossed **9,000 names** , and Barry Silbert and WallStreetBets both mentioned the project! Barry Silbert: > WallStreetBets: > > > Barry Silbert @BarrySilbert Special thanks to everyone who tests ZcashMe and ZcashNames, shares them, contributes code and gives us feedback along the way. We’re making privacy as normal as names. ZM ZN, Julian & Team [Retroactive Grant Application - ZcashNames · Issue #34 · Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram · GitHub](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/34)! ---
**Author:** ![Kenbak](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/kenbak/32/40417_2.png) [@Kenbak](https://forum.zcashcommunity.com/u/Kenbak)\ **Post date:** [August 13, 2026, 3:18pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/14 "2026-08-13T15:18:59Z")
Submitted a retroactive grant application for CipherScan, the Zcash block explorer and analytics platform. 🫡 > > > \### Terms and Conditions > > \- \[x\] I agree to the \[Grant Agreement\](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_6ff6db4095fd4c4ba21babec361e927e.pdf) terms if funded > \- \[x\] I agree to \[Provide KYC information\](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_7d9e73d16b584a61bae92282b208efc4.pdf) if funded above $50,000 USD > \- \[x\] I agree to disclose conflicts of interest > \- \[x\] I understand that this grant program is only eligible for completed work, as it is a retroactive grant program. Applications for planned or partially completed work will not be considered. All completed work will be verified and accepted by its intended users or their representatives, who will confirm that the outputs meet the required quality, functionality, and usability before the work is listed as an option for Coinholder voting. > \- \[x\] I agree that for any new open-source software, I will create a CONTRIBUTING.md file that reflects the high standards of Zcash development, using the \[\`librustzcash\` style guides\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#styleguides) as a primary reference. > \- \[x\] I understand when contributing to existing Zcash code, I am required to adhere to the project specific contribution guidelines, paying close attention to any \[merge\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#merge-workflow), \[branch\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#branch-history), \[pull request\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#pull-request-review), and \[commit\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#commit-messages) guidelines as exemplified in the librustzcash repository. > \- \[x\] I understand all grants are valued in USD but will be disbursed in Shielded ZEC. I acknowledge and accept that disbursement amounts may fluctuate based on the ZEC/USD exchange rate at the time of payment. > > \### Application Owners (@octocat, @octocat1) > > @Kenbak > > \### Organization or Individual Name > > Kenbak > > \### Additional Team Members > > \`\`\`team-members.yaml > None > \`\`\` > > \### How did you learn about the Lockbox: Coinholder Retroactive Grants Program? > > Through active participation in the Zcash Community Forum and discussions with other Zcash ecosystem contributors. > > \### Requested Grant Amount (USD) > > $125,000 > > \### Category > > Infrastructure > > \### Project Summary > > CipherScan is a production Zcash block explorer and privacy-intelligence platform at \[cipherscan.app\](https://cipherscan.app/). This application covers completed, previously unfunded work that expanded CipherScan beyond its existing ZCG deliverables: a custom Rust chain indexer, privacy-linkage analysis, wallet-fingerprint research, mining intelligence, an automated public data bot, and analytics tools serving the broader Zcash ecosystem. > > CipherScan provides a public mainnet and testnet explorer, a documented REST API, a public Lightwalletd endpoint. The work claimed here is live, public, and independently verifiable. > > > \### Project Description > > Zcash users need more than pages displaying blocks and hashes. Shielded transactions hide their contents, but users can still weaken privacy through distinctive amounts, unusual fees, timing patterns, or wallet-specific construction. Miners, researchers, wallets, and market-data providers also need reliable public network data. > > CipherScan makes that information accessible without accounts, analytics trackers, server-side viewing keys, or wallet scans. Its privacy tools analyze public aggregate chain data and explicitly state their limitations. > > This application covers five completed work packages that were not ZCG milestones. > > \### 1. Privacy intelligence and wallet anonymity > > CipherScan now precomputes potential shield-to-deshield linkage rather than running expensive correlations when a page loads. The pipeline provides: > > \- Linkage edges scored by amount, timing, conservation, and ambiguity. > \- Batch clusters for one-to-many and many-to-one behavior. > \- Transaction graphs explaining possible public relationships without asserting identity. > \- Risk tiers and plain-language explanations. > \- Blend Check amount-commonality scoring and privacy-improving split suggestions. > \- ZIP-317 fee-lane distributions. > \- Wallet-pattern analysis using fees, expiry height, nLockTime, and action padding. > > The public pages are \[Privacy Risks\](https://cipherscan.app/privacy-risks), \[Blend Check\](https://cipherscan.app/tools/blend-check), and \[Wallet Anonymity Analysis\](https://cipherscan.app/privacy/wallets). > > These tools do not decrypt transactions, identify shielded senders, or prove which wallet created a transaction. Fingerprint matches are estimates. > > \### 2. Mining and network intelligence > > CipherScan shipped a dedicated \[Mining Analytics\](https://cipherscan.app/mining) product: > > \- Mining-pool distribution and ranking. > \- Historical hashrate share. > \- Reward and fee aggregation. > \- Miner hold-versus-move behavior based on subsequent coinbase-output spends. > \- Daily snapshots for efficient historical queries. > \- Per-pool ZODL destination analysis: shielded, exchange, and other. > \- Network metrics and expanded pool attribution. > > This makes mining centralization and miner behavior visible through public, reproducible queries. > > \### 3. Public explorer and analytics expansion > > Completed public features outside the funded milestones include: > > \- \*\*Pool Analytics:\*\* dedicated \[/pools\](https://cipherscan.app/pools) page with per-pool (Sprout/Sapling/Orchard/Ironwood) supply breakdown, daily shield/deshield flow volume charts, and UTXO-level turnstile tracking showing whether deshielded ZEC stayed at transparent addresses or was moved. > \- \*\*Rich List:\*\* transparent-holder concentration and supply breakdown, including P2PK/bare-multisig address resolution for early mining outputs. Clearly excludes private shielded holdings. > \- \*\*Usage Clock:\*\* aggregate hourly activity combined with network-node geography. > \- \*\*Charts hub:\*\* searchable privacy, pool, mining, network, and fee charts. > \- \*\*Fully shielded transaction browser:\*\* filtering, statistics, and trends without exposing amounts. > \- \*\*Raw transaction data and USD equivalence:\*\* verbose node data tab on transaction pages, historical ZEC/USD price integration for fee and value context, P2PKH/P2SH script-type breakdown, and commitment tree/nullifier set growth charts. > \- \*\*Migration wallet fingerprints:\*\* implementation-family detection for Ironwood migrations (Vizor/ZIP-318 SDK, Cake/zkool2-compatible, partial compliance patterns) using fee, action structure, anchor alignment, and denomination signals. Public on the Ironwood analytics page. > \- \*\*Granular wallet anonymity breakdown:\*\* decomposition of the "librustzcash family" into actionable sub-categories (ZODL/Vizor Ironwood sends, ZIP-318 migration batches, cross-pool transfers, Orchard-only, shielding/deshielding) plus new wallet attributions (Cake Wallet, Nozy). Reduced "Unknown" from ~40% to ~21% of shielded transactions. > \- \*\*Real-time data delivery:\*\* ISR with on-demand cache invalidation triggered by the indexer on new blocks, combined with WebSocket instant client-side updates. CDN speed with zero staleness. > \- \*\*SEO and accessibility foundation:\*\* server-rendered content, canonical lifecycle rules, structured data, sitemaps, crawl controls, semantic design tokens, reusable tables, and shared accessible components. > \- \*\*Valuation and on-chain metrics page:\*\* \[/valuation\](https://cipherscan.app/valuation) with daily MVRV ratio, SOPR, NUPL, realized price vs market price, and shielded pool realized capitalization charts. Powered by a custom UTXO-tracking pipeline that computes realized value from transparent spend events. > \- \*\*HODL Waves and Coin-Days-Destroyed:\*\* daily UTXO age-bucket computation across 27M+ UTXOs producing HODL wave charts (1d–10y buckets) and a CDD dormancy indicator. Displayed on the valuation page. > \- \*\*Network Pulse anomaly detection:\*\* a 12-metric statistical engine computing rolling 90-day z-scores daily for transaction counts, shielded adoption, shield/deshield volume, cross-chain flows, fees, exchange deposits, MVRV, migration volume, and miner sell pressure. Events at |z| ≥ 2.5 are stored and surfaced on a dedicated \[/pulse\](https://cipherscan.app/pulse) page with severity tiers, metric filters, and pagination. A floating homepage widget animates based on live anomaly state. > \- \*\*NU7 Vote Hub:\*\* \[/governance/nu7\](https://cipherscan.app/governance/nu7) page for the upcoming network upgrade coinholder vote (Aug 25 – Sep 12, 2026), displaying poll questions, voting timeline, key dates, and a chain-data explorer tab for vote-related on-chain activity. > > These features are deployed on the public explorer. > > \### 4. Chain indexer infrastructure > > A from-scratch Rust chain indexer (\[cipherscan-rust\](https://github.com/Kenbak/cipherscan-rust)) replaced the original Node.js indexer, improving throughput from ~7 tx/s to 1,000+ tx/s. This is the data foundation that makes everything else possible, privacy analysis, mining stats, valuation metrics, and real-time alerts all depend on having the full chain indexed quickly and reliably. The indexer reads directly from Zebra's state, handles full-chain rebuilds in hours rather than weeks, and includes automated health monitoring with alerting. > > \### 5. CipherScan Data Bot — automated Zcash intelligence feed > > A dedicated X (Twitter) bot publishing factual, deterministic chain data from CipherScan's indexer without manual intervention: > > \- Real-time alerts for large confirmed shield/deshield flows (\>10K ZEC, top percentile of 90-day rolling window), cross-chain whale swaps (\>$5K), Ironwood pool milestones (ZEC volume and USD value thresholds), large Orchard-to-Ironwood migrations, and Network Pulse anomaly events (|z| ≥ 3.0). > \- Daily digest summarizing shielded supply, pool movements, Ironwood migration progress, ZIP-318 compliance, and cross-chain inflows/outflows. > \- Custom branded image cards generated server-side using node-canvas, following CipherScan's design system (dark glass panels, branded colors, chain logos). Separate card layouts for daily digest, milestone, cross-chain, flow alert, and pulse alert tweet types. > \- X API v2 OAuth2 integration with media upload, token refresh, and dedup-key outbox to prevent duplicate posts. > \- Deployed as a standalone systemd service with restricted privileges. > > The bot is live at \[@cipherscan\_data\](https://x.com/cipherscan\_data) and its source is in the public CipherScan repository under \`server/bot/\`. > > \### Scope intentionally excluded > > This application does not request payment for any ZCG-funded deliverables (M1–M4 and M3.5), Crosslink explorer work, Ironwood activation, corrective indexer maintenance, or unannounced integrations. > > > \### Technical Approach (how you did it) > > CipherScan's production architecture uses two public-source repositories: > > \- \[Kenbak/cipherscan\](https://github.com/Kenbak/cipherscan): Next.js/React, Express, PostgreSQL, Redis, and scheduled analytics jobs. > \- \[Kenbak/cipherscan-rust\](https://github.com/Kenbak/cipherscan-rust): Rust, Zebra chain types, RocksDB, JSON-RPC/gRPC, SQLx, and PostgreSQL. > > The work claimed by this application spans both repositories. The explorer/API repository contains the analytics, privacy tools, and public pages. The Rust indexer provides the chain data layer that makes them possible. > > Privacy jobs precompute linkage edges and batch clusters from public shield/deshield records. APIs read these records with bounded filters and pagination. These tools require no viewing keys and create no user profiles. > > Mining endpoints aggregate blocks by known payout addresses and group multiple addresses under a pool identity. A daily job snapshots whether coinbase outputs remain held or have moved. > > The public API uses parameterized SQL, bounded pagination, and short-lived caching. The Rust indexer supplies normalized chain data, while the claimed analytics are computed in the API and background-job layer. > > > \### Time Period of Work Completion > > November 2025 – August 2026 > > \### Total Budget (USD) > > $125,000 > > \### Budget Breakdown > > > \- Compensation: > - $(USD): $125,000 > - Justification: Fixed retrospective valuation of four completed work packages: chain indexer infrastructure, privacy intelligence, mining and network intelligence, and public explorer/analytics expansion. > \- Technology/Software: > - $(USD): 0 > - Justification: No separate technology expense requested. > \- Infrastructure/Hosting: > - $(USD): 0 > - Justification: Hosting expenses covered by ZCG and M3.5 are excluded. > \- Services/Contractors: > - $(USD): 0 > - Justification: No contractors included. > \- Other: > - $(USD): 0 > - Justification: No domains, marketing, or future expenses included. > \- Total $(USD): $125,000 > > \### Previous Funding > > No > > \### Previous Funding Details > > \_No response\_ > > \### Other Funding Sources > > Yes > > \### Other Funding Sources Details > > The original CipherScan ZCG grant approved $58,800 across four $14,700 tranches. A $14,700 M3.5 amendment raised the approved commitment to $73,500. > > > \### Success Metrics > > A block explorer is the heartbeat monitor of a blockchain network. It is the tool developers reach for when debugging, the reference journalists cite when reporting, the dashboard researchers consult when analyzing, and the first page a newcomer visits to understand whether the chain is alive and healthy. For a privacy network like Zcash, the explorer carries additional responsibility: it must communicate shielded activity without compromising it. > > CipherScan is shaped by its users. Developers from ZODL, Shielded Labs, Valar Group and other teams, regularly provide feedback and feature suggestions that inform development priorities from the Ironwood migration tiers to wallet fingerprint categories. Protocol researchers use its data to inform specification changes. This is a tool that improves continuously through the input of the people who rely on it. CipherScan is also listed as an official Zcash explorer on \[CoinGecko\](https://www.coingecko.com/en/coins/zcash), serving as a reference point for the broader crypto community. > > CipherScan has proven this value under pressure: > > \- \*\*NU6.2 incident (June 2026):\*\* When the Orchard soundness bug forced an emergency network upgrade, CipherScan was the first explorer back online and providing real-time fork monitoring throughout the event. Developers, wallet teams, and protocol engineers used CipherScan to verify the chain had stabilized and to track reorg depth in real time. > \- \*\*Ironwood activation and migration tracking (July–August 2026):\*\* The largest pool migration in Zcash history is ongoing. CipherScan's Ironwood Migration Tracker is the most comprehensive public tool for monitoring migration progress, combining pool balances, migration velocity, wallet compliance scoring, cohort analysis, denomination privacy, and tier breakdowns in a single dashboard. This depth lets wallet developers, protocol engineers, and the community follow the migration in real time with actionable granularity. > \- \*\*Direct protocol contribution\*\* — ZIP-318 parameter update: CipherScan's migration data was used by protocol developers to inform changes to the ZIP-318 pool migration specification. The observed migration rates and timing analysis provided the empirical basis for \[ZIP-318 PR #1343\](https://github.com/zcash/zips/pull/1343), which shortened preparation delay (mean 24→16 blocks), halved migration latency (mean 144→66 blocks), and reduced the anchor age cap (16→4 boundaries). CipherScan is acknowledged in the PR for gathering the migration data that informed these changes. > \- \*\*Automated public data presence:\*\* The \[@cipherscan\_data\](https://x.com/cipherscan\_data) bot publishes deterministic on-chain facts to Twitter daily, shielded pool milestones, whale movements, cross-chain flows, anomaly events. This gives Zcash a visible, credible data presence on social media that does not depend on any individual posting manually. > \- \*\*Developer and researcher infrastructure:\*\* CipherScan's public API, Lightwalletd endpoint, testnet explorer, and real-time WebSocket feed are used by wallet developers (for testing), and by community researchers analyzing network behavior. This is not a vanity dashboard, it is infrastructure. > > The value of a reliable explorer is most visible when things go wrong. CipherScan passed that test during the hardest months Zcash has faced, and continues to serve the network around the clock without interruption. > > \### Platform scale (August 2026) > > \- 1,100+ commits across two public repositories (explorer/API + Rust indexer). > \- 50+ public page routes, 113 API endpoints, 14 indexer subcommands. > \- Live mainnet, testnet, and Crosslink explorers with real-time WebSocket updates. > \- Public REST API, public Lightwalletd endpoint, and Tor hidden services. > > > > \### Community reach > > \- \[@cipherscan\_app\](https://x.com/cipherscan\_app): 647 followers, 421K impressions, 7.4K engagements, 4.7K likes over 10 months. Verified account. > \- \[@cipherscan\_data\](https://x.com/cipherscan\_data): automated bot publishing daily chain data, milestone alerts, and anomaly events. > \- 20 Privacy Index newsletter issues published. > \- Migration data cited in \[ZIP-318 PR #1343\](https://github.com/zcash/zips/pull/1343) for protocol parameter changes. > > > > \### Live data served > > \- 3.4M+ blocks indexed, real-time to chain tip. > \- 274K+ ZEC tracked in the Ironwood pool with live migration analytics. > \- 12-metric anomaly detection engine running daily z-score analysis. > \- On-chain valuation suite (MVRV, SOPR, NUPL, realized price) computed from 27M+ UTXOs. > > > > \### Proof of completion > > \### Repositories > > \- \[CipherScan explorer/API\](https://github.com/Kenbak/cipherscan) > \- \[CipherScan Rust indexer\](https://github.com/Kenbak/cipherscan-rust) > > > > \### Key commits > > \- \[Privacy linkage pipeline (\](https://github.com/Kenbak/cipherscan/commit/1d4103b)\`1d4103b\`\[)\](https://github.com/Kenbak/cipherscan/commit/1d4103b) > \- \[Wallet anonymity analysis (\](https://github.com/Kenbak/cipherscan/commit/a9fa19d)\`a9fa19d\`\[)\](https://github.com/Kenbak/cipherscan/commit/a9fa19d) > \- \[Mining analytics (\](https://github.com/Kenbak/cipherscan/commit/ebe9e38)\`ebe9e38\`\[)\](https://github.com/Kenbak/cipherscan/commit/ebe9e38) > \- \[ZODL mining endpoint (\](https://github.com/Kenbak/cipherscan/commit/69b833e)\`69b833e\`\[)\](https://github.com/Kenbak/cipherscan/commit/69b833e) > \- \[Rich List (\](https://github.com/Kenbak/cipherscan/commit/af836b7)\`af836b7\`\[)\](https://github.com/Kenbak/cipherscan/commit/af836b7) > \- \[Usage Clock (\](https://github.com/Kenbak/cipherscan/commit/78b3e62)\`78b3e62\`\[)\](https://github.com/Kenbak/cipherscan/commit/78b3e62) > \- \[Charts hub (\](https://github.com/Kenbak/cipherscan/commit/1de6c6d)\`1de6c6d\`\[)\](https://github.com/Kenbak/cipherscan/commit/1de6c6d) > \- \[Fully shielded browser (\](https://github.com/Kenbak/cipherscan/commit/cba62a2)\`cba62a2\`\[)\](https://github.com/Kenbak/cipherscan/commit/cba62a2) > \- \[SEO foundation (\](https://github.com/Kenbak/cipherscan/commit/3d025ba)\`3d025ba\`\[)\](https://github.com/Kenbak/cipherscan/commit/3d025ba) > > > > \### Live deployments > > \- \[Mainnet explorer\](https://cipherscan.app) > \- \[Testnet explorer\](https://testnet.cipherscan.app) > \- \[Privacy Risks\](https://cipherscan.app/privacy-risks) > \- \[Wallet Anonymity Analysis\](https://cipherscan.app/privacy/wallets) > \- \[Mining Analytics\](https://cipherscan.app/mining) > \- \[Pool Analytics\](https://cipherscan.app/pools) > \- \[Ironwood Migration Analytics\](https://cipherscan.app/ironwood) > \- \[Rich List\](https://cipherscan.app/rich-list) > \- \[Usage Clock\](https://cipherscan.app/usage-clock) > \- \[Charts\](https://cipherscan.app/charts) > \- \[Valuation (MVRV, SOPR, NUPL, Realized Price)\](https://cipherscan.app/valuation) > \- \[Network Pulse\](https://cipherscan.app/pulse) > \- \[NU7 Vote Hub\](https://cipherscan.app/governance/nu7) > \- \[CipherScan Data Bot\](https://x.com/cipherscan\_data) — live automated X feed > > > > > \### Conflict of Interest Disclosure > > I am the founder and lead developer of CipherScan and would directly receive this grant. I hold separately scoped ZCG grants for CipherScan and the Open Wallet Standard Zcash fork; the CipherScan payment ledger and excluded deliverables are disclosed above. I also own CipherPay, whose separate $35,000 retroactive application is pending in this round, its six repositories and grant scope entirely separate. > > I am not employed by the Zcash Foundation, Shielded Labs, ZODL, or a wallet vendor, and I hold no keyholder role in the Coinholder or ZCG multisig programs. > > > \### Community Forum Posting > > \- \[x\] I understand it is my responsibility to post a link to this issue on the \[Zcash Community Forums\](https://forum.zcashcommunity.com/t/about-the-retroactive-grants-category/52106) after this application has been submitted so the community can give input. I understand this is required in order for the community to discuss and vote on this grant application. Note: If you are unable to post on the forum (for example, due to new user restrictions), please leave a comment below, and we will adjust your posting permissions. > [@Retroactive Grant Application - CipherScan](https://forum.zcashcommunity.com/t/retroactive-grant-application-cipherscan/56997): > > Github Application: [CipherScan Grant](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/47) Live: [https://cipherscan.app](https://cipherscan.app/) Repositories: [CipherScan Explorer/API](https://github.com/Kenbak/cipherscan) | [Rust Indexer](https://github.com/Kenbak/cipherscan-rust) A block explorer is the heartbeat monitor of a blockchain. Developers reach for it when debugging, journalists cite it when reporting, researchers consult it when analyzing, and newcomers visit it to check whether the chain is alive. CipherScan is that tool. It’s shaped by its users, developers from ZODL, Shielded Labs, and Valar Group give direct feedback that turns into fea… ---
**Author:** ![Giri-Aayush](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/giri-aayush/32/46477_2.png) [@Giri-Aayush](https://forum.zcashcommunity.com/u/Giri-Aayush)\ **Post date:** [August 13, 2026, 7:41pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/15 "2026-08-13T19:41:30Z")
Just submitted an application for the self-sovereign Zcash testnet faucet. Full write-up here: [Retroactive Grant Application: Self-sovereign Zcash Testnet Faucet](https://forum.zcashcommunity.com/t/retroactive-grant-application-self-sovereign-zcash-testnet-faucet/57002) Short version: it runs its own Zebra node, Zallet wallet, embedded Zaino indexer, and miner, and hands out shielded z-to-z TAZ so the payouts stay private. Live at [https://zcashfaucet.jinolabs.xyz](https://zcashfaucet.jinolabs.xyz). Running the real stack also turned up two Crosslink node bugs I fixed and reported upstream. Happy to take questions in the thread. ---
**Author:** ![dismad](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dismad/32/18432_2.png) [@dismad](https://forum.zcashcommunity.com/u/dismad)\ **Post date:** [August 13, 2026, 9:06pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/16 "2026-08-13T21:06:46Z")
Just want to comment and say its awesome so many new builders are using this resource! Good luck to everyone 😍 🛡 🦓 ♥ Open question to coinholders, ## How much time will you invest in research and testing for all these wonderful builders? This is not a trival problem!!! ---
**Author:** ![FPF](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/fpf/32/30829_2.png) [@FPF](https://forum.zcashcommunity.com/u/FPF)\ **Post date:** [August 13, 2026, 9:19pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/17 "2026-08-13T21:19:49Z")
FWIW, FPF will provide a summary post tomorrow once the deadline passes to help support the review process. Regardless, given the volume and technical breadth of the submissions a thorough review will be challenging! ---
**Author:** ![coinwallet](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/coinwallet/32/47900_2.png) [@coinwallet](https://forum.zcashcommunity.com/u/coinwallet)\ **Post date:** [August 14, 2026, 12:01pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/18 "2026-08-14T12:01:25Z")
Hello, I’m writing from the Coin Wallet team. Our wallet has been around for 11 years, and we plan to add Zcash support in the coming months. We only learned about the grants last week. I have a short question: Would it still be possible to submit an application today with a description of the planned work? We already support 23 blockchains, including Monero, so this is mainly a matter of time - we have relevant experience. Our wallet is fully functional across platforms: we cover mobile apps, desktop, web app, and Tor .onion. > **[GitHub - CoinSpace/CoinSpace: Coin Wallet is a self-custodial crypto wallet for...](https://github.com/CoinSpace/CoinSpace)** > > Coin Wallet is a self-custodial crypto wallet for Bitcoin, Bitcoin Cash, Ethereum, Litecoin, XRP, Stellar, Dogecoin, Dash, Monero, Binance Smart Chain, Cardano, Ethereum Classic, Solana, Avalanche, TRON, Polygon, Arbitrum, Toncoin, and Sui. ---
**Author:** ![FPF](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/fpf/32/30829_2.png) [@FPF](https://forum.zcashcommunity.com/u/FPF)\ **Post date:** [August 14, 2026, 12:02pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/19 "2026-08-14T12:02:29Z")
This program is only for completed grants. For future work you can consider applying for a [ZCG grant](https://zcashcommunitygrants.org/). ---
**Author:** ![aquietinvestor](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/aquietinvestor/32/34528_2.png) [@aquietinvestor](https://forum.zcashcommunity.com/u/aquietinvestor)\ **Post date:** [August 14, 2026, 1:44pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/20 "2026-08-14T13:44:00Z")
> [@Project Tachyon - Bonus Grant for Ironwood zk-SNARK Formal Verification](https://forum.zcashcommunity.com/t/project-tachyon-bonus-grant-for-ironwood-zk-snark-formal-verification/57021): > > I’ve submitted a bonus grant nomination for the formal verification work done by the [Tachyon Foundation](https://forum.zcashcommunity.com/t/retroactive-grant-application-ironwood-zk-snark-formal-verification-project-tachyon/57007). It was inspired by [Zooko’s post](https://forum.zcashcommunity.com/t/retroactive-grant-application-give-bigger-grants-to-taylor-and-tachyon/57012) suggesting we should be able to nominate people for retroactive grants instead of waiting for them to apply, and that they asked for too little. @frankbraun also reached out to me separately to advocate for a bonus grant for both applicants, having come to the same conclusion on his own. I agree. Tachyon’s application prices their emergency work at the bottom … ---
**Author:** ![aquietinvestor](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/aquietinvestor/32/34528_2.png) [@aquietinvestor](https://forum.zcashcommunity.com/u/aquietinvestor)\ **Post date:** [August 14, 2026, 2:25pm UTC](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/21 "2026-08-14T14:25:19Z")
> [@Taylor Hornby - Bonus Grant for Orchard Counterfeiting Vulnerability Bug Bounty](https://forum.zcashcommunity.com/t/taylor-hornby-bonus-grant-for-orchard-counterfeiting-vulnerability-bug-bounty/57025): > > I’ve submitted a bonus grant nomination for [Taylor Hornby](https://forum.zcashcommunity.com/t/retroactive-grant-application-orchard-counterfeiting-vulnerability-bug-bounty/57008). It was inspired by [Zooko’s post](https://forum.zcashcommunity.com/t/retroactive-grant-application-give-bigger-grants-to-taylor-and-tachyon/57012) suggesting we should be able to nominate people for retroactive grants instead of waiting for them to apply, and that he asked for too little. @frankbraun also reached out to me separately to advocate for a bonus grant for both applicants, having come to the same conclusion on his own. I agree. Taylor’s requested bounty for disclosing the Orchard vulnerability works out to 0.033% of the funds at risk, a f… [Next page](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885.md?page=2)