When a user confirms a swap on STONfi, the flow starts with a quote request rather than a direct transaction. The interface or integrated app asks the STONfi backend for an exact input and output pair, including the maximum acceptable deviation and a time window in which the swap must be executed.

Under the hood, this request is passed to Omniston, which queries multiple solvers. Each solver examines the current state of STONfi pools and other connected venues, simulates potential paths and returns a candidate route with a locked price.

Only after one of these routes is selected does the front end build a transaction that encodes the chosen path. By separating quoting from execution, STONfi can guarantee that the user either receives the agreed result or the transaction fails. The route is not recomputed mid flight, so slippage is limited to what was negotiated at the quote stage, and any deviation beyond that threshold causes the transaction to revert. $TON $DOGS