- ZETAPHY testnet is not real money. Do not put anything of value here.
- The seed is the only key to this wallet. Lose it or forget the passphrase and the funds are gone for good. Nobody can recover them.
- The seed stays in this browser only, encrypted with your passphrase, and is never sent anywhere.
If this page is opened over https, the RPC must be https too (browsers block http).
More settings
Its 0x… address on ZETAPHY (remembered in this browser), or for everyone in index.html's zetaphy-threat-registry meta tag. Empty = the meta tag.
Get started
Wallet locked
Use MetaMask (ZETAPHY Snap)
The ML-DSA-44 key is made inside MetaMask from your Secret Recovery Phrase; this page never sees it. MetaMask shows every transaction in plain words before it signs.
Until the snap is published and MetaMask has reviewed it, it installs only in MetaMask Flask (the developer build).
More settings
The account depends on the snap ID: the same snap always gives the same account (recoverable from the Secret Recovery Phrase), a local:… snap gives another one.
Your account
Both are the same account. It can receive funds at either.
The key is in MetaMask (ZETAPHY Snap), not in this page. Your MetaMask Secret Recovery Phrase is its backup.
Accounts this wallet controls
ECDSA accounts (e.g. MetaMask) quantum-locked to this wallet. Their own keys no longer work; this wallet sends, sends tokens and stakes for them (signed with ML-DSA-44, fees paid by this wallet).
Acting as
Send, token transfers and staking below act for this account (as_owner). Fees come from this wallet.
Send ZETAPHY
Confirm the transfer
- To
- Amount
- Max fee
- Total
Sent. tx hash:
ERC-20 tokens
Confirm the token transfer
- Token
- To
- Amount
- Max fee
Simulated on the node: it succeeds (it is simulated again just before signing).
Sent. tx hash:
The fee is paid in ZETAPHY. If the contract reverts, the whole tx fails and the fee is still paid, so this page simulates every transfer before signing.
Stake ZETAPHY
Confirm the stake
- Validator
- Amount
- Max fee
- Total
Unstaked ZETAPHY comes back after the chain's unbonding period. Until then it cannot be used and earns no rewards.
Sent. tx hash:
Deploy a contract
Confirm the contract creation
- Code size
- Code hash (keccak-256)
- Max fee
Simulated on the node: it succeeds (it is simulated again just before signing). Compare the code hash with the one the contract's author published. A contract creation has no destination, so it is not checked against the ThreatRegistry.
Sent. tx hash:
New contract address:
Lock a MetaMask account to this wallet
Hand control of an ECDSA account in MetaMask to this quantum-safe wallet. Its address, balance, tokens and stake stay where they are, but from now on only this wallet can move them.
- Permanent, no undo: after the lock the chain refuses every transaction that account's MetaMask key signs, and contracts no longer accept its signatures (e.g. permits).
- If you lose this wallet's seed, the locked account is lost too. Download the seed backup first.
- This wallet must have sent at least one transaction on chain (so the chain knows its ML-DSA-44 public key).
MetaMask sent the lock. tx hash:
Prepare for Q-day
Q-day is when the network stops trusting ECDSA signatures (MetaMask-style keys), because a quantum computer may forge them. From then on an ECDSA account that has not moved is frozen (its funds stay, but it cannot send). The safest way is to lock your MetaMask account to this wallet beforehand (the card above).
Consent to a flagged contract
With the threat gate on, the network does not deliver a transaction to a contract with an enforced Neuro flag unless the account itself consents (one transaction, at most a day). This is consent, not censorship: you can still go ahead, but read the flag's reason first.
Consent sent. tx hash:
Back up the seed
The backup file is the seed in plain form. Anyone who gets it can move the funds. Keep it offline and safe, and never share it.
The file works as ~/.zetaphy/pq.seed for the zetaphy pq native command.
Security
Change the passphrase
Unlock with fingerprint / Face ID (passkey)
Creates a passkey for this site on this device.
Passkeys may sync to your other devices.
Use ZETAPHY in other wallets
Add the ZETAPHY Testnet network to the wallet you already use (MetaMask, Rabby, Trust, OKX, Coinbase, Keplr, Leap, …) with the buttons below, or type the values in yourself. Everything comes from the RPC URL above.
EVM wallets in this browser
No EVM wallet found in this browser. Install an extension (MetaMask, Rabby, Trust, OKX, Coinbase Wallet, …), or on a phone open this page in your wallet app's browser.
WalletConnect (phone wallets when this page is open in another browser, e.g. Binance Wallet) is off: it needs a Reown projectId first.
Add the network by hand: the values to type in
- Network name
- RPC URL
- Chain ID
- Currency symbol
- Decimals
- Block explorer
https://explorer.sawasdeecoin.com
Cosmos wallets (Keplr, Leap, Cosmostation)
They show the zetaphy1… address of the same account as in an EVM wallet (eth_secp256k1 key, coin type 60). They need the node's https address, which serves /rpc and /rest (nodes set up with setup-node.sh do).
Which wallets work
- Work now (custom networks): MetaMask, Rabby, Trust, OKX, Coinbase Wallet, Brave, Rainbow, Zerion, Frame, and Ledger/Trezor through them. Keplr, Leap and Cosmostation with the buttons above.
- May work (not confirmed): Binance Wallet, inside the Binance app, if it accepts the network; outside the app it needs WalletConnect.
- Not until the wallet adds ZETAPHY itself: Phantom, and wallets with a fixed list of chains.
- Never: Solana-only or Bitcoin-only wallets. They are not EVM or Cosmos wallets.
- Quantum-safe: only this page's own ML-DSA-44 key and the ZETAPHY Snap. Every other wallet signs with ECDSA (secp256k1), which a large enough quantum computer can break; lock such an account to this wallet to protect it.
More settings
Free at cloud.reown.com. Set it here (remembered in this browser), or for everyone in index.html's zetaphy-walletconnect-project-id meta tag.