Skip to content

About

ADRs and field notes on post-quantum migration for L1 chains, BFT consensus in production, crypto agility and verifiable AI

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

4 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

architecture-notes

Working notes and architecture decision records from R&D across blockchain infrastructure, verifiable AI and post-quantum cryptography.

Most of this started as internal write-ups at Magnus Mage and while building Xyress. Client specifics are stripped out. What is left is the reasoning, which tends to be the part people ask about anyway.

Nothing here is a tutorial. Each note assumes you already know the basics and want the trade-offs.

Decision records

ADR Title Status
001 Post-quantum migration path for an L1 Accepted
002 Treat consensus keys and account keys as separate migrations Accepted
003 Anchor AI audit roots on chain, keep records off chain Accepted

Notes

Note Topic
crypto-agility.md Designing transaction and key formats that can change algorithms without a hard fork
bft-in-production.md What breaks first when you run a Tendermint style BFT chain for real
verifiable-ai-stack.md Receipts, TEEs and zkML, and which one a given use case actually needs

Related code

  • hybrid-pq-sig: composite Ed25519 + ML-DSA-65 signatures with a height based migration policy
  • inference-anchor: Merkle batched receipts for AI inference

Format

ADRs follow the usual shape: context, decision, consequences, alternatives. A superseded ADR stays in place with a pointer to the one that replaced it. Being able to see why we changed our minds is half the value.

About

ADRs and field notes on post-quantum migration for L1 chains, BFT consensus in production, crypto agility and verifiable AI

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors