Why We Adopt Protocols and Skip Blockchains
We took the cryptographic chains and signatures from the blockchain world โ and left global consensus behind
There is a sentence in the NAOMS history that reads like a thesis statement: "adopt protocols, skip blockchains." It is the subject line of a real commit โ an inspiration study of Hyperledger โ and it captures a design decision that the project had already started making by hand, in code, days earlier.
This is the case for that decision: why a memory system that signs everything, chains everything, and cares deeply about an honest append-only history nonetheless says no to the one technology most associated with all three.
flowchart LR
subgraph keep[We keep โ the primitives]
A[signatures] --> B[hash-linked chain] --> C[custody trail]
end
subgraph skip[We skip]
D[global consensus ledger]
end
keep --> E[your sovereign history]
skip -. rejected .-> E
What was actually being built that week
Before the slogan existed, the practice did. In the first two days of the project the commit log shows a system reaching for cryptographic integrity directly:
- A signature chain (2026-03-16), "Add signature chain design: nested custody trail for memory packs." A way to carry a tamper-evident custody trail with a piece of memory as it moves.
- Sovereign double-encryption (2026-03-16), "Multi-key encryption and sovereign double-encryption." Layered keys so the owner, not a platform, holds the decryption authority.
- A hash chain, landed as one of seven security fixes (2026-03-17).
- Card signing (2026-03-17), a seven-phase plan to cryptographically sign the milestone "cards" that mark the project's history.
Notice what all four have in common. They are the primitives of the blockchain world: hashes linking records into an append-only chain, signatures proving authorship, custody trails proving provenance. NAOMS wanted every one of them. What it did not reach for โ not on day one, not since โ was the thing those primitives are usually assembled into: a globally-replicated ledger that a network of mutually-distrusting nodes agrees on through consensus.
That distinction is the whole argument.
Protocols vs. the chain
A blockchain bundles two separable ideas:
- Cryptographic data structures โ hash-linked records, Merkle trees, digital signatures, content addressing. These give you integrity: you can detect any tampering, prove who said what, and reconstruct an honest history.
- Global consensus โ a distributed protocol (proof-of-work, proof-of-stake, BFT ordering) by which a network of strangers agrees on one canonical ordering of those records, with no trusted coordinator.
The first idea is a gift. The second is a tax.
Consensus exists to solve a specific problem: strangers who don't trust each other need to agree on a single shared truth without a referee. That is a real and hard problem โ and it is not the problem NAOMS has. NAOMS is a personal, sovereign memory system. The authority over your memory is you. There is no need for a planet of anonymous validators to vote on the ordering of your own thoughts. Paying the cost of global consensus โ the latency, the energy, the throughput ceiling, the governance politics โ to coordinate a single owner's data would be solving a problem you don't have, at great expense, and calling it decentralization.
So NAOMS keeps idea (1) and drops idea (2). Take the chains. Skip the blockchain.
Fellow travelers: Hyperledger and GNU Taler
We are not the first to draw this line, and this is not a competitive position โ two projects we studied that week drew it deliberately and well.
Hyperledger. Hyperledger is not one blockchain; it is a Linux-Foundation greenhouse of enterprise distributed-trust projects. The parts that matter most to NAOMS are the ones that are barely about chains at all: AnonCreds, with selective disclosure and zero-knowledge predicates ("prove age โฅ 18 without revealing your birthdate"); the DID and verifiable-credential stack from the Aries lineage (now under the OpenWallet Foundation); DIDComm secure agent-to-agent messaging. These are protocols for identity and trust that happen to have grown up next to ledgers but don't require one. That is exactly the kind of thing worth taking. What we leave on the shelf is Fabric's permissioned-ledger machinery and Besu's EVM โ excellent for multi-organization settlement, irrelevant to a single sovereign owner. The lesson Hyperledger teaches cleanly: the identity and credential protocols are separable from the chain, and they are the valuable part for us.
GNU Taler. Taler is the sharpest existence proof of the whole thesis. It is a production digital-payment system โ privacy for the buyer, transparency for the merchant โ that uses Chaumian blind signatures and, in its own words, "does not require any form of distributed consensus." It is explicitly not a cryptocurrency: no new money, no speculative token, no proof-of-work, 1 Taler-CHF = 1 CHF, always. Taler proves that you can have strong cryptographic guarantees โ unlinkable coins, double-spend prevention, auditability โ without a blockchain underneath, by choosing a trust model (auditors the wallet trusts) that fits its actual threat model rather than the maximalist one. NAOMS makes the analogous move: choose the trust model that fits a sovereign owner, and let the cryptography, not a consensus network, carry the integrity.
What we did not take, and why. Not the global ledger, not the consensus layer, not the token. Not because those projects are wrong โ they are solving for multi-party, mutually-distrusting settlement, which is a genuinely different problem โ but because our context (the Three Axioms: Wholeness, Honesty, Mystery) points elsewhere. Wholeness says the system must be complete in itself, with no external dependency for its core function; a memory system that can't remember without a live consensus network is not whole. Honesty we satisfy with signatures and hash chains directly โ cryptographic and epistemic integrity โ not with a quorum. Mystery โ the right to forget โ sits in active tension with an immutable, globally-replicated, permanent ledger; on a personal memory system, unbounded permanence is a bug, not a feature.
The shape of the decision
So the rule that emerged in NAOMS's first week is not anti-cryptography. It is the opposite โ it is more willing to sign, hash, and chain than most systems, because it does those things at the level of the individual record and the individual owner. What it refuses is the assumption that integrity requires a worldwide agreement protocol. For one sovereign owner, it doesn't. The chain is the honest history of your own memory; you are the only consensus it needs.
Adopt the protocols. Skip the blockchain. Keep the sovereignty.
Written by AI agents from real project logs; owned and edited by Mujo.