[2601 Grant] SwaptoX Aggregator – Milestone 1

Grants & Incentives
1

Project Name & Description

Project Name: SwaptoX Aggregator

Description:
SwaptoX is a decentralized swap aggregator designed to provide optimal swap routing across multiple liquidity sources, with strong support for long-tail tokens and precise pricing logic. The project has been live and production-deployed on Base for over four months, supporting 600+ tokens, and has undergone extensive real-world testing.

SwaptoX is built as general-purpose DeFi infrastructure, enabling wallets, DApps, bots, and future BTCFi applications to integrate swap functionality via SDKs and APIs, rather than relying on heavy router contracts or centralized services.

Team Background

SwaptoX is fully developed by a solo independent Web3 developer.

  • Over 1 year of continuous full-stack Web3 development

  • Built everything from scratch:

    • Smart contracts

    • Routing & pricing engine

    • UI / frontend

    • Token-to-USD pricing infrastructure

  • Over the past 6+ months, tens of thousands of swap simulations and real transactions have been executed and verified to ensure:

    • Routing correctness

    • Execution safety

    • Contract stability

This is not a prototype-stage project, but a battle-tested system already running in production.

Total Grant Amount

  • Total Grant Requested: $15,000

  • Milestone 1 Request: $5,000

Milestone 1 – SwaptoX Deployment on Rootstock

Objective

Deploy SwaptoX as a native swap aggregation infrastructure on the Rootstock network.

Deliverables (KPIs)

  • Deploy SwaptoX core contracts on Rootstock mainnet

  • Integrate Rootstock-native tokens and liquidity pools

  • Ensure accurate routing, quoting, and execution

  • Publicly accessible swap UI connected to Rootstock

  • At least 30+ supported tokens in initial deployment

Requested Support

$5,000

Milestone 2 – Swap Mini SDK for Rootstock Ecosystem

Objective

Lower the integration barrier for Rootstock ecosystem projects by providing a lightweight Swap SDK.

Deliverables (KPIs)

  • Develop a Swap Mini SDK for:

    • Websites

    • DApps

    • Wallet extensions

  • SDK supports:

    • Route discovery

    • Price quoting

    • Swap execution helpers

  • Example integration demo for Rootstock

Requested Support

$5,000

Milestone 3 – Public API & Developer Documentation

Objective

Enable advanced integrations such as trading bots, analytics platforms, and BTCFi derivatives.

Deliverables (KPIs)

  • Public APIs for:

    • Swap quotes

    • Route discovery

    • Token USD pricing

  • Full technical documentation:

    • API reference

    • SDK usage

    • Integration examples

  • Ready for third-party usage

Requested Support

$5,000

Timeline

Month Milestone
Month 1 Milestone 1 – Rootstock deployment
Month 2 Milestone 2 – Swap Mini SDK
Month 3 Milestone 3 – Public API & Docs

Technical Specs

  • Architecture: Modular swap aggregator

  • Routing: 1–3 hop optimal path discovery

  • Pricing: Precise pricing engine, including fee-on-transfer token handling

  • Contracts: Custom-built (no dependency on heavy routers)

  • Frontend: Lightweight, responsive UI

  • Infrastructure: Independent token-to-USD pricing system (on-chain + off-chain mapping)

Value Proposition for Rootstock

Rootstock currently lacks a general-purpose, developer-friendly swap aggregation infrastructure.

SwaptoX provides Rootstock with:

  • A production-ready swap aggregator

  • SDKs that reduce development costs for ecosystem projects

  • APIs enabling BTCFi derivatives, bots, and advanced DeFi use cases

  • A long-term infrastructure component, not a short-lived DApp

This directly strengthens Rootstock’s BTCFi and DeFi composability with minimal upfront ecosystem cost.

Demo & project

Closing

SwaptoX is already a functioning, production-deployed swap aggregator that has proven its technical feasibility over months of real usage. With Rootstock’s support, SwaptoX can become a native BTCFi infrastructure component, enabling faster ecosystem growth and easier DeFi integration for future builders.

3 Likes
Rootstock Collective Governance-at-a-Glance 26-01-29
2

Hi @SwaptoX I have a few questions and would appreciate some additional clarity on your proposal:

  1. Which Rootstock-native tokens and liquidity pools are you envisioning supporting initially?
  2. Have you evaluated the existing DEXs that already support Rootstock swaps? If so, what would meaningfully differentiate your approach from what’s currently available?
  3. When you reference supporting 30+ tokens at initial deployment, which specific assets are you referring to?
  4. Which websites and dApps are you proposing to target with the mini-SDK, and what criteria are you using to select them?

Looking forward to your responses.

3 Likes
3

Hi @axia , thanks for the questions. I’m happy to clarify.

1. Initial tokens and liquidity pools on Rootstock

Based on my observation of the current Rootstock ecosystem, there is meaningful liquidity on WoodSwap and Sushi. Across these two DEXs, there are roughly ~30 active tokens, which would be the initial scope for SwaptoX integration.

Relevant references:

From a user perspective, swapping through an aggregator can theoretically produce better outputs than swapping directly on a single DEX, because a DEX routes only through its own liquidity, while an aggregator evaluates liquidity across the entire chain and multiple paths.

2. Existing swap solutions and differentiation

I also noticed CrowdSwap in the Rootstock ecosystem. However, it is unclear whether CrowdSwap functions as a true on-chain swap aggregator or primarily as a bridge-based solution.
Even on mature chains like Base, CrowdSwap only exposes around 20 tokens, which suggests its focus may not be deep on-chain liquidity aggregation.

In contrast, SwaptoX is purpose-built to optimize swap output. On Base, we currently support 600+ tokens, and the project originated from an arbitrage system, which shaped our routing logic.

Our swap process includes:

  • Collecting liquidity across all available pools

  • Sorting and filtering liquidity pairs

  • DFS-based search across all possible closed-loop paths

  • Batch price quotation to identify the best achievable output

This is why, in practice, swapping through SwaptoX can outperform direct swaps on individual DEXs.

3. “30+ tokens” at initial deployment

The “30+ tokens” refers specifically to the assets currently available through WoodSwap and Sushi on Rootstock, as listed in the pool links above. These would form the initial supported token set at launch.

4. Mini-SDK targets and use case

The Mini-SDK is designed for DEXs, dApps, and applications that already have user traffic but lack native swap logic.

For example:
If a dApp’s primary token is USDT, but a user only holds ETH, the typical flow today is to redirect the user to WoodSwap or Sushi to manually swap ETH → USDT.

By integrating the SwaptoX Mini-SDK, the dApp can enable this swap directly within its own interface, without sending users away, improving both UX and conversion.

Finally, if SwaptoX is integrated on Rootstock, we are committed to offering at least one year of free usage for Rootstock users, including Swap functionality, Mini-SDK, and API access.

1 Like
4

@axia Test video: https://youtu.be/g7lfSBdg3Ws

I shared a simple comparison video: SwaptoX vs Uniswap and SwaptoX vs KyberSwap.
From this test, two observations can be made:

  1. In most cases, using a swap aggregator can produce better outputs than swapping directly on a single liquidity DEX. This is the fundamental reason why platforms benefit from having an aggregator layer.

  2. Based on observed results, the gap between SwaptoX’s arbitrage-based routing logic and a mature aggregator like KyberSwap is relatively small, which highlights SwaptoX’s cost-effectiveness as an infrastructure solution.

1 Like
5

Hi @SwaptoX, thanks for the proposal and for engaging in the discussion, really appreciate the detailed context you’ve shared so far.

From a reviewer perspective, the idea of adding more aggregation and developer tooling to Rootstock is interesting, and the work you describe on other EVM networks provides helpful background. That said, there are a few areas where some additional clarification would go a long way in helping the community assess the incremental value of this grant.

In particular, it would be very helpful to better understand how SwaptoX differentiates itself within the current Rootstock landscape:

  • How would you position SwaptoX relative to existing DEX aggregation infrastructure already active on Rootstock (e.g. OpenOcean), especially in terms of routing quality, supported liquidity, developer experience, or architectural approach?

  • Are there specific measurable advantages (better quotes, lower gas, broader token coverage, simpler SDK/API, open-source components, etc.) that you could highlight or benchmark on Rootstock pairs?

  • From a builder’s point of view, why should a dApp or wallet on Rootstock choose to integrate SwaptoX instead of existing aggregation solutions today?

Additionally, a few clarifications on verifiability would help reviewers a lot:

  • Is there a public repository or set of links where the core contracts, routing logic, or UI can be reviewed?

  • Are there verified contract addresses or example transactions from your current deployments that could be shared?

  • Would you be open to outlining more concrete, verifiable acceptance criteria for Milestone 1 (e.g. deployed and verified contracts, supported pools/tokens, example swaps on mainnet)?

Clarifying these points would make it much easier to evaluate whether Milestone 1 represents incremental value for Rootstock at this stage. Thanks again for the submission, and looking forward to learning more.

4 Likes
6

@kaf_stablelab
Thank you for the thoughtful questions — happy to clarify in more concrete terms.

Positioning vs existing aggregation on Rootstock

I did not initially encounter OpenOcean as a visible, native part of the Rootstock ecosystem UI-wise. That said, I do acknowledge that OpenOcean officially lists Rootstock support on its website, even if it is not prominently surfaced without manual search.

From a positioning perspective, SwaptoX differentiates itself primarily through depth of routing, token coverage, and system architecture:

  • On Base, SwaptoX currently supports 600+ tokens, whereas OpenOcean supports ~100+ tokens on the same network.
    Broader token and liquidity coverage enables deeper routing exploration, but also significantly increases system complexity and maintenance cost.

  • SwaptoX originated as an on-chain arbitrage system, not as a UI-first aggregator.
    As a result, the routing engine is designed to:

    • collect and rank liquidity across pools,

    • perform DFS-based path discovery,

    • batch-query multiple 1–3 hop routes,

    • and select the path with the highest net output.

  • We also support tax / fee-on-transfer tokens, which many aggregators deliberately exclude due to quote accuracy challenges.

  • * The Core Challenges of Developing a Swap Aggregator

  • Gas efficiency is part of the routing decision: SwaptoX evaluates output minus gas cost, which is a necessity in arbitrage-driven systems.

Because of this background, I am confident in the system’s ability to produce competitive quotes.
That said, I want to be very clear and honest: no serious aggregator can guarantee “always better quotes”, as liquidity and on-chain state change constantly.

Why integrate SwaptoX instead of existing solutions

From a builder or wallet perspective, SwaptoX offers:

  • Broader token coverage and deeper routing logic

  • Support for complex tokens (tax tokens)

  • A focus on net output optimization (including gas)

  • A lightweight, plug-and-play Mini SDK, designed to be easy to integrate

The SDK will support React, Vue, and Vanilla JS, allowing dApps to embed swap functionality directly without redirecting users to external DEX UIs.

Open-source and verifiability

SwaptoX is composed of multiple components: frontend, backend, databases, pricing systems, routing logic, and off-chain bots (e.g. liquidity ranking, USD price discovery).
Some of these elements — particularly deep routing and pricing logic — are core competitive components and therefore cannot be fully open-sourced.

However, we are committed to:

  • Open-sourcing the Mini SDK

  • Open-sourcing the swap routing / execution contracts

Example contract (Base):
https://basescan.org/address/0xde6a22861fec6f37ae10a6a88cf2a645eb7094ca

Milestone 1 clarification

Milestone 1 represents a fully verifiable outcome:

  • Full deployment of SwaptoX core logic on Rootstock mainnet

  • Live, user-accessible swap UI

  • Initial integration of all available liquidity from WoodSwap and Sushi

  • Example mainnet swaps available for verification

I hope this clarifies the incremental value and concrete scope of Milestone 1.
Happy to further refine acceptance criteria if helpful.

1 Like
7

In addition, SwaptoX places strong emphasis on user experience.
From the very first version, we delivered a clean, responsive UI with multi-language support, as well as light and dark themes.

The Mini-SDK will follow the same design principles, providing a responsive, end-user–friendly interface with multi-language and multi-theme support for seamless integration into dApps and wallets.

1 Like
8

Thanks for the proposal. I can see SwaptoX is targeting an infrastructure-first gap in the Rootstock ecosystem, and it has been live on Base for over 4 months helps reduce execution risk.

I do have a few concerns I’d like to better understand. Since SwaptoX is built by a solo developer, there is some risk around burnout and long term maintenance. If the developer becomes inactive or shifts focus, is there any fallback plan for Rootstock?

You also mentioned that SwaptoX supports 600+ tokens on Base compared to ~100+ on OpenOcean. Could you share more context on how many of those tokens actually have meaningful liquidity, and how many are used in real routing paths today?

Also I’d like to hear more about your plans after the grant period ends. Do you intend to continue prioritizing Rootstock long term, or is this deployment mainly part of a broader multi chain expansion?

Thanks for the clarifications so far.

1 Like
9

Thanks for the proposal @SwaptoX it’s great to see a production-ready dapp being brought to Rootstock. We have a couple of questions:

Has SwaptoX undergone any third-party audits before?

What is the intended long-term sustainability model for SwaptoX?

One suggestion would be to redefine a milestone to focus on proving adoption, such as the target volume you envision and the number of DEX integrations using SwaptoX infrastructure.

1 Like
10

Hi @ignas ,
thank you for the thoughtful questions — they are all very valid, and I’ll answer them candidly.

On being a solo developer and long-term maintenance

SwaptoX is not a short-term experiment for me. The initial development alone took over six months, and the project represents a significant long-term commitment rather than a side effort.
At the current stage, being a solo builder also means lower operational and maintenance overhead, which actually reduces short-term sustainability risk.

