Back to projects
Zephyr Wallet icon

Zephyr Wallet

Zypherpunk privacy, MetaMask simplicity

$500
Total awarded
Zephyr Wallet
Max
Builder
HTML JavaScript .NET TypeScript MongoDB

Awards

The problem it solves

Privacy is a huge upcoming meta, but it’s still hard to access - complex UX, steep learning curves, and siloed ecosystems currently pose a barrier to entry.

The Zephyr wallet by OASIS Web4 solves this. In addition to Solana and Ethereum, it integrates 4 Zypherpunk providers (Zcash, Starknet, Miden, Aztec) in a single wallet that works like Phantom or Metamask - retaining the core privacy features of each chain, while keeping the UX exactly as regular people have come to expect.

image

image

Zephyr leverages several powerful cross-chain APIs that we’ve been working on with OASIS WEB4, to handle complexity and present a unified, secure user experience. Users authenticate with a single secure cross-chain avatar (which can also be anonymous) - which then generates unique wallet addresses for each of the providers. Users manage this account with a single seed phrase. Important to note - our provider architecture can extend to include any chain.

We’ve included all the wallet features that users expect - send, receive, swap (atomic), view token history. In addition to this, we’ve added useful new privacy tools, such as one-click shielded transfers, and send / receive drops. And, a stablecoin function between ZCash and Aztec.

Users shouldn’t have to understand the underlying technology to get their benefits - as we move into a world with increasing surveillance, making sure as many people have access to privacy tools as possible, and allowing privacy ecosystems to share liquidity and overcome silos, without compromising on their core principles, is worth fighting for.

Challenges we ran into

One of the major challenges we faced was tackling wallet address derivation for each provider, using our own API (which is .NET based). Each provider works differently - so generating working wallet addresses for all our chains at the same time required a lot of research. We got around it by finding existing .NET based SDKs, and switching from a generic key generation to a custom approach per chain.

Massive thanks to Starknet, and Andrew Arnott of Zcash’s Nerdbank for their SDKs, without which we wouldn’t have been able to integrate Starknet / Zcash.

Building the underlying back-end technology we are using has been a huge undertaking - in fact it’s a 10 year project, and we are extremely excited to be using it for this use case.

Gallery