Steer Protocol
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Steer provides off-chain computation and on-chain vault execution, and the surveyed Liquidity Manager record covers its Smart Pool AMM vaults rather than every Steer compute, staking or rewards product. Smart Pool users own paired concentrated-liquidity inventory whose ranges rebalance automatically. Automation changes position management, not the market-making loss path, so the version-1 amm-lp dossier controls regardless of the approximately $17.84M observed across Steer’s broad current network perimeter.
- Ships a product line without impermanent-loss exposure that merits its own review
The research file
Mechanism applicability
Steer Smart Pools are automated concentrated-liquidity vaults deployed across many AMMs and chains. Users join a vault holding paired assets; a selected strategy and decentralized execution jobs reposition liquidity when price, time or other triggers fire. Vault shares remain claims on the AMM inventory. The surrounding compute network and ERC-4626 interface automate execution but do not remove paired market-making exposure.
Current observation and perimeter
The DefiLlama protocol API read on 2026-08-15 classified Steer as a Liquidity Manager and reported approximately $17.84M across 44 listed networks, led by BSC, Katana, Flare, Base and Ethereum. Current Steer documentation advertises Smart Pools across more than 27 chains and 32 DEXs alongside distinct hooks, staking, rewards, bonds, compute and data products. This application is limited to the Smart Pool liquidity measured in the survey record.
Control, loss and exit applicability
Strategy authors choose distribution logic and rebalance triggers, while Steer execution infrastructure applies those instructions to on-chain vaults. Price movement and arbitrage still determine the assets left in the position, and a rebalance can realize prior divergence loss. Users can join and leave through SteerPeriphery, receiving the current vault assets; pending tokens may sit idle until the next rebalance, and separately deposited gas is expressly non-withdrawable.
Why the class rule decides
Multi-chain reach, strategy choice and automated range maintenance can improve convenience and fee capture but do not change the client claim into single-asset yield. The client remains an LP across the underlying DEX and Steer execution layers. The shared version-1 amm-lp dossier therefore decides before strategy, chain or audit selection. Reopen only for a separately measured Steer product whose client return does not require paired or synthetic market-making inventory.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Steer — current products and Smart Pool scope · primary · accessed 2026-08-15
Supports: Smart Pools, concentrated liquidity, current lifecycle, chains, DEXs, separate product lines - Steer — Smart Pool strategy library · primary · accessed 2026-08-15
Supports: automated LP strategies, balanced liquidity, strategy selection, rebalancing - Steer — rebalance triggers · primary · accessed 2026-08-15
Supports: price triggers, time triggers, position adjustment, vault accounting, automation - Steer — vault join and leave interface · primary · accessed 2026-08-15
Supports: vault enumeration, join vault, leave vault, vault assets, pending rebalance - Steer — gas-vault exit constraint · primary · accessed 2026-08-15
Supports: execution gas, strategy threshold, non-withdrawable gas, rebalance - DefiLlama — Steer Protocol survey record · secondary · accessed 2026-08-15
Supports: current TVL, current chains, Liquidity Manager category, survey observation
Inherited controls
The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.
| Chain | Verdict | Grade | Control constraint |
|---|---|---|---|
| Base | Approved · limits | hybrid | Coinbase — one regulated US company — operates the only sequencer, and admin keys can upgrade bridge contracts within ~7 days. |
| Arbitrum One | Approved · limits | hybrid | a single sequencer orders >99% of transactions and admin keys can upgrade bridge contracts on a ~7-day timelock. |
| Hyperliquid / HyperEVM | Rejected | freezable | a 21-validator permissioned set operates both the chain and its bridge — one compromise reaches both. |
| Ethereum | Approved | sovereign | No sequencer, no upgrade key, no operator who can be compelled — rule changes require social consensus. |
| Avalanche | Approved · limits | crypto-backed | no party can freeze or seize C-Chain funds, but one vendor writes the only production client and Messari measured over a third of stake hosted on AWS. |
| Flare | Approved · limits | crypto-backed | consensus entry is permissionless, but the Foundation monopolizes governance proposals and manually executes some approved changes. |
| Mantle | Rejected | freezable | the team can push instant upgrades — there is no exit window a client could use. |
| X Layer | Rejected | freezable | OKX operates the ordering path, proof roles are permissioned, and an X Layer multisig can upgrade immediately; the operator has also suspended block production for an upgrade. |
| OP Mainnet | Rejected | hybrid | Ethereum forced inclusion limits sequencer censorship, but the Foundation and Security Council can co-sign an immediate upgrade before a client can exit. |
| BNB Smart Chain | Rejected | freezable | the validator set concentrates around one company, and the chain has been halted by decision. |
| Polygon PoS | Rejected | hybrid | a public validator set orders transactions, but a 5-of-9 multisig can instantly upgrade staking and canonical bridge contracts, while a 5-of-8 controls custom child tokens. |