> 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.md).

# TPAI Chain

**TPAI Chain is a next-generation blockchain with built-in AI compute.** It is Stage's layer 1, built only for AI.

TPAI Chain is an original design, not a fork of Ethereum or any other chain: its architecture, its virtual machine (TPE) and its 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 **\[Founder statement]**. Stage Technology's in-house engineering team builds it, led by co-founder and CEO Vahid (Vito) Akbari, and the code is kept in a private repository until launch **\[Founder statement]**.

The public testnet opens on **11 June 2027** and mainnet goes live on **11 October 2027**. Both dates are fixed by the founders. If a feature is not ready, it moves to a later phase; the core that launches on 11 October must first pass the readiness checklist below **\[Founder statement]**.

TPAI Chain is the native home of TPAs and TPC. Every AI job is routed through a TPA, every payment for AI is split on chain, and a pool of real datacenter GPUs sits under the chain **\[Planned]**.

## Why a separate chain

A blockchain works because every node repeats every computation and reaches exactly the same result. AI cannot work that way: one answer from a large model takes billions of calculations on a GPU, and no two GPUs return bit-identical results. That is why Ethereum, Solana and the chains that followed record transactions but cannot run AI, and why GPU marketplaces only match buyers and sellers of compute **\[Analysis]**.

TPAI Chain is built for that reality: a datacenter GPU pool sits under the protocol, and the blockchain layer on top decides who may run what, proves the work was done on genuine hardware, and pays every participant automatically **\[Planned]**. The features below have to live in the chain itself, in how accounts sign, how transfers settle and how compute is paid; a token contract on an existing chain cannot add them on its own **\[Analysis]**:

* a GPU pool that every AI payment pays for directly, with no middleman;
* TPAs as the only gateway to AI, with AI contracts instead of general smart contracts;
* 1,000 licensed validators that settle AI usage and can quarantine dangerous or fake endpoints;
* post-quantum signatures for every account;
* confidential balances with an auditor key;
* wallets with two or more keys, two-step transfers and multi-level approvals.

AI itself runs off the consensus path. The chain executes only the AI contract's rules and the payment; the GPU work happens off chain and returns a signed receipt, so consensus never waits for AI work **\[Planned]**. See [Architecture and how a request works](https://docs.thetpa.ai/deai-tokenized-processing-architecture/architecture.md) for the full job flow, pre-paid sessions and how cheating is caught.

## The GPU pool

The GPU pool is real datacenter hardware, not home computers **\[Planned]**.

* **NVIDIA GPUs, for now.** The pool runs on NVIDIA datacenter GPUs, programmed with CUDA, the most widely supported AI platform, which lets the pool manage batching and scheduling for maximum capacity. S-LoRA, which serves many fine-tuned models on one GPU, runs from day one. Other GPUs or AI chips may be added later **\[Planned]**.
* **It opens in three steps.**

| Stage    | Who provides GPUs                           | How work is proven                                                                            |
| -------- | ------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Launch   | Stage only                                  | Attested GPUs, signed receipts with model fingerprints, random re-runs of jobs by super nodes |
| Year one | Stage plus approved partner datacenters     | The same, with a larger re-run sample for new providers                                       |
| Later    | Open datacenters that post a slashable bond | The same, plus slashable bonds for every provider                                             |

