What happens if I lose my recovery phrase?

The funds are unreachable, by us and by anyone else. Self-custody has no password reset, so write the phrase down offline before you fund the wallet, and keep a second copy in a different place.

Can I use the same wallet on desktop and phone?

Yes. Import the same recovery phrase, or pair the two by QR code. Accounts and names sync; the key itself stays on each device.

Which chains are supported?

262 chains from the Zunia chain registry: 218 Cosmos chains, 43 EVM chains and 1 Solana chain, including Safrochain. The list updates without an app release. Custom chains can be added by RPC endpoint.

The wallet is free. You pay only the network fee for each transaction, shown before you sign. Zunia takes no cut of transfers or staking rewards, and there is no premium tier.

Yes, Apache 2.0. A third-party audit and reproducible builds for the extension are scoped for the 1.0 release and will be published on this page.

Does Zunia have a token?

No. There is no Zunia token, no airdrop and no presale. Anything claiming otherwise is a scam, whoever it appears to come from.

Do you support hardware wallets?

Ledger Nano S Plus, Nano X and Stax over USB and WebHID, and Keystone 3 by QR code. On mobile you can also approve a desktop transaction by scanning it, so the key never touches the computer.

Hold, send, stake,
across every chain.

Zunia is a multi-chain wallet for the Cosmos ecosystem, running as a browser extension and a mobile app on the same keys.

9:41

Portfolio

$12,408.20

SendStake

Cosmos HubATOM$4,102.40+ 3.4%

SafrochainSAF$2,410.001,250 SAF

What Zunia does

One wallet for
every Cosmos chain.

Zunia holds your keys on your own device and speaks IBC natively. Send between chains in one step, stake from the same screen, and connect to any Cosmos dApp from the extension or the phone. No custodian, no bridge accounts, no second wallet.

read the docs

262

Chains supported

from the Zunia chain registry, updated without an app release

4.2s

Median transfer

end to end across IBC, fee shown on both ends before signing

0

Keys held by us

generated and encrypted on your device, never on a server

How these numbers are measured

262 Chains supported: Mainnet entries in the Zunia chain registry, counted at build time: 218 Cosmos, 43 EVM and 1 Solana. Testnets and entries hidden in the wallet are excluded.
4.2s Median transfer: Median wall-clock time from signature to destination acknowledgement, measured on Cosmos Hub to Safrochain over channel-141 during internal testing.
0 Keys held by us: Zunia operates no key-custody service. The claim is checkable in the open source client, which contains no key export path to a Zunia endpoint.

Reviewed 2026-08-31. Figures are restated whenever the underlying measurement changes.

Chains

Chains Zunia already speaks

safrochain-1cosmoshub-4osmosis-1celestianeutron-1injective-1dydx-mainnet-1stride-1

juno-1akashnet-2noble-1axelar-dojo-1kaiyo-1phoenix-1pacific-1archway-1

262 chains today. 218 Cosmos chains, 43 EVM chains and 1 Solana chain. Chain metadata is read from the registry at runtime, so a new chain does not require an app release. Custom and testnet chains can be added by RPC endpoint.

Full chain list Chain registry on GitHub

IBC transfer

Route

cosmoshub-4safrochain-1

Channelchannel-141

Est. time~4.2s

Fees0.003 ATOM + 0.001 SAF

Channel, fees and route resolved before you sign.

Bridge

FROM COSMOS HUB1.200 ATOM

ATOM0.500

TO SAFROCHAINsafro1q9f…7k2d

SAF0.4982

relaying via IBC1 of 3 · ~10 min

Bridge fee0.0018 ATOM

Arrival~12 min

Review bridge

Capabilities

What you can do

On deviceHoldEvery balance across every chain in one list.

TransferIBC in one step, channel and fee resolved for you.

StakeDelegate, claim and redelegate from one screen.

ConnectAny Cosmos dApp, per-site permissions.

SecureLedger, Keystone and QR signing on mobile.

DashboardPortfolio, rewards and activity for every chain in one view.

Across devices

One key.
Three different jobs.

Pair once, by QR or with the same recovery phrase. The extension starts a transaction, the phone can confirm it, and the web dashboard is only allowed to look.

Platforms

Two clients.
The same keys.

Browser extension

Manifest V3

Signs where you work. Every transaction is decoded into plain language before you approve it, with the exact chain, fee and destination.

Chrome In store review
Brave In store review
Edge In store review
Firefox Planned

Minimum browser: Chrome 120 or Chromium equivalent
Permissions: Storage and active tab, per-site approval
Package: Reproducible build, checksum published per release

