Introduction
Hey everyone!
After listening to some feedback and discussion about how the current SWAP.HIVE <> HIVE transactions are being done, one of the most complaints I heard was "oh but the bridge I am using is out of funds!" or something along those lines.
To solve that issue, I wrote @swaps, a simple aggregator that ensures (as much as it can) that you receive your SWAP.HIVE, or HIVE -- depending on which coin you send to it. By checking and using well-known and reputable bridges on the network.
How to use it?
Very simple! Just send >1.5 HIVE/SWAP.HIVE to @swaps with no memo (or put one in, if you'd like, doesn't really matter) and hopefully, in a couple of seconds, you should receive your HIVE or SWAP.HIVE, depending on which token you sent. If you send @swaps SWAP.HIVE, you'll receive HIVE. If you send it HIVE, you'll receive SWAP.HIVE. If by chance, the bridging services utilized by @swaps are completely out of funds, the bot will automatically refund you instead. (Read further for a hopeful solution to this problem.)
Currently, the service utilizes Leodex & Beeswap depending on their wallet holdings. So basically, you do not have to bother checking them if they have funds or bother with seeing if you got your refund... or actually be like my friend who forgot about his SWAP.HIVE because it got refunded and he never checked.
In the next couple of weeks, I am planning to implement an internal liquidity/swap system to ensure even in the worst-case scenario where both services that @swaps utilizes are out of funds, that @swaps can handle the coin bridging itself.
Why should I use it?
Because it's easy! You do not have to bother checking liquidity on other platforms. Simply use Keychain, Peakd, Hive.blog, Ecency -- whatever platform you're using to send your coin to @swaps, and it will convert it and send it to you.
In the future, with an internal liquidity system implemented, you can expect lower fees :)
Note
Please do note that while I and a couple of other people have tested the bot vigorously, it is possible that there might be some issues. I tried to prepare for most edge cases (in terms of node errors, library errors etc.) to automatically refund the user if a problem occurs. But if, by chance, you do not get a refund, please contact me.
I suggest delegating more HP to it. It seems like it runs out of RC at a pretty fast rate after only a few transactions.
*deleted
*Deleted
@deathwing
I was sleeping, my apologies.
I don't have a "Deathwing" discord channel, but you can find me almost in all Hive related Discords. On the other hand, apparently, the bot had an issue with Hive-Engine when trying to process your transfer and then got stuck, confused.
I both fixed this issue where it shouldn't have this problem anymore, as well as forced it to process your transaction.
Tested it a few times now with small amounts. Received the Hive a few seconds later. Got one trasaction that took about a minute to complete.
Thanks. Got the HIve. Good idea. Looking foreward to when it's more stable...
Interesting, I think I'll prefer to test it out when there's much liquidity added.
Swap.hive are hive engine tokens right?
Swaps are taking really long to receive. Not sure what's going on.
I still haven't received my swap 1 hour later.
Hmm... have you received it now? I can see some node errors on my logs for Hive-Engine related stuff but it does appear to have processed it, albeit a bit late.
No not yet. I sent two 1.6 Hive test transfers but only one of those was successful. I'm still waiting on the other one.
Posted Using LeoFinance Beta
After the test transfer failed, I stopped trying to do anymore transfers using @swaps until whatever issue was fixed.
2021-11-15 18:27:15 @swaps Sent tokens_transfer
2021-11-15 18:21:18 @swaps Sent tokens_transfer
Alright, edited quite a few things and tested with several different transactions. I found one bug while my testing which is potentially why your transaction did not get processed. But that bug is fixed now so, it should be fine.
Yeah, I sent you your 1.6 SWAP.HIVE back. I am looking into how, but it seems like the bot did not even recognise one of those transactions, I am not saying something went wrong... it just didn't even see it. So I am assuming something happened with Hive-Engine connectivity. Will look into it next time this happens as I just added some extra logs to be sure.
I tried a test 1.6 SWAP.HIVE transfer to @swaps a few hours ago. I haven't received the HIVE conversion yet.
2021-11-16 15:51:09 @swaps Sent tokens_transfer
Hmm...
I was able to find https://hiveblocks.com/tx/94ab37c9124243448fc1ea8a507602afd371dbe7 this transaction that might be the one you mentioned. It appears so that we clashed :) I was doing some updates at the time to Swaps to add new features so it appears you sent 1.6 HIVE the moment I was working on it.
Sorry about that, but thankfully, it was not a bug. I sent you your 1.6 SWAP.HIVE back. :)