Block a user
a fedora rpm from a spec with vendored crates, published to a signed dnf repo on our infra
a release workflow: tag from the workspace version, bundle every target, publish artifacts
platform smoke: webkitgtk quirks on linux, and the same flows on windows and macos
history: what happened to each account, readable offline
pending reversible transfers, with a cancel that works until the block it executes
send: a review screen that shows what rust decoded, then sign and watch
accounts and receive: live balances, address, qr and checkphrase
onboarding: create a wallet, restore a phrase, or open a quantus-cli file
app shell: navigation, lock screen, network switcher and settings that persist
a dev node in ci for the chain adapter's integration tests
history from an indexer on our infra, through the relay
transfer: prepare, decode for review, sign, submit and watch, with a reversal window
balances, nonce and a new-heads subscription for every open account
rpc to our own nodes: endpoint list, tls, reconnect and a runtime-version watch
a subxt config for quantus, lifted from quantus-cli, with offline signing
chain profiles: quantus mainnet, heisenberg and dev as data, not code
an unlock session: password in, signatures out, auto-lock, nothing else
mnemonic lifecycle: generate, import, verify the backup, show the checkphrase
read and write the quantus-cli keystore file format
ml-dsa key schemes: derive at a bip44 path, sign under a context, address by poseidon2