DEV Community

Cover image for Ecosystem Map: How STON.fi, Omniston, and xStocks Connect on TON
Web3KD
Web3KD

Posted on

Ecosystem Map: How STON.fi, Omniston, and xStocks Connect on TON

#webdev #programming #ai #web3

Ecosystem Map: How STON.fi, Omniston, and xStocks Connect on TON

Three names get mentioned together constantly in TON DeFi conversations, and it's easy to assume they're roughly interchangeable — different marketing terms for the same underlying thing. They're not. Each one is a genuinely distinct layer, and understanding where one ends and the next begins is the difference between a surface-level impression of "TON has DeFi and stocks now" and actually understanding the architecture connecting them.

🗨️ "STON.fi technically integrates the last step. It does not issue the product, does not hold the legacy instruments, and does not run the custody; it surfaces the on-chain jetton and routes swaps around it." — STON.fi Blog, "How xStocks Actually Work"

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔

🌐 Three Layers, Three Different Jobs

  • 🎫 STON.fi is the trading surface — the AMM, the app, the interface where swaps, liquidity provision, farming, and staking actually happen
  • 🏷️ Omniston is the routing and liquidity-sourcing layer underneath STON.fi — it decides where a trade actually gets filled, whether that's a public pool, another DEX, or private resolver liquidity
  • 🪧 xStocks is an asset category, not a protocol at all — tokenized real-world equities that happen to be tradeable through STON.fi, routed by Omniston, but issued and backed by an entirely separate, regulated entity

The relationship isn't three peers. It's a stack: an asset class (xStocks) flows through a routing engine (Omniston) that surfaces inside a trading interface (STON.fi). Each layer can be understood independently, but the interesting part is exactly where they connect.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔

Where xStocks Actually Come From Before They Ever Reach TON

It's tempting to think of an xStock as something STON.fi created. It didn't — and tracing the actual path clarifies what STON.fi's role really is.

🗨️ "Traditional asset → regulated product → bToken on an origin chain → wrapped representation on TON → xStock jetton you see in your wallet." — STON.fi Blog

xStocks are issued by Backed Finance, a regulated entity that holds the actual underlying equities — real shares of Apple, Tesla, Nvidia, and others — through licensed custodians. Backed mints a blockchain-native representation of that holding, originally on an EVM chain, which then gets wrapped into a TON-native jetton. By the time an xStock shows up as AAPLx or TSLAx in a TON wallet, it's already passed through several steps of regulated tokenization that have nothing to do with STON.fi at all. STON.fi's actual job starts at the very last step: making that jetton tradeable.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔

🧬 How Omniston Specifically Had to Adapt for xStocks

This is the part that actually reveals how these layers connect technically, not just conceptually.

🗨️ "The harder challenge was liquidity: unlike established crypto pairs, xStocks don't yet have deep AMM pools across pairs. Technically, AMM support is there. But we also introduced an additional execution path — escrow swaps — so users can access deeper liquidity. Today, most xStocks volume executes through escrow." — Fedorov, STON.fi team, via BeInCrypto

xStocks behave like any other TON jetton technically, but they don't yet have the deep, organic AMM liquidity that established crypto pairs have built up over time. Omniston's answer wasn't to force xStocks trades through thin public pools — it was to lean on escrow swaps, the same private-resolver liquidity mechanism built to solve liquidity gaps generally, now handling the majority of actual xStocks trading volume. This is a concrete example of one layer (Omniston) adapting specifically to support a new asset category (xStocks) surfacing through the trading layer (STON.fi) — the connection isn't abstract, it's a real routing decision happening on real trades.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔

🏦 The Full Map, Layer by Layer

🪙 Issuance and custody — outside the TON stack entirely Backed Finance holds the actual underlying equities through regulated custodians and mints the tokenized representation. Kraken provides institutional validation. Neither of these entities is part of STON.fi or Omniston — they're the foundation the whole thing rests on, sitting entirely outside TON's technical stack.

🧾 Token standard — where regulation meets on-chain mechanics xStocks follow the TON jetton standard for basic transfers and wallet compatibility, but specifically use Scaled UI Jettons (TEP-526) — a standard that lets a token's displayed balance reflect a scaling factor over time, used here to represent accumulated dividend value without STON.fi itself distributing any dividends directly.

🎫 STON.fi — the trading surface A dedicated page at ston.fi/xstocks lets eligible users swap TON or USDT directly for xStocks like AAPLx, TSLAx, NVDAx, GOOGLx, AMZNx, and broader index exposure. Once acquired, xStocks behave like any other jetton — they can be held, used in other TON DeFi applications, or provided as liquidity.

🏷️ Omniston — the routing decision underneath every xStocks trade Because AMM depth for xStocks pairs is still thin, Omniston evaluates both public pool liquidity and private resolver-priced liquidity for every xStocks trade, routing through whichever actually delivers a better realized price — which in practice means escrow swaps carry most of the real volume today.

🪧 Wallets and Telegram — the distribution layer on top of all of it Because xStocks comply with the jetton standard, they're automatically recognized by TON-native wallets — TON Wallet, Tonkeeper, MyTONWallet — including the wallet built directly into Telegram, meaning the full stack described above ultimately surfaces inside an app hundreds of millions of people already have open daily.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔

