MaelleCrypto

The fee model on TON assigns a small cost to each on chain operation, but recent improvements have pushed this cost down to a fraction of what it used to be. As a result, complex operations that involve several contract calls can still remain inexpensive in absolute terms.
STONfi uses this margin to offer richer flows without making them feel heavy. A single user action can include route selection, multi hop swaps, internal conversions for Arbitrary Provision and optional farming enrollment, yet the total fee remains low enough for everyday use.
From the user’s point of view, this means th

The broader TON ecosystem includes games, digital collectibles, payment tools and Telegram based services. Each of these domains introduces its own tokens and user flows, but they all eventually need a way to convert value between assets and connect to the rest of the network.
STONfi fills this role by acting as the connector between these domains. When a game issues a reward token, a messaging bot introduces a new asset or a payment tool uses its own unit, they can all attach to STONfi pools and routes to reach the main TON liquidity.
The STONfi SDK makes this integration straightforward f

TON stores contract state in a structured tree format, where each contract has its own isolated storage and code. Updates happen by applying transactions to this storage, and every change can be traced through the chain of blocks.
STONfi uses this model to keep pools, routing components and farming contracts clearly separated. Each pool has its own state tree with balances, fee parameters and share information. Farming contracts maintain separate trees for reward tracking, while routing logic focuses on building transactions that touch these components in a controlled sequence.
For integra

In TON, operations are built around messages that travel between contracts. A single transaction can send several messages, which are processed in order and can trigger further calls.
This design allows complex interactions to be expressed as a chain of messages rather than a single function call. STONfi uses this mechanism when executing multi step operations. A user initiated swap can trigger messages that move assets into a pool, perform the swap, send results back and optionally notify another contract about the outcome.
The same pattern applies to liquidity additions, withdrawals and f

TON targets short block times, so new blocks with confirmed transactions appear frequently. This has a direct impact on how quickly applications can react to user input and update their interfaces with final results. STONfi takes advantage of this by structuring swaps and liquidity actions so that they usually complete within one or a few consecutive blocks.
The Omniston routing layer prepares routes, the STONfi SDK builds transactions, and the network provides fast inclusion. This supports high swap cadence, where new operations can safely be started shortly after the previous ones finalize

When a swap is prepared through the STONfi SDK, it includes a minimum acceptable output value. This value is derived from the quoted result and the slippage tolerance chosen by the user or the integrating application. The transaction sent to the network embeds this minimum as part of the contract call.
During execution, the STONfi pool contracts and Omniston routes must respect this limit. If the actual output would fall below the specified minimum, the transaction reverts rather than completing at a worse rate. This prevents unexpected outcomes when pool states change between quote and exec

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

Fees collected by STONfi pools stay inside the pool and effectively compound over time. When a swap occurs, a fraction of the input is retained as a fee and added to the pool balances.
No separate withdrawal or redistribution step is needed for these fees. This means that liquidity providers see their share of the pool grow in value as more trades pass through. The compounding is implicit: every new swap uses slightly larger reserves, and the pricing curve takes that into account when calculating outputs.
The effect accumulates without any manual intervention. From an integration standpoin

Deterministic execution is a core property of STONfi contracts. Given the same inputs and the same chain state, every node will compute the same result for swaps, liquidity operations and farming interactions.
This is achieved by strictly using fixed point arithmetic, avoiding external data sources and keeping all state within contracts. For integrators, this means that simulations done via the STONfi SDK will match on chain outcomes as long as the underlying state has not changed. If state does change between simulation and execution, slippage and minimum output checks ensure that transacti

A full user journey on STONfi often combines several contract interactions into what looks like a single action. For example, adding liquidity through a wallet can involve approving asset movement, performing an internal swap for Arbitrary Provision, minting pool shares and optionally staking them in a farming contract
. The STONfi SDK coordinates these steps into one prepared transaction or a short sequence, depending on wallet capabilities. From the user’s perspective it remains a simple flow: select a pool, choose an amount and confirm. Under the hood, each step is carefully ordered so tha

