Multi hop routes on STONfi are encoded as sequences of operations that pass through several pools. The Omniston layer builds these sequences, and the STONfi SDK turns them into a single transaction payload.

Each hop is represented as a call to a specific pool contract with defined input and expected output. At execution time, the transaction processes these hops in order. Output from one hop becomes input to the next, while each pool applies its own fee and updates its balances.

If any hop fails to meet its local constraints or the overall route fails to meet the minimum output, the entire transaction reverts. This approach keeps multi hop routes atomic. Users do not end up with partial results from intermediate hops. Either the entire chain of swaps succeeds according to STONfi rules or the state remains unchanged, preserving the integrity of user balances. $TON $DOGS