oxley documentation
Trading
How external interfaces interact with canonical oxley pools.External execution only
oxley does not operate a swap interface or render price charts. Discover links to validated external market pages, and trading interfaces or bots integrate the immutable oxley adapter and SDK.
Each token has one canonical USDG pool created by the oxley factory. An integration validates factory registration, hook, quote asset, and pool ID before presenting a quote.
Fees
Each swap has two separate charges:
0.5%oxley fee, based on actual filled USDG notional.0.5%native LP fee, paid to active liquidity positions.
Because the two fees apply at different stages, the combined cost is
approximately 0.9975% before price impact for an ordinary exact-input trade,
not exactly 1%. Slippage and price movement are additional.
Partial fills
Exact-input trades may fill up to the user's price limit or available liquidity. The oxley fee is calculated from the amount actually filled, and unused input is returned by the adapter.
Exact-output trades are all-or-revert when the requested output cannot be satisfied within the limit.
Finite Arc boundaries
No finite liquidity profile provides infinite buying or selling capacity. At an outer Arc boundary, a trade can stop when the active side is exhausted. Permissionless LPs can add positions to the same canonical pool and extend executable liquidity without migration or a second oxley market.
The correct public claim is: Arcs provide programmed liquidity across the configured launch range. They do not guarantee that every trade size or price can execute.
Trading oxley Pools
oxley pools require SETTLE -> SWAP -> TAKE/REFUND action ordering. Generic
Uniswap v4 planners that assume another sequence are not compatible. The
oxley SDK hides that route behind one transaction builder, validates the
canonical pool, and returns a ready-to-sign request. It never signs or submits
on the user's behalf.