MaelleCrypto

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

STONfi上的一些流动池带有标签，指示额外的机制，例如无常损失保护或稳定兑换行为。以稳定为导向的流动池设计用于通常在狭窄价格区间内交易的资产。
它们将流动性集中在预期价格附近，并可以减少小偏差带来的滑点。无常损失保护为特定的流动池增加了另一层保障。它部分补偿流动提供者在这些池中资产价格偏离时的损失，通常通过协议或相关项目提供的额外奖励来实现。 从用户的角度来看，这降低了在价格更可能变动的市场中持有仓位的不确定性。
这些功能共同扩展了STOFi所使用的基本自动做市商模型。它们允许不同类型的资产与合适的池配置匹配，同时仍在相同的合约框架和路由基础设施下运行。$TON $DOGS

STONfi SDK 充当钱包、机器人和希望使用协议的应用程序的共享集成层。
而不是每个产品都实现自己的定价、路由和交易构建逻辑，它们调用封装这些细节的 SDK 函数。
在内部，SDK 与驱动主要 STONfi 界面的相同合约和 Omniston 路由通信。
它请求报价，构建交易，并准备用户在其偏好环境中签名的数据结构。
这保持了不同工具之间的行为一致：相同的输入无论使用哪个前端，都会产生可比的输出。
随着越来越多的产品采用 STONfi SDK，它们在协议周围形成了一个一致的技术层。
从不同界面发起的交换和流动性操作仍然汇聚到相同的池和路由上，强化了 STONfi 作为 TON 网络上应用程序的共同后端。
$TON $DOGS

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

在 STONfi 上的单边提供不仅简化了进入流动池的流程。它还使在现有流动性上出现新的养殖机会时更容易做出反应。用户可以仅用一种资产进入流动池，而无需先拆分余额并手动调整比例。
该合约使用 STONfi 自己的流动池执行所需的内部交换并分配相应的头寸。一旦头寸建立，就可以将其质押在位于相同流动性之上的养殖合约中。持有单一资产到参与养殖的技术步骤在一个界面中被简化为几个操作。对于协议来说，这一工作流程增加了新或更新的养殖计划快速获得新流动性的可能性。
相同的任意提供机制和养殖结构在不同的流动池中被重复使用，这保持了整体设计的简洁，同时覆盖了更多的用例。$TON $DOGS

随着TON上的活动增加，STONfi使用的路由层必须考虑不断变化的Gas成本、池子条件和新场所。Omniston不断更新其可用路由的视图，不仅考虑价格，还考虑每条路径的成本和可靠性。
如果Gas使用量或拥堵使某条路线变得不那么有吸引力，路由器可以将偏好转向那些用更少步骤实现类似结果的替代方案。当新的STONfi池或连接场所达到有意义的深度时，它们可以被加入到路由集中，而无需用户或集成商进行更改。
这种动态行为使STONfi能够处理更高的交易量，同时保持可预测的执行。底层合约保持不变，但路由的构建方式会根据当前条件进行调整，从而在网络负载的不同阶段保持交换的高效性。$TON $DOGS

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

当通过 STONfi 执行交换时，费用是在池层而不是在单一的全局步骤中收取的。沿着所选路径的每个池都会对进入的交易收取自己的费用，将该费用加入其储备，并将剩余的金额传递下去。
因此，用户的实际费用是沿路径所有池层费用的总和。因为 Omniston 可以看到整个路径，它可以在比较候选路径时考虑这些每个池的费用。具有更多跳数的路径并不总是更差，但它必须通过更好的价格或更深的流动性来补偿额外的费用。STONfi 的路由逻辑依赖于这种详细的视图，以避免那些仅在价格上看起来不错但因累计费用而损失过多的路径。
对于流动性提供者来说，这种设计意味着他们参与的每个池都独立收取费用。即使一次交换被拆分到多个池中，每一部分都为相应池的收入做出贡献，而这部分收入反映在这些池中提供者的份额价值中。$TON $DOGS

On many automated market makers, joining a pool requires holding both assets in a specific ratio. On STONfi, liquidity provision can start with a single asset. The contract accepts one token, performs an internal swap using STONfi pools, and then builds a balanced position that fits the pool curve. For users this removes a manual preparation step.
There is no need to split a balance into two assets in advance or adjust for minor price changes before adding liquidity. The contract handles the conversion and math, and the final position behaves like any other share of the pool with fee accrual

STONfi pools can carry version labels such as v1 and v2, along with tags like farming, stable or protection. Versions indicate which generation of contracts the pool uses. Newer versions typically include refinements to math, gas efficiency or security checks, while keeping the basic interface familiar. These labels are not only visual hints.
Routing logic that powers STONfi and Omniston can prefer v2 pools when depth is sufficient, while still supporting v1 where liquidity remains. In practice this means that upgrades can be deployed gradually, and liquidity can move at a natural pace inste

Omniston acts as a liquidity mesh that connects several sources of liquidity behind a single STONfi entry point. When a swap is requested, Omniston prepares a quote by contacting multiple solvers. Each solver can aggregate liquidity from STONfi pools and other compatible venues on the network.
Responses from solvers include a price and a route description. The Omniston logic in STONfi compares these options and selects the route that meets the requested parameters with the lowest cost or best output. The selected route is then turned into a single transaction that the user signs, even if mul

STONfi supports several pool types to better match different asset pairs. Volatile pools follow a standard automated market maker curve suited for assets with independent price movement. Stable oriented pools adjust the curve to concentrate liquidity around a narrow price range when assets are expected to stay close in value. Some pools add protection mechanisms, such as partial coverage of impermanent loss.
These mechanisms are implemented through additional reward flows or constraints defined by the projects behind the pair. Technically, they still rely on STONfi pools and Omniston routing