Bitcoin Forum
November 22, 2026, 09:08:29 PM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN] Aegis v0.1.0 released - Post-Quantum P2P e-cash  (Read 268 times)
m.sato04ffff (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
October 30, 2026, 01:18:18 AM
Last edit: November 14, 2026, 06:03:27 AM by m.sato04ffff
 #1

Aegis: A Post-Quantum Peer-to-Peer Electronic Cash System

October 30, 2026

I've been working on a new electronic cash system that's fully peer-to-peer, with no trusted third party.


The main properties:
- Double-spending is prevented with a peer-to-peer network.
- No mint or other trusted parties. New downloads begin at the onion door in start.cmd.
- Tor hides the path address from the node that is called. It does not make a person impossible to identify.
- New coins are made from Argon2id style proof-of-work.
- The proof-of-work for new coin generation also powers the network to prevent double-spending.


Classical elliptic-curve signatures face exposure to quantum computation, and broadcasting over clearnet IP addresses exposes the physical topology of nodes. Aegis addresses these issues directly in a standalone implementation written in Rust.


Design details:

Network transport is strictly Tor v3 onion-native via an embedded Arti engine. Nodes communicate exclusively over .onion circuits without exchanging IP addresses or requiring router port forwarding; the public coin port stays closed, and the status page is the separate page in usage note 4. Peer discovery is handled via a local 512-slot onion address book (data\peers.txt) and optional puzzle-free seed nodes (--seed).

Proof-of-work uses memory-hard Argon2id (1 pass, 1 lane, 256 MiB scratchpad per puzzle instance). Public mining uses up to 4 worker threads running independently across CPU cores (~1 GiB total working memory) to return block production to consumer hardware.

Signatures use NIST-standardised lattice cryptography (ML-DSA-44) from genesis, with public transactions domain-bound (AEGIS/public|) to the genesis hash (3628a26e7ad2487acab970add22b5f9adf6496082994d8792c0e63e75c120d28). Elliptic-curve cryptography is omitted entirely.

Difficulty adjusts continuously at every block via ASERT with a 300-second target spacing.

Total circulation will be 21,000,000 coins (1 AEGIS = 100,000,000 QUA). Block 0 pays nothing; Block 1 and onward distribute 25 AEGIS per block, halving every 420,000 blocks (~4 years).

Storage and wire messages use compact binary serialisation (Bincode). On the public network, the ledger separates the append-only block log (blocks.app), the Merkle state index with a rolling 1,024-block undo window (leaves.idx), and registered 1,312-byte public keys (keys.dat). Because public keys are stored on disk after an account's initial transaction, subsequent transfers omit the key and reference the sender address directly.

Ordinary P2P frames are capped at 250 KB. Blocks up to 4 MB are relayed via compact 32-byte transaction ID lists (Names / GetTxs), and full block bodies are gated until the header's Argon2id proof-of-work is verified first.

Aegis-wallet new writes nothing to disk and opens no network port (generating keys on the same machine is not an air gap; use a separate offline system if isolation is required). You can generate your 24-word BIP39 seed with aegis-wallet new (Argon2id KDF, 32 MiB, salt AEGIS-KDF-v3). On first startup with mining enabled, the program asks once for the 24 words, saves only the public payout address (data\miner.hex), and wipes the phrase from its own memory (note that the terminal window may still display the typed line until closed).


The software is still beta, but the core consensus rules are set in stone.


Download (Windows x64 binaries aegis.exe & aegis-wallet.exe, Cargo.toml & full source):
Code:
Archive (aegis-windows.zip | 6,733,943 bytes):
https://drive.proton.me/urls/CH9TYZ0QNW#0DX1fL5wLbTZ

This archive replaces all previous files. Those fingerprints no longer match.


SHA-256 Checksums:
Code:
aegis-windows.zip: 6,733,943 bytes
SHA-256:           b783c7ed8c7d5c846ac12ce982eee0383a6c4c9e359fa2a30caad69e3b746234

aegis.exe:         13,146,624 bytes
SHA-256:           3dec33cfd0086bf8c6955239198d8febb99bd91a6297a9a2c9af1dde5df6e76f


Usage notes:

1. Extract aegis-windows.zip into an empty folder and double-click start.cmd (do not launch aegis.exe without arguments, as that defaults to the local lab network).

2. On first launch, enter your 24 English words separated by spaces. The words are not saved to disk; data\miner.hex stores only the public receiving address for future runs, though the console window itself may continue to show the typed line. Double-clicking aegis-wallet.exe before a book exists closes the window at once. Open a command prompt in the folder and run aegis-wallet.exe new.

3. start.cmd automatically dials the initial public onion door. Initial Tor circuit bootstrap can remain quiet for several minutes. Mining waits until data\mesh.name is written. If a neighbor is ahead, mining waits again until that book has been fetched.

4. With start.cmd, the read-only status dashboard opens on all network interfaces of the machine; on the machine itself, the address remains http://127.0.0.1:8080. Keep port 8080 closed on your router. If "home dashboard bind failed (os error 10048)" appears, port 8080 is already held by another process or a previous instance; close the old aegis.exe in Task Manager (note: background P2P and mining continue even if port 8080 is occupied).

5. While standalone Core Temp is open in the background, the dashboard automatically reads CPU core temperatures and package power from CoreTempMappingObjectEx.

-- m.sato
m.sato04ffff (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
November 09, 2026, 08:09:43 PM
 #2

Status, November 9, 2026.

The public chain is at height 8957. Recent blocks are about 410 seconds apart. The target is still 300 seconds. The consensus rules are unchanged.

The archive in the first post is the current one. The 30 October 2026 file and the 1 November 2026 file do not match it. A node that is behind waits and fetches that book. The line "puzzle door is shut for a moment" means one puzzle check is already running. The download waits and then continues.
m.sato04ffff (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
November 11, 2026, 12:00:26 AM
 #3

Status, November 11, 2026.

The archive named in the first post waits before it mines. start.cmd still dials the door on its start line. Mining starts only after that door's book is on this computer. The line "mining waits for the door" is that wait. A few minutes of quiet while Tor starts is normal. Closing the window and opening it again is not required.

"puzzle door is shut for a moment" means one puzzle check is already running. The download waits and then continues. A book that has already stored a different chain more than 1,024 blocks long cannot step back onto the public book.
yoshikiazuma
Member
**
Offline

Activity: 168
Merit: 10


View Profile WWW
November 13, 2026, 07:41:35 AM
 #4

Thank you

I've just started out and the miner is running

Is it possible to increase the mining threads on this

I didn't see any options for this
m.sato04ffff (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
November 14, 2026, 06:12:15 AM
 #5

Status, November 14, 2026.

The public chain is past height 10,170.

An issue was identified in that public build. A valid hash stopped the search, but the path that records a found block was not running, so the window never showed miner candidate and the block was not saved. The next peer check printed "sync resume mining" and started the search again at tries=1. Nodes on that build stayed synchronized and found no coins.

The archive in the first post has been updated with the fix (aegis-windows.zip, 6,733,943 bytes; SHA-256: b783c7ed8c7d5c846ac12ce982eee0383a6c4c9e359fa2a30caad69e3b746234). Found blocks are now properly claimed, recorded, and advanced to the next height via miner retarget.

If you were running a previous public build, stop the node, replace aegis.exe from the updated archive in the first post, and restart while keeping your existing data\ folder intact.

-- m.sato
drywall777
Newbie
*
Offline

Activity: 29
Merit: 2


View Profile
November 14, 2026, 03:43:14 PM
 #6

Hello.  I've been mining for a while and the 127.0.0.1 dislpay shows a healthy balance.  Your post mentions a height of 10,000+.  My miner window shows much lower than that. What can I do to make sure I'm mining the proper chain? Thanks for your time.
m.sato04ffff (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
November 16, 2026, 10:57:34 AM
 #7

Thanks for testing and reporting back, drywall777.

If your local dashboard on 127.0.0.1 shows a much lower height than 10,000+, your node is mining on an isolated branch created with the earlier binary before the November 11 peer-sync update.  Because the network always follows the chain with the most accumulated Argon2id proof-of-work, blocks mined on a disconnected local branch will not be merged once you reconnect to the main mesh.

To get onto the main chain:

1. Stop your node.
2. Download the updated aegis-windows.zip (6,733,943 bytes, SHA-256: b783c7ed8c7d5c846ac12ce982eee0383a6c4c9e359fa2a30caad69e3b746234) from the first post, containing aegis.exe (13,146,624 bytes, SHA-256: 3dec33cfd0086bf8c6955239198d8febb99bd91a6297a9a2c9af1dde5df6e76f) and replace your binary.
3. Always keep your wallet.key safe. If your local branch diverged within the 1,024-block undo window, the node will reorganize onto the heavier chain automatically on restart. If your local fork is deeper than 1,024 blocks, remove blocks.app, leaves.idx, and keys.dat from your data folder (keep wallet.key) and start the node again so it pulls the main chain cleanly from genesis.

The main network is currently past block 10,867 and has processed 667 chain reorganizations cleanly without error.  Once your node catches up to the tip, it will resume mining on the main chain automatically.

- - m.sato
drywall777
Newbie
*
Offline

Activity: 29
Merit: 2


View Profile
November 16, 2026, 06:29:41 PM
 #8

Performed the steps you outlined above and I believe I am with the proper chain now...10,954.  Thank you for your help.
m.sato04ffff (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
Today at 08:43:11 PM
 #9

Status, November 22, 2026.

The public chain is past height 12,700. The consensus rules and the archive in the first post are unchanged.

Verified from the genesis block, every block's parent matches the one before it. The last 1,000 blocks average 306 seconds against the 300-second target, and the last day looks the same. The puzzle is now about 8 times harder than the minimum setting; the hardest it has been is about 27 times.

A node following the chain from genesis has processed 680 chain reorganizations without error: 625 times the heavier branch was one block longer, and 55 times height stayed the same and the heavier block won. None went deeper, and none failed. The last reorganization was at height 12,534.

-- m.sato
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!