🧑‍💻 What the Connection Between These Layers Actually Looks Like in Code

Since the interesting part of this map is a real routing decision, not just a diagram, it's worth seeing what that decision looks like from a developer's side. The snippets below are illustrative, written in the style of STON.fi's documented SDK patterns.

Requesting a quote for an xStock behaves identically to any other jetton — the trading surface (STON.fi) doesn't need special-case code, because the asset category difference is invisible at this layer:

import { Omniston, blockchain, settlementMethod } from '@ston-fi/omniston-sdk';

const omniston = new Omniston({ apiUrl: 'wss://omni-ws.ston.fi' });

const { rfqId } = await omniston.requestQuote({
  quoteRequest: {
    offerAsset: { blockchain: blockchain.Ton, address: 'EQC...usdt_jetton' },
    askAsset: { blockchain: blockchain.Ton, address: 'EQC...aaplx_jetton' }, // an xStock
    amount: { offerAmount: '500000000' },
    settlementMethods: [settlementMethod.Swap],
  },
});
Enter fullscreen mode Exit fullscreen mode

Where the layers actually diverge is inside the quote response itself — this is the concrete, code-level evidence of Omniston's routing adaptation for thin-liquidity assets like xStocks:

omniston.trackQuote({ rfqId }).subscribe((event) => {
  if (event.type === 'quoteUpdated') {
    console.log('Settlement source:', event.quote.settlementSource);
    // For an established crypto pair, this is often 'amm_pool'
    // For most xStocks pairs today, this commonly resolves to 'escrow_resolver'
  }
});
Enter fullscreen mode Exit fullscreen mode

Detecting the TEP-526 scaling factor on an xStock jetton, relevant if a wallet or app wants to display accumulated dividend value correctly rather than a raw balance:

async function getDisplayBalance(jettonWalletAddress: string) {
  const jettonData = await client.runMethod(jettonWalletAddress, 'get_wallet_data');
  const rawBalance = jettonData.balance;
  const scalingFactor = jettonData.scalingFactor ?? 1; // TEP-526, defaults to 1 for non-scaled jettons

  return rawBalance * scalingFactor; // what the user should actually see
}
Enter fullscreen mode Exit fullscreen mode

Nothing in the first snippet knows or cares that it's trading an xStock — that's the point. The routing and scaling differences live entirely inside Omniston's decision logic and the token's own metadata, not in application-level branching a developer has to write themselves.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔

🌐 Comparing on the Dimensions That Actually Matter

💧 What STON.fi controls vs. what it doesn't. STON.fi controls the trading interface and the on-chain swap mechanics. It doesn't control issuance, custody, regulatory compliance, or the underlying equity itself — that entire layer belongs to Backed Finance, independently of anything happening on TON.

🧭 Crypto-native pairs vs. xStocks pairs, at the routing level. A deep, established crypto pair might resolve almost entirely through public AMM pools. An xStocks pair, at least currently, resolves mostly through escrow — a genuinely different routing outcome for a genuinely different liquidity situation, decided automatically by the same underlying Omniston logic.

⏱️ Traditional market hours vs. on-chain availability. Once tokenized, an xStock trades whenever TON itself is live — 24/7, independent of when the underlying equity's home exchange is actually open, which is a structural difference from the asset it represents, not just a convenience feature.

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔

✅ What Genuinely Connects These Three Layers

  1. A shared token standard, not shared ownership. xStocks work inside STON.fi because they follow TON's jetton standard, not because STON.fi issues or controls them in any way.
  2. Omniston adapting its routing logic for a new asset category. The rise in escrow-swap usage for xStocks is a direct, measurable consequence of a new asset type surfacing through the existing routing engine.
  3. Wallet-level recognition tying the whole stack to actual distribution. Because of jetton-standard compliance, the entire chain — from regulated custody to a TON swap — ends up one tap away inside apps people already use daily, including Telegram.

⚠️ What's Worth Understanding Correctly

  • STON.fi is not the issuer of xStocks, and doesn't hold the underlying equities. That responsibility sits entirely with Backed Finance and its regulated custodians.
  • Most xStocks liquidity today runs through escrow, not public AMM pools. This is a current state of a growing asset category, not a permanent architectural limitation.
  • xStocks are not available to all users. Eligibility restrictions apply, and prospective users should check current terms directly rather than assume universal access.

🏁 Bottom Line

STON.fi, Omniston, and xStocks aren't three versions of the same thing — they're three layers of one connected stack, each doing a genuinely different job. Backed Finance and its custodians handle issuance and regulatory backing, entirely outside TON. Omniston handles the routing decision for every trade, adapting its own liquidity strategy specifically because xStocks arrived with a different liquidity profile than crypto-native pairs. STON.fi surfaces all of it as an actual tradeable interface, one that jetton-standard compliance then makes visible inside wallets — including Telegram's — that people already have open. Understanding the map means understanding that "STON.fi has stocks now" is really shorthand for a much more layered, cross-entity system working together underneath one interface.

🔗 Sources & Further Reading

This article reflects independent research based on STON.fi's and TON's public documentation and announcements as of mid-2026. Asset availability, eligibility requirements, and routing behavior evolve as the ecosystem grows — always verify current details directly on ston.fi and docs.ston.fi before making decisions involving real funds.

Top comments (0)