In store reviewSource

Mobile wallet

iOS and Android

The same accounts in your pocket, unlocked with Face ID or fingerprint. Scan a QR code to approve a desktop transaction without exporting anything.

App Store In store review
Google Play In store review
Direct APK Available

Minimum OS: iOS 15, Android 8.0
Unlock: Face ID, Touch ID, fingerprint or passcode
Air-gapped signing: QR approval, no key ever leaves the phone

In store reviewSource

Security

Self-custody that does not
ask you to trust us.

Keys are generated on your device and encrypted there. Zunia runs no server that can hold them, freeze an account or reverse a transfer. The client is open source, so the claim is checkable rather than promised.

Pair a device

Passcode or Face ID first, then a code that expires in 60 seconds. Keys stay on the device.

expires in 48 s

No account: No email, no sign-up, no profile to leak.
No analytics: No tracking scripts and no cookies on this site.
Self-hosted assets: Fonts and icons are served from our origin, so no third party sees your IP.
Your endpoints: Default RPC endpoints are listed in the docs and every one can be replaced.

How the key is kept

Key generation: On device, BIP39
Derivation: BIP44, coin type per chain
Storage: AES-256, OS keystore
Unlock: Passphrase or biometric
Hardware: Ledger Nano S Plus, Nano X, Stax, Keystone 3
Telemetry: None by default
Licence: Apache 2.0

Transparency

Check it.
Do not take our word.

Anything not finished is marked planned. The links are the ones we actually publish.

Found something? Write to [email protected], or read the disclosure policy. The machine-readable contact is security.txt.

Planned
Third-party audit
Scoped for the 1.0 release. Auditor, scope and full report published here, unredacted.
Available
Source code
Open
Extension, mobile app, SDK and chain registry, Apache 2.0.
Planned
Reproducible builds
Open
Build the extension from a tag and compare the checksum with the published store package.
Available
Responsible disclosure
Open
[email protected], 90-day coordinated window, acknowledgements page.
Planned
Bug bounty
Opens with the audited 1.0 build. Key extraction and unauthorised signing rank highest.

Verify

Check that you installed
the real Zunia.

A counterfeit wallet looks identical and behaves identically until it drains an account. These are the only identifiers we publish. If what you installed does not match one of them, uninstall it and start again from this page.

Zunia has no token, no airdrop and no presale. Any account offering one is impersonating us.
Support never sends the first message and never asks for a recovery phrase, a screenshot of one, or a remote session.
An extension that asks you to re-enter a recovery phrase after install is not Zunia.

Only official domain: zunialab.com
Web portfolio: Plannedwallet.zunialab.com
Documentation: Planneddocs.zunialab.com
Android package: com.zuniawallet.zunia_mobile
iOS bundle: com.zuniawallet.zuniaMobile
Firefox add-on id: Planned[email protected]
Chrome extension id: PlannedPublished with the store listing
APK SHA-256: PlannedPublished in each GitHub release, signed

Developers

One interface,
both platforms.

Zunia implements the standard Cosmos wallet interface, so an existing integration works unchanged. On mobile the same calls arrive over WalletConnect.

01Drop-in support for existing Cosmos dApps
02Amino and Direct signing, arbitrary messages
03Suggest a chain at runtime, testnets included
04WalletConnect v2 for the same calls on mobile

Integration guide Source on GitHub

connect.tsTypeScript

1// same call in the extension and over WalletConnect2const chainId = "safrochain-1";3 4await window.zunia.enable(chainId);5const signer = window.zunia.getOfflineSigner(chainId);6const [account] = await signer.getAccounts();7 8// account.address -> safro1x...4f9

extension popup · approve

app.osmosis.zoneverified domainosmosis-1

Approve 2 messages

1. MsgSwapExactAmountIn · pool 1441
Swap 50 OSMO for 172.4 SAF
2. MsgTransfer · channel-141
Send 172.4 SAF to safrochain-1

Network fee0.004 OSMO

SimulationNo errors

RejectApprove

wallet.zunialab.com · portfolio

Net worth

$12408.20

Claimable

$142.80

Avg APR

18.4%

Balance

ATOM612.40$4,102

SAF1,250.00$2,410

FAQ

Questions

No. The phrase is generated and encrypted on your device. There is no account, no email and no server-side key material, which also means recovery is your responsibility.

Support

Reach a human, not a group chat

These are the only channels we operate. We never open a conversation with you and we never ask for a recovery phrase.