Built like a wallet. Acts like a vault.
A browser wallet for private, instant payments. No one sees your balance. Not even us.
Two steps. That's it.
Install
Add Fire Wallet to Chrome. No account, no email, no KYC.
Send
Enter an address or scan a QR. Payment confirms in under 5 seconds.
Every transaction is private by default. No one sees your balance, your history, or your identity.
See the difference.
| Fire Wallet | MetaMask / Rabby | Phantom | |
|---|---|---|---|
| Private transactions | Default | Never | Never |
| Settlement time | ~3 seconds | ~12 seconds | ~400ms |
| Transaction fees | ~$0.001 | $1–$50+ | < $0.01 |
| Balance visible to others | Never | Always | Always |
| Data collected | None | IP, usage, balances | IP, usage, balances |
Sources: [1] [2] [3] [4] [5] [6]
Fire Wallet
- Private transactions
- Default
- Settlement time
- ~3 seconds
- Transaction fees
- ~$0.001
- Balance visible
- Never
- Data collected
- None
MetaMask / Rabby
- Private transactions
- Never
- Settlement time
- ~12 seconds
- Transaction fees
- $1–$50+
- Balance visible
- Always
- Data collected
- IP, usage, balances
Phantom
- Private transactions
- Never
- Settlement time
- ~400ms
- Transaction fees
- < $0.01
- Balance visible
- Always
- Data collected
- IP, usage, balances
Accept private payments.
Four ways to start accepting Fire payments today.
Fire Pay
Drop a payment button or gated content into any WordPress site. One plugin, one shortcode.
Fire Shop
Full eCommerce for WordPress. Products, carts, checkout.
WooFire
WooCommerce payment gateway. Drop it into your existing store.
Shopify
Accept private payments on the world's largest commerce platform.
No SDK. No API key. No backend.
Accept payments from any website with a single postMessage call.
// One call. No SDK. No API key.
window.postMessage({
type: 'KYOTO_PAYMENT_REQUEST',
recipientB58: recipientAddress,
amount: amountInPicoMOB,
memo: 'Coffee order #1234',
merchantRef: 'order-1234'
}, '*');Four layers. Zero secrets on device.
Private keys never exist on your machine. Every transaction is gated by biometric proof.
Extension isolation
Popup has zero key access. XSS cannot reach secrets. The attack surface is the Chrome extension sandbox itself.
Threshold recovery
2-of-3 Juicebox realms with independent HSMs. No single point of failure. No seed phrase to lose.
WASM-only keys
Private keys never cross the JS/WASM boundary. Ring signatures, bulletproofs, and Ristretto curve ops run in Rust.
Biometric signing
Touch ID and Face ID gate every transaction. WebAuthn key derivation through the secure enclave.
The stack.
React 18
The wallet UI is a 400x600px Chrome extension popup. React with Zustand gives us a state model simple enough to audit in an afternoon. Every screen, every state transition, one render tree.
Rust / WASM
Private keys never touch JavaScript. 5,624 lines of Rust compile to WebAssembly — ring signatures, bulletproofs, Ristretto curve operations. The cryptographic boundary is the language boundary.
gRPC-Web
Fog relay, consensus validation, and encrypted transaction submission run through a gRPC-Web proxy. The wallet talks to MobileCoin's network without exposing endpoints to the browser.
Fly.io
The market maker, swap engine, and proxy infrastructure run as Docker containers on Fly.io. Structured logging. Geographic distribution. The backend Fire's users never see.