Atho: A Post-Quantum Proof-of-Work Payment Network for the Quantum Age

Atho.io

Atho: A Post-Quantum-Aware Proof-of-Work Payment Network

Ticker: ATHO
Consensus: Proof of Work
PoW Hash: SHA3-384
Transaction Signatures: Falcon-512
Model: Public UTXO payment chain
Implementation: Rust-first
Block Target: 100 seconds
Decimals: 8
Smallest Unit: atom, where 1 ATHO = 100,000,000 atoms
Starting Subsidy: 20 ATHO
Halving Interval: 1,250,000 blocks
Tail Reward: 0.3125 ATHO per block from Era 7
Hard Max Supply: None under the current soft-cap tail model
Introduction

Atho is a payment-focused Layer 1 Proof-of-Work blockchain designed around long-term verification, simple ownership rules, and post-quantum-aware transaction authorization. The goal of Atho is not to become a general-purpose smart-contract platform or to copy every feature from existing chains. The goal is narrower and more conservative: build a public UTXO payment network that users, miners, node operators, wallet developers, and future exchanges can understand, verify, and operate without unnecessary complexity.

Atho uses SHA3-384 for Proof-of-Work and hashing commitments. Transactions are authorized with Falcon-512 signatures. This means Atho does not rely on the same elliptic-curve signature assumptions used by many older cryptocurrency systems. This is not a claim that any existing chain is broken today, and it is not a claim of permanent immunity to all possible future cryptographic threats. It is a design choice intended to reduce long-term dependence on classical elliptic-curve transaction authorization.

Atho is built as a public UTXO chain. Every coin exists as an unspent transaction output. Transactions consume existing UTXOs and create new UTXOs. Full nodes validate ownership, signatures, fees, output values, block structure, and proof-of-work. Wallets build and sign transactions locally, but wallets do not define consensus truth. The node remains the final authority for validation.

Why Atho Exists

Many blockchain systems have become large execution environments with complex state, bridges, wrapped assets, VM surfaces, and many moving parts that are difficult for ordinary users to audit. Atho takes a simpler path. It is designed as digital payment infrastructure first.

The main design goals are:

Atho’s strongest traits are not maximal complexity. They are explicitness, deterministic validation, and operator-readable rules.

Core Technical Design

Atho is organized around a Rust implementation with separate responsibilities for protocol types, consensus validation, storage, peer networking, wallet logic, API surfaces, mining, and desktop-client interaction.

The basic lifecycle is straightforward:

accepted blocks update the UTXO set and indexed state

This separation matters. Wallet code should not override consensus. Explorer output should not define spendability. Mining code should not bypass validation. Every accepted block and transaction should be independently verifiable by a normal full node.

Consensus and Network Parameters

Current Atho parameters:

max raw serialized block size: 24 MB

The emission model uses a 50M-style early distribution followed by a permanent low tail reward. The purpose of the tail is to provide a long-term miner security floor and payment-network liquidity instead of relying only on transaction fees in the distant future.

Post-Quantum-Aware Authorization

Atho uses Falcon-512 for transaction authorization. Public keys, signatures, and witness data are validated under strict rules. A node does not trust the wallet’s claim about what was signed. Instead, the node rebuilds the canonical signing digest locally and verifies the Falcon signature against the transaction and UTXO being spent.

This protects against malformed signatures, wrong-message signatures, missing witness data, ownership mismatches, wrong-network usage, and replay-style confusion between networks.

Atho also uses SHA3-384 for mining and hashing commitments. SHA3-384 gives the network a modern sponge-based hash function with a 384-bit digest for Proof-of-Work and consensus-facing commitments.

UTXO Model and Transaction Validation

Atho uses a public UTXO model. Each transaction spends previous outputs and creates new outputs. The chain validates that:

Atho uses a canonical ownership model. Outputs lock to a canonical 32-byte payment digest. Visible Base56 addresses are user-facing encodings of that ownership digest with network-specific prefixes and checksums. The address string helps users and software avoid mistakes, but consensus validates the canonical underlying lock.

Block Structure and Mining

Atho blocks contain a canonical header and transaction list. A valid block must satisfy proof-of-work, but proof-of-work alone is not enough. The block must also satisfy transaction structure, UTXO validity, coinbase rules, duplicate-spend checks, size limits, commitment roots, and monetary correctness.

Mining is designed to stay inside the same validation system as the rest of the node. A miner should not create a private shortcut around the rules. Candidate blocks must contain valid transactions, correct coinbase value, correct commitments, and valid proof-of-work. Solved blocks are returned to the node and re-enter full validation before becoming accepted chain state.

Mainnet and testnet mining require an explicit same-network reward address. This prevents mining to a silent default address or accidentally using a wrong-network reward target.

Wallet Design

Atho wallets are designed to keep keys local. The wallet derives addresses, scans for wallet-owned outputs, builds transactions, creates change, signs with Falcon-512, and submits signed transactions to the node. The node validates and relays. The wallet does not become consensus authority.

