<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Crypto Vazima on Medium]]></title>
        <description><![CDATA[Stories by Crypto Vazima on Medium]]></description>
        <link>https://medium.com/@ivan.zimanov?source=rss-36ca3ad36ac9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*qn_Zx_FxWq0rfXlNhgqchg.jpeg</url>
            <title>Stories by Crypto Vazima on Medium</title>
            <link>https://medium.com/@ivan.zimanov?source=rss-36ca3ad36ac9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:58:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ivan.zimanov/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Compare the True Cost of Cross-Chain Swaps on STON.fi]]></title>
            <link>https://medium.com/@ivan.zimanov/how-to-compare-the-true-cost-of-cross-chain-swaps-on-ston-fi-dd886759174a?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd886759174a</guid>
            <category><![CDATA[cross-chain-swap]]></category>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[swap]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 10:59:46 GMT</pubDate>
            <atom:updated>2026-10-17T10:59:46.830Z</atom:updated>
            <content:encoded><![CDATA[<p><em>The lowest visible fee doesn’t always mean the best deal. Learn how STON.fi and Omniston handle cross-chain execution, what affects your final received amount, and how to evaluate a swap before confirming it.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MEpOKjoNKtvvJP_mPsXzIQ.png" /></figure><p>Moving stablecoins from TON to another blockchain can look simple: select an asset, enter an amount, review a quote, and confirm the transaction. But if you want to understand what you’re actually paying, the visible network fee tells only part of the story.</p><p><strong>The most useful way to compare cross-chain swap costs on STON.fi is to measure the value you receive at the destination, then account for any additional expenses not already included in the quote.</strong> This approach captures the combined effect of network fees, execution pricing, liquidity conditions, and exchange-rate differences without counting the same cost twice.</p><p>STON.fi makes this process easier to follow through its cross-chain functionality powered by Omniston. Let’s use a TON-to-Base stablecoin swap to explore how the costs work, what happens behind the interface, and which numbers deserve your attention.</p><h3>Why the visible swap fee doesn’t tell the whole story</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u4nSEZlvjIUiMJiwa2-CYA.png" /></figure><p>Imagine that you hold 1,000 USDt on TON and want to receive USDt on Base. Both tokens are dollar-denominated stablecoins, so you might expect the conversion to deliver almost exactly 1,000 tokens, minus a small blockchain fee.</p><p>That expectation overlooks how cross-chain execution works. TON and Base maintain separate transaction histories, and moving value between them requires coordinating liquidity and settlement on two independent networks. Even when both assets target the same dollar value, the executable exchange rate may reflect additional costs.</p><p>STON.fi’s Omniston infrastructure coordinates this process through independent market makers called resolvers. When you request a supported cross-chain swap, resolvers can provide quotes specifying how much of the destination asset they are prepared to deliver under particular conditions.</p><p>The result isn’t simply a token transfer with a fixed processing charge. It’s an exchange whose final output reflects the available liquidity, resolver pricing, and applicable execution costs.</p><p>For example, receiving 997 USDt on Base after exchanging 1,000 USDt on TON doesn’t automatically mean that STON.fi charged a three-dollar protocol fee. The difference may include several components already incorporated into the quote, and identifying those components is essential for a meaningful comparison.</p><h3>How STON.fi coordinates a cross-chain swap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T4oQn-FXTh9lD7-uG3tbpg.png" /></figure><p>Omniston is the execution infrastructure developed by STON.fi to coordinate swaps across supported blockchains without requiring a traditional wrapped-token bridge.</p><p>Instead of placing all liquidity into a single shared custodial vault, Omniston uses resolvers that provide destination-side assets for individual transactions. These resolvers respond to a Request for Quote (RFQ), allowing the infrastructure to evaluate executable offers before settlement.</p><p>A simplified STON.fi cross-chain workflow looks like this:</p><ol><li><strong>Select your assets.</strong> Choose the source token on TON and a supported destination token on Base.</li><li><strong>Request a quote.</strong> STON.fi uses Omniston to obtain executable pricing from connected resolvers.</li><li><strong>Evaluate the output.</strong> Review the destination amount, applicable costs, receiving address, and other execution conditions.</li><li><strong>Confirm the transaction.</strong> The accepted swap proceeds through linked smart-contract settlement conditions.</li><li><strong>Complete or recover.</strong> The transaction settles according to its conditions, or the relevant timelock mechanism provides a recovery path if settlement cannot complete.</li></ol><p>This architecture matters because the quote describes a specific exchange outcome rather than an open-ended promise to move tokens across networks.</p><p>For the person using STON.fi, however, the immediate financial question remains straightforward: how much of the desired asset will actually arrive?</p><h3>What makes up the true cost of a STON.fi swap?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DAA5gX4sBFLVGMB0ROKZbQ.png" /></figure><p>A useful cost comparison separates four factors that can influence the result. They don’t necessarily appear as four independent charges in the interface, and some are already incorporated into the quoted amount.</p><h3>Source-chain network fees</h3><p>Every swap begins with blockchain operations that require computing and processing resources. On TON, these operations involve transaction fees for messages and smart-contract execution.</p><p>The amount reserved by your wallet may be greater than the amount ultimately consumed. For example, a transaction may require a certain TON balance to be available for execution even though not all of that balance is spent.</p><p>The distinction is important when estimating costs. <strong>Reserved gas is not necessarily the same as actual gas spent</strong>, so you shouldn’t treat the full reserved amount as a permanent expense without checking the transaction outcome.</p><h3>Resolver and execution costs</h3><p>Cross-chain resolvers provide liquidity and take on the operational responsibility of completing the destination-side exchange. Their quotes can account for inventory costs, market conditions, execution requirements, and the expenses associated with settlement.</p><p>Omniston also supports protocol and integrator fees. According to its official documentation, these fees can be embedded in the quoted execution price and collected in the destination asset.</p><p>Consequently, an amount deducted through the exchange quote should not be subtracted again when calculating the effective transaction cost.</p><h3>Exchange-rate differences</h3><p>Stablecoins are intended to maintain relatively stable values, but their trading prices can still differ slightly. A token worth approximately one dollar on TON may not have precisely the same executable value as its counterpart on Base at every moment.</p><p>If the transaction involves different stablecoins, such as USDt and USDC, the quoted result also reflects a token conversion rather than just movement between networks.</p><p>STON.fi displays an executable destination amount, which is more useful for evaluating the swap than assuming that every dollar-denominated token must always exchange at an exact 1:1 ratio.</p><h3>Liquidity and trade size</h3><p>The amount you’re exchanging can influence the available quote. A resolver may be able to offer attractive pricing for a smaller transaction but require a different rate when supplying substantially more liquidity.</p><p>Available inventory, market conditions, and transaction size can all contribute to this difference. Larger orders may also require different execution arrangements, depending on the protocol’s supported functionality and current liquidity.</p><p>These conditions can affect your effective exchange rate without appearing as a separate line labeled “liquidity fee.”</p><p>For a practical decision, it is better to examine the final quote than to estimate the result solely from the current market price of the source token.</p><h3>The number that matters most: net destination value</h3><p>When evaluating a STON.fi cross-chain transaction, start by expressing both sides of the exchange in the same reference currency. Then compare the value you’re giving up with the value you’re expected to receive.</p><p>A simplified calculation is:</p><p><strong>Effective transaction cost = Source reference value — Destination reference value + Additional costs not included in the quote</strong></p><p>To calculate the percentage:</p><p><strong>Effective cost (%) = Effective transaction cost / Source reference value × 100</strong></p><p>For example, if you exchange assets worth $1,000 and receive destination assets worth $997, the difference is $3. If an additional $0.25 in network costs is not already reflected in that quote, the effective total cost becomes $3.25, or 0.325% of the original reference value.</p><p>This calculation measures the economic difference relative to your chosen benchmark. It doesn’t identify exactly how much STON.fi, a resolver, or the underlying networks collected individually.</p><p>That distinction prevents a common mistake: counting an embedded fee once through the reduced destination amount and then subtracting it a second time.</p><p>The formula is most useful when both reference values are measured at approximately the same time. If the market value of either asset changes significantly between observations, part of the apparent cost difference may actually reflect market movement.</p><h3>Practical example: comparing two STON.fi quotes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tLuKA7Vdg5nuPXBlAWvRdw.png" /></figure><p>Consider a hypothetical TON-to-Base transaction in which you’re exchanging 1,000 USDt on TON for USDt on Base. Suppose you observe two STON.fi quotes at different moments and want to determine which provides the better economic result.</p><p>For this example, assume that each USDt has a reference market value of exactly $1. The figures below are illustrative and are not taken from live STON.fi transactions.</p><p>At first glance, Quote A has the lower additional network expense. Its assumed gas cost is only $0.25, compared with $0.50 for Quote B. Looking exclusively at that number could make Quote A appear more attractive.</p><p>The destination amounts tell a different story.</p><h3>Calculating Quote A</h3><p>The starting reference value is $1,000, while the destination amount is worth $996.80. That creates a value difference of $3.20 before accounting for the additional gas expense.</p><p>Adding the hypothetical $0.25 network cost gives:</p><p><strong>$1,000 — $996.80 + $0.25 = $3.45</strong></p><p>The effective percentage cost is:</p><p><strong>$3.45 / $1,000 × 100 = 0.345%</strong></p><h3>Calculating Quote B</h3><p>Quote B delivers 998 USDt, worth $998 under our assumption. The difference from the original reference value is therefore $2.00, even though the additional network expense is higher.</p><p>Adding the hypothetical $0.50 gas cost gives:</p><p><strong>$1,000 — $998.00 + $0.50 = $2.50</strong></p><p>The effective percentage cost is:</p><p><strong>$2.50 / $1,000 × 100 = 0.250%</strong></p><h3>What the comparison reveals</h3><p>Quote B produces a better overall result despite its higher assumed gas expense. The improvement in the destination amount outweighs the additional network cost, leaving a $0.95 difference between the two effective totals.</p><p><strong>A lower visible fee doesn’t necessarily produce a lower effective transaction cost.</strong> The amount you receive, together with any genuinely additional expenses, determines the more useful comparison.</p><p>In the real STON.fi interface, you may not see multiple resolver offers presented as manually selectable alternatives. Omniston evaluates available quotes through its routing infrastructure, while you review the resulting transaction conditions.</p><p>You can still apply the same calculation when comparing quotes obtained at different moments or evaluating supported destination-asset configurations. Just remember that quotes can expire, and a previously observed result may no longer be executable.</p><h3>Following a TON-to-Base swap on STON.fi</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gk31i1o-byL4QxHpMid6xw.png" /></figure><p>The calculations become more useful when connected to an actual transaction workflow. STON.fi provides a dedicated TON-to-Base cross-chain guide that explains how supported assets can move between the two networks.</p><p>You can find that guide here:</p><p>STON.fi TON-to-Base Cross-Chain Swap Guide: <a href="https://ston.fi/cross-chain-swap-from-ton-to-base">https://ston.fi/cross-chain-swap-from-ton-to-base</a></p><p>Suppose you have USDt on TON and want to receive a supported stablecoin on Base. Rather than beginning with a calculation, start by confirming that the destination network and asset match what you actually need.</p><h3>Connecting the right wallets</h3><p>Open the official STON.fi application and connect your TON wallet. You’ll also need to configure a compatible receiving wallet or address for the Base network.</p><p>Before requesting a quote, verify that the receiving address is correct and that you control the destination wallet. Receiving the right quantity of tokens won’t help if they are sent to an address you cannot access.</p><h3>Reviewing the asset pair and quoted output</h3><p>Select TON as the source network and Base as the destination. Choose the relevant assets from the supported options, then enter the amount you want to exchange.</p><p>STON.fi uses Omniston to request the corresponding execution quote. Available routes depend on current asset support, liquidity, and resolver participation, so the presence of a network in the interface doesn’t guarantee that every possible token pair can be exchanged.</p><p>For an additional walkthrough focused on USDt, STON.fi also provides this guide:</p><p>How to Send USDT from TON to Base: <a href="https://ston.fi/how-to-send-usdt-from-ton-to-base">https://ston.fi/how-to-send-usdt-from-ton-to-base</a></p><p>Once the quote appears, compare the offered destination amount against the reference value of your source assets. Check whether any additional blockchain costs apply separately and make sure you’re not subtracting expenses that are already included in the conversion.</p><h3>Confirming and monitoring the transaction</h3><p>If the quote meets your requirements, you can approve the transaction through your connected wallet. Omniston then coordinates the corresponding cross-chain settlement according to the accepted execution conditions.</p><p>Because the operation involves two independent blockchains, completion may take longer than a standard swap on one network. Processing time depends on the settlement sequence and relevant blockchain conditions.</p><p>If the transaction remains pending, check its status before attempting an identical swap. Signing another transaction without understanding the first one’s state may create an unnecessary second operation.</p><h3>What happens if the cross-chain swap cannot complete?</h3><p>Cost comparisons usually focus on successful transactions, but the settlement mechanism matters too. A cheaper quote is less useful if you don’t understand what happens when the required execution conditions cannot be fulfilled.</p><p>Omniston uses linked Hashed Timelock Contracts, or HTLCs, to coordinate cross-chain settlement. An HTLC locks assets under conditions involving a cryptographic secret and a time limit, allowing the corresponding operations on two independent blockchains to be linked.</p><p>In a simplified STON.fi TON-to-Base scenario, the source assets are committed to a conditional contract on TON, while the resolver commits the agreed destination assets to a matching contract on Base. Both contracts use the same cryptographic condition, allowing the parties to settle their corresponding sides of the exchange when that condition is fulfilled.</p><p>If the process cannot complete within the required window, the contracts provide recovery paths based on their timelock rules. The design is intended to prevent one side of an individual atomic settlement from completing permanently without its corresponding fulfillment.</p><p>There are important limitations to understand. A refund is not necessarily instantaneous, and network fees already consumed during blockchain operations may not be recoverable. Larger orders may also be divided into independent partial fills, allowing successful portions to settle while unsuccessful portions follow their own recovery paths.</p><p>Atomic settlement therefore describes how the exchange is coordinated, not a promise that every transaction will finish immediately or without any expense.</p><p>When evaluating STON.fi, you should consider these execution conditions alongside the quoted destination amount rather than treating the lowest apparent fee as the only measure of transaction quality.</p><h3>Three mistakes that can distort your cost calculation</h3><p>Even with an executable quote, it’s possible to misunderstand what the numbers represent. Three mistakes are particularly worth avoiding.</p><p><strong>Looking only at the blockchain fee.</strong> A small gas estimate can make a transaction appear inexpensive, but the destination amount may already reflect a less favorable conversion rate or additional execution costs. Compare the full output against a consistent reference value instead of focusing on one fee line.</p><p><strong>Subtracting embedded expenses twice.</strong> If resolver pricing and protocol fees are already reflected in the quoted destination amount, deducting them again produces an exaggerated estimate. Only add costs that genuinely fall outside the quote.</p><p><strong>Ignoring your next transaction.</strong> Receiving a stablecoin on Base may be only one stage of your intended activity. If you later transfer those tokens or interact with another smart contract, that operation may require additional network gas that isn’t part of the STON.fi swap. Keep immediate execution costs separate from future expenses.</p><p>These mistakes all come from treating individual transaction details in isolation. A better comparison considers what you spend, what you receive, and which additional operations remain necessary.</p><h3>What to check before confirming on STON.fi</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K-aH_mXBR8oD7Er2LBJ_hg.png" /></figure><p>You don’t need to calculate every underlying protocol expense individually to make an informed decision. A short review of the quote and transaction details can help you recognize the most important risks and cost differences.</p><p>Before signing, check:</p><ul><li><strong>Source asset and amount:</strong> Confirm that you’ve selected the intended token on TON and entered the correct quantity.</li><li><strong>Destination network and token:</strong> Make sure Base and the receiving asset are exactly what you need.</li><li><strong>Receiving wallet:</strong> Verify the destination address and your ability to access it.</li><li><strong>Quoted destination value:</strong> Compare the expected output against the reference value of the assets you’re spending.</li><li><strong>Additional expenses:</strong> Identify fees already included in the quote and any separate network costs.</li><li><strong>Quote validity:</strong> Review the current execution conditions immediately before confirming.</li></ul><p>After signing, monitor the transaction through STON.fi and the relevant blockchain records if necessary. If settlement is delayed or a recovery process becomes applicable, use the available transaction information to understand the status before attempting further actions.</p><p><strong>The practical goal is simple: compare the usable value that reaches your destination wallet, not just the fee that looks smallest on the screen.</strong> STON.fi and Omniston provide the quoted execution framework, while understanding its costs helps you decide whether the proposed exchange meets your needs.</p><h3>Frequently Asked Questions</h3><h3>Are cross-chain swaps on STON.fi free?</h3><p>No. Cross-chain swaps involve blockchain processing resources, liquidity provision, and potentially protocol-related execution costs. Some expenses may appear separately, while others are already incorporated into the quoted destination amount. The most useful way to evaluate a transaction is to review its complete economic outcome rather than looking only for a single displayed fee.</p><h3>Why can two STON.fi quotes show different destination amounts?</h3><p>Different quotes can reflect changing liquidity availability, resolver pricing, transaction size, or market conditions. Even dollar-denominated stablecoins may not trade at precisely identical values across networks. Since execution offers can change over time, a quote observed earlier should not be treated as permanently available.</p><h3>Is the lowest network fee always the cheapest swap?</h3><p>Not necessarily. A transaction with a lower gas expense may offer a less favorable destination amount, producing a higher overall cost. Compare the reference value of the source assets with the destination value received, then account for additional expenses that are not already embedded in the quote.</p><h3>What is the difference between a swap fee and price impact?</h3><p>A fee is an explicit or embedded charge associated with transaction processing or execution. Price impact describes how the effective exchange price changes because of transaction size and available liquidity. Both can influence the final output, but price impact should not automatically be added as a separate expense if its effect is already reflected in the quote.</p><h3>Does Omniston guarantee the best exchange rate?</h3><p>Omniston evaluates executable pricing from its connected liquidity infrastructure, but this does not guarantee the best possible rate across every source in the wider market. Route availability also depends on supported assets, connected resolvers, and current execution conditions. Always review the actual STON.fi quote before signing.</p><h3>Can I exchange USDt from TON into a stablecoin on Base using STON.fi?</h3><p>STON.fi documents a TON-to-Base cross-chain workflow, including a dedicated guide for USDt transfers. The exact destination assets and available routes depend on current support and liquidity conditions. Select the intended asset and destination network in the live STON.fi interface, then verify that an executable quote is available.</p><h3>What happens to my assets if a STON.fi cross-chain swap fails?</h3><p>Omniston uses linked HTLC settlement conditions that provide recovery paths when an individual atomic swap cannot complete. Depending on the stage and applicable timelock rules, recovery may require additional processing time. Blockchain fees already consumed during attempted execution may not be recoverable, and independently completed partial fills may remain settled.</p><h3>What should I check first when comparing two STON.fi cross-chain quotes?</h3><p>Start with the destination amount and the exact asset you’re receiving. Compare its reference value with the source assets you’re spending, then account for network expenses not already included in the quote. Finally, verify the destination wallet, current execution conditions, and quote validity before deciding whether to proceed.</p><h3>Sources and Further Reading</h3><ol><li><strong>STON.fi — TON-to-Base Cross-Chain Swap Guide.</strong> Official guide to the TON-to-Base transaction workflow and supported cross-chain functionality: <a href="https://ston.fi/cross-chain-swap-from-ton-to-base">https://ston.fi/cross-chain-swap-from-ton-to-base</a></li><li><strong>STON.fi — How to Send USDT from TON to Base.</strong> Practical resource for a stablecoin transfer between TON and Base: <a href="https://ston.fi/how-to-send-usdt-from-ton-to-base">https://ston.fi/how-to-send-usdt-from-ton-to-base</a></li><li><strong>STON.fi — Omniston Cross-Chain Execution.</strong> Official overview of RFQ infrastructure, resolver liquidity, fee architecture, and HTLC-based settlement: <a href="https://ston.fi/omniston">https://ston.fi/omniston</a></li><li><strong>STON.fi Blog — Omniston Explained: How Cross-Chain Swaps on TON Work Without a Bridge.</strong> Technical explanation of resolvers, paired HTLCs, and recovery paths: <a href="https://blog.ston.fi/omniston-explained-how-cross-chain-swaps-on-ton-work-without-a-bridge/">https://blog.ston.fi/omniston-explained-how-cross-chain-swaps-on-ton-work-without-a-bridge/</a></li><li><strong>STON.fi Blog — TON to Base, BNB Chain, and Polygon: How Cross-Chain Crypto Swaps Actually Work.</strong> Examples of cross-chain execution and destination-side settlement: <a href="https://blog.ston.fi/ton-to-base-bnb-chain-and-polygon-how-cross-chain-crypto-swaps-actually-work/">https://blog.ston.fi/ton-to-base-bnb-chain-and-polygon-how-cross-chain-crypto-swaps-actually-work/</a></li><li><strong>STON.fi Blog — How STON.fi’s TON Cross-Chain Works: A Guide for Beginners.</strong> Accessible explanation of conditional settlement and cross-chain transaction behavior: <a href="https://blog.ston.fi/how-ston-fis-ton-cross-chain-works-a-guide-for-beginners/">https://blog.ston.fi/how-ston-fis-ton-cross-chain-works-a-guide-for-beginners/</a></li><li><strong>STON.fi Developer Documentation — Omniston Swap Overview.</strong> Technical reference for quotes, routes, settlement status, and transaction parameters: <a href="https://docs.ston.fi/developer-section/omniston/swap/overview">https://docs.ston.fi/developer-section/omniston/swap/overview</a></li><li><strong>STON.fi Developer Documentation — Resolver Guide.</strong> Explanation of how resolvers submit and update executable quotes and interact with the RFQ system: <a href="https://docs.ston.fi/developer-section/omniston/resolvers/guide">https://docs.ston.fi/developer-section/omniston/resolvers/guide</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd886759174a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Find the Best Available Swap Route on STON.fi with Omniston]]></title>
            <link>https://medium.com/@ivan.zimanov/how-to-find-the-best-available-swap-route-on-ston-fi-with-omniston-e8cf6acd9f2c?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8cf6acd9f2c</guid>
            <category><![CDATA[omniston]]></category>
            <category><![CDATA[swap]]></category>
            <category><![CDATA[cross-chain-swap]]></category>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Sat, 17 Oct 2026 10:58:37 GMT</pubDate>
            <atom:updated>2026-10-17T10:58:37.965Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A practical guide to liquidity aggregation, smart routing, price impact, and better swap execution on STON.fi.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zgtESdX0jQeIv4MH7S91nQ.png" /></figure><p>A token swap on STON.fi is not simply a matter of choosing two assets and accepting a fixed exchange rate. The amount you receive depends on available liquidity, trade size, routing options, and execution conditions.</p><p>STON.fi addresses this complexity through <strong>Omniston</strong>, its integrated liquidity aggregation protocol. Omniston searches connected liquidity sources, evaluates executable quotes, and helps identify a suitable route for your swap.</p><p>You don’t need to understand every liquidity pool or manually construct a complicated transaction. However, knowing how Omniston finds routes and how to evaluate its quotes can help you make better trading decisions.</p><h3>Why the same token pair can produce different swap results</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lB9m0S2INGlsr0bH5Ar0QQ.png" /></figure><p>Imagine swapping TON for STON on STON.fi. You might expect the same pair to have one exchange rate, but decentralized liquidity does not work that way.</p><p>In automated market maker (AMM) pools, prices depend on the assets available in each pool, the pricing mechanism, and the size of your transaction. A pool with substantial liquidity may handle a trade with relatively little price impact, while a smaller pool can produce a less favorable execution price.</p><p>For a broader explanation of <a href="https://whatisdex.com/">DEX pricing, liquidity pools, and swap execution fundamentals</a>, it helps to understand how AMMs calculate token exchange rates. On STON.fi, these fundamentals become especially important because Omniston can evaluate liquidity beyond a single pool.</p><p>Several factors can change your expected output:</p><ul><li><strong>Liquidity depth:</strong> Deeper available liquidity generally absorbs larger orders more efficiently.</li><li><strong>Price impact:</strong> Larger transactions can move the execution price further along an AMM’s pricing curve.</li><li><strong>Trading fees:</strong> Different routes may involve different fee structures.</li><li><strong>Routing:</strong> A direct swap is not necessarily better than a route involving intermediate tokens.</li><li><strong>Liquidity availability:</strong> Connected sources and resolver quotes can change as market conditions evolve.</li></ul><p>Consequently, selecting the most suitable STON.fi route requires considering the entire transaction rather than relying on a token pair’s displayed market price.</p><h3>Omniston: the routing infrastructure behind STON.fi swaps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0DDZXTjJtvlRqJAVpsPEEg.png" /></figure><p>Omniston is STON.fi’s liquidity aggregation protocol. It connects liquidity discovery and execution through a Request for Quote (RFQ) mechanism.</p><p>Instead of evaluating only one STON.fi liquidity pool, Omniston can consider multiple connected AMM liquidity sources and quotes from specialized market participants known as <em>resolvers</em>.</p><p>Resolvers can provide executable swap offers and compete to supply favorable terms. Omniston evaluates eligible quotes according to the requested assets, amount, and execution constraints.</p><p>The distinction between STON.fi and Omniston is straightforward:</p><p><strong>STON.fi is where you interact with the swap. Omniston is the infrastructure that helps discover how the swap can be executed.</strong></p><p>The STON.fi interface integrates this routing functionality, allowing you to request a swap without manually visiting different liquidity sources.</p><p>Importantly, Omniston searches its connected and eligible sources. It cannot guarantee the best result across every possible source in the entire market, including sources outside its available routing network.</p><h3>From quote request to completed swap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlbMbt38v6AZ-KV0-zf2WA.png" /></figure><p>Although the STON.fi interface simplifies the experience, a swap involving Omniston follows several technical stages.</p><ol><li><strong>Quote request:</strong> You select the input token, output token, and amount on STON.fi. These parameters form the basis of an RFQ.</li><li><strong>Liquidity evaluation:</strong> Omniston requests quotes from connected sources and resolvers. The available responses depend on liquidity, supported routes, and trade requirements.</li><li><strong>Route selection:</strong> The protocol evaluates eligible offers, considering output amounts and execution parameters. Quotes may be updated as more favorable offers arrive.</li><li><strong>Transaction preparation:</strong> Once a quote is selected, the relevant transaction instructions are prepared for wallet approval.</li><li><strong>Execution and settlement:</strong> After you authorize the transaction, the applicable smart contracts process the swap. Its status can then be tracked through the settlement flow.</li></ol><p>STON.fi keeps this process accessible through one swap interface. Nevertheless, the quoted outcome still depends on the conditions attached to the selected route.</p><p>A quote is not an unconditional promise that a transaction will succeed at any future time.</p><h3>Direct routes versus multi-hop routes on STON.fi</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHf1_1jbJqYh4QdKXVIKPA.png" /></figure><p>Omniston can evaluate different paths between the assets you want to exchange.</p><p>A <strong>direct route</strong> exchanges the input token for the output token in one swap step. For example:</p><p><strong>TON → STON</strong></p><p>A <strong>multi-hop route</strong> introduces one or more intermediate assets:</p><p><strong>TON → USDT → STON</strong></p><p>In the second example, Omniston evaluates whether converting TON into USDT before obtaining STON offers better execution conditions than a direct conversion.</p><p>A multi-hop route might benefit from deeper liquidity along its individual steps. However, additional swaps can introduce extra trading fees, execution requirements, and blockchain costs.</p><p>The correct comparison is therefore not simply the number of steps. It is the expected final output under the complete route’s conditions.</p><p>STON.fi lets the aggregation infrastructure handle this complexity while you evaluate the quote presented through the interface. Where route details are available, they can help explain why one path was selected.</p><h3>Why larger swaps can change the preferred route</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qc6F980nlUQePKwCHpfFpg.png" /></figure><p>Trade size is one of the most important inputs to Omniston’s routing process.</p><p>Suppose a STON.fi liquidity pool can comfortably execute a small TON-to-STS token swap. Increasing the input amount substantially might produce a worse average exchange rate because the transaction consumes more of the pool’s available liquidity.</p><p>Omniston can respond by evaluating alternative connected liquidity sources or different routing paths.</p><p>This creates an important relationship:</p><p><strong>The preferred route for a small trade may not be the preferred route for a large trade involving exactly the same tokens.</strong></p><p>Larger orders may also benefit from splitting liquidity across eligible execution paths where supported, although such routing is not guaranteed for every pair or transaction.</p><p>A useful STON.fi exercise is to compare quotes at several input amounts. Observe how the expected output changes relative to the input rather than assuming that doubling the trade size should double the tokens received.</p><h3>A hypothetical STON.fi swap: comparing two execution paths</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*16pZphCJ3vvsL3NqagyHqg.png" /></figure><p>Consider a hypothetical trade involving 100 TON exchanged for STON.</p><p>For illustration, assume Omniston evaluates two available routes and produces these results:</p><p>Route and Estimated output:</p><p>TON → STON = 950 $STON</p><p>TON → USDT → STON = 970 $STON</p><p><em>These figures are entirely illustrative, not live STON.fi quotes or actual token prices.</em></p><p>In this scenario, the second route offers approximately 2.1% more STON than the direct route, assuming the estimated outputs already account for the respective swap fees.</p><p>A trader might initially assume that the shortest route must be the cheapest. The hypothetical comparison demonstrates why that assumption can be misleading.</p><p>However, the additional 20 STON does not automatically settle the decision. You must still consider the route’s blockchain fees, minimum received amount, quote validity, and execution requirements.</p><p>If liquidity conditions change, Omniston may return different quotes or select another path. A previously attractive route may no longer be available when you attempt the trade.</p><p>The objective is to evaluate the best available executable terms for your particular transaction, not to identify one universally superior path.</p><h3>How to evaluate an Omniston route in the STON.fi interface</h3><p>You can apply this knowledge directly without interacting with Omniston’s developer APIs.</p><h3>A practical route evaluation</h3><ol><li><strong>Open STON.fi and connect your wallet.</strong> Use the official STON.fi application and navigate to the Swap interface.</li><li><strong>Check the routing configuration.</strong> Ensure Omniston routing is enabled where the interface provides that setting.</li><li><strong>Choose the tokens.</strong> Select your input and output assets carefully, verifying token identities and the intended network.</li><li><strong>Enter the trade amount.</strong> Allow the interface to retrieve an available quote. If the quote refreshes, evaluate the latest terms.</li><li><strong>Review the output and execution details.</strong> Examine the expected amount, minimum received, applicable fees, and any available route information.</li><li><strong>Compare trade sizes.</strong> Try a smaller amount or another reasonable transaction size to see whether the effective exchange rate changes significantly.</li><li><strong>Confirm only after reviewing the wallet transaction.</strong> Check that the displayed transaction matches your intended swap before authorizing it.</li></ol><p>Interface labels and available route details may change as STON.fi develops, but the underlying evaluation remains relevant.</p><h3>Your pre-swap checklist</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b0Kdc-Czom5HCdBufuW8pw.png" /></figure><p>Before approving a STON.fi swap, verify:</p><ul><li><strong>Estimated output:</strong> How many tokens does the current quote expect to deliver?</li><li><strong>Minimum received:</strong> What is the lowest output permitted by the selected slippage protection?</li><li><strong>Price impact:</strong> How much does the trade size affect the effective exchange rate?</li><li><strong>Fees:</strong> What trading and blockchain costs apply, and is sufficient TON available for execution?</li><li><strong>Execution conditions:</strong> Is the quote still valid, and are there route-specific constraints or warnings?</li></ul><p>Minimum received is especially important. Omniston’s swap settlement model supports minimum output parameters designed to protect against execution below the accepted threshold.</p><p>If the necessary conditions cannot be satisfied, the swap may fail or abort rather than execute as expected. Blockchain fees may still be incurred.</p><p>Likewise, estimated blockchain costs should not be confused with the exact eventual cost of every transaction.</p><p>A favorable displayed output is meaningful only when its associated execution conditions are acceptable.</p><p><strong>The practical takeaway:</strong> Use STON.fi’s Omniston routing to discover available swap opportunities, then evaluate the actual quote rather than focusing only on the advertised token price. Compare trade sizes when appropriate, inspect the minimum received amount, and confirm that the expected benefit justifies the execution costs.</p><h3>Frequently asked questions</h3><h3>Does Omniston always find the best possible swap price?</h3><p>No. Omniston evaluates connected liquidity sources and eligible resolver quotes to find competitive execution terms. It cannot evaluate every source in existence or guarantee a globally optimal result. Available routes also depend on the token pair, trade size, and current liquidity conditions.</p><h3>Can STON.fi use multiple liquidity pools for one swap?</h3><p>Yes. Through Omniston, STON.fi can access routing paths involving different liquidity sources. Multi-hop execution can involve successive swap steps, potentially improving the final output compared with a direct pool. The exact route depends on what Omniston can quote and execute for the requested transaction.</p><h3>Is a multi-hop route always better than a direct route?</h3><p>No. Intermediate swaps may improve access to liquidity, but they can also introduce additional fees and execution complexity. A direct route may deliver a better result for a particular order. Omniston evaluates available quotes rather than assuming that more routing steps automatically produce better pricing.</p><h3>Does Omniston eliminate slippage?</h3><p>No. Omniston can improve execution opportunities through liquidity aggregation, but that does not mean every transaction experiences zero slippage or price impact. The minimum received amount and applicable settlement conditions remain important safeguards, particularly when liquidity is limited or prices change.</p><h3>Why does my STON.fi quote change when I increase the amount?</h3><p>Larger transactions interact differently with available liquidity. They may produce greater price impact, change the effective execution rate, or make another route more competitive. Omniston therefore evaluates the specified transaction amount rather than assuming that a quote for a smaller swap scales proportionally.</p><h3>What should I do if STON.fi shows an unfavorable Omniston quote?</h3><p>First, verify the correct tokens and amount. Review price impact, minimum received, and execution fees. You can also compare a smaller trade size or refresh the quote to assess current conditions. If the available terms remain unattractive, avoiding the transaction may be preferable to accepting excessive execution costs.</p><h3>Sources and Further Reading</h3><ol><li><strong>STON.fi Omniston Protocol Documentation</strong> — Official introduction to liquidity aggregation and RFQ-based routing: <a href="https://docs.ston.fi/developer-section/omniston">https://docs.ston.fi/developer-section/omniston</a></li><li><strong>STON.fi Omniston Overview</strong> — Connected liquidity sources, quote discovery, and settlement models: <a href="https://docs.ston.fi/developer-section/omniston/overview">https://docs.ston.fi/developer-section/omniston/overview</a></li><li><strong>STON.fi Omniston Swap Overview</strong> — Quote parameters, swap routes, minimum received, and execution requirements: <a href="https://docs.ston.fi/developer-section/omniston/swap/overview">https://docs.ston.fi/developer-section/omniston/swap/overview</a></li><li><strong>STON.fi Omniston Resolvers</strong> — How resolvers provide quotes and participate in route execution: <a href="https://docs.ston.fi/developer-section/omniston/resolvers">https://docs.ston.fi/developer-section/omniston/resolvers</a></li><li><strong>Why Omniston Matters: Smarter Liquidity for TON DeFi</strong> — Official STON.fi explanation of Omniston integration and liquidity fragmentation: <a href="https://blog.ston.fi/why-omniston-matters-smarter-liquidity-for-ton-defi/">https://blog.ston.fi/why-omniston-matters-smarter-liquidity-for-ton-defi/</a></li><li><strong>Cross-DEX Swaps Using Omniston</strong> — STON.fi’s explanation of multi-step routing and aggregated liquidity: <a href="https://blog.ston.fi/cross-dex-swaps-via-ton/">https://blog.ston.fi/cross-dex-swaps-via-ton/</a></li><li><strong>How Tax Tokens Trade: Quotes, Slippage, and What Really Lands in Your Wallet</strong> — STON.fi guidance on quote interpretation, minimum received, fees, and price impact: <a href="https://blog.ston.fi/how-tax-tokens-trade-quotes-slippage/">https://blog.ston.fi/how-tax-tokens-trade-quotes-slippage/</a></li><li><strong>What Is a DEX?</strong> — Introductory reference explaining decentralized trading, AMMs, liquidity pools, and swap execution: <a href="https://whatisdex.com/">https://whatisdex.com/</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8cf6acd9f2c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Can STON.fi Temporarily Pause the Interface During a TON Outage?]]></title>
            <link>https://medium.com/@ivan.zimanov/why-can-ston-fi-temporarily-pause-the-interface-during-a-ton-outage-36551f5135a2?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/36551f5135a2</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ston-fi-project]]></category>
            <category><![CDATA[cross-chain-swap]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[stonfi]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 10:55:43 GMT</pubDate>
            <atom:updated>2026-09-28T10:55:43.464Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A frontend pause can stop new swap requests from being created while the underlying TON smart contracts and user-owned assets remain separate from the website itself.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9qhF9ajIeDZW1N24BPc5kQ.png" /></figure><p>STON.fi can temporarily pause swap functionality in its interface during a TON outage because the web application is not the blockchain. The frontend is a service operated by the STON.fi team, so it can stop offering a button or transaction-building flow when the network is unable to process transactions normally.</p><p>That does not mean STON.fi can simply switch TON off, reverse blockchain history, or take custody of tokens sitting in users’ wallets. The purpose of an interface pause is narrower: prevent additional users from launching transactions into conditions where execution may be heavily delayed, prices may change before execution, or transactions may need to fail and refund later.</p><p>STON.fi used exactly this type of precaution during the major TON disruption in August 2024. As transaction delays grew and TON later stopped producing blocks, STON.fi temporarily disabled swaps through app.ston.fi.</p><h3>The interface and the blockchain are two different layers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5de0Kg9WGxZFd-2aho02-g.png" /></figure><p>A decentralized exchange can have decentralized smart contracts while still presenting those contracts through a conventional website.</p><p>When you visit STON.fi, the interface helps you choose tokens, request or simulate a quote, prepare transaction parameters, connect a wallet, and send a request for signing. The actual asset movement happens after the signed transaction enters TON and reaches the relevant contracts.</p><p>It helps to separate the system into three layers:</p><ul><li><strong>Interface:</strong> app.ston.fi displays markets, quotes, controls, warnings, and transaction actions.</li><li><strong>Wallet:</strong> your wallet holds the keys and decides whether to authorize a transaction.</li><li><strong>TON and STON.fi contracts:</strong> the blockchain processes messages and executes the swap logic.</li></ul><p>STON.fi documentation for developers reflects this separation. Applications can use STON.fi APIs and SDKs to obtain routing information and generate transactions that interact with STON.fi contracts on TON.</p><p>Because the frontend is an application layer, its operators can decide not to create new swap requests when network conditions become unsafe or unpredictable.</p><p>That is very different from taking control of assets already held in a self-custodial wallet.</p><h3>Why an outage makes continuing to accept swaps risky</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xG2mOLOD0sm9Q9mMb58XFg.png" /></figure><p>Under normal conditions, you request a quote, approve the transaction, and TON processes the resulting sequence of messages quickly enough that the market state often remains reasonably close to the state used for the quote.</p><p>An outage breaks that assumption.</p><p>TON applications depend on nodes and validators to accept, propagate, order, validate, and include transactions in blocks. TON’s own documentation describes validators as the participants that reach consensus on blockchain state, while liteservers and other infrastructure connect client applications to the network.</p><p>If block production stops or the network becomes severely congested, signed transactions can remain unresolved for far longer than expected.</p><p>Imagine opening STON.fi and requesting a swap when TOKEN A is worth 10 TON. You approve the transaction, but TON then spends a long period processing a backlog. By the time the relevant contract messages execute, liquidity reserves may have changed because of other activity that reached the pool first.</p><p>The request you originally saw and the market state at execution are no longer the same thing.</p><p>During the August 2024 disruption, STON.fi reported delays reaching hours. According to its post-mortem, some transactions were ultimately declined because the execution conditions no longer satisfied their price protection.</p><h3>The risk grows in several ways</h3><p>During severe network disruption:</p><ul><li>quotes can become stale before execution</li><li>pool reserves may change while a transaction is waiting</li><li>refunds may also take time because refunds themselves require blockchain messages</li><li>users may incorrectly assume that a pending operation has failed and submit another transaction</li><li>interfaces may have difficulty reporting accurate transaction status while infrastructure is unstable</li></ul><p>Stopping new requests does not immediately solve transactions already in the queue. It does, however, stop the queue of potentially problematic user actions from growing through that interface.</p><h3>What STON.fi actually did during the 2024 TON outage</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HOikOoBqHCKpl0sBfqN9ug.png" /></figure><p>The August 2024 incident provides a concrete example.</p><p>STON.fi reported that heavy activity around the DOGS token claim generated a large volume of transactions and cross-shard messages. Transaction queues grew, delays increased, and TON eventually stopped producing blocks for several hours.</p><p>When the blockchain resumed, it had to process queued activity. Congestion then returned as user activity increased again.</p><p>STON.fi responded by temporarily disabling swap functionality on app.ston.fi. Its post-mortem states that the measure was intended to reduce problems associated with slippage and possible asset freezing while network conditions remained unstable. Liquidity operations were kept operational during that specific pause.</p><p>The sequence is important:</p><ol><li>TON experienced abnormal transaction delays.</li><li>The blockchain stopped producing blocks.</li><li>Block production resumed and queued transactions began processing.</li><li>Congestion returned.</li><li>STON.fi stopped accepting new swaps through its interface.</li><li>TON later suffered another shutdown.</li><li>Once the network had recovered, STON.fi reopened swap functionality.</li></ol><p>STON.fi reported that swaps were disabled for roughly 18 hours before normal functionality was restored.</p><p>The pause therefore acted as an operational safety measure around the interface, not as a claim that the frontend controlled TON itself.</p><h3>A paused button does not cancel transactions already sent</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ql62_RsZcpsX7kwn0wvTw.png" /></figure><p>This is one of the most important details to understand.</p><p>Suppose you sign a transaction at 12:00. At 12:03, STON.fi disables the swap interface because TON conditions have deteriorated.</p><p>The interface pause cannot reach backward in time and remove the transaction you already submitted from the network.</p><p>Your transaction may still:</p><ul><li>execute later</li><li>fail an execution condition</li><li>trigger refund logic</li><li>remain unresolved until TON catches up</li></ul><p>This is why a temporary interface pause is mainly preventative. It limits <em>new</em> exposure to problematic network conditions.</p><p>It should not be interpreted as a universal cancellation mechanism.</p><h3>Why slippage protection still matters during recovery</h3><p>DEX swaps do not simply promise to give you whatever amount was visible on the screen earlier.</p><p>STON.fi V2 swap payloads include a min_out value, which defines the minimum amount the swap must produce. STON.fi&#39;s Router documentation states that the swap fails if the calculated result would give the recipient less than this minimum.</p><p>This matters greatly after congestion.</p><p>Consider a transaction that was created from pool reserves at one moment but executes much later. If other swaps change the reserves first, the delayed trade may produce less output than originally expected.</p><p>The minimum output becomes a protection boundary.</p><p>A network recovery can therefore produce a strange experience from the user’s perspective: TON starts working again, yet an old swap does not necessarily complete at the price originally displayed.</p><p>That is not contradictory. Network availability and acceptable swap execution conditions are separate questions.</p><h3>Deadlines add another layer of protection</h3><p>The 2024 outage also influenced how STON.fi discussed future transaction protection. In its post-mortem, the project said it planned to introduce transaction deadlines so excessively delayed operations could be handled more safely.</p><p>That protection is now part of STON.fi DEX V2.</p><p>The current V2 Router specification includes a deadline field in swap payloads. It is stored as a uint64 timestamp representing the transaction&#39;s execution deadline. DEX V2 documentation also lists transaction deadlines among its swap and liquidity features.</p><p>These mechanisms are related, but they do different jobs.</p><p>A deadline does not make an outage disappear. Minimum output does not prevent a transaction from waiting. Refund logic does not guarantee that a refund is instant when the blockchain itself is stalled.</p><p>The frontend pause operates earlier in the process by discouraging creation of additional transactions until the underlying infrastructure becomes dependable again.</p><h3>Does pausing STON.fi mean the DEX has become centralized?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fXqKaan725k9xpRpnXAWQg.png" /></figure><p>Not in the simple sense that the website suddenly owns the exchange.</p><p>A decentralized protocol and an official frontend can have different control boundaries.</p><p>STON.fi smart contracts exist on TON. At the same time, app.ston.fi is an application maintained by a team. The team can decide what the application displays and which transactions it helps users prepare.</p><p>That distinction appears throughout decentralized finance. A protocol may be accessible through smart contracts, SDKs, APIs, third-party applications, or an official frontend. Controlling one access path is not automatically identical to controlling every contract interaction.</p><p>STON.fi publishes developer tooling specifically for programmatic interaction with its protocol. Its SDK is described as a wrapper around STON.fi contracts, with functionality including swaps and liquidity management.</p><p>So when evaluating a pause, ask precisely what has been disabled.</p><p><strong>A frontend swap pause</strong> means the official application is not facilitating new swaps.</p><p><strong>A network outage</strong> means TON itself cannot process transactions normally.</p><p><strong>A smart-contract restriction</strong> would be a separate protocol-level condition.</p><p>Those situations should not be treated as interchangeable.</p><h3>What should you do if STON.fi pauses swaps?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WcJGfumEB3cGAW2zi6AhQ.png" /></figure><p>If the official interface reports that swaps are paused because TON is experiencing problems, attempting to force the same action repeatedly is usually not useful.</p><p>A better checklist is:</p><ul><li>Check whether TON is producing blocks normally.</li><li>Check whether STON.fi has published an incident update.</li><li>Do not assume a pending transaction disappeared.</li><li>Avoid submitting duplicate transactions simply because the first one has not appeared yet.</li><li>Wait for confirmed network recovery before judging the final status of an in-flight swap.</li><li>Inspect the eventual transaction trace and wallet balances rather than relying only on an old interface status.</li></ul><p>TON maintains a documentation page listing network monitoring resources, including validator dashboards, TON Center status information, and the official validator status channel.</p><p>For someone using STON.fi, the practical lesson is simple: the interface is a gateway to on-chain execution, not the execution environment itself. When TON cannot reliably settle the messages behind a swap, disabling that gateway temporarily can prevent more users from entering an already unstable processing queue.</p><h3>Following one STON.fi swap through an outage</h3><p>Take a simple TON to Jetton swap.</p><p>You open STON.fi, select the assets, and obtain a simulated result. Modern STON.fi integrations can use the API to simulate the swap, receive routing information, construct the appropriate Router interaction, and generate the transaction parameters.</p><p>You then approve the transaction in your wallet.</p><p>At that point, the web interface has mostly completed its job. The transaction must now travel through TON and the relevant smart-contract message flow.</p><p>If TON stops producing blocks immediately afterward, STON.fi cannot make the blockchain process your transaction by keeping its swap page open.</p><p>Leaving the interface active would mainly allow additional users to create more transactions facing the same problem.</p><p>A temporary pause changes that.</p><p>New visitors cannot easily launch another swap from the official interface, while the team can monitor TON’s recovery and the state of existing transactions. Once reliable processing returns, the frontend can reopen.</p><p>That is why the pause is useful even though it does not itself repair the blockchain.</p><p><strong>Practical takeaway:</strong> if STON.fi pauses its interface during a TON outage, treat the pause as a warning about execution conditions, not as proof that your tokens have moved or disappeared. Check whether you already signed a transaction, follow its on-chain status after TON recovers, and only create a new swap once the previous operation and the network state are clear.</p><h3>Frequently Asked Questions</h3><h3>Can STON.fi stop the TON blockchain?</h3><p>No. STON.fi operates applications and smart contracts that use TON, but TON’s block production depends on its validator network. Temporarily disabling a feature on app.ston.fi stops that frontend from facilitating new actions. It does not switch TON on or off.</p><h3>Does an interface pause freeze the tokens in my wallet?</h3><p>No. Tokens held in a self-custodial wallet remain controlled by the wallet’s keys. The important exception is an operation you already authorized. If you signed and submitted a transaction before the pause, that transaction may still be waiting for blockchain processing.</p><h3>Why not leave swaps enabled and let users decide?</h3><p>During severe congestion or an outage, a newly submitted transaction may execute much later under different pool conditions. Users may also create duplicates when transactions appear stuck. Temporarily disabling the normal swap path can limit the number of new transactions entering uncertain conditions while the network recovers.</p><h3>Can a transaction still execute after the interface has been paused?</h3><p>Yes. If the transaction was already signed and broadcast before the pause, turning off the swap interface does not automatically remove it from TON’s transaction flow. Its final result depends on network recovery and the conditions encoded in the transaction.</p><h3>What happens if the price changes before a delayed STON.fi swap executes?</h3><p>STON.fi V2 swaps can specify min_out, the minimum acceptable output. If execution would return less than that amount, the swap can fail instead of accepting the worse result. The exact outcome also depends on the transaction path and applicable refund logic.</p><h3>Does STON.fi use transaction deadlines now?</h3><p>Yes. STON.fi DEX V2 documentation includes a transaction deadline in swap payloads. The deadline limits how long the encoded operation should remain valid for execution, providing another safeguard against transactions arriving too late.</p><h3>How can I tell whether TON itself is having problems?</h3><p>TON documentation lists several monitoring resources, including the validator dashboard, TON Center status metrics, TON Stat, Tonscan validation information, and official validator status channels. Looking at network-level sources helps distinguish a STON.fi interface problem from a broader TON disruption.</p><h3>What should I check when STON.fi reopens swaps after an outage?</h3><p>First confirm the final status of any transaction you submitted before the disruption. Check your wallet balances and transaction trace before sending the same swap again. Then request a fresh quote, because pool conditions and the expected output may have changed while TON was congested or offline.</p><h3>Sources and Further Reading</h3><p>STON.fi, “August 26–28 Transaction Delays: Causes and Future Prevention Strategies” — STON.fi’s post-mortem describing the August 2024 TON congestion, blockchain stoppages, temporary swap pause, recovery, and planned protections: <a href="https://blog.ston.fi/links/transaction-delays-on-ton/?utm_source=chatgpt.com">blog.ston.fi/links/transaction-delays-on-ton/</a></p><p>STON.fi DEX V2 Router documentation — Technical specification for V2 swap payloads, including deadline, min_out, refund addresses, and Router message handling: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/router?utm_source=chatgpt.com">docs.ston.fi/developer-section/dex/smart-contracts/v2/router</a></p><p>STON.fi DEX V2 documentation — Overview of V2 functionality, including transaction deadlines and custom refund handling: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2?utm_source=chatgpt.com">docs.ston.fi/developer-section/dex/smart-contracts/v2</a></p><p>STON.fi V2 Swap Examples — Examples of direct swaps, routed swaps, and refund behavior when swap conditions cannot be satisfied: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/examples/swap?utm_source=chatgpt.com">docs.ston.fi/developer-section/dex/smart-contracts/v2/examples/swap</a></p><p>STON.fi V2 Swap SDK documentation — Current production workflow for simulating a swap, resolving Router metadata, and generating on-chain transaction parameters: <a href="https://docs.ston.fi/developer-section/dex/sdk/v2/swap?utm_source=chatgpt.com">docs.ston.fi/developer-section/dex/sdk/v2/swap</a></p><p>STON.fi SDK repository — Official developer SDK for interacting with STON.fi DEX contracts, swaps, and liquidity functions: <a href="https://github.com/ston-fi/sdk?utm_source=chatgpt.com">github.com/ston-fi/sdk</a></p><p>TON Documentation, Network Status — Official list of monitoring resources for TON network, validator, latency, and infrastructure status: <a href="https://docs.ton.org/ecosystem/status?utm_source=chatgpt.com">docs.ton.org/ecosystem/status</a></p><p>TON Documentation, Blockchain Foundations — Overview of TON validators, consensus, nodes, liteservers, and how applications communicate with the blockchain: <a href="https://docs.ton.org/v3/guidelines/dapps/transactions/foundations-of-blockchain?utm_source=chatgpt.com">docs.ton.org/v3/guidelines/dapps/transactions/foundations-of-blockchain</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36551f5135a2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Use STON.fi Cross-Chain When the Source and Destination Tokens Differ]]></title>
            <link>https://medium.com/@ivan.zimanov/how-to-use-ston-fi-cross-chain-when-the-source-and-destination-tokens-differ-cf127e6611a1?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf127e6611a1</guid>
            <category><![CDATA[ston-fi-project]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crosschain]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Mon, 28 Sep 2026 10:54:42 GMT</pubDate>
            <atom:updated>2026-09-28T10:54:42.923Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bFyZFZsrkH8FGDcZrMatbA.png" /></figure><p>A cross-chain swap does not have to mean moving the same token from one blockchain to another. With STON.fi cross-chain execution through Omniston, you can request one asset on the source network and a different asset on the destination network, provided that the route is currently supported and a resolver can quote it.</p><p>That distinction changes how you should think about the transaction. You are not simply transferring a token between networks. You are exchanging one asset for another while also changing the blockchain on which your value ends up.</p><p>For example, the conceptual route might be:</p><p><strong>Token A on TON -&gt; Token B on Base</strong></p><p>instead of:</p><p><strong>Token A on TON -&gt; Token A on Base</strong></p><p>The first is both an asset conversion and a cross-chain movement. Omniston is designed to coordinate those two jobs inside one execution flow rather than requiring you to bridge first and swap afterward. STON.fi describes its current cross-chain architecture as resolver-based execution using linked Hashed Timelock Contracts, or HTLCs.</p><h3>The key idea: you request what you want to receive</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zQ3LmIPWxFn6C07LvVOQuQ.png" /></figure><p>A traditional bridge usually starts with the asset you own and asks how to represent that same value on another network. Depending on the bridge architecture, that may involve locking an asset on one chain and creating or releasing a corresponding representation elsewhere.</p><p>A token-to-token cross-chain swap asks a different question:</p><p><strong>What asset do you have now, and what asset do you actually want at the destination?</strong></p><p>Suppose you hold Token A on TON but your goal is Token B on another supported blockchain. Converting Token A into a bridged version of itself may not help much if you would immediately need another swap after arriving.</p><p>A direct cross-chain quote can instead describe the full desired result:</p><ul><li>source blockchain</li><li>source asset</li><li>amount being sent</li><li>destination blockchain</li><li>destination asset</li><li>receiving address</li></ul><p>Omniston sends the request to resolvers capable of supplying destination-side liquidity. Resolvers return executable quotes, and the selected route determines how much of the requested destination asset you will receive.</p><p>The important mental shift is simple: <strong>the destination token does not have to mirror the source token.</strong></p><p>It is the requested output of an exchange.</p><h3>Why changing the token matters</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iW8fffTMAIsXTHu-qvZEOg.png" /></figure><p>Crossing a blockchain boundary and changing an asset at the same time introduces more variables than a same-token transfer.</p><p>Imagine that you hold a stablecoin on the source network but want a volatile token on the destination network. The requested amount of the destination token now depends not only on cross-chain execution, but also on the exchange rate between the two assets.</p><p>The third route is the one discussed here.</p><p>It combines two decisions that are often handled separately: where you want your funds to end up and what you want to own when they arrive.</p><p>That can remove an intermediate operation, but it also means you should judge the route by its <strong>final destination output</strong>, not merely by whether value successfully moved between chains.</p><h3>What Omniston does with the request</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bWI2Ew_IrOCmq0qsernd_A.png" /></figure><p>STON.fi uses Omniston as its execution and aggregation layer. For cross-chain transactions, the protocol uses a Request for Quote model rather than requiring one universal liquidity pool to contain every possible cross-chain token combination.</p><p>When you define the source and destination assets, Omniston can broadcast the request to resolvers. These are independent liquidity providers that can quote against the request using their own inventory and pricing.</p><p>A simplified flow looks like this:</p><ol><li>You specify the source chain, source token, destination chain, destination token, and amount.</li><li>Omniston requests quotes from eligible resolvers.</li><li>Resolvers calculate what destination amount they can provide.</li><li>An executable quote is selected.</li><li>Source-side and destination-side assets are locked through linked HTLCs.</li><li>The linked settlement completes, or the timelock mechanism allows the locked assets to be refunded.</li></ol><p>The resolver therefore does more than relay your original token. It supplies the asset requested on the destination side.</p><p>STON.fi’s current Omniston page describes destination liquidity as resolver-provided liquidity supplied per order rather than inventory that an integrator must pre-fund. It also states that the cross-chain settlement uses linked HTLC contracts and settles atomically or refunds the parties.</p><h3>You are not performing two independent swaps</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*95HA6mnRGfskLVVbchMtbQ.png" /></figure><p>It is tempting to imagine a different-token cross-chain route as two conventional trades joined together:</p><p><strong>Token A -&gt; bridge asset -&gt; Token B</strong></p><p>That mental model can be misleading for Omniston.</p><p>The resolver model is based around the requested input and output. If a resolver accepts the order, it commits destination-side liquidity corresponding to the quote. The linked HTLCs then coordinate settlement across the independent blockchains.</p><p>Two contracts share a cryptographic condition known as a hashlock. The destination-side asset can be claimed when the required secret is revealed, and that same secret allows the resolver to claim the source-side asset. If settlement cannot complete within the permitted period, the timelock provides the refund path.</p><p>That is why the source and destination assets can differ.</p><p>The contracts do not need Token A to somehow transform into Token B while travelling between chains. Instead, the protocol coordinates an exchange between assets that already exist on their respective networks.</p><p>This distinction also explains why a resolver needs suitable liquidity on the destination side.</p><h3>How to make a different-token cross-chain swap on STON.fi</h3><p>From your perspective, the most important task is defining the destination correctly.</p><p>STON.fi’s cross-chain interface presents the operation as one coordinated swap flow. Current STON.fi materials describe cross-chain support across multiple networks, including TON, TRON and several EVM networks. The supported network list and available routes can change, so the interface and live quote should be treated as the current source of truth.</p><h3>1. Connect the required wallet or wallets</h3><p>Start from the official STON.fi interface and connect the wallet required for your source network.</p><p>When the source and destination use different wallet ecosystems, you may also need an appropriate receiving wallet for the destination network. For example, TON and an EVM network use different address systems.</p><p>Do not assume that a wallet address from one network can be used on another.</p><h3>2. Choose the source network and token</h3><p>Select the blockchain where your funds currently exist.</p><p>Then select the exact token you intend to spend and enter the amount.</p><p>The token’s network is part of its identity. A ticker alone is not enough to establish that two assets are interchangeable, especially when similarly named tokens exist across several networks.</p><h3>3. Choose a different destination token</h3><p>Now choose the blockchain where you want the transaction to settle.</p><p>Instead of selecting the same token again, select the asset you actually want to receive.</p><p>Conceptually, your request could now look like:</p><p><strong>Source:</strong> Token A on TON<br><strong>Destination:</strong> Token B on Base</p><p>At this point, you have defined both the cross-chain movement and the asset conversion.</p><h3>4. Check whether a quote is available</h3><p>The existence of both tokens in the wider crypto market does not guarantee that a usable cross-chain route exists.</p><p>Omniston needs an eligible resolver capable of quoting the request and supplying the required destination-side liquidity.</p><p>If a route can be quoted, review the output shown by the interface. If no eligible quote appears, do not assume that manually repeating the request will somehow create liquidity. The specific asset combination, networks, amount, resolver availability, and current market conditions all matter.</p><h3>5. Review the final output before signing</h3><p>This is the most important part of a different-token route.</p><p>Check:</p><ul><li>the source network</li><li>the exact source asset</li><li>the amount being spent</li><li>the destination network</li><li>the exact destination asset</li><li>the destination wallet address</li><li>the quoted amount you will receive</li><li>applicable fees</li><li>any displayed execution or quote conditions</li></ul><p>Do not compare only the number of tokens on each side. One unit of the source token may have a completely different value from one unit of the destination token.</p><p>The useful comparison is the economic value of the input against the quoted value of the final output.</p><h3>6. Confirm and follow the execution</h3><p>Once you approve the transaction, the cross-chain execution can proceed according to the quoted route.</p><p>The source asset and resolver-provided destination asset are coordinated through the cross-chain settlement mechanism. Settlement speed can depend on the blockchains involved, so a cross-chain transaction should not be expected to behave exactly like a normal TON-only swap.</p><p>Wait for the interface or relevant blockchain records to indicate that execution has completed before treating the destination balance as settled.</p><h3>What happens behind the interface</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JM9QiR7krY4OZNTjX_e2PA.png" /></figure><p>Consider a hypothetical route where you spend Token A on TON and request Token B on a supported EVM network.</p><p>You are not sending Token A to the EVM address.</p><p>Instead, the process can be understood as four linked actions.</p><p><strong>First, a quote is created.</strong> Omniston communicates the requested input and output to eligible resolvers.</p><p><strong>Second, a resolver commits to the destination side.</strong> The resolver agrees to provide a specified amount of Token B according to its quote.</p><p><strong>Third, the assets are conditionally locked.</strong> The source-side and destination-side legs are placed into linked HTLC arrangements.</p><p><strong>Fourth, the exchange settles.</strong> Once the shared cryptographic condition is satisfied, you receive Token B on the destination network and the resolver can claim Token A on the source network.</p><p>STON.fi describes this design as native asset execution without requiring wrapped tokens or a centralized intermediary during settlement.</p><p>The result you care about is therefore not “my original token arrived on another blockchain.”</p><p>It is:</p><p><strong>“I spent the quoted source asset and received the quoted destination asset on the requested destination blockchain.”</strong></p><h3>What can change the quote</h3><p>A different-token route has a real exchange rate, so the amount offered to you can change before you execute.</p><p>Several factors can affect whether a quote exists and what it looks like:</p><ul><li>the amount you want to exchange</li><li>market prices of the two assets</li><li>available resolver liquidity</li><li>source and destination networks</li><li>fees associated with the route</li><li>current competition among resolvers</li><li>how long the quote remains valid</li></ul><p>For that reason, an earlier quote should not be treated as a permanent exchange rate.</p><p>If you modify the amount, token, network, or other relevant swap parameters, review the refreshed quote rather than relying on the previous output.</p><p>Omniston’s same-chain aggregation documentation uses the same RFQ principle: a request is sent and available liquidity sources or resolvers respond with routes and quotes. Cross-chain execution extends the idea across separate networks.</p><h3>The mistakes most worth avoiding</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZcHHpS5erj25A_utG1w9FA.png" /></figure><p>Different-token cross-chain swaps are convenient precisely because several operations are being combined. That makes reviewing the final configuration more important, not less.</p><p><strong>Do not choose by ticker alone.</strong> Verify that the destination asset is the one you intended to receive on that particular blockchain.</p><p><strong>Do not paste an address without checking its network.</strong> The destination wallet must be compatible with the chosen destination chain.</p><p><strong>Do not treat a missing quote as a normal transfer problem.</strong> A token-to-token cross-chain route depends on resolver liquidity and supported execution paths.</p><p><strong>Do not judge the trade by token count.</strong> Receiving fewer units than you send can be perfectly normal when the destination asset has a higher unit price.</p><p><strong>Do not confuse a cross-chain swap with a direct token transfer.</strong> The original source token is not simply travelling to the destination address.</p><p>TON’s own documentation reinforces why network-specific token identity matters. Fungible tokens on TON use the Jetton model, with Jetton master and wallet contracts forming the token architecture. An asset on another blockchain follows that blockchain’s own token model instead.</p><h3>A practical STON.fi example</h3><p>Suppose your current portfolio contains Token A on TON, but the application you want to use next operates on Base and requires Token B.</p><p>A manual workflow could involve finding a bridge route, moving an intermediate asset to Base, waiting for it to arrive, opening a DEX on Base, approving another transaction, and swapping the intermediate asset into Token B.</p><p>A different-token STON.fi cross-chain route aims to express the actual objective directly:</p><p><strong>Spend Token A on TON -&gt; receive Token B on Base</strong></p><p>You select both sides, obtain the live quote, verify the Base receiving address and final Token B amount, then decide whether the quoted result is acceptable.</p><p>If a suitable resolver wins the RFQ, it provides the required Token B liquidity on the destination side. The linked settlement mechanism coordinates the exchange rather than requiring you to manually reproduce each intermediate step.</p><p>STON.fi gives the same general pattern in its cross-chain material: connect the appropriate wallets, choose the token and destination network, enter the amount, review swap details and fees, confirm, and wait for execution. Its TON-to-Base guide also specifically advises checking the source and destination networks, receiving wallet, destination asset, amount, exchange rate, fees, and price impact before confirming.</p><p><strong>Practical takeaway:</strong> when the source and destination tokens differ, read the STON.fi transaction from right to left before signing. First confirm exactly what token will arrive, on which network, at which address, and in what amount. Then verify what you are spending to obtain it. That keeps your attention on the actual purpose of the route rather than treating cross-chain execution as a simple transfer.</p><h3>Frequently Asked Questions</h3><h3>Can I use STON.fi cross-chain if I want a different token on the destination network?</h3><p>Yes, where a supported route and executable quote are available. Omniston’s resolver model allows a request to specify one source asset and another destination asset. A resolver can then quote the destination asset and supply the corresponding destination-side liquidity rather than merely moving an identical token between networks.</p><h3>Is the source token converted into the destination token inside a bridge?</h3><p>Not in the way a conventional wrapped-token bridge is normally understood. Omniston coordinates an exchange between source-side and destination-side assets using resolver liquidity and linked HTLCs. The destination asset already exists on its destination network. The resolver supplies it as part of the quoted exchange.</p><h3>Do I need to bridge first and swap afterward?</h3><p>Not necessarily. When STON.fi can produce a suitable cross-chain token-to-token quote, the requested asset conversion and blockchain change can be handled as one coordinated flow. If the desired route is unavailable, however, a separate route or set of operations may still be necessary.</p><h3>Why might a different-token route have no quote?</h3><p>A quote requires current support for the relevant networks and assets plus sufficient resolver interest and destination liquidity for the requested amount. Availability can therefore differ between token combinations and can change over time. The absence of a quote does not mean that either token itself is invalid.</p><h3>Is a different-token cross-chain swap the same as a normal DEX swap?</h3><p>No. A normal same-chain DEX swap changes the asset while settlement remains on one blockchain. A different-token cross-chain swap changes both the asset and the blockchain. That requires coordination between independent networks in addition to determining the exchange terms.</p><h3>What happens if the cross-chain settlement cannot complete?</h3><p>Omniston’s cross-chain design uses linked HTLCs with timelocks. STON.fi describes the mechanism as atomic settlement in which the swap settles across the linked sides or locked assets become refundable when the required settlement conditions are not completed within the permitted period.</p><h3>What should I check when the source and destination token tickers look similar?</h3><p>Verify the blockchain and token identity rather than trusting the ticker. Tokens with the same or similar symbols can exist through different contracts or token standards on different networks. Check that the destination asset shown by STON.fi is specifically the asset you want on the selected destination chain.</p><h3>What is the most important thing to verify before confirming a different-token STON.fi cross-chain swap?</h3><p>Check the final destination state: the destination blockchain, receiving wallet, exact asset, and quoted amount. Then verify the source asset and amount you are giving up. When those two sides match your intention and the live quote is acceptable, you can evaluate the cross-chain route as one complete exchange rather than as a simple transfer.</p><h3>Sources and Further Reading</h3><p>STON.fi Omniston — official overview of cross-chain execution, resolver liquidity, HTLC settlement, supported chains, and integration paths: <a href="https://ston.fi/omniston">https://ston.fi/omniston</a></p><p>STON.fi Blog, Omniston explained: how cross-chain swaps on TON work without a bridge — detailed explanation of resolvers, linked HTLCs, hashlocks, timelocks, and settlement: <a href="https://blog.ston.fi/omniston-explained-how-cross-chain-swaps-on-ton-work-without-a-bridge/">https://blog.ston.fi/omniston-explained-how-cross-chain-swaps-on-ton-work-without-a-bridge/</a></p><p>STON.fi Blog, How STON.fi’s TON cross-chain works: a guide for beginners — user-focused explanation of cross-chain swaps and different-token routing scenarios: <a href="https://blog.ston.fi/how-ston-fis-ton-cross-chain-works-a-guide-for-beginners/">https://blog.ston.fi/how-ston-fis-ton-cross-chain-works-a-guide-for-beginners/</a></p><p>STON.fi, Cross-chain swap from TON to Base — practical interface flow and pre-confirmation checklist for a TON-to-Base transaction: <a href="https://ston.fi/cross-chain-swap-from-ton-to-base">https://ston.fi/cross-chain-swap-from-ton-to-base</a></p><p>STON.fi Blog, How TON users can access cross-chain liquidity on Ethereum, Base, and BNB Chain — comparison of bridge-based routes and resolver-based atomic swaps into destination assets: <a href="https://blog.ston.fi/how-ton-users-can-access-cross-chain-liquidity-on-ethereum-base-and-bnb-chain/">https://blog.ston.fi/how-ton-users-can-access-cross-chain-liquidity-on-ethereum-base-and-bnb-chain/</a></p><p>STON.fi Documentation, Omniston Overview — official documentation of Omniston requests, aggregation, routing, liquidity sources, and execution: <a href="https://docs.ston.fi/developer-section/omniston/overview">https://docs.ston.fi/developer-section/omniston/overview</a></p><p>STON.fi Help Center, How do I swap tokens on STON.fi? — basic swap flow and the fields users should review before confirmation: <a href="https://help.ston.fi/hc/en-us/articles/28370505213084-How-do-I-swap-tokens-on-STON-fi">https://help.ston.fi/hc/en-us/articles/28370505213084-How-do-I-swap-tokens-on-STON-fi</a></p><p>TON Documentation, Jettons Overview — official explanation of TON’s fungible-token standard and Jetton architecture: <a href="https://docs.ton.org/standard/tokens/jettons/overview">https://docs.ton.org/standard/tokens/jettons/overview</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf127e6611a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Custom Refund Addresses Create Both Flexibility and Responsibility in STON.fi V2]]></title>
            <link>https://medium.com/@ivan.zimanov/how-custom-refund-addresses-create-both-flexibility-and-responsibility-in-ston-fi-v2-30c380c3721c?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/30c380c3721c</guid>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crosschain]]></category>
            <category><![CDATA[swap]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 05:51:06 GMT</pubDate>
            <atom:updated>2026-09-27T05:51:06.971Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rSbQzpzHdVG9tfn63bMzCA.png" /></figure><p>STON.fi V2 lets a swap define where assets should be returned if execution fails. Instead of assuming that every refund must go back to the wallet that started the transaction, the swap payload can contain a separate refund_address. V2 also supports a refund payload that can accompany a failed swap. These capabilities are explicitly part of the V2 swap design.</p><p>That flexibility is useful for wallets, dApps, automated systems, and more complex transaction flows. It also moves an important decision into the transaction itself. If the refund address is wrong, inaccessible, or misunderstood, the protocol cannot simply guess where the assets were intended to go.</p><p>The feature is therefore best understood as programmable failure handling. You are not only defining what should happen when a swap succeeds. You can also define where value should go when it does not.</p><h3>The refund address is not the same as the recipient</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fUqYM6C8drzHX5rvqRHMjA.png" /></figure><p>A normal swap already needs to answer a basic question: where should the purchased tokens go?</p><p>STON.fi V2 separates that successful destination from the destination used after a failure.</p><p>At the Router level, the V2 swap payload includes a refund_address, an excesses_address, a transaction deadline, and additional swap data. Inside that additional data, receiver_address identifies where the successfully swapped tokens should be sent.</p><p>Keeping these roles separate matters because they solve different problems. Sending output tokens to one wallet does not automatically mean refunds must go there too, and the address receiving gas excesses is not necessarily the address that should recover the traded asset.</p><p>For a simple personal swap, all of these addresses may effectively point back toward the same user. For an integration, they can represent different parts of an application.</p><h3>Why V2 made the failure path configurable</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zHKdD1ZNsEPWC9BAySohFQ.png" /></figure><p>DEX interfaces often make a swap look like a single action: choose two assets, enter an amount, review the quote, and sign.</p><p>On TON, the execution behind that action can involve a sequence of messages between contracts. TON documentation describes contract interactions as asynchronous message flows that can form transaction traces across multiple accounts. Different contracts involved in one interaction do not necessarily execute as one indivisible operation in the same block.</p><p>STON.fi V2 therefore has to define what happens not only on success, but also when execution reaches a condition that prevents the requested swap from finishing.</p><p>Official V2 opcode documentation includes failure conditions such as:</p><ul><li>insufficient liquidity for the requested swap</li><li>output equal to zero</li><li>output below the specified minimum</li><li>a locked pool</li><li>an expired transaction</li><li>insufficient gas or an invalid request in certain routing stages</li></ul><p>STON.fi exposes specific refund-related operation codes for several of these conditions.</p><p>A configurable refund address gives an integration control over the destination of funds when one of those failure branches is taken.</p><h3>What actually triggers a refund?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KQybeHVcsuTmfRHhVsc9uA.png" /></figure><p>One of the clearest examples is slippage protection.</p><p>A STON.fi V2 swap contains min_out, the minimum amount of output tokens acceptable to the transaction. The Pool documentation states that the swap fails when the amount the user should receive is below that minimum.</p><p>Imagine a swap is prepared when a pool can return 1,000 units of the target token. The transaction is built with a minimum acceptable output of 990.</p><p>Before the swap reaches execution, pool conditions change. The same input would now produce only 980.</p><p>The contract should not silently accept the worse result. The minimum output condition causes the requested swap to fail. The refund mechanism then becomes relevant.</p><p>The same broad idea applies to other protected failure conditions. A transaction can also carry a deadline, so a request that arrives too late does not have to execute under conditions that may no longer resemble the original quote. STON.fi V2 documents transaction deadlines as part of the swap feature set.</p><p>The refund address is therefore part of the protection model, not a substitute for it. min_out and the deadline decide whether execution remains acceptable. The refund configuration helps determine where value goes when it does not.</p><h3>Flexibility becomes useful when the sender and owner are not the same operational role</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q5pAltQFeNDw3ldDAdc7Gw.png" /></figure><p>Why would anyone want a refund sent somewhere other than the address that initiated a transaction?</p><p>Because modern dApps often separate signing, receiving, accounting, and recovery.</p><p>Consider a wallet-connected application that builds a swap on behalf of a user. The successful output might be intended for a dedicated destination wallet. Refunds, however, might need to return to the original user-controlled address.</p><p>Another integration might intentionally use a recovery address dedicated to failed operations. An automated service could route successful assets into one operational wallet while directing unsuccessful flows into another address that is easier to monitor and reconcile.</p><p>The Omniston transaction building interface reflects this distinction. Its transaction.build_transfer parameters include a source address, destination address, gas excess address, and optional refund address. The documentation states that when the refund address is not provided, funds are returned to the sender&#39;s wallet, and that this refund parameter currently works for swaps through STON.fi.</p><p>That default is important. Customization is available when an integration needs it, but the ordinary case does not require inventing a separate recovery destination.</p><h3>A simple failure flow</h3><p>For a direct V2 swap, the conceptual path looks like this:</p><ol><li>A wallet initiates a swap.</li><li>The transaction specifies the desired receiver, refund address, minimum output, deadline, and other execution data.</li><li>The Router forwards the swap to the relevant Pool.</li><li>The Pool evaluates whether the operation can satisfy its conditions.</li><li>If the swap succeeds, output is delivered through the normal success path.</li><li>If it fails in a refundable condition, the refund path uses the designated refund destination.</li></ol><p>The address choice is therefore made before the failure occurs. By the time execution reaches that branch, the transaction already contains the instructions needed to determine where the returned funds should go.</p><h3>Custom refund payloads make failure handling more programmable</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4LJTMNilXAVgYZ1h4JTHcg.png" /></figure><p>STON.fi V2 does not stop at choosing an address.</p><p>Its swap data can also contain refund_fwd_gas and a refund_payload. The Router documentation describes these fields as gas for forwarding a transfer notification when the swap fails and an optional payload sent with that notification.</p><p>This opens a more advanced design space.</p><p>A smart contract receiving the refund may need context about why or how the funds arrived. An application can use a payload to carry information into that failure path instead of treating the refund as an isolated token movement.</p><p>That can be useful for contract-based systems that maintain their own state, transaction identifiers, or follow-up logic.</p><p>It also adds another layer of responsibility. Once an integration starts attaching custom data and routing refunds into contracts rather than ordinary wallets, developers need to understand what the receiving contract expects and whether enough forward gas has been provided for the intended notification.</p><p>For most ordinary wallet swaps, none of this needs to be manually engineered. STON.fi’s V2 documentation recommends using the official SDK for production applications rather than manually constructing low-level transaction bodies.</p><h3>The most important responsibility is verifying the destination</h3><p>A custom refund address is powerful precisely because the protocol follows the address encoded in the transaction.</p><p>That makes address verification part of transaction safety.</p><p>Before signing an integration-generated V2 transaction with a custom refund destination, check:</p><ul><li><strong>Who controls the refund address?</strong> It should correspond to the intended recovery destination.</li><li><strong>Why is it different from the sender?</strong> A different address can be legitimate, but the integration should have a clear reason.</li><li><strong>Can the recipient handle the returned asset?</strong> This is especially important when refunds are directed into smart-contract workflows.</li><li><strong>Is the successful receiver different as well?</strong> Do not confuse receiver_address with refund_address.</li><li><strong>Where are excess TON funds going?</strong> excesses_address solves a separate problem and should be reviewed independently.</li></ul><p>For developers, the safest pattern is to construct transactions from current protocol metadata rather than hardcoding assumptions about routers or contract layouts. STON.fi’s current V2 SDK guidance recommends obtaining Router metadata from the STON.fi API and using factory helpers to build the appropriate contracts dynamically.</p><p>The general rule is simple: flexibility should be intentional. If an application cannot explain why a refund is going to a particular address, it probably should not override the normal sender-based behavior.</p><h3>A custom refund address cannot make a multi-step swap atomic</h3><p>The limits become especially important when routing involves several swaps.</p><p>STON.fi’s V2 examples explain that TON multi-contract transactions are not atomic in the way a user might imagine from a single interface action. In a cross-swap, a failure after an earlier swap stage may mean that the entire route cannot simply be reversed back into the original asset. The user can instead receive an intermediate token associated with the route.</p><p>This is a crucial distinction.</p><p>A custom refund address answers:</p><p><strong>Where should the refundable asset go?</strong></p><p>It does not necessarily answer:</p><p><strong>Which asset will exist when a complex route fails?</strong></p><p>Suppose a route conceptually looks like:</p><p>Token A -&gt; Token B -&gt; Token C</p><p>If the first swap succeeds but the second cannot execute, the system may already have converted Token A into Token B. The refund path cannot always recreate the original pre-swap state.</p><p>The custom refund address can determine where the relevant returned asset is delivered, but it does not turn an asynchronous chain of contract interactions into one atomic operation.</p><p>That is why developers building cross-swap interfaces should communicate both the recovery destination and the possible recovery asset clearly.</p><h3>Custom refund addresses are especially important for integrations</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SuiqK6K1r2gwXWHFeM4R5g.png" /></figure><p>A person swapping through a standard interface may never need to think about the raw refund_address field.</p><p>Developers do.</p><p>Once a wallet, trading interface, bot, treasury system, or other application generates STON.fi transactions, it becomes responsible for translating its own account model into the protocol’s address model.</p><p>A robust integration should know which address represents:</p><ul><li>the transaction source</li><li>the successful output recipient</li><li>the refund recipient</li><li>the TON excess recipient</li></ul><p>Omniston exposes the same basic separation in its transaction-building interface. Its gRPC integration documentation also describes the refund address as optional and says it defaults to the sender’s wallet when omitted.</p><p>Defaults reduce unnecessary configuration. Custom addresses should normally appear because the application’s workflow actually requires them, not because every available field must be customized.</p><p>For developers, that also suggests a useful testing practice: deliberately test a refundable failure before shipping the integration. A transaction with a deliberately unreachable minimum output can help verify where funds return and whether monitoring correctly identifies the result.</p><p>Use small test amounts and verify the complete transaction trace before relying on the same logic for significant value.</p><h3>What V2 changes for the user</h3><p>The broader design lesson is that STON.fi V2 treats failure as something an integration can plan for.</p><p>V2’s documented swap improvements include a custom refund address, refund payloads, transaction deadlines, and more flexible swap chaining.</p><p>Those capabilities make sophisticated transaction flows possible, but they also reduce the number of assumptions the protocol can safely make on behalf of the person signing.</p><p>With a simple default configuration, failure can return funds toward the original sender.</p><p>With a customized transaction, the destination may be deliberately different.</p><p>Neither approach is inherently better. What matters is that the address encoded in the transaction matches the intended ownership and recovery model.</p><p><strong>Practical takeaway:</strong> when reviewing or building a STON.fi V2 swap, treat the refund destination as a first-class transaction parameter. Confirm where successful output goes, where a failed operation returns funds, and where excess TON is sent. For multi-step routes, also remember that the refunded asset may reflect how far execution progressed rather than recreating the transaction’s original starting state.</p><h3>Frequently Asked Questions</h3><h3>What is a custom refund address in STON.fi V2?</h3><p>It is the address specified in a V2 swap for receiving funds returned after a failed swap. It is separate from the receiver_address, which is used for successful swap output, and from the excesses_address, which receives excess TON associated with execution.</p><h3>Does a refund always go back to the wallet that started the swap?</h3><p>Not necessarily. V2 supports an explicit refund address. In Omniston’s transaction builder, the refund address is optional and defaults to the sender’s wallet when it is not supplied. A custom value allows an integration to direct the refund elsewhere when its workflow requires that behavior.</p><h3>Why can a STON.fi swap fail even after I sign it?</h3><p>Signing authorizes the transaction, but execution conditions still matter. For example, the swap can fail if the resulting output is below min_out, if liquidity is insufficient, if the Pool is locked, or if the transaction reaches an expiry condition documented by the protocol.</p><h3>Is the refund address the same as the gas excess address?</h3><p>No. They represent different destinations. The refund address handles funds returned after a failed operation, while the excesses address is used for excess TON related to execution. Keeping them separate allows applications to control asset recovery and gas handling independently.</p><h3>Can STON.fi V2 send data with a refund?</h3><p>Yes. V2 swap data supports a refund_payload together with refund_fwd_gas. This can be used when a receiving contract needs a transfer notification with additional data after a failed swap. It is primarily relevant to advanced integrations rather than normal manual swaps.</p><h3>Will a failed cross-swap always return my original token?</h3><p>No. STON.fi’s swap examples explain that multi-contract transactions on TON are not fully atomic. If part of a routed swap has already executed before a later stage fails, the recovery can involve an intermediate token rather than the asset originally supplied.</p><h3>Should developers manually construct the V2 refund payload?</h3><p>Only when they have a specific advanced reason to work at that level. STON.fi recommends using its official SDK for production integrations and obtaining current Router information dynamically instead of relying on manually assembled transaction bodies or hardcoded contract assumptions.</p><h3>What should I verify before using a custom refund address on STON.fi?</h3><p>Verify who controls the address, why the refund should go there instead of to the sender, whether the destination can correctly handle the returned asset, and whether the successful receiver and TON excess destination are also correct. For routed swaps, check the transaction model carefully because a failure may return an intermediate asset rather than reconstructing the original position.</p><h3>Sources and Further Reading</h3><p>STON.fi DEX V2 Smart Contracts — overview of V2 swap features, including custom refund addresses, refund payloads, deadlines, and chained swaps: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2?utm_source=chatgpt.com">STON.fi V2 smart contracts documentation</a></p><p>STON.fi Router V2 — detailed Router message structure, including refund_address, receiver_address, excesses_address, refund_payload, and refund_fwd_gas: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/router?utm_source=chatgpt.com">STON.fi Router V2 documentation</a></p><p>STON.fi Pool V2 — Pool-level swap processing, minimum output checks, refund fields, and swap result handling: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/pool?utm_source=chatgpt.com">STON.fi Pool V2 documentation</a></p><p>STON.fi V2 Swap Examples — examples of simple swaps, cross-swaps, and refund behavior when routed operations fail: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/examples/swap?utm_source=chatgpt.com">STON.fi V2 swap examples</a></p><p>STON.fi V2 Op Codes — documented success, refund, expiry, liquidity, slippage, and other operation codes: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/op-codes?utm_source=chatgpt.com">STON.fi V2 op codes</a></p><p>STON.fi V2 SDK Swap Guide — current API-driven workflow for building production V2 swap transactions using Router metadata and the official SDK: <a href="https://docs.ston.fi/developer-section/dex/sdk/v2/swap?utm_source=chatgpt.com">STON.fi V2 SDK swap guide</a></p><p>Omniston Swap Overview — transaction building parameters including source, destination, gas excess, and optional refund addresses: <a href="https://docs.ston.fi/developer-section/omniston/swap/overview?utm_source=chatgpt.com">Omniston swap overview</a></p><p>TON Documentation, Transaction Foundations — explanation of transaction traces and asynchronous message handling across TON smart contracts: <a href="https://docs.ton.org/v3/guidelines/dapps/transactions/foundations-of-blockchain?utm_source=chatgpt.com">TON transaction foundations</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30c380c3721c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How STON.fi Transaction Deadlines Limit Stale Execution]]></title>
            <link>https://medium.com/@ivan.zimanov/how-ston-fi-transaction-deadlines-limit-stale-execution-edc4f2337028?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/edc4f2337028</guid>
            <category><![CDATA[transactions]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[swap]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 05:49:33 GMT</pubDate>
            <atom:updated>2026-09-27T05:49:33.273Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why a swap needs a time limit as well as slippage protection</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*woDuO0qF6UNebsRgwaDnHw.png" /></figure><p>A STON.fi transaction deadline is a time boundary encoded into a DEX v2 operation. If the operation reaches the relevant contract after that deadline, it should no longer execute as a normal swap or liquidity action. Instead of allowing an old instruction to remain valid indefinitely, the protocol can treat it as expired.</p><p>That matters because a swap request is based on conditions that existed when the transaction was prepared. Pool reserves can move, prices can change, messages can be delayed, and a user may no longer want the operation several minutes later. STON.fi v2 therefore includes a deadline field in swap and liquidity payloads specifically to limit stale execution.</p><h3>Why a transaction can become stale</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FlGuGYHEfTsFQdaYgWigBg.png" /></figure><p>Imagine that you prepare a token swap at 12:00. The interface calculates an expected output from the current pool state, creates the transaction, and your wallet asks you to approve it.</p><p>Normally, you sign quickly and the transaction travels through TON without unusual delay. But several things can interrupt that sequence:</p><ul><li>you leave the wallet confirmation screen open</li><li>your connection becomes unstable</li><li>a wallet or application retries a previously created request</li><li>network processing takes longer than expected</li><li>several other swaps change the pool before your message reaches the DEX logic</li></ul><p>The instruction may still be technically valid, but the economic context that produced it is getting older.</p><p>That is the stale execution problem.</p><p>A decentralized exchange cannot safely assume that a transaction prepared earlier should remain executable forever. A deadline converts the instruction from “perform this operation whenever it eventually arrives” into “perform this operation only while this time condition is still satisfied.”</p><p>STON.fi v2 documents transaction deadlines as a feature for both swaps and liquidity provision. In the Router payload, deadline is a uint64 timestamp described as the execution deadline for the transaction.</p><h3>The deadline is checked inside the DEX flow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IUr-7HKjTtCLGqwb4cF3CA.png" /></figure><p>A STON.fi swap is not merely a wallet transfer from one address to another. The transaction initiates a message flow involving token wallets, the Router, a pool, and potentially additional contracts depending on the route.</p><p>TON smart contracts communicate asynchronously through messages. A multi-contract interaction can therefore span multiple transactions and even multiple blocks rather than executing as one globally atomic operation. TON documentation specifically notes that contract interactions may interleave because internal message handling is asynchronous.</p><p>STON.fi’s protocol-level deadline matters in that environment because the time restriction travels with the DEX instruction itself.</p><p>The simplified idea is:</p><ol><li>A swap is prepared using current pool information.</li><li>The transaction includes the swap parameters and a deadline.</li><li>The wallet signs and sends the initial message.</li><li>The message flow reaches STON.fi’s Router.</li><li>The contract compares the current time with the encoded deadline.</li><li>If the operation is already too old, the stale swap is rejected rather than processed normally.</li></ol><p>STON.fi’s v2 examples demonstrate the intended timeout pattern with a check that treats now() &gt; deadline as an expired operation.</p><p>The deadline is therefore not merely a countdown displayed by the interface. It is part of the logic that defines whether the transaction is still acceptable when execution reaches the protocol.</p><h3>Deadline and minimum received protect different things</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4RESzX_ezSafdPuDK85_pg.png" /></figure><p>It is easy to confuse a transaction deadline with slippage protection because both can cause a swap not to proceed. They answer different questions.</p><p>ProtectionMain questionExample failureTransaction deadlineIs the operation too old?The swap reaches execution after its allowed time windowMinimum receivedIs the output too low?Current pool conditions would return less than the encoded minimumWallet validityIs the signed wallet request still acceptable?The wallet receives or processes the external request after its validity period</p><p>STON.fi’s Router v2 payload contains both a deadline and min_out. The documentation describes min_out as the minimum required amount of output tokens and states that a swap fails when the resulting amount would be below it.</p><p>Suppose you prepare a swap expecting approximately 100 tokens and the transaction requires at least 98.</p><p>If the swap reaches STON.fi quickly but pool conditions now produce only 97, the minimum output protection is what blocks the trade.</p><p>If the pool would still produce 99 but the transaction reaches the deadline check too late, the deadline is what blocks it.</p><p>One protects against an unacceptable execution price. The other protects against an instruction being executed after its intended lifetime.</p><p>Using both creates a stronger boundary around the original intent.</p><h3>A deadline does not freeze the quoted price</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GUUfawwNQb5qtclsV63slQ.png" /></figure><p>The presence of a deadline does not reserve a price, freeze a pool, or guarantee that the amount shown before signing will remain available until the final second.</p><p>An AMM pool continues changing while your transaction is pending. Other traders can execute swaps, liquidity can change, and the relationship between reserves can move.</p><p>The deadline only defines how old the transaction may become before it should stop being executable.</p><p>Your minimum output parameter handles the separate question of how much deterioration you are willing to accept before the trade should fail.</p><p>Think of the two protections as a rectangle around the transaction:</p><ul><li>the deadline limits acceptable movement through time</li><li>min_out limits acceptable movement in output amount</li></ul><p>A transaction must remain inside both boundaries.</p><p>This is why extending a deadline is not equivalent to increasing slippage tolerance. A longer deadline gives the instruction more time to reach execution, but it does not make a poor output acceptable if min_out remains unchanged.</p><p>Similarly, very loose slippage settings do not eliminate the need for a deadline. Without a meaningful time limit, an instruction could theoretically remain acceptable far longer than the context in which it was created.</p><h3>STON.fi’s deadline is not the same as wallet valid_until</h3><p>TON introduces another time-related field at the wallet layer: valid_until.</p><p>Wallet contracts use valid_until to limit the lifetime of the signed external message. TON documentation describes it as a Unix timestamp included in the wallet signing message. When the current time exceeds it, the wallet rejects the external message. Together with the wallet sequence number, this helps prevent an old signed request from being reused indefinitely.</p><p>STON.fi’s DEX deadline sits at a different layer.</p><p>A simplified comparison looks like this:</p><p><strong>Wallet </strong><strong>valid_until</strong></p><p>Protects the signed request entering the user’s wallet transaction flow.</p><p><strong>STON.fi transaction deadline</strong></p><p>Protects the DEX operation when the STON.fi message flow reaches the protocol logic.</p><p>That distinction is particularly relevant on TON because accepting the external wallet message does not mean every subsequent internal message has already completed. A transaction can begin successfully at the wallet while the resulting contract-to-contract message cascade continues asynchronously.</p><p>Developers should therefore avoid treating wallet validity as a complete substitute for the protocol deadline.</p><p>The two mechanisms operate at different points in the transaction lifecycle.</p><h3>What happens when the deadline is missed?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WX_jqupoEOc7oq1yEx4ajA.png" /></figure><p>The main objective is simple: an expired operation should not continue as an ordinary swap.</p><p>STON.fi v2 supports refund-related fields directly in its Router swap payload, including a refund_address and optional refund payload behavior. Its v2 architecture also describes improved failure handling and transaction completion deadlines as explicit protocol features.</p><p>Still, “the swap expired” should not be interpreted as “nothing happened on-chain.”</p><p>The initial wallet transaction may already have been processed. Messages may already have moved between contracts. Gas may have been consumed. TON transactions charge for message handling and computation as execution progresses.</p><p>There is another complication with multi-step routes. STON.fi’s swap documentation explains that TON multi-contract transactions are not globally atomic. In cross-swaps, if a later part of the route cannot complete, a full rollback to the original asset is not always possible, and the user may receive an intermediate token instead.</p><p>So a deadline should be understood as an execution guard, not as a magical reversal mechanism.</p><p>Its job is to stop an operation from continuing normally once its permitted time window has passed.</p><h3>Following one STON.fi swap</h3><p>Consider a user exchanging Token A for Token B.</p><p>The interface first obtains current routing and output information. STON.fi’s current SDK guidance recommends simulating the swap, using the returned Router information, generating the transaction parameters, and then sending those parameters through the chosen wallet integration.</p><p>At the moment the transaction is constructed, several pieces of intent are effectively being expressed:</p><ul><li>how much Token A is being offered</li><li>which Token B should be received</li><li>where the result should go</li><li>the minimum acceptable Token B output</li><li>where a refund should go if the operation fails</li><li>the time boundary after which the operation is stale</li></ul><p>Now imagine two paths.</p><h3>The transaction arrives in time</h3><p>The Router sees that the deadline is still valid.</p><p>Execution proceeds toward the pool. The pool determines the output from its current state. If that output satisfies min_out, the swap can continue and Token B is delivered according to the transaction parameters.</p><h3>The transaction arrives too late</h3><p>The Router reaches the operation after the encoded deadline.</p><p>Even if the token pair still exists and even if the current price looks acceptable, the transaction has crossed its permitted time boundary. The intended behavior is to treat the operation as expired rather than execute an instruction whose creator considered it valid only for an earlier window.</p><p>That distinction is the real value of the deadline.</p><p>It does not predict future market conditions. It limits how long previously expressed intent remains actionable.</p><h3>What should users and developers check?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZyordwgOdgRkEdMHELSE6A.png" /></figure><p>Most ordinary STON.fi users will not manually inspect a raw uint64 deadline before every swap. The interface and wallet normally handle transaction construction.</p><p>The concept still matters when diagnosing failed transactions or building an integration.</p><p>For a stale or unexpectedly failed swap, separate these questions:</p><ul><li><strong>Was the wallet request still valid?</strong> Check the wallet-level validity window.</li><li><strong>Did the DEX deadline expire?</strong> The protocol transaction may have reached STON.fi too late.</li><li><strong>Was </strong><strong>min_out violated?</strong> The operation may have arrived in time but failed because output deteriorated.</li><li><strong>Was the route multi-step?</strong> A partial message flow can make the final result more complex than a simple rollback.</li><li><strong>Was the transaction built long before it was sent?</strong> Reusing old transaction parameters defeats the purpose of creating them from current market state.</li></ul><p>For developers, a useful rule is to keep quote generation, transaction construction, signing, and broadcasting close together. If the transaction becomes stale before the user signs it, rebuild it from current state instead of treating old parameters as permanently reusable.</p><p>The low-level Router documentation defines the deadline as a timestamp but does not prescribe one universal duration that every application must use. The appropriate window is therefore part of transaction construction and application design, not a guarantee that every STON.fi interaction has one fixed countdown.</p><p><strong>Practical takeaway:</strong> when a STON.fi swap fails after sitting pending or unsigned for an unusually long time, do not look only at slippage. Check whether the transaction itself became stale. A current quote, a sensible minimum output, a fresh wallet request, and a valid protocol deadline protect different parts of the same swap.</p><h3>Frequently Asked Questions</h3><h3>What is a STON.fi transaction deadline?</h3><p>It is a timestamp included in STON.fi DEX v2 swap and liquidity operation data. The timestamp defines the time boundary for execution. If the relevant contract processes the operation after that boundary, the transaction should be treated as expired rather than executed normally.</p><h3>Why does a DEX transaction need a deadline?</h3><p>Because the transaction was created using earlier market and pool conditions. If it stays valid indefinitely, an old instruction could execute long after the context in which it was prepared. A deadline limits how long that previously expressed instruction remains actionable.</p><h3>Is a deadline the same as slippage tolerance?</h3><p>No. A deadline limits how late the transaction may execute. Slippage protection, implemented through a minimum output such as min_out, limits how unfavorable the execution amount may become. A swap can fail either protection independently.</p><h3>Does the deadline guarantee the quoted price?</h3><p>No. Pool conditions continue changing before execution. The deadline limits transaction age, not market movement. The minimum output parameter is the relevant protection when the current pool state would produce less than the user is willing to accept.</p><h3>Is STON.fi’s deadline the same as TON Connect validUntil?</h3><p>No. TON wallet validity limits the lifetime of the signed external wallet request. STON.fi’s deadline applies to the DEX operation itself. Because TON interactions can involve asynchronous messages between several contracts, both time limits can matter at different stages.</p><h3>Does an expired STON.fi transaction cost nothing?</h3><p>Not necessarily. Parts of the message flow may already have been processed, and TON execution and message handling consume fees. Expiration prevents stale DEX execution, but it does not mean every preceding blockchain action is erased or free.</p><h3>Can an expired multi-hop swap always return the original token?</h3><p>Not necessarily. STON.fi notes that multi-contract transactions on TON are not globally atomic. In a failed cross-swap, the result can sometimes be an intermediate token rather than a complete reversal to the original asset.</p><h3>What should a STON.fi integration do when a prepared swap becomes old?</h3><p>Generate fresh transaction parameters from current state rather than indefinitely reusing the old transaction. Keep simulation, transaction construction, wallet approval, and broadcast reasonably close together, and preserve both the protocol deadline and minimum output checks as separate safeguards.</p><h3>Sources and Further Reading</h3><p>STON.fi DEX v2 smart contracts — Overview of DEX v2 features, including transaction completion deadlines for swaps and liquidity operations: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2?utm_source=chatgpt.com">Official STON.fi documentation</a></p><p>STON.fi Router v2 — Low-level Router payload definitions for deadline, min_out, refund addresses, and swap execution: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/router?utm_source=chatgpt.com">Official Router v2 documentation</a></p><p>STON.fi swap examples — Examples of swap execution, expiry checks, refunds, and multi-contract swap behavior: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/examples/swap?utm_source=chatgpt.com">Official swap examples</a></p><p>STON.fi SDK v2 swap guide — Current workflow for simulation, Router selection, transaction construction, and transaction sending: <a href="https://docs.ston.fi/developer-section/dex/sdk/v2/swap?utm_source=chatgpt.com">Official SDK swap guide</a></p><p>STON.fi transaction sending guide — How SDK transaction parameters are passed to TON wallet integrations: <a href="https://docs.ston.fi/developer-section/common/transaction-sending?utm_source=chatgpt.com">Official transaction sending guide</a></p><p>TON Docs, How TON wallets work — Explanation of valid_until, sequence numbers, signing, and wallet-level replay protection: <a href="https://docs.ton.org/standard/wallets/how-it-works?utm_source=chatgpt.com">Official TON wallet documentation</a></p><p>TON Docs, Foundations of blockchain — Explanation of TON messages, transactions, traces, execution phases, fees, and asynchronous contract interaction: <a href="https://docs.ton.org/v3/guidelines/dapps/transactions/foundations-of-blockchain?utm_source=chatgpt.com">Official TON foundations documentation</a></p><p>TON Connect documentation — Example of constructing a wallet transaction with a finite validUntil value: <a href="https://docs.ton.org/develop/dapps/ton-connect/react?utm_source=chatgpt.com">Official TON Connect documentation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=edc4f2337028" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Move Value from TRON to TON with STON.fi Cross-Chain]]></title>
            <link>https://medium.com/@ivan.zimanov/how-to-move-value-from-tron-to-ton-with-ston-fi-cross-chain-ee36ff0a8cd1?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee36ff0a8cd1</guid>
            <category><![CDATA[tron]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ton]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[stonfi]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 06:51:44 GMT</pubDate>
            <atom:updated>2026-09-24T06:51:44.105Z</atom:updated>
            <content:encoded><![CDATA[<p><em>How an atomic cross-chain swap can turn a TRON-side asset into a TON-side asset without a separate bridge or centralized exchange.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*00Zx5P_wW0m37u4LeRprWw.png" /></figure><p>Moving value from TRON to TON no longer has to mean depositing to a centralized exchange, trading there, and withdrawing to another network. STON.fi now supports cross-chain swaps between TRON and TON through Omniston, letting you start with an asset on TRON and receive the selected asset on TON in one coordinated flow.</p><p>A practical example is USDT. You can start with TRC-20 USDT in a TRON wallet, choose USDT on TON as the destination asset, review one cross-chain quote, and approve the route from your wallets. The important detail is that this is a cross-chain swap, not a normal token transfer and not simply the same USDT moving between two addresses.</p><p>As of September 22, 2026, STON.fi lists both TON and TRON among its supported cross-chain networks and describes TON to TRON execution as atomic through Omniston.</p><p><strong>Key takeaways</strong></p><ul><li>TRON and TON are separate blockchains, so you should not send a TRC-20 token directly to a TON address.</li><li>STON.fi combines the cross-chain movement and asset conversion into one route.</li><li>Omniston uses resolver liquidity and atomic execution rather than asking you to operate a conventional bridge manually.</li><li>You see the route, expected output, and fees before confirming.</li><li>If you use TRON as the source network, account for its Bandwidth and Energy model and keep enough TRX available for source-side costs.</li><li>Always verify both the source asset and the destination asset, even when they share the same ticker such as USDT.</li></ul><h3>Why TRON to TON needs a cross-chain route</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-kB_8tHrazhCPq5XUm0Msg.png" /></figure><p>A wallet transfer normally works inside one blockchain. TRC-20 tokens belong to TRON, while fungible tokens on TON use the Jetton architecture. A token with the same name can therefore exist as separate on-chain assets on both networks.</p><p>USDT makes this especially easy to misunderstand. Tether introduced TRC-20 USDT on TRON, while TON represents USDT as a Jetton. TON documentation identifies the official USDT Jetton as an example of the network’s fungible token model.</p><p>So a route such as:</p><p><strong>TRON / USDT → TON / USDT</strong></p><p>does not mean that one blockchain transaction somehow crosses directly from TRON into TON. TRON cannot write a token balance into TON’s ledger, and TON cannot simply import a TRON transaction.</p><p>Something has to coordinate value on both sides.</p><p>This also explains why copying your TON wallet address into a normal TRON token transfer is not the solution. TRON wallet addresses are commonly displayed in Base58Check form beginning with T, while TON uses its own address formats. STON.fi&#39;s current cross-chain wallet interface treats the TRON wallet and TON wallet as separate endpoints for exactly this reason.</p><h3>What STON.fi changes in the workflow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dt8fikUDkr26i12jTyFBGA.png" /></figure><p>The older route from TRON into TON often meant assembling several independent actions yourself.</p><p>You might send USDT to an exchange, wait for the deposit, trade or convert it if necessary, select TON as the withdrawal network, enter a TON address, pay the withdrawal fee, and wait again. A bridge-based workflow can remove the centralized exchange but still leave you managing a bridge operation and possibly another swap after arrival.</p><p>STON.fi treats the desired destination outcome as one cross-chain swap.</p><p>The difference is useful because “move value to TON” and “receive the asset I actually want on TON” are not always the same task.</p><p>If you hold USDT on TRON and ultimately want USDT on TON, the destination can be selected directly. If the available route supports another TON-side asset that you want instead, the cross-chain swap can be built around that final asset rather than forcing you to bridge first and perform a separate manual conversion later.</p><p>STON.fi currently describes the interface as supporting TON, TRON, and major EVM networks in a single workflow, with routes, fees, and output visible before confirmation.</p><h3>What happens underneath the swap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2firEmsvbc0AbwHaRRSBg.png" /></figure><p>The user experience is intentionally simple, but the settlement problem underneath it is not.</p><p>Omniston is the execution layer behind STON.fi’s cross-chain swaps. Its model combines liquidity discovery with atomic settlement. In the resolver model described by STON.fi, a request for quote can be answered by liquidity providers called resolvers. Instead of requiring you to find another person who wants the opposite trade, the resolver side supplies the corresponding destination liquidity.</p><p>Settlement then uses the logic of Hashed Timelock Contracts, or HTLCs.</p><p>An HTLC combines two conditions:</p><ul><li>a hashlock, which requires the correct cryptographic secret to release funds</li><li>a timelock, which creates a deadline after which funds can be refunded</li></ul><p>For a simplified TRON to TON example, your source-side value and the resolver’s TON-side value are placed under linked conditions. The same cryptographic condition ties the two sides together. Successful revelation of the required secret allows the two legs to settle. If the required conditions are not completed in time, the timelock provides the refund path.</p><p>That is what gives an atomic swap its all-or-nothing property. STON.fi describes the current cross-chain experience as one where the intended swap completes or the assets are refunded instead of leaving one leg successfully executed while the other remains unfinished.</p><p>Non-custodial does not mean that smart contracts are absent. During settlement, assets can be conditionally locked by contract logic. The important distinction is that STON.fi itself is not taking your deposit into a company-controlled account and deciding later whether to release it. You sign transactions with your own wallets, while the settlement rules are enforced by the protocol.</p><h3>How to move value from TRON to TON</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a6_GgT8NzjPxrtizT-FImQ.png" /></figure><p>A USDT to USDT move is a useful example because it keeps the asset choice simple while making the network change obvious.</p><h3>1. Prepare both wallets</h3><p>You need control of the TRON wallet holding the source asset and a TON wallet that can receive the destination asset.</p><p>STON.fi’s current connection guide supports TronLink as a desktop TRON option and WalletConnect with supported TRON wallets. For TON, the interface uses TON Connect with compatible wallets such as Tonkeeper, My Wallet, and Gram Wallet. Wallet support can change, so check the current connection screen rather than assuming a particular mobile or desktop combination will work.</p><p>Never enter a seed phrase into STON.fi or any website simply to connect a wallet. Wallet connection and transaction signing should happen through the wallet itself.</p><h3>2. Select TRON as the source</h3><p>Choose TRON as the source blockchain and select the asset you actually hold there.</p><p>For example:</p><p><strong>Source network:</strong> TRON<br><strong>Source asset:</strong> USDT</p><p>Do not rely only on the ticker. Confirm that the interface has selected the correct network and asset.</p><h3>3. Select TON and the final asset</h3><p>Choose TON as the destination blockchain and then choose what you want to receive.</p><p>For the simplest stablecoin move:</p><p><strong>Destination network:</strong> TON<br><strong>Destination asset:</strong> USDT</p><p>Your TON wallet is the destination. Check it carefully before proceeding.</p><h3>4. Enter the amount and read the quote</h3><p>Enter how much you want to move and let the interface construct the route.</p><p>Before signing, look at the actual result rather than only the amount you are sending. STON.fi says its cross-chain interface displays the route, fee, and output before confirmation. Those values matter because liquidity and network conditions can change.</p><p>A quote that looks unattractive is not something you have to accept. You can reduce the amount, wait, or compare the result again later.</p><h3>5. Confirm from the source wallet</h3><p>Once the network, asset, destination wallet, output, and cost all look correct, approve the required transaction.</p><p>On TRON, smart contract interactions consume network resources. TRON distinguishes Bandwidth, which covers transaction data, from Energy, which covers smart contract computation. If the account lacks sufficient resources, TRX can be burned to pay the shortfall according to current network parameters.</p><p>For that reason, do not assume that holding only the exact amount of a TRC-20 token you want to swap is sufficient. Check the wallet’s estimated source-side cost and keep the required TRX available.</p><h3>6. Verify the TON-side result</h3><p>After execution, confirm the destination balance in your TON wallet.</p><p>If you receive USDT, remember that you now hold the TON-side USDT Jetton, not TRC-20 USDT. The economic unit may still be USDT, but its on-chain representation and transaction environment have changed.</p><p>If you plan to make another swap, send the asset elsewhere, or interact with TON DeFi, keep some native TON network currency available for those later actions.</p><h3>What should you check before signing?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yWhqA_6RKftgu3qRDSZkYg.png" /></figure><p>Cross-chain interfaces remove steps, but they do not remove your responsibility to verify the transaction.</p><p>Before confirming a TRON to TON swap, check:</p><ul><li><strong>Source chain:</strong> It should say TRON, not another network containing a token with the same ticker.</li><li><strong>Source asset:</strong> Verify the token you are actually spending.</li><li><strong>Destination chain:</strong> Confirm TON explicitly.</li><li><strong>Destination asset:</strong> Make sure the quoted TON-side asset is the one you want to own after settlement.</li><li><strong>TON wallet:</strong> Check the receiving address instead of assuming the connected wallet is correct.</li><li><strong>Expected output:</strong> Compare what leaves your TRON wallet with what should arrive on TON.</li><li><strong>Fees:</strong> Read the current quote rather than relying on an old fee estimate.</li><li><strong>Available TRX:</strong> Make sure the source wallet can cover the TRON-side execution requirements.</li></ul><p>One more check deserves special attention: <strong>do not authenticate tokens by name or logo alone</strong>.</p><p>TON documentation warns that fake Jettons can copy legitimate metadata. The master contract is what identifies a Jetton, which is why contract verification matters when you inspect an unfamiliar asset outside a trusted interface.</p><p>For a large move, a smaller first transaction can also be useful. It verifies your wallet combination, route selection, and understanding of the final asset before you expose a larger amount to an operational mistake.</p><h3>What if the cross-chain swap does not complete?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ZYqzYrZeA_8I1B-8QLO4Q.png" /></figure><p>Failure handling is one of the reasons the execution model matters.</p><p>Imagine that you send USDT from TRON and expect USDT on TON. With a manually assembled multi-step workflow, several independent operations can fail at different stages. A deposit can arrive while a later conversion fails. A bridge operation can finish while the destination swap gives a worse result. A withdrawal can be delayed after earlier steps have already completed.</p><p>Atomic settlement is designed to narrow that failure shape.</p><p>STON.fi states that its cross-chain swaps through Omniston are executed on an all-or-nothing basis: both sides complete, or the swap fails and the assets are refunded according to the protocol’s settlement conditions.</p><p>That protection does not make every possible problem disappear. You can still select the wrong destination wallet, approve a malicious wallet prompt, misunderstand which asset you selected, or lose access to your wallet. Atomicity protects the relationship between the two legs of the swap. It cannot correct information that you intentionally supplied incorrectly.</p><p>The practical takeaway is simple: use the official STON.fi interface, connect the correct TRON and TON wallets, select both networks explicitly, read the quoted destination amount, and treat your final confirmation as the point where every detail should already be correct.</p><h3>Frequently Asked Questions</h3><h3>Can I move USDT from TRON to TON with STON.fi?</h3><p>Yes. STON.fi currently supports cross-chain routes involving TON and TRON. A route can start with USDT on TRON and end with the corresponding supported destination asset on TON. Always check the live interface before sending because available routes, assets, liquidity, and quotes can change.</p><h3>Is TRC-20 USDT the same token as USDT on TON?</h3><p>They represent the same USDT denomination from the user’s economic perspective, but they are different on-chain implementations. TRC-20 USDT exists on TRON under the TRC-20 standard. USDT on TON is implemented using TON’s Jetton architecture. A normal TRC-20 transfer therefore cannot turn one into the other.</p><h3>Can I just send TRC-20 USDT to my TON wallet address?</h3><p>No. A normal token transfer stays inside its source blockchain. A TON address is not a TRON destination for a TRC-20 transfer. Use a supported cross-chain route that explicitly identifies TRON as the source network and TON as the destination network.</p><h3>Do I need a centralized exchange?</h3><p>Not for a supported STON.fi cross-chain route. STON.fi presents TRON, TON, and supported EVM cross-chain swaps as self-custodial transactions that do not require the usual deposit, trade, and withdrawal cycle of a centralized exchange. You still need compatible wallets and sufficient source-side network resources.</p><h3>Is STON.fi cross-chain the same as a traditional bridge?</h3><p>Not in the classic lock-and-mint sense. STON.fi describes Omniston as an atomic cross-chain execution protocol using resolver liquidity and HTLC-based settlement. The objective is to exchange source-side value for a destination-side asset directly rather than asking you to mint and manage a wrapped representation through a conventional bridge workflow.</p><h3>Why do I need TRX if I am swapping USDT?</h3><p>TRON charges for network activity through Bandwidth and Energy. TRC-20 operations involve smart contracts, so the source transaction can consume these resources. When the account does not have enough allocated resources, TRX may be used to cover the cost. Check the wallet’s current estimate before confirming.</p><h3>What happens if the Omniston route fails halfway?</h3><p>The purpose of atomic settlement is to prevent a valid half-completed outcome. Linked HTLC conditions and timelocks provide completion and refund paths so the cross-chain exchange either settles as intended or unwinds according to the protocol rules. That is different from manually chaining several independent transactions together.</p><h3>What should I verify before making my first TRON to TON swap on STON.fi?</h3><p>Confirm TRON as the source, TON as the destination, both token selections, your destination TON wallet, expected output, current fee, and the TRX required for source-side execution. For a significant amount, consider testing the same route with a smaller transaction first.</p><h3>Sources and Further Reading</h3><p>STON.fi main website — current network support, cross-chain workflow, atomic execution, fees, and TON to TRON release information: <a href="https://ston.fi/?utm_source=chatgpt.com">STON.fi official website</a></p><p>STON.fi Cross-chain — current TON, TRON, and EVM support, wallet connection model, atomic execution, and cross-chain FAQ: <a href="https://cross-chain.ston.fi/?utm_source=chatgpt.com">STON.fi Cross-chain</a></p><p>STON.fi Cross-chain wallet guide — current desktop and mobile connection options for TON and TRON wallets: <a href="https://cross-chain.ston.fi/wallets?utm_source=chatgpt.com">How to connect wallets</a></p><p>Omniston explained — STON.fi’s explanation of resolver-based execution, RFQ liquidity discovery, HTLC settlement, and the distinction from traditional bridges: <a href="https://blog.ston.fi/omniston-explained-how-cross-chain-swaps-on-ton-work-without-a-bridge/?utm_source=chatgpt.com">Omniston explained</a></p><p>What is atomic swap execution and why does it matter? — explanation of hashlocks, timelocks, atomicity, and cross-chain failure handling: <a href="https://blog.ston.fi/what-is-atomic-swap-execution-and-why-does-it-matter/?utm_source=chatgpt.com">STON.fi guide to atomic swap execution</a></p><p>Cross-chain swap fees explained — breakdown of network costs, route fees, destination costs, and execution quality: <a href="https://blog.ston.fi/cross-chain-swap-fees-explained-what-youre-actually-paying/?utm_source=chatgpt.com">STON.fi cross-chain fee guide</a></p><p>TRON Bandwidth and Energy — official explanation of TRON’s network resource model and how contract interactions consume resources: <a href="https://developers.tron.network/docs/bandwidth-and-energy?utm_source=chatgpt.com">TRON Developer Hub: Bandwidth and Energy</a></p><p>TON Jetton documentation — official explanation of fungible tokens on TON, including USDT as a Jetton use case: <a href="https://docs.ton.org/standard/tokens/jettons/overview?utm_source=chatgpt.com">TON Docs: Jettons overview</a></p><p>Tether USDT on TRON — Tether’s official announcement and explanation of TRC-20 USDT on the TRON blockchain: <a href="https://tether.to/en/usdt-introduced-to-tron-blockchain/?utm_source=chatgpt.com">Tether: USDT introduced to TRON</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee36ff0a8cd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does “Best Rate” Mean in an Omniston-Powered Widget?]]></title>
            <link>https://medium.com/@ivan.zimanov/what-does-best-rate-mean-in-an-omniston-powered-widget-1988cb474008?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/1988cb474008</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[omniston]]></category>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[flutter-widget]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 06:51:02 GMT</pubDate>
            <atom:updated>2026-09-24T06:51:02.534Z</atom:updated>
            <content:encoded><![CDATA[<p>When an Omniston-powered swap widget shows a “best rate,” it does not mean that the interface has discovered one permanent, universal price for a token pair. It means Omniston has compared the eligible quotes available for your specific swap request and is presenting the most favorable one it currently has.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EGbigtMURmh58WcohpmiRg.png" /></figure><p>That distinction matters. The result depends on what you are swapping, how much, which assets are involved, the available liquidity, resolver responses, fees, routing constraints, and the moment when the quote is requested.</p><p>Omniston uses a Request for Quote model in which resolvers compete to provide executable swap quotes. Its documentation says quote updates can continue arriving, with the active quote changing when a more profitable deal for the trader appears.</p><p>So “best rate” is better understood as <strong>best currently available eligible quote for this exact request</strong>, not “the objectively best market price everywhere.”</p><h3>The rate belongs to a specific swap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YgjG8QS5j9YCQI8T6KqijQ.png" /></figure><p>A token does not have one swap rate that works independently of trade size and execution conditions.</p><p>Imagine that you enter:</p><ul><li>You send: 500 TON</li><li>You receive: USDT</li></ul><p>The widget does not simply look up a TON/USD market price and multiply it by 500. An executable DEX quote has to answer a more practical question:</p><p><strong>How much USDT can actually be delivered for this particular 500 TON swap under the current available routes and conditions?</strong></p><p>Omniston aggregates liquidity and pricing from connected sources rather than relying on a single liquidity pool. Official documentation describes it as an aggregation layer combining on-chain liquidity sources and RFQ resolvers.</p><p>A resolver can construct a route through supported liquidity venues and return a quote. Other resolvers may respond with different routes or prices. Omniston can then surface the more favorable quote.</p><p>That makes the amount important.</p><p>A route that is attractive for 10 TON might not be the strongest route for 5,000 TON. Larger trades can interact differently with pool depth, liquidity distribution, price impact, fees, and resolver inventory.</p><p>“Best rate” therefore always needs an implied suffix:</p><p><strong>Best rate for this swap request right now.</strong></p><h3>Where does the quote come from?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HAdcISkK0ht4m8KEBLps6g.png" /></figure><p>Omniston uses an RFQ process.</p><p>In simplified form:</p><ol><li>The widget sends a request describing the assets and amount.</li><li>Omniston makes that request available to eligible resolvers.</li><li>Resolvers calculate executable offers.</li><li>Quotes begin arriving.</li><li>A better quote can replace the previous one.</li><li>The selected quote is used to build the transaction if you decide to proceed.</li></ol><p>STON.fi’s resolver documentation describes resolvers as services that provide token exchange rates and execute trades. Multiple resolvers can compete for the same request, with the best quote being selected.</p><p>The quote can also contain route information. Omniston’s swap documentation describes routes as a sequence of steps and swap operations, including the assets being exchanged, the protocol used, the amount sent, and the expected amount received.</p><p>This is why aggregation can improve a swap without changing anything about the tokens themselves. The system is searching among available ways to execute the same requested exchange.</p><p>For a fixed-input swap, Quote B is economically more favorable in this simplified example because the same 500 TON produces more USDT.</p><p>The user normally does not need to manually inspect every resolver and pool to make that comparison. Aggregation moves that competition behind the swap interface.</p><h3>What is Omniston actually optimizing?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*St-7XhPZCg-i018nfZgqIg.png" /></figure><p>The most useful number is usually not an abstract exchange rate. It is the economic result of the quote.</p><p>Omniston quote data contains bid_units, representing the amount of the input asset the trader must pay, and ask_units, representing the amount of the output asset the trader will receive. The official documentation states that the bid amount includes fees and that the ask amount represents what the trader receives after fees.</p><p>That gives “best” two natural interpretations depending on how the swap is specified.</p><p><strong>If you fix the amount you send</strong>, a better quote generally means receiving more of the destination asset.</p><p><strong>If you fix the amount you want to receive</strong>, a better quote generally means needing less of the source asset.</p><p>There is an important qualification: network gas is represented separately in Omniston’s quote data through gas budget and estimated gas consumption fields.</p><p>So you should not automatically translate “best rate” into “lowest possible total cost under every imaginable accounting method.”</p><p>A quote may be the most favorable swap quote among the offers being compared while the transaction still requires network gas.</p><h3>A useful mental model</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5pCoVLn8eM3zV2vmLHJ3Lg.png" /></figure><p>Think of three layers:</p><ul><li><strong>Reference price:</strong> what the assets appear to be worth in a broader market context.</li><li><strong>Executable quote:</strong> what someone is currently willing and able to execute for your exact amount.</li><li><strong>Final settlement:</strong> what actually happens after you sign and the transaction executes.</li></ul><p>The “best rate” label belongs primarily to the second layer.</p><h3>Why can the best rate change while you are looking at it?</h3><p>Because the quote is live rather than permanent.</p><p>Omniston’s quote interface works as a stream. After a request is acknowledged, quote updates can arrive from resolvers, and the active quote can be updated when a more profitable offer appears. Quotes also contain timestamps and a trade-start deadline.</p><p>Several things can change during that process:</p><ul><li>pool reserves can move</li><li>another trade can change available liquidity</li><li>a resolver can update its offer</li><li>token prices can move elsewhere</li><li>a quote can approach its validity deadline</li><li>a different eligible route can become more attractive</li></ul><p>Suppose your widget initially displays 1,031 USDT for 500 TON. A few seconds later, another resolver offers 1,034 USDT.</p><p>The displayed best quote can improve.</p><p>The reverse problem also exists. If market conditions move before execution, the original economics may no longer remain available. This is one reason a quote should not be interpreted as a permanent promise about the token pair.</p><p>The protocol distinguishes quote discovery from execution. A quote tells you what is currently being offered. Your wallet still has to initiate the transaction, and the resulting trade then proceeds through its settlement flow.</p><h3>Best rate is not the same as minimum received</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dDQgvnHsC8Z1bLdcJ2uM4w.png" /></figure><p>These two numbers solve different problems.</p><p>The quote tells you the expected economic result.</p><p>Minimum received is a protection condition.</p><p>Omniston’s swap quote structure includes both a minimum ask amount and a recommended minimum ask amount, along with recommended slippage information. The transaction builder can also use Omniston’s recommended slippage rather than a trader-provided value.</p><p>Consider a simplified example:</p><p><strong>Current quote:</strong> 1,034 USDT<br><strong>Minimum acceptable amount:</strong> 1,023 USDT</p><p>The first number answers:</p><p><strong>What does the selected quote currently expect?</strong></p><p>The second answers:</p><p><strong>How far can execution deteriorate before this trade should no longer be accepted under the configured protection?</strong></p><p>They should not be treated as synonyms.</p><p>A minimum amount that is lower than the quote does not mean the system intentionally expects you to receive the minimum. It creates room for execution conditions to change within an accepted range.</p><p>Likewise, seeing a strong “best rate” does not make slippage controls irrelevant.</p><h3>Fees can affect which quote is actually best</h3><p>An Omniston-powered widget can include an integrator fee.</p><p>The current widget documentation allows an integrator to provide a referral address and configure a fee. Omniston’s quote data separately exposes protocol fee and referral fee information.</p><p>This matters because comparing raw liquidity prices while ignoring fees can produce a misleading answer.</p><p>Omniston also supports a flexible referral fee option. When enabled, resolvers can reduce the effective integrator fee if doing so unlocks a more favorable rate for the trader. The official guide explains that the fee can be reduced, but not increased, in this mode.</p><p>For someone using the widget, the practical lesson is simple:</p><p><strong>Compare what you actually send and receive, not just a headline exchange ratio.</strong></p><p>The quoted output is more meaningful than a theoretical pool price that cannot be obtained after routing and applicable swap fees.</p><p>Gas remains a separate consideration.</p><h3>Reading “best rate” in a STON.fi swap widget</h3><p>The STON.fi Swap Widget is built around Omniston and can be embedded by other applications. Its configuration allows an integrator to choose default assets, control the available token list, connect TON Connect, and optionally configure integrator fees.</p><p>Suppose you encounter the widget inside a wallet, DeFi dashboard, Telegram product, or another application.</p><p>You select TON and USDT and enter an amount.</p><p>From your perspective, the flow feels simple. You enter a trade and receive a quote.</p><p>Behind that interface, the relevant logic is closer to:</p><p><strong>Your requested swap</strong><br>→ <strong>Omniston RFQ</strong><br>→ <strong>eligible resolver responses</strong><br>→ <strong>candidate execution routes</strong><br>→ <strong>most favorable current quote</strong><br>→ <strong>transaction construction</strong><br>→ <strong>wallet approval</strong><br>→ <strong>execution and settlement</strong></p><p>The widget therefore does not need to expose every liquidity venue for aggregation to be useful. Its job is to turn the routing and quote competition into a usable swap experience.</p><h3>What to check before signing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5FHK2cy_41zvmzY6ACM4iQ.png" /></figure><p>Even when the interface says “best rate,” review:</p><ul><li>the exact input and output tokens</li><li>the amount you are sending</li><li>the expected amount you will receive</li><li>the minimum acceptable output, when shown</li><li>any visible fee information</li><li>the wallet transaction you are being asked to authorize</li></ul><p>The phrase “best rate” should make comparison easier. It should not replace transaction review.</p><p>A useful way to verify the concept yourself is to change only the trade amount while keeping the token pair the same. If the effective rate changes, that demonstrates why “best” belongs to a specific executable request rather than to the pair forever. You can also wait for quote refreshes and observe whether the expected output changes as new conditions are evaluated.</p><h3>Frequently Asked Questions</h3><h3>Does “best rate” mean the best price anywhere in crypto?</h3><p>No. It refers to the most favorable eligible quote Omniston has available for the specific request being processed. Omniston compares connected liquidity sources and resolver offers, not every possible market or private transaction venue in existence. The result also depends on the tokens, amount, routing conditions, fees, and current market state.</p><h3>Is the best rate guaranteed until I press swap?</h3><p>Not indefinitely. Omniston quotes contain timestamps and trade-start deadlines, and quote updates can arrive while an RFQ is active. Market and liquidity conditions can also change. A displayed quote should therefore be treated as a current executable offer subject to its validity and transaction conditions, rather than as a permanent exchange rate.</p><h3>Does best rate include fees?</h3><p>Omniston’s quote model defines the amount paid by the trader as including fees and the amount received as being after fees. Protocol and referral fee fields are also exposed separately in quote data. Network gas is represented separately, so “best quote” and “lowest total transaction cost including gas” are not automatically identical concepts.</p><h3>Why does the rate get worse when I increase the swap amount?</h3><p>Because executable pricing depends on available liquidity and routing at that size. A route capable of absorbing a small transaction efficiently may be less attractive for a much larger trade. Aggregation gives resolvers an opportunity to search for a stronger route, but it cannot make liquidity constraints disappear.</p><h3>Is best rate the same thing as lowest price impact?</h3><p>Not necessarily. Price impact describes how the trade interacts with available liquidity and affects execution pricing. “Best rate” compares the resulting eligible offers for your request. A resolver may find a better overall result through another route even though individual pools or route components have different liquidity characteristics.</p><h3>Is minimum received the same as the quoted amount?</h3><p>No. The quote is the expected output associated with the selected offer. Minimum received is a protection threshold used to define how much deterioration can be accepted. Omniston’s swap data distinguishes quoted ask units from minimum ask amounts and recommended slippage settings.</p><h3>Can an integrator fee change the best rate in an Omniston widget?</h3><p>Yes. The widget can be configured with an integrator fee, and fees affect the economics of a quote. Omniston also supports a flexible fee mode in which the effective integrator fee can be reduced when doing so allows a better rate for the trader.</p><h3>How should I interpret “best rate” before confirming a STON.fi widget swap?</h3><p>Read it as the most favorable current eligible Omniston quote for the exact swap you entered. Then verify the tokens, input amount, expected output, protection settings, fees, and wallet transaction before signing. The label is useful for route comparison, but your final decision should still be based on the actual transaction details displayed for that swap.</p><h3>Sources and Further Reading</h3><p>Omniston Protocol — official overview of aggregation, RFQs, liquidity sources, and integration options. <a href="https://docs.ston.fi/developer-section/omniston?utm_source=chatgpt.com">STON.fi Omniston Protocol documentation</a></p><p>Omniston Swap Overview — official technical reference for quote requests, quote updates, amounts, fees, routes, deadlines, slippage, and trade tracking. <a href="https://docs.ston.fi/developer-section/omniston/swap/overview?utm_source=chatgpt.com">STON.fi Omniston Swap Overview</a></p><p>Resolvers — explanation of how resolvers provide competing quotes and execute winning trades. <a href="https://docs.ston.fi/developer-section/omniston/resolvers?utm_source=chatgpt.com">STON.fi Resolvers documentation</a></p><p>Resolver Integration Guide — detailed description of resolver quote submission, validation, updating, and invalidation. <a href="https://docs.ston.fi/developer-section/omniston/resolvers/guide?utm_source=chatgpt.com">STON.fi Resolver Integration Guide</a></p><p>React SDK — official SDK reference covering streamed quote updates and the fields contained in an Omniston quote. <a href="https://docs.ston.fi/developer-section/omniston/sdk/react?utm_source=chatgpt.com">STON.fi Omniston React SDK documentation</a></p><p>Referral Fees — official explanation of integrator fees and the flexible referral fee mechanism. <a href="https://docs.ston.fi/developer-section/omniston/referral-fees?utm_source=chatgpt.com">STON.fi Omniston Referral Fees guide</a></p><p>STON.fi Swap Widget Full Guide and Reference — official documentation for embedding and configuring the Omniston-powered swap widget. <a href="https://docs.ston.fi/developer-section/widget/widget?utm_source=chatgpt.com">STON.fi Swap Widget documentation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1988cb474008" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Transaction Deadlines Reduce One Class of STON.fi Execution Risk]]></title>
            <link>https://medium.com/@ivan.zimanov/how-transaction-deadlines-reduce-one-class-of-ston-fi-execution-risk-5da61b733aa9?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5da61b733aa9</guid>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[cross-chain-swap]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[transactions]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Wed, 23 Sep 2026 06:47:01 GMT</pubDate>
            <atom:updated>2026-09-23T06:47:01.709Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why a time limit can stop an old swap from executing after conditions have moved on, and why that protection is different from slippage control.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qRVe7BdcZacd17XD1kF-PQ.png" /></figure><p>A transaction deadline reduces a very specific execution risk: the risk that an already prepared STON.fi operation reaches the relevant DEX contracts much later than intended and still executes under conditions the sender no longer considers timely.</p><p>STON.fi DEX v2 includes an execution deadline in swap payloads. When the operation is processed after that timestamp, the contracts can reject the expired operation instead of continuing normally. STON.fi introduced this feature specifically in response to cases where blockchain transaction processing could take unusually long under high load.</p><p>That is useful protection, but it is deliberately narrow. A deadline does not guarantee a good exchange rate, prevent price impact, verify the token you selected, or make every multi-contract operation atomic. To understand what it does protect, it helps to separate time risk from price risk.</p><h3>The risk begins after you decide to trade</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-VjbUzVTfbUh6QW1y01wog.png" /></figure><p>Imagine you receive a swap quote, review it, and approve the transaction. Under normal conditions, the transaction reaches the blockchain quickly and the relevant contracts process it while the market still resembles the one you saw.</p><p>Now change one detail: processing is delayed.</p><p>The transaction may spend longer than expected between signing, wallet submission, inclusion on-chain, token transfer processing, Router handling, and Pool execution. During that interval, other users can trade, pool reserves can change, and your original decision can become stale.</p><p>Without a time boundary, an old transaction could remain eligible for execution simply because its other conditions are still technically valid.</p><p>A deadline asks a different question:</p><p><strong>Is this operation still timely enough to execute at all?</strong></p><p>That creates a clear temporal boundary between an operation you still authorize and one that has become too old.</p><h3>A simple example</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eulaW4rXeKATNOnZkOcjsA.png" /></figure><p>Suppose you prepare a swap at 12:00 and the swap carries a 12:15 execution deadline.</p><ul><li>At 12:02, the deadline condition is still satisfied.</li><li>At 12:14, the transaction can still proceed if its other requirements are satisfied.</li><li>At 12:16, the operation is expired and should follow the failure or refund path rather than execute normally.</li></ul><p>The deadline does not ask whether the price changed by 0.1%, 2%, or 20%. It only compares execution time with the timestamp encoded into the operation.</p><p>That is why deadlines should be understood as <strong>time-based execution protection</strong>, not price protection.</p><h3>STON.fi v2 puts the deadline inside the DEX operation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JkJ1gMWUIjmkylAc-vNJ4A.png" /></figure><p>The distinction matters because STON.fi DEX v2 does not rely only on a front-end timer.</p><p>Its Router specification includes a deadline field in the swap payload. The field is a uint64 timestamp described as the execution deadline for the transaction. The same architecture also carries a deadline in liquidity-provision payloads and cross-swap payloads.</p><p>At the contract level, a normal swap payload includes information such as:</p><ul><li>the other Router token wallet</li><li>the refund address</li><li>the excesses address</li><li>the transaction deadline</li><li>the minimum output</li><li>the receiving address</li><li>optional custom and referral data</li></ul><p>That placement is important. The deadline travels with the swap instructions that the contracts process. It is therefore part of the conditions governing execution, rather than merely a countdown displayed by an interface.</p><p>STON.fi’s documented v2 exit codes also distinguish expiration from other failure reasons. The documentation lists separate codes for a transaction that expires at the Router and for a swap that expires at the Pool. It separately identifies failures caused by insufficient liquidity, zero output, slippage, a locked pool, and other conditions.</p><p>The separation tells you something useful: <strong>expiration is its own execution condition</strong>.</p><h3>Deadline and minimum received solve different problems</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JkuONQKyHMAfiFdTXwy4Cg.png" /></figure><p>The most important misconception is to treat a deadline as another form of slippage protection.</p><p>They complement each other, but they do different jobs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rW0zX07tNbJieXodi-t3aw.png" /></figure><p>STON.fi’s Router documentation defines min_out as the minimum required number of tokens to receive, and explicitly notes that the swap fails if the resulting output is below that value. The deadline sits separately in the same payload structure.</p><p>Consider a hypothetical swap that expects 1,000 units of an output token with a minimum received value of 990.</p><p>If the transaction executes five minutes later and the Pool can still return 995, the price condition may pass and the transaction can execute if the deadline has not expired.</p><p>If the Pool can return only 985, the minimum-output condition fails even if execution occurs almost immediately.</p><p>If the Pool could return 995 but the transaction arrives after its deadline, the time condition fails instead.</p><p>These are three different states. Combining a deadline with a sensible minimum output therefore protects against more than either condition can cover alone.</p><h3>Why delayed execution can matter even when slippage is limited</h3><p>You might ask: if min_out already prevents execution below an acceptable output, why is a deadline necessary?</p><p>Because your decision can become stale for reasons that are not fully represented by one minimum-output number.</p><p>Perhaps the market moved dramatically and then returned to a level that satisfies your old minimum. Perhaps the trade was part of another manual action that you already abandoned. Perhaps you submitted a replacement strategy elsewhere. Perhaps the broader market context changed enough that you simply would not authorize the same trade now.</p><p>A minimum output says:</p><p><strong>“Do not give me less than this amount.”</strong></p><p>A deadline says:</p><p><strong>“Do not execute this instruction after this time.”</strong></p><p>Those are different dimensions of intent.</p><p>The second condition is particularly useful for transactions that are delayed unexpectedly. STON.fi’s SDK changelog explains that the optional deadline was added to v2.1 swap and liquidity operations because blockchain processing can occasionally take longer during high load. The changelog documented a 15-minute default when the feature was introduced.</p><p>That historical default is useful context, but integrations should rely on the behavior of the SDK and contract version they actually use rather than hardcoding assumptions from an older release note.</p><h3>There are actually two time limits you may encounter</h3><p>TON applications can introduce another deadline-like value before the STON.fi contracts even receive the operation.</p><p>When a transaction is sent through TonConnect, the transaction request can include validUntil. STON.fi&#39;s own TonConnect example demonstrates this field when sending SDK-generated transaction parameters.</p><p>TON wallets themselves also use a valid_until timestamp in signed external messages. TON documentation explains that the wallet rejects an external message once the current time exceeds that value. This limits how long the signed wallet message remains usable and works together with the wallet&#39;s sequence number for replay protection.</p><p>So there can be two separate time boundaries:</p><ol><li><strong>Wallet-level validity</strong> limits how long the signed request can be accepted by the wallet.</li><li><strong>STON.fi DEX deadline</strong> limits how long the swap or liquidity operation remains valid as it moves through DEX execution.</li></ol><p>These should not be collapsed into one concept.</p><p>A wallet-level expiry can prevent a stale signed request from entering the transaction flow at all. A DEX-level deadline remains relevant because TON execution can involve asynchronous internal messages after the originating wallet transaction has already been accepted.</p><h3>Following a delayed STON.fi swap</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T2FCn8F4oMxh9HRrAaeGYA.png" /></figure><p>STON.fi’s v2 architecture makes this easier to see because a swap is not one monolithic calculation.</p><p>The user’s asset transfer reaches the Router through the relevant jetton wallet flow. The Router identifies the appropriate Pool and forwards the swap operation. The Pool then calculates the result and, on success, initiates the outgoing transfer path.</p><p>Suppose a swap is created with:</p><ul><li>a defined input amount</li><li>a minimum acceptable output</li><li>a refund address</li><li>an execution deadline</li></ul><p>If it progresses normally before expiry, the deadline does nothing visible. It acts as a boundary that the execution never crosses.</p><p>If processing becomes unusually delayed, expiration becomes relevant. STON.fi’s documented transfer exit codes include transfer_bounce_tx_expired for expiration at the Router and swap_refund_tx_expired for expiration at the Pool.</p><p>That is the class of risk the deadline reduces: <strong>very late execution of an operation whose intended lifetime has already ended</strong>.</p><h3>Expiration does not make TON transactions atomic</h3><p>There is an important limitation.</p><p>STON.fi’s documentation notes that TON multi-contract transactions are not atomic in the way a single all-or-nothing execution might be on another architecture. In a cross-swap, if a later stage fails, a complete reversal to the original starting asset is not always possible. The user can instead receive an intermediate token associated with the route already executed.</p><p>This matters when thinking about deadlines.</p><p>A deadline can stop an expired stage from executing normally, but it cannot rewind the blockchain and erase earlier messages that have already completed.</p><p>For a simple swap, the failure and refund path may be relatively straightforward. For a multi-hop or multi-Router route, execution can already have progressed before a later condition fails.</p><p>So the safe mental model is not:</p><p><strong>“Deadline means nothing happens after expiry.”</strong></p><p>It is:</p><p><strong>“The contracts can reject execution that reaches the relevant deadline check too late, then use the protocol’s applicable failure or refund logic.”</strong></p><p>That wording better matches an asynchronous multi-contract environment.</p><h3>What deadlines do not protect you from</h3><p>A deadline is valuable precisely because its purpose is narrow. Expanding that purpose in your head creates false confidence.</p><p>It does not protect against:</p><ul><li>selecting the wrong token or contract</li><li>signing a transaction to an incorrect destination</li><li>excessive price impact before the deadline</li><li>an overly loose minimum received setting</li><li>smart-contract vulnerabilities</li><li>malicious assets</li><li>insufficient gas</li><li>pool liquidity disappearing</li><li>execution failure for unrelated contract reasons</li><li>losses already incurred in an earlier stage of a non-atomic multi-hop route</li></ul><p>STON.fi documents multiple failure conditions independently of expiration, including low output, insufficient liquidity, locked contracts, low gas, and invalid requests.</p><p>A deadline should therefore sit beside other execution controls, not replace them.</p><h3>A practical STON.fi review workflow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ShuxH0_Q4rLntxocCRcc1A.png" /></figure><p>For a current production integration, STON.fi recommends an API-driven v2 workflow: simulate the swap first, use the Router metadata returned by the API, create the correct contracts through the SDK factory, and build the transaction from the simulation result. The current SDK guide specifically recommends reusing simulated values such as the input amount and minAskUnits when constructing the actual swap.</p><p>When reviewing a swap from the perspective of deadline risk, check four things:</p><ol><li><strong>Quote freshness.</strong> If substantial time has already passed before signing, simulate again rather than relying on an old quote.</li><li><strong>Minimum output.</strong> Make sure the encoded minimum still reflects the downside you are willing to accept.</li><li><strong>DEX deadline.</strong> For integrations that expose or configure it, use a lifetime that matches the intended transaction workflow rather than an unnecessarily long one.</li><li><strong>Wallet validity.</strong> If TonConnect or another wallet layer uses its own validity window, remember that this controls the signed wallet request, not the entire downstream DEX message chain.</li></ol><p>A shorter deadline reduces the amount of time an operation remains executable, but making it unrealistically short can create unnecessary expirations during legitimate network delays. A longer deadline gives the network more time to complete the flow, but also extends the period during which the original instruction remains live.</p><p>The correct trade-off is therefore not “shortest possible.” It is <strong>long enough for normal execution, short enough that you would still stand behind the instruction throughout that period</strong>.</p><p>For STON.fi specifically, the easiest way to observe the concept is to compare the v2 Router payload fields with the documented expiration and slippage exit codes. You can see that deadline and min_out are independent controls. One limits <em>when</em> execution remains acceptable; the other limits <em>what output</em> remains acceptable. Together, they define a more precise boundary around the swap you intended to authorize.</p><h3>Frequently Asked Questions</h3><h3>What is a transaction deadline in a DEX swap?</h3><p>It is a timestamp after which the relevant smart contract should no longer execute the operation normally. In STON.fi DEX v2, the swap payload contains a dedicated deadline field. The purpose is to prevent an operation from remaining executable indefinitely when processing has been delayed beyond the period the sender intended.</p><h3>Is a deadline the same as slippage tolerance?</h3><p>No. Slippage protection controls the acceptable execution result, usually through a minimum output. A deadline controls time. A swap can fail because its output is too low even before the deadline, or it can expire even when the current output would otherwise satisfy the minimum.</p><h3>Can a deadline prevent all losses caused by market movement?</h3><p>No. Prices and Pool reserves can change while the transaction is still inside its allowed time window. The deadline does not impose a price limit. Minimum received and other quote parameters are what constrain the acceptable output, while the deadline only limits how long the instruction remains valid.</p><h3>Why not simply use a very long deadline?</h3><p>A very long deadline gives delayed processing more time to succeed, but it also keeps your old instruction executable for longer. If your trading decision is highly time-sensitive, that may not reflect your intent. The useful window is one that accommodates ordinary processing without keeping stale instructions alive unnecessarily.</p><h3>What happens when a STON.fi v2 swap expires?</h3><p>STON.fi documents expiration-specific failure codes at both Router and Pool stages. The operation enters the applicable failure or refund path rather than completing as a normal swap. The exact result depends on where the operation has progressed, particularly for multi-contract and cross-swap routes.</p><h3>Does TonConnect validUntil replace the STON.fi deadline?</h3><p>No. TonConnect’s transaction validity applies to the wallet transaction request. STON.fi’s DEX deadline is carried inside the DEX operation itself. They operate at different layers and can both be useful in the same transaction flow.</p><h3>Are deadlines only used for STON.fi swaps?</h3><p>No. STON.fi DEX v2 also documents deadlines for liquidity-provision operations, and deadline fields appear in cross-swap payloads as well. The same principle applies: an operation can be rejected when it reaches execution after its allowed lifetime.</p><h3>What should I check before signing a STON.fi swap with deadline protection?</h3><p>Review the fresh simulated quote, input amount, minimum received, selected assets, Router information, and wallet transaction details. Then treat the deadline as an additional time boundary, not as a substitute for those checks. If the quote has become stale before you sign, obtain a new simulation rather than relying on the deadline to compensate for an outdated decision.</p><h3>Sources and Further Reading</h3><p>STON.fi Router v2 — low-level Router specification showing the swap deadline, min_out, refund data, and related payload fields: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/router?utm_source=chatgpt.com">STON.fi Router v2 documentation</a></p><p>STON.fi DEX v2 Smart Contracts — overview of v2 features including transaction-completion deadlines for swaps and liquidity provision: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2?utm_source=chatgpt.com">STON.fi DEX v2 smart-contract documentation</a></p><p>STON.fi v2 Op Codes — documented Router and Pool expiration codes alongside slippage, liquidity, gas, and other failure reasons: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/op-codes?utm_source=chatgpt.com">STON.fi v2 op-codes reference</a></p><p>STON.fi Swap Examples — diagrams and explanations of simple swaps, cross-swaps, and refund behavior in TON’s non-atomic multi-contract execution model: <a href="https://docs.ston.fi/developer-section/dex/smart-contracts/v2/examples/swap?utm_source=chatgpt.com">STON.fi v2 swap examples</a></p><p>STON.fi SDK Changelog — historical release note explaining the introduction and motivation of the optional v2.1 deadline: <a href="https://github.com/ston-fi/sdk/blob/main/CHANGELOG.md?utm_source=chatgpt.com">STON.fi SDK changelog</a></p><p>STON.fi Swap v2 SDK Guide — current production workflow using swap simulation, Router metadata, dexFactory(), and simulated minimum-output values: <a href="https://docs.ston.fi/developer-section/dex/sdk/v2/swap?utm_source=chatgpt.com">STON.fi v2 SDK swap guide</a></p><p>STON.fi Transaction Sending via TonConnect — example of sending SDK-generated STON.fi transaction parameters with wallet-level validUntil: <a href="https://docs.ston.fi/developer-section/common/transaction-sending/tonconnect?utm_source=chatgpt.com">STON.fi TonConnect transaction-sending guide</a></p><p>TON Wallet Documentation — explanation of wallet valid_until, sequence numbers, and the lifetime of signed external messages: <a href="https://docs.ton.org/standard/wallets/how-it-works?utm_source=chatgpt.com">TON wallet operation documentation</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5da61b733aa9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How STON.fi DAO Governance Connects Community Decisions to Real-World Execution]]></title>
            <link>https://medium.com/@ivan.zimanov/how-ston-fi-dao-governance-connects-community-decisions-to-real-world-execution-82e95e08e3a4?source=rss-36ca3ad36ac9------2</link>
            <guid isPermaLink="false">https://medium.com/p/82e95e08e3a4</guid>
            <category><![CDATA[dao]]></category>
            <category><![CDATA[stonfi]]></category>
            <category><![CDATA[ston-fi-project]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Crypto Vazima]]></dc:creator>
            <pubDate>Wed, 23 Sep 2026 06:45:56 GMT</pubDate>
            <atom:updated>2026-09-23T06:45:56.947Z</atom:updated>
            <content:encoded><![CDATA[<p><em>STON.fi separates community decision-making from operational execution, creating a path from staked voting power to proposals, on-chain votes, treasury authorization, technical work, and real-world implementation.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VcV60Vek4J0-FqorPYjreQ.png" /></figure><p>STON.fi DAO governance does not end when a proposal receives enough votes. A successful vote is the point where a community decision becomes authorized. The actual work may still require treasury transactions, multisig signatures, software development, contractors, legal agreements, infrastructure changes, or other actions that cannot be performed simply by counting votes.</p><p>STON.fi connects these two layers through a governance structure in which the community proposes and approves direction, while Ston Foundation acts as an execution and coordination entity for approved actions. The distinction is important because it explains what an on-chain DAO vote can control, what still needs human execution, and how you can follow a decision from an idea to an implemented result.</p><h3>The governance system has two connected layers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_fIt0mrCJRz7pRYmDZ6Ejw.png" /></figure><p>A useful way to understand STON.fi governance is to separate <strong>decision authority</strong> from <strong>execution capacity</strong>.</p><p>The DAO provides the decision layer. Community members stake STON, receive voting power through ARKENSTON, submit proposals when they meet the required threshold, discuss those proposals, and cast on-chain votes. The governance contracts record participation and determine whether a proposal passes.</p><p>The Foundation provides much of the execution layer. STON.fi’s Governance Rules state that the DAO itself is a community governance forum rather than a legal entity capable of entering contracts or directly carrying out every protocol operation. Approved actions can therefore move to the Foundation for implementation under legal and operational requirements.</p><p>That creates a chain rather than a single event:</p><ol><li>A governance participant develops an idea.</li><li>The proposal becomes visible to the community.</li><li>Eligible participants vote with ARKENSTON voting power.</li><li>The governance system determines the result on-chain.</li><li>An accepted proposal becomes authorization for the approved action.</li><li>The Foundation, contributors, multisig signers, or other responsible parties carry out the required work.</li><li>Implementation can then be reflected in the DAO record.</li></ol><p>The distinction prevents a common misunderstanding about DAOs. “On-chain governance” does not necessarily mean that every successful vote automatically modifies a smart contract or sends money at the moment voting closes.</p><h3>STON staking turns participation into voting power</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kO_th3T9e_BwBXzrCgQqLQ.png" /></figure><p>STON.fi does not assign governance influence simply because an address holds STON.</p><p>To participate through voting power, STON is staked for a lock period between 3 and 24 months. The staking position creates ARKENSTON, a soulbound NFT connected to the wallet. ARKENSTON represents voting power and is non-transferable. Voting weight depends on factors including the amount of STON staked and the duration of the lock.</p><p>The result is a commitment-based governance model. A person who locks more STON for longer can receive greater voting power than someone making a smaller or shorter commitment.</p><p>Voting power is also dynamic. The Governance Rules explain that it changes according to the staking formula and can be affected by time, restaking, unstaking, and changes in total protocol voting power. Thresholds and quorum values are calculated using voting power rather than a simple count of wallets.</p><h3>What ARKENSTON does</h3><ul><li>It represents a staked governance position.</li><li>It determines how much voting power that position contributes.</li><li>It can be used to vote on active proposals when the stake remains eligible.</li><li>Sufficient voting power is also required to create proposals.</li><li>The token is soulbound, so governance weight is tied to the staking position rather than freely transferable as an ordinary NFT.</li></ul><p>This is the first connection between economic commitment and governance. The next connection is between governance and an actionable decision.</p><h3>A proposal moves through discussion before it becomes a decision</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w5uIf26vzbGZ1FEpxPRaZg.png" /></figure><p>STON.fi governance deliberately separates writing a proposal from voting on it.</p><p>According to the Governance Rules, an eligible participant can first prepare a draft privately. Publishing that draft creates an on-chain proposal record and begins the Discussion phase. The standard discussion period is seven days, during which the community can inspect the proposal and provide feedback. The proposer can still revise it, although an update to the proposal content resets the discussion timer so the community has time to assess the new version.</p><p>After discussion, the proposal can enter voting.</p><p>The standard voting period is 14 days. Eligible ARKENSTON holders vote either For or Against, with voting weight based on the governance power they use. Quorum must also be reached. If the required participation and acceptance conditions are satisfied, the proposal is recorded as accepted. STON.fi’s current DAO interface also describes an extension mechanism that can add a 72-hour stability window when quorum is newly reached or the projected result changes during the final part of voting.</p><p>At that point, something important has happened: the community has produced an on-chain governance decision.</p><p>But that still does not necessarily mean the requested action has occurred.</p><h3>Accepted and implemented are different states</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*weUrFBHey-5OFHjRm7v39A.png" /></figure><p>STON.fi’s Governance Rules explicitly distinguish a proposal that has <strong>Passed</strong> from one that has been <strong>Implemented</strong>.</p><p>The voting contracts can automatically determine whether voting conditions have been satisfied and record the result. Execution is different. A passed proposal may move into an off-chain implementation phase under Foundation oversight. Once the approved action has actually been carried out, an authorized DAO Manager can mark the proposal as Implemented.</p><p>That distinction is especially easy to see with proposals involving treasury funds.</p><p>A vote can authorize a budget or transfer, but governance contracts cannot hire a developer, negotiate with a service provider, pay an invoice under a commercial agreement, satisfy a jurisdictional requirement, or coordinate a technical deployment by themselves.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dgvaaUEotBwEKOgZOTcM9g.png" /></figure><p>This hybrid design is the bridge between blockchain governance and the operational world.</p><h3>Why the Ston Foundation is part of the execution path</h3><p>The role of the Foundation was itself addressed through governance.</p><p>An accepted December 2025 proposal formalized Ston Foundation as the DAO’s authorized representative for implementing community-approved decisions. The proposal describes the DAO as lacking the legal capacity to sign contracts, manage assets directly, or interact with external counterparties in the way a legal entity can. It therefore authorized the Foundation to perform functions such as treasury operations, budget management, contributor engagement, technical deployments, administrative processes, and external representation when those actions are approved through governance.</p><p>That does not mean every operational decision requires a separate community vote at the level of individual invoices or contractor choices.</p><p>Instead, governance can approve a scope and authorization boundary. The Foundation can then execute inside that boundary. If a material change goes beyond what the DAO approved, another proposal may be required.</p><p>The model can be summarized as:</p><p><strong>Community decides the mandate -&gt; governance records authorization -&gt; the execution entity works within that mandate.</strong></p><p>A real STON.fi proposal makes this much easier to see.</p><h3>Following the 2026 operational budget from vote to execution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u3FuTxdpS9WrxwNQVY1btw.png" /></figure><p>The STON.fi DAO’s 2026 operational budget proposal is a practical example of governance moving beyond an abstract opinion poll.</p><p>The proposal requested authorization for an annual operational cap of $2.5 million in specified assets plus a separate allocation of 4 million STON. The defined purposes included protocol development and maintenance, infrastructure, contributors, ecosystem activity, communications, operational support, and other approved categories. The vote concluded on April 1, 2026, and the proposal page’s timeline includes the Implemented stage.</p><p>The interesting part is what happens after approval.</p><p>The proposal authorizes Ston Foundation to receive funds within the approved limits and use them for the specified purposes. It also allows the Foundation to select and manage contractors and service providers within the authorized development directions and budget.</p><p>That is where a governance decision becomes operational activity.</p><p>For example, the DAO does not need to vote separately on every developer contract. It approves the budget, permitted categories, development directions, and execution mandate. The Foundation can then coordinate contributors and payments within those constraints.</p><p>The same proposal establishes limits on that discretion. Expenditures must remain within the authorized scope and budget cap, and material changes to the scope, categories, or overall budget require another DAO proposal. It also requires periodic reporting to the DAO, at least quarterly, at a high-level expenditure level while allowing sensitive contractual, personal, or security information to remain confidential.</p><p>So the governance loop becomes:</p><p><strong>proposal -&gt; community authorization -&gt; operational mandate -&gt; spending and work -&gt; reporting and accountability.</strong></p><p>That is a much more complete picture of DAO governance than simply looking at the final vote count.</p><h3>Execution includes safeguards as well as authority</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F9-MiharG98GJ00x1iQY7Q.png" /></figure><p>Moving from a public vote to real protocol changes creates risks that do not exist at the discussion stage.</p><p>An approved proposal could contain an implementation error. Market or technical conditions could change. A treasury transaction could require additional checks. A protocol deployment could expose security concerns discovered only after voting ends.</p><p>STON.fi’s Governance Rules therefore describe a timelock safeguard for binding actions, particularly protocol changes or significant treasury disbursements. The delay creates an additional review window before the Foundation multisig executes the relevant change or transfer.</p><p>The Rules also make clear that governance does not override legal and security responsibilities. The Foundation can delay or refuse execution in exceptional circumstances when it considers an action unlawful, unsafe, or incompatible with its legal responsibilities. DAO votes are described as governance authorizations rather than enforceable contracts against the Foundation.</p><p>That limitation is worth understanding before interpreting an accepted proposal as unconditional automatic execution.</p><p>The community has meaningful decision-making power, but the system deliberately retains an operational layer capable of dealing with security, compliance, technical feasibility, contracts, and other real-world constraints.</p><h3>How to verify the full path yourself</h3><p>You can inspect STON.fi governance more usefully by following a proposal beyond the headline vote.</p><p>Start at the DAO proposal page and check what the proposal actually authorizes. Look for its scope, requested budget or protocol change, implementation conditions, and any limitations placed on the executor.</p><p>Then compare four things:</p><ul><li><strong>Discussion:</strong> What exactly was proposed, and did the text change before voting?</li><li><strong>Vote:</strong> Was quorum reached, and how much voting power supported or opposed the proposal?</li><li><strong>Authorization:</strong> What actions did the accepted proposal permit?</li><li><strong>Implementation:</strong> Has the proposal moved from accepted to implemented, and what observable actions or reports correspond to that implementation?</li></ul><p>The accepted proposal to convert part of STON.fi protocol fees into STON and GEMSTON provides another example. The DAO approved high-level rules for treasury acquisitions, while the detailed execution mechanics were left to designated contributors under Foundation oversight and subject to infrastructure readiness and compliance requirements.</p><p>That separation is not an exception. It is a core part of how STON.fi connects collective governance with practical execution.</p><p><strong>Practical takeaway:</strong> when reviewing a STON.fi DAO decision, do not stop at whether the proposal passed. Read what it actually authorizes, identify who is responsible for implementation, check the limits placed on that authority, and look for the transition from Accepted to Implemented. That gives you a much clearer picture of whether community governance has translated into observable action.</p><h3>Frequently Asked Questions</h3><h3>Does a successful STON.fi DAO vote automatically execute a protocol change?</h3><p>Not necessarily. The governance system can record voting and determine whether a proposal passes, but the official Governance Rules explicitly allow accepted proposals to move into an implementation phase. Technical changes, treasury operations, contracts, or other real-world actions may then require execution by the Foundation, multisig signers, contributors, or service providers.</p><h3>Who can vote in the STON.fi DAO?</h3><p>Governance voting power comes from staking STON and receiving ARKENSTON. ARKENSTON is a soulbound NFT representing the voting power of the staking position. The amount of STON, lock duration, timing, and staking mechanics affect that voting power. Merely holding unstaked STON does not provide the same DAO voting power.</p><h3>How long does a STON.fi governance proposal take?</h3><p>The standard public lifecycle includes a seven-day Discussion phase followed by a 14-day Voting phase. The current DAO interface also describes a 72-hour extension mechanism for certain late changes in quorum or the projected voting result. Actual implementation can take additional time because it depends on the type of approved action.</p><h3>What is the difference between Accepted and Implemented?</h3><p>Accepted means the governance vote has satisfied the conditions required for approval. Implemented means the authorized action has subsequently been carried out and recorded as completed. The distinction is particularly important for proposals involving budgets, external counterparties, software development, or treasury transactions.</p><h3>Can the STON.fi DAO control treasury spending?</h3><p>DAO proposals can approve treasury allocations, budgets, and related economic policies. The 2026 operational budget, for example, defined spending caps, permitted categories, execution authority, and reporting requirements. Actual administration and payments are handled through the operational execution structure rather than through the vote count alone.</p><h3>Why is Ston Foundation needed if governance is on-chain?</h3><p>On-chain governance can transparently record proposals, votes, and results, but it cannot perform every legal or operational task required to run a protocol. Ston Foundation acts as an execution and coordination entity that can manage counterparties, treasury operations, administrative work, technical deployments, and other approved activities within the DAO’s authorization.</p><h3>Can the Foundation ignore a DAO decision?</h3><p>The Governance Rules state that approved decisions are carried out on a best-effort basis within legal and practical constraints. They also reserve the ability to delay or refuse an action in exceptional circumstances involving law, security, or the Foundation’s responsibilities. That means governance authorization is significant, but it is not identical to an automatically enforceable legal contract.</p><h3>How can I check whether a STON.fi DAO decision was actually executed?</h3><p>Open the relevant proposal on dao.ston.fi and follow its lifecycle rather than looking only at the vote totals. Read the authorized scope, check the voting result, identify the party responsible for execution, and look for an Implemented status plus any related treasury activity, deployment, reporting, or other evidence appropriate to that proposal.</p><h3>Sources and Further Reading</h3><p>STON.fi DAO About — current overview of staking, ARKENSTON voting power, proposal stages, quorum, voting, and governance participation: <a href="https://dao.ston.fi/about?utm_source=chatgpt.com">STON.fi DAO About</a></p><p>STON.fi DAO Governance Rules — official governance framework covering proposal eligibility, voting, execution, timelocks, Foundation responsibilities, moderation, and safeguards: <a href="https://static.ston.fi/dao/DAO_Governance_Rules.pdf?utm_source=chatgpt.com">STON.fi DAO Governance Rules PDF</a></p><p>STON.fi Help Center, What is the STON.fi DAO? — concise explanation of participation and the proposal lifecycle: <a href="https://help.ston.fi/hc/en-us/articles/28370533885340-What-is-the-STON-fi-DAO?utm_source=chatgpt.com">STON.fi DAO Help Center guide</a></p><p>STON.fi DAO launch article — background on the launch of the governance system and the connection between voting and Foundation-led implementation: <a href="https://blog.ston.fi/from-users-to-governors-ston-fi-launches-tons-first-full-dao/?utm_source=chatgpt.com">From users to governors: STON.fi launches TON’s first full DAO</a></p><p>Delegation of authority to Ston Foundation as the DAO’s representative — accepted proposal defining the Foundation’s operational and representative mandate: <a href="https://dao.ston.fi/proposal/EQAxx_aLDGHt_9GOQIBMvXi8UAc0pcqETWfdgqohk2zQZbsm?utm_source=chatgpt.com">Delegation of authority proposal</a></p><p>Approval of Operational Budget Allocation to Ston Foundation for 2026 — detailed example of DAO-approved spending limits, execution authority, contractor management, and reporting requirements: <a href="https://dao.ston.fi/proposal/EQAxCNFNxVKsBwiTvU-_0fe1baHCYQeRRQ_NSuv5_pUwCWry?utm_source=chatgpt.com">2026 operational budget proposal</a></p><p>Convert protocol fees to STON and GEMSTON tokens — example of the DAO approving economic policy while leaving detailed execution mechanics to contributors operating under Foundation oversight: <a href="https://dao.ston.fi/proposal/EQAxD9y1V_dL5a7o0VB4Dq3JrjBgr1r8WZ6D8T3Xp61orukV?utm_source=chatgpt.com">Protocol fee conversion proposal</a></p><p>STON.fi DAO proposals — current public proposal directory for reviewing accepted, rejected, voting, and discussion-stage governance activity: <a href="https://dao.ston.fi/?utm_source=chatgpt.com">STON.fi DAO proposals</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82e95e08e3a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>