Whitepaper
v0.1 — public draft.
The whitepaper is the canonical reference for the protocol's behaviour. The text below is parsed live from the markdown source in the repository — what you read here is what is committed.
Thirteen sections, in order.
Each section's opening paragraph is rendered inline below. Click through to read the canonical full markdown on GitHub.
- § 00 Read full ↗
Abstract
Adamant is a Layer 1 blockchain protocol designed to serve users who require properties that no existing programmable chain delivers in combination: privacy by default, high transaction throughput, sub-second finality, post-quantum cryptographic security, phone-verifiable correctness, and credibly neutral governance with no foundation, no premine, no admin…
- § 01 Read full ↗
Introduction & Motivation
## 1.1 The state of the art (2026)
- § 02 Read full ↗
Design Principles
This section establishes the principles that constrain every subsequent design decision in this document. These principles are not aspirational; they are normative. Where a technical choice in later sections must be made between alternatives, the alternative more consistent with the principles below MUST be chosen, even at the cost of performance,…
- § 03 Read full ↗
Cryptographic Foundation
This section specifies every cryptographic primitive used by the Adamant protocol. It is the foundation on which all other sections depend: the consensus mechanism, the privacy layer, the encrypted mempool, the identity system, and the recursive verification all rest on the primitives specified here.
- § 04 Read full ↗
Identity & Accounts
This section specifies how identity is represented on Adamant: how accounts are constructed, how keys authorise transactions, how users delegate visibility through view keys, and how recovery from key loss is handled. The design follows directly from the principles in section 2: privacy by default (II), permissionless participation (VII), and the…
- § 05 Read full ↗
Object Model & State
This section specifies how Adamant represents data on the chain. It is the longest technical section in the whitepaper because the object model touches every other component: it determines what transactions can do, what the virtual machine operates on, what the consensus mechanism orders, what the privacy layer shields, and what the recursive verification…
- § 06 Read full ↗
Execution & Virtual Machine
This section specifies how transactions are executed on Adamant: the smart-contract language, the virtual machine, the parallel execution model, and the resource accounting (gas) framework. It builds directly on the object model of section 5 and is the layer at which user-defined logic interacts with chain state.
- § 07 Read full ↗
Privacy Layer
This section specifies how Adamant achieves privacy by default. It is the longest and most cryptographically dense section in this whitepaper, because privacy that is genuinely usable — private by default, programmable, auditable when the user chooses, and resistant to deanonymisation through chain analysis — requires substantial cryptographic machinery.
- § 08 Read full ↗
Consensus
This section specifies how Adamant's validators agree on the order of transactions, the state of the chain, and the validity of each state transition. It is the longest technical section in this whitepaper because consensus is where the protocol's correctness, performance, and credible-neutrality properties are simultaneously realised.
- § 09 Read full ↗
Networking & Mempool
This section specifies the network layer of Adamant: how nodes find each other, how transactions reach validators, how messages are propagated, and how network-level metadata is protected. It complements section 8 (Consensus) by specifying the infrastructure on which consensus operates.
- § 10 Read full ↗
Economics & Incentives
This section specifies the protocol's economic model: the native token, the genesis pool and launch mechanics, the post-launch issuance schedule, the fee mechanism, and the staking and reward economy. These specifications are part of the consensus rules; they cannot be modified by any on-chain mechanism (Principle I).
- § 11 Read full ↗
Genesis & Constitution
This section is the protocol's constitutional commitment. It specifies what is fixed forever at genesis, what cannot be changed by any party including the protocol's original implementers, and the precise mechanism by which the protocol may change despite this — through socially-coordinated hard forks in which every node operator individually chooses…
- § 12 Read full ↗
Conclusion & Open Problems
This section closes the whitepaper. It is shorter than the technical sections by design: it does not specify new protocol behaviour but reflects on what has been specified, identifies the open problems that remain, and outlines the path from this document to a running chain.
The whitepaper is the source of truth. If a property of Adamant is described differently elsewhere — on this site, in a chat, in a thread — the whitepaper wins.
— Editorial policy