Atho wallets use separate receive and change paths. This makes fresh addresses cheap and helps avoid unnecessary address reuse. The wallet can generate new receive addresses, track used and unused addresses, create change outputs, and support wallet-level privacy controls.

The goal is simple: make better behavior the default. Users should not have to reuse one public address forever. Users should not have to expose their whole wallet history every time they send a payment.

Wallet-Level Privacy and Coin Control

Atho is a transparent UTXO chain. This is important to state clearly. Atho does not currently hide amounts, hide receivers, hide txids, hide inputs, or implement shielded notes. The chain is public.

Atho’s privacy work is wallet-level privacy and linkability reduction. That means the wallet helps users avoid unnecessary links, but it does not claim full anonymity.

The wallet privacy tools include:

privacy warnings before signing

This matters because many privacy failures on transparent chains happen by accident. A wallet may silently combine mining rewards, exchange withdrawals, personal funds, business funds, and change outputs into one transaction. Once those coins are spent together, the chain can link them.

Atho’s wallet is being designed to stop that kind of careless merging.

Advanced Coin Control

Advanced coin control gives the user direct control over individual coins. Instead of only seeing one wallet balance, the user can inspect UTXOs and decide what should be spent.

The advanced wallet controls include:

privacy warnings before signing

The purpose is not to hide the chain. The purpose is to give users control over what they reveal. If a user wants to spend only one prepared coin, the wallet should not silently add unrelated coins. If a user wants to keep mining rewards separate from personal funds, the wallet should warn before merging them. If a user wants to avoid change, the wallet should help search for exact-match coins.

Prepared Coins, Split Outputs, and Change Control

Atho also supports transaction-shape controls. Users can split funds into multiple outputs, choose fresh change, split change, and prepare future spend pieces.

In advanced mode, users should be able to decide:

which outputs should be labeled or protected from merging later

This is useful because one large UTXO can expose more balance than necessary. If a user has one 1,000 ATHO coin and wants to make many smaller future payments, spending from that single large coin repeatedly may create obvious change and reveal wallet structure. Prepared outputs allow the user to create cleaner future spend pieces.

This is not a mixer. Split outputs are still born in the same transaction and can be analyzed as siblings. But it gives users better future spending control and reduces avoidable balance exposure.

Monetary Policy

Atho uses deterministic height-based issuance.

The current schedule starts at 20 ATHO per block and halves every 1,250,000 blocks. At the 100-second target cadence, each halving era lasts about 3.96 years. After six halving eras, Atho enters a permanent Era 7 tail reward of 0.3125 ATHO per block.

The supply near tail start is about 49.2 million ATHO. After tail begins, new issuance continues at about 98,550 ATHO per year at target cadence.

This means Atho does not have a hard maximum supply under the current model. Instead, it has a low permanent tail designed to support miner incentives and long-term security. At tail start, the annualized supply expansion is about 0.20%, and that percentage slowly declines as total supply grows.

Why No Hard Max?

A hard cap is simple to market, but a Proof-of-Work network still needs long-term security. If block rewards eventually disappear, the network must rely only on transaction fees. That may work for some networks, but it can also create uncertainty for miners and future security budgets.

Atho’s soft-cap tail takes a different approach. The tail is small, predictable, transparent, and locally verifiable. It gives miners a permanent base reward while keeping long-term inflation very low.

Storage, Explorer, and API Design

Atho uses a storage model that separates raw block archives from indexed chainstate data. Raw accepted block bytes are stored in flat files, while indexed state such as UTXOs, block metadata, transaction archives, peers, and wallet-related data can be stored in LMDB-backed structures.

Explorers and APIs are presentation layers over validated node data. They do not define consensus. They display validated blocks, transactions, addresses, supply behavior, and network health, but full nodes remain the authority.

For exchanges and services, Atho should provide typed RPC/API responses for:

reorg handling

Security Philosophy

Atho’s security model is based on:

encrypted wallet persistence

Atho should be described honestly. It is not “quantum-proof forever.” It is a payment-focused Proof-of-Work chain that uses a post-quantum-aware transaction signature scheme and modern hashing to reduce long-term dependence on older signature assumptions.

Current Status

Atho is active software under development. The project is moving toward a stable public network release with focus on node stability, wallet usability, mining flow, explorer support, public documentation, and launch readiness.

Before mainnet, the most important tasks are:

public security disclosure process

Conclusion

Atho is being built as a conservative, payment-focused Proof-of-Work network for long-term settlement. It combines SHA3-384 mining, Falcon-512 transaction authorization, public UTXO accounting, Base56 addresses, deterministic full-node validation, explicit monetary rules, and wallet-level coin control.

The goal is not to be the most complex chain. The goal is to be understandable, verifiable, mineable, and practical.

Atho’s position is simple:

Atho is still early, and feedback from miners, developers, wallet users, node operators, and exchange integrators is welcome.

Disclaimer: Atho is experimental software under active development. Nothing in this post should be treated as financial advice. Users should verify code, run their own nodes where possible, back up wallets safely, and understand that public UTXO chains expose transaction graph data.