# Coinholder-Directed Retroactive Grants Program Q2 2026 - Now Accepting Proposals **URL:** \ **Category:** Retroactive Grants\ **Created:** [April 13, 2026, 11:47am UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328 "2026-04-13T11:47:23Z")\ **Posts on this page:** 9\ **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:** [April 13, 2026, 11:47am UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/1 "2026-04-13T11:47:23Z")
The Coinholder-Directed Retroactive Grants Program is now accepting proposals for the Q2 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 June. **Deadline to submit a proposal:** May 14 at 20:00 UTC After the submission deadline, there will be a mandatory 30-day review period from Monday, May 18 to Wednesday, June 17. The coinholder poll will then run from Thursday, June 18 through Tuesday, June 30. 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 have any questions about the process or your submission, please post them in this thread. Thank you! ---
**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:** [April 13, 2026, 11:47am UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/2 "2026-04-13T11:47:38Z")
Pinned globally on April 13, 2026, 11:47am UTC ---
**Author:** ![dev\_tochi](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/dev_tochi/32/43790_2.png) [@dev\_tochi](https://forum.zcashcommunity.com/u/dev_tochi)\ **Post date:** [April 16, 2026, 3:37pm UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/4 "2026-04-16T15:37:03Z")
How about projects that are in Beta and codebase is not public yet, would those be considered in anyway? ---
**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:** [April 16, 2026, 4:05pm UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/5 "2026-04-16T16:05:04Z")
This program provides retroactive funding exclusively for completed projects. To qualify for a grant, your work must be verifiable; if coinholders cannot confirm your project’s completion and impact, your proposal will not be funded. When submitting your retroactive request via GitHub, you must agree to the following: > I understand that this program is only for **fully completed work**. Applications for planned or partially finished projects will not be considered. All work must be verified by its intended users or their representatives to ensure it meets quality, functionality, and usability standards before it is eligible for a coinholder vote. ### Which Program is Right for You? - **For completed work:** Wait until your project is live and public before applying for this funding program. - **For future or ongoing work:** Please contact **ZCG** (Zcash Community Grants) [\* to apply](https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/new/choose) for proactive funding. ---
**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:** [April 16, 2026, 8:25pm UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/6 "2026-04-16T20:25:00Z")
Grant requests to be included in the Q2 2026 vote (will be updated as new proposals are received and pass review for eligibility): - 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) - Expandng 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-2026-core-protocol-development/55700), [\* GitHub Submission](https://github.com/Financial-Privacy-Foundation/ZcashCoinholderGrantsProgram/issues/33) ---
**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:** [May 13, 2026, 12:55pm UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/8 "2026-05-13T12:55:45Z")
Reminder: The deadline to submit proposals for the CDRGP Q2 round is tomorrow, May 14th, at 20:00 UTC. There are currently six proposals for consideration. ---
**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:** [May 14, 2026, 7:59pm UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/9 "2026-05-14T19:59:19Z")
Greetings from the ZcashNames Team! > > > \### 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) > > @craftsoldier @ZcashUsersGroup > > \### Organization or Individual Name > > ZcashMe, Inc. > > \### Additional Team Members > > \`\`\`team-members.yaml > \- Name: Zechariah — Founder / product lead. Founder of ZECpages; responsible for product direction, protocol requirements, partnerships, and launch/community coordination. (zcash.me/zechariah) > \- Name: craftsoldier — Engineer. Responsible for app architecture, wallet flows, explorer, referral systems, docs integration, and release execution. (zcash.me/julian\_abraham) > \`\`\` > > \### How did you learn about the Lockbox: Coinholder Retroactive Grants Program? > > Word-of-mouth (previous applicant, Q1 2026 round) > > \### Requested Grant Amount (USD) > > $122,400 > > \### Category > > Non-Wallet Applications > > \### Project Summary > > ZcashMe made Zcash easier to use by letting people create a public profile page and share a simple link instead of a long address. People who received the link could pay quickly from QR or wallet URI, while profile owners could manage their display name, bio, nearest city, avatar, and social media links. ZcashMe also introduced memo + OTP verification to confirm address ownership before profile edits and social authentication. > > That usability win came with an important trust limitation: ZcashMe resolves payment destinations through a centrally managed database. Even with honest operators and verification controls, a privileged admin or compromised backend could alter a stored address mapping, creating a man-in-the-middle risk where funds could be redirected or payment relationships surveilled. ZcashNames is the completed next step that removes this trust bottleneck by moving name-to-address resolution on-chain. > > ZcashNames is an on-chain naming system for Zcash that maps human-readable names like alice.zcash to shielded addresses. The completed work delivered a live beta web app, public explorer, open documentation, integration guides, and supporting developer infrastructure that makes ZNS usable and testable by end users, wallet teams, and app builders. > > \### Project Description > > ZcashMe proved there is strong demand for human-readable payments, public recipient discovery, and lightweight identity around shielded addresses. It helped users share a memorable payment destination, build a public profile, and receive funds more easily than copying raw addresses in chat. In practice, it served as an onboarding and usability layer for Zcash. > > However, ZcashMe also exposed a structural limitation of centralized name resolution. Because the username-to-address mapping lives in a server-controlled database, users and integrators must trust the operator not only to stay online, but also to preserve the correctness of the mapping at all times. A malicious or compromised administrator could substitute a different address, intercept funds, or observe and influence payment flows. This is not a flaw in Zcash itself; it is the trust model imposed by an off-chain directory. > > ZcashNames is the solution to that problem. Instead of relying on a mutable central database, ZcashNames anchors human-readable name resolution on-chain, so wallets and applications can verify name-to-address mappings directly from Zcash state. ZcashMe demonstrated the product need, and ZcashNames completes the architecture needed to satisfy that need without introducing a centralized interception point. > > The transition path is straightforward and practical. ZcashMe can evolve from being the source of truth for payment destinations into a discovery, profile, and social UX layer that sits on top of ZcashNames. Public profiles, avatars, bios, verified links, and discovery features can remain useful, but the canonical payment destination should become the user's \`.zcash\` name and its on-chain mapping. This preserves the usability benefits of ZcashMe while eliminating its most important trust assumption. > > ZcashNames includes a production website, claim/manage/list/buy/release flows for names, OTP- and keypair-based authorization paths, a live explorer and marketplace view, a public roadmap, waitlist and referral onboarding, beta application flows, a share kit for community distribution, and a docs portal that explains usage, protocol rules, wallet integration, RPC methods, and SDK usage. Taken together, this lowers the barrier to Zcash adoption by making shielded addresses easier to use while preserving the verification and privacy properties of the underlying chain. > > \### Technical Approach (how you did it) > > \[Zcash.me\](http://zcash.me/) is a Next.js web application with a Postgres SQL database. It features a stand-alone background verification service to decrypt incoming requests and generate OTP responses. Social OAuth is integrated via Supabase. 1Click swap APIs are used for cross-chain execution. External market pricing provided by CoinGecko, Coinbase. > > ZcashNames uses a Next.js 15 / React 19 / TypeScript web app and docs site, aligned to zcashname-sdk and the canonical ZNS OpenRPC spec. State-changing actions are encoded as signed ZNS: memos inside standard Orchard shielded transactions and delivered through ZIP-321 wallet flows. Reads come from the Rust ZNS indexer over JSON-RPC; address ownership proofs use the separate ZVS OTP flow; the explorer is SDK-first and server-rendered; and the docs are published from MDX/Nextra in the same repo so protocol, integration, and user-facing guidance stay synchronized. The completed work covers Alpha v1 (2026-03-09 to 2026-04-19), Alpha v2 (2026-04-20 to 2026-05-08), and the associated public onboarding / referral / beta-prep surfaces completed by 2026-05-14. > > \### Time Period of Work Completion > > Q2 2020, Q3 2025, October 2025 - February 2026 > > \### Total Budget (USD) > > $122,400 > > \### Budget Breakdown > > \### Budget Breakdown: ZcashMe > > \- Compensation: > - $(USD): 48000 > - Justification: core engineering across frontend and backend, including static-to-SSR migration, TypeScript refactor, modular architecture, verification pipeline rewrite, wallet APIs, swap/status systems, NS apps (directory, point-of-sale, guestbook) and leaderboard. > \- Technology: > - $(USD): 4200 > - Justification: backend compute/storage/network and productivity apps > \- Services/Contractors: > - $(USD): 9000 > - Justification: development and marketing support contracts > \- Total $(USD): 61,200 > > \### Budget Breakdown: ZcashNames > \- Compensation: $48,000 - core engineering across frontend and backend, including static-to-SSR migration, TypeScript refactor, modular architecture, verification pipeline rewrite, wallet APIs, swap/status systems, NS apps (directory, point-of-sale, guestbook), and leaderboard. > \- Technology/Software: $4,200 - backend compute, storage, network, development tooling, software subscriptions, and productivity apps. > \- Infrastructure/Hosting: $0 - included in the Technology/Software line above. > \- Services/Contractors: $9,000 - development and marketing support contracts. > \- Other: $0 - no additional costs claimed outside the categories above. > \- Total (USD): $61,200 > > \### Previous Funding > > Yes > > \### Previous Funding Details > > \<$25,000 > > \### Other Funding Sources > > No > > \### Other Funding Sources Details > > Angel investor > > \### Success Metrics > > \- 1700+ members on Zcash.me > \- Internal project materials also recorded 300+ waitlist signups within the first few days after the April 1, 2026 waitlist launch. Currently 1100+. > \- Beta v1: 45 applicants, 39 invites sent, 24 activated testers, 47 feedback reports from 12 unique testers. > \- Beta v2: 65 applicants as of May 14, 2026; invitations and participation had not yet started. > \- The repo currently ships 39 public documentation pages across introduction, usage, integration, protocol, indexer/RPC, SDK, terminology, ecosystem, and FAQ sections. > \- The public docs and ecosystem pages document 8 first-party SDK language ports and a canonical OpenRPC surface for direct integrations. > \- The completed alpha work shipped end-user flows for claim, update, list, delist, buy, and release, plus supporting verification and explorer surfaces. Public deployments are live for the main site, docs, explorer, roadmap, beta application flow, share kit, and referral leaderboard. The project created concrete integration surface area for wallet and app teams, including wallet-resolution guidance, RPC reference, testing guidance, and public endpoints on testnet and mainnet beta. > > \### Proof of completion > > \- ZcashMe: https://zcash.me > \- Repository/Commit: https://github.com/zcashme/zcashnames ; https://github.com/zcashme/ZNS ; https://github.com/zcashme/ZNS/blob/master/openrpc.json > \- Publication: https://www.zcashnames.com/docs ; https://www.zcashnames.com/docs/integrate/wallet-resolution ; https://www.zcashnames.com/docs/indexer/rpc-reference > \- Deployment/Release: https://www.zcashnames.com ; https://www.zcashnames.com/explorer ; https://www.zcashnames.com/roadmap ; https://www.zcashnames.com/beta/apply ; https://www.zcashnames.com/sharekit > \- Other Evidence: https://www.npmjs.com/package/zcashname-sdk ; https://www.zcashnames.com/leaders ; https://www.zcashnames.com/brandkit > > > \### Conflict of Interest Disclosure > > None known beyond the applicant’s direct role in building and operating the project; confirm and expand this field if there are financial, advisory, governance, or personal relationships that should be disclosed. > > \### 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. Update: > [@Call For Proposals: Coinholder-Directed Retroactive Grants Program Q3](https://forum.zcashcommunity.com/t/call-for-proposals-coinholder-directed-retroactive-grants-program-q3/56885/13): > > 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: We built seer-sync, a standalone Rust c… ---
**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:** [May 14, 2026, 8:09pm UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/10 "2026-05-14T20:09:56Z")
Unpinned on May 14, 2026, 8:09pm UTC ---
**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:** [May 15, 2026, 7:36pm UTC](https://forum.zcashcommunity.com/t/coinholder-directed-retroactive-grants-program-q2-2026-now-accepting-proposals/55328/11 "2026-05-15T19:36:05Z")
Open to thoughts and feedback! 🫡[https://forum.zcashcommunity.com/t/retroactive-grant-application-thorswap-metro/](https://forum.zcashcommunity.com/t/retroactive-grant-application-thorswap-metro/) > > > \### 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) > > @paperX-TS > > \### Organization or Individual Name > > THORSwap Labs > > \### Additional Team Members > > \`\`\`team-members.yaml > PaperX — CEO & Product Lead > Background: 5+ years at THORSwap, self-custody advocate, product-focused leadership > Role: Product strategy, business development, operations, communications, ecosystem partnerships > Contribution to ZEC Integration: Led Maya/NEAR partnership negotiations, product roadmap, launch coordination > \-- > 0xBadgers — Head of Data & Analytics > Background: Original THORSwap team member with 5+ years DeFi experience since 2020 > Role: Data analysis, financial reporting, volume tracking, product management > Contribution to ZEC Integration: ZEC metrics tracking, competitive analysis, liquidity monitoring > \-- > Paz — Engineering Manager > Background: 15+ years building infrastructure, platform tooling, distributed systems (web3 & enterprise) > Role: DevOps, team management, engineering flow, technical R&D > Contribution to ZEC Integration: Infrastructure architecture, overseeing continued updates and maintenance > \-- > Epicode — Lead Frontend Engineer > Background: 5+ years web3 development, built Metro embedded wallet with ZEC support > Role: Full-stack frontend development, wallet integrations > Contribution to ZEC Integration: Frontend ZEC swap UI, Metro wallet ZEC module, Maya/NEAR integration > \-- > Faizan — Senior Full-Stack Developer > Background: 7+ years React/Node.js engineering, DeFi-focused > Role: Full-stack development, API integration > Contribution to ZEC Integration: THORSwap frontend ZEC support, Keystore wallet integration, hardware wallet flows > \-- > Towan — SDK Engineer & Advisor > Background: Ex-THORSwap SDK engineer, now SwapKit SDK lead > Role: SwapKit SDK development & maintenance, wallet abstraction > Contribution to ZEC Integration: SwapKit SDK Zcash module (open source), SDK wallet support for ZEC-compatible wallets > \-- > Furan — QA Lead > Background: 20+ years IT engineering, QA at THORSwap since 2022 > Role: Quality assurance, bug tracking, edge case testing > Contribution to ZEC Integration: Comprehensive ZEC swap testing across 24+ chains, hardware wallet QA, production validation > \-- > Kvasir — Support Lead > Background: Crypto enthusiast since 2013 (Mt. Gox era), THORSwap contributor since 2021 > Role: Community support, ticket management > Contribution to ZEC Integration: Dedicated ZEC user support desk, cross-chain troubleshooting, wallet assistance > \`\`\` > > \### How did you learn about the Lockbox: Coinholder Retroactive Grants Program? > > We were referred to this program by Zcash community members. > > \### Requested Grant Amount (USD) > > $60,000 > > \### Category > > Non-Wallet Applications > > \### Project Summary > > Established in 2021, \[THORSwap\](https://app.thorswap.finance/) is a no-KYC DEX supporting cross-chain swaps across leading ecosystems such as Bitcoin, Ethereum, Zcash, Solana, XRP, BNB and more via permissionless non-custodial protocols. > > THORSwap integrated Zcash on October 1st 2025, enabling users to perform native cross-chain swaps directly to and from native ZEC via self-custodial wallets. Over the past 6 months, we have processed \*\*$50M+ in $ZEC volume\*\* with a \*\*$520K+ largest single swap record\*\*. > > We followed this up with \[Metro.exchange\](http://metro.exchange/), our new DeFi superapp currently in open beta, with \*\*native Zcash network\*\* support via our embedded \*\*Metro wallet\*\* for swaps, send, portfolio and asset management while ensuring users retain full self-custody. > > \### Project Description > > THORSwap is requesting for retroactive recognition of work already delivered: > > ✅ $50M+ ZEC volume > ✅ $520k largest swap (institutional/whale scale) > ✅ 24+ chains supported for Zcash trading > ✅ 6 months of proven uptime (no hacks or loss of user funds) > ✅ Mainstream media recognition (Bitcoin.com, CoinDesk, Binance) > > \### \*\*Today THORSwap enables Zcash users to:\*\* > > \- \*\*Access Cross-Chain Liquidity:\*\* > Swap ZEC permissionlessly to/from 24+ leading blockchains including Bitcoin, Ethereum, Solana, BNB, XRP, Tron, Sui, Cardano, Litecoin, Dogecoin, Bitcoin Cash, Avalanche, Arbitrum, Base, Polygon, Dash, Monad, NEAR, Optimism, Gnosis, THORChain, Mayachain, Kujira, Radix > > \- \*\*Maintain Self-Custody & Privacy:\*\* > No KYC, no sign-ups, no custodial risk. Users connect their own external wallet or manage self-custody Keystore/Metro wallet and retain full control of their keys and funds throughout the swap process > > \- \*\*Choose Hardware or Software Wallets:\*\* > Native ZEC support across Ledger, Trezor, KeepKey (hardware), Keystore Wallet (software), and Metro embedded wallet (passkey-based) > > \- \*\*Deep Onchain Liquidity:\*\* > Proven capacity to handle $300k+ swaps with sub-1% slippage via dual routing through Maya Protocol and NEAR Intents > > \- \*\*Trade Long-Tail Assets:\*\* > Beyond major cryptocurrencies, THORSwap provides access to stablecoins (USDC, USDT, DAI) and hundreds of ERC-20/BEP-20/SPL tokens directly swappable with ZEC > > \### What Sets THORSwap Apart > \*\*vs Centralized Exchanges:\*\* > \- No KYC/identity verification required > \- Non-custodial (wallet-to-wallet trading, no asset freezing mid-swap) > \- No withdrawal limits or account freezes > > \*\*vs Other DEXs:\*\* > \- $50M+ proven ZEC volume > \- 24+ chains tradable with $ZEC > \- Proven execution for whale/institutional traders ($520k largest swap) > \- Dual routing protocols (Maya + NEAR) for optimal execution > > \*\*vs Single-Chain Zcash Wallets:\*\* > \- Access to entire crypto ecosystem from ZEC holdings > \- No need to use centralized exchanges as intermediary > \- Enables ZEC holders to participate in DeFi across multiple chains > > \### Commitment to Continued Zcash Support > \*\*Regardless of grant outcome, THORSwap commits to:\*\* > \- Maintaining ZEC support on THORSwap and Metro platforms > \- Providing ongoing customer support for ZEC users via dedicated support desk > \- Implementing protocol upgrades as Zcash network evolves (e.g., future consensus upgrades, wallet compatibility) > \- Monitoring and optimizing ZEC routing liquidity across Maya and NEAR protocols > > \*\*We are also in the process of exploring:\*\* > > \- Additional new chain integrations for ZEC swaps (ie. TON, Starknet, Stellar, Midnight) > \- Zcash-specific feature enhancements (e.g., shielding support via external wallets and our native embedded Metro wallet solution, direct swaps to shielded addresses) > \- Increase marketing budget for Zcash ecosystem growth and user education > \- Zcash DeFi integrations (e.g., potential ZEC lending or earn products via NEAR or Solana) > > \### Technical Approach (how you did it) > > We integrated ZEC support through two independent routing protocols (Maya Protocol and NEAR Intents) via SwapKit SDK (previously THORSwap SDK), contributed to Zcash wallet integrations support hardware and software wallet interfaces, and continue delivered comms & marketing to onboard users to Zcash ecosystem. > > \### Development Timeline & Milestones > > \- \*\*May 2025:\*\* Research & planning, Business Development > > \- \*\*June 2025:\*\* Maya Protocol integration kickoff > > \- \*\*July 2025:\*\* Hardware wallet integrations (Ledger, Trezor, KeepKey) > > \- \*\*August 2025:\*\* NEAR Intents integration, dual-routing logic > > \- \*\*September 2025:\*\* Finalize UI+UX, Dual provider dynamic routing, QA testing > > \- \*\*October 1, 2025:\*\* Public launch. Marketing Comms and PR > > \- \*\*Oct 2025 - May 2026:\*\* Ongoing support, bug fixes, Metro wallet ZEC integration, maintenance > > \### What THORSwap Specifically Built and Maintains: > > \*\*1. Frontend UI & UX\*\* > - Integrating Zcash blockchain and supported wallets in the frontend > - Algorithmic dynamic quoting/recommendation between Maya Protocol and NEAR Intents (price vs time) > \- Swap confirmation optimization and error handling > \- Cross-chain tracker UI for Zcash swaps > \- Wallet connection support for native Zcash wallets (Keystore, Ledger, Trezor, Keepkey) > \- Mobile-responsive design > \- Metro Wallet Zcash integration (beta) > > \*\*2. Contributions to SwapKit SDK (collaborative effort between SwapKit and THORSwap)\*\* > - Wallet connection and transaction signing for native Zcash wallets (Keystore, Ledger, Trezor, Keepkey) > - Open source SDK published at: github.com/thorswap/swapkit > > \*\*3. Infrastructure & Services\*\* > - Hosting & tooling (Google cloud, Cloudflare, RPCs, GSuite, Quicknode, Sentry and more) > - Customer service (in-app and Discord support desk) > - Error monitoring and performance optimization > > \*\*4. PR, Comms and Marketing\*\* > - Launch PR, comms and outreach > - Continued marketing on social networks > > \*\*To enable Zcash crosschain swaps, we utilize:\*\* > - SwapKit.dev SDK and API for quoting, onchain transaction payload and tracking > - Execution of $ZEC swaps via AMM cross-chain liquidity pools (Maya Protocol) > - Execution of $ZEC swaps via Intent-based RFQ swaps (NEAR Intents) > > > \### Time Period of Work Completion > > 5 months of R&D + 6 months of ongoing production support (May 2025 - May 2026) > > \### Total Budget (USD) > > $60,000 > > \### Budget Breakdown > > \- \*\*Core Engineering & Development\*\* (500 hours, 3x Senior Devs) > - $(USD): $37,000 > - Justification: Frontend engineering UI+UX, Maya Protocol and NEAR Intents via SwapKit, contributions to SwapKit SDK Zcash module & hardware wallet support (Ledger, Trezor, KeepKey), Keystore and Metro wallet integrations, quote recommendation routing logic and more. > \- \*\*Quality Assurance & Testing\*\* (100 hours) > - $(USD): $4,000 > - Justification: Comprehensive testing across 24+ chains, hardware wallet compatibility, edge case validation, production readiness > \- \*\*Ongoing Maintenance & Dapp Upgrades\*\* (100 hours) > - $(USD): $5,000 > - Justification: Bug fixes, adopting protocol/wallet/SDK & API updates, performance optimization (Oct 2025 - May 2026), error reporting to wallets (ie. Ledger) > \- \*\*Research & Planning\*\* (20 hours) > - $(USD): $1,000 > - Justification: Initial R&D for Maya Protocol and NEAR Intents Zcash integration, network infrastructure setup, liquidity routing optimization > \- \*\*Infrastructure/Hosting (partial)\*\*: (6 months) > - $(USD): $5,000 > - Justification: Hosting and infra servicing costs (Google cloud, Cloudflare, RPCs, GSuite, Quicknode, Sentry and more) > \- \*\*Marketing, Communications & Media\*\*: > - $(USD): $3,500 > - Justification: Launch announcement, press releases, media coverage coordination, documentation, tutorials, community education materials > \- Customer Support & Community Management: (100 hours) > - $(USD): $4,000 > - Justification: Dedicated 24/7 support desk for ZEC users across 6 months, cross-chain navigation assistance, bug diagnostic and reporting > \- Misc Administration & Business Development: (10 hours) > - $(USD): $500 > - Justification: ongoing ecosystem collaboration, coordination, partnership development with KOLs, ECC, ZFND, Maya Protocol, NEAR, SwapKit etc. > > \### Total $(USD): $60,000 > > \### Previous Funding > > No > > \### Previous Funding Details > > \_No response\_ > > \### Other Funding Sources > > No > > \### Other Funding Sources Details > > \_No response\_ > > \### Success Metrics > > \### Volume & Liquidity Metrics: > > \- Processed \*\*$50 Million+ in native ZEC cross-chain swaps\*\* > \- Executed \*\*10+ swaps exceeding $300K each\*\*, largest: \*\*$520,718\*\* > \- Maintained \*\*$8.9M average monthly ZEC volume\*\* in 2025 > \- Average ZEC swap: \*\*~$22K (general), ~$46K (BTC ↔ ZEC)\*\* > \- \*\*45% of total ZEC volume\*\* from swaps over \*\*$100K\*\* > \- Zcash represents 3% of total platform volume > > \### Whale Activity: > \- Largest single swap: $520,718 > \- 10 individual swaps exceeded $300k each > \- 45% of total ZEC volume originated from swaps over $100k > \- Average swap size: ~$22k (general), ~$46k (BTC↔ZEC pairs specifically) > \- The BTC ↔ ZEC path averages $46,184 per swap — the highest of any path — indicating large holders actively rotating between the two leading cypherpunk assets > > \### Infrastructure Reliability — 98.4% completion rate > Only 40 swaps were refunded out of 2,527 total. A 98.4% completion rate over thousands of swaps proves the routing is production-grade and reliable at scale. > > \### Product Market Fit > ZEC totals 3% of THORSwap's total platform volume despite ZEC being one of 10,000+ supported assets. THORSwap is used by real traders daily, with consistent month-on-month retention well into 2026. > > \### Net Buy Pressure: +$10.4 Million > More capital has flowed in to purchase ZEC ($31.5M) than out ($21.1M). THORSwap users are net accumulators of ZEC, not distributors. This signals genuine demand and successful onboarding to Zcash ecosystem on THORSwap. > > \### Technical Integration: > > \- Enabled permissionless ZEC swaps across \*\*24+ blockchains\*\* > \- Support Zcash swaps via two cross-chain protocols: \*\*Maya Protocol\*\* and \*\*NEAR Intents\*\* > \- Shipped hardware wallet support (\*\*Ledger, Trezor, KeepKey\*\*) > \- Integrated self-custody wallets (\*\*Keystore, Metro embedded wallet\*\*) > > \### Ecosystem Impact: > > \- Recognized as a \[Zcash Ecosystem DEX\](https://z.cash/ecosystem/thorswap) > \- Mainstream media coverage recognizing THORSwap's ZEC integration as major adoption catalyst: > \-- \[Bitcoin.com: "Privacy coin ZEC soars after THORSwap support"\](https://news.bitcoin.com/privacy-coin-zec-soars-after-thorswap-support-and-grayscale-trust-announcement/) > \-- \[CoinDesk: "Inside Zcash: Encrypted Money at Planetary Scale" (featuring THORSwap)\](https://www.coindesk.com/research/inside-zcash-encrypted-money-at-planetary-scale) > \-- \[MSN\](https://www.msn.com/en-us/money/markets/zcash-soars-to-three-year-high-after-thorswap-adds-cross-chain-swaps-with-btc-eth-sol-and-others/ar-AA1NFKYt?apiversion=v2&domshim=1&noservercache=1&noservertelemetry=1&batchservertelemetry=1&renderwebcomponents=1&wcseo=1), \[Binance\](https://www.binance.com/en/square/post/30454517375034), \[OKX\](https://www.okx.com/learn/zec-privacy-coin-zcash-momentum), \[Bitget Academy\](https://www.bitget.com/academy/zcash-zec-latest-news-price-surge-grayscale-thorswap) all attributed ZEC price momentum to THORSwap launch (more examples in ‘Media Coverage’ section below) > > \*\*Detailed Report:\*\* > \Image > \Image > \Image > \Image > \Image > > \### Proof of completion > > \- Links: > - THORSwap dApp: \[app.thorswap.finance\](https://app.thorswap.finance) > - Metro dApp (beta): \[metro.exchange\](https://metro.exhange) (with Metro embedded wallet) > - SwapKit SDK (MIT License): \[github.com/thorswap/swapkit\](https://github.com/thorswap/swapkit) > - Documentation: \[docs.thorswap.finance\](https://docs.thorswap.finance) > > \- Contact Information > - Twitter/X: \[@THORSwap\](https://x.com/THORSwap) > - Discord: \[discord.gg/thorswap\](https://discord.gg/thorswap) > - Support: \[contact@thorswap.finance\](mailto:contact@thorswap.finance) > > \- On-Chain Verification > - Volume Data: https://app.thorswap.finance/dashboard > - DeFillama: https://defillama.com/protocol/thorswap > - Maya Protocol block explorer: mayascan.org > - NEAR Protocol explorer: \[Swaps from ZEC\](https://explorer.near-intents.org/?fromChainId=zec&affiliate=thorswap.near), \[Swaps to ZEC\](https://explorer.near-intents.org/?affiliate=thorswap.near&toChainId=zec) > > \- Official Announcements > - THORSwap Medium: \["Zcash Native Cross-Chain Integration Now Live on THORSwap" \](https://thorswap.medium.com/zcash-native-cross-chain-integration-now-live-on-thorswap-f925524b2cb0)(Oct 1, 2025) > - Discord: \[Community announcement\](https://discord.com/channels/831398059484250142/832288784922050600/1422615550835691691) > - Twitter/X: \[Official launch thread with community engagement\](https://x.com/THORSwap/status/1973055026622062869) > - Twitter/X: \[Zcash announcement article\](https://x.com/THORSwap/status/1973054857788723236) > - \[Telegram announcement\](https://t.me/thorswap\_ann/378) > - \[Farcaster announcement\](https://farcaster.xyz/thorswap/0x02b67096) > - \[Debank announcement\](https://debank.com/stream/3328598) > \- Sample of ongoing engagement: > https://x.com/THORSwap/status/1974528131873825151?s=20 > https://x.com/THORSwap/status/1973401700166935008?s=20 > https://x.com/THORSwap/status/1984670370490950043?s=20 > https://x.com/near\_intents/status/1981324497430139322?s=20 > https://x.com/THORSwap/status/1986551117258629518?s=20 > https://x.com/THORSwap/status/1982563016643387811?s=20 > https://x.com/paperX\_Art/status/1991195055366042085?s=20 > https://x.com/THORSwap/status/1981079492006465876?s=20 > \- Media Coverage: > - Bitcoin.com: \["Privacy coin ZEC soars after THORSwap support and Grayscale Trust announcement"\](https://news.bitcoin.com/privacy-coin-zec-soars-after-thorswap-support-and-grayscale-trust-announcement/) > - CoinDesk: \["Inside Zcash: Encrypted Money at Planetary Scale"\](https://www.coindesk.com/research/inside-zcash-encrypted-money-at-planetary-scale) (featuring THORSwap as key infrastructure) > - MSN: \["Zcash soars to three-year high after THORSwap adds cross-chain swaps with BTC, ETH, SOL and others"\](https://www.msn.com/en-us/money/markets/zcash-soars-to-three-year-high-after-thorswap-adds-cross-chain-swaps-with-btc-eth-sol-and-others/ar-AA1NFKYt?apiversion=v2&domshim=1&noservercache=1&noservertelemetry=1&batchservertelemetry=1&renderwebcomponents=1&wcseo=1) > - Binance Square: \[Coverage of ZEC momentum following THORSwap launch\](https://www.binance.com/en/square/post/30421188322586) > - OKX Learn: \["ZEC Privacy Coin Zcash Momentum"\](https://www.okx.com/learn/zec-privacy-coin-zcash-momentum) (citing THORSwap integration) > - Bitget Academy: \["Zcash (ZEC) Latest News: Price Surge, Grayscale, THORSwap"\](https://www.bitget.com/academy/zcash-zec-latest-news-price-surge-grayscale-thorswap) > - https://stocktwits.com/news-articles/markets/cryptocurrency/zcash-soars-to-three-year-high-after-thorswap-adds-cross-chain-swaps/chCYe58R3ao > - https://www.cointribune.com/en/crypto-zcash-makes-a-historic-comeback-of-220/ > - https://www.onesafe.io/blog/zcash-60-surge-privacy-coins-cryptocurrency > - https://finance.yahoo.com/news/zcash-enters-top-25-smash-100206821.html > - https://www.tradingview.com/news/coinpedia:14b4fbcc9094b:0-zec-price-reclaims-spotlight-with-breakout-rally-and-rising-demand/ > > \### Conflict of Interest Disclosure > > THORSwap Labs has no conflicts of interest with respect to this retroactive grant application: > > \- No financial relationships with Zcash Foundation, Electric Coin Company, or grant program reviewers > \- No competing grants from other Zcash funding sources (this is our first Zcash grant application) > > THORSwap maintains commercial relationships with Swapkit, Maya Protocol and NEAR Intents as infrastructure providers for cross-chain routing. Our cross-chain routing infrastructure utilizes SwapKit’s API and open source SDK (previously THORSwap SDK), leading up to the Zcash integration our current and ex contributors updated the SDK for wallets and chain integrations. This does not affect our independence or commitment to the Zcash ecosystem. > > \### 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.