chain 9693 · PoQu devnetChrome extension (MV3)

The post-quantum wallet for PoQu.

Every transaction you sign uses ML-DSA-44 (FIPS 204, Dilithium-class) — the PoQu chain's native signature scheme — not ECDSA. Keys are generated and kept inside the extension's background worker and never leave your machine.

⬇ Download poqu Wallet

…

Install in one minute

Why "Load unpacked"? The wallet ships as a signed-source zip during the devnet phase — it is not on the Chrome Web Store yet. Unpacked extensions run exactly like store ones; Chrome just shows a developer-mode banner.

Download & unzipGrab the zip above and unzip it — you get a poqu-wallet-extension/ folder. Keep the folder where it is (Chrome loads it from disk).

Open Chrome extensionsGo to chrome://extensions (works in Chrome, Brave, Edge, Arc).

Enable Developer modeToggle Developer mode in the top-right corner.

Load unpackedClick Load unpacked and select the unzipped poqu-wallet-extension folder. The poqu icon appears in the toolbar — pin it.

Create your walletOpen the extension, set a password, and write down the recovery phrase (PQ-HD v1 — it deterministically derives your ML-DSA-44 keys). It is the only backup; nobody can restore it for you.

Get started on the devnet

Fund your addressCopy your 0x… address and request devnet funds at the faucet — 10,000 POQU per address per 24 h.

Try the appsSwap on the DEX, mint on the NFT marketplace, or launch a token on the launchpad — every site detects the wallet automatically (EIP-6963) via its Connect wallet button.

Watch it on-chainEvery confirmed transaction links to the explorer; the /pq/tx view shows your raw ML-DSA-44 public key and 2,420-byte signature.

What's inside

🛡️

ML-DSA-44 signatures (FIPS 204)

Transactions are PoQu's type 0x50, signed with a NIST-standardized lattice scheme. No ECDSA anywhere in the signing path — resistant to harvest-now-decrypt-later quantum attacks.

🔑

Keys never leave the background

Key material lives only in the extension's background service worker, encrypted at rest with Argon2id + AES-GCM. Pages and dApps only ever see addresses and signatures.

🧮

Rust → WASM signer

The FIPS 204 implementation is compiled from Rust to WebAssembly and runs locally. Recovery phrase → keys via PQ-HD v1 (HKDF-SHA3-256) — restore on any machine.

🔌

Standard dApp connect

EIP-1193 provider + EIP-6963 multi-wallet discovery. Any PoQu dApp's "Connect wallet" finds it; approvals show exactly what you're signing.

🪙

Tokens & NFTs built in

ERC-20 balances from the public token list, plus an NFT tab that auto-discovers your ERC-721s (Enumerable or Transfer-log scan with ownership checks).

🚦

Client-side tx safety

Malformed dApp requests (bad hex, absurd gas, wrong chain) are rejected in the wallet before anything reaches the network — verified by a 48-check harness against the live devnet.

Good to know

Which networks does it support?

PoQu only (chain id 9693, 0x25dd). Default RPC is https://rpc.poqu.org; a localhost devnet entry is included for node operators. Requests to switch to any other chain are refused by design.

What does my address look like?

A normal 0x… EVM address — keccak256(ML-DSA-44 pubkey)[12:] with EIP-55 checksum. The same account appears as poqu1… (bech32) in CLI/staking tools; both encode identical bytes.

Is this audited / mainnet-ready?

This is devnet software. The chain and contracts went through internal AuditForge engine runs (report in the repo), but there has been no independent audit yet. Don't put real value on it.

MetaMask can't do this?

No — standard wallets sign with secp256k1 ECDSA. PoQu nodes only accept ML-DSA-44 (0x50) transactions, so a PQ-aware wallet is required; that's this one.

Download

Latest	poqu Wallet v0.2.0 · Chrome / Brave / Edge (Manifest V3), unpacked
File	poqu-wallet-latest.zip
SHA-256	—
Verify	shasum -a 256 poqu-wallet-*.zip # must match the line above
Source	Built from the PoQu monorepo (`wallet/`: extension + Rust signer + test harness). Repo publication coming with the devnet docs.

Only download from wallet.poqu.org. The team will never DM you a wallet file, ask for your recovery phrase, or "validate" your wallet. Anyone who does is scamming you.