HuTao

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 fr

Before a swap on STONfi ever reaches the chain, it goes through a full preparation and validation cycle off chain. The interface or integrated app asks the STONfi backend and SDK for an exact route, expected output and a minimum acceptable result based on user settings. This step already filters out routes that do not respect basic constraints like pool depth or maximum hops.
The prepared transaction includes all these parameters directly in the contract call. During execution, the STONfi contracts and Omniston routes must match or exceed the quoted expectations. If pool states change in a w

In cases where liquidity is spread across several pools or venues, STONfi relies on Omniston to treat them as a combined resource. A single swap can be split across multiple STONfi pools or even across pools and external venues, as long as the final path meets all constraints.
Each portion of the trade is executed against its respective pool with independent fee accounting. The routing layer keeps track of how the trade is divided, aggregates outputs and still enforces a single minimum result for the entire operation. If any component cannot deliver its part, the whole transaction reverts.

STONfi contracts are built to favor explicit reverts over silent degradation. When an operation violates a constraint, such as an invalid ratio for liquidity, an expired deadline or an output below the minimum, the contract aborts and leaves state unchanged.
The STONfi SDK anticipates many of these failure modes and avoids constructing transactions that are likely to fail. Still, if conditions change between preparation and execution, the contracts act as the final line of defense. No partial updates or half completed trades are allowed to persist on chain.
For integrators, this means that

When STONfi introduces new pool versions, such as v2 contracts, it does so alongside existing pools rather than replacing them immediately. New pools run in parallel with older ones and offer improved math, gas usage or safety features. Liquidity can gradually migrate as users and integrators adjust.
The STONfi SDK and routing logic detect these versions and can prefer newer pools when they meet depth and stability criteria. Older pools remain available until liquidity naturally shifts or until projects behind specific pairs decide to deprecate them. This versioned approach allows STONfi to

JetTon 养殖直接在包含 JetTon 交易对的 STONfi 池子之上实现。
在 JetTon 生态系统内收集的代币份额被重定向到 STONfi 的养殖合约中，
在那里它们被分配给在这些池子中提供流动性的用户。
从实现角度来看，养殖的奖励与 JetTon 产品和机器人产生的实际流量相关。
只要这些产品产生活动，STONfi 上的养殖池就会收到新的代币用于分发。
用户使用与 STONfi 上其他养殖设置相同的存款、质押和提取操作与这些池子互动。
这种设计将养殖变成核心流动性层的扩展，而不是一个孤立的系统。
奖励逻辑、会计和退出遵循与其他 STONfi 池子相同的模式，
这简化了开发者的集成，也使参与者更容易理解行为。 $DOGS $TON

Omniston 是 STONfi 使用的路由层，用于在 TON 网络上跨多个场所聚合流动性。当用户通过 STONfi 提交交换时，请求会被发送到 Omniston，后者会向连接到不同池和协议的多个求解器广播报价请求。
每个求解器会使用 STONfi 池以及其他可用场所构建一条路径，并返回一个建议价格。STONfi 内部的 Omniston 逻辑会比较这些响应，并选择最有效的路径。一旦确定的交易在构建最终交易时只会进行一次，即使所选路径在内部会触达多个池或协议。从用户的角度来看，它仍然是一笔单独的 STONfi 交换，结果固定，且输出金额已知。
这种架构使 STONfi 能够像一个入口点一样运行，同时在底层使用一张流动性来源网络。价格发现和求解器竞争在后台进行，但执行和会计仍然在由 STONfi 维护的同一个合约框架内进行。 $TON $DOGS

Omniston 充当一个流动性网格，将多个流动性来源连接到同一个 STONfi 入口点之下。 当发起兑换请求时，Omniston 会通过联系多个求解器来准备报价。
每个求解器都可以聚合来自 STONfi 池以及网络上其他兼容场所的流动性。 求解器的响应包括价格和路线描述。 STONfi 中的 Omniston 逻辑会比较这些选项，并选择能满足所请求参数、成本最低或输出最佳的路线。 随后，无论内部可能涉及多个池或协议，所选路线都会被转换为一笔供用户签署的单一交易。
这种设计让 STONfi 能够在不增加用户额外复杂性的情况下，受益于更广泛的流动性环境。 交易如何被拆分、以及流动性究竟从哪里获取的细节由 Omniston 和求解器负责处理，而 STONfi 则保持稳定、可预测的接口，用于将它们连接起来。 $TON $DOGS

