On the surface, a simple swap looks like “take asset A, give asset B”. For STONfi, a minimal version of that might include all of the following steps in one flow.

First, the application asks the STONfi SDK for a route: which pools to use, in what order, with what expected output. The SDK delegates this to routing, which asks solvers to propose paths. One route wins.

Second, the SDK builds a transaction that encodes that route, the minimum acceptable output and a deadline. The wallet shows the numbers and asks for confirmation.

Third, the transaction reaches TON and runs through the pool contracts. Balances change, fees are collected, messages are sent, and only if every check passes does the user see a new balance. All of this still counts as “just a swap”, but the path from click to result is carefully shaped so it behaves the same across many interfaces. $GRAM $DOGS