Aegis · AEG — Mainnet since 16 Sep 2026

A coin you can mine, hold, and verify for yourself.

Aegis is a mineable coin with post-quantum consensus signatures, an experimental shielded layer and a built-in program layer; contracts you deploy yourself are not available yet. Supply is capped at 100,000,000 AEG, and the live figures on this page are read from the node that serves it.

Experimental software. The code has not been independently audited.

01Design

Built on four ideas.

A short list of design decisions, stated plainly, including where the design is still a goal and not yet a guarantee.

Network
Mainnet, genesis 16 Sep 2026
Consensus
Proof-of-work (SHA-3) with proof-of-stake finality
Block time
60 seconds (target)
Supply cap
100,000,000 AEG
Signatures
ML-DSA-65 (FIPS 204) for consensus
Contracts
Account-based, built-in programs only, not EVM
Node
Rust, peer-to-peer on TCP 9100

Post-quantum signatures

Validator attestations and the mint authority are signed with ML-DSA-65 (NIST FIPS 204), and the proofs are hash-based STARKs. Addresses, commitments and note delivery are still classical (Ristretto255) and would need a migration. The optional encrypted P2P transport uses Kyber-768, not the final ML-KEM.

ML-DSA-65STARKRistretto255

Shielded notesExperimental

Payments are Pedersen commitments in a Rescue-Merkle note tree, and the note itself travels to the recipient encrypted, through a relay that stores it. Mint and stake amounts and miner addresses are public. The layer is experimental and not yet audited: its privacy and security properties are goals of the design, not guarantees.

note treestealth ECDH

Mined, then finalized

Blocks come from proof-of-work, about one a minute. Validators sign attestations on the blocks they see, and a block that is 64 blocks deep and carries a 2/3+1 stake-weighted quorum is marked final. Anyone can produce blocks; only staked validators finalize them.

SHA-3 proof-of-workstake-weighted attestations64-block finality

Built-in programs

An account-based layer, with programs, accounts and instructions, executes inside consensus and is verified by the same nodes that validate blocks. Today it runs only the programs that ship inside the node: a system program, a counter and a simple balance-transfer program. You cannot deploy your own code yet, and there are no user-issued tokens. Deployable contracts are planned, not available. An EVM layer exists only as an optional command-line demo, outside consensus.

loop-contracts

02Privacy

How a payment moves, and what the chain gets to see.

  1. Step 1

    Build

    The sender’s wallet creates a note for a fresh one-time address, derived from the recipient’s view key and a random nonce, plus a STARK proof that value is conserved.

  2. Step 2

    Publish

    The transaction goes on-chain: new note commitments, a nullifier for the note that was spent, the proof and a fee. Consensus checks the proof.

  3. Step 3

    Deliver

    The note itself, with its amount and secret material, is encrypted to the recipient’s view key and handed to a relay. The relay stores and forwards it and does not have the key.

  4. Step 4

    Receive

    The recipient’s wallet fetches the ciphertext and decrypts it with its view key. The note is now in that wallet.

Schematic · the note tree

What the chain actually stores

Each payment adds new note commitments to a Merkle tree and publishes a nullifier for the note that was spent. A nullifier is designed not to reveal which commitment it belongs to. The drawing is schematic; the pulse marks a new block reported by the node.

Note commitments
—
Nullifiers
—
Transactions
—

Public on the chain

  • Blocks, transactions and their hashes
  • Miner addresses, and mint and stake amounts
  • Note commitments, nullifiers and STARK proofs
  • The validator set and its attestations

Designed to stay off the chain

  • The contents of a noteAmount and secret material travel encrypted to the recipient.
  • Which wallet a one-time address belongs toPayments to the same recipient use different addresses. This reduces linkability; it is not a proof of unlinkability.

Known limitsThe STARK proof is not zero-knowledge.Note encryption is classical, not post-quantum.You cannot deploy your own contracts yet.None of this has been independently audited. These are design goals, not guarantees.

03Supply

A cap, a vesting pre-mine, and the rest mined.

Where supply stands

Capped at 100,000,000 AEG by the emission schedule in the code. The figures below are read from the node.

Unclaimed pre-mine
2,000,000AEG
Circulating
—AEG
Burned to date
—AEG
Cap
100,000,000AEG

The pre-mine vests on a schedule

