I have submitted a Zcash Community Grants application on behalf of Cryppit:
The application requests $24,500 to make transparent ZEC-source swaps in Vultisig/SwapKit compatible with Zcash v5 and ZIP 244. A live unsigned probe documented in vultisig-android#6115 found that current ZEC-source routes are available but the provider still returns a Sapling-v4 transparent transaction. Under the proposed NU7 rules, this creates a swap-specific compatibility gap that cannot safely be repaired only inside the Android signer.
The proposed deliverables are:
- a maintainer-approved provider payload specification and canonical ZIP 244 fixtures;
- a v5 transaction-construction path in the SwapKit/provider layer;
- Vultisig Android v5 swap-signing integration that preserves the provider transaction plan and existing security checks;
- cross-platform conformance and deterministic NU7 acceptance evidence; and
- three months of bounded maintenance.
This proposal is intentionally separate from pending ZCG application #511. That application covers the native transparent Wallet Core foundation and explicitly lists swaps as outside scope. Cryppit will reuse and credit compatible Wallet Core outputs rather than request funding to recreate them.
The principal dependency is written coordination from Vultisig/SwapKit identifying the backend owner, contribution path and intended-user validators. If that access is unavailable, the provider implementation milestone will not be claimed and the project will seek a formal rescope.
I would particularly appreciate feedback on:
- whether the swap-provider and wallet-integration scope is sufficiently distinct from application #511;
- whether Vultisig/SwapKit should co-fund the provider-specific milestone;
- the proposed intended-user validation and cross-platform acceptance criteria; and
- whether the three-month maintenance period should remain part of this application.
Tagging @ZcashGrants for guidance and review.
— Anirudh Tumuluru, Cryppit (@Anirudh-712 on GitHub)