Reference
If you have used single-sided liquidity on another chain, most of your model carries over. Three parts of it do not, and they are the three that cost money.
01
Liquidity covers a span of prices. Put that span entirely above the market and it holds only the token you are selling — so as price rises through it, the pool hands the token out and gives you the other asset back. That is the whole trick: a sell order made of liquidity.
A band from +5% to +8% sells progressively across the entire span. There is no single price at which it executes.
02
Price rises through a band and it fills. Price falls back through it and it un-fills — you hold the original token again. Taking the proceeds out is what makes the sale permanent: collecting it yourself on a wallet ladder, or a settle on an auto-settle one, which anybody can send once the band has filled past the floor recorded at mint.
A settle is final. The proceeds go to the address recorded when the ladder was placed, that band can never fill or reverse again, and a second attempt is refused. Reversal itself is normal for this kind of liquidity everywhere and is not something Echelon does differently — what differs is an exchange limit order, which stays filled.
03
Each pool defines the price lines a band may start and end on. On a 1% pool the finest expressible band is 2.02% wide, so asking for “sell at exactly +1%” is not something the venue can express. Edges snap outward, never inward, so a band can only get wider than you asked.
The builder shows the pool’s real minimum rather than accepting a number it will quietly widen.
04
An unfilled band is working liquidity, so it takes a share of the fees on everything that trades through the pool. That share depends entirely on what the pool actually trades — which is why a pool with no volume never fills a ladder and earns nothing.
No figure is quoted for this anywhere in Echelon, because any number would be a projection.
Custody
Echelon does not have one answer about custody. Which of the two modes you place in decides whether the position NFT sits in your wallet or in a contract, and it is the only thing that decides it.
Plain ladder
Each band is an ERC-721 minted straight to the address that signed for it. Only that address can close a band or collect from one, and no Echelon contract holds anything of yours once the transaction ends.
The builder pulls the token, mints, refunds the remainder, and holds nothing when the transaction ends. It checks that it holds nothing and reverts rather than strand a leftover.
Auto-settle ladder
The position NFT is held by the auto-settle contract instead of by you. That is the mechanism rather than a side effect: a settle can only be permissionless if the contract, not your wallet, is the address the position manager will take instructions from.
Ownerless and immutable — no admin, no pause, no upgrade path, no sweep, and no function that changes the recorded owner of a position. There is no path that moves your position anywhere but back to you.
What the auto-settle contract buys you is that anybody can close a filled band on your behalf, so an exit does not wait for you to be awake. What stops that being a forced exit is a floor: the contract refuses a settle below a minimum computed at mint from the threshold you chose, so a stranger cannot push the price down and settle you out at a price you never picked. The proceeds can only reach the address recorded when the ladder was minted, and you can take the position back with a withdrawal at any time, settled or not.
One hazard, stated plainly: if you place an auto-settle ladder from a contract address that cannot receive an ERC-721 — one with no onERC721Received — the withdrawal back to you will fail and the position stays where it is. Nothing on chain prevents this. An ordinary wallet is not affected, and the plain ladder path is not affected either.
Contracts
Every contract Echelon calls is listed here, with its address and its full source — open, verified on Blockscout, and matched byte-for-byte against the code actually running on chain. So you do not have to take our description of it on faith: open an address, read the Solidity, and audit it yourself. Nothing below asks your permission to be checked.
Pulls the token you are selling, mints one position per band straight to the address that signed, and refunds every unit it did not use. It asks its own factory whether the pool is real and refuses anything else. Stateless: it checks that it holds nothing when the call ends and reverts rather than strand a leftover.
Source verified on Blockscout, exact match. Read it →
The same job against a different dialect. Ramses keys its pools by tick spacing rather than by fee, and its mint, burn and collect calls each carry an extra index field, so the encoding differs even though the mechanism does not.
Source verified on Blockscout, exact match. Read it →
Mints ladders through V4, where every pool lives inside one singleton manager rather than in a contract of its own. A ladder still becomes ordinary positions you hold; only the venue underneath is different.
Source verified on Blockscout, exact match. Read it →
The Uniswap V3 builder, deployed a second time against GIGA’s own manager and factory.
Byte-for-byte the same runtime code as the Uniswap V3 builder in the first row — measured against the deployed bytecode, not assumed — differing only in the addresses fixed into it at construction. Auditing that one audits this one.
Source verified on Blockscout, exact match. Read it →
up.’s position manager takes a twelve-field mint struct whose last field can create the pool, against eleven fields everywhere else, so this builder is its own Solidity rather than a re-deploy of an existing one.
Source verified on Blockscout, exact match. Read it →
The only contract that holds anything of yours, and only if you choose an auto-settle ladder. It keeps the position NFTs so that anybody can close a filled band on your behalf without waiting for you. A settle is refused below a floor computed at mint, the proceeds can only reach the address recorded when the ladder was placed, and only that address can withdraw the position. No owner, no pause, no upgrade path, no sweep.
Source verified on Blockscout, exact match. Read it →
The five builders are stateless — they take your token, mint, refund the remainder and hold nothing once the transaction ends. Only the auto-settle contract holds anything, only the position NFT, and only until you withdraw it. None of the six has an owner, a pause, an upgrade path or a function that could move your position anywhere but back to you.
Verification status above was last checked on 2026-09-09. The pool contracts these build into — the position managers and factories at each venue, and WETH — are not ours and are not listed here; each builder asks its own venue’s factory whether a pool is real and refuses anything else. The contracts have had no external audit, which is the reason this section gives you the addresses rather than a reassurance.
Contracts
Every contract Echelon calls is ownerless and immutable. The builders are stateless and hold nothing once the transaction ends; the auto-settle contract holds the position and nothing else, until you withdraw it.
Status
This is new software handling real money, and a first ladder is worth placing at a size you would not mind being wrong about. The contracts have had no external audit.
Reality
Filling depends entirely on the market price moving into your bands. Nothing in Echelon can promise that, and a pool with no volume will not.
Nothing here promises a fill, a return, or a price.