2,000,000 AEG sit in vesting accounts. Nothing can be claimed before a one-year cliff; after that it is released linearly over nine more years. The schedule below is read from /api/premine.

Genesis
16 Sep 2026
Cliff ends
16 Sep 2027
Fully vested
13 Sep 2036
Ecosystem
1,000,000AEG
Liquidity
1,000,000AEG
Team
0AEG
Vested so far
—AEG

Every block reward is split three ways

The validator share adapts: 5% while stake coverage is low, to attract validators, and 3% once the chain is covered. The miner’s share moves the other way, up to 87%.

Miner
85%
Today, up to 87%. Goes to whoever finds the block. Emission decays smoothly; there are no halvings.
Treasury
10%
Funds the burn for the first 10 years. After that the balance stays at the treasury address; the code defines no other use for it yet.
Validators
3–5%
Shared by the stakers who attest to blocks. The 3–5% adjusts automatically with stake coverage.

A burn that phases out

Every 144 blocks, about 2 hours 24 minutes at the 60-second target, a share of the treasury balance is burned. Validators can change that rate by a stake-weighted vote. After 10 years (block 5,256,000) the burn stops, and the balance stays at the treasury address; the code defines no other use for it yet. The full history is public at /api/relay/burn.

Burned to date
—
AEG, read from the node

04Verify

Check it yourself.

The live figures on this page come from the node that serves it, and that node is ours. The same endpoints are public, with no account or key, and a node you run yourself answers them too: that is the independent check.

Receipts. A receipt is a Merkle proof that a transaction is in a block, which anyone can check against the block’s transaction root. It also reports how much validator stake attested the block and whether the block is final. How to check one: /receipt.

Live response
$ curl -s https://aegisprivacycoin.com/api/relay/chain
waiting for the node…
# your own node answers the same:
# curl -s http://127.0.0.1:9090/api/relay/chain
$ 

05Participate

Hold it, mine it, or help finalize it.

RoleYou runYou needYou earn
Hold A wallet. The Android app is a wallet only; the macOS app and the Linux node include a wallet and also run a node. Your 24-word recovery phrase, written on paper. Nothing. This is for keeping and sending AEG.
Mine The node, with mining on. No pool needed: each miner builds its own blocks against the network’s difficulty. A normal laptop can run it. Mining is CPU-bound SHA-3, and rewards follow work and luck. 85% of every block you find today, up to 87%.
Validate The node with a stake of 1,000 AEG. It then attests to every block.
aegisd rpc stake 1000 --rpc 127.0.0.1:8631
1,000 AEG, and a node that stays online. The adaptive validator share, 3–5% of each block reward.

06Download

Get Aegis.

Pick your system. Each option creates your wallet and gives you a 24-word recovery phrase.

macOS

The Aegis app. Open the .dmg and double-click Aegis: it creates your wallet, starts the node and opens the wallet in your browser. Mining is on by default.

macOS 14 or later · Apple silicon and Intel · signed and notarized

Android

A native wallet. Your seed is stored on the phone, encrypted with a key in the Android Keystore, and the app builds transactions on the device.

Android will ask you to allow installs from your browser.

Linux

The installer downloads the node (about 7.5 MB), creates your wallet, prints your recovery phrase once and runs the node as a background service. Mining is on by default; stop it any time with aegisd rpc setmining false --rpc 127.0.0.1:8631.

curl -O https://aegisprivacycoin.com/install.sh && bash install.sh
Linux x86-64 only. macOS is covered by the app above.

What you need

  • Suggested: 2 CPU cores, 2 GB of RAM (4 GB is comfortable), 1 GB of disk
  • Outbound internet on TCP 9100 for peer-to-peer
  • To mine or validate, port 9100 should also be reachable from outside
Your recovery phrase

The installer shows your 24-word recovery phrase once. Those words are your coins: write them on paper and keep them offline. Nobody, not us and not the network, can recover them for you. You can show them again with aegisd backup.

07Status

Where things stand.

Live

  • Mainnet since 16 Sep 2026Genesis block cb296b74…c651
  • Hybrid proof-of-work mining with proof-of-stake finality
  • Native Android wallet and macOS app
  • Block explorer, with verifiable receipts

Not done yet

  • More independent operatorsAs of 7 Oct 2026, one operator mines almost every block and runs the only validator.
  • Independent security audit
  • Public source repository
  • A stricter proof system
  • Exchange listings