When swaps approach the limits of pool capacity, STONfi must handle edge cases such as near zero output or extreme price shifts. Pool contracts include checks that prevent trades from draining almost all of one asset or pushing prices into unreasonable ranges relative to reserves.
Omniston also plays a role by flagging routes where expected output is too small compared to input or where slippage would exceed configured limits even before execution. Such routes are rejected at the quoting stage, so they never reach the point where a user can sign them.
By combining contract level guards wit

Some pools on STONfi carry tags that indicate additional mechanics, such as impermanent loss protection or stable swap behavior. Stable oriented pools are designed for assets that usually trade in a narrow price band.
They concentrate liquidity around an expected price and can reduce slippage for small deviations. Impermanent loss protection adds another layer for specific pools. It partially compensates liquidity providers for price divergence between the assets in those pools, often through extra rewards financed by the protocol or related projects. From a user’s point of view, this reduce

The STONfi SDK acts as a shared integration layer for wallets, bots and applications that want to use the protocol. Instead of each product implementing its own logic for pricing, routing and transaction construction, they call SDK functions that encapsulate these details. Internally, the SDK talks to the same contracts and Omniston routing that power the main STONfi interface.
It requests quotes, builds transactions and prepares data structures that can be signed by users in their preferred environment. This keeps behavior aligned across different tools: the same input leads to comparable o

Single sided provision on STONfi does more than simplify entry into pools. It also makes it easier to react when new farming opportunities appear on top of existing liquidity. A user can enter a pool with just one asset, without first splitting their balance and adjusting ratios manually.
The contract uses STONfi’s own pools to perform the required internal swap and allocate the resulting position. Once the position exists, it can be staked in farming contracts that sit on top of the same liquidity. The technical steps between holding a single asset and participating in a farm are reduced to

Single sided provision on STONfi does more than simplify entry into pools. It also makes it easier to react when new farming opportunities appear on top of existing liquidity. A user can enter a pool with just one asset, without first splitting their balance and adjusting ratios manually.
The contract uses STONfi’s own pools to perform the required internal swap and allocate the resulting position. Once the position exists, it can be staked in farming contracts that sit on top of the same liquidity. The technical steps between holding a single asset and participating in a farm are reduced to

As activity on TON grows, the routing layer used by STONfi has to account for changing gas costs, pool conditions and new venues. Omniston continuously updates its view of available routes, taking into consideration not only prices but also the cost and reliability of each path.
If gas usage or congestion make a particular route less attractive, the router can shift preferences toward alternatives that achieve a similar result with fewer steps. When new STONfi pools or connected venues reach meaningful depth, they can be added into the routing set without requiring changes from users or inte

STONfi is used as a backend by many wallets, bots and applications on the TON network. When a user taps a swap button in a wallet or a Telegram bot, the request often goes to STONfi pools and routing rather than to a separate in house exchange.
This shared backend model means that different interfaces can offer swaps, liquidity provision and farming without duplicating core logic. They rely on the same pools, the same Omniston routing layer and the same STONfi SDK.
For users this results in similar pricing and behavior across tools, even if the front ends look very different. As more produc

On top of its technical architecture, STONfi supports community aligned mechanics such as ambassador programs, educational calls and open discussions about protocol updates.
These initiatives use the same contracts and data that power the core system, for example distributing rewards through farming contracts or linking recognition to on chain participation. Because community rewards flow through the same infrastructure as regular DeFi actions, there is no separate accounting system that could drift away from actual usage.
Incentives can be tied directly to providing liquidity, interacting

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 fr

Internally, each STONfi pool tracks liquidity providers through a share based accounting model. When a user adds liquidity, the contract calculates how many shares correspond to their contribution, taking into account the current pool size and composition.
These shares represent a fraction of the pool’s total reserves. As swaps happen, fees accumulate inside the pool and change the absolute balances of both assets. The number of shares held by each provider stays the same, but the value behind each share increases with the pool’s total reserves. When a provider withdraws, the contract uses t