GitHub - biochain-code/biochain: "Post-quantum Layer-1 blockchain (ML-DSA-44/Dilithium3), organic node emergence, honest tokenomics" · GitHub
/" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
/;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
biochain-code
biochain
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star
main
BranchesTags
Go to file
CodeOpen more actions menu
Folders and files<br>NameNameLast commit message<br>Last commit date<br>Latest commit
History<br>24 Commits<br>24 Commits
backend
backend
docs
docs
wallet
wallet
.gitignore
.gitignore
README.md
README.md
github_discussion_intro.md
github_discussion_intro.md
View all files
Repository files navigation
BioChain — AAECN
Autonomous Adaptive Emergent Consensus Network
A post-quantum Layer-1 blockchain where nodes are not registered or deployed — they emerge organically from participant activity. An address that sends 21 impulses (transactions) automatically becomes a live network node; without continued activity its energy decays and it dies; new impulses revive it.
Status: early, working, production-deployed on two independent nodes. Not yet publicly announced. Access to this repository is by direct invitation while the project completes decentralization and legal review — see Access below.
What makes this different
Post-quantum from genesis. Every signature uses ML-DSA-44 (CRYSTALS-Dilithium3, NIST FIPS 204) — not retrofitted onto an ECDSA chain, built with it from block zero.
Organic node emergence. No staking-to-register, no permissioned validator set at launch. Activity itself creates nodes.
Integer money, no exceptions. All monetary values are satoshi-scale integers. The supply invariant (wallets + pools + locked + staked == 21,000,000 BIO) is checked with exact equality, not tolerance — any drift of even one satoshi is a bug, not a rounding error.
Custody-free atomic swaps. HTLC-based swaps (SWAP_OFFER / SWAP_LOCK / SWAP_CLAIM / SWAP_REFUND) between BIO and any external asset, with want_asset as free text — no hardcoded whitelist tying the protocol to any single external chain.
State checkpoints. New nodes can adopt a hash-verified snapshot instead of replaying the full chain from genesis, with automatic fallback to full replay on any hash mismatch.
liboqs (C) signature backend. ~228x faster ML-DSA-44 verification than the pure-Python reference implementation, measured on real production hardware — ~44,365 verifies/sec.
Real-world validation, not just a test suite
This isn't a whitepaper-only design. As of the current release:
194-test regression suite passes with genuine ML-DSA-44 cryptography (not mocked), on-device and in production. Covers consensus, the supply invariant across all five money-holding buckets, the wallet-registration grant, node-discovery/auto-promotion logic, Sybil-resistant node emergence, cryptographic peer self-recognition, and the developer and server-operator grants pools.
Two independently-hosted production nodes (different countries, different data centers) run live peer synchronization, including automatic fork resolution after a real network partition — the longer valid chain wins, with no operator intervention.
Automatic node discovery, once introduced. A brand-new node can announce itself (POST /peer/announce, matching Bitcoin's addr messages / Ethereum's FINDNODE) to become visible — this alone grants no trust. Actual promotion into a trusted peer still requires independent confirmation from a strict majority of the existing trust set through normal gossip, the same as any other candidate. A brand-new server can immediately pull the chain from any existing node once pointed at it; an operator on at least one existing trusted node still adds the new URL once, manually, for the reverse direction — from there, gossip and majority promotion spread that trust further automatically.
Sybil-resistant node emergence. Becoming a live, voting node has always required 21 impulses; it now additionally requires at least 7 real days between an address's first activity and that 21st impulse — turning mass node creation into something that costs real time, not just a script and spare change.
Developer...