OPTUS Update: New Chapter after Demo Launch

OPTUS
3 min readAug 10, 2023

--

We’ve got some fantastic news — the highly anticipated OPTUS update is finally here. We used your valuable feedback to compile the bug list because your input means the world to us. Transparency is our mantra, and we believe our community should be part of our product’s creation. In this article, we’ve detailed all the fixes our developers implemented after the demo launch.

Our main achievement is deploying the first-ever decentralized interface on TON Blockchain, allowing us to utilize multiple providers (http, json, RPC) in case the main one fails.

Even if our servers encounter errors, rest assured our app will keep running. Plus, anyone can deploy it on their server. We’re open to data verification because your data safety matters to us.

You might experience slow interface loading due to direct blockchain data retrieval. Within a month, we’ll be launching a centralized version that will significantly enhance performance and speed up operations.

So, what have we done?

  1. Styled ‘Settings’:

2. Fixed the liquidity provision calculation by considering the proper fractional part of Jetton.

3. Added an informative window for liquidity provision:

4. Introduced a field for indicating burned LP Jettons:

5. Locked the burn button when there’s insufficient TON balance for the fee

6. Fixed ‘Price Impact’ calculation when flipping tokens

7. Corrected token selection when choosing TON

8. Fixed minimum token calculation during ‘Swap’

9. Fixed minimum token calculation during liquidity withdrawal

10. Created a utility for DECIMAL calculation in case of different Jetton metadata

11. Added a notification for insufficient TON balance next to the wallet address

12. Displayed TON balance next to the wallet address

13. Fixed styles for the mobile version

14. Fixed an error where swapped Jettons confused the balances

15. Adjusted input field styles for smaller screen resolutions

16. If the user’s Jetton balance is insufficient, the input field will be highlighted in red

17. Fixed an error where the form lost its background in some resolutions

18. Implemented blocking of swaps and liquidity addition in case of insufficient TON

19. Fixed TON and pair selection logic

20. Fixed commission estimation

21. Rolled out the decentralized interface to use multiple providers (http, json, rpc) in case of primary provider failure

22. Added the ability to specify a provider in ‘Settings’

23. Added the ability to check pool availability and automatic pool verification if we can’t request token contract balances from TONAPI.IO

24. Added a loader for liquidity withdrawal

25. Fixed an error in liquidity calculation display

26. Added an informational window when withdrawing liquidity, showing the current pool token amount, the amount available for withdrawal, and the amount to be received

27. Fixed edge alignment on the screen

28. Fixed input color logic

29. Ensured price remains up-to-date when changing token amounts

30. Fixed allowable slippage settings

31. Implemented that clicking on balance or MAX button uses all tokens for exchange

32. Fixed metadata and app icon

Impressive list, right? We’ve put in our best efforts!

In addition, we’ve introduced four new trading pairs along with liquidity for each. Now, alongside WTON-FNZ, you can trade and provide liquidity for jUSDC-WTON, jUSDC-jUSDT, jWBTC-WTON, and WTON-jUSDT pairs.

Stay tuned as we gradually add new trading pairs and liquidity over the next few weeks. We plan to release a frontend version on IPFS and also utilize tonSite and tonStorage.

Stay updated with us:

🌐 Our DEX: https://app.optus.fi/

📊 Dashboard: https://board.optus.fi/

🗣️ Telegram Channel: https://t.me/optus_fi

🐦 Twitter: https://twitter.com/OPTUS_dex

💬 Discord: http://discord.gg/b8xdDmgTZu

Thank you for your incredible support, and let’s keep pushing the boundaries together!

--

--

OPTUS
OPTUS

Written by OPTUS

Decentralized exchange & DEX aggregator with the largest liquidity on TON. https://linktr.ee/optus_dex

No responses yet