# Grant Application - Shielded ZEC (Ironwood) for React Native wallets — Any Wallet Kit

**URL:** <https://forum.zcashcommunity.com/t/grant-application-shielded-zec-ironwood-for-react-native-wallets-any-wallet-kit/59428>\
**Category:** Applications\
**Created:** [November 18, 2026, 1:58pm UTC](https://forum.zcashcommunity.com/t/grant-application-shielded-zec-ironwood-for-react-native-wallets-any-wallet-kit/59428 "2026-11-18T13:58:03Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![0xdanya](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/0xdanya/32/50458_2.png) [@0xdanya](https://forum.zcashcommunity.com/u/0xdanya)\
**Post date:** [November 18, 2026, 1:58pm UTC](https://forum.zcashcommunity.com/t/grant-application-shielded-zec-ironwood-for-react-native-wallets-any-wallet-kit/59428/1 "2026-11-18T13:58:03Z")

</div>

Hi everyone,

We’ve submitted a ZCG application for shielded ZEC in React Native wallets:

> <https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/582>
>
> \### Terms and Conditions
> 
> \- \[X\] I agree to the \[Grant Agreement\](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_f81ef4e4b5f040038350270590eb2e42.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 agree to adhere to the \[Code of Conduct\](https://forum.zcashcommunity.com/t/zcg-code-of-conduct/41787) and \[Communication Guidelines\](https://forum.zcashcommunity.com/t/zcg-communication-guidelines/44284)
> \- \[X\] I understand all milestone deliverables will be validated and accepted by their intended users or their representatives, who will confirm that the deliverables meet the required quality, functionality, and usability for each user story.
> \- \[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 agree to post request details on the \[Community Forum\](https://forum.zcashcommunity.com/c/grants/33)
> \- \[X\] I understand it is my responsibility to post a link to this issue on the \[Zcash Community Forums\](https://forum.zcashcommunity.com/c/grants/33) after this application has been submitted so the community can give input. I understand this is required in order for ZCG to discuss and vote on this grant application.
> 
> \### Application Owners (\`@Octocat\`, \`@Octocat1\`)
> 
> @ultratestbro
> 
> \### Organization Name
> 
> Any Wallet Kit (AWK) — independent open-source project (no legal entity)
> 
> \### How did you learn about Zcash Community Grants
> 
> Zcash Community Forum, while working on NU7 / Ironwood support
> 
> \### Requested Grant Amount (USD)
> 
> $20,000
> 
> \### Category
> 
> Wallets
> 
> \### Project Lead
> 
> \`\`\`project-lead.yaml
> Name: Danya
> Role: Founder & developer, Any Wallet Kit
> Background: Builds AWK, an open-source SDK for self-custodial React Native wallets (59 npm packages). Shipped AWK's transparent Zcash package (v5 / ZIP-244 signing, ZIP-317 fees) in October 2026 and its NU7 fix a day after activation (@anywalletkit/wallet-zcash 0.5.2, 2026-11-07). Built and measured the shielded prototype described below.
> Responsibilities: All development, upstream contributions, measurements and milestone reports.
> \`\`\`
> 
> \### Additional Team Members
> 
> \`\`\`team-members.yaml
> None
> \`\`\`
> 
> \### Project Summary
> 
> A reusable, MIT-licensed TypeScript module, \`@anywalletkit/wallet-zcash-shielded\`, that gives any React Native wallet shielded ZEC on the Ironwood pool: a unified address, sync, per-pool balances, history, sending, shielding and the Orchard → Ironwood migration. It runs on the ZODL SDKs through EdgeApp/react-native-zcash. We write no new Zcash cryptography and fork nothing, and we contribute what we fix back to the wrapper. A mainnet prototype already exists and has received ZEC into Ironwood.
> 
> \### Project Description
> 
> AWK is an open-source SDK for self-custodial mobile wallets: 59 npm packages, 8,200+ tests, 560 smoke checks on the Hermes engine, docs at https://docs.anywallet.tech. Our test app runs it end to end on iOS and Android. AWK supports Zcash today, but transparent only.
> 
> This grant adds the shielded side in a form other React Native wallets can reuse. Wallet developers install one package and get shielded ZEC with AWK's safety layer: address checks, review before signing, spending policies, and the seed kept in the Keychain / Keystore.
> 
> \### Proposed Problem
> 
> \- Most new mobile wallets are built in React Native, but shielded ZEC there means native Swift/Kotlin work on each platform.
> \- The only RN bridge, react-native-zcash, needs Expo-specific native edits before it installs, and its NU7 path (\`jon/zcash-nu7-sdks\`) is not released yet.
> \- As a result, RN wallets that list ZEC usually stop at transparent addresses, and their users get no privacy.
> \- After NU6.3, value also needs to move from Orchard into Ironwood, and there is no reusable RN flow for that.
> 
> \### Proposed Solution
> 
> A thin TypeScript layer over react-native-zcash that:
> 
> \- exposes typed, \`bigint\`-safe APIs for addresses, sync, balances, history, sending, shielding and migration;
> \- validates everything the native side returns. Unified addresses are decoded in TS (ZIP-316 + F4Jumble, tested against zcash-test-vectors), must carry a shielded receiver, and their transparent receiver must equal the account's t-address;
> \- keeps keys where AWK keeps them and passes the seed to the native SDK only for the call that needs it. Our upstream proposal EdgeApp/react-native-zcash#81 is for the wrapper to open accounts by viewing key, so the phrase does not cross the bridge on every start;
> \- ships an Expo config plugin upstream, so Expo apps install the wrapper without hand-editing native projects.
> 
> \### Solution Format
> 
> An npm package (\`@anywalletkit/wallet-zcash-shielded\`) with docs and an example app in the AWK repository, plus upstream pull requests and issues to EdgeApp/react-native-zcash and the ZODL SDKs.
> 
> \### Dependencies
> 
> \- \*\*ZODL wallet SDKs (AGPL-3.0-only).\*\* Apps built on AWK must either be AGPL themselves or hold a commercial licence from ZODL. App Store distribution always needs that licence: \`LICENSE-EXCEPTIONS.md\` §3b grants no exception. We wrote to licensing@zodl.com on 2026-11-18 and are awaiting a reply. Our module stays MIT and contains no ZODL code.
> \- \*\*EdgeApp/react-native-zcash \`jon/zcash-nu7-sdks\`.\*\* We will move to a tagged NU7 release when one exists. Until then we build it with its own \`update-sources\` and carry local fixes via patch-package only.
> \- \*\*lightwalletd / Zaino servers.\*\* Tested on zec.rocks (ECC lightwalletd v0.6.1, Zebra 7.1.0); the server is configurable.
> 
> \### Technical Approach
> 
> \`\`\`
> React Native app (Hermes, New Architecture)
> └─ @anywalletkit/wallet-zcash-shielded TypeScript, MIT
> └─ react-native-zcash Edge, RN native module (Swift / Kotlin)
> └─ ZODL Zcash SDK zodl-swift-wallet-sdk / zodl-android-wallet-sdk
> └─ librustzcash keys (ZIP-32), scanning, proving, wallet DB
> └─ lightwalletd (gRPC/TLS)
> \`\`\`
> 
> \*\*Prototype (done, measured 2026-11-17/18):\*\*
> 
> \- \*\*Builds:\*\* react-native-zcash \`jon/zcash-nu7-sdks\` builds without a fork on both platforms; Release builds of our test app (Expo 58, RN 0.88, New Architecture) include the module.
> \- \*\*Unified address:\*\* transparent + Sapling + Orchard-format receivers. Ironwood shares the Orchard receiver (\`zcash\_keys\` 0.17), so the address receives into Ironwood.
> \- \*\*Mainnet receive:\*\* 0.00575 ZEC received into Ironwood, txid \`c8459b64116abc8f9cb83e03bca259e7505020414b499821d64168b371188cf7\` (block 3,586,149), shown as spendable Ironwood balance on an iPhone 16 Pro.
> 
> | | iPhone 16 Pro, iOS 27.0.1 | Android emulator (2 cores, 2 GB)\* |
> |---|---|---|
> | First sync from a one-month-old birthday (~66k / 63k blocks) | 308 s | 1,135 s |
> | First sync, new wallet (~6k / 2.6k blocks) | 32 s | 298 s |
> | CPU during sync (mean, % of one core) | 124 % of 600 % | 104 % of 200 % |
> | Memory during sync | 165–178 MB footprint | 249–275 MB RSS |
> | App size added | IPA +23.3 MB | APK arm64 +56.1 MB |
> 
> \\\* Emulator, not a physical low-end phone; a real low-end device is part of Milestone 1.
> 
> Method, raw numbers and limits: https://github.com/ultratestbro/anywalletkit/blob/feat/zcash-shielded-proto/packages/wallet-zcash-shielded/sdk229/METHOD\_NOTE.md
> 
> \### Upstream Merge Opportunities
> 
> Filed (2026-11-18):
> \- EdgeApp/react-native-zcash#81 — open accounts by UFVK; take seed bytes instead of the phrase for spends.
> \- EdgeApp/react-native-zcash#82 — stale checkpoints on the NU7 branch; checkpoint script assumes 75 s blocks.
> \- EdgeApp/react-native-zcash#83 — iOS loses the first \`SYNCING\` status event.
> \- zodl-inc/zodl-swift-wallet-sdk#120 and zodl-inc/zodl-android-wallet-sdk#64 — Tor / voting / Keystone as Cargo features; the FFI library adds ~56 MB per ABI.
> 
> Planned PRs to react-native-zcash: an Expo config plugin (iOS modular headers; Android desugaring + minSdk 27); an NDK version check in \`update-sources\`; reject instead of crash (\`try!\`) on storage-path errors; the UFVK initialisation from #81; Android event-emitter stubs and manifest clean-up. Earlier context: EdgeApp/react-native-zcash#80.
> 
> \### Open Source License
> 
> MIT
> 
> \### Hardware/Software Costs (USD)
> 
> $500
> 
> \### Hardware/Software Justification
> 
> \- A physical low-end Android phone (~$150): the prototype's Android numbers come from an emulator.
> \- A mid-range iPhone (~$350, used): we only have a high-end iPhone 16 Pro.
> 
> Both are needed for the sync, memory and battery figures that wallet developers will rely on.
> 
> \### Service Costs (USD)
> 
> $0
> 
> \### Service Costs Justification
> 
> None. We use public lightwalletd servers and our existing CI.
> 
> \### Compensation Costs (USD)
> 
> $19,500
> 
> \### Compensation Costs Justification
> 
> 260 hours of senior development at $75/h: the module, the example app, the upstream PRs, documentation and mainnet test transactions across three milestones.
> 
> \### Total Budget (USD)
> 
> $20,000
> 
> \### Previous Funding
> 
> No
> 
> \### Previous Funding Details
> 
> \_No response\_
> 
> \### Other Funding Sources
> 
> No
> 
> \### Other Funding Sources Details
> 
> Self-funded so far, including the prototype.
> 
> \### Implementation Risks
> 
> 1. \*\*Licence.\*\* Without terms from ZODL, closed-source apps built on AWK cannot ship the module, and no app can ship it on the App Store. Mitigation: the module, the example app, open-source/AGPL builds and the upstream work go ahead regardless; we document the licensing path for developers and report the ZODL outcome at Milestone 1.
> 2. \*\*No tagged NU7 release of the wrapper.\*\* Mitigation: build from the branch with its own script, pin commits, move to the release when it is tagged.
> 3. \*\*Upstream responsiveness.\*\* If PRs are not merged, we keep them as patch-package patches and document them. We do not fork.
> 4. \*\*App size (~+23 MB IPA, ~+56 MB APK).\*\* Mitigation: the Cargo-features proposal upstream; we report the delta per release.
> 
> \### Potential Side Effects
> 
> \- \*\*Larger apps\*\* for wallets that add the module; the size is documented up front.
> \- \*\*Transparent receiver privacy.\*\* The unified address includes a transparent receiver, and senders who use it get no privacy. Milestone 2 adds an option for addresses without a transparent receiver, and clear UI guidance about which pool funds land in.
> 
> \### Success Metrics
> 
> \- \`@anywalletkit/wallet-zcash-shielded\` published on npm with docs and an example app.
> \- The example wallet app (iOS and Android) covers every flow; the integration guide is verified by installing the module into a fresh Expo app.
> \- Mainnet transactions from the module for each flow (receive, send shielded → shielded, shield transparent funds, Orchard → Ironwood migration), with txids published in the milestone reports.
> \- First-sync time, memory and CPU measured on a low-end Android and a mid-range iPhone, published with each milestone.
> \- At least the Expo config plugin PR submitted to react-native-zcash; merged PRs and closed issues tracked in the reports.
> 
> \### Startup Funding (USD)
> 
> $0
> 
> \### Startup Funding Justification
> 
> Not requested; the prototype is already built.
> 
> \### Milestone Details
> 
> \`\`\`milestones.yaml
> \- Milestone: 1
> Amount (USD): 10000
> Expected Completion Date: 2027-01-15
> User Stories:
> - "As a React Native wallet developer, I want to add one package and show my users a unified address, shielded balances per pool and sync progress, so that they can receive ZEC privately"
> - "As an Expo developer, I want react-native-zcash to install without hand-editing native projects, so that adding shielded ZEC takes minutes, not days"
> Deliverables:
> - "@anywalletkit/wallet-zcash-shielded" beta on npm: unified address, sync from birthday, per-pool balances (incl. Ironwood), transaction history, sync progress and errors
> - Example app (iOS and Android) in the AWK repository; install verified in a fresh Expo app
> - Expo config plugin PR and UFVK-initialisation PR (#81) submitted to react-native-zcash
> - Sync, memory, CPU and size measurements on a physical low-end Android and a mid-range iPhone
> - Licensing guide for developers (AGPL vs ZODL commercial licence) and the ZODL outcome
> Acceptance Criteria: A developer installs the beta into a fresh Expo app following the docs, receives mainnet ZEC into Ironwood and sees it in the balance; measurement report published with device models, versions and server.
> \- Milestone: 2
> Amount (USD): 6000
> Expected Completion Date: 2027-02-12
> User Stories:
> - "As a wallet user, I want to send ZEC privately and shield my transparent funds, so that my balance and payments are not public"
> - "As a wallet user holding Orchard notes, I want a guided Orchard → Ironwood migration, so that my funds move to the current pool safely"
> Deliverables:
> - send (shielded and to transparent), shield transparent funds, Orchard → Ironwood migration
> - describeTransaction (review before signing) and AWK spending policies for every write
> - Option for unified addresses without a transparent receiver
> Acceptance Criteria: Each flow runs from the example app on mainnet; txids for every flow are published; the review screen shows pools, amount, fee and recipient before signing.
> \- Milestone: 3
> Amount (USD): 4000
> Expected Completion Date: 2027-03-05
> User Stories:
> - "As a wallet developer, I want a stable, documented release, so that I can ship shielded ZEC to production"
> Deliverables:
> - 1.0 release on npm; docs and an integration guide on docs.anywallet.tech; example app
> - Remaining upstream PRs (NDK check, storage-error handling, Android emitter stubs)
> - Final report: measurements, upstream status, known limits
> Acceptance Criteria: 1.0 is installable from npm with the published docs; the final report lists every upstream PR/issue with its status.
> \`\`\`
> 
> \### Supporting Documents
> 
> \`\`\`files.yaml
> \- Method note (prototype, architecture, measurements): https://github.com/ultratestbro/anywalletkit/blob/feat/zcash-shielded-proto/packages/wallet-zcash-shielded/sdk229/METHOD\_NOTE.md
> \- Prototype code: https://github.com/ultratestbro/anywalletkit/tree/feat/zcash-shielded-proto/packages/wallet-zcash-shielded
> \- Upstream issues: EdgeApp/react-native-zcash#80-#83, zodl-inc/zodl-swift-wallet-sdk#120, zodl-inc/zodl-android-wallet-sdk#64
> \- AWK docs: https://docs.anywallet.tech
> \`\`\`

**What:** `@anywalletkit/wallet-zcash-shielded`, an MIT-licensed TypeScript module that gives any React Native wallet shielded ZEC on the Ironwood pool. It covers the unified address, sync, per-pool balances and history (M1), sending, shielding and the Orchard → Ironwood migration (M2), and a documented 1.0 (M3). It runs on the ZODL SDKs through EdgeApp/react-native-zcash. No new Zcash cryptography and no fork; fixes go upstream.

**Already working:** a mainnet prototype on react-native-zcash’s NU7 branch received 0.00575 ZEC into Ironwood (block 3,586,149) on an iPhone 16 Pro. First sync from a one-month-old birthday took 308 s on the iPhone and 1,135 s on a 2-core Android emulator. A new wallet synced in 32 s on the iPhone. Method note with all numbers:

> <https://github.com/ultratestbro/anywalletkit/blob/feat/zcash-shielded-proto/packages/wallet-zcash-shielded/sdk229/METHOD_NOTE.md>

**Upstream so far:** react-native-zcash #81 (open accounts by viewing key, so the seed phrase doesn’t cross the JS bridge), #82 (stale checkpoints), #83 (lost iOS status event); ZODL SDKs swift#120 / android#64 (optional Tor / voting / Keystone to cut ~56 MB per ABI). Next: an Expo config plugin PR.

**Budget:** $20,000 in three milestones ($10k / $6k / $4k), through early March 2027.

**Open question we’re working on:** the ZODL SDKs are AGPL-3.0-only with no App Store exception. We’ve asked ZODL about terms for developers building on AWK and will report the outcome at M1.

Feedback very welcome, especially from wallet developers who’d use this.

— Danya, Any Wallet Kit