* **Proof from day one.** Verifying AI work is the hardest problem in decentralized AI; Bittensor, Gensyn and Ritual each take a different approach. At launch Stage runs the only GPUs, so a receipt signed by Stage alone would be Stage vouching for itself. Instead, every GPU in the pool proves its hardware and software with NVIDIA attestation before it can take jobs, and is re-checked regularly. Attestation proves the hardware and the approved serving software. That software records a fingerprint of the exact model and adapter it ran, and of the request and answer, in a receipt signed with a key held inside the attested environment. From launch, super nodes also re-run a random sample of jobs as a second check, and the sample grows as partner and open datacenters join. Trust rests on verifiable hardware proof rather than on Stage's word **\[Planned]**. External API jobs are not attested; they carry the owner's signed receipt and are labelled External.
* **Workloads.** Inference at launch, fine-tuning in phase two. Full model training is out of scope **\[Planned]**.
* **Trained models stay home.** Models fine-tuned on the pool run only on TPAI infrastructure, with an enterprise export path; see [Architecture](https://docs.thetpa.ai/deai-tokenized-processing-architecture/architecture.md) **\[Planned]**.
* **Stage AI compute datacenters.** Stage plans to build its own AI compute datacenters in Canada, starting in Alberta, to host part of the TPAI Chain GPU pool. Like every operator, Stage will follow the network's limits: no more than 5% of validator nodes per hosting operator and no more than 10% per datacenter **\[Planned]**.
* **Who is served when the pool is busy.** GPU power goes to people who pay for it. When the pool is busy, the Meta Energy (PING) formula sets the order among paying jobs, and a fair-share cap stops any single TPA from pushing others out **\[Founder statement]**. GPU booking, reserving a future time slot, comes later as a service module.

## Validator nodes

TPAI Chain always has **exactly 1,000 validator nodes**, all live from day one. They are licensed, KYC-verified and run on high-quality servers, unlike open chains where anyone can join **\[Founder statement]**. Validator nodes, like Stage's hosted base models, are system TPAs in the reserved address range (see [Addressing, networking and isolation](https://docs.thetpa.ai/deai-tokenized-processing-architecture/addressing-networking-isolation.md)) **\[Planned]**.

### Four tiers, one vote each

Nodes come in four tiers: **micro, standard, super and super max**. A tier is defined by the duties a node takes on, and it decides the node's income and responsibilities, never its voting power. Every node has equal voting weight: one node, one vote, never more. An attacker would need 334 nodes to break consensus **\[Planned]**.

### Chains of nodes

Nodes can work together as a **chain of nodes**: a pipeline that orders, verifies and executes, with backup and rotation. A chain handles more work and earns a bigger share of the fee pool. Every voting node still verifies signatures and blocks for itself, as Byzantine fault tolerance requires; a chain shares only the work around voting, such as preparing and proposing blocks, relaying transactions and re-running sampled AI jobs. Chains start at about seven nodes and no single chain can earn more than about 10% of the fee pool **\[Planned]**.

### The license

A node holds a license: a one-time license or upgrade fee plus a locked, slashable stake. Prices are set in US dollars, paid in TPC, and follow a formula on chain linked to network activity **\[Founder statement]**. License prices, stake amounts and reward weights for each tier are published in the **Node terms** document before the node sale, not in this paper.

### How a node earns

Validator nodes are paid for the work they do: validating, proposing blocks, relaying, re-running sampled AI jobs and policing the network **\[Founder statement]**. TPAI Chain is designed so that the chain's own revenue flows to the nodes that run it:

| Revenue stream                                | Share to validator nodes                                                    |
| --------------------------------------------- | --------------------------------------------------------------------------- |
| AI usage on the GPU pool                      | 20% of every payment                                                        |
| AI usage through external API TPAs            | 20% of every payment                                                        |
| Ordinary transaction fees                     | 100%                                                                        |
| TPA subscriptions ($10 a month per TPA)       | 50%                                                                         |
| Staking rewards, early years                  | Paid from Community & Ecosystem until AI usage grows, within the reward cap |
| Confirmed reports of fake or harmful TPAs     | A reward from the offender's slashed bond                                   |
| Extra work by chains of nodes and super nodes | A bigger share of the fee pool                                              |

Any other fee the chain itself charges, including the name service, the coin bridge and future service modules such as GPU booking, goes to the validator nodes **\[Founder statement]**.

No new tokens are created to pay validators. All nodes share one fixed fee pool by reward weight, and a higher tier earns more as its duties grow **\[Planned]**. Until AI usage grows, node income is backed by staking rewards from the Community & Ecosystem allocation, within the reward cap set out in [TPCoin](https://docs.thetpa.ai/deai-tokenized-processing-architecture/tpcoin.md); fees take over as usage grows **\[Founder statement]**. This paper does not forecast node income; income depends on network usage.

### Who holds the nodes on launch day

1. Early adopters stake TPC before launch and earn staking rewards.
2. Applicants need a minimum stake, KYC and a server check, or an approved hosting operator who runs the node for them.
3. If more than 1,000 qualify, stake × time decides.
4. Each holder chooses a tier on launch day, and their staked TPC moves automatically into the node stake **\[Founder statement]**.
5. All 1,000 nodes run from day one. Any slot not taken by a qualified holder at launch is run by approved independent hosting operators within the operator and datacenter caps, staked from the reserved allocation, and released to qualified new holders as they join **\[Founder statement]**.

### Keeping the network decentralized

| Limit                | Rule                                | How it is enforced                                                                                                      |
| -------------------- | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Per owner            | At most 10 nodes (1%)               | KYC of each node's real owner, including companies under common control; the chain applies the limit per verified owner |
| Per hosting operator | At most 5% of nodes (50 of 1,000)   | Operators are registered on chain; the chain refuses any node that would break the cap                                  |
| Per datacenter       | At most 10% of nodes (100 of 1,000) | Datacenters are registered on chain; the chain refuses any node that would break the cap                                |

Reaching the 334 nodes needed to attack the chain would take at least seven separate operators working together. Stage is bound by the same rules: it owns at most 10 nodes itself, and as a hosting operator it can run at most 50, including nodes owned by others **\[Founder statement]**. Every role Stage holds at launch, and when each one changes, is listed in [How Stage earns and what Stage controls](https://docs.thetpa.ai/deai-tokenized-processing-architecture/tpcoin.md).

### Losing a license

Automatic, with appeal: a warning, then probation, then revocation with partial slashing. Dishonesty means immediate revocation and heavy slashing. A node can appeal to the review council, which also handles force majeure **\[Planned]**.

### Ten years out

In about ten years every node is expected to be super max, and the 1,000 nodes work together as one coordinated compute network, while each node stays independently owned, votes on its own and stays within the caps **\[Vision]**.

## 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. This is the preferred design; the engineering team may propose an alternative that meets the same goals **\[Planned]**.
* **A random committee from the start.** Post-quantum signatures are kilobytes rather than bytes, so having all 1,000 nodes sign every block would be heavy. Each block is therefore decided by a committee chosen at random from all 1,000 nodes; every node has the same chance of selection, the committee changes every round, and every node still verifies everything. Over time every node votes equally, so one node, one vote is preserved **\[Planned]**.
* **Signatures sized for the job.** Everyday votes and transactions use ML-DSA, the smaller post-quantum signature. SLH-DSA is kept for special cases such as long-term keys and recovery **\[Planned]**.
* **Finality.** Blocks are designed to be final in about one to two seconds, and a final block can never be reversed. The public testnet confirms the real number **\[Planned]**.
* **Published benchmarks.** From 11 June 2027 the public testnet publishes speed, finality and data per node at 100, 300 and 1,000 nodes **\[Planned]**.

**Ready at mainnet.** The core that launches on 11 October 2027 must first have: at least two independent security audits completed, about four months of public testnet, a live bug bounty, and a tested migration from Ethereum. The core logic is formally verified and built on a proven consensus design **\[Founder statement]**.

## TPE and AI contracts

TPAI Chain has no EVM. Its virtual machine is **TPE (Tokenized Processing Engine)**, with its own specification. One rule runs through it: everything deploys inside a TPA, and everything uses AI **\[Founder statement]**. There are no general smart contracts on TPAI Chain; there are **AI contracts**.

* **AI contracts, from mainnet.** An AI contract lives inside a TPA and holds the rules for a model or agent: who can call it, its price, its permissions and where its income goes. AI contracts can call and pay AI contracts in other TPAs, so a legal agent can hire a translation agent, within spending limits the TPA owner sets **\[Planned]**.
* **AI-powered dApps, from Phase 2.** Each dApp deploys inside a TPA through an AI contract and must use AI as part of what it does. To make this real, a dApp must spend a minimum share of its fees on AI compute **\[Planned]**. The share is **\[Open]**.
* **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, and dApps take payment in TPC or approved bridged coins **\[Founder statement]**.
* **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 **\[Founder statement]**.
* **Built-in modules.** TPAI-21 tokens, the TPA gateway, compute receipts and pricing, the validator registry and the GPU capacity registry are native parts of the chain, not contracts **\[Planned]**.
* **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 **\[Planned]**.

The same removal process that covers fake TPAs covers dApps: a harmful or fake dApp is reported, paused and removed, and its TPA owner's bond is at stake **\[Planned]**.

## TPAI-21, the token standard

TPAI-21 is TPAI Chain's built-in token standard. It is designed as the successor to the "20 series" of token standards, such as ERC-20 on Ethereum, TRC-20 on TRON and BEP-20 on BNB Chain **\[Planned]**. A TPAI-21 token adds three things those standards do not have: post-quantum signatures, confidential balances with an auditor key, and configurable transfers. Only TPC and approved bridged coins exist as TPAI-21 tokens.

### Post-quantum signatures

Today's blockchains sign transactions with elliptic-curve cryptography, which a large enough quantum computer could break. TPAI-21 signatures and wallets follow the post-quantum signature standards the US National Institute of Standards and Technology (NIST) published in August 2024: **ML-DSA (FIPS 204)** and **SLH-DSA (FIPS 205)** ([NIST](https://csrc.nist.gov/Projects/digital-signatures)) **\[Planned]**. Post-quantum signatures are much larger than today's (a few kilobytes rather than under 100 bytes), so blocks and fees are designed for them **\[Analysis]**.

### Confidential balances with an auditor key

A holder can switch on privacy mode. Balances and transfer amounts are then encrypted, so the public cannot see how much a wallet holds or sends. Wallet addresses stay visible, and an authorized auditor or regulator holds a key that can check amounts **\[Planned]**. This follows the model of Solana's Confidential Balances ([Solana](https://solana.com/docs/finance/privacy)).

Confidential balances launch with proven, classical privacy cryptography, as on Solana, which keeps amounts hidden today. That privacy layer is not itself post-quantum; funds stay protected by post-quantum signatures either way, and the privacy layer will be upgraded to a post-quantum scheme once one is mature **\[Planned]**.

TPAI-21 is deliberately not an anonymous token. Regulators such as Dubai's Virtual Assets Regulatory Authority prohibit issuing anonymity-enhanced cryptocurrencies and all activities related to them ([VARA rulebook](https://rulebooks.vara.ae/node/297)). Privacy from the public, with an auditor key, keeps TPAI-21 compatible with anti-money-laundering rules **\[Analysis]**.

### Configurable wallets

On most blockchains a transfer is final the moment it is sent: a stolen key or a mistyped address means the money is gone. On TPAI Chain each wallet sets its own rules **\[Planned]**:

| Setting                | How it works                                                                                                                                                                                                                                                |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| One step or two        | A sender can send in one step, as on any blockchain, or use two-signature transfers. Every wallet has at least two private keys.                                                                                                                            |
| Two-signature transfer | The first signature sends the funds; the receiver sees them as pending. The funds stay under the sender's control until the sender's second key releases them into the receiver's wallet. A sender who spots a mistake or a scam can stop before releasing. |
| Approval chains        | Institutions can require several approvals, for example five or six levels, before a large transfer goes out.                                                                                                                                               |
| Privacy mode           | Confidential balances with an auditor key, switched on or off.                                                                                                                                                                                              |

In a self-custody wallet only the owner's keys can move funds; Stage cannot freeze, release or block them. Wallets opened by email are held by Stage until the user takes their key **\[Founder statement]**. Wallets show pending and released funds separately, so a receiver such as a merchant can wait for the release before treating a payment as final.

Two-signature transfers reduce theft with a single stolen key and losses from mistaken transfers. They cannot stop every fraud: a sender can still be tricked into approving both steps **\[Analysis]**. Ethereum already offers multi-signature wallets (such as Safe) and smart accounts with spending rules; what TPAI Chain adds is building these options into every wallet at the protocol level, with release controlled by the sender.

## Addresses, names and the coin bridge

* **Wallet addresses.** Wallet addresses start with **TPAI21-** and are about 120 to 130 characters long, built on a 512-bit hash with post-quantum keys (ML-DSA or SLH-DSA). A built-in checksum catches typing mistakes before funds are sent **\[Planned]**. A wallet address is not a TPA address: TPA addresses such as ABC-042 name AI endpoints (see [Addressing, networking and isolation](https://docs.thetpa.ai/deai-tokenized-processing-architecture/addressing-networking-isolation.md)).
* **Name service.** TPAI Chain has its own name service, like ENS, so people can use readable names instead of long addresses **\[Planned]**.
* **Coin bridge.** Approved coins such as BTC and USDT move in only through a TPA wallet. A coin bridge transfer takes 48 hours, the coins are held in cold wallets with shared keys, and each bridged coin is a TPAI-21 token backed 1:1. The coin bridge opens only after the chain has run safely for a period **\[Planned]**.
* **TPC migration.** Separate from the coin bridge, ERC-20 TPC can be swapped 1:1 for native TPC from mainnet day; see [TPCoin](https://docs.thetpa.ai/deai-tokenized-processing-architecture/tpcoin.md) **\[Planned]**.

## Governance and upgrades

TPAI Chain is built to grow for decades: new services plug in as modules, validators approve changes, and the core promises are designed so that no vote can change them **\[Planned]**.

* **Service modules.** New services such as GPU booking, new GPU types or new coin bridge coins are added as modules, without rebuilding the chain.
* **Normal upgrades.** The core team proposes, validators vote (2/3, one node one vote), then a 14-day wait before going live.
* **Emergency security fixes.** A fast path: the core team ships the fix, the review council approves it, and validators confirm it afterwards.
* **Review council.** Seven members, elected by the validators by a 2/3 vote for one-year terms. Stage holds at most two seats. Stage appoints the first council before mainnet, and the validators elect the next one within six months of mainnet. The council approves emergency fixes, hears appeals and handles force majeure **\[Founder statement]**.
* **Permanent rules:** a fixed supply of 17,576,000,000 TPC; exactly 1,000 validator nodes; every validator node has equal voting weight, one node, one vote, never more **\[Founder statement]**.

## Stage AI models

Stage builds its own AI models on TPAI Chain, funded by the AI Computing Power allocation (see [TPCoin](https://docs.thetpa.ai/deai-tokenized-processing-architecture/tpcoin.md)) **\[Founder statement]**.

* **Open source, chain-hosted.** Stage models are open source: code, training methods, data and research are public. The models themselves run only on TPAI Chain and can never be downloaded. Anyone can use, test and fine-tune them through a TPA **\[Founder statement]**.
* **A stop button.** Because Stage models stay on TPAI Chain, the validator nodes can stop one if it ever becomes dangerous **\[Planned]**.

{% hint style="info" %}
The usual definition of open source AI also includes downloadable weights. Stage models differ on purpose: the weights stay on TPAI Chain so that validators can stop a model. The stop button covers the chain-hosted model, not copies someone retrains elsewhere from the public research.
{% endhint %}

## Long-term vision: toward ASI

Stage's long-term goal is artificial superintelligence (ASI), built in the open and kept under the control of 1,000 independent validators **\[Vision]**.

* **Why chain-hosted matters for safety.** A powerful model that anyone can download cannot be recalled. A model that runs only on TPAI Chain can be paused or stopped by validator vote if it becomes dangerous.
* **Funded under oversight.** The AI Computing Power allocation (40% of supply) funds this work. It is released only against milestones the validators approve, and every payment from it is proposed on chain and moves only after a 2/3 validator vote (see [TPCoin](https://docs.thetpa.ai/deai-tokenized-processing-architecture/tpcoin.md)) **\[Founder statement]**.
* **Open by design.** Code, training methods, data and research are public, so progress can be checked by anyone, while the models themselves stay on the chain **\[Founder statement]**.

## TPC on TPAI Chain

The remaining 9% of the public allocation (1,581,840,000 TPC) is launched natively on TPAI Chain on 11 October 2027, and ERC-20 TPC moves across through the TPC migration. Supply, allocation, vesting and the migration rules are in [TPCoin](https://docs.thetpa.ai/deai-tokenized-processing-architecture/tpcoin.md) **\[Founder statement]**.

## Stablecoins and DeFi

Two-signature transfers and approval chains are designed to suit institutions and large stablecoin and DeFi transfers **\[Vision]**. Whether a stablecoin is issued on TPAI Chain is decided by its issuer, not by Stage; on TPAI Chain it would arrive as an approved bridged coin.

## Status and what is still open

| Item                                   | Status                                                                                                                                                      |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Original design, not a fork            | \[Founder statement]                                                                                                                                        |
| Code                                   | In a private repository, kept private before launch to prevent copying \[Founder statement]                                                                 |
| Team                                   | Stage Technology's in-house engineering team, led by Vahid (Vito) Akbari \[Founder statement]; team size and backgrounds \[Open]                            |
| Public testnet                         | Opens 11 June 2027, with benchmarks at 100, 300 and 1,000 nodes \[Founder statement]                                                                        |
| Mainnet date                           | 11 October 2027, fixed by the founders, after the readiness checklist \[Founder statement]. Earlier plans targeted Q2 2026, then Q2 to Q3 2027.             |
| Consensus and validators               | Decided: DAG-based BFT with a random rotating committee, exactly 1,000 licensed nodes, one node one vote \[Planned]                                         |
| Verification of AI compute             | Decided: attested GPUs, receipts with model fingerprints, random re-runs, challenge window and slashing \[Planned]; exact numbers set after testnet \[Open] |
| TPC migration from Ethereum            | Decided: 1:1 swap from mainnet day, Ethereum retired at 95% migrated or after 24 months \[Founder statement]                                                |
| Compatibility with Ethereum apps       | Not planned: TPAI Chain has its own virtual machine, TPE, and no EVM \[Founder statement]                                                                   |
| Investor demo                          | A private demo for investors is planned \[Planned]                                                                                                          |
| Technical specification                | \[Open]                                                                                                                                                     |
| Node license prices and reward weights | Published in the Node terms document before the node sale \[Open]                                                                                           |
| Meta Energy calculation                | The 2.9741α rate comes from Stage's Meta Energy formula; the full calculation will be published later \[Open]                                               |
| Legal reviews                          | Securities counsel is reviewing node licenses, staking rewards and Meta Energy rewards \[Open]                                                              |

A new layer 1 is a large engineering project; comparable chains took several years and large teams. This chapter will add the technical specification, the testnet results and more about the team as they become public.
