Wallet custody and staking designed for long-run network safety.
Atho wallet security uses encrypted-at-rest lockbox controls with Argon2id, AES-256-GCM payload encryption,
and mandatory Kyber DEK wrap. Wallet staking remains deterministic and auditable: payouts are weighted by
each address share of total active stake in the settled epoch.
Settlement windowsDeterministic 720-block epoch plus 3600-block finalization buffer.
Wallet Addressing + Fees
How Base56 addresses and fee-per-byte policy work in Atho wallets.
Wallet addresses are generated from Falcon public-key material through deterministic SHA3-384 pathways, then
encoded in Base56 for human use. Fee policy is calculated by vsize with a floor of
500 atoms/vB and minimum transaction fee 200,000 atoms.
Deterministic Address Pipeline
One key source, multiple role-safe addresses. Domain-separated hashes prevent regular, bond, and stake
destination mix-ups.
Role domainsATHO_ADDR_V1, ATHO_BOND_V1, ATHO_STAKE_V1.
Base56 Format (Human-Safe Encoding)
Base56 avoids ambiguous symbols to reduce copy/read mistakes in wallets, terminals, and printed records.
Base56 character set (excerpt)23456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnpqrstuvwxyz
Mainnet:A regular, B bond, S stakeTestnet/Regnet:T regular, D bond, E stake
Role-Separated Base56 UX
Fee-Per-Byte Policy in Wallet Send Flow
Wallet send estimation uses virtual size (vsize) policy. Current floor is
500 atoms/vB with minimum tx fee 200,000 atoms and dust limit
20,000 atoms.
Policy Floor500 atoms/vB
Minimum Tx Fee200,000 atoms
required_fee_atoms = max(500 * vsize, 200000)
Address Protection and Key Isolation
Role addresses are deterministic and domain-separated from the same Falcon pubkey source bytes, so regular,
bond, and stake pathways cannot be confused or replayed across roles.
Role derivation domainsATHO_ADDR_V1, ATHO_BOND_V1, and ATHO_STAKE_V1 each hash to separate addresses.
Plaintext vs encrypted fieldsDisplay identifiers and Base56 addresses stay visible; raw keys, mnemonic material, and private components remain encrypted while locked.
Fail-closed lock policySensitive wallet operations refuse to run while lockbox is encrypted and locked.
Atomic + backup-safe writesKey file writes are lock-protected and backup-on-write to reduce corruption risk.
Visible While Lockedidentifiernetwork / rolehashed public keyBase56 address
Kyber does not replace AES; it wraps the same DEK used by AES payload encryption. This keeps fast encrypted
payload handling plus a post-quantum recovery/control plane.
1) Generate random DEK
2) Encrypt wallet payload with AES-256-GCM(DEK)
3) Wrap DEK with Argon2id-derived KEK
4) Wrap same DEK with Kyber metadata/ciphertext
5) Persist lockbox metadata + encrypted payload
Private Transaction UX in Wallet Nodes
Wallet nodes orchestrate private transaction assembly: sender authentication, note selection, deterministic witness context,
recipient bundle parsing, and payload encryption before any transaction reaches mempool.
Public -> private fundingSpend public UTXOs and produce private commitments with recipient-bound encrypted note payloads.
Private -> private transferConsume private notes via nullifiers and create fresh commitments while preserving spend privacy.
Private -> public releaseSpend private notes and emit public UTXO outputs when transparent settlement is needed.
Reusable receive bundlesWallets can expose reusable bundle data for receive UX while private-note derivation remains unlinkable through deterministic counters.
QR and copy workflowsReceive views support QR payload sharing and direct address/bundle copy for low-friction transaction initiation.
X-address integrity checksValidation logic enforces x-address hash consistency with bundle material before accepting private payloads.
Password-gated private sendsSensitive private send operations require unlocked wallet auth policy on each send path.
Bundle Reuse UXDeterministic Note KeysEncrypted PayloadX-Address Hash Match
Wallet Staking Mechanics
Staking rewards are weighted by active stake share, not fixed equally.
Wallet staking is separate from mining rights. Rewards are settled from the stake-side bucket and distributed
by proportional active share in each settled epoch.
Staking Lifecycle
Stake transitions follow deterministic state rules: pending -> active -> exiting -> unlockable -> withdrawn.
PendingActiveExitingUnlockableWithdrawn
Epoch accounting720-block epoch with 3600-block finalization buffer.
Role separationStaking accrues economic rewards only; block production still requires PoW + active bond.
Stake Pool Weighting Visual
Example from reward docs: if epoch stake pool is 900 ATHO, payout follows each staker's active share.
Bigger active share = bigger payoutRewards scale linearly with your active stake percentage in the settled epoch.
No hidden manual overridesPool split and weighting rules are deterministic consensus/accounting pathways.
AuditabilityReward constants, split math, and epoch windows are documented across Whitepaper, Consensus, and Rewards docs.
Current staking bounds20 ATHO minimum, 500 ATHO max per address, 25,000 ATHO max new stake per rolling 30 days, and 25,000,000 ATHO max total staked network-wide.
Wallet creation defaults to mnemonic-backed deterministic keys with 24 words. Creation flow
supports 12, 24, or 48 words, and recovery can import the same
mnemonic path later.
12 Words24 Words (Default)48 Words
Creation optionsGenerate new mnemonic wallet, recover from existing mnemonic, or import an existing Falcon key export.
Passphrase handlingMnemonic passphrases are never stored in key JSON or export files; keep passphrases separately.
Recovery + Lockbox Flow
After import or recovery, lockbox controls apply the same encrypted-at-rest policy and unlock controls used
for daily wallet operations.
Create / RecoverVerify Address + HPKEncrypt LockboxUnlock to Sign
Mobile Wallet (App Store + Google Play) is in progress.
Mobile clients are being prepared with the same custody posture: encrypted lockbox pathways, deterministic
role-address handling, and transparent staking controls. Release will prioritize security review, predictable
backup flows, and clear recovery UX before public launch.