Thank you for the detailed technical feedback. I want to address your concerns about market viability by clarifying the institutional context that informed this proposal (Grant Application Forum Post)
Clarifying the Initial Discussion
The forum introduction that prompted your feedback was an introduction to BazaarSwap as a platform and business. It was not a proposal for WalletConnect v2 integration at that time. The current grant application represents the first formal proposal for WalletConnect v2 infrastructure, informed by Crosslink’s development timeline and LST-ZEC’s anticipated launch.
BazaarSwap’s value proposition as a cross-chain liquidity aggregator stands independently from this infrastructure request. The WalletConnect v2 integration enhances that existing platform by enabling non-custodial wallet connectivity, but does not define its core utility.
Crosslink: The Ecosystem Inflection Point
Shielded Labs is targeting completion of a Crosslink prototype within 12 months, with a 9-month productionization phase to follow. This consensus upgrade will introduce staking mechanics to Zcash, producing liquid staked ZEC (LST-ZEC) as a primary ecosystem asset.
Once Crosslink activates on mainnet, LST-ZEC holders will require non-custodial access to decentralized finance applications. This is not speculative demand, it is an architectural requirement of the protocol upgrade itself.
The Interoperability Necessity
LST-ZEC utility depends on standardized wallet-to-dApp connectivity. Current options are:
-
Custodial bridges (wrapped tokens, CEX deposits)
-
Custom point-to-point integrations (wallet-specific development)
-
WalletConnect v2 (standardized, non-custodial, 600+ wallet ecosystem)
WalletConnect v2 is the industry standard mechanism for non-custodial wallet interoperability. It is the only mechanism that enables LST-ZEC to participate in:
-
Rujira Primitives (currently live, will support ZEC lending, borrowing, and liquidity pools)
-
THORChain swaps
-
MayaChain swaps
-
600+ additional WalletConnect-compatible applications
Without standardized wallet connectivity, LST-ZEC users are forced back to custodial solutions, which is the opposite of Zcash’s core value proposition.
Why BazaarSwap Matters (And Why It Doesn’t)
You are correct that a single DApp cannot drive WalletConnect adoption. That is not the ask.
BazaarSwap’s role is to serve as a proof of concept that demonstrates:
-
WalletConnect v2 functions correctly for all Zcash address types (transparent, Sapling, Orchard, Unified)
-
Cross-chain liquidity aggregation is a valid use case for LST-ZEC
-
The infrastructure is production-ready and secure before other wallets and DApps build on it
BazaarSwap (https://bazaarswap.io) aggregates liquidity from over 350+ decentralized exchanges across 45+ cross-chain protocols, including THORChain and MayaChain. Once WalletConnect v2 integration is complete, BazaarSwap will enable non-custodial ZEC liquidity access on THORChain through native wallet connectivity. This is a capability that does not currently exist for Zcash users.
BazaarSwap’s integration with leading cross-chain infrastructure is documented in Rubic Exchange’s public ecosystem documentation: https://docs.rubic.finance/rubic/overview/ecosystem
This positions BazaarSwap as a legitimate first integration demonstrating WalletConnect v2 functionality, not as a commercial bet on a single application’s success.
Why Zcash’s Architecture Doesn’t Limit WalletConnect’s Value
You correctly identified that Zcash lacks smart contract functionality, which is the primary driver of WalletConnect adoption on Ethereum. This distinction is important and worth addressing directly.
WalletConnect’s value on Ethereum derives from enabling users to negotiate smart contract interactions through a standardized protocol. Zcash does not need this capability. LST-ZEC utility does not depend on smart contract execution on the Zcash layer.
Instead, LST-ZEC derives utility from deployment across external DeFi ecosystems:
-
Rujira Primitives: Users lend, borrow, and provide liquidity using LST-ZEC without executing Zcash smart contracts
-
THORChain and MayaChain: These protocols handle settlement and execution; WalletConnect simply enables users to authorize transactions from their Zcash wallet
-
Other WalletConnect-compatible applications: Similarly, these platforms execute logic on their own layers while WalletConnect enables simple, non-custodial wallet authorization
WalletConnect for Zcash is not about enabling complex contract negotiation. It is about enabling non-custodial transaction authorization across external DeFi platforms that already support Zcash assets.
Regarding multi-currency wallet support: Unstoppable Domains, Edge Wallet, and similar platforms will naturally integrate WalletConnect v2 for Zcash once the standard is established. Their incentive is user demand. Once LST-ZEC exists and users seek to deploy it in DeFi, these wallet teams will update their repositories to reflect the latest WalletConnect protocol additions for Zcash support. This is a routine maintenance update, not a speculative build.
The distinction you raised between QR codes and wallet connectivity is also worth clarifying. For a single swap on a single chain, QR code authorization is sufficient. But LST-ZEC’s value depends on liquidity deployment across multiple ecosystems simultaneously: users need to manage positions across Rujira, THORChain, and MayaChain without scanning QR codes for each transaction. This is where standardized wallet connectivity becomes necessary, not optional.
Wallet Integration is Not Speculative
You identified a real constraint: wallets need incentive to integrate. We have already had initial discussions with two wallet teams that currently support WalletConnect v2. Their integration path is straightforward. They update their repository to reflect the latest protocol additions for Zcash support.
Once WalletConnect v2 is standardized for Zcash, wallet integration becomes a routine update, not a custom development effort. Wallet teams integrate because:
-
Their users hold Zcash and will demand access to LST-ZEC utility
-
WalletConnect v2 integration is no longer optional for competing wallets
-
The effort is maintenance-level, not engineering-intensive
Institutional Validation
Vitalik Buterin has provided a second round of funding to Shielded Labs to accelerate Crosslink development, emphasizing that Zcash is “one of the most honorable crypto projects focused on privacy.” This funding is explicitly supporting the productionization phase of Crosslink, including security audits and thorough analysis.
The convergence of these initiatives (Crosslink’s core infrastructure work backed by external funding and a 12-month development roadmap, paired with WalletConnect v2 standardization) represents a coordinated ecosystem build, not speculative infrastructure.
Success Metrics Are Infrastructure-Level
The proposal’s success criteria are independent of any single application’s commercial performance:
-
SDK passes independent security audit with zero critical findings
-
2+ wallets successfully integrate the SDK
-
SDK is listed in WalletConnect’s official ecosystem registry
-
1+ production application deploys LST-ZEC via WalletConnect v2
These are ecosystem infrastructure benchmarks, measured by standardization and adoption enablement.
The Timing Argument
This proposal positions WalletConnect v2 integration to be complete and audited at the moment LST-ZEC enters active circulation on mainnet. This is synchronized infrastructure development, not speculative deployment.
Once LST-ZEC is live, the market demand for wallet connectivity is not “hoped for.” It is architectural. Users holding a new asset class on Zcash will immediately seek ways to deploy that asset in DeFi. WalletConnect v2 is the mechanism that makes this possible without custodial intermediation.