19 / 19IN DEVELOPMENTLive parts and proposed parts, each tagged
Mechanism and sources
ProposedParts of this chapter are PROPOSED. Each proposed part is tagged where it appears; everything else describes what runs. Charging is off, TAON is not deployed, no TAO reserve exists and no audit has been done.
EvidenceToken (proposed) Demand Reserve Status
TAONIC routes paid intelligence across Bittensor. Eligible fees acquire TAO. A proposed policy, not a running one: charging is OFF, revenue is $0, no TAO has been bought and no token exists. The pages Token, Demand and Reserve hold the detail; this chapter holds the whole, the sources and the contracts status.
0 sections on this page fold on a phone. Each opens on its own; this opens them all.
The mechanism in four steps
PROPOSED| Step | State | What it does |
|---|---|---|
| 01 Ask | LIVE | A request enters. TAONIC reads what kind of work it needs. |
| 02 Route | LIVE | One connected Bittensor route able to do the work is selected, with a fallback where a second connected route can do it. The answer returns with a receipt: route, subnet, latency, cost class, record ID. |
| 03 Accumulate | PROPOSED | When charging opens, paid requests would leave an eligible surplus after every cost. Half of it, and half of every eligible market fee, would buy TAO. Today: no paid request, no surplus, no TAO. |
| 04 Earn | PROPOSED | Proposed and not operating: TAO that has actually arrived in a reward vault would stream to TAON stakers. No token, no vault, no funded TAO exists. Nothing is earned today. |
PROPOSED ECONOMICS · NOT OPERATING · TOKEN NOT DEPLOYED
The two value sources would be kept in separate ledgers. Market fees: 1.00% of eligible swaps in a TAON / TAO pool under a 1.50% immutable ceiling, taken in bridged TAO, split by code half to a reward vault and half to a treasury multisig. Product surplus: what a paid request leaves after refunds, processor fees, provider cost, operating and tax reserves and earlier losses, split by policy the same way. The reward vault would hold TAO against stakers’ liabilities; a permanent reserve, if the owner ever funds one from the treasury half, would hold protocol-owned assets with no claim by anyone. The Demand Reserve of version one is a published index with no capital behind it.
Half acquires TAO. Half funds TAONIC. 50% of every eligible fee to the TAO mechanism, 50% to the TAONIC treasury multisig; signers and threshold are an owner decision. None. Wallet-to-wallet transfers are never charged. The holder line, “Stake TAON. Accrue funded TAO.”, is PROPOSED, NOT OPERATING, TOKEN NOT DEPLOYED: it would be true only once a vault exists, is funded, is audited and has been reviewed by counsel, and the thesis sentence (“Stake TAON to participate in TAO rewards funded by real usage and eligible market fees.”) is false today in every part. Token line: TOKEN NOT YET JUSTIFIED; gates 0 of 8.
The five accounting classes
PROPOSED| Class | Kind | Today |
|---|---|---|
| Reward-vault liabilities | LIABILITY | NOT DEPLOYED. No vault contract exists. Funded liability: none. Accrued: none. Coverage: not applicable. |
| Protocol-owned reserve | PROTOCOL-OWNED ASSET | NOT DEPLOYED. No reserve address. TAO acquired: none. In version one the Demand Reserve is a published index with no capital behind it. |
| Treasury assets | PROTOCOL-OWNED ASSET | NOT DEPLOYED. No multisig, no address, no signers (OWNER DECISION), no statement. |
| Native-Bittensor custody | CUSTODY | ZERO. No coldkey, no multisig, no Bittensor-side contract. Nothing is staked anywhere. |
| Bridged assets | RESTRICTED, IN TRANSIT | ZERO. No fee collector, no balance, no bridge transaction. The bridged TAO contract itself exists and is an external fact, not a TAONIC holding. |
Contracts status
FACTClassification: PROTOTYPE, NOT AUDIT-READY, NOT LAUNCH-AUTHORIZED. A Foundry prototype of the TAO-denominated fee hook, fee collector, locker, vesting, reward vault and staking vault. Never deployed anywhere. No external audit. No key, wallet or transaction was used.
| Evidence | State |
|---|---|
| Local Foundry suite | 175 tests passed, 0 failed, 0 skipped (16 suites), from the branch log. Unit, fuzz and invariant tests for the vault properties I1 to I12 and P1 to P8. |
| Robinhood Chain fork suite | 24 fork tests passed, 0 failed, 0 skipped, against the real PoolManager, Universal Router 2.1.2, V4Quoter, StateView and the bridged TAO at pinned block 106,558,300, in one run whose log is uncommitted. A re-run through a free public RPC passed 23 of 24: the RPC refused one storage read (HTTP 403). Free RPCs keep historical state for seconds to minutes, so a fresh fork run is not reproducible in CI: a release blocker, not a pass. |
| Mutation check | 38 of 38 mutants killed in the committed run, including a deliberately broken round-up-claims variant. A later, uncommitted re-run with more mutants killed 53 of 54; the survivor accepts a team vesting schedule with a short linear period. |
| Findings N1 to N13 | Per the branch’s commit messages: N1 and N13 closed with regression tests; N2 to N8 and N12 fixed or decided. N9 (the timelock is a notice, not a veto) and N11 (an expired operation cannot be re-queued) are documented and unchanged. The branch’s review documents are the phase-0 record. |
| External audit | None. Counsel: none engaged. Key custody: none exists. |
Never described as Robinhood-compatible without passing fork evidence, never as audited, and never as authorized. Contract preparation may continue without authorizing a launch.
Source register
FACTEvery conclusion the mechanism rests on carries one of five tags. A tag names how the claim is known, not how much it matters.
| Tag | Means |
|---|---|
| VERIFIED IN CODE | Read from verified contract source or a chain call, with the block named. |
| VERIFIED IN OFFICIAL DOCUMENTATION | Stated by the first party’s own documentation or API. |
| PUBLIC CLAIM NOT CODE-VERIFIED | Said in press or on a site; not checked against code. |
| INFERENCE | Derived from verified facts; no source states it. |
| UNKNOWN | Not established. What would settle it is named. |
| Claim | Tag | Source | Read |
|---|---|---|---|
| Bridged TAO on Robinhood Chain is the Chainlink BurnMintERC20 at 0xf3081494B87e8D5fb7960f066E931D1D0e6E3d67, 18 decimals, no transfer fee, no pause, no blacklist, not a proxy. | VERIFIED IN CODE | Sourcify v2 exact match (chain 4663); eth_call at block 106,538,331 | 2026-11-05 |
| Chainlink’s CCIP directory names that address as TAO on chain 4663 and on Base, with lanes only to and from Bittensor EVM (964). | VERIFIED IN OFFICIAL DOCUMENTATION | docs.chain.link CCIP token directory API (mainnet) | 2026-11-05 |
| Its supply is uncapped and a Safe-style admin can grant minting rights to any address. | VERIFIED IN CODE | maxSupply() = 0; hasRole and RoleGranted logs (blocks 46,972,275 to 96,972,274; later window unread, HTTP 429) | 2026-11-05 |
| The admin Safe’s owners and threshold; any minter granted after block 96,972,274; CCIP rate limits; whether the 964 lock-side token redeems for native TAO. | UNKNOWN | Settled by getOwners, getThreshold, the unread log window and the lock-side token code | 2026-11-05 |
| The Bittensor EVM lock pool held 14,945.84 TAO against 14,945.85 TAO minted across Robinhood Chain and Base. | VERIFIED IN CODE | eth_call on chains 964, 8453 and 4663, within minutes of one another | 2026-11-05 |
| A project called Forever Money operates the bridge. | PUBLIC CLAIM NOT CODE-VERIFIED | Press articles; nothing on chain or in Chainlink’s directory names an issuer | 2026-11-05 |
| Robinhood’s official chain documentation lists WETH and USDG and does not list TAO. | VERIFIED IN OFFICIAL DOCUMENTATION | docs.robinhood.com/chain/contracts and /protocol-contracts | 2026-11-04 |
| Uniswap v4 PoolManager, PositionManager, Universal Router 2.1.2 (0x204FAca1764B154221e35c0d20aBb3c525710498), V4Quoter, StateView and Permit2 have code on chain 4663 and are listed by Uniswap. | VERIFIED IN OFFICIAL DOCUMENTATION | Uniswap deployments page and 4663.json; eth_getCode at blocks 106,538,331 and 106,539,962 | 2026-11-05 |
| Staking on a Bittensor subnet is a swap with price impact and a small default swap charge (33 of 65,535 of the input, about one twentieth of one percent); root staking is one to one; there is no unbonding period; a stake position lives under a coldkey or a contract mirror on Bittensor EVM. | VERIFIED IN OFFICIAL DOCUMENTATION | bittensor.com docs: concepts/staking-pools, guides/evm/stake-from-evm, guides/root-reborn | 2026-11-04 |
| Bittensor emissions are split by each subnet’s EMA alpha price, not by demand or revenue; 0.5 TAO per block after the first halving. | VERIFIED IN OFFICIAL DOCUMENTATION | bittensor.com docs: concepts/emissions | 2026-11-04 |
| A reserve on Robinhood Chain cannot earn staking yield where it sits; staking needs a bridge to Bittensor EVM and a Bittensor-side signer or contract. | INFERENCE | Derived from the staking documentation and the CCIP lane list | 2026-11-05 |
| Depth of TAO pools in Uniswap v4 on chain 4663. | UNKNOWN | Settled by a PoolManager Initialize scan and StateView reads; not done within the RPC budget | 2026-11-05 |
| The public Robinhood Chain RPC throttles at about 35 calls and refuses wide eth_getLogs ranges, so reproducible fork testing needs a private RPC or a caching proxy. | VERIFIED IN CODE | Probes on 2026-11-05 and earlier sessions | 2026-11-05 |
| Comparable TAO-adjacent token projects, subnet products and routing platforms were studied from first-party sites, documentation and verified contracts, twenty fields each, every cell tagged. The findings inform the design; no project is named or compared here. | VERIFIED IN OFFICIAL DOCUMENTATION | Research package R1; Sourcify v2 for the contracts that were read | 2026-11-05 |
Open owner decisions
UNKNOWN- Which reserve model stands: the 2026-09-23 record (reserve growth, no staking) or the 2026-11-05 analysis (a funded reward vault with staking). These pages describe the 2026-11-05 analysis as the proposal, labelled PROPOSED; the owner has adopted neither, and the two records letter their models differently.
- Multisig signers and threshold for the treasury, and for any reserve.
- TAO purchase cadence: the 2026-09-25 record says weekly review with a $250 minimum; the 2026-11-05 policy models a monthly batch with the same minimum.
- Whether the TAON/TAO pair proceeds at all: the bridged asset’s identity is verified, its issuer governance is not.
- Token distribution set, supply and launch route (Set A or Set B above, or neither).
- Whether any usage-incentive allocation exists, and only after counsel.
- Whether the Demand Reserve ever controls capital, and under which published, timelocked policy.
- Engagement of counsel and of an external auditor.
Website wording stays PROPOSED until legal review completes. No counsel has reviewed any of it.
Every state on this page matches Status. Where they ever differ, Status is right and this page is a defect.