Bitcoin is the reserve layer. BAN is the operating layer. The Bitcoin Attestation Network is designed to extend Bitcoin into receipts, identity, verified work, local AI, and operator tools without changing Bitcoin's monetary policy or trying to replace Bitcoin as the reserve asset.
BAN is post-quantum from genesis, anchored to Bitcoin, and built for people running their own hardware. The goal is simple: money, proofs, and useful work should live in the same system.
Important notice. This overview paper is informational only. It is not legal, financial, tax, or investment advice, and it is not an offer, solicitation, or deposit invitation. Public deposits remain disabled. Roadmap, rollout, and feature availability are forward-looking and subject to legal, technical, and operational readiness.
The Bitcoin Attestation NetworkTM is a standalone Layer 1 network anchored to Bitcoin. It is designed to preserve the properties people value most in Bitcoin - scarce monetary policy, verifiability, and permissionless participation - while adding a broader operating layer for credentials, receipts, local AI, programmable attestations, and user-run tools.
In BAN's model, Bitcoin remains the long-term reserve and highest-integrity settlement layer. BAN handles the operational layer: the day-to-day proofs, verified work, app activity, and machine-readable receipts that modern economies need but centralized platforms currently control.
| Layer | Role | Why It Matters |
|---|---|---|
| Bitcoin | Reserve layer and final settlement anchor | Keeps long-term value tied to the most credible monetary network |
| BAN | Operating layer for receipts, identity, verified work, and applications | Makes everyday economic activity auditable, programmable, and replayable |
| Toshi + Blockie Talkie | User-facing wallet and operator surface | Lets people interact with the network through tools they can actually use |
Most major blockchain systems were launched on classical cryptography. BAN is designed around post-quantum signatures and transport from the beginning instead of treating migration as a future emergency.
Modern economic life runs on opaque databases and platform logs. BAN is built around signed attestations and replayable receipts so claims can be verified instead of merely asserted.
AI is increasingly part of how decisions are made. BAN is built around local-first AI that can read from verified knowledge and produce receipts without relying on remote black-box APIs.
Every node runs a real Bitcoin node, and the BAN trust model is anchored back to Bitcoin rather than detached from it.
Signatures, identity, and transport are designed around post-quantum cryptography from block one.
BAN is designed to move from fast acknowledgement to signed finality without relying only on probabilistic settlement.
The network keeps a UTXO architecture while separating major asset and workflow categories into parallel lanes.
The economic model is intended to reward measured network contribution rather than passive staking or custodial yield.
Wallet, mesh communication, Git, and AI tooling are designed to run from user-controlled hardware instead of depending on centralized service platforms.
The easiest way to understand BAN is to keep the two rails separate.
Bitcoin is the reserve layer. That is where long-term value sits, where external settlement matters most, and where the strongest monetary credibility already exists.
BAN is the operating layer. That is where proofs, receipts, credentials, local AI outputs, software events, and verified work can be recorded and coordinated. In other words, BAN is designed to handle the machine-readable memory of the economy while Bitcoin remains the reserve anchor.
This separation matters because it avoids trying to force one system to do everything. Bitcoin does not need to become an AI network, a credential system, or a generalized app platform. BAN is designed to extend the stack above Bitcoin while staying anchored to it.
BAN is built around attestations and replayable receipts. Instead of relying on screenshots, platform dashboards, or mutable back-office logs, the system is designed to produce signed records that can be checked later.
That model applies broadly: payments, credentials, AI outputs, developer actions, and coordination events can all be expressed as verifiable receipts. The architectural goal is simple: if a claim matters, there should be durable evidence for it.
This is also why the system leans so heavily on local-first tooling. If the proof only exists inside someone else's cloud account, the user does not really control the evidence. BAN's design tries to move that evidence back onto user-controlled infrastructure.
BAN's economic framing is based on verified work, not passive returns. The network is designed to recognize measurable contribution such as mining, validation, rowstore maintenance, AI-related work, and related operator participation as those systems are enabled. That is different from asking users to deposit assets and wait for yield.
The public posture is intentionally conservative: if a rewards path is not enabled, it should be treated as planned, not live. Public deposits and withdrawals are not currently enabled.
The user entry point for self-custody, identity, and BAN participation. The wallet is designed to make the stack usable without making the user think in daemon diagrams.
The operator console for the Bitcoin economy: AI group chat, terminal workflows, mesh communication, cloud controls, and GitNode access as features are enabled.
A post-quantum Bitcoin hardware wallet designed around on-device ML-DSA-65 key generation and local signing.
Developer and publishing tools designed to let code, sites, and attestations live on user-run infrastructure instead of relying on a centralized platform account.
The point of BAN is not to add more blockchain jargon. The point is to reduce dependence on opaque intermediaries. A system with signed receipts, replayable history, local-first AI, and Bitcoin-anchored settlement changes how trust works. Instead of "trust us," the model becomes "show the receipts."
That matters for payments, identity, credentials, AI-generated work, software supply chains, and community coordination. If a claim matters, the system should be able to preserve evidence for it.
Want the deeper version? Read the Technical Whitepaper for the full consensus, cryptography, architecture, and interoperability discussion.
Want the broader story? Start with the book, browse the applications, or join the early-access list.
Contact: info@bitcoinattestationnetwork.org
Legal: This overview paper may be updated without notice. It is provided for discussion purposes only and does not create contractual rights. Deposits remain disabled until legal and technical readiness requirements are complete.