Social recovery
k-of-n guardians can rotate keys without the original. Default for reference wallet: 2-of-3.
§ Wallet · reference interface
Shielded by default,
disclosed by intent.
The reference wallet for Adamant — Apache 2.0, self-custodial, default-shielded. Native iOS, native Android, desktop reference. Every screen below reflects the intended UX of the production application.
prototype only · holds no real assets · pre-launch
◉ Shielded balance
specification
view key required for disclosure
○ Transparent balance
specification
visible on the public ledger
Adamant accounts default to OWNER_UPGRADEABLE, dual-signature (Ed25519 + ML-DSA), with 2-of-3 social recovery (WP §4.8). The wallet sets this up in the same number of taps as a legacy single-key wallet.
Send
Shielded Transparent
Recipient
adm1… (paste stealth address) · or scan QR
Amount
— ADM
Memo · encrypted
Optional. ChaCha20-Poly1305 + ML-KEM-768 envelope.
Mempool regime
Threshold (N≥15) · time-lock VDF (N<15) · auto
Receive stealth address + payment request
QR · stealth address
Payment request URI
adamant:adm1…?amount=10&memo=invoice%2342&label=Vendor
Stealth addresses are derived from a long-lived viewing key via ML-KEM-768. Each payment uses a fresh, one-time address; observers cannot link payments to the same recipient (WP §7.2).
§ 01 / Disclosure
View keys, not court orders.
Issue a scoped, revocable view key to a counterparty, tax authority, or auditor. They see what you choose to show — within a date range, an amount band, or a counterparty filter. They never gain spending authority. You can revoke at any time.
VK.01
Scope
Date range, amount range, counterparty filter, contract scope. The view key only reveals what its scope permits. WP §4.4.2.
VK.02
Authority
View only — no spending. Cannot move funds, cannot sign on your behalf, cannot derive the spending key. One-way trapdoor.
VK.03
Revocable
Each view key has an expiry and may be revoked at any time. Revocation is a single on-chain transaction.
Tx hash0x9f3a…c0a1
Block184 217
Fee0.0042 ADM
Sender▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Recipient▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Amount▒▒▒▒▒▒▒▒
Memo▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Issued view keys none · pre-launch
| Label | Scope | Issued | Expires | Status | Action |
|---|---|---|---|---|---|
| No view keys issued yet. | |||||
§ 02 / History
Transaction history.
Your view of your own activity. Labels and notes are stored locally and encrypted with your account key. Export CSV under any view-key scope you've issued.
All Sent Received Shielded Transparent Contracts
| Date | Direction | Counterparty | Amount | Label | Memo | Tx |
|---|---|---|---|---|---|---|
| No transactions yet — wallet is not connected to a live network. | ||||||
§ 03
Address book.
Contacts · stored locally
| Name | Address | Notes |
|---|---|---|
| No contacts yet. | ||
§ 04
Accounts & watch-only.
Wallets · select to switch
Personal · OWNER_UPGRADEABLE
Ed25519 + ML-DSA · 2-of-3 recovery
Cold · IMMUTABLE
Air-gapped device · ML-DSA only
§ 05 / Acquire
Burn-to-mint.
During the launch phase, the only way to acquire newly-minted ADM. Burn BTC, ETH, USDT, or USDC at a verifiably-unspendable source-chain address; the validator set verifies the proof and mints ADM at the fixed launch-phase rate.
Step 1 · select source asset
BTC
ETH
USDT
USDC
Step 2 · amount & destination
2 500 USD-eq → 50 000 ADM → adm1…
Step 3 · sign & broadcast burn on source chain
BTC 6 conf · ETH 32 epochs · USDT/USDC 64 conf
Per-address claim cap · WP §10.2.3
| Window | Cap · % of burn pool |
|---|---|
| Months 0–1 | 1% |
| Months 1–3 | 2% |
| Months 3–6 | 4% |
| Months 6–12 | 8% |
| Month 12+ | uncapped |
Burns are full-or-nothing: if a claim would push past the sub-counter or the cap, the claim reverts (and the source-chain transaction is rejected where possible).
Stablecoins: 1 USDT/USDC → 20 ADM, fixed. BTC/ETH: rate calibrated to USD-equivalent at protocol design time, constant through launch — not a live oracle.
§ 06 / Fees
Multi-dimensional fees.
Adamant prices compute, bandwidth, state, mempool, and disclosure separately. The wallet collapses them into a single ADM number you can review before signing — but the breakdown is always visible.
| Dimension | Unit | Estimated | What it pays for |
|---|---|---|---|
| Compute (F.01) | gas-eq | — | Verifier cycles + signature ops. |
| Bandwidth (F.02) | bytes | — | On-DAG bytes (ciphertext priced). |
| State (F.03) | slots | — | New shielded notes / transparent UTXOs. |
| Mempool (F.04) | regime | — | Threshold is cheaper than VDF. |
| Disclosure (F.05) | kB | — | Optional, paid only on view-key disclosure. |
Each transaction pays the sum across dimensions. Base fee is burned (EIP-1559-style) — sustained usage is deflationary against new issuance (WP §10.4).
§ 07 / Recovery
Recovery — your problem, our building blocks.
Adamant provides no protocol-level recovery (Principle I). The account model lets you build the right one for your threat model: social, time-locked, multi-device, inheritance, or hardware-secured.
Time-locked recovery
Recovery key gains rotation power after a delay (e.g. 7 days). You can cancel using your primary key.
Multi-device
2-of-3 across phone, laptop, hardware wallet. Loss of one device does not compromise the account.
Inheritance / dead-man's-switch
After a configurable inactivity period, beneficiary keys gain transaction authority. Any signed transaction resets the clock.
Hardware-attested
Recovery keys held in HSMs or secure elements. Validation logic accepts attestation evidence.
IMMUTABLE
No rotation, ever. Choose only with explicit informed consent — the protocol cannot help if you lose the key.
Wallet default: OWNER_UPGRADEABLE, dual-signature (Ed25519 + ML-DSA), 2-of-3 social recovery. Reference wallets SHOULD NOT default new users to single-key IMMUTABLE (WP §4.6.3).
§ 08 / Hardware
Hardware-wallet roadmap.
ML-DSA support is new on commercial hardware wallets. The reference wallet ships with software keys at launch; hardware integration follows.
| Brand | Model | Classical (Ed25519) | Post-quantum (ML-DSA) | Target |
|---|---|---|---|---|
| Ledger | Nano S+ / X / Stax | planned | planned (ML-DSA app) | mainnet + 6mo |
| Trezor | Safe 3 / Safe 5 | planned | planned | mainnet + 12mo |
| Open-source HW | reference design | spec | spec | open RFC |
§ 09 / Mobile
Phone-first by construction.
A phone can fully verify the chain via recursive proofs (Halo 2). The reference wallet runs as a Node Watcher tier client by default — your wallet checks the chain itself, without trusting a server.
iOS
App Store · TestFlight
Available at mainnet activation. TestFlight builds during public testnet.
badges render at launch
Android
Play Store · F-Droid · APK
Reproducible builds on F-Droid. APK + signing keys published in the reference-wallet repository.
badges render at launch