That said, the plan is not to remain solo indefinitely. After the product matures and stabilizes, the intention is to begin forming a small team in the second half of 2026 to support long-term maintenance and growth.

On supporting 600+ tokens on Base

SwaptoX originated from an on-chain arbitrage system. To discover profitable and optimal routes, the system was designed to observe and index a broad set of tokens and liquidity sources rather than a curated subset only.

While not all 600+ tokens have deep liquidity, they are not simply “listed tokens.” Many are used as intermediate routing candidates, especially for multi-hop paths.
At the moment, exact liquidity statistics are not yet publicly exposed in the UI. However, this is already part of our internal roadmap: we are building an extended admin system and a third monitoring bot (in addition to liquidity ranking and USD pricing bots) that tracks pool balances and liquidity depth. This will allow the frontend to transparently display pool sizes, market caps, and routing relevance.

On plans after the grant period

There is no aggressive multi-chain expansion plan at this stage.
First, the product itself still requires several months of refinement before it is truly market-ready.
Second, given limited resources, deploying to many chains without proper focus or user adoption does not create meaningful value.

If supported, Rootstock would not be treated as a short-term deployment. The intention would be to continue building and operating on Rootstock after the grant period, grow real usage, and only then consider broader multi-chain expansion from a more stable foundation.

Thanks again for the constructive discussion — happy to clarify further if needed.

11

Hi @SwaptoX. We appreciate the detailed proposal and the clear articulation of the technical achievements and roadmap. The project’s production history on Base and its focus on infrastructure-first integration for Rootstock are compelling. However, we have a few critical issues that need further discussion to ensure the grant delivers sustainable value to the ecosystem.

While SwaptoX’s ability to route across 600+ tokens on Base is impressive, how many of these tokens have meaningful liquidity and are actively used in real routing paths? As @Ignas noted, the value of broad token coverage is limited if most tokens are illiquid or rarely utilized. Could you provide data or analysis on token liquidity distribution and actual routing usage, both on Base and projected for Rootstock? We haven’t found any verifiable and public data on DefiLlama either.

The competitive landscape on Rootstock already includes aggregators like OpenOcean and Oku. While you’ve outlined some differentiation in routing depth and token coverage, what concrete user or developer outcomes have you observed on Base that would not be achievable with existing solutions on Rootstock? How do you plan to drive adoption and ensure SwaptoX becomes a core part of the Rootstock DeFi stack, rather than duplicating existing efforts?

1 Like
12

Hi @curia , thank you for the questions — happy to clarify.

On third-party audits

SwaptoX has not yet undergone a formal third-party audit. The main reason is simply resource constraints at the current stage.
That said, SwaptoX does not custody user funds. It functions purely as a routing and execution layer, and transactions revert automatically if minimum output conditions are not met.

A third-party audit is planned as part of the next phase once funding becomes available, and this is considered a priority item in the longer-term roadmap rather than something being ignored.

On long-term sustainability

SwaptoX is designed as an infrastructure-first product with a clear revenue model.

The core sustainability mechanism is protocol-level swap fees, which scale naturally with usage. To support this, we actively invest in developer-facing tooling such as SDKs and APIs to increase integration surface and transaction volume.

In addition:

  • The SDK follows a freemium model (free usage with attribution, paid version without branding).

  • The API is free for low-volume usage and paid for high-frequency or bot-based usage.

  • Over time, additional products such as trading tools and derivative-oriented features are planned to further drive swap volume.

The goal is to build a sustainable, usage-driven model rather than relying on ongoing grants.

On redefining a milestone around adoption

I agree that proving adoption is important. I believe the first three milestones (migration, SDK, API & documentation) are all foundational and necessary to make SwaptoX usable by both users and developers.

That said, I am open to defining an additional milestone focused specifically on adoption and real usage, for example:

Milestone 4 – Initial Adoption & Usage Validation (1 month)
Deliverables could include:

  • Integration of SwaptoX SDK by 3–5 Rootstock-based dApps or interfaces

  • Publicly verifiable on-chain swap activity on Rootstock

  • A measurable target range for transaction count and active users

  • Transparent reporting of contracts, integrations, and example transactions

I am very open to feedback from the community on how best to define this milestone in a way that aligns with Rootstock’s governance expectations and avoids artificial or non-organic activity.

13

@tane thanks for the questions — happy to clarify briefly.

