14 / 19PROPOSEDA design; nothing here is deployed
v4 launch proposal
ProposedPROPOSED. This chapter describes a design. Nothing in it is deployed, approved or running. Charging is off, TAON is not deployed, no TAO reserve exists and no audit has been done.
ARCHIVED PROPOSAL · NOT ADOPTED · TOKEN NOT YET JUSTIFIED
0 sections on this page fold on a phone. Each opens on its own; this opens them all.
A future TAON / TAO market could charge a fee on eligible swaps, taken by a Uniswap v4 hook on the pool itself. It would supplement the reserve; it is not the product’s economic story, which is paid intelligence (02 What TAONIC does). The proposed parameters:
| Parameter | Proposed value | State |
|---|---|---|
| Venue | A direct Uniswap v4 pool on Robinhood Chain, TAON paired with bridged TAO | PROPOSED |
| Launch path | A direct TAON / TAO Uniswap v4 pool with the TAONIC hook. Not a PONS launch: a PONS market uses PONS’s own hook and fee escrow, so this fee design could not apply to it. | PROPOSED |
| Wallet transfer tax | None. Wallet-to-wallet transfers are never charged. | PROPOSED |
| Eligible-swap fee | 1.25% | PROPOSED |
| Fee applies to | Eligible swaps in the TAONIC pool only; transfers, deposits and withdrawals never. | PROPOSED |
| Maximum fee | 2%, immutable in the hook | PROPOSED |
| Allocation changes | Behind a proposed 7-day timelock | PROPOSED |
| Accounting | Onchain, per swap, readable by anyone | PROPOSED |
| Before any deployment | Hook-bypass analysis; Independent audit | NOT DEPLOYED |
fee(swap) = eligible(swap) ? amount_in × f : 0, with f ≤ f_max = 2%
- eligible
- a swap through the TAON/TAO pool the hook is attached to
- amount_in
- the swap’s input amount, in the asset the hook takes
- f
- the fee rate, proposed at 1.25%
- f_max
- a ceiling written into the hook that no one can raise
Why a v4 hook, and not a token tax
- Only eligible market trades are charged.
- Wallet transfers stay clean, so integrations need no special handling.
- The fee path is visible onchain, swap by swap.
- A permanent maximum can be enforced in code.
- TAO is already the paired asset, so no second conversion is needed.
What must be answered first
- Hook bypass: whether trades can route around the hooked pool (another pool, another venue), and what share of volume would be eligible at all.
- Which asset the hook takes the fee in, and whether converting it costs price impact.
- Depth: how much TAO liquidity exists on Robinhood Chain to buy into.
- An independent audit of the hook and every contract it touches.
A token is reconsidered only if all eight gates pass, and none may be lowered silently. None has passed. The gates are proposed by the 2026-11-03 decision analysis; the owner has not adopted them. The ten steps of the proposed loop on the homepage are steps, not gates.
| Gate | Threshold | Evidence required | Who decides | Read 2026-11-05 | Status |
|---|---|---|---|---|---|
| G1 Real paying users | 200 or more paying accounts, de-duplicated by payment instrument, 30% or more buying a second pack, over 90 consecutive days of charging on (assumed thresholds). | Counts from the accounts and payment tables, with operator and helper accounts excluded and counted, checked by an independent reviewer. | Lead engineer, checked by the independent reviewer. | Accounts OFF, charging OFF, 0 paying accounts. | NOT MET |
| G2 Measured product revenue | The register D-R21 accounting fixes merged and reviewed; charging on for 90 days with no unresolved ledger discrepancy above $1; earned revenue reported in three consecutive signed monthly statements. | Merged commits with tests, the review report and the three statements. | Lead engineer proposes, independent reviewer confirms, project owner signs. | Revenue $0, charging OFF, D-R21 not verified merged. | NOT MET |
| G3 Positive eligible surplus | Eligible surplus of at least $1,000 a month for 3 months in a row, with the TAO half of those months bought and recorded. | Three signed monthly statements computed by the published surplus formula, plus the purchase records. For scale only: about 4,900 paid attempts a day at the proposed prices (modelled). | Project owner, on statements signed by 2 signers. | Eligible surplus $0, not computed while charging is off. | NOT MET |
| G4 Multiple working subnet routes | 4 or more connected routes across 3 or more distinct subnets, at least 2 routes for text, and 95% or more answered over 30 days. | The public accounting read for a 30-day window, per route and overall, with no-route and timeout counted as not answered. | Lead engineer. | 2 of 10 routes configured, on 2 subnets; 22 of 45 non-reused requests answered all time, under half. | NOT MET |
| G5 Published reserve and treasury policy | A treasury multisig address with its signer roles and threshold (an owner decision), spending categories and statement schedule published; a reserve address with 3 or more monthly purchase or no-purchase records and the custody drill. | Publication on the site and in the repository; statements signed by 2 signers; drill transaction hashes. | Project owner. | No multisig, no reserve address, no records; the drill was never run. | NOT MET |
| G6 Fork-tested and audited contracts | Every holder-mechanics property implemented as a Foundry invariant or unit test; fork tests on chain 4663 against the official PoolManager, Universal Router, Quoter, StateView and the bridged TAO, run in CI through a reproducible RPC with zero skips; an external audit of the exact commit with every high and medium finding closed or accepted in writing. | The CI run and the final audit report. Skipped tests do not count. | Independent reviewer confirms the audit scope matches the code to deploy. | Prototype only: local and one-off fork runs pass; no CI, no reproducible RPC, no audit. | NOT MET |
| G7 Verified paired TAO asset and viable liquidity | Identity: address, code and bridge named by a first-party source. Issuer governance: the admin multisig’s owners and threshold read and published, the full role history with no undisclosed minter, bridge limits and redemption verified. Liquidity: measured depth at which a $1,000 buy moves the price two percent or less, from a disclosed plan. | Chain reads with block numbers, the Chainlink token page, the liquidity plan. | Lead engineer. | Identity verified in code and in Chainlink’s directory; issuer governance UNKNOWN; depth UNKNOWN. 1 of 3 parts met. | NOT MET |
| G8 Legal and custody readiness | A signed written opinion from qualified counsel in the operator’s jurisdiction on the token, staking rewards in bridged TAO, the fee split, product-surplus distribution, team allocation, marketing, geography and tax; treasury and guardian keys on hardware wallets with at least 2 independent signers under signer agreements; a published custody drill. | A public summary of the opinion (the opinion may stay private) and the drill hashes. | Project owner. | No counsel engaged; no keys, multisigs or signer agreements exist. | NOT MET |
All eight must hold at the same time. Passing them authorises a new owner decision, never a deployment. A threshold can be raised at any time and lowered only by a published change with 30 days’ notice. Each gate is published as NOT MET, MEASURING or PASSED.
Before any contract: a 3-of-5 multisig behind a proposed 7-day timelock with named independent signers, the hook-bypass analysis published, and TAO depth on Robinhood Chain measured. Designed, not deployed.
Every state on this page matches Status. Where they ever differ, Status is right and this page is a defect.