An exit plan,
built from liquidity.
Ladder translates your targets into concentrated-liquidity ranges and uses third-party execution contracts to place them on Robinhood Chain.
Choose where you want to exit.
Pick a pool, the token to sell, an amount, and a range above its current price. Choose equal allocation, more at lower or higher targets, heavy early allocation, a retained portion, or custom weights across 2 to 32 bands. A moonbag remains untouched in your wallet.
A band is a range, not a limit order.
The pool converts your token as its price trades through the range. If price reverses, the conversion can reverse too. You must remove liquidity and collect the resulting amounts, or settle through the supported contract, to end that exposure. Collecting fees alone does not close a position. Trading volume and price movement determine whether a band fills; neither is guaranteed. Only liquidity active at the traded price earns pool fees.
The pool sets the grid.
Each venue enforces its own tick spacing. Ladder expands the outer boundaries to this grid and snaps internal shared boundaries to the nearest valid tick. It refuses overlapping or collapsed bands. The preview shows both requested and actual ranges before any signing.
Choose who holds the position.
With wallet custody, each band is an NFT held by your wallet. You control collection and closure. With auto-settle, the contract holds the NFTs and anyone may settle when the contract's minimum quote-proceeds floor is met. The proceeds go to the recorded owner, who may also withdraw the NFT. A keeper's availability is not guaranteed.
Simulate, then sign.
Ladder verifies the network, pool factory, token ordering, balance, allowance, ticks, and allocation. If allowance is insufficient, you explicitly approve the exact amount. Only then can the actual mint be simulated successfully. Ladder repeats validation and simulation before submitting the final wallet request. Simulation cannot guarantee that state will remain unchanged before mining.
Understand the dependencies.
Ladder uses third-party execution contracts that it did not author or audit. These contracts are reported to have no external audit. Tokens, pool managers, hooks, RPC services, and indexers carry separate risks. Smart-contract bugs, manipulation, low liquidity, and unavailable infrastructure can cause losses or prevent an exit.
Contract addresses
| Contract | Address / verified source | Ladder support |
|---|---|---|
| Uniswap V3 builder | 0xE7137876Adc37C1006ABb0f0DAD36dBEbCA813E8 | Wallet + auto-settle |
| Ramses V3 builder | 0x2b46D0CB2Feb284Ab1bE0B1F429622F2630f8c2e | Wallet + auto-settle |
| GIGA builder | 0xFE09E4Cc0014BAd26fe64273959F4582Ad901fcB | Wallet |
| up. builder | 0x14d0e6f5887CF4f13ccC76E758d6829A2b2c1dbb | Wallet |
| Uniswap V4 builder | 0xe2ba64f2dA86FbfA8b513d6cf9BBECA9877fA1bE | Disabled pending exact-liquidity adapter validation |
| Auto-settle | 0xE47E9E186C8B6f314782740E35030929107125DE | Uniswap V3 + Ramses V3 |
Source and ABI retrieved September 10, 2026. The deployed auto-settle contract also supports V4, which this interface does not yet execute.