IPFS-messaging improvement, no way for the null secret and multiple tabs…Atomic Swaps on EOS?
We would like to share with you our latest updates on the development progress that occured during this hot August. Like our previous development report, this one is dedicated mostly to the issues of stability and usability.
Since instant and reliable cross-chain transactions are one of the market problems we address, the stability of swaps is one of our ‘things’. Thus, we’re working hard to avoid all the malfunctions which can occur within the swap process. For example, we improved the process of IPFS-messaging. In our previous articles, we briefly described the usage of this technology in the Atomic Swaps process. “Now in case of IPFS-connection failure, the users are able to get reconnected very shortly. The system checks the correct IPFS-room and reconnects you automatically; as a result, now the lost progress of swap is not an option’, comments the improvement our lead developer Nikita Dementiev.
Also, the mechanism of swaps now considers whether the messages between a market maker and a market taker are finalized correctly or not. Remember our pesky Alice and Bob. Alice is sending a message to Bob. Now in Swap.Online, Mr. Bob should confirm the receipt of the Alicе’s message for the procedure continuation. If he doesn’t, for the bilateral security of traders, the message is requested one more time.
Moreover, now the Swap.Online IPFS-mechanism avoids the proceeding of null secrets. Finding the fact that some transaction secret is null, the mechanism also removes such transaction.
Finally, we prohibited the Swap.Online launch from the multiple tabs. As the processing machine sees the tab when the swap is launched, the six Swap.Online tabs can mislead the user (but not the Swap.Online). So, this limitation (used e.g. in Telegram Web) is introduced with the purpose to secure the stability of swaps.
As we work with the cryptocurrency remittance, we fully accept our user’s desire to know all the details about their swaps’ proceeding. To grant this request, we presented two visualization options. Firstly, now all the errors (e.g. gas insufficiency) are displayed in the swap monitor screen. You are not only unable to lose your money but even to miss a single thing about its status. Secondly, now the progress of the IPFS-connection loading is shown in the left bottom of the start page. You can trace when the connection will be reached and how many users (‘peers’) are online.
Also, now the user is able to copy the link on a given order to the clipboard and send it to a friend. As Nikita says, ‘In addition, you can see, which orders you have opened via the received links. Now, you can discuss it with your friends or post to social network boasting about your success in crypto trading’
The orders you have received via the copied links are highlighted green
Finally, we implemented constant checking of users’ ETH balance. In case of its insufficiency, the user will be informed before the trade.
Moreover, we fixed some minor bugs, checked the SEO-optimization of our site and made Swap.Online operations much easier for low-performance computers with poor RAM. So our service will really be mass adopted.
And now we are getting closer to the good part.
Our team made a tremendous progress on the EOS implementation in our decentralized multi-chain wallet. Why it matters and how it was done – that deserves another single article. Stay tuned and exchange EOS on BTC and ERC-20 tokens in a decentralized way!