Tuo docs

Roles and admin controls

Every on-chain role in Tuo, what each can and cannot do, and the boundaries that keep customer funds inside the position.

Tuo uses OpenZeppelin AccessControl with three roles. The vault wires their administration in its constructor, and the super-admin role is never granted, so there is no single key that can reconfigure the system.

Actors

ActorOn-chain identityCan doCan never do
CustomerOwner of the position NFTdeposit, requestWithdraw, withdraw, emergencyWithdraw, finalizeHlClaim, transfer the NFTAnything else. Ownership of the NFT is the whole authority model
TreasuryTREASURY_ROLE, a 2-of-3 Safe with hardware-wallet signersGrant and revoke KEEPER_ROLE and PAUSER_ROLE, rotate itself, set the fee recipient, sweep accrued fees, set the per-position cap, set the keeper swap tolerance (setKeeperSwapSlippageBps), maintain the Hyperliquid operator allowlist, register and retire products, add and retire aggregators, set the NFT base URIChange the fee percentage, upgrade anything, touch a position, reach a deployed liquidity position, move idle balances, stop a withdrawal
KeeperKEEPER_ROLE, an EOA whose key is held in a cloud HSMReshape a position's holdings inside the vault (swapIdle, mintLp, burnLp), send hedge margin to the position's bound operator (bridgeToHl), pull it back or attest a final return (markBridgeInboundComplete), return hedge value against an emergency claim (settleHlClaim)Cause funds to rest anywhere but the vault, the Uniswap position manager, the bound operator, or the NFT owner. Exceed a bucket of 10 metered actions or 150 bps of basis in measured loss per position, each refilling over 24 hours
PauserPAUSER_ROLE, a dedicated hardware walletpauseDeposits, unpauseDepositsAffect withdrawals or emergency exits in any way
Hyperliquid operatorOne EOA per position, on the treasury allowlist, key in a cloud HSMReceive bridged margin, act as the position's Hyperliquid account, approve the vault to pull margin backCall the vault. It is a destination and a pull source, never a caller
AggregatorAddress on the router allowlistBe the target of one call per swap, with an exact-amount approval cleared immediately afterHold funds across calls or receive an open-ended approval

Trust boundary

Every arrow into the vault is bounded by a role check. Every arrow out of the vault goes to one of four destinations: the owner, the Uniswap position manager, an allowlisted aggregator inside one atomic swap, or the position's bound Hyperliquid operator.

The treasury surface

FunctionNotes
setFeeRecipientRejects the zero address and the three protocol-owned addresses (the vault, its position NFT, its swap router). None of them can forward or recover a token
claimFees, claimTokenFeesPull payment. Reverts on a zero balance. A broken recipient blocks Tuo's revenue, never a customer's exit
setPerNftCapZero rejected. Bounds one position's basis and nothing else. No aggregate cap exists on-chain
setKeeperSwapSlippageBpsRejected above 250 bps. Moves the floor under the keeper's idle swaps only: the fill happens at spot while the floor comes off the 30-minute mean, so the tolerance has to cover the drift the deviation gate permits plus the route's cost. The owner's exit floor is compiled in and does not follow it, and every leg is still charged the larger of its mean- and spot-measured loss
setHlOperatorAdds or removes an operator from the allowlist. Listing rejects the zero address and the three protocol-owned addresses, none of which can return the margin: the vault would debit the position and transfer to itself, and neither the NFT nor the router has a path that pays a stranded balance back out. Removing one is always allowed. That removes three unrecoverable destinations, it does not validate an operator: any other address that cannot approve the vault strands margin the same way, which is why the treasury is a 2-of-3 Safe and the bridge is reconciled off-chain. Never unbinds a position that already bridged to that operator, and never frees that operator for another position
registerProduct, setProductOpenAdd-only registry. Retiring a product blocks new positions only
addAggregator, removeAggregatorForwarded to the router. Emptying the list stops non-USDC deposits, the exit swap, and the keeper's idle swaps. A USDC withdrawal that the position's idle USDC already covers still settles; one that does not waits for a replacement aggregator. Only the in-kind emergency exit is unconditional
setBaseURICosmetic. No custody or accounting reads it

Role administration

  • DEFAULT_ADMIN_ROLE is never granted. The deployment script asserts that nobody holds it.
  • TREASURY_ROLE administers itself, KEEPER_ROLE and PAUSER_ROLE.
  • TREASURY_ROLE cannot be renounced or self-revoked. If the last holder could give the role up, nobody could ever revoke a compromised keeper again. Rotation is grant, then the new holder revokes the old one.
  • KEEPER_ROLE and PAUSER_ROLE are rotatable by the treasury at any time.

Pausing

pauseDeposits stops new deposits and top-ups. It does not affect requestWithdraw, withdraw or emergencyWithdraw, and it does not stop the keeper from unwinding a position. It is a circuit breaker on inflows only, held by a single hardware wallet so it never waits on two signatures.

Residual risks in this model

These are disclosed design decisions, listed in full on Audits.

  • The Hyperliquid operator set is treasury-mutable. Each position binds to the operator it first bridged to and never rebinds, the operator binds to that one position for life, and both inbound legs pull only from that operator.
  • A compromised treasury could retire every aggregator but one it controls. That is a smaller power than the one it already holds over the keeper role, and it cannot touch the guaranteed exit, which pays in kind and needs no swap. It can, by emptying the list, suspend the ordinary USDC settlement of a position still holding WETH or WBTC, because the keeper needs an aggregator to turn those back into the idle USDC a payout is debited from.
  • The loss budget is a bucket of 150 bps that refills over 24 hours, so a closed 24-hour span admits up to 300 bps and the sustained rate is 150 bps per day. The ceiling is a share of recorded basis, which measured loss does not reduce, so thirty daily refills are 45% of the original basis rather than a compounding figure. It is sized on total basis, so against the on-chain allocation the keeper can still reach it is 3% at Basis Plus Core's hedge cap and 15% at Delta Hedge Standalone's, where the swap floor and the action budget bind first, at about 9.6% at the launch swap tolerance of 100 bps. Detection and the Safe revoking the keeper are the real bound. See Operational risk.

On this page