Skip to content
HOODTENSOR
Protocol

The mechanism

What is ordinary about this design, what is actually proposed, and what would have to be true before any of it could be deployed.

PROPOSEDNOT DEPLOYED

Parameter registry

Every value below is proposed. None has been approved, modelled against real liquidity, or reviewed. They live in one place, so changing one changes every screen at once.

PROPOSED
  • Protocol fee30bpsCharged on eligible swapsPROPOSED

    Charged by the v4 hook on swaps through eligible HOODTENSOR pools only. The token itself has no transfer fee.

  • TAO acquisition share80%Fee split, staker sidePROPOSED

    Share of the captured fee used to acquire TAO for the reward reserve.

  • Treasury share20%Fee split, operations sidePROPOSED

    Share of the captured fee retained for protocol operations. Never paid to stakers.

  • Execution threshold0.1000TAOWhen a batch may executePROPOSED

    Pending capital must reach this before an acquisition runs, so gas does not consume small batches.

  • Execution cooldown1h 0mHow often it may executePROPOSED

    Minimum gap between acquisitions. Limits how precisely an observer can front-run the executor.

  • Minimum stake duration1d 0hWhen a stake may leavePROPOSED

    How long a stake must be held before it can be withdrawn. Stops a staker from entering purely to capture a pending credit.

  • Slippage ceiling100bpsWhen an execution revertsPROPOSED

    An acquisition that would exceed this reverts rather than filling at a bad price. The batch is retried later.

  • Minimum claim0.0005TAOSmallest payable claimPROPOSED

    Smallest claimable amount, so a claim cannot cost more in gas than it returns.

The two shares must account for the whole fee. That is asserted by a test, not assumed: if a future edit made them sum to anything but 100%, the build fails rather than quietly leaking capital.

Four responsibilities, one custody boundary

No single contract both holds user principal and executes market orders. That separation is what lets acquisition pause without freezing claims.

CUSTODY BOUNDARYUniswap v4HOODTENSOR / TAO poolVENUE VERIFIED · POOL NOT CREATEDRevenueHookobserves, forwardsPROPOSEDAcquisitionExecutortrades, holds nothingPROPOSEDRewardVaultcustodies stake + TAOWOULD HOLD USER FUNDSHoodtensorTokenplain ERC-20PROPOSEDTAO (CCIP)verified assetVERIFIEDSolid lines carry value. The token is staked against the vault but never holds or routes it.Four proposed contracts, none written. The two verified boxes are existing infrastructure.

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.

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.

PROPOSED
Eligible
  • Swaps through HOODTENSOR/TAO pools created with the protocol hook.
  • Any future protocol-created pool, once explicitly added to the eligible set.
UNAVAILABLE
Never 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

None written, none compiled, none deployed.

NOT DEPLOYED
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.

    VERIFIED
  • Chainlink CCIP

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

    VERIFIED
  • Uniswap v4

    The venue and hook interface. Pool creation is permissionless.

    VERIFIED
  • An event indexer

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

    UNAVAILABLE
  • A TAO/USD oracle

    Not confirmed on chain 4663. Needed for onchain valuation.

    UNAVAILABLE

What could go wrong

In order, with nothing dated that cannot be

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

SIMULATION
Now
  • Research and verification of the TAO route
  • Canonical state and reward accounting
  • This interface, every figure marked
PENDING
Next
  • Write the four contracts
  • Fork tests against Robinhood Chain
  • Measure real TAO book depth
PENDING
Before deployment
  • Independent audit
  • Parameter approval and timelock
  • Testnet with public addresses
NOT DEPLOYED
Not scheduled
  • Mainnet deployment
  • Token distribution
  • Liquidity provision

HOODTENSOR is not TAO, not wrapped TAO, and not an official product of Bittensor, Robinhood Markets, or anyone else. Current readiness