No request yet · reading routes · charging off. EXAMPLE REQUEST · ROUTE ELIGIBILITY FROM CURRENT CONFIGURATION · NOT EXECUTED
AI usage buys TAO. (proposed; not operating)
Proposed economicscharging offno TAO boughtno token
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.
Live today One request. The right subnet. A receipt for every answer. TAONIC routes each request through the Bittensor provider suited to the work, then returns the answer with a receipt. The receipt names the route, the time and the reported cost.
Question
Your question is sent to the external provider that answers it. TAONIC’s records hold the request, its route and its cost, never the question or the answer.
Intent
ESTIMATED INTENT
Market
Read from your wording in this browser. The gateway records the final classification.
Route
Routing plane, ten routes. No request. Every berth shows its route state. Route states are being read.
Request port
- ChutesREADING
- EngyREADING
- OpenRouter to ChutesREADING
- DesearchREADING
- NuminousREADING
- SynthREADING
- Chutes imageREADING
- Chutes speechREADING
- Chutes transcribeREADING
- Chutes embedREADING
No request yet · idle sweep
IDLE
Nothing is running: the moving marker is the idle sweep, not a request. Ask a question and the routes able to do the work light up here, and the one chosen rises.
Receipt
Not issued
A receipt is written by TAONIC when a real request is answered.
Execution
NOT EXECUTED
- 01Question
- 02Intent
- 03Route
- 04Execution
- 05Answer
- 06Receipt
Answer
The answer appears here after a real request.
Inspect this route · 5 routes cannot serve now
Reading which routes are connected
LIVE ROUTER
Runs today: a request is routed, answered and recorded. Free while charging is off.
Kinds of work
7
Answer, Search, Market, Check a claim, Image, Speech, Find a match.
Connected routes
…
Of 10. Connected means a real request completed through the route.
Need a key
…
Adapters exist; no credential is set, so nothing is sent.
Production records
…
Read from the gateway’s own accounting.
01VERIFIED
Ask
A request enters. TAONIC reads what kind of work it needs.
02VERIFIED
Route
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.
03PROPOSED
Accumulate
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.
04PROPOSED
Earn
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.
Why TAONIC
Multiple Bittensor routes VERIFIED
One request can reach any connected subnet route for its kind of work; routes without a key are shown and never used. Coverage is still thin: the token gate for multiple working routes (four connected routes on three subnets) is not met.
Evidence for every answer VERIFIED
Every served request is booked in a durable ledger with its route, subnet, latency and cost class. The receipt never holds the question or the answer.
Paid demand guides the reserve PROPOSED
The Demand Reserve would follow the subnets customers actually pay to use, measured from receipts, not from a vote or a price. Today the index is empty: no paid demand yet.
PROPOSED ECONOMICS
Written down and modelled. Charging is off, revenue is $0, no fee is collected and no TAO has been bought.
Proposed · Not operating · Token not yet justified
Paid demand would guide the reserve
The Demand Reserve follows the subnets customers actually pay to use. Each paid request would leave a receipt naming the capability, route, provider, subnet, cost, latency and outcome; verified paid demand, not a vote or a price, would guide how eligible reserve capital is allocated across Bittensor.
Charging is off and revenue is $0, so the index is empty and the reserve holds zero. This is a design, not a balance. No token, pool, vault or reserve exists.
- Charging is OFF
- Customer revenue is $0
- TAON NOT DEPLOYED
- TAO reserve NOT DEPLOYED
Future reserve use is undecided. Potential uses require a published policy, custody design and measurable connection to product operation.
Read the proposalA static treasury holds assets whatever customers do. Here every allocation would originate from paid route evidence: no paid demand, no allocation.
The methodology, the caps and the empty indexWhat a reserve would hold, by accounting class
NOT-DEPLOYED TOKEN
TAON has no contract, no address and no market. 0 of 8 token gates are met.
Not deployed · 0 of 8 gates met · TOKEN NOT YET JUSTIFIED
The proposed token mechanism
TAON is a proposed token with no contract, no address and no market. A token is reconsidered only if all eight published gates pass at the same time, and passing them authorizes an owner decision, never a deployment. Today the recommendation is product first, token later.
Why TAON may exist, what was rejected, the gates and the risks
PROPOSED ECONOMICS · NOT OPERATING · TOKEN NOT DEPLOYED
Stake TAON. Accrue funded TAO.
PROPOSEDPROPOSED · NOT OPERATING · TOKEN NOT DEPLOYED
Only once contracts and funding exist. Rewards would be TAO that has actually arrived in a reward vault, streamed to TAON stakers; zero deposited means zero rewards. No fixed rate, no return promise, no yield figure anywhere.
Half acquires TAO. Half funds TAONIC.
- 50% of every eligible fee to the TAO mechanism: the reward vault
- 50% to a public TAONIC treasury multisig; signers and threshold are an owner decision
- 1.00% proposed eligible swap fee on the TAON / TAO pool
- 1.50% immutable proposed ceiling, written into the hook
- No wallet-transfer tax; no hidden token-side fee; no blacklist; no arbitrary mint
TodayCharging is OFFCustomer revenue is $0TAON not deployedTAO reserve not deployedNo public auditToken gates 0 of 8All 31 rows on Status
How TAONIC worksDocs: route a requestDocs: the mechanism and its sourcesRoutes and evidenceToken (proposed)DemandReserveStatus