TRUSS LP
LP ProtocolHow toDocs

Safety

Risks

Providing liquidity carries market, venue, contract and operational risk. Going out of pool reduces some of these risks. It does not remove your exposure to the tokens themselves.

Market risk

  • Loss to volatility (impermanent loss). A liquidity position loses value relative to holding whenever the price moves, and a concentrated position loses more than a full-range one. The strategy manages this loss; it can’t remove it.
  • Token prices. Your vault always holds the pool’s tokens, in a position or out of pool. If their prices fall, your vault falls with them.
  • Emissions. Returns are paid in AERO. A falling AERO price, lower emissions to a gauge, or new liquidity diluting the pool all reduce your return, possibly below what was expected when the range was opened.
  • Rebalancing direction. Inside a range your vault sells the rising token and buys the falling one. If you want to keep full exposure to a token that is rising, this is not the right product.
  • Jumps. A sudden large move can carry the price straight through a range, locking in the full loss for that range before the bot can respond.
  • Stop loss is not a guarantee. It is run by the bot, not the contract, and may fire a little after your line is crossed. In a fast move the exit can land below your line, and if the bot is offline it can’t fire. USDC pools only.

Venue risk

  • Stopped gauges. If Aero stops a pool’s gauge, new stakes revert. Existing positions can still be withdrawn, but a position closed for a rebalance may not be able to re-enter.
  • Price manipulation. The bot works from observed pool prices. A manipulated price can lead to a poor decision for a short period.
  • Failed swaps. A swap that cannot meet its minimum output does not execute, and the rebalance waits. Meanwhile the vault may hold its tokens outside a range.

Contract and operational risk

  • Smart contracts. The TRUSS LP factories, vaults and executor, the TRUSS VAULT, TRUSS AGG and the dust sweeper may contain bugs. They cannot be upgraded, so a fix means a new contract. Some of their sources are not yet verified on Basescan.
  • Third-party contracts. Vaults depend on Aero’s pools, gauges and position managers; swaps go through Uniswap, PancakeSwap and aggregator routers (KyberSwap, 1inch, FlyTrade, LI.FI, Velora, Sushi), and the dust sweep uses Permit2. TRUSS LP doesn’t control any of them. The allow-lists limit where funds can go; they don’t make those destinations risk-free.
  • Owner settings. Using TRUSS LP means trusting the TRUSS LP owner wallet. At once, it can add any contract to the executor’s router allow-list, choose each pool’s reference price and its on-chain loss limit, lengthen the price window, relax the rebalance limits (the defaults allow 25 rebalances an hour, so losses can add up), raise the executor’s fee ceilings (up to 20%; bot operations stay capped by your vault’s own ceilings, an owner rescue does not), and name keepers that can lock bot operations and managers that can change your vault’s bot. It cannot withdraw from your vault or block your exit: only your wallet can withdraw. Every change is a public on-chain transaction.
  • Bot key. The bot can make only the executor’s checked calls and cannot withdraw funds, but a faulty or compromised bot could still trade badly within each swap’s maximum loss.
  • Bot downtime. If the bot is offline, an in-range position keeps earning, but it won’t be rebalanced until the bot is back. Withdrawals don’t depend on the bot.
  • Signatures. Only sign TRUSS LP messages that you started. Connecting a wallet and signing in move no funds. Deposits, withdrawals and swaps do, so review each transaction before you confirm it.
  • TRUSSV. Its price in the TRUSSV/WETH pool can differ from its NAV, minting and redeeming at NAV carry a high fee, and a redemption larger than the vault’s free USDC is queued rather than paid at once. When prices are moving fast, minting and redeeming revert until they calm down, and the vault can be paused for up to 7 days at a time.
  • TRUSS VAULT launch phase. Until the owner wallet ends the launch phase, it can withdraw everything the TRUSS VAULT holds (except USDC owed to queued redemptions) while all other holders together hold no more than 5% of the starting TRUSSV, and changes such as approving a new router can take effect without a delay. At any time it can replace the NAV reader - which supplies every price NAV uses, so in effect it controls NAV (after the launch phase, only after a public delay) - mint and redeem with no fee, change the vault’s settings within their limits, move money between the vault and its positions, or shut it down - a shutdown pays holders their share in the vault’s tokens, not in USDC. See TRUSS VAULT.