Skip to documentation
Resources/Docs
RevenueSinjoh v2

Conversion paths

Enabled descriptors, multi-hop execution, slippage and the limits of available liquidity.

3 min read·
On this page

An approved path describes actual pools

Automated conversions use Settings-approved descriptors. Hops can include a Sinjoh market, an external Uniswap v3 pool or an external v4 pool. A v4 hop carries the fee, tick spacing and hook information needed to reconstruct its pool key. A v3 hop must correspond to the selected canonical router factory’s pool for its token pair and fee.

Paths have direction, input/output assets, enabled state, per-path slippage and stock-prize classification where applicable. Approval installs a descriptor; it does not deposit liquidity into that pool. Native ETH and WETH are different representations and require explicit supported wrapping behavior.

Fresh quotes and enforced output limits

Keepers quote the actual conversion size using the execution-matching path and submit an enforced minimum output. Default path slippage is 1%; configured per-path slippage is capped at 5%. Disabled paths cannot execute. Recognized routes, the platform router, vaults and reward-settlement callers are authorized only for their own prescribed work.

text
minimum output = fresh quoted output × (1 − configured path slippage)

The converter does not add a separate historical-average deviation gate or arbitrary fixed loss cap. Slippage limits are not a guarantee of deep liquidity or an independent fair-value oracle.

Validate the whole route

  1. Check token addresses, decimals, direction and pool identity against the intended chain.
  2. Read enabled state and applicable path limits.
  3. Quote the full intended amount through every hop.
  4. Check actual input consumed and output produced at each conversion boundary.
  5. Simulate the complete authorized call, including the destination’s funding or payout behavior.
  6. After execution, verify its receipt and actual output; installation and quoting are separate milestones.

Adding or disabling a path

Any current Safe can add a path with Governance.perform(AddSwapPath, encodedPath) or disable it with the corresponding immediate action. No second Safe confirmation or timelock is required. Large installation sets still need gas-bounded transactions; gas limits are distinct from governance delays.