<?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 Nura Musa on Medium]]></title>
        <description><![CDATA[Stories by Nura Musa on Medium]]></description>
        <link>https://medium.com/@nuraibrahim1043?source=rss-86588d9fc8f8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8UUlAUXfkWyz-k6Ixn3FQA@2x.jpeg</url>
            <title>Stories by Nura Musa on Medium</title>
            <link>https://medium.com/@nuraibrahim1043?source=rss-86588d9fc8f8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:59:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nuraibrahim1043/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[What Is a DEX and How Does It Work?]]></title>
            <link>https://medium.com/@nuraibrahim1043/what-is-a-dex-and-how-does-it-work-187a4279f626?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/187a4279f626</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 09:31:13 GMT</pubDate>
            <atom:updated>2026-09-27T09:31:13.259Z</atom:updated>
            <content:encoded><![CDATA[<p>If you have ever connected a crypto wallet, selected one token, selected another, and clicked Swap, you have probably interacted with a decentralized exchange — or DEX.</p><p>But what actually happens after you press that button?</p><p>Where does the other token come from?</p><p>Who controls the funds?</p><p>What is a liquidity pool?</p><p>And how is a DEX different from a traditional exchange with a buy and sell order book?</p><p>The easiest way to understand a DEX is to start with the underlying idea rather than with any particular platform.</p><p>A DEX is a blockchain-based exchange system that allows users to trade digital assets through on-chain mechanisms such as smart contracts, without depositing their funds into a traditional centralized exchange account.</p><p>There are different DEX architectures, but two important models are Automated Market Makers (AMMs) and order-book exchanges. AMMs use liquidity pools and mathematical pricing mechanisms, while order-book systems match buy and sell orders.</p><p>As a practical example, we can then look at STON.fi⁠, an AMM-based DEX on the TON blockchain.</p><h3>The basic idea behind a DEX</h3><p>Imagine you want to exchange TON for USDT.</p><p>On a centralized exchange, you would normally:</p><ol><li>Create an account.</li><li>Deposit your assets.</li><li>Place a buy or sell order.</li><li>The exchange matches the order.</li><li>Your account balance is updated.</li></ol><p>A DEX changes the structure.</p><p>Instead, the basic flow can look like:</p><p>Your wallet → DEX smart contracts → liquidity → swapped asset → your wallet</p><p>You don’t necessarily create an exchange account or deposit your assets into an exchange-controlled balance.</p><p>Your wallet remains the starting point for the transaction, and you authorize the blockchain transaction needed to perform the swap.</p><p>That is one of the central ideas behind decentralized trading.</p><h3>What does “decentralized” actually mean?</h3><p>The word decentralized can sound more complicated than it is.</p><p>In the context of a DEX, it generally refers to using blockchain infrastructure and smart contracts to execute trading operations rather than relying on a centralized exchange to hold users’ assets and manually operate the trading process.</p><p>But “decentralized” does not mean there is no website or user interface.</p><p>You can still have a normal-looking website where you:</p><ul><li>connect your wallet;</li><li>choose tokens;</li><li>enter an amount;</li><li>review a quote;</li><li>click Swap.</li></ul><p>The important distinction is what happens underneath that interface.</p><p>The website helps you construct the transaction.</p><p>The blockchain and smart contracts handle the on-chain execution.</p><h3>Self-custody: your wallet remains important</h3><p>One of the biggest differences between many DEXs and centralized exchanges is self-custody.</p><p>With a self-custodial wallet, you control the wallet’s private keys or recovery mechanism.</p><p>The DEX does not simply take your tokens into a centralized account and give you an internal database balance.</p><p>Instead, you connect your wallet and authorize transactions.</p><p>This creates an important distinction:</p><p>Connecting your wallet is not the same thing as depositing your funds into the DEX.</p><p>The wallet is still the place from which you authorize blockchain transactions.</p><p>STON.fi’s current documentation describes its DEX as non-custodial and says users maintain control of their funds.</p><p>That does not mean the process has no risk. You still have to approve transactions, pay blockchain fees, choose the correct tokens and understand the smart contracts you are interacting with.</p><h3>So what does the smart contract do?</h3><p>A smart contract is code deployed on a blockchain that can respond to transactions according to its programmed rules.</p><p>For a DEX, smart contracts can handle things such as:</p><ul><li>receiving tokens;</li><li>determining the swap according to the DEX’s pricing mechanism;</li><li>transferring the output asset;</li><li>maintaining liquidity-pool balances;</li><li>calculating applicable fees;</li><li>recording the resulting state on-chain.</li></ul><p>The user does not need an employee at an exchange to manually approve each trade.</p><p>The transaction interacts with the relevant smart contracts.</p><p>This is why a DEX can operate continuously as blockchain infrastructure rather than as a traditional trading desk.</p><h3>Where does the token you receive come from?</h3><p>This is where liquidity becomes important.</p><p>Suppose a DEX has a TON/USDT liquidity pool.</p><p>The pool contains both assets.</p><p>For example, conceptually:</p><p>TON + USDT</p><p>A trader who wants to swap TON for USDT sends TON into the pool’s trading mechanism and receives USDT from the available liquidity, subject to the pool’s pricing rules and fees.</p><p>The pool’s balances change as a result.</p><p>You can therefore think of a liquidity pool as a shared reserve that allows users to trade without requiring a specific person to be waiting on the other side of every transaction.</p><p>STON.fi’s current documentation describes its DEX as using liquidity pools for token-to-token swaps, with liquidity providers depositing assets and receiving LP tokens representing their pool share.</p><h3>What is an AMM?</h3><p>AMM stands for Automated Market Maker.</p><p>Instead of maintaining a traditional list of buyers and sellers, an AMM uses liquidity pools and an algorithm to determine how much of one asset a trader receives for another.</p><p>This changes the trading experience.</p><p>With an order book, you might say:</p><p>“I want to buy 100 tokens at this price.”</p><p>With an AMM, you are effectively saying:</p><p>“I want to swap this amount of Token A for Token B using the available pool liquidity.”</p><p>The AMM calculates the resulting exchange according to its pricing mechanism.</p><p>STON.fi’s current DEX documentation identifies it as an AMM protocol on TON and documents constant-product pools alongside other pool types supported by its newer architecture.</p><h3>The liquidity pool is the engine behind an AMM</h3><p>Consider a simplified pool containing:</p><p>100 TON + 20,000 USDT</p><p>The pool has a relationship between the quantities of its two assets.</p><p>When someone buys TON using USDT, the pool receives USDT and releases TON.</p><p>After the transaction, the pool might contain something conceptually like:</p><p>101 TON + 19,800 USDT</p><p>The exact numbers depend on the amount traded, fees and the particular AMM design.</p><p>The important idea is that the pool’s balance changes when trades happen.</p><p>That changing balance affects the price available to the next trader.</p><h3>Why does a larger trade usually move the price more?</h3><p>This is known as price impact.</p><p>Imagine a small pool containing relatively little liquidity.</p><p>A small trade may barely change its balance.</p><p>A very large trade, however, can consume a substantial portion of the available liquidity.</p><p>The AMM therefore gives progressively different execution prices as the pool’s balance changes.</p><p>This is one reason liquidity matters so much on DEXs.</p><p>STON.fi’s educational material explains that larger trades relative to the size of a liquidity pool can produce greater price impact.</p><p>So when using an AMM, the displayed token price isn’t necessarily the exact price every unit of a large transaction receives.</p><h3>What does the mathematical formula do?</h3><p>A common AMM model is the constant-product formula:</p><p>x × y = k</p><p>Here:</p><ul><li>x represents the quantity of one asset;</li><li>y represents the quantity of the other;</li><li>k represents the constant relationship maintained by the pricing mechanism.</li></ul><p>You don’t need to calculate this manually to use an AMM.</p><p>The smart contracts and supporting infrastructure perform the calculations.</p><p>STON.fi’s current documentation identifies the Constant Product Market Maker model as one of its DEX pool types.</p><p>The important beginner-level takeaway is:</p><p>The pool’s asset balances and mathematical pricing mechanism determine the swap rather than a traditional list of individual buy and sell orders.</p><h3>Who puts the tokens into the pool?</h3><p>This is where liquidity providers, often called LPs, come in.</p><p>Liquidity providers deposit assets into a liquidity pool.</p><p>For example, someone could provide liquidity to a:</p><p>TON/USDT pool</p><p>The assets they provide become available for traders to use.</p><p>In return, liquidity providers can receive a share of applicable trading fees, according to the pool’s rules.</p><p>STON.fi’s documentation says liquidity providers receive LP tokens representing their share of a pool.</p><p>This creates an important relationship:</p><p>Liquidity providers → supply liquidity</p><p>Traders → use liquidity</p><p>Pool → facilitates swaps</p><p>Fees → can be distributed according to the protocol/pool rules</p><p>Providing liquidity is not risk-free. Changes in the relative prices of pooled assets can create impermanent-loss effects, among other risks.</p><h3>AMM vs order book: two different ways to organize trading</h3><p>Not every DEX uses an AMM.</p><p>Another model is the order book.</p><p>The concept will be familiar to anyone who has used a traditional trading platform.</p><p>An order book contains:</p><p>Buy orders</p><p>and</p><p>Sell orders</p><p>A trader can specify the amount and price they are willing to trade at.</p><p>When compatible orders meet, the trade can execute.</p><p>Simplified example</p><p>A buyer submits:</p><p>Buy 100 TOKEN at $2.</p><p>A seller submits:</p><p>Sell 100 TOKEN at $2.</p><p>The orders match.</p><p>The transaction can then be executed according to the exchange’s architecture.</p><p>STON.fi’s educational material distinguishes order-book DEXs from AMM DEXs in this way: order-book systems rely on buy/sell orders being matched, while AMMs use liquidity pools and mathematical pricing.</p><h3>Why an AMM feels different from an order book</h3><p>The user interface can make the difference easy to understand.</p><p>Order book</p><p>You are looking at:</p><p>Buyers</p><ul><li>$1.98</li><li>$1.99</li><li>$2.00</li></ul><p>Sellers</p><ul><li>$2.01</li><li>$2.02</li><li>$2.03</li></ul><p>You choose an order.</p><p>AMM</p><p>You are more likely to see:</p><p>You pay:</p><p>10 TON</p><p>You receive:</p><p>approximately X USDT</p><p>Rate:</p><p>X</p><p>Price impact:</p><p>X%</p><p>Minimum received:</p><p>X USDT</p><p>The system calculates the swap against available liquidity.</p><p>Neither model should automatically be treated as universally better. They represent different ways of organizing liquidity and trade execution.</p><h3>Now let’s follow one DEX swap from beginning to end</h3><p>Suppose you have TON in your wallet and want USDT.</p><p>Here’s the simplified journey.</p><p>Step 1: Your wallet contains TON</p><p>Your TON is controlled by your wallet.</p><p>You have not deposited it into a centralized exchange account.</p><p>Step 2: You connect your wallet to the DEX</p><p>The DEX interface connects to your wallet.</p><p>You select the assets you want to exchange.</p><p>Step 3: You enter the amount</p><p>For example:</p><p>10 TON → USDT</p><p>The DEX can use information about the available liquidity to calculate an estimated output.</p><p>Step 4: You review the transaction</p><p>Depending on the interface and swap, you may see information such as:</p><ul><li>expected output;</li><li>swap rate;</li><li>price impact;</li><li>minimum received;</li><li>blockchain fee;</li><li>route.</li></ul><p>STON.fi’s current documentation and API provide swap simulation and quote-related information before execution.</p><p>Step 5: You authorize the transaction</p><p>You confirm the transaction through your wallet.</p><p>This is an important moment.</p><p>You are authorizing the blockchain transaction rather than simply clicking a button that changes a centralized database balance.</p><p>Step 6: The blockchain processes the transaction</p><p>The transaction reaches the relevant smart-contract system.</p><p>Step 7: The DEX executes the swap</p><p>The smart contracts process the swap against the relevant liquidity.</p><p>Step 8: You receive the output asset</p><p>After successful execution, the resulting token is delivered according to the transaction’s instructions.</p><h3>The basic flow is therefore:</h3><p>Your wallet</p><p>. ↓</p><p>Connect</p><p>. ↓</p><p>Choose Token A → Token B</p><p>. ↓</p><p>Enter amount</p><p>. ↓</p><p>Receive quote</p><p>. ↓</p><p>Review price impact / fees / minimum received</p><p>. ↓</p><p>Sign transaction</p><p>. ↓</p><p>Blockchain</p><p>. ↓</p><p>DEX smart contracts</p><p>. ↓</p><p>Liquidity pool</p><p>. ↓</p><p>Token B</p><p>. ↓</p><p>Your wallet</p><h3>STON.fi as a practical TON example</h3><p>Now that the general DEX model is clear, we can look at STON.fi’s DEX documentation⁠ as a concrete example.</p><p>STON.fi is a decentralized exchange protocol on The Open Network (TON).</p><p>Its current developer documentation describes the DEX as an AMM protocol supporting permissionless swaps and liquidity provision. Its current architecture includes multiple contract types and supports different pool designs in its newer version.</p><p>This makes STON.fi useful for seeing how the concepts above translate into an actual blockchain implementation.</p><h3>What happens inside STON.fi?</h3><p>At a simplified level, STON.fi’s architecture contains several important components.</p><p>Router</p><p>The Router acts as an entry point for DEX operations.</p><p>STON.fi’s documentation explains that the Router receives relevant token-transfer messages and routes swap operations to the appropriate pool.</p><p>Pool</p><p>The Pool contains the AMM data for a particular trading pair and handles swap and liquidity operations.</p><p>For example, a pool can represent a particular pair of assets.</p><p>The current STON.fi documentation says pool contracts maintain information including token reserves and pool-fee information.</p><p>Account and wallet contracts</p><p>STON.fi’s broader DEX architecture also includes contracts associated with liquidity-provider positions and LP-token operations.</p><p>You don’t normally need to understand these contracts individually to perform a swap.</p><p>But they demonstrate something important:</p><p>The simple “Swap” button on the screen can represent a much more complex on-chain process underneath.</p><h3>The STON.fi swap, simplified</h3><p>Imagine:</p><p>TON → USDT</p><p>The user sees something simple:</p><p>FROM</p><p>10 TON</p><p>. ↓</p><p>TO</p><p>≈ X USDT</p><p>[ Swap ]</p><p>Behind that interface, the transaction interacts with the DEX’s smart-contract architecture.</p><p>A simplified representation is:</p><p>TON wallet</p><p>. ↓</p><p>Token transfer / transaction</p><p>. ↓</p><p>STON.fi Router</p><p>. ↓</p><p>TON/USDT Pool</p><p>. ↓</p><p>AMM calculation</p><p>. ↓</p><p>USDT output</p><p>. ↓</p><p>User wallet</p><p>The exact transaction structure depends on the DEX version, pool type and assets involved, but the important conceptual flow is the same: the wallet authorizes an on-chain transaction, and the DEX’s smart contracts process the swap against available liquidity.</p><h3>Why the wallet-to-swap model matters</h3><p>This architecture changes the user’s relationship with the exchange.</p><p>On a custodial exchange, you generally see:</p><p>Your exchange account → exchange database → trading engine → exchange account</p><p>With a self-custodial DEX, the conceptual flow is closer to:</p><p>Your wallet → blockchain transaction → smart contracts → your wallet</p><p>That doesn’t mean a DEX eliminates every intermediary or every risk.</p><p>It means the trade execution mechanism is moved onto blockchain infrastructure and smart contracts rather than depending entirely on a centralized exchange’s internal account system.</p><h3>What a DEX does not automatically solve</h3><p>It is easy to hear “decentralized” and assume that everything is automatically safer.</p><p>That would be a mistake.</p><p>DEX users still need to think about:</p><p>Smart-contract risk</p><p>The software executing the transaction can contain vulnerabilities or unexpected behavior.</p><p>Token risk</p><p>A DEX can provide infrastructure for trading tokens that users still need to research.</p><p>Liquidity risk</p><p>Thin liquidity can lead to substantial price impact.</p><p>Slippage</p><p>The final execution can differ from the initial quote when market conditions change.</p><p>Network fees</p><p>The blockchain still charges fees for processing transactions.</p><p>User error</p><p>Sending the wrong token, using the wrong network, approving a malicious transaction or interacting with a fake token can still cause losses.</p><p>Decentralization changes how the exchange operates. It does not eliminate the need for users to understand what they are signing.</p><h3>Why liquidity is so important</h3><p>A DEX can have excellent smart contracts and still provide poor execution if there isn’t enough useful liquidity.</p><p>Imagine two pools.</p><p>Pool A</p><p>$100,000 liquidity</p><p>Pool B</p><p>$10 million liquidity</p><p>A $50,000 trade represents a much larger portion of Pool A than Pool B.</p><p>The larger trade relative to available liquidity can therefore cause substantially more price impact in the smaller pool.</p><p>This is why DEX users should look beyond the token’s headline price.</p><p>Before confirming a swap, it can be useful to look at:</p><p>Expected output</p><p>Price impact</p><p>Minimum received</p><p>Fees</p><p>Liquidity</p><p>These values describe different parts of the execution.</p><h3>The DEX is more than a “Swap” button</h3><p>From the user’s perspective, a DEX may look extremely simple.</p><p>You select:</p><p>TON</p><p>↓</p><p>USDT</p><p>↓</p><p>Swap</p><p>But underneath that action can be a combination of:</p><ul><li>wallet authorization;</li><li>token transfers;</li><li>smart contracts;</li><li>liquidity pools;</li><li>pricing formulas;</li><li>fees;</li><li>blockchain consensus;</li><li>transaction execution.</li></ul><p>The interface hides much of this complexity.</p><p>That is actually one of the major challenges in DeFi UX:</p><p>Making complicated blockchain infrastructure understandable without pretending the complexity does not exist.</p><h3>A simple mental model</h3><p>If you want one way to remember everything in this article, use this:</p><p>Wallet</p><p>Controls your assets and signs transactions.</p><p>Smart contract</p><p>Executes predefined on-chain logic.</p><p>Liquidity pool</p><p>Provides assets that traders can exchange against.</p><p>AMM</p><p>Uses an algorithm to determine swap pricing from pool conditions.</p><p>Order book</p><p>Matches buyers and sellers through orders.</p><p>DEX</p><p>Provides the decentralized trading mechanism that connects these pieces.</p><p>STON.fi</p><h3>A practical AMM-based DEX example on TON.</h3><p>From the user’s perspective, it can be this simple</p><p>You have:</p><p>TON</p><p>You want:</p><p>USDT</p><p>You open a DEX.</p><p>You connect your wallet.</p><p>You select:</p><p>TON → USDT</p><p>You enter the amount.</p><p>The DEX calculates an estimated result using available liquidity.</p><p>You review the quote, price impact, minimum received and applicable fees.</p><p>You authorize the transaction.</p><p>The blockchain processes it.</p><p>The smart contracts execute the swap.</p><p>You receive:</p><p>USDT</p><p>in your wallet.</p><p>That simple experience is powered by a combination of self-custody, smart contracts, liquidity and automated market-making.</p><h3>Final thought</h3><p>A decentralized exchange is not simply a website where you press Swap.</p><p>It is a different way of organizing digital-asset trading.</p><p>Instead of relying entirely on a centralized exchange to hold funds and maintain an internal trading system, a DEX can use blockchain transactions, smart contracts and on-chain liquidity mechanisms to execute trades.</p><p>AMM-based DEXs replace the traditional order-matching model with liquidity pools and mathematical pricing.</p><p>Order-book DEXs retain the concept of bids, asks and matching orders.</p><p>And the user’s wallet becomes an important part of the process because the user can authorize transactions directly rather than first depositing assets into a centralized exchange account.</p><p>STON.fi provides a useful real-world example on TON: its DEX uses AMM liquidity pools, smart-contract infrastructure and a Router/Pool architecture to facilitate token swaps.</p><p>So the next time you see:</p><p>Connect Wallet → Select Tokens → Swap</p><p>remember that there is an entire on-chain system working behind that simple interface.</p><p>The button is simple.</p><p>The infrastructure underneath it is the DEX.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*jL-PCzyfvqwn5P_Iq_It9g@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=187a4279f626" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is an Automated Market Maker (AMM)?]]></title>
            <link>https://medium.com/@nuraibrahim1043/what-is-an-automated-market-maker-amm-27d0b517b097?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/27d0b517b097</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Sun, 27 Sep 2026 05:05:48 GMT</pubDate>
            <atom:updated>2026-09-27T05:05:48.181Z</atom:updated>
            <content:encoded><![CDATA[<p>If you have ever swapped one crypto token for another on a decentralized exchange, you may have wondered:</p><p>Who is actually on the other side of the trade?</p><p>On a traditional exchange, the answer is often another trader. Buyers place bids, sellers place asks, and an order-matching system connects them.</p><p>An Automated Market Maker (AMM) works differently.</p><p>Instead of waiting for a buyer and seller to match, an AMM uses liquidity pools, smart contracts, and mathematical pricing rules to make swaps possible.</p><p>STON.fi provides a practical example on TON: its DEX uses an AMM model where users swap against liquidity pools rather than a traditional order book.</p><p>But before looking at STON.fi, it helps to understand the AMM itself.</p><h3>The basic idea: liquidity replaces the order book</h3><p>A traditional order-book exchange maintains a list of buy and sell orders.</p><p>For example:</p><p>Buyers	Sellers</p><p>Buy 100 USDT at $1.00	Sell 100 USDT at $1.01</p><p>Buy 200 USDT at $0.99	Sell 300 USDT at $1.02</p><p>A trade happens when compatible orders can be matched.</p><p>An AMM doesn’t need this matching process.</p><p>Instead, it has a liquidity pool containing tokens. A trader interacts with the pool through a smart contract, and the AMM’s pricing mechanism determines how much of the other token the trader receives.</p><p>STON.fi’s own documentation describes its AMM as using liquidity pools and a pricing formula rather than an order book.</p><p>This creates an important difference:</p><p>Order book:</p><p>Buyer ↔ Seller</p><p>AMM:</p><p>Trader ↔ Liquidity Pool</p><p>The pool can therefore provide liquidity without requiring a specific person to be waiting to take the other side of your trade.</p><h3>What is inside an AMM liquidity pool?</h3><p>Think of a simple TON/USDT pool.</p><p>The pool contains two reserves:</p><ul><li>TON</li><li>USDT</li></ul><p>For illustration, imagine a pool containing:</p><p>1,000 TON + 6,800 USDT</p><p>The ratio gives the pool an approximate starting price of:</p><p>1 TON ≈ 6.8 USDT</p><p>These numbers are only an example. Real pool balances and prices continuously change.</p><p>The important concept is that the quantities of the tokens inside the pool influence the exchange rate.</p><p>STON.fi describes a liquidity pool as a smart-contract vault containing a pair of tokens, with its price determined algorithmically from the assets held inside it.</p><h3>The mathematical engine behind a simple AMM</h3><p>One of the best-known AMM models uses the constant-product formula:</p><p>x × y = k</p><p>Where:</p><ul><li>x = quantity of token A in the pool</li><li>y = quantity of token B</li><li>k = the pool’s constant-product relationship</li></ul><p>STON.fi’s documentation identifies constant-product pools as part of its AMM design.</p><p>You don’t need to calculate this manually when using an AMM.</p><p>The smart contracts and interface handle the mathematics.</p><p>But understanding the idea explains something important:</p><p>When someone trades against the pool, the pool’s reserves change, and that changes the price for subsequent trades.</p><h3>What happens when someone swaps?</h3><p>Let’s make the example simple.</p><p>Imagine our pool starts with:</p><p>1,000 TON</p><p>6,800 USDT</p><p>Now a trader wants to swap 100 TON for USDT.</p><p>The trader sends TON into the pool.</p><p>The pool now has more TON than before.</p><p>At the same time, USDT leaves the pool and goes to the trader.</p><p>So the reserves move roughly like this:</p><p>Before</p><p>1,000 TON</p><p>6,800 USDT</p><p>⬇️</p><p>Trader adds TON</p><p>100 TON enters</p><p>⬇️</p><p>Trader receives USDT</p><p>USDT leaves the pool</p><p>⬇️</p><p>After</p><p>More TON</p><p>Less USDT</p><p>The ratio has changed.</p><p>That means the price available to the next trader also changes.</p><p>This is one reason large trades relative to pool liquidity can have significant price impact. STON.fi’s Help Center specifically explains that larger swaps in smaller pools tend to produce greater price impact.</p><h3>Why doesn’t the trader simply receive the headline price?</h3><p>This is where AMM mechanics become important.</p><p>Suppose a pool appears to imply:</p><p>1 TON = 6.8 USDT</p><p>That doesn’t necessarily mean you can swap a very large amount of TON and receive exactly 6.8 USDT for every TON.</p><p>Why?</p><p>Because your own transaction changes the pool.</p><p>The more liquidity your trade consumes relative to the pool, the more the reserve ratio moves during execution.</p><p>This creates price impact.</p><p>For example:</p><p>A small trade might barely change the pool.</p><p>A very large trade can move the pool considerably.</p><p>STON.fi therefore shows users information such as expected output, swap rate, price impact, minimum received, and blockchain fee before confirmation.</p><h3>Where does the liquidity come from?</h3><p>This is where liquidity providers, or LPs, enter the picture.</p><p>An AMM needs tokens inside its pools so traders can use them.</p><p>Liquidity providers supply those tokens.</p><p>For a standard two-token position, an LP might provide:</p><p>TON + USDT</p><p>to a TON/USDT pool.</p><p>Those assets become available for other users to trade against.</p><p>In return, the liquidity provider receives a representation of their share of the pool, commonly called LP tokens.</p><p>So the system has two important participants:</p><p>Traders</p><p>They use the pool to exchange tokens.</p><p>Liquidity providers</p><p>They supply the assets that make those exchanges possible.</p><p>This creates a simple relationship:</p><p>LPs provide liquidity → traders use liquidity → swaps generate fees → LPs receive a share of fees</p><h3>How do liquidity providers earn fees?</h3><p>AMM swaps generally charge a trading fee.</p><p>That fee is separate from the blockchain’s network fee.</p><p>For example, a user swapping through a pool may pay:</p><p>AMM/pool fee</p><p>and also:</p><p>TON blockchain fee</p><p>These are different costs.</p><p>STON.fi’s current Help Center says swap fees vary by pool and that liquidity providers receive a portion of swap fees generated by trades through their pool. It currently describes 0.2% as a typical LP fee, while noting that the exact fee depends on the pool.</p><p>The fee mechanism gives liquidity providers an economic reason to make their assets available to traders.</p><p>For example, imagine:</p><ul><li>Pool trading volume = 1,000,000 USDT</li><li>Applicable LP fee = 0.2%</li><li>LP owns 5% of the pool</li></ul><p>The simplified fee calculation would be:</p><p>1,000,000 × 0.002 × 0.05 = 100 USDT</p><p>That’s an illustration, not a prediction of actual returns.</p><p>Actual results depend on trading volume, pool fees, liquidity share, token prices, and other factors.</p><h3>The STON.fi pool example</h3><p>Now we can put the pieces together.</p><p>Imagine a TON/USDT pool on STON.fi.</p><p>The simplified architecture looks like this:</p><p>Liquidity providers</p><p>↓</p><p>TON + USDT</p><p>↓</p><p>STON.fi liquidity pool</p><p>↓</p><p>Smart-contract pricing mechanism</p><p>↓</p><p>Trader swaps TON → USDT</p><p>The trader doesn’t need to find a specific person selling USDT.</p><p>The pool already contains USDT.</p><p>The AMM calculates the swap according to the pool’s pricing mechanism, adjusts the reserves, and sends the resulting USDT to the trader.</p><p>STON.fi describes its DEX as a non-custodial AMM on TON, where users connect their wallets and swaps are executed through smart contracts rather than through a central party holding user funds.</p><h3>What actually happens when you swap on STON.fi?</h3><p>From the user’s perspective, the process is relatively simple.</p><ol><li>Connect your wallet</li></ol><p>You connect a compatible TON wallet.</p><p>2. Select your tokens</p><p>For example:</p><p>From: TON</p><p>To: USDT</p><p>3. Enter the amount</p><p>The interface calculates the expected output.</p><p>4. Review the trade</p><p>STON.fi displays information such as:</p><ul><li>expected output</li><li>swap rate</li><li>price impact</li><li>minimum received</li><li>blockchain fee</li></ul><p>5. Confirm the transaction</p><p>You approve the transaction in your wallet.</p><p>6. Smart contracts execute the swap</p><p>The pool’s reserves change and the output token is sent to your wallet.</p><p>STON.fi’s current Help Center describes this wallet → token selection → quote review → wallet approval flow.</p><p>The important point is that you don’t deposit your assets into a centralized exchange account first.</p><p>The transaction is executed on-chain through the relevant smart contracts.</p><h3>AMMs don’t mean every pool works exactly the same way</h3><p>The constant-product model is one important AMM design, but it isn’t the only possible model.</p><p>STON.fi’s current documentation says its ecosystem includes different pool types, including constant-product pools and stable-oriented pool designs.</p><p>This matters because different assets have different trading characteristics.</p><p>A volatile pair such as:</p><p>TON / USDT</p><p>behaves differently from a pair where the assets are designed to remain close in value, such as:</p><p>USDT / USDC</p><p>A stable-oriented AMM can therefore use a different pricing curve designed for that type of market.</p><p>The underlying principle remains the same:</p><p>Liquidity + algorithm + smart contracts → automated trading</p><h3>One pool is not the whole liquidity picture</h3><p>This is where Omniston becomes relevant.</p><p>An AMM pool is a specific source of liquidity.</p><p>But imagine that several liquidity sources exist across TON.</p><p>Instead of relying on only one pool, an aggregation layer can examine multiple sources and determine which available route can provide the requested swap.</p><p>That’s the role Omniston is designed to play.</p><p>STON.fi’s current documentation describes Omniston as a TON liquidity aggregation protocol that can aggregate liquidity from multiple sources, including AMM DEXs and on-chain RFQ resolvers.</p><p>Its documentation also describes a routing process in which multiple liquidity sources are queried and routes are selected based on the available quotes.</p><p>So the distinction is important:</p><p>STON.fi AMM pool</p><p>Provides liquidity through a specific pool and its pricing mechanism.</p><p>Omniston</p><p>Can look across multiple liquidity sources and routes rather than treating one pool as the only possible source.</p><p>STON.fi’s current developer documentation specifically references liquidity sources including STON.fi DEX, other TON DEXs, and RFQ resolvers.</p><p>In simple terms:</p><p>One AMM pool</p><p>“Here is the liquidity available inside this pool.”</p><p>Aggregation layer</p><p>“Let’s examine the available liquidity sources and routes before executing the trade.”</p><p>That distinction becomes increasingly important as a blockchain ecosystem develops more DEXs, pools, and liquidity providers.</p><h3>What an AMM actually automates</h3><p>The word “automated” can be misleading if we don’t explain what is being automated.</p><p>An AMM isn’t a robot trader deciding what token will become valuable.</p><p>Instead, automation refers primarily to the market-making process.</p><p>The protocol can automatically:</p><ul><li>calculate swap prices</li><li>determine the output amount</li><li>adjust the pool’s reserves</li><li>execute token transfers</li><li>collect swap fees</li><li>distribute the economic benefits of those fees to liquidity providers according to the pool’s rules</li></ul><p>Smart contracts perform these operations according to their programmed logic.</p><p>That is why an AMM can operate continuously without a traditional trading desk matching individual buyers and sellers.</p><h3>What are the risks?</h3><p>AMMs solve one problem — how to provide continuous liquidity and execute trades without a traditional order book.</p><p>They don’t eliminate every risk.</p><p>Price impact</p><p>Large trades can move the pool price significantly, particularly when liquidity is limited.</p><p>Slippage</p><p>The market can change between the time you review a transaction and when it is executed.</p><p>Impermanent loss</p><p>Liquidity providers can end up with a different asset composition and potentially lower value than if they had simply held the assets, depending on how the relative prices move.</p><p>Smart-contract risk</p><p>AMMs depend on smart contracts. Bugs or vulnerabilities can create risks.</p><p>Token risk</p><p>A pool can contain tokens with unusual mechanics, including transfer taxes or other restrictions.</p><p>Liquidity risk</p><p>A pool with limited liquidity may provide poor execution for larger trades.</p><p>So AMM does not mean risk-free.</p><p>It means the market-making mechanism is automated through programmed rules and liquidity pools.</p><h3>The easiest way to remember an AMM</h3><p>Think of an AMM as a self-operating token exchange powered by liquidity pools.</p><p>Instead of:</p><p>Buyer → Order Book ← Seller</p><p>you have:</p><p>Liquidity Providers → Pool ← Trader</p><p>The pool contains assets.</p><p>The AMM’s pricing mechanism determines the exchange rate.</p><p>The trader changes the pool’s reserves by swapping.</p><p>The new reserves influence subsequent prices.</p><p>Liquidity providers earn a share of applicable trading fees for making their assets available.</p><p>And an aggregation layer such as Omniston can go one step further by examining multiple liquidity sources rather than relying on a single pool.</p><h3>Final thought</h3><p>The most important idea behind an Automated Market Maker isn’t the formula itself.</p><p>It’s the change in how liquidity is organized.</p><p>Traditional markets can depend on matching individual buyers and sellers through an order book.</p><p>AMMs move that responsibility into liquidity pools and smart contracts.</p><p>STON.fi provides a practical example on TON: users can swap through AMM liquidity pools while liquidity providers supply the assets that make those swaps possible.</p><p>And once multiple liquidity sources exist, aggregation becomes another layer of the system. Omniston is designed to query and route across multiple TON liquidity sources rather than treating a single AMM pool as the entire market.</p><p>AMM = liquidity pools + algorithmic pricing + smart-contract execution.</p><p>Omniston = an aggregation layer that can connect multiple liquidity sources and routes.</p><p>Understanding those two layers makes it much easier to understand how modern DeFi trading infrastructure works.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=27d0b517b097" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does “Unknown Asset” Mean on STON.fi?]]></title>
            <link>https://medium.com/@nuraibrahim1043/what-does-unknown-asset-mean-on-ston-fi-d73bf4648389?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d73bf4648389</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 11:13:50 GMT</pubDate>
            <atom:updated>2026-09-26T11:13:50.937Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are using STON.fi and encounter a token displayed with the label:</p><h3>Unknown Asset</h3><p>the first thing to understand is that the label itself should not be treated as a safety verdict.</p><p>At the time of reviewing STON.fi’s publicly available Help Center and Blog documentation, the exact meaning and trigger conditions for the “Unknown Asset” label are not clearly defined in the public documentation reviewed.</p><h3>That distinction matters.</h3><p>Rather than guessing what the label means, users should treat it as a reason to pause and verify the asset independently.</p><p>What does the interface actually show?</p><p>The interface state in question is straightforward:</p><p>Token → “Unknown Asset”</p><p>That is the information a user can see.</p><p>What is not established by the publicly available documentation reviewed is exactly what STON.fi’s backend uses to assign this particular label, what conditions cause it to appear, or whether it corresponds to a specific internal asset-resolution process.</p><p>STON.fi’s documented token-warning system currently describes labels such as Fake, Honeypot, Taxable, Suspicious, and DMCA Notice. These labels have documented meanings and specific interface behavior. “Unknown Asset” is not given the same canonical public definition in the sources reviewed.</p><p>Therefore, it would be inaccurate to tell users that “Unknown Asset” definitely means a scam, an unverified token, a newly created token, or a token with insufficient liquidity.</p><p>Those interpretations require confirmation from STON.fi.</p><p>Unknown identity is not the same as unsafe</p><p>There is an important distinction between not having enough information about an asset and having evidence that an asset is dangerous.</p><p>For example, STON.fi explicitly documents certain risk categories.</p><p>A Fake token is one that imitates a known asset, project, or brand.</p><p>A Honeypot can generally be bought but cannot normally be sold.</p><p>A Taxable token has additional transfer or swap-fee mechanics.</p><p>A Suspicious token raises concerns requiring additional attention.</p><p>These labels communicate specific characteristics identified by STON.fi’s monitoring and review processes.</p><p>“Unknown Asset,” however, should not automatically be interpreted as belonging to any of those categories.</p><p>Likewise, it should not be interpreted in the opposite direction as:</p><p>“STON.fi has checked this token and confirmed that it is safe.”</p><p>There is no basis in the reviewed public documentation for making that claim.</p><h3>What can you verify yourself?</h3><p>Until STON.fi publishes or confirms the exact meaning of the label, users can perform several independent checks.</p><ol><li>Verify the contract address</li></ol><p>The contract address is one of the most important pieces of information when identifying a token.</p><p>A token’s name, ticker, and logo can be copied.</p><p>The contract address provides a much more precise way to identify the asset you are interacting with.</p><p>STON.fi’s Help Center specifically warns that scam tokens can copy popular names and recommends using the correct official contract address when importing a custom token. It also states that STON.fi cannot verify whether a custom token is trustworthy.</p><p>So:</p><p>Find the token’s official contract address → compare it with the address shown by the asset you’re considering.</p><p>If the addresses do not match, stop and investigate.</p><p>2. Check the project’s official sources</p><p>Do not rely only on the token’s name or logo.</p><p>Look for the project’s official website and official communication channels, then compare the contract address published there with the asset you’re viewing.</p><p>This is especially important when dealing with popular names or newly launched tokens.</p><p>STON.fi itself recommends checking official sources and doing your own research before interacting with custom tokens.</p><p>3. Check the liquidity</p><p>Even if the contract address is correct, you still need to understand the market you are entering.</p><p>STON.fi explains that liquidity pools contain the assets available for swaps, and anyone can provide liquidity or create a pool.</p><p>A token having a pool does not automatically tell you that the project is legitimate.</p><p>It also does not mean there is enough liquidity for your intended trade.</p><p>STON.fi’s pool guidance notes that small liquidity can result in significant price impact when users make swaps.</p><p>So check:</p><ul><li>How much liquidity is in the pool?</li><li>How large is your trade compared with that liquidity?</li><li>What price impact does STON.fi display?</li><li>Does the expected output make sense?</li></ul><p>Liquidity is a market-condition check, not a token-verification check.</p><p>4. Understand what the label does not tell you</p><p>If you see Unknown Asset, do not use that label alone to answer questions such as:</p><p>“Is this token legitimate?”</p><p>“Is this token a scam?”</p><p>“Is this the official token?”</p><p>“Will I be able to sell it?”</p><p>“Is this a good investment?”</p><p>The public documentation reviewed does not establish that the Unknown Asset label answers any of these questions.</p><p>Those questions require additional evidence.</p><p>For example, the contract address can help establish whether you have the asset published by the project.</p><p>Liquidity and price impact can help you understand the trading environment.</p><p>Project sources can help you establish whether the asset is actually associated with the project you intended to interact with.</p><p>These checks complement each other.</p><h3>What STON.fi does document about token warnings</h3><p>STON.fi has a documented interface-level labeling system for certain non-standard or potentially risky tokens.</p><p>The documented labels include:</p><p>Label	Documented meaning</p><p>Fake	Token imitates a known asset, project, or brand</p><p>Honeypot	Token can generally be bought but cannot normally be sold</p><p>Taxable	Token contract has an additional transfer/swap-fee mechanism</p><p>Suspicious	Token raises concerns requiring additional attention</p><p>DMCA Notice	Token is associated with an intellectual-property complaint</p><p>STON.fi explains that these labels are based on signals such as user complaints, manual monitoring, automatic honeypot alerts, and legal notices.</p><p>This documented system is useful because it shows an important principle:</p><p>A label should communicate a specific piece of information, rather than being interpreted as a universal safety score.</p><p>That same principle is why we should not invent a definition for “Unknown Asset” when the public documentation does not provide one.</p><p>A simple checklist when you see “Unknown Asset”</p><p>Before interacting with the token, ask:</p><p>Contract</p><ul><li>Do I have the correct contract address?</li><li>Does it match the address published by the project’s official source?</li></ul><p>Project</p><ul><li>Can I identify the actual project behind the token?</li><li>Are its official website and communication channels genuine?</li></ul><p>Liquidity</p><ul><li>Is there sufficient liquidity for the trade?</li><li>What price impact does the swap show?</li></ul><p>Token behavior</p><ul><li>Are there unusual taxes or transfer mechanics?</li><li>Can the token’s trading behavior be independently verified?</li></ul><p>Interface</p><ul><li>Is there another documented STON.fi warning or restriction?</li><li>Am I relying on the absence of a warning as if it were verification?</li></ul><p>If you cannot confidently answer these questions, slowing down is better than assuming.</p><p>What we can and cannot say about “Unknown Asset”</p><p>Based on the current public documentation reviewed, we can confidently say that STON.fi has a documented system for identifying certain token characteristics and risks.</p><p>We can also verify that STON.fi allows users to import custom tokens using their smart-contract addresses, while explicitly warning that the platform cannot verify whether a custom token is trustworthy.</p><p>What we cannot currently verify from the reviewed public documentation is the exact technical or operational definition of the “Unknown Asset” label.</p><p>That could represent an asset-resolution or metadata state, but that would be an interpretation unless STON.fi confirms it.</p><p>For support education, that distinction is important.</p><h3>Final takeaway</h3><p>If STON.fi shows “Unknown Asset,” don’t automatically translate it into “scam.”</p><p>But don’t translate it into “safe” either.</p><p>The label’s exact current meaning should be confirmed directly with STON.fi product/support before treating it as a defined safety signal.</p><p>Until then, verify the contract address, check the project’s official sources, examine liquidity and price impact, and understand the asset’s mechanics before interacting with it.</p><p>When the available information is incomplete, the safest assumption is not certainty. It is to pause, verify, and understand what you are interacting with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*aDM916PN5FDg3X6XSYSQEQ@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d73bf4648389" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does No Warning on STON.fi Mean a Token Is Safe?]]></title>
            <link>https://medium.com/@nuraibrahim1043/does-no-warning-on-ston-fi-mean-a-token-is-safe-3707e62d0fb0?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/3707e62d0fb0</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 08:04:10 GMT</pubDate>
            <atom:updated>2026-09-26T08:04:10.321Z</atom:updated>
            <content:encoded><![CDATA[<p>When swapping a token on a DEX, users often look for warning labels as a quick safety signal.</p><p>That is useful, but there is an important distinction that can easily be missed:</p><p>No warning on STON.fi does not mean a token has been verified as safe.</p><p>STON.fi uses interface-level labels and restrictions to give users additional context about certain tokens. These labels can help identify specific risks, but they are not a universal certification system for every token available on the protocol.</p><p>Understanding that difference can help users make better decisions before swapping.</p><h3>What do STON.fi labels actually tell you?</h3><p>STON.fi can apply different interface-level labels to tokens when specific characteristics or risk signals are identified.</p><p>For example:</p><ul><li>Fake: The token imitates a known asset, project, or brand.</li><li>Honeypot: The token can generally be bought but cannot be sold normally.</li><li>Taxable: The token has an additional swap or transfer-fee mechanism.</li><li>Suspicious: The token raises concerns that require additional attention.</li><li>DMCA Notice: The token is associated with an intellectual-property complaint.</li></ul><p>These labels are not all saying the same thing. Each one communicates a particular characteristic or concern that STON.fi has identified.</p><p>Some labels also affect how the token can be accessed through the STON.fi interface. For example, Fake and Honeypot tokens are not available for swapping through the standard STON.fi interface, while some other flagged tokens may remain swappable with the warning visible.</p><p>So a label is best understood as context and risk information, not as a complete security assessment.</p><p>No warning is not verification</p><p>This is the key point:</p><p>A token having no warning on STON.fi does not mean the token is verified, endorsed, or guaranteed to be safe.</p><p>STON.fi itself does not operate a token-verification system. For example, the “Unverified Token” badge found in products such as Tonkeeper or Tonviewer belongs to those third-party services, not to STON.fi.</p><p>STON.fi also operates permissionlessly. There is no formal listing process requiring STON.fi approval before a TON Jetton can be added to the protocol. Anyone can create a Jetton and create a liquidity pool.</p><p>That means users should not interpret the absence of a warning as:</p><h3>“STON.fi checked this token and confirmed that it is safe.”</h3><p>That is not what the interface is communicating.</p><p>Instead, think of it this way:</p><p>A warning can tell you that something specific has been identified. No warning simply means you should continue your own checks.</p><p>What should you check before buying a token?</p><p>A token’s name, logo, price, or lack of a warning should never be your only basis for deciding whether to interact with it.</p><h3>Here are some independent checks worth performing.</h3><ol><li>Verify the contract address</li></ol><p>This is one of the most important checks.</p><p>Scam tokens can copy the name, ticker, and visual identity of legitimate projects. The contract address is what distinguishes one token deployment from another.</p><p>Get the contract address from a project’s official source and compare it carefully with the address shown by the token interface.</p><p>STON.fi specifically recommends using the correct official contract address and warns that scam tokens can copy popular names.</p><p>Do not assume that a familiar ticker means you have found the legitimate asset.</p><p>2. Check the project’s official channels</p><p>Look for the project’s official website and verified social channels.</p><p>Then compare the contract address published there with the address of the token you are about to swap.</p><p>Be particularly careful with links received through random replies, private messages, Telegram groups, or unofficial accounts.</p><p>The goal is to establish that the token you are looking at is actually connected to the project you think it is.</p><p>3. Understand the token’s mechanics</p><p>Some tokens have mechanics that can materially affect your trade.</p><p>For example, taxable tokens can charge additional fees when tokens are transferred or swapped. STON.fi marks supported taxable tokens with a Taxable flag and applies restrictions around their use.</p><h3>Before buying an unfamiliar token, understand:</h3><ul><li>whether it has transfer or trading taxes,</li><li>whether there are unusual restrictions,</li><li>whether buying and selling work normally,</li><li>whether the contract has special permissions or mechanics,</li><li>and whether the amount you receive can differ significantly from the quoted amount.</li></ul><p>4. Look at liquidity</p><p>Liquidity is another important part of the picture.</p><p>A token can exist and be tradable while having very little liquidity.</p><p>That matters because a shallow pool can cause a relatively small trade to move the price significantly. STON.fi’s own pool guidance notes that insufficient liquidity can create high price impact and unstable pricing.</p><p>This is where liquidity checks complement token labels.</p><p>The label answers one question:</p><p>“Has STON.fi identified a specific characteristic or risk signal?”</p><p>The liquidity check answers another:</p><p>“How much liquidity is actually available for this trade, and how much could my transaction move the market?”</p><p>Neither replaces the other.</p><p>5. Check price impact before confirming</p><p>Even when a token has no warning, look at the quote before signing.</p><p>STON.fi shows information such as the expected amount received, price impact, and route before confirmation.</p><p>If a small trade produces unexpectedly high price impact, stop and investigate.</p><p>A high price impact does not automatically prove that a token is malicious. It can simply indicate that the available liquidity is small relative to your trade. But it is still a reason to slow down and understand what is happening.</p><h3>Why contract address and liquidity checks work together</h3><p>Consider two different scenarios.</p><p>Scenario A: Familiar name, wrong contract</p><p>You see a token called “USDT” with the familiar logo.</p><p>There is no warning.</p><p>You check the official issuer’s contract address and discover that the address does not match.</p><p>The absence of a warning does not make the token legitimate.</p><p>The contract-address check catches what the label alone cannot.</p><p>Scenario B: Correct token, very low liquidity</p><p>Now imagine you find the correct contract address for a legitimate project.</p><p>The token has no warning.</p><p>But the pool has very little liquidity, and your intended trade produces significant price impact.</p><p>The token may not be a fake token or a honeypot. The issue here is market liquidity.</p><p>The liquidity and price-impact checks reveal a different risk that a token label is not designed to answer.</p><p>This is why responsible token research requires multiple checks rather than one signal.</p><h3>What labels can and cannot communicate</h3><p>It helps to think of STON.fi labels as one layer of information.</p><p>Labels can:</p><ul><li>highlight specific identified characteristics;</li><li>warn about certain known risk patterns;</li><li>add context before interaction;</li><li>restrict access to some categories of tokens;</li><li>make potentially problematic token behavior more visible.</li></ul><p>STON.fi says its labeling inputs can include user complaints, manual monitoring, automatic honeypot alerts, and official legal requests.</p><p>Labels cannot:</p><ul><li>certify every unlabelled token as safe;</li><li>replace checking the contract address;</li><li>tell you whether a token is a good investment;</li><li>eliminate market or liquidity risk;</li><li>guarantee that a token will not lose value;</li><li>replace your own research.</li></ul><p>This distinction is especially important in permissionless DeFi, where new tokens can be created without needing approval from the DEX.</p><h3>A simple pre-swap checklist</h3><p>Before swapping an unfamiliar token, take a few seconds to ask:</p><p>Contract</p><ul><li>Is this the correct contract address?</li><li>Did I get it from an official source?</li></ul><p>Project</p><ul><li>Does the project have legitimate official channels?</li><li>Does the published contract match the token I am viewing?</li></ul><p>Token mechanics</p><ul><li>Does the token have taxes or unusual transfer rules?</li><li>Can it normally be bought and sold?</li></ul><p>Liquidity</p><ul><li>How much liquidity is available?</li><li>Is my trade large relative to that liquidity?</li></ul><p>Trade</p><ul><li>What is the price impact?</li><li>How much will I actually receive?</li><li>Does the route and expected output make sense?</li></ul><p>Warnings</p><ul><li>Does STON.fi show a Fake, Honeypot, Taxable, Suspicious, or other warning?</li><li>If there is no warning, have I still completed the other checks?</li></ul><p>That last question is the one users should remember.</p><h3>The bigger lesson</h3><p>DeFi interfaces can provide useful safety signals, but no single interface label can perform all of your due diligence.</p><p>STON.fi’s warning system is designed to provide additional context around tokens with specific identified characteristics. It is not a blanket verification system for every asset users can encounter.</p><p>So when you see no warning, don’t read it as “verified safe.”</p><p>Read it as:</p><p>“No warning is currently being shown. I still need to check what I am buying.”</p><p>Verify the contract address. Check the project’s official sources. Understand the token mechanics. Look at liquidity and price impact. Then decide whether the trade makes sense for you.</p><p>Risk awareness starts before you click Swap. DYOR, and never treat the absence of a warning as proof that a token is safe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*dFzWHit4uNdOlISPhh-T_A@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3707e62d0fb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does “Unknown Asset” Mean on STON.fi?]]></title>
            <link>https://medium.com/@nuraibrahim1043/what-does-unknown-asset-mean-on-ston-fi-0d7e07b09d94?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d7e07b09d94</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 09:08:16 GMT</pubDate>
            <atom:updated>2026-09-25T09:08:16.674Z</atom:updated>
            <content:encoded><![CDATA[<p>If you are using STON.fi and encounter a token displayed with the label:</p><h3>Unknown Asset</h3><p>the first thing to understand is that the label itself should not be treated as a safety verdict.</p><p>At the time of reviewing STON.fi’s publicly available Help Center and Blog documentation, the exact meaning and trigger conditions for the “Unknown Asset” label are not clearly defined in the public documentation reviewed.</p><h3>That distinction matters.</h3><p>Rather than guessing what the label means, users should treat it as a reason to pause and verify the asset independently.</p><h3>What does the interface actually show?</h3><p>The interface state in question is straightforward:</p><p>Token → “Unknown Asset”</p><p>That is the information a user can see.</p><p>What is not established by the publicly available documentation reviewed is exactly what STON.fi’s backend uses to assign this particular label, what conditions cause it to appear, or whether it corresponds to a specific internal asset-resolution process.</p><p>STON.fi’s documented token-warning system currently describes labels such as Fake, Honeypot, Taxable, Suspicious, and DMCA Notice. These labels have documented meanings and specific interface behavior. “Unknown Asset” is not given the same canonical public definition in the sources reviewed.</p><p>Therefore, it would be inaccurate to tell users that “Unknown Asset” definitely means a scam, an unverified token, a newly created token, or a token with insufficient liquidity.</p><p>Those interpretations require confirmation from STON.fi.</p><p>Unknown identity is not the same as unsafe</p><p>There is an important distinction between not having enough information about an asset and having evidence that an asset is dangerous.</p><p>For example, STON.fi explicitly documents certain risk categories.</p><p>A Fake token is one that imitates a known asset, project, or brand.</p><p>A Honeypot can generally be bought but cannot normally be sold.</p><p>A Taxable token has additional transfer or swap-fee mechanics.</p><p>A Suspicious token raises concerns requiring additional attention.</p><p>These labels communicate specific characteristics identified by STON.fi’s monitoring and review processes.</p><p>“Unknown Asset,” however, should not automatically be interpreted as belonging to any of those categories.</p><p>Likewise, it should not be interpreted in the opposite direction as:</p><p>“STON.fi has checked this token and confirmed that it is safe.”</p><p>There is no basis in the reviewed public documentation for making that claim.</p><h3>What can you verify yourself?</h3><p>Until STON.fi publishes or confirms the exact meaning of the label, users can perform several independent checks.</p><h4>1. Verify the contract address</h4><p>The contract address is one of the most important pieces of information when identifying a token.</p><p>A token’s name, ticker, and logo can be copied.</p><p>The contract address provides a much more precise way to identify the asset you are interacting with.</p><p>STON.fi’s Help Center specifically warns that scam tokens can copy popular names and recommends using the correct official contract address when importing a custom token. It also states that STON.fi cannot verify whether a custom token is trustworthy.</p><p>So:</p><p>Find the token’s official contract address → compare it with the address shown by the asset you’re considering.</p><p>If the addresses do not match, stop and investigate.</p><h4>2. Check the project’s official sources</h4><p>Do not rely only on the token’s name or logo.</p><p>Look for the project’s official website and official communication channels, then compare the contract address published there with the asset you’re viewing.</p><p>This is especially important when dealing with popular names or newly launched tokens.</p><p>STON.fi itself recommends checking official sources and doing your own research before interacting with custom tokens.</p><h4>3. Check the liquidity</h4><p>Even if the contract address is correct, you still need to understand the market you are entering.</p><p>STON.fi explains that liquidity pools contain the assets available for swaps, and anyone can provide liquidity or create a pool.</p><p>A token having a pool does not automatically tell you that the project is legitimate.</p><p>It also does not mean there is enough liquidity for your intended trade.</p><p>STON.fi’s pool guidance notes that small liquidity can result in significant price impact when users make swaps.</p><p>So check:</p><ul><li>How much liquidity is in the pool?</li><li>How large is your trade compared with that liquidity?</li><li>What price impact does STON.fi display?</li><li>Does the expected output make sense?</li></ul><p>Liquidity is a market-condition check, not a token-verification check.</p><h4>4. Understand what the label does not tell you</h4><p>If you see Unknown Asset, do not use that label alone to answer questions such as:</p><p>“Is this token legitimate?”</p><p>“Is this token a scam?”</p><p>“Is this the official token?”</p><p>“Will I be able to sell it?”</p><p>“Is this a good investment?”</p><p>The public documentation reviewed does not establish that the Unknown Asset label answers any of these questions.</p><p>Those questions require additional evidence.</p><p>For example, the contract address can help establish whether you have the asset published by the project.</p><p>Liquidity and price impact can help you understand the trading environment.</p><p>Project sources can help you establish whether the asset is actually associated with the project you intended to interact with.</p><p>These checks complement each other.</p><h3>What STON.fi does document about token warnings</h3><p>STON.fi has a documented interface-level labeling system for certain non-standard or potentially risky tokens.</p><p>The documented labels include:</p><p>Label	Documented meaning</p><p>Fake	Token imitates a known asset, project, or brand</p><p>Honeypot	Token can generally be bought but cannot normally be sold</p><p>Taxable	Token contract has an additional transfer/swap-fee mechanism</p><p>Suspicious	Token raises concerns requiring additional attention</p><p>DMCA Notice	Token is associated with an intellectual-property complaint</p><p>STON.fi explains that these labels are based on signals such as user complaints, manual monitoring, automatic honeypot alerts, and legal notices.</p><p>This documented system is useful because it shows an important principle:</p><p>A label should communicate a specific piece of information, rather than being interpreted as a universal safety score.</p><p>That same principle is why we should not invent a definition for “Unknown Asset” when the public documentation does not provide one.</p><p>A simple checklist when you see “Unknown Asset”</p><p>Before interacting with the token, ask:</p><p>Contract</p><ul><li>Do I have the correct contract address?</li><li>Does it match the address published by the project’s official source?</li></ul><p>Project</p><ul><li>Can I identify the actual project behind the token?</li><li>Are its official website and communication channels genuine?</li></ul><p>Liquidity</p><ul><li>Is there sufficient liquidity for the trade?</li><li>What price impact does the swap show?</li></ul><p>Token behavior</p><ul><li>Are there unusual taxes or transfer mechanics?</li><li>Can the token’s trading behavior be independently verified?</li></ul><p>Interface</p><ul><li>Is there another documented STON.fi warning or restriction?</li><li>Am I relying on the absence of a warning as if it were verification?</li></ul><p>If you cannot confidently answer these questions, slowing down is better than assuming.</p><h3>What we can and cannot say about “Unknown Asset”</h3><p>Based on the current public documentation reviewed, we can confidently say that STON.fi has a documented system for identifying certain token characteristics and risks.</p><p>We can also verify that STON.fi allows users to import custom tokens using their smart-contract addresses, while explicitly warning that the platform cannot verify whether a custom token is trustworthy.</p><p>What we cannot currently verify from the reviewed public documentation is the exact technical or operational definition of the “Unknown Asset” label.</p><p>That could represent an asset-resolution or metadata state, but that would be an interpretation unless STON.fi confirms it.</p><p>For support education, that distinction is important.</p><p>Final takeaway</p><p>If STON.fi shows “Unknown Asset,” don’t automatically translate it into “scam.”</p><p>But don’t translate it into “safe” either.</p><p>The label’s exact current meaning should be confirmed directly with STON.fi product/support before treating it as a defined safety signal.</p><p>Until then, verify the contract address, check the project’s official sources, examine liquidity and price impact, and understand the asset’s mechanics before interacting with it.</p><p>When the available information is incomplete, the safest assumption is not certainty. It is to pause, verify, and understand what you are interacting with.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*aDM916PN5FDg3X6XSYSQEQ@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d7e07b09d94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does No Warning on STON.fi Mean a Token Is Safe?]]></title>
            <link>https://medium.com/@nuraibrahim1043/does-no-warning-on-ston-fi-mean-a-token-is-safe-e3f2efbed460?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3f2efbed460</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Fri, 25 Sep 2026 06:44:11 GMT</pubDate>
            <atom:updated>2026-09-25T06:44:11.085Z</atom:updated>
            <content:encoded><![CDATA[<p>When swapping a token on a DEX, users often look for warning labels as a quick safety signal.</p><p>That is useful, but there is an important distinction that can easily be missed:</p><p>No warning on STON.fi does not mean a token has been verified as safe.</p><p>STON.fi uses interface-level labels and restrictions to give users additional context about certain tokens. These labels can help identify specific risks, but they are not a universal certification system for every token available on the protocol.</p><p>Understanding that difference can help users make better decisions before swapping.</p><h3>What do STON.fi labels actually tell you?</h3><p>STON.fi can apply different interface-level labels to tokens when specific characteristics or risk signals are identified.</p><p>For example:</p><ul><li>Fake: The token imitates a known asset, project, or brand.</li><li>Honeypot: The token can generally be bought but cannot be sold normally.</li><li>Taxable: The token has an additional swap or transfer-fee mechanism.</li><li>Suspicious: The token raises concerns that require additional attention.</li><li>DMCA Notice: The token is associated with an intellectual-property complaint.</li></ul><p>These labels are not all saying the same thing. Each one communicates a particular characteristic or concern that STON.fi has identified.</p><p>Some labels also affect how the token can be accessed through the STON.fi interface. For example, Fake and Honeypot tokens are not available for swapping through the standard STON.fi interface, while some other flagged tokens may remain swappable with the warning visible.</p><p>So a label is best understood as context and risk information, not as a complete security assessment.</p><h3>No warning is not verification</h3><p>This is the key point:</p><p>A token having no warning on STON.fi does not mean the token is verified, endorsed, or guaranteed to be safe.</p><p>STON.fi itself does not operate a token-verification system. For example, the “Unverified Token” badge found in products such as Tonkeeper or Tonviewer belongs to those third-party services, not to STON.fi.</p><p>STON.fi also operates permissionlessly. There is no formal listing process requiring STON.fi approval before a TON Jetton can be added to the protocol. Anyone can create a Jetton and create a liquidity pool.</p><p>That means users should not interpret the absence of a warning as:</p><p>“STON.fi checked this token and confirmed that it is safe.”</p><p>That is not what the interface is communicating.</p><p>Instead, think of it this way:</p><p>A warning can tell you that something specific has been identified. No warning simply means you should continue your own checks.</p><p>What should you check before buying a token?</p><p>A token’s name, logo, price, or lack of a warning should never be your only basis for deciding whether to interact with it.</p><h3>Here are some independent checks worth performing.</h3><ol><li>Verify the contract address</li></ol><p>This is one of the most important checks.</p><p>Scam tokens can copy the name, ticker, and visual identity of legitimate projects. The contract address is what distinguishes one token deployment from another.</p><p>Get the contract address from a project’s official source and compare it carefully with the address shown by the token interface.</p><p>STON.fi specifically recommends using the correct official contract address and warns that scam tokens can copy popular names.</p><p>Do not assume that a familiar ticker means you have found the legitimate asset.</p><p>2. Check the project’s official channels</p><p>Look for the project’s official website and verified social channels.</p><p>Then compare the contract address published there with the address of the token you are about to swap.</p><p>Be particularly careful with links received through random replies, private messages, Telegram groups, or unofficial accounts.</p><p>The goal is to establish that the token you are looking at is actually connected to the project you think it is.</p><p>3. Understand the token’s mechanics</p><p>Some tokens have mechanics that can materially affect your trade.</p><p>For example, taxable tokens can charge additional fees when tokens are transferred or swapped. STON.fi marks supported taxable tokens with a Taxable flag and applies restrictions around their use.</p><p>Before buying an unfamiliar token, understand:</p><ul><li>whether it has transfer or trading taxes,</li><li>whether there are unusual restrictions,</li><li>whether buying and selling work normally,</li><li>whether the contract has special permissions or mechanics,</li><li>and whether the amount you receive can differ significantly from the quoted amount.</li></ul><p>4. Look at liquidity</p><p>Liquidity is another important part of the picture.</p><p>A token can exist and be tradable while having very little liquidity.</p><p>That matters because a shallow pool can cause a relatively small trade to move the price significantly. STON.fi’s own pool guidance notes that insufficient liquidity can create high price impact and unstable pricing.</p><p>This is where liquidity checks complement token labels.</p><p>The label answers one question:</p><p>“Has STON.fi identified a specific characteristic or risk signal?”</p><p>The liquidity check answers another:</p><p>“How much liquidity is actually available for this trade, and how much could my transaction move the market?”</p><p>Neither replaces the other.</p><p>5. Check price impact before confirming</p><p>Even when a token has no warning, look at the quote before signing.</p><p>STON.fi shows information such as the expected amount received, price impact, and route before confirmation.</p><p>If a small trade produces unexpectedly high price impact, stop and investigate.</p><p>A high price impact does not automatically prove that a token is malicious. It can simply indicate that the available liquidity is small relative to your trade. But it is still a reason to slow down and understand what is happening.</p><p>Why contract address and liquidity checks work together</p><p>Consider two different scenarios.</p><p>Scenario A: Familiar name, wrong contract</p><p>You see a token called “USDT” with the familiar logo.</p><p>There is no warning.</p><p>You check the official issuer’s contract address and discover that the address does not match.</p><p>The absence of a warning does not make the token legitimate.</p><p>The contract-address check catches what the label alone cannot.</p><p>Scenario B: Correct token, very low liquidity</p><p>Now imagine you find the correct contract address for a legitimate project.</p><p>The token has no warning.</p><p>But the pool has very little liquidity, and your intended trade produces significant price impact.</p><p>The token may not be a fake token or a honeypot. The issue here is market liquidity.</p><p>The liquidity and price-impact checks reveal a different risk that a token label is not designed to answer.</p><p>This is why responsible token research requires multiple checks rather than one signal.</p><h3>What labels can and cannot communicate</h3><p>It helps to think of STON.fi labels as one layer of information.</p><p>Labels can:</p><ul><li>highlight specific identified characteristics;</li><li>warn about certain known risk patterns;</li><li>add context before interaction;</li><li>restrict access to some categories of tokens;</li><li>make potentially problematic token behavior more visible.</li></ul><p>STON.fi says its labeling inputs can include user complaints, manual monitoring, automatic honeypot alerts, and official legal requests.</p><h3>Labels cannot:</h3><ul><li>certify every unlabelled token as safe;</li><li>replace checking the contract address;</li><li>tell you whether a token is a good investment;</li><li>eliminate market or liquidity risk;</li><li>guarantee that a token will not lose value;</li><li>replace your own research.</li></ul><p>This distinction is especially important in permissionless DeFi, where new tokens can be created without needing approval from the DEX.</p><p>A simple pre-swap checklist</p><p>Before swapping an unfamiliar token, take a few seconds to ask:</p><p>Contract</p><ul><li>Is this the correct contract address?</li><li>Did I get it from an official source?</li></ul><p>Project</p><ul><li>Does the project have legitimate official channels?</li><li>Does the published contract match the token I am viewing?</li></ul><p>Token mechanics</p><ul><li>Does the token have taxes or unusual transfer rules?</li><li>Can it normally be bought and sold?</li></ul><p>Liquidity</p><ul><li>How much liquidity is available?</li><li>Is my trade large relative to that liquidity?</li></ul><p>Trade</p><ul><li>What is the price impact?</li><li>How much will I actually receive?</li><li>Does the route and expected output make sense?</li></ul><p>Warnings</p><ul><li>Does STON.fi show a Fake, Honeypot, Taxable, Suspicious, or other warning?</li><li>If there is no warning, have I still completed the other checks?</li></ul><p>That last question is the one users should remember.</p><h3>The bigger lesson</h3><p>DeFi interfaces can provide useful safety signals, but no single interface label can perform all of your due diligence.</p><p>STON.fi’s warning system is designed to provide additional context around tokens with specific identified characteristics. It is not a blanket verification system for every asset users can encounter.</p><p>So when you see no warning, don’t read it as “verified safe.”</p><p>Read it as:</p><p>“No warning is currently being shown. I still need to check what I am buying.”</p><p>Verify the contract address. Check the project’s official sources. Understand the token mechanics. Look at liquidity and price impact. Then decide whether the trade makes sense for you.</p><p>Risk awareness starts before you click Swap. DYOR, and never treat the absence of a warning as proof that a token is safe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*dFzWHit4uNdOlISPhh-T_A@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3f2efbed460" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Where Can You See the Blockchain Fee Before a Swap on STON.fi?]]></title>
            <link>https://medium.com/@nuraibrahim1043/where-can-you-see-the-blockchain-fee-before-a-swap-on-ston-fi-18090cb89e71?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/18090cb89e71</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 05:39:49 GMT</pubDate>
            <atom:updated>2026-09-24T05:39:49.143Z</atom:updated>
            <content:encoded><![CDATA[<p>When making a token swap on STON.fi, it is important to understand the costs before approving the transaction.</p><p>One of the values shown in the swap preview is the blockchain fee. This is the network cost required to execute the transaction, and on TON it is paid in GRAM (formerly Toncoin).</p><p>The useful part is that you do not have to wait until after the transaction to discover the estimated fee. STON.fi displays it in the Swap Details section before you confirm the swap.</p><h3>Where to find the blockchain fee</h3><p>Start by opening the STON.fi swap interface and connecting your wallet.</p><p>Then:</p><ol><li>Select the token you want to send.</li><li>Select the token you want to receive.</li><li>Enter the amount.</li><li>Wait for the swap quote to appear.</li><li>Open or review the Swap Details.</li><li>Look for the field labelled Blockchain fee.</li></ol><p>STON.fi’s Help Center says that after you enter the amount, the interface immediately shows the expected output, swap rate, blockchain fee and price impact.</p><p>So the fee is part of the information you should review before clicking Swap and approving the transaction in your wallet.</p><h3>What does “Blockchain fee” mean?</h3><p>The blockchain fee is the network cost associated with executing the transaction.</p><p>For TON-based swaps, this cost is paid in GRAM.</p><p>It is different from the amount you’re swapping.</p><p>For example, imagine you’re swapping:</p><p>10 GRAM → USDT</p><p>The 10 GRAM is your swap input.</p><p>The blockchain fee is the separate network cost needed to process the transaction.</p><p>This is why your wallet needs to retain some GRAM even when you intend to swap GRAM itself.</p><p>STON.fi currently says a typical swap’s actual blockchain fee is usually around 0.02 GRAM, although the exact amount depends on the route, pool configuration and transaction complexity.</p><p>Estimated fee vs reserved amount</p><p>This is where the terminology can become confusing.</p><p>STON.fi distinguishes between the actual blockchain fee and the amount it temporarily reserves to execute the transaction safely.</p><p>According to the current Help Center:</p><ul><li>A typical swap’s actual blockchain fee is usually around 0.02 GRAM.</li><li>STON.fi reserves approximately 0.3 — 0.35 GRAM when executing the transaction.</li><li>Any unused portion of that reserve is automatically refunded after the swap completes.</li></ul><p>So you should not automatically interpret the entire reserved amount as a permanent fee.</p><p>Think of it as:</p><p>Estimated/required network cost → temporary reserve → transaction executes → unused reserve returned</p><p>The actual amount spent can therefore be lower than the amount temporarily reserved.</p><h3>Why does the fee vary?</h3><p>There isn’t necessarily one universal blockchain-fee number for every STON.fi swap.</p><p>STON.fi says the exact amount depends on factors including:</p><ul><li>The swap route</li><li>Pool configuration</li><li>Transaction complexity</li></ul><p>That means two swaps can display different fee estimates even if they are made by the same wallet.</p><p>For example, a simple route may require different transaction processing from a more complex route.</p><p>This is why checking the current quote is more useful than relying on an old screenshot or assuming that every swap costs exactly the same amount.</p><p>The full swap preview matters</p><p>The blockchain fee is only one part of the information you should examine.</p><p>Before confirming, STON.fi displays several transaction parameters, including:</p><p>Swap rate</p><p>How much of the output token you receive for the token you’re sending.</p><p>Price impact</p><p>How much your own swap affects the price inside the liquidity pool.</p><p>Minimum received</p><p>The lowest amount of the output token you’re guaranteed to receive, taking your slippage tolerance into account.</p><p>Blockchain fee</p><p>The network cost required to execute the transaction, paid in GRAM on TON.</p><p>Looking at only the fee can therefore give you an incomplete picture.</p><p>Don’t confuse blockchain fees with the swap fee</p><p>A blockchain fee and a swap fee are not necessarily the same thing.</p><p>The blockchain fee relates to processing the transaction on the underlying network.</p><p>A swap fee is associated with the swap/liquidity mechanism.</p><p>They serve different purposes, so when reviewing a quote, pay attention to the specific labels shown by the interface rather than treating every cost as “gas.”</p><h3>What should you check before confirming?</h3><p>A good pre-confirmation routine is:</p><ol><li>Check the input token</li></ol><p>Make sure you selected the asset you actually intend to sell.</p><p>2. Check the output token</p><p>Verify that the destination token is correct.</p><p>3. Check the amount</p><p>Make sure the amount you’re sending is what you intended.</p><p>4. Check the expected output</p><p>Look at approximately how much you should receive.</p><p>5. Check the blockchain fee</p><p>This tells you the network cost currently displayed for the transaction.</p><p>6. Check price impact</p><p>A large price impact can significantly affect the effective execution rate.</p><p>7. Check minimum received</p><p>This shows the lower boundary for the output based on your slippage settings.</p><p>8. Check your remaining GRAM</p><p>Especially when swapping GRAM, make sure your wallet retains enough GRAM for network fees.</p><p>9. Only then confirm</p><p>Once the complete quote makes sense, proceed with the swap and approve it in your wallet.</p><p>STON.fi’s own swap guide follows this general flow: enter the amount, review the displayed parameters, click Swap, and then approve the transaction in your wallet.</p><h3>Why you shouldn’t rely on a fixed fee</h3><p>Suppose someone tells you:</p><p>“STON.fi swaps always cost 0.02 GRAM.”</p><p>That would be an oversimplification.</p><p>STON.fi currently describes 0.02 GRAM as the usual actual blockchain fee for a typical swap, not as a guaranteed fixed fee for every transaction. The Help Center specifically notes that the exact amount depends on the route, pool configuration and transaction complexity.</p><p>The better habit is:</p><p>Check the fee displayed for your transaction.</p><p>The interface has the current quote for the route you’re actually about to use.</p><p>What about the temporary reserve?</p><p>The reserve is particularly important when your wallet contains only a small amount of GRAM.</p><p>STON.fi automatically reserves approximately 0.3 — 0.35 GRAM when executing a swap to ensure sufficient funds are available for the transaction.</p><p>This is also why STON.fi won’t allow you to simply swap your entire GRAM balance.</p><p>The wallet needs some GRAM available for network costs.</p><p>After the transaction completes, STON.fi says the unused portion of the reserved amount is automatically refunded.</p><p>A simple example</p><p>Imagine your wallet contains:</p><p>5 GRAM</p><p>You select:</p><p>GRAM → USDT</p><p>After entering the amount, STON.fi displays the swap details.</p><p>You might see information such as:</p><ul><li>Expected output</li><li>Swap rate</li><li>Price impact</li><li>Minimum received</li><li>Blockchain fee</li></ul><p>The important point is that the blockchain fee shown there is the current estimate for that transaction, while the temporary amount reserved for execution can be higher.</p><p>So don’t assume that the entire reserve will disappear from your wallet.</p><p>The safest habit: review the whole quote</p><p>A blockchain fee by itself doesn’t tell you whether the swap makes sense from an execution perspective.</p><p>Before signing, look at the complete transaction:</p><p>Input amount</p><p>↓</p><p>Expected output</p><p>↓</p><p>Swap rate</p><p>↓</p><p>Price impact</p><p>↓</p><p>Minimum received</p><p>↓</p><p>Blockchain fee</p><p>↓</p><p>Wallet balance remaining</p><p>↓</p><p>Confirm</p><p>This gives you a much clearer picture of what you’re actually approving.</p><h3>Final takeaway</h3><p>The blockchain fee on STON.fi is visible before you confirm the swap.</p><p>After selecting your tokens and entering the amount, check the Swap Details section and look for Blockchain fee. STON.fi says this fee is paid in GRAM and that the exact cost depends on the route, pool configuration and transaction complexity.</p><p>Also remember the distinction between the estimated/actual fee and the temporary reserve. STON.fi currently says a typical swap’s actual blockchain fee is usually around 0.02 GRAM, while approximately 0.3 — 0.35 GRAM may be reserved during execution, with unused reserve refunded afterward.</p><p>The best practice is simple: don’t confirm a swap by looking at the output alone. Check the entire quote — including the blockchain fee, price impact, minimum received and remaining wallet balance — before approving the transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*RQHQopsaDMHCbfkzG_P0Yw@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18090cb89e71" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Can’t I Swap My Entire GRAM Balance on STON.fi?]]></title>
            <link>https://medium.com/@nuraibrahim1043/why-cant-i-swap-my-entire-gram-balance-on-ston-fi-7de9f5d8cb9e?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/7de9f5d8cb9e</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 05:37:32 GMT</pubDate>
            <atom:updated>2026-09-24T05:37:32.880Z</atom:updated>
            <content:encoded><![CDATA[<p>If you try to swap your entire GRAM balance on STON.fi, you may notice that the interface does not allow you to use 100% of what is in your wallet.</p><p>This is intentional.</p><p>The reason is simple: GRAM is not only the token you may want to swap — it is also needed to pay the TON blockchain fee required to execute the transaction.</p><p>STON.fi therefore keeps a small amount available for network costs instead of allowing your entire balance to be committed to the swap.</p><p>GRAM has two roles in this situation</p><p>Suppose your wallet contains 10 GRAM and you want to swap GRAM for another token.</p><p>It might seem natural to enter:</p><p>10 GRAM → [another token]</p><p>But the transaction itself needs GRAM to be executed on the TON blockchain.</p><p>So if all 10 GRAM were used as the swap input, there would be nothing left in the wallet to cover the transaction’s network cost.</p><p>This is why STON.fi automatically keeps part of your GRAM balance available for the transaction.</p><p>The STON.fi Help Center explains that swaps require GRAM, formerly Toncoin, to cover blockchain fees.</p><h3>What is the reserve?</h3><p>STON.fi currently says that, at the moment of a swap, it reserves approximately 0.3 — 0.35 GRAM to execute the transaction safely.</p><p>This does not mean that you permanently lose 0.3 — 0.35 GRAM.</p><p>The actual blockchain fee for a typical swap is usually around 0.02 GRAM, while the larger temporary reserve gives the transaction enough room to execute. Any unused portion of the reserve is automatically refunded after the swap completes.</p><p>Think of it like carrying extra cash for a transaction:</p><p>GRAM balance → temporary reserve → transaction executes → unused amount returned</p><p>The reserve exists because the exact transaction cost can depend on the swap route, pool configuration, and transaction complexity.</p><h3>Why can’t you leave your wallet with zero GRAM?</h3><p>Because the swap transaction itself needs to be submitted and processed on TON.</p><p>GRAM is the native currency used to pay the network fee.</p><p>If you attempted to spend your entire GRAM balance on the swap, you would have no GRAM available for the blockchain transaction.</p><p>That creates a practical problem:</p><p>You need some GRAM to spend GRAM.</p><p>This is why STON.fi prevents you from simply committing your complete GRAM balance to the swap. Its Help Center explicitly says that the interface automatically reserves a small amount of GRAM and therefore does not allow the entire GRAM balance to be swapped at once.</p><p>This isn’t a limitation on the amount of GRAM you own. It is a requirement for executing the transaction.</p><p>A simple example</p><p>Imagine you have:</p><p>10 GRAM</p><p>You want to swap it for USDT.</p><p>Instead of entering:</p><p>10 GRAM → USDT</p><p>you could reduce the input amount and leave some GRAM available for the transaction.</p><p>For example:</p><p>9.6 GRAM → USDT</p><p>The exact amount you can swap depends on the balance and the transaction requirements shown by the STON.fi interface.</p><h3>The important principle is:</h3><p>Don’t use your entire GRAM balance as the swap input.</p><p>Leave enough GRAM for the network fee/reserve.</p><p>How to reduce the amount you swap</p><p>The process is straightforward:</p><ol><li>Connect your TON wallet to STON.fi.</li><li>Select GRAM as the token you’re sending.</li><li>Select the token you want to receive.</li><li>Enter an amount below your total GRAM balance.</li><li>Check the Blockchain fee shown in the swap details.</li><li>Review the expected output and other transaction parameters.</li><li>Confirm the swap in your wallet.</li></ol><p>STON.fi’s current swap guide says the interface displays the expected output, swap rate, blockchain fee and price impact before confirmation.</p><p>For example</p><p>If your wallet shows:</p><p>Balance: 10 GRAM</p><p>Don’t try to swap:</p><p>10 GRAM</p><p>Instead, lower the input until the interface accepts the transaction and leaves sufficient GRAM available for the network cost.</p><p>The exact amount to leave should not be treated as a universal fixed number because transaction costs can vary.</p><h3>What happens to the unused reserve?</h3><p>This is an important detail.</p><p>You might see STON.fi reserve around 0.3 — 0.35 GRAM, while the actual blockchain fee for a typical swap is usually around 0.02 GRAM.</p><p>The difference is not simply an additional fee charged to you.</p><p>STON.fi states that unused reserved GRAM is automatically refunded to your wallet after the swap completes.</p><p>So the reserve should be understood as an amount temporarily set aside to make sure the transaction can execute, rather than the amount you should expect to permanently spend.</p><h3>Check the fee before confirming</h3><p>STON.fi shows the estimated blockchain fee in the swap details before you approve the transaction.</p><p>This gives you an opportunity to check:</p><ul><li>How much GRAM you’re swapping</li><li>Expected output</li><li>Swap rate</li><li>Price impact</li><li>Blockchain fee</li><li>Minimum received</li><li>Whether enough GRAM remains in your wallet</li></ul><p>STON.fi’s Help Center recommends keeping a small amount of GRAM in the wallet for network fees.</p><h3>What if you only have a very small GRAM balance?</h3><p>This is where the distinction becomes especially important.</p><p>If almost all of your wallet balance is GRAM, you cannot necessarily convert every last fraction of it into another token because the transaction still needs GRAM for network fees.</p><p>For example, having:</p><p>0.10 GRAM</p><p>doesn’t necessarily mean you can swap the entire 0.10 GRAM.</p><p>The wallet needs to retain enough GRAM for the transaction itself.</p><p>If your balance is too small, you may need to add more GRAM to the wallet before making the swap.</p><p>GRAM isn’t just another swap asset</p><p>On TON, GRAM has an additional role: it is the native currency used for network fees.</p><p>That means when you swap GRAM, you have to account for two things simultaneously:</p><ol><li>The amount you want to exchange</li></ol><p>and</p><p>2. The amount required to execute the transaction.</p><p>This is different from swapping a Jetton such as USDT.</p><p>If you’re swapping USDT for another token, the blockchain fee is still paid in GRAM, so you need some GRAM in the wallet even though GRAM isn’t the token being swapped. STON.fi’s glossary specifically notes that users need a small amount of GRAM in their wallet to pay network fees.</p><p>Don’t confuse the reserve with the swap fee</p><p>There are three concepts worth separating:</p><p>Swap amount</p><p>The amount of GRAM you’re exchanging for another asset.</p><p>Blockchain fee</p><p>The network cost required to execute the transaction.</p><p>Temporary reserve</p><p>The larger amount STON.fi sets aside during the transaction to ensure there is enough GRAM available; unused funds are refunded afterward.</p><p>STON.fi says the exact blockchain fee can depend on the route, pool configuration and transaction complexity, which is why the interface’s fee estimate is more useful than assuming a single fixed number.</p><h3>Where can you check the fees?</h3><p>STON.fi provides a dedicated fee guide covering blockchain and swap-related costs.</p><p>STON.fi Blockchain and Swap Fees Guide⁠</p><p>You can also check the Blockchain fee directly in the swap interface before confirming the transaction.</p><p>The simple rule to remember</p><p>If you’re swapping GRAM on STON.fi, don’t try to spend your entire wallet balance.</p><p>Leave some GRAM available for the transaction.</p><p>A simple way to think about it is:</p><p>Your GRAM balance is not entirely available for swapping because part of it is needed to execute the swap itself.</p><p>STON.fi currently reserves approximately 0.3 — 0.35 GRAM at swap time, while stating that a typical swap’s actual blockchain fee is usually around 0.02 GRAM and that unused reserved GRAM is refunded after completion.</p><p>So if the interface won’t let you swap your entire GRAM balance, it isn’t necessarily an error.</p><p>Reduce the input amount, leave enough GRAM for gas, review the fee shown by STON.fi, and then confirm the transaction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/836/1*b-QDIM2N_0CabwM-gXkTeA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7de9f5d8cb9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Does “Minimum Received” Mean on STON.fi?]]></title>
            <link>https://medium.com/@nuraibrahim1043/what-does-minimum-received-mean-on-ston-fi-6efeb98bbec3?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/6efeb98bbec3</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 12:39:52 GMT</pubDate>
            <atom:updated>2026-09-20T12:39:52.377Z</atom:updated>
            <content:encoded><![CDATA[<p>When you prepare a token swap on STON.fi, you may notice several numbers before confirming the transaction:</p><ul><li>Expected output</li><li>Swap rate</li><li>Price impact</li><li>Blockchain fee</li><li>Minimum received</li></ul><p>At first glance, “Minimum received” can look like just another estimate.</p><p>It isn’t.</p><p>For a same-chain swap, it represents an important protection limit: the lowest amount of the output token you are willing to receive for the transaction to execute.</p><p>STON.fi defines Minimum received as the lowest amount of the output token guaranteed by the swap, taking your slippage tolerance into account.</p><p>Understanding this number helps you know what you are actually agreeing to when you click Swap.</p><h3>What exactly is “Minimum received”?</h3><p>Suppose you want to swap:</p><p>100 USDT → TON</p><p>STON.fi might show an estimated output of:</p><p>250 TON</p><p>But the market can move between the moment you review the quote and the moment your transaction is actually executed.</p><p>Your Minimum received might therefore be:</p><p>247.5 TON</p><p>That means the transaction is not simply saying:</p><p>“You will definitely receive exactly 250 TON.”</p><p>Instead, the protection is closer to:</p><p>“I accept this swap only if I receive at least 247.5 TON.”</p><p>That lower boundary is determined using your slippage tolerance.</p><p>STON.fi’s Help Center describes Minimum received as the lowest amount you are guaranteed to receive, given your slippage tolerance.</p><p>This distinction is important because the expected output and the minimum acceptable output are not necessarily the same number.</p><h3>Minimum received and slippage are connected</h3><p>To understand Minimum received, you first need to understand slippage tolerance.</p><p>Slippage tolerance is the maximum price movement you are willing to accept between confirming a swap and the transaction being executed on-chain.</p><p>For example, imagine:</p><p>Expected output: 1,000 tokens</p><p>Slippage tolerance: 1%</p><p>A simplified calculation would be:</p><p>1,000 × (1 − 0.01) = 990 tokens</p><p>So the minimum acceptable output would be approximately:</p><p>990 tokens</p><p>The exact amount shown by the interface depends on the quote and transaction details, but the concept is the same.</p><p>Your slippage setting establishes the boundary.</p><p>Minimum received expresses that boundary in tokens.</p><h3>Why do you need this protection?</h3><p>Because the price you see when you prepare a transaction is not necessarily the price that exists when the transaction executes.</p><p>Between those two moments, the pool’s state can change.</p><p>For example:</p><p>You open STON.fi.</p><p>You select your tokens.</p><p>The interface calculates an expected output of 500 tokens.</p><p>You click Swap.</p><p>Your wallet asks you to approve the transaction.</p><p>During that short period, other transactions may interact with the same liquidity pool.</p><p>The available rate can change.</p><p>Without a minimum-output condition, you could potentially receive substantially less than the amount you expected.</p><p>The minimum-received value creates a boundary.</p><p>If execution cannot provide at least that amount, the swap should not proceed at an unacceptable output.</p><p>STON.fi describes its swap protection as being designed to protect users from unfavorable price movement, with slippage tolerance controlling the amount of movement accepted.</p><h3>A simple example</h3><p>Let’s make this more practical.</p><p>Suppose you want to swap:</p><p>100 USDT → STON</p><p>STON.fi displays:</p><p>Expected output: 600 STON</p><p>Your slippage tolerance is:</p><p>1%</p><p>Your minimum received would be approximately:</p><p>594 STON</p><p>So there are two important numbers:</p><p>Expected output</p><p>600 STON</p><p>This is what the current quote estimates you will receive.</p><p>Minimum received</p><p>594 STON</p><p>This is the lower boundary you are accepting.</p><p>If the swap can execute at 599 STON, that is above your minimum.</p><p>If it can execute at 596 STON, that is also above your minimum.</p><p>But if the execution would result in only 590 STON, that falls below your minimum.</p><p>The protection is designed to prevent that transaction from executing at that unacceptable output.</p><h3>Where can you see Minimum received?</h3><p>You don’t need to wait until after the transaction.</p><p>You should check it before signing the swap in your wallet.</p><p>The normal STON.fi swap flow is:</p><ol><li>Connect your wallet</li></ol><p>↓</p><p>2. Select the From token</p><p>↓</p><p>3. Select the To token</p><p>↓</p><p>4. Enter the amount</p><p>↓</p><p>5. Review the swap details</p><p>↓</p><p>6. Click Swap</p><p>↓</p><p>7. Approve the transaction in your wallet</p><p>STON.fi’s Help Center says the interface displays important swap information before confirmation, including the expected output, swap rate, blockchain fee and price impact; its detailed transaction-parameter guidance also defines Minimum received.</p><p>So before you approve the transaction, don’t look only at:</p><p>“How much will I get?”</p><p>Also look at:</p><p>“What is the minimum I will accept?”</p><p>That second number is the protection boundary.</p><h3>Minimum received does not eliminate price impact</h3><p>This is one of the most important distinctions.</p><p>Minimum received and price impact solve different problems.</p><p>Price impact</p><p>Price impact describes how much your own trade moves the pool’s price.</p><p>Large swaps relative to available liquidity generally have greater price impact. STON.fi specifically describes larger trades in smaller pools as having higher price impact.</p><p>Minimum received</p><p>Minimum received establishes the lowest output amount you will accept based on your slippage tolerance.</p><p>So imagine STON.fi shows:</p><p>Expected output: 1,000 tokens</p><p>Price impact: 4%</p><p>Slippage tolerance: 1%</p><p>Minimum received: 990 tokens</p><p>The 1% slippage setting does not magically remove the 4% price impact.</p><p>The price impact is already reflected in the quote you are receiving.</p><p>The minimum-received protection then establishes how much additional unfavorable movement you are willing to tolerate between the quote and execution.</p><p>This is why you should look at both numbers.</p><h3>Price impact happens before you even think about slippage</h3><p>This is easier to understand with an example.</p><p>Suppose a liquidity pool is relatively small.</p><p>You want to make a large swap.</p><p>Your trade itself changes the balance of the pool.</p><p>That can move the exchange rate against you.</p><p>STON.fi might therefore calculate a significant price impact.</p><p>You could have:</p><p>Price impact: 5%</p><p>while still having:</p><p>Slippage tolerance: 1%</p><p>The 1% doesn’t mean you are getting a 1%-impact trade.</p><p>It means you are allowing up to a certain amount of additional movement around the quoted execution conditions.</p><p>This is why reducing slippage tolerance is not a substitute for finding adequate liquidity.</p><p>If the underlying trade has high price impact, you need to understand that cost before confirming.</p><h3>What happens if the market moves too far?</h3><p>Suppose your quote shows:</p><p>Expected output: 1,000 tokens</p><p>Your minimum received is:</p><p>990 tokens</p><p>Then the market changes.</p><p>If the transaction can still execute and deliver:</p><p>995 tokens</p><p>the output is above your minimum.</p><p>But if the transaction would only deliver:</p><p>980 tokens</p><p>that is below your stated lower bound.</p><p>The transaction should not execute at that output.</p><p>That’s the protection logic.</p><p>Minimum received = your lower acceptable output boundary.</p><h3>Why you shouldn’t automatically set very high slippage</h3><p>You may sometimes encounter a swap that won’t execute because the selected slippage tolerance is too restrictive.</p><p>The temptation can be:</p><p>“I’ll just increase the slippage.”</p><p>That can make a transaction easier to execute, but it also means accepting a wider range of possible outcomes.</p><p>STON.fi’s Help Center notes that users can adjust slippage and price-impact thresholds, but warns that increasing them above the defaults can lead to worse execution.</p><p>So increasing slippage is not simply a way to make a transaction “work.”</p><p>You are changing the protection boundary.</p><p>That’s why it should be treated as a deliberate setting rather than something to increase automatically.</p><h3>Minimum received is not a guarantee of profit</h3><p>Another important distinction:</p><p>Minimum received protects the transaction from executing below a specified output threshold.</p><p>It does not guarantee that the trade is profitable.</p><p>It doesn’t guarantee that the token price won’t fall afterward.</p><p>It doesn’t guarantee low price impact.</p><p>It doesn’t guarantee that the token itself is legitimate.</p><p>And it doesn’t eliminate network fees.</p><p>It is specifically about the minimum output accepted by the swap transaction.</p><h3>What about Omniston cross-chain swaps?</h3><p>This distinction is especially important when discussing STON.fi’s cross-chain functionality.</p><p>A same-chain STON.fi swap can use a minimum-output condition to protect against unfavorable execution relative to the user’s slippage tolerance.</p><p>Omniston’s cross-chain architecture is a different mechanism.</p><p>For supported cross-chain routes, Omniston uses resolver-based RFQ execution and paired HTLCs to coordinate the source and destination chains. STON.fi describes the resulting settlement as all-or-nothing: either the quoted assets are exchanged, or the transaction unwinds through the timelock/refund mechanism.</p><p>That should not be described as simply the same thing as a normal same-chain Minimum received field.</p><p>There are two different concepts:</p><p>Same-chain swap</p><p>Minimum received</p><p>→ Defines the lower output boundary accepted for the swap, based on slippage tolerance.</p><p>Omniston cross-chain swap</p><p>Firm quote + cross-chain atomic settlement</p><p>→ The resolver provides a quote, and paired HTLCs coordinate the two sides so the quoted exchange either settles or unwinds according to the protocol’s conditions.</p><p>Both involve execution protection, but the mechanisms are different.</p><h3>Why this distinction matters</h3><p>Imagine you’re comparing two transactions.</p><p>Swap A: TON → TON</p><p>You are swapping one TON asset for another on the same blockchain.</p><p>You review:</p><ul><li>expected output;</li><li>price impact;</li><li>minimum received;</li><li>blockchain fee;</li><li>slippage tolerance.</li></ul><p>Here, Minimum received is directly relevant to the lower output boundary of your same-chain swap.</p><p>Swap B: TON → Ethereum</p><p>Now you’re dealing with a cross-chain route.</p><p>Omniston’s architecture involves a quote, resolver liquidity and linked settlement across the two chains. The destination asset is locked by the resolver, while the source asset is locked on the other side under the paired HTLC structure.</p><p>The protection model is therefore not simply:</p><p>“Minimum received on one TON pool.”</p><p>It is a different settlement mechanism designed for coordinating independent blockchains.</p><p>Keeping those concepts separate prevents a lot of confusion about what STON.fi’s various protection mechanisms actually do.</p><h3>What should you check before signing?</h3><p>Before approving a same-chain swap on STON.fi, take a few seconds to look at the complete transaction summary.</p><ol><li>Expected output</li></ol><p>How much does the current quote estimate you will receive?</p><p>2. Minimum received</p><p>What is the lowest output amount you are accepting?</p><p>3. Price impact</p><p>How much does your own trade affect the pool price?</p><p>4. Swap rate</p><p>What rate is being used for the exchange?</p><p>5. Blockchain fee</p><p>How much Gram is required to execute the transaction?</p><p>STON.fi’s first-swap guide specifically recommends reviewing the transaction details before clicking Swap, including the expected output, swap rate, blockchain fee and price impact.</p><h3>A simple mental model</h3><p>You can think about the three numbers like this:</p><p>Expected output</p><p>“This is what I currently expect to receive.”</p><p>Minimum received</p><p>“This is the least I am willing to receive.”</p><p>Price impact</p><p>“This is how much my trade itself moves the pool’s price.”</p><p>And then:</p><p>Slippage tolerance</p><p>“This is how much additional price movement I am willing to tolerate between confirmation and execution.”</p><p>Once you separate these concepts, the STON.fi swap screen becomes much easier to understand.</p><h3>Final thoughts</h3><p>Minimum received is a protection boundary.</p><p>It tells you the lowest amount of the output token that your same-chain swap is allowed to deliver under the selected slippage conditions.</p><p>It is not simply another estimate.</p><p>And it is not the same thing as price impact.</p><p>Before signing a swap, look at the relationship between:</p><p>Expected output → Minimum received → Price impact → Slippage tolerance</p><p>That gives you a much clearer picture of what you’re agreeing to.</p><p>Most importantly, don’t confuse this same-chain protection mechanism with Omniston’s cross-chain all-or-nothing settlement. Omniston uses a different architecture involving resolver quotes and paired HTLCs to coordinate settlement across independent blockchains.</p><p>So the simple rule is:</p><p>For a same-chain swap, Minimum received tells you the lowest output you are accepting.</p><p>Check that number before you sign, understand how it relates to slippage, and remember that it does not make price impact disappear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/887/1*zFfsZzMmnzfQJwi2JC_-vw@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6efeb98bbec3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Price Impact vs Slippage on STON.fi: What’s the Difference?]]></title>
            <link>https://medium.com/@nuraibrahim1043/price-impact-vs-slippage-on-ston-fi-whats-the-difference-c09a885305c5?source=rss-86588d9fc8f8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c09a885305c5</guid>
            <dc:creator><![CDATA[Nura Musa]]></dc:creator>
            <pubDate>Sun, 20 Sep 2026 11:11:36 GMT</pubDate>
            <atom:updated>2026-09-20T11:11:36.538Z</atom:updated>
            <content:encoded><![CDATA[<p>When you swap tokens on a decentralized exchange, two terms can easily cause confusion:</p><p>Price impact</p><p>and</p><p>Slippage</p><p>They both relate to the price you receive, but they describe different things.</p><p>The easiest way to remember the difference is:</p><p>Price impact comes from your trade. Slippage comes from what happens between your quote and execution.</p><p>Understanding this difference makes the STON.fi swap preview much easier to read.</p><h3>What Is Price Impact?</h3><p>Price impact is the effect your own swap has on the price inside a liquidity pool.</p><p>STON.fi uses automated market maker liquidity pools, where token prices are determined by the relationship between the assets available in the pool.</p><p>When you make a swap, you change that balance.</p><p>A small trade may barely affect the pool.</p><p>A large trade relative to the available liquidity can move the pool price much more.</p><p>For example, imagine a pool has deep liquidity.</p><p>You swap a small amount:</p><p>100 TON → USDT</p><p>Your trade represents only a small portion of the available liquidity, so the price impact may be low.</p><p>Now imagine you swap:</p><p>20,000 TON → USDT</p><p>against the same pool.</p><p>The trade is much larger relative to the pool, so it can move the pool price significantly.</p><p>This is why STON.fi explains that bigger swaps in smaller pools have higher price impact.</p><h3>What Causes Price Impact?</h3><p>The main factor is the relationship between trade size and available liquidity.</p><p>Think of liquidity as the depth available to absorb your trade.</p><p>If the pool is deep compared with your transaction, your trade may have relatively little effect.</p><p>If the pool is shallow compared with your transaction, your trade can move the price much more.</p><p>For example:</p><p>Small trade + deep liquidity = potentially lower price impact</p><p>Large trade + shallow liquidity = potentially higher price impact</p><p>The exact percentage depends on the pool, route, token pair and size of the transaction.</p><h3>What Is Slippage?</h3><p>Slippage is the difference between the price you see before confirming a transaction and the price at which the swap actually executes on-chain.</p><p>Unlike price impact, slippage is not necessarily caused by your trade alone.</p><p>The market can move after you receive your quote.</p><p>Another trader could interact with the same liquidity.</p><p>Network delays can give market conditions time to change.</p><p>High volatility can also cause the execution price to move.</p><p>STON.fi specifically describes network delays, market volatility and other users trading at the same time as factors that can increase slippage.</p><p>So:</p><p>Price impact = your trade changes the pool price.</p><p>Slippage = the execution differs from the price you saw before execution.</p><p>A Simple Way to Separate Them</p><p>Imagine you open STON.fi and receive a quote.</p><p>The interface says:</p><p>Estimated Amount: 1,000 USDT</p><p>At that moment, your trade itself has a 4% price impact.</p><p>You click Swap.</p><p>While the transaction is waiting for confirmation, another large trader swaps against the same liquidity.</p><p>The market moves.</p><p>Your transaction eventually executes at a different price.</p><p>In this situation:</p><p>The 4% impact came from your trade’s effect on the pool.</p><p>The additional difference caused by the market changing before execution is slippage.</p><p>Both can affect the final result of the same swap.</p><p>Price Impact Happens Because of the Trade</p><p>This distinction is important.</p><p>Price impact is closely connected to the size of your transaction.</p><p>Suppose two people trade the same token pair.</p><p>Trader A</p><p>Trade: 100 TON</p><p>Pool: Deep liquidity</p><p>Price impact: 0.2%</p><p>Trader B</p><p>Trade: 10,000 TON</p><p>Pool: Same liquidity</p><p>Price impact: 4%</p><p>The second trader is interacting with the same pool, but the trade is much larger relative to its available liquidity.</p><p>That means the second trade can move the pool price more.</p><p>These percentages are illustrative, not live STON.fi quotes. The principle is what matters.</p><p>Slippage Can Happen Even With Low Price Impact</p><p>Now consider a different situation.</p><p>You make a relatively small swap against a deep pool.</p><p>Your price impact is only:</p><p>0.1%</p><p>You receive a quote for:</p><p>1,000 USDT</p><p>You click Swap.</p><p>But the token is moving quickly because the market is volatile.</p><p>Before your transaction is confirmed, the available price changes.</p><p>You might receive:</p><p>995 USDT</p><p>The 0.1% price impact did not suddenly become 0.5%.</p><p>Instead, the difference between your quoted amount and final execution can be related to slippage.</p><p>This is why low price impact does not mean that the final execution must exactly match the original quote.</p><h3>How They Appear on STON.fi</h3><p>STON.fi shows swap information before you confirm the transaction.</p><p>The current swap flow is:</p><ol><li>Open the STON.fi swap interface.</li><li>Connect your wallet.</li><li>Choose the token you are sending.</li><li>Choose the token you want to receive.</li><li>Enter the amount.</li><li>Review the swap preview.</li><li>Check the expected output, price impact and other transaction details.</li><li>Review your slippage settings.</li><li>Confirm the transaction if the conditions are acceptable to you.</li></ol><p>STON.fi’s current Help Center says the interface shows the expected output, swap rate, blockchain fee and price impact after you enter the amount. (STON.fi Help Center)</p><p>STON.fi also explains that slippage tolerance controls how much price movement you are willing to accept between confirming the swap and the transaction landing on-chain. (STON.fi Help Center)</p><h3>Where Slippage Tolerance Fits In</h3><p>This is another area where the two concepts can get mixed up.</p><p>Price impact describes what your trade does to the pool.</p><p>Slippage tolerance is a setting that defines how much execution movement you are willing to accept.</p><p>For example, suppose the interface gives you:</p><p>Estimated Amount: 1,000 USDT</p><p>You have a slippage tolerance of 1%.</p><p>Your minimum acceptable output would be approximately:</p><p>990 USDT</p><p>The exact displayed value can depend on the interface and transaction parameters.</p><p>The important idea is that slippage tolerance acts as a protection against an unfavorable change between the quote and execution.</p><p>STON.fi currently lists a default slippage tolerance of 1%, while noting that users can adjust it and take on the associated risk when doing so. (STON.fi Help Center)</p><p>Scenario 1: High Price Impact</p><p>Imagine a small liquidity pool.</p><p>You want to swap a large amount relative to the pool.</p><p>The STON.fi preview shows:</p><p>Estimated Amount: 9,500 USDT</p><p>Price Impact: 8%</p><p>The high price impact is telling you something about the relationship between your trade and the available liquidity.</p><p>Your trade is large enough to move the pool price significantly.</p><p>This is a price impact issue.</p><p>It exists because of the size of your trade relative to the available liquidity.</p><p>Scenario 2: Market Movement Causes Slippage</p><p>Now imagine a different swap.</p><p>You are trading a relatively small amount against a liquid market.</p><p>The preview shows:</p><p>Estimated Amount: 1,000 USDT</p><p>Price Impact: 0.2%</p><p>You click Swap.</p><p>Before the transaction confirms, another large trade moves the market.</p><p>The price changes.</p><p>Your transaction executes at:</p><p>995 USDT</p><p>The difference between the earlier quote and the execution is related to slippage.</p><p>Here, the important cause is what happened between the quote and the actual execution.</p><p>Can Both Happen at the Same Time?</p><p>Yes.</p><p>This is one of the most important things to understand.</p><p>A swap can have:</p><p>Price impact from your own trade</p><p>and</p><p>Slippage caused by market movement before execution</p><p>at the same time.</p><p>For example:</p><p>You make a large trade against a relatively small pool.</p><p>Your trade creates significant price impact.</p><p>Then the market moves while your transaction is waiting for confirmation.</p><p>The final execution can therefore reflect both effects.</p><p>They are separate concepts, but they can appear in the same transaction.</p><p>Price Impact vs Slippage at a Glance</p><p>Price Impact	Slippage</p><p>What is it?	Effect of your trade on the pool price	Difference between quoted and actual execution price</p><p>Main cause	Your trade size relative to liquidity	Market movement, network delay, other trades and volatility</p><p>Happens when?	As your trade interacts with the liquidity	Between quote and on-chain execution</p><p>Related to liquidity?	Yes, directly	Can be indirectly affected by liquidity and market conditions</p><p>Can you see it before swapping?	Yes	You can set a slippage tolerance before execution</p><p>Simple example	Large trade moves pool price	Market moves before your transaction confirms</p><h3>Why Both Numbers Matter</h3><p>Looking at only one number can give you an incomplete picture.</p><p>Suppose STON.fi shows:</p><p>Price Impact: 0.3%</p><p>That tells you your trade has relatively limited impact on the pool under the quoted conditions.</p><p>But you should still understand your slippage tolerance because the market can move before execution.</p><p>Now imagine the interface shows:</p><p>Price Impact: 7%</p><p>That tells you the trade itself is having a much larger effect on the available liquidity.</p><p>In both cases, the price impact tells you something about your trade.</p><p>Slippage tolerance tells you something about how much execution movement you are willing to accept.</p><p>What About Minimum Received?</p><p>Minimum Received connects these concepts to the actual transaction.</p><p>STON.fi defines Minimum Received as the lowest amount of the output token you are guaranteed to receive, taking your slippage tolerance into account. (STON.fi Help Center)</p><p>For example:</p><p>Estimated Amount: 1,000 USDT</p><p>Minimum Received: 990 USDT</p><p>The Estimated Amount is the current quote.</p><p>The Minimum Received is the lower boundary created by your slippage settings.</p><p>This is why it is useful to look at all three:</p><p>Estimated Amount</p><p>Price Impact</p><p>Minimum Received</p><p>They answer different questions.</p><h3>A Practical Way to Read the STON.fi Preview</h3><p>Before confirming a swap, you can think through the numbers in this order.</p><ol><li>Look at the Estimated Amount</li></ol><p>What does the current quote say you may receive?</p><p>2. Check Price Impact</p><p>How much is your own trade affecting the pool price?</p><p>3. Check Minimum Received</p><p>What is the lowest output allowed under your current slippage settings?</p><p>4. Review Slippage Tolerance</p><p>How much movement between the quote and execution are you allowing?</p><p>5. Review the Other Transaction Details</p><p>Check the route, fees and any warnings shown by the interface.</p><p>This gives you a much clearer picture of the swap than focusing on the headline quote alone.</p><p>One Easy Rule to Remember</p><p>If you only remember one thing from this article, remember:</p><p>Price impact is caused by your trade. Slippage is caused by changes between your quote and execution.</p><p>A large trade against a shallow pool can create high price impact.</p><p>A volatile market can create slippage even when your own trade has very little impact.</p><p>And a single swap can experience both.</p><h3>Final Thoughts</h3><p>Price impact and slippage are related, but they are not interchangeable.</p><p>Price impact tells you how much your own swap moves the price inside the liquidity pool.</p><p>Slippage describes the difference between the price you saw before confirming and the price at which the transaction actually executes.</p><p>STON.fi exposes these concepts through its swap flow so users can review execution conditions before confirming a transaction. (STON.fi Help Center)</p><p>The practical habit is simple:</p><p>Check the price impact.</p><p>Understand your slippage tolerance.</p><p>Look at the minimum received.</p><p>Then review the rest of the swap details before confirming.</p><p>Understanding these numbers does not tell you whether a trade is profitable or whether a token is safe.</p><p>It simply helps you understand what is happening to the price before and during your swap.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c09a885305c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>