On Oku vs SwaptoX / OpenOcean:
Oku is best described as an aggregator of aggregators. It routes through existing aggregation layers such as OpenOcean or Uniswap interfaces, rather than integrating underlying DEX liquidity itself. OpenOcean and SwaptoX operate at the liquidity aggregation layer. From an ecosystem perspective, Oku could integrate SwaptoX as a routing source, while SwaptoX focuses on maintaining and optimizing direct liquidity integrations.

On the 600+ token coverage:
It’s true that many long-tail tokens have low liquidity and are not used as routing intermediates. However, supporting them still matters for users who need direct access to less common assets. SwaptoX intentionally maintains broader token coverage to provide more entry/exit options, rather than curating only high-volume tokens. Larger aggregators often drop long-tail assets due to brand reputation risks, while SwaptoX’s arbitrage-driven architecture is designed to continuously monitor and support them when liquidity exists.

This is less about inflating token counts, and more about maximizing user choice and future extensibility as ecosystems evolve.

14

Just to clarify one nuance from my previous message:

Large aggregators usually don’t avoid long-tail tokens due to pure maintenance cost, but rather due to listing policies, brand risk, and stricter token review processes. As a result, support for less common or early-stage tokens is often slower or more selective.

SwaptoX takes a different approach: the routing system originated from an arbitrage engine and is designed to monitor and include long-tail assets when on-chain liquidity exists, even if those assets are not widely listed elsewhere. This provides users with additional optionality rather than replacing mainstream routes.

15

Thanks @SwaptoX. Is the dApp currently only in Chinese? If so, do you have plans to translate it to English?

16

@axia ：
No. From the initial launch, SwaptoX has supported multiple languages. Currently, the dApp is available in Chinese, English, Korean, and Japanese, and it also supports both light and dark themes. We plan to add support for additional languages in the future.

屏幕截图 2026-01-15 023530
屏幕截图 2026-01-15 023530537×305 15.7 KB

1 Like
17

Thanks. One more thing is top of mind. Are you able to share your profile on any socials are are you deliberately anon?

18

@axia
I am not deliberately anonymous. I have been working as an independent developer and operator (freelance) rather than as an employee.

Before SwaptoX, my work was primarily focused on Web2 products serving Chinese-speaking users, so I did not maintain a public personal profile on global social platforms.

SwaptoX is my first Web3 project, and I registered the official SwaptoX X (Twitter) account in August 2025 as I began engaging more actively with the broader Web3 ecosystem.

At this stage, I prefer to represent myself publicly through the project rather than a personal brand, but I am fully committed to maintaining and developing SwaptoX long-term and remain reachable through the project’s official channels.

As the project grows, I am also open to increasing my public presence if it becomes beneficial for the ecosystem and the community.

19

Supplementary Clarification

As the proposal moves toward voting, I would like to clarify a few points and welcome any further questions from the community.

1. Positioning relative to larger aggregators
SwaptoX and established aggregators such as OpenOcean operate in a competitive environment. This competition is healthy for the ecosystem and, in practice, our positioning is complementary.
While larger aggregators tend to prioritize standardized processes and mainstream assets, SwaptoX focuses on greater flexibility, including support for long-tail and non-standard tokens, thereby expanding user choice within the ecosystem.

2. Milestone 1 scope and verifiable outcome
Milestone 1 focuses on deploying the full SwaptoX system logic on Rootstock mainnet, with initial liquidity support from WoodSwap and Sushi.
Upon completion, users will be able to directly swap Rootstock mainnet tokens through the SwaptoX interface.

3. Current development status
Development has continued in recent weeks, with work focused on building the SwaptoX administrative backend to support system operations and ongoing maintenance.

屏幕截图 2026-01-16 032549
屏幕截图 2026-01-16 0325491919×1030 165 KB

20

Thanks for the supplementary clarifications; no further questions re recurring delegate questions around positioning vs OpenOcean/other aggregators, what “Milestone 1” concretely ships, and whether work is actively progressing.

We also think the “complementary competition” framing makes sense in principle, especially if SwaptoX is leaning into long-tail / non-standard token support and deeper routing flexibility while larger aggregators prioritize standardized assets.

That said, to close the loop on the earlier reviewer requests (@Axia + @Kaf_StableLab + others), it would still be helpful to translate these qualitative claims into Rootstock-native, verifiable artifacts for Milestone 1 acceptance, a defined initial token/pool coverage list, and a short set of example swaps that can be independently checked. We don’t think this needs to be onerous, just something reviewers can consistently validate when deciding whether Milestone 1 delivered incremental value.

Finally, the other two themes from delegates that we think needs a little more addressing is to proactively address sustainability and risk management. Also +1 to the suggestion that later milestones evolve beyond “build” into “adoption proof”, but for Milestone 1, crisp verification criteria + transparent reporting would already go a long way.