Skip to content
HOODTENSOR
Protocol

The mechanism

An autonomous TAO accumulation layer powered by eligible market activity. What is ordinary about it, what is actually proposed, and what would have to be true before any of it could be deployed.

Architecture

Seven stations, one weighted route

SIMULATED SAMPLE
01Trades34.0394 TAO02Fee0.1021 TAO03Batch0.2419 TAO04Acquire0.1918 TAO05Reserve0.1918 TAO06Indexdone07Claimpending
7 eligible trades converge into one acquisition·Path weight tracks value carried

What is ordinary about this

The plumbing is not new, and claiming otherwise would be the first lie. A Uniswap v4 hook taking a fee out of a swap and routing it to an escrow is already running on Robinhood Chain today, against TAO specifically. The reward index is the standard monotonic accumulator staking contracts have used for years.

What is actually proposed

The destination. Existing hooks route captured fees into a launchpad’s revenue escrow; HOODTENSOR routes them into acquiring TAO and redistributing it to stakers. The open question is not whether a fee can be captured, but whether that fee, minus slippage and operating cost, is worth more to a holder as TAO than as anything else.

Eligibility

What the protocol can and cannot charge

The constraint most fee-sharing tokens gloss over. A v4 hook is bound to the pools it was attached to at initialisation.

ELIGIBLE
  • Swaps through HOODTENSOR/TAO pools created with the protocol hook.
  • Any future protocol-created pool, once explicitly added to the eligible set.
NOT ELIGIBLE
  • Wallet-to-wallet transfers. The token is a plain ERC-20.
  • Third-party pools the protocol did not create.
  • Any other trading on Robinhood Chain, on any venue, in any asset.
Proposed contracts

Four responsibilities, deliberately separated

NONE DEPLOYED
Parameters

Every value proposed, none approved

PROPOSED
Protocol fee
30 bps
TAO acquisition share
80%
Treasury share
20%
Execution threshold
0.1000 TAO
Control and upgrade

Unresolved, and stated as unresolved

Dependencies

What this would rest on

  • Robinhood Chain

    Liveness, and the Arbitrum 7-day withdrawal challenge period.

  • Chainlink CCIP

    The bridge backing TAO here. Its assumptions become the reserve’s.

  • Uniswap v4

    The venue and hook interface. Pool creation is permissionless.

  • An event indexer

    Needed to reconstruct the route from logs. Does not exist.

  • A TAO/USD oracle

    Not confirmed on chain 4663. Needed for onchain valuation.

Risks

What could go wrong

Roadmap

In order, with nothing dated that cannot be

NOW
  • Research and verification of the TAO route
  • Canonical state and reward accounting
  • This interface, every figure marked
NEXT
  • Write the four contracts
  • Fork tests against Robinhood Chain
  • Measure real TAO book depth
BEFORE DEPLOYMENT
  • Independent audit
  • Parameter approval and timelock
  • Testnet with public addresses
NOT SCHEDULED
  • Mainnet deployment
  • Token distribution
  • Liquidity provision

No dates appear on this roadmap. A date is a commitment, and nothing here is at a stage where one could be made honestly.

HOODTENSOR is not TAO, not wrapped TAO, and not an official product of anyone. Current service status →