> For the complete documentation index, see [llms.txt](https://docs.thetpa.ai/deai-tokenized-processing-architecture/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thetpa.ai/deai-tokenized-processing-architecture/tpai-chain-full-architecture/chain-core-consensus-voting-and-tpe.md).

# Chain core: consensus, voting and TPE

TPAI Chain is an original design, not a fork of Ethereum or any other chain: its architecture, virtual machine (TPE) and rules are its own. Inside, it uses proven, audited open-source components where they fit, such as standard post-quantum cryptography libraries and a well-studied consensus design, rather than reinventing them, and every part of its core is designed for 1,000 known validators and post-quantum security.

**Consensus: DAG-based BFT.** All 1,000 nodes share batches of transactions continuously, and blocks are agreed from that shared graph, in the style of Narwhal/Bullshark or Mysticeti \[Preferred]. Blocks are designed to be final in about 1–2 seconds, with testnet confirming the real number, and can never be reversed. Every voting node verifies signatures and blocks for itself, as BFT requires. A chain of nodes shares the work around voting: preparing and proposing blocks, relaying transactions and spot-checking AI compute, so it handles more work and earns a bigger share. To keep traffic manageable with post-quantum signatures, each block is decided by a committee chosen at random from all 1,000 nodes from the start: every node has the same chance of selection, the committee changes every round, and every node still verifies everything. Everyday votes and transactions use ML-DSA; the larger SLH-DSA is kept for special cases such as long-term keys and recovery. The public testnet (from 11 June 2027) publishes benchmarks at 100, 300 and 1,000 nodes: speed, finality and data per node.

**One node, one vote.** Tier decides a node's income and duties, never its voting power. Committee selection never gives a node more than one vote. An attacker would need 334 nodes.

**Before mainnet:** start from a proven consensus design, formally verify the core logic, pass at least two independent audits, run a long public testnet and a bug bounty.

**TPE (Tokenized Processing Engine).** TPAI Chain has no EVM. TPE is its own virtual machine with its own specification. One rule runs through it: **everything deploys inside a TPA, and everything uses AI.** This is an AI chain.

**Who builds in year one.** TPA owners build on TPE: AI agents, fine-tuned models and AI services, deployed inside their TPA through AI contracts. Stage provides an SDK, templates and documentation. Outside dApps follow in Phase 2, also inside TPAs.

* **AI contracts** from mainnet: rules for AI models and agents that use GPU power and earn from their work.
* **AI-powered dApps** from Phase 2. Each dApp deploys inside a TPA through an AI contract and must call AI as part of what it does. A dApp that does not use AI cannot deploy. To make this real, a dApp must spend a minimum share of its fees on AI compute; the tech team proposes the share.
* **No new coins.** TPAI-21 is the chain's built-in token standard, used only by TPC and by approved coins bridged in 1:1. Developers cannot create new tokens: TPE, where AI contracts run, has no token-creation or mint function. Points or credits inside a dApp cannot be transferred. dApps take payment in TPC or bridged approved coins.
* **No NFTs.** The TPA itself is the only NFT-like object on the chain: a unique on-chain asset with one owner, created only through the TPA process, never minted freely.

**AI stays off the consensus path.** AI output is not identical from run to run, but consensus must be. So TPE executes only the AI contract's rules and the payments; the GPU work happens off chain and returns a receipt.

**Built-in modules.** TPAI-21 tokens (with confidential balances and an auditor key), the TPA gateway, compute receipts and pricing, the validator registry and the GPU capacity registry are native parts of the chain, not contracts.
