Dex Aggregator for Bittorent

So have been to thinking on working on a Dex Aggregator but not sure if that is a right call.

And reason been me & a friend built an NFT marketplace and submitted during the Hackathon

But after submission there haven’t been much engagement or interest with the project.

And I know most people will advice me to build but building something that is not used or seeing that it interest people kinda of takes the mode away.

That why I want to ask the community in general - Do you see yourself using a DEX Aggregator on BTT ( Bittorrent) ?


We did that for #TronNetwork and aggregated all the prices from all the DEXes on #Tron within our mobile dApp (Android).

Well is not the greatest idea as now the exchanges are using Smart Routers and a smart router finds the best path to the best price and some of them also uses other DEXes liquidity like @JustMoney uses liquidity. Meaning your direct route could cost the user less tokens in its balance. We are looking now to use the liquidity over all the DEXes and create our internal pathfinder so that we get the user the best price.

If you want to check more our DEX Aggregator


Looks solid but when finding the best path you first need to get all Dex outputs.

The first step is to have the router for the aggregator and helper contract designed for each Dex.

Since many Dexes on bittorrent and Tron use uniswap v2 it will be much easier to implement the only thing which will be different is the fees for each Dex.

Anyways these helpers contract will get the amount out/output from each Dex and the router can compare which one has the best out.

But also since this is an aggregator, we won’t want to swap it just like that else we might cause an imbalance in the price difference leaving room for arbitrgaer to take the profit.

What the router will do now is to use the out comes calculate the an optimal path using other tokens and if possible spilt the trade among the Dexes.

1 Like

It’s common for new projects to experience a lack of engagement initially, especially in the competitive blockchain space.
Instead of giving up on the project altogether, consider conducting market research to better understand the needs and preferences of potential users.
You could reach out to the NFT community, participate in relevant forums or social media groups, and gather feedback on what features or improvements they would like to see in an NFT marketplace.

Additionally, you could focus on marketing and promoting the Rooni platform to increase visibility and attract more users. This could include partnerships with popular NFT projects, running social media campaigns, or participating in events and conferences to showcase the platform.

Ultimately, it’s important to assess the potential of the project and the level of interest from the market before making a decision to pivot to a Dex aggregator.
It’s possible that with some adjustments and effort in marketing and community engagement, Rooni could gain traction and become a successful marketplace for digital treasures.

1 Like

thanks :slight_smile: but we are not given up on Rooni( the reason i brought it up was because we havent had much activity has expected ) we are still working on the financial part which is the Lending and borrowing of asset using the Btt.

Also posted the Dex aggregator here so I could get an insight on the thought of the community since most of the community uses this forum has a source of new and update ( maybe they could share some thoughts )


you did the right thing by writing about your idea here. I am sure that there will be like-minded people and many ideas from users.
Feel free to share your progress here

That is what we do check all the DEX outputs.

We use so far each ones user but we migrate now to a generic Router

Not sure what will you use the helper contract for? You need to know in the dApp only the factory addresses.

Is good to have a router that make multi router wil parts of the total amount as long as the fees are worth the difference in the token that you get

yeah most of the pools use uniswap v2. The fees on TRON can be estimated before doing the tran

the fees am referring to is the Dex fees ( some are 0.2%, others 0.17%) so while this fees might me small if not taken into account the transaction might failed depending on how the contract is set plus the users will like lose much more than they would have if they use dex directly)

anyways for helper contract (the reason why i mentioned it, was that creating the aggregator - the main contract should be the router contract which only job is to execute trade) the helper contract will be contract that help the main contract estimate trade path,

example let say we have 6 dexes on chain
two of those dexes are using the uniswap v2 protocol ( let call them ASWAP & BSWAP )

another two that uses the uniswap v3 protocol ( CSWAP & DSWAP )

last two dex using Algebra ( ESWAP & FSWAP )

so instead of creating a helper contract for each of this dex independently you , all what needed to be done is to create onehelper contract that can carter for all dexes depending on the protocol they are using,

since ASWAP & BSWAP are using same protocol helper contract which will be in assistant to the router in providing (e.g amount out ), same for the Algebra & uniswap v3 protocol.
so helper for uniswap v2, v3 and algebra

hope you get my idea


hi @Rink3y

sorry if my question seems strange. But I found this topic interesting and would like to know where can I find a list of all the DEXs on the TRON ?

well i found a repo similar to what have shared>

yieldyak/yak-aggregator: On-chain dex aggregator (

i will look into that and share more info - this look very similar to the structure I have in mind

1 Like

1 Like

thank you @Rink3y for that link