Oryn coordinates a user intent across two settlement sides:
  • the source side, where the user initiates the swap by locking funds
  • the destination side, where a solver prepares the funds the user wants to receive
Both sides share a commitment hash. When the destination side is claimed with the secret, the same secret lets the solver claim the source side.

​
The core idea

This gives every route the same high-level outcomes:
  • Claim when the swap completes successfully.
  • Cancel when a side expires before settlement.

​
Key participants

ParticipantRole
UserRequests a quote, creates the order, and initiates the source side.
SolverProvides destination liquidity and later claims the source side.
OrderbookRecords the order, route, quote data, and indexed on-chain status.
RelayerSubmits supported destination claims after validating the secret and route.
WatcherIndexes escrow events so the app and API can show current status.
Escrow vaultsEnforce initiate, claim, and cancel rules on-chain.
Some code and older notes may use the word “filler.” In these docs, solver means the participant that supplies destination liquidity and completes the other side of the swap.

​
Flow

​
Direct routes and hop routes

Most routes settle directly on the destination chain. Avalanche L1 routes can use a hop: the destination side is claimed on a bridge chain, then the vault dispatches the token transfer toward the final L1 recipient. Read Supported Routes when you need the developer-facing route model.