Tuo docs

Changelog

Dated record of changes to the Tuo protocol, its deployments, its security reviews and this documentation.

Entries are newest first. Deployment addresses and audit reports are added here as they land, with a link to the page that holds the detail.

How to read this page

  • Protocol entries describe a change to the deployed contracts, their configuration or a product policy. Because the contracts are immutable, a contract change always means a new deployment and is listed with its addresses.
  • Deployment entries record a new network or a new contract set, with the deploy block and verified-source links.
  • Security entries record audit reports, disclosed findings and their resolution, and bug bounty milestones.
  • Documentation entries record material changes to this site. Wording fixes are not listed.

Every entry carries the date it took effect, not the date it was written.

2026-10-01

Documentation updated to match the keeper's entry order:

  • The keeper sends a new position's hedge margin to its Hyperliquid operator account first, then swaps and mints the ranges. Each short opens only once a range in its pool is live and the margin has landed. See Position lifecycle.
  • The hedge margin leaves the vault on the keeper's first cycle after a deposit, before any range. From that transfer until the keeper's final return, the margin sits at the Hyperliquid account and the emergency exit opens 24 hours after a withdrawal request. See Withdrawals.

2026-09-26

Security review. Cyfrin reviewed the Tuo contracts in September 2026. The fixes for the findings Tuo accepted are in the code, and the report will be published on Audits when final.

Documentation updated to match the contracts after those fixes:

  • Settlement and the 24-hour emergency delay depend on the position's Hyperliquid lifecycle, which only the keeper's final return closes.
  • A 100% withdrawal waits until every range is burned. An armed withdrawal request also stops new ranges and swaps out of USDC.
  • The vault enforces one Hyperliquid operator per position, and the owner closes an emergency claim with finalizeHlClaim.
  • The treasury Safe sets the keeper's swap tolerance, 0 to 250 bps. A deposit's entry swap is bounded only by the depositor's own minimum.
  • Test suite and size figures: 426 tests, TuoVault at 24,434 bytes.

2026-09-13

Documentation published. First public version of this site. It covers:

  • What Tuo is, who it is for and the custody model, including the hedge-leg qualification.
  • The full position lifecycle: concentrated liquidity, hedging on Hyperliquid, Engine v25, valuation and withdrawals.
  • The two products, Basis Plus Core and Delta Hedge Standalone, with their sleeves, ranges and hedge models.
  • The 30% performance fee, every venue and bridge cost a position pays, and a worked example.
  • Risks: market and strategy, counterparty and venue, smart contract and oracle, operational.
  • Security: roles and admin controls, the guarded launch, audit status and disclosure.
  • Smart contracts: architecture, protocol parameters, events for integrators, deployed addresses and the BUSL-1.1 licence.

Status at publication:

  • Target network is Arbitrum One. The mainnet deployment has not happened yet.
  • An Arbitrum Sepolia rehearsal deployment exists and predates the current contract ABI. It is listed for reference only.
  • Internal audit-readiness review of the contracts completed 2026-09-08. Independent external review pending.
  • Bug bounty planned for after launch.

Coming entries

  • Arbitrum One deployment: addresses, deploy block and verified-source links.
  • External audit report and the list of resolved findings.
  • Bug bounty launch, scope and reward tiers.
  • Any change to protocol parameters, allowlists or product policies made by the treasury.

On this page