Krushitel

Each STONfi pool is designed as a reusable building block that can be combined with different layers on top. At the core, the pool holds two assets, exposes swap functions and tracks liquidity shares. On top of that, additional contracts can attach farming, protection or custom reward logic without changing the base behavior of the pool. This modular structure is what allows STONfi to serve many use cases at once.
A single pool can participate in direct swaps, be part of an Omniston route, provide yield for farming participants and act as a reference price for external tools. All of these ro

Single sided provision on STONfi relies on internal routing that uses the protocol’s own pools. When a user supplies one asset to a pool that expects two, the contract calculates how much needs to be swapped to reach the target ratio and executes that internal swap through STONfi liquidity.
This process uses the same pricing and fee logic as a regular user initiated swap. The difference is that it is triggered as part of a liquidity action rather than a standalone trade. Once the conversion is complete, the resulting pair of balances is added to the pool as a standard liquidity position.
B

Because a significant share of swap volume and liquidity on TON flows through STONfi, many DeFi tools treat it as their default hub. Portfolio trackers and analytics dashboards often start by reading data from STONfi pools to understand market depth and recent activity.
Automated strategies also use STONfi as a predictable anchor. They plan operations such as rebalancing or cross pair moves with the assumption that core liquidity is available in STONfi pools and reachable via Omniston routes. When other venues are needed, they can still be included, but STONfi remains a central node.
This

When Agentic Wallets are connected to STONfi, they can execute predefined actions such as recurring swaps, periodic rebalancing or simple liquidity adjustments. Each agent operates a dedicated wallet funded and limited by the user and uses it to interact with STONfi pools and farming contracts.
From the perspective of STONfi, these agents behave like regular accounts. They call the same swap and liquidity methods, rely on Omniston routing and face the same constraints as any other participant. The only difference is that decisions are encoded in the agent’s logic instead of being entered man

Analytical tools available on top of STONfi help liquidity providers understand how their positions behave over time. APR values are derived from current fee and reward flows relative to total liquidity in a pool, while APY estimates show what happens if rewards are regularly reinvested into the position.
These metrics update as on chain conditions change. When swap volume increases or farming rewards grow, APR and APY reflect that rise. When liquidity increases faster than income, they move in the opposite direction. Integrations that use the STONfi SDK can surface the same metrics directly

While STONfi focuses on swaps inside the TON network, the Omniston routing layer it uses can participate in cross chain flows. In tested designs, swaps can move value between TON and other networks through native execution paths instead of relying on wrapped tokens stored in a central bridge.
On the TON side, STONfi provides the pools and contracts that source or deliver assets. Omniston coordinates with contracts on the external network so that both sides complete under matching conditions or revert together. The user interacts with STONfi as usual, even though part of the transaction is ex

STONfi supports pools for assets with very different behavior, from highly volatile tokens to pairs that stay close in value. Volatile pools use a classic automated market maker curve, which is suitable when each asset follows its own price path. Stable oriented pools adjust the curve so that most liquidity sits around a narrow price band.
For users this difference affects slippage and resilience under stress. In a volatile pool, large trades can move the price further but leave room for independent price discovery. In a stable oriented pool, smaller trades tend to be cheaper as long as the

因为TON上的交换量和流动性很大一部分通过STONfi进行，许多DeFi策略将其视为起点。投资组合工具、再平衡脚本和策略引擎通常围绕STONfi池作为主要的深度和价格来源进行规划，然后在需要时扩展到其他场所。
当Omniston与STONfi一起使用时，这些策略仍然可以达到外部流动性，而不会失去中心枢纽的优势。以STONfi开始的路线可以通过求解器分支出去，然后以单一结果返回，这保持了执行的可预测性，同时利用多个来源。
对于开发者来说，这意味着只需与STONfi及其SDK进行一次集成，就可以覆盖网络流动性的大部分。额外的逻辑可以专注于何时行动以及如何构建仓位，而底层的交换依赖于已经广泛使用的合约。$TON $DOGS

在STONfi的核心，每个池合约维护两个余额、一个内部定价曲线和一个流动性份额记录。 交换根据曲线改变余额并应用手续费，手续费留在池中。
流动性操作调整总份额数量并为每个提供者分配比例索赔。 独立的合约可以叠加在这些池上，引入农业、保护或特定分析行为。
它们使用对池份额的引用，而不是复制余额，因此核心合约仍然是资产的唯一真实来源。 通过Omniston进行路由时，也会针对这些核心池构建路径。 通过保持池合约的专注和可组合性，STONfi允许在不改变基础逻辑的情况下添加新功能。 这降低了风险，也使集成商更容易依赖池作为其自身设计中的稳定构建块。 $TON $DOGS

