BTC
Bitcoin
Mainnet, Testnet3 and Signet. Every modern address family — legacy P2PKH (1…), P2SH-wrapped SegWit (3…), native SegWit (bc1q…) and Taproot (bc1p…) — all four sign and broadcast, picked per-wallet in Settings.
The multi-chain wallet built into the browser you're already using.
Download Theseus Already using it? Aegis is in the toolbar.
Aegis is the wallet that ships inside Theseus Navigator — one seed vault, many chains. Day-one support for Bitcoin (mainnet + testnet3), Bitcoin Cash (mainnet + Chipnet), Tron (mainnet + Nile), Ethereum (mainnet + Sepolia), Solana (mainnet-beta + Devnet), Siacoin and DigiByte, with more chains queued behind a chain-adapter interface. Not an extension, not a downloadable app, not a bridge to a server: it lives in the browser process and signs transactions where your keys already are.
The name comes from the shield of Athena, gifted to Perseus and later to the heroes she chose to protect. In this project, the shield is your private keys — and the browser holds it.
It is in Theseus now. The toolbar button opens a sidebar panel — balance, send, receive and transaction history across every chain you have enabled — or a full window when you want the room. All self-hosted, all offline-first. Updates arrive over a signed channel: Aegis checks for them on its own and the browser does not need reinstalling.
One seed, derived per BIP-32 into every chain's native address space. Add or remove chains anytime; the vault stays the same.
Mainnet, Testnet3 and Signet. Every modern address family — legacy P2PKH (1…), P2SH-wrapped SegWit (3…), native SegWit (bc1q…) and Taproot (bc1p…) — all four sign and broadcast, picked per-wallet in Settings.
Mainnet and Chipnet testnet. Native bitcoincash: addresses; BNS names as recipients. Dapps on .x sites sign through window.bitcoincash.
Mainnet and Nile testnet. TronLink-compatible bridge: window.tronWeb and window.tronLink on any https page, with per-origin consent.
Mainnet and Sepolia built-in — every other EVM (Base, Arbitrum, Optimism, Polygon, BSC, anything with a chain id) lands via the standard wallet_addEthereumChain flow. EIP-1559 sends, EIP-712 typed-data, EIP-6963 discovery. MetaMask's derivation, so any seed round-trips.
Mainnet-beta and Devnet. Phantom's default SLIP-0010 derivation, so the seed round-trips. Native SOL and SPL tokens — USDC, USDT, Token-2022, anything with a mint. TransferChecked with auto-created recipient ATAs. Dapps see Aegis at window.solana with the full wallet-adapter surface, including multi-signer flows.
v2 walletd-backed — native to the storage layer we already use. Bring your own walletd node (public or self-hosted); the URL stays on your machine.
Native SegWit (dgb1q…), Taproot (dgb1p…), Wrapped SegWit (S…) and legacy P2PKH (D…) — pick the family, get the right addresses. Shares code with the SilentCode DigiByte web-wallet.
Every wallet is a sub-account of your Theseus password vault — same seed, derived per chain via HKDF. Testnet wallets get a small TEST tag next to the network name so a Testnet3 / Signet / Chipnet / Nile / Sepolia / Devnet balance can't be mistaken for real money.
A seed and a send box is the easy half. The rest is what a wallet owes you when something goes wrong — or when one device should not be enough on its own.
An m-of-n wallet needs signatures from several devices, so the transaction has to travel. Aegis delivers it: the second device is told a signature is wanted instead of waiting to be asked. No pairing step, no server, and the relay carries it without being able to read it. The protocol is published with a test vector so other wallets can implement it.
A covenant that lets the everyday key spend small amounts alone and asks a second device for anything larger — the shape an app or a game wallet actually wants, and one a plain multisig cannot express. The rule is in the script, not in an app asking itself nicely.
A balance is a pile of coins, and each one costs about 149 sat to spend whatever it holds. Aegis says when combining them is worth it and when it is not — the sums are written out, including the case where the honest answer is to leave the dust alone.
Token outputs are never picked up by an ordinary send. Spending one without carrying its token data forward destroys the category, and there is no undo — so they are excluded from coin selection entirely and counted separately from the spendable balance.
The wallet is designed to grow one chain-adapter file at a time. This one is queued next:
Stealth addresses and ring signatures, so an address cannot be watched the way the chains above can. Subaddresses per payment, and a view-key mode that reads the balance without being able to spend it.
Keys never leave the browser process. No server holds a copy, no operator has a recovery back-door. You are the only party who can sign.
Aegis is part of Theseus. If you have the browser, you have the wallet — the same UI, the same trust boundary.
Every chain gets its own native address family and asset scheme — cashaddr on BCH, base58 on Tron, unlock-hash on Siacoin, bech32 on DigiByte. Token-level extensions (CashTokens, TRC-20, ERC-20 once EVM lands) plug into the same per-chain adapter. No wrapped tokens, no bridges, no separate wallets per ecosystem.
Send to friend.bch or alice.eth instead of a 42-character address. The browser already resolves the chain — the wallet uses the same resolver.
dApps ask Aegis to sign via CashConnect-style flows. You see the exact tx before it signs — no blind approval, no phishing overlays.
Reads balances through the same electrum / RPC pool Theseus uses for BNS. If Theseus is online, Aegis is online — no separate infrastructure per chain.
A multisig wallet is several keys and a threshold: any two of three can send, and losing one device loses nothing. A guarded wallet keeps one key in charge but caps what it can move alone — small payments go through, anything larger needs your second device to agree, and it is the chain that enforces the limit rather than Aegis asking itself nicely. Neither is a phishable code; both are signatures this process cannot produce on its own. How they work.
The browser is the trust surface where every dApp interaction already happens. Putting the wallet outside that surface — in an extension, a mobile app, a separate window — introduces a boundary every attacker wants to exploit.
No separate download and no extension to approve. Aegis is in the toolbar from the first launch, and updates itself over a signed channel.
Download Theseus