rob thijssen
3db8b05032
keys/wormhole.rs derives the wormhole keys from the seed at the wormhole coin type (m/44'/189189189'/i'/0'/0'), pinned to what quantus-node's `key quantus --scheme wormhole` prints for the public dev phrase at index 0 and 1, and derives a miner's address from its published inner hash (bob's, as the observer shows it). The nullifier that spends a leaf is mirrored on the Poseidon core alone, pinned to four vectors produced once with the circuit crate, so the wallet does not carry the prover to know what it has spent. substrate/wormhole.rs reads ZkTree::LeafCount, scans ZkTree::Leaves in pages of 500 locally computed keys for leaves paying an address, and checks Wormhole::UsedNullifiers. Nothing on chain indexes leaves by recipient, so the scan runs once from zero and then only over what was appended; the SQLite cache keeps the leaves and the frontier under a ShieldedCache port. The wormhole_summary command derives the keys from the session's seed for the call, scans, marks spent leaves, and answers with the address, the inner hash and the shielded and received totals; the accounts page shows it with copy and rescan. A raw-seed wallet with no seed is told so rather than shown a fake address. Verified on mainnet through the public endpoint: a full scan of 107,127 leaves in 16 s found 31 leaves paying bob's wormhole address for 9.34 QTC, the observer's 30-reward attribution of 9.33 plus the one since; the dev phrase restored in the app shows qzq32vN2ZtX2T9YrvCh69CMvbC2nWmEq4tCjRWKg4CyuxeShg and inner hash 0x5a5891e7…, the node's own numbers, with the tree scanned to its end. doc/threat-model.md names the assets, the boundaries and the file behind each mitigation; its review by someone else is what closes #48. Closes #45 Refs #48 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014ftBXYuba8ARhQeF74oUgW
blackbeard wallet
A desktop wallet for post-quantum chains, Quantus first.
Linux, Windows and macOS; installable on Fedora with dnf.
Shape
The wallet is a Rust cargo workspace with a Tauri shell and a React webview. That split is the security model, not a convenience: every key, signature, decoded transaction and amount lives on the Rust side, and the webview only renders what a Tauri command hands it. Nothing that could serialise a secret is reachable from JavaScript.
crates/
wallet-entities/ domain types and the IPC wire protocol; exported to TypeScript
wallet-core/ wallet logic and the ports it is written against
wallet-data/ adapters behind those ports: keystore, cache, RPC, provider APIs
wallet-app/ the Tauri binary; commands are one-line shims into core
ui/ Vite + React + TypeScript webview
The ports in wallet-core are what make "any post-quantum chain" a profile
rather than a rewrite:
KeySchemeturns a seed and a path into a signer. ML-DSA-65 and ML-DSA-87 now; whatever the next chain uses later.ChainAdapterknows one chain: balances, building and submitting a transaction, watching it. The Substrate adapter is driven by runtime metadata plus a small per-chain profile (ss58 prefix, decimals, signature enum, transaction extensions, signing-context rule, coin type).SwapProvideris a swap venue. NEAR Intents first.FiatRampbuilds a provider session through a relay on our infrastructure, which holds the provider secrets, and opens it in the system browser.
The wallet is post-quantum only. Classical chains appear only as transit legs of a swap or ramp; the wallet never derives a secp256k1 or ed25519 key.
Why these choices
Quantus signs extrinsics with ML-DSA, hashes public keys with Poseidon2 for
the account id, and shields mining rewards behind a Plonky2 wormhole whose
prover is minutes of native CPU. All of that exists as Rust crates and nothing
else, so the core is Rust. Tauri is the house desktop convention
(~/git/architecture/generic.md §4) and the only shell that packages rpm, deb,
msi and dmg with a Rust-owned IPC boundary out of the box.
NEAR's post-quantum work (their MPC fork with threshold ML-DSA-87) is not yet able to sign a Quantus extrinsic, so the swap module is built and tested against chains NEAR Intents already lists, with Quantus as a registry entry that lights up when the bridge does.
Building
pnpm --dir ui install
cargo tauri dev --config crates/wallet-app/tauri.conf.json # from crates/wallet-app: cargo tauri dev
cargo test --workspace # also regenerates ui/src/api/generated
The CI gate is cargo fmt --check, cargo clippy -D warnings, cargo test,
and the webview's typecheck, lint and build. Run them before claiming done.
Work
Work is filed before it is done. Epics carry the epic label and an external
definition of done; their steps carry child, in dependency order, at
https://git.lair.cafe/blackbeard/wallet/issues. A commit that finishes a
child closes it (Closes #N); when an investigation contradicts an issue, the
correction is a comment on the issue, dated, not a surprise in a diff.