STONfi 提供分析工具，帮助用户理解其仓位随时间可能如何演变。APR 基于当前奖励和池子规模，显示一个简单的年化利率。APY 会在奖励定期加入回仓位时，考虑复利效应。 这些指标源自链上数据，而非固定承诺。
它们会随着 STONfi 各个池中的流动性、手续费与奖励流动变化而更新。用户可以使用 APR 和 APY 对不同池子进行对比，决定资金分配方向，并了解不同风险画像可能如何影响长期结果。
通过将这些工具与 STONfi 现有的路由与流动性机制结合，参与者可以将池子视为不仅仅是静态的代币容器，而是具备可衡量行为的结构化工具。这也将协议早期的教育重点与实际决策相连接。 $TON $DOGS

代理钱包为软件代理提供了一种受控的方式与STONfi交互，而无需转移资金所有权。每个代理操作一个由用户出资和配置的专用钱包。对价值和操作范围的限制提前定义，主钱包仍然是所有权人。
从技术角度来看，这些代理钱包像其他账户一样与STONfi合约交互。只要其内部逻辑和配置的限制允许，代理可以执行交换、调整流动性头寸或领取奖励。所有操作仍然通过现有STONfi文档中描述的相同路由和池合约进行。
这种模型允许用户在STONfi上自动化部分活动，例如定期再平衡或奖励管理，而无需引入新的执行层。代理依赖于相同的基础设施，控制权可以随时通过提取资金或关闭专用钱包来收回。$TON $DOGS

当通过 STONfi 提交交换时，多个求解器可以竞争提供最佳路径。每个求解器都维护自己对 STONfi 流动池和其他兼容场所的视图，以及它们的深度和当前价格。当收到报价请求时，求解器会尝试构建一条路径，以在给定约束条件下以最低成本达到目标资产。
这种竞争改善了 STONfi 路由层内的价格发现。找到更高效路径的求解器将赢得更多请求，这鼓励随着时间推移优化路由逻辑。与此同时，最终交易仍然会选择一条路径进行提交，这使链上执行变得简单且可预测。
由于此逻辑嵌入在 STONfi 使用的 Omniston 层中，用户无需手动在不同场所之间选择。他们只需与一个界面交互，而路由基础设施在幕后将订单流分配到多个流动性来源。 $TON $DOGS

STONfi provides analytical tools that help users understand how their positions may evolve over time. APR shows a simple annualized rate based on current rewards and pool size. APY includes the effect of compounding when rewards are periodically added back into the position. These metrics are derived from on chain data rather than fixed promises.
They update as liquidity, fees and reward flows change across STONfi pools. Users can compare pools using APR and APY, decide where to allocate capital, and see how different risk profiles might affect long term outcomes.
By combining these tools

Agentic Wallets give software agents a controlled way to interact with STONfi without transferring ownership of funds. Each agent operates a dedicated wallet funded and configured by the user. Limits on value and scope of actions are defined in advance, and the main wallet remains the owner.
From a technical point of view, these agent wallets interact with STONfi contracts like any other account. An agent can execute swaps, adjust liquidity positions or claim rewards, as long as its internal logic and configured limits allow it. All operations still pass through the same routing and pool con

When a swap is submitted through STONfi, several solvers can compete to offer the best route. Each solver maintains its own view of STONfi pools and other compatible venues, along with their depth and current prices. When a quote request arrives, the solver tries to construct a path that reaches the target asset with minimal cost under the given constraints.
This competition improves price discovery inside the STONfi routing layer. A solver that finds a more efficient path will win more requests, which encourages better optimization of routing logic over time. At the same moment, the final t

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

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 t

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

Liquidity in STONfi pools is a shared resource for many applications on the TON network. When one interface adds liquidity or attracts more users, the depth of those pools increases for everyone who integrates STONfi, including wallets, bots and external apps.
From a technical perspective, this centralization simplifies routing. Omniston can prioritize STONfi pools when they offer sufficient depth, and only look for alternative venues when necessary. The STONfi SDK exposes this behavior so that integrators do not need to manage separate liquidity maps.
For participants this means that cont

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 step