在技术基础设施之上，STONfi 还运行社区导向的机制，例如大使计划、电话会议和教育内容。这些举措使用与普通用户交互的相同合约和工具，例如通过耕作合约分发奖励或通过链上活动跟踪参与情况。
从协议的角度来看，这意味着激励措施保持接近实际使用情况。社区奖励可以与提供流动性、参与交换或测试新池等行为挂钩，所有这些都已由 STONfi 合约记录。无需单独的会计系统。
这种一致性使社区层与 STONfi 的核心功能保持连接。通过教育或大使渠道加入的用户会被引导使用技术帖子中描述的实际工具，而不是进入一个与协议脱节的平行系统。$DOGS $TON

Many Telegram bots and mobile wallets on TON use STONfi as their swap backend. When a user confirms an exchange in a chat or in a wallet interface, the request can be forwarded to STONfi contracts via the STONfi SDK instead of going through a separate matching engine.
This setup lets different products offer a consistent swap experience without reimplementing core logic. They rely on the same pools, the same Omniston routing layer and the same fee structure defined by STONfi.
For users this means that similar inputs produce similar outputs across tools, even if the interfaces differ. As ne

STONfi 池中的流动性是 TON 网络上众多应用的共享资源。当某个界面增加流动性或吸引更多用户时，所有集成 STONfi 的人（包括钱包、机器人和外部应用）都会因此受益——这些池的深度对所有人都会增加。
从技术角度看，这种集中化简化了路由。Omniston 可以在 STONfi 池提供足够深度时优先选择它们，只有在必要时才会寻找其他场所。STONfi SDK 将这种行为暴露出来，因此集成方无需管理各自独立的流动性映射。
对参与者而言，这意味着向 STONfi 贡献流动性，其影响不止局限于单一界面。相同的池支持多个产品中的交易，使该协议成为 TON 上广泛用例的通用基础层。 $DOGS $TON

Single sided provision on STONfi lowers the barrier to entering both pools and farming programs. A user can deposit one asset into a pool, let the contract perform the internal swap using STONfi liquidity, and receive a balanced position ready for farming.
Once the position is created, it can be staked in farming contracts that sit directly on top of the same STONfi pool. This sequence compresses several manual actions into a few contract calls: internal routing, liquidity addition and optional farming enrollment.
The user interacts with one flow, while STONfi coordinates the underlying ste

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 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 produ

When Agentic Wallets are connected to STONfi, they can execute well defined tasks such as recurring swaps or periodic rebalancing. Each agent operates a dedicated wallet funded and limited by the user, and uses it to interact with STONfi pools and farming contracts.
From the perspective of the protocol, these actions look like operations from any other account. The agent calls STONfi contracts through standard methods, uses the same routing and faces the same constraints as a regular user. The difference lies in how the decisions are made and when they are triggered.
This setup allows peop

STONfi supports both volatile and more stable oriented pools. Volatile pools use standard automated market maker curves suited for assets with independent price movement. Stable oriented pools adjust the curve to concentrate liquidity around a narrow price band when assets are expected to stay close in value.
For users this affects slippage and behavior under stress. In a volatile pool, large trades can move the price further but leave more room for independent price discovery. In a stable pool, small trades remain cheaper, but the configuration assumes limited divergence between assets.
Bo

STONfi is often used as the exchange layer beneath Telegram bots and mobile wallets on TON. When a user taps a swap button in a chat or inside a wallet, the request can be forwarded to STONfi contracts through the STONfi SDK, instead of relying on a separate matching engine.
This arrangement turns STONfi into a shared execution layer. Routing, price discovery and fee distribution are handled once at the protocol level, while different front ends decide how to present actions and data. Users see familiar interfaces, but their operations converge on the same set of pools and Omniston routes.

Within the TON ecosystem, STONfi acts as one of the main anchors for liquidity. Many assets first gain meaningful on chain depth when they are listed in STONfi pools, and other venues reference those pools as part of their own price discovery.
Omniston integrates this role by treating STONfi pools as primary candidates when building routes, especially for pairs that have proven volume and depth. When cross chain components are involved, the TON side still relies on STONfi as the place where local assets are sourced or delivered.
This central position means that changes in STONfi pools, suc

All important state in STONfi is exposed through contract methods that can be read by integrators. Pools provide access to current reserves, total share supply, fee parameters and version information. Farming contracts expose reward rates, accumulators and user specific positions.
The STONfi SDK builds on this by offering higher level views, such as effective APR, APY and expected rewards per position. It composes raw contract data into metrics that are easier to present in user interfaces while preserving a direct link back to the on chain source.
Because state is transparent and derived