Omniston — Bridge-Free Atomic Swap Execution Between TRON and TON

TBL
1

Omniston — Bridge-Free Atomic Swap Execution Between TRON and TON

Project Name: Omniston cross-chain execution layer

Project Track: pay-defi

Team: STON.fi Dev — builders of STON.fi (#1 DEX on TON) and Omniston

Requested amount: $180,000 (milestone-based)

Technical docs: Overview (Omniston) | STON.fi

Telegram:@stonfidex@stonfidex

X (Twitter):@ston_fi@ston_fi

Discord: STON.fi Portal

Website: https://ston.fi/

Contact: [email protected]

:compass: Project Overview

Project Goal: Deploy audited Omniston HTLC contracts on TRON mainnet and bootstrap a resolver network — opening the first bridge-free corridor between TRON’s ~$85B stablecoin base, TON’s Telegram-native distribution, and the EVM chains Omniston already serves

Project Demo: https://cross-chain-demo.ston.fi/

Expected Completion Date: December 2026

Current Progress (%): TBA

How is the Project Governed: DAO-governed

1. Summary

We’re requesting a milestone-based grant to deploy Omniston on TRON — creating the first atomic, HTLC-based execution corridor between TRON, TON, and the EVM chains Omniston already runs on (Base, Polygon).

Omniston is a resolver-based cross-chain execution layer that settles swaps using Hash Time-Locked Contracts (HTLCs). Assets stay native on each chain, no wrapped tokens, no custodial pool ever holds user funds. A swap either completes in full or reverts entirely.

This is not a concept. Omniston has been in development for 12+ months at over $1M of sustained investment, is live on TON, Base, and Polygon mainnet with an active resolver network and real swap volume. TRON contract development is already in progress; this grant funds the path from current work to audited TRON mainnet, with a resolver bootstrap to seed TRON liquidity.

2. Team & Traction

STON.fi Dev, founded 2022 by Slavik Baranov, Mike Fedorov, and Stanislav Bazylevich — a team with a prior working relationship across earlier technology and blockchain products.

  • Slavik Baranov (CEO & Co-Founder) — ~30 years in software development, fintech, and blockchain

  • Alexey Papirovskiy (CPO) — DeFi product architect; led Omniston protocol design

  • Andrey Fedorov (CMO/CBDO) — 20+ years in IT, marketing, and BD, including 7+ years in Web3

  • Dmitriy Malinovskiy (CFO) — 15+ years in financial strategy, compliance, and fundraising

Since launching in November 2022, the team has built STON.fi into the backbone of TON DeFi: $7B+ all-time volume, 33M+ swaps, 5.9M+ all-time swappers, #1 DEX on TON by TVL and volume.

Funding: Seed round (May 2024, CoinFund lead); $9.5M Series A (July 2025, Ribbit Capital and CoinFund lead). Additional investors include Delphi Ventures, Karatage, The Open Platform, TON Ventures, Philipp Zentner (LI.FI co-founder), Sergej Kunz and Anton Bukov (1inch co-founders).

On funding and this grant: Series A capital is allocated to core protocol development and TON ecosystem expansion. The TRON-specific integration cost — chain-specific contract work, independent audit, and resolver bootstrap — is what this grant covers. Ongoing protocol maintenance post-grant is covered by existing revenue.

LinkedIn: Slavik Baranov · Alexey Papirovskiy · Andrey Fedorov

Legal entity: StonFi Holding Ltd · Token: STON

3. The Problem

Blockchain ecosystems remain largely isolated. Liquidity, users, and applications are fragmented across chains, which limits growth for every ecosystem involved.

For TRON, the gap is specific. TRON is the largest single-chain USDT footprint — ~$85B circulating, with daily USDT volume routinely in the $20–30B range. Today, TRON ↔ TON transfers go one of two ways: through messaging-layer bridges like Stargate/LayerZero and USDT0, or through centralized routes — exchanges and services like MoonPay-powered deposits in Wallet in Telegram. Neither offers atomic settlement. The same trade-offs apply for TON’s ~100M+ Telegram Wallet users entering TRON.

Most existing solutions are bridges, and they introduce structural trade-offs: custodial pools or wrapped assets make them high-value attack targets — over $2.8B in cumulative bridge exploit losses since 2022, with another $329M+ in 2026 alone as of mid-May. UX is also fragmented: multi-step flows, unpredictable settlement, failures, and unclear outcomes.

Omniston is complementary to existing TRON cross-chain infrastructure, with a different security model. Using an RFQ-based execution model backed by HTLCs, resolvers compete to fill cross-chain orders while both parties lock assets simultaneously under a shared hashlock. The swap completes in full or reverts entirely — no custody window, no wrapped token, no intermediary holding funds.

4. The Solution — How Omniston Works

Omniston replaces bridge-based transfers with a conditional exchange between two independent blockchains, secured cryptographically.

A swap involves two roles:

  • User — submits a quote request and locks the bid-side asset on the origin chain

  • Resolver — a professional liquidity provider that competes to fill the order, commits the ask-side asset on the destination chain, and executes settlement

The mechanism rests on two cryptographic guarantees:

  • Hashlock. The protocol generates a secret and embeds its hash in the order. Both HTLCs — origin and destination — are locked under the same hash. Funds are only claimable when the secret is disclosed on-chain. The two HTLCs are cryptographically linked: one cannot settle without the other.

  • Timelock. Each HTLC defines bounded windows for withdrawal, public withdrawal, and refund. The resolver’s window expires before the user’s, so the user is never exposed to a late-funding resolver. Funds cannot be locked indefinitely.

There are only three possible outcomes, and none results in one party losing funds:

Scenario Result
Protocol discloses the secret within the public withdrawal window Both parties receive funds
Resolver fails to fund the destination HTLC User is refunded
Protocol fails to disclose the secret in window Both parties are refunded

There is no state in which one side claims while the other does not. That atomicity eliminates the class of “stuck mid-bridge” failures that bridge and messaging-layer architectures can produce.

Properties relevant to TRON’s stablecoin flows:

  • Resolver-supplied liquidity, on demand. Integrators never pre-fund or manage cross-chain inventory.

  • Partitioned execution. A 1,000 USDT swap can settle as four independent 25% sub-swaps, each with its own secret, hashlock, and timelock. Non-fill of one does not affect the others — relevant on a network that routinely processes >$20B in daily USDT volume.

  • No oracle, no messaging layer, no wrapped asset. The cross-chain link is the shared hash itself. There is no third party whose compromise breaks atomicity.

5. Why Omniston Fits TRON

Three direct contributions to the TRON ecosystem:

5.1 A native exit/entry route for TRON’s stablecoin liquidity

TRON is the largest single-chain USDT footprint at ~$85B. Omniston creates a native, non-custodial routing corridor between TRON stablecoins and TON, and — because Omniston is already live on Base and Polygon — between TRON and those EVM chains at the same launch. This is liquidity movement that currently has no native execution path; today it leaks to centralized exchanges and custodial conversion services.

5.2 New user acquisition from outside the EVM/TRON world

TRON gains a direct, frictionless entry point into Telegram’s 1B+ monthly active user base, including the 100M+ users on Wallet in Telegram — a retail-first, mobile-first audience that currently has no clean native path to TRON. Every TON user who executes a swap via Omniston is a new TRON on-chain user. These are net-new TRON users, not redirected existing ones.

5.3 Open infrastructure for TRON builders

Omniston integrates via SDK, API/RFQ endpoint, or drop-in widget. Any TRON wallet, DEX, aggregator, or DeFi app can add TRON ↔ TON and TRON ↔ EVM cross-chain swaps with a single integration — no bridge infrastructure to operate, no resolver liquidity to manage, no cross-chain settlement logic to build.

Built-in monetization for TRON dApps. Omniston’s two-layer fee model lets integrators set a custom fee (0.01–100 bps), embedded in the quoted price and paid out automatically at settlement. A TRON wallet or DeFi frontend earns revenue on cross-chain volume without operating liquidity or bridge infrastructure — a revenue primitive most cross-chain protocols don’t offer integrators.

Competitive context

Category Examples How Omniston differs
Bridge apps / LayerZero-based solutions Stargate, LayerZero ecosystem apps HTLC-based atomic settlement: no custody, no wrapping, full execution or refund.
Cross-chain aggregators CoW Swap, Symbiosis Cross-chain routing with native TON liquidity access and support for TON ↔ TRON / EVM flows.
Intent / RFQ protocols 1inch Fusion+, UniswapX, NEAR Intents RFQ / intent-based execution extended cross-chain across TON, TRON, and EVM.
Custodial swap services Changelly Non-custodial execution enforced by smart contracts, without a centralized swap operator.
TON liquidity access -– Aggregates STON.fi, TON DEX liquidity, and resolvers into one execution layer.

6. Roadmap, Milestones & Budget

Total requested budget: $180,000 Program duration: 24 weeks

MILESTONE 1 — TRON Testnet Enablement

Type: Technical readiness · Timeline: Weeks 1–4 · Budget: $40,000

Scope: Complete and validate the TRON-native Omniston settlement contract on TRON testnet. Confirm TRON-specific deployment parameters, contract configuration, resolver interaction, event indexing, and timeout/refund assumptions work correctly in the Omniston cross-chain flow.

Deliverables:

  • TRON testnet deployment completed

  • Public testnet contract addresses

  • Representative testnet transaction hashes for successful execution and timeout/refund flows

  • Deployment notes covering tested flows, known constraints, and mainnet readiness status

Success criteria:

  • TON → TRON and TRON → TON testnet flows validated

  • TRON-side timeout/refund behavior validated

  • Event indexing and monitoring requirements confirmed

  • No TRON-specific blockers identified for audit coverage or mainnet deployment

MILESTONE 2 — Security Review and Audit Coverage

Type: Security · Timeline: Weeks 3–8 (partial overlap with M1) · Budget: $60,000

Scope: Commission an independent third-party audit of the TRON-native Omniston settlement contract. The review covers escrow logic, hashlock/timelock behavior, refund paths, resolver interaction model, factory/deployment pattern, and access control as implemented for TRON.

Deliverables:

  • Third-party audit report published or shared according to audit disclosure policy

  • TRON deployment assumptions included in the reviewed scope

  • Remediated code version referenced in release/deployment notes

  • Summary of resolved critical and high-severity findings, if any

Success criteria:

  • Audit completed before TRON mainnet launch

  • No unresolved critical or high-severity findings affecting TRON deployment

  • Final mainnet deployment uses the audited/remediated contract version

MILESTONE 3 — TRON Mainnet Launch and Developer Enablement

Type: Launch + developer integration · Timeline: Weeks 8–12 · Budget: $30,000

Scope: Deploy audited TRON-native Omniston settlement contracts to mainnet and enable TRON routes in Omniston SDK/API infrastructure. Supported routes at launch include TON ↔ TRON and EVM ↔ TRON swaps (Omniston already runs on Base and Polygon), initially focused on stablecoin routes.

Deliverables:

  • TRON mainnet contract addresses

  • Production deployment with chain configuration and supported initial routes

  • Representative transaction hashes for TON ↔ TRON and EVM ↔ TRON swaps

  • Updated Omniston SDK/API support for TRON routes

  • Updated RFQ/API documentation

  • Example integration request or integration guide

  • Reporting view for TRON route activity

Success criteria:

  • TRON mainnet contracts deployed

  • Controlled live swaps completed successfully in both directions where supported

  • SDK/API can quote and initiate TRON routes

  • At least one STON.fi-owned or partner-facing integration environment can initiate TRON routes through Omniston

MILESTONE 4 — Partner and Ecosystem Integration Support

Type: Ecosystem adoption · Timeline: Weeks 12–24 · Budget: $15,000

Scope: Support TRON ecosystem partners integrating Omniston routes through SDK, API, or widget. Target partners include wallets, aggregators, trading apps, DeFi frontends, and cross-chain applications. Support includes integration guidance, troubleshooting, route testing, reusable documentation, and partner-specific launch assistance.

Deliverables:

  • Minimum 2 supported partner integration pilots

  • At least 1 production-ready or live integration by the end of the grant period

  • Partner integration guide or reusable integration notes

Success criteria:

  • At least one partner or partner-facing integration can initiate TRON routes through Omniston

  • Integration status is verifiable through public demo, production environment, transaction activity, or partner confirmation

  • Reusable integration learnings documented for future TRON ecosystem partners

MILESTONE 5 — TRON Resolver Bootstrap

Type: Liquidity infrastructure · Timeline: Weeks 12–24 · Budget: $30,000

Scope: Bootstrap TRON resolver participation for Omniston routes (TON ↔ TRON and EVM ↔ TRON). Incentivize active resolvers based on measurable production performance: successful execution of accepted quotes, executed volume, response reliability, settlement latency. Initial scope is limited to stablecoin routes to reduce complexity and improve execution reliability.

Definition of active resolver: Configured for TRON routes, completed production validation, and quoted or executed eligible TRON route activity during the reporting period.

Deliverables:

  • Minimum 1 active TRON resolver by Week 20

  • Monthly swap performance reports

  • Documentation of resolver onboarding process for future participants

Success criteria:

  • Stablecoin TRON routes supported by active resolvers

  • Report metrics published through the end of the grant period

Note: Initial scope focuses on stablecoin routes. Non-stablecoin routes may be added in a later phase based on resolver readiness, route demand, liquidity conditions, and risk controls.

MILESTONE 6 — Analytics, Monitoring, and Grant Reporting

Type: Transparency + reporting · Timeline: Ongoing throughout grant period · Budget: $5,000

Scope: Maintain public analytics for TRON route activity, publish regular progress updates, and provide a final closeout report covering milestone completion, deployment status, resolver activity, partner integration progress, usage metrics, and post-grant sustainability.

Deliverables:

  • Public analytics dashboard or equivalent reporting view

  • Final closeout report within 2 weeks after program completion

  • Metrics covering TRON route swap count, executed volume, supported assets/routes, unique wallets where measurable

Success criteria:

  • Public reporting accessible through the grant period

  • On-chain activity metrics verifiable through transactions, contract events, or public dashboards

  • Final report published on schedule with milestone status, usage metrics, and post-grant sustainability plan

Budget summary

Milestone Focus Timeline Budget
1 TRON testnet validation Weeks 1–4 $40,000
2 Security review & audit Weeks 3–8 $60,000
3 Mainnet launch & dev enablement Weeks 8–12 $30,000
4 Partner integration support Weeks 12–24 $15,000
5 Resolver bootstrap Weeks 12–24 $30,000
6 Analytics & reporting Ongoing $5,000
7 Total 24 weeks $180,000

7. KPIs & Sustainability

Reported publicly through the grant period:

  • Deployment: TRON testnet + audited mainnet contracts live, addresses public

  • Security: Independent audit completed before mainnet; no unresolved critical/high findings

  • Liquidity: ≥2 active TRON resolvers by Week 20, supporting stablecoin routes

  • Integrations: ≥3 partner integration pilots; ≥2 production/live integrations by grant end

  • Usage (measurable on-chain): TON ↔ TRON and EVM ↔ TRON swap count, executed volume, supported routes, unique wallets where measurable

  • Transparency: Public dashboard maintained; final closeout report delivered on schedule

We’ve intentionally avoided projecting specific volume or wallet targets without baseline data on TRON, but reported metrics will be verifiable on-chain.

Post-grant sustainability. Omniston’s economics are pull-based: resolvers compete for fee revenue, integrators earn embedded fees on cross-chain volume, and the protocol generates revenue at settlement. Once resolvers and integrations are bootstrapped, the system grows on its own incentives — the grant covers ramp, not ongoing operation. Protocol maintenance and developer support for TRON routes are covered by STON.fi’s existing revenue post-grant.

8. Why Now & Next Steps

TRON’s stablecoin position is consolidating: USDT supply on TRON crossed $85B in 2026, the largest single-chain USDT footprint. TON’s Telegram-native user base remains one of the few large pools of fresh, mobile-first retail users in Web3, and cross-chain demand between the two is already real — served today by custodial and centralized routes. Omniston is production infrastructure, live on TON, Base, and Polygon, with TRON contract development already underway.

This grant funds the path from current work to audited TRON mainnet with bootstrapped resolver liquidity — giving the TRON ecosystem first-corridor access to TON liquidity and distribution, and to Omniston’s existing EVM routes, on native non-custodial rails.

We’re happy to answer questions from the community and the review team directly in this thread, and to schedule a technical walkthrough with the grants committee if useful.

2 Likes