Some time ago, Hive-Engine introduced a system that should prevent spam transactions. In theory, that is a good idea. In practice, it started to annoy me today. I can imagine that other “normal” users are running into the same issue.
Let me explain what happened.
I had several open sell orders for different tokens. My plan was simple: cancel them all at once and then recreate them afterwards. Tribaldex allows you to select multiple buy or sell orders at the same time, so I thought this would be quick and easy.
And at first, everything looked fine. I selected my orders in the Tribaldex frontend, Hive-Keychain popped up, I confirmed the transaction, and it was sent correctly.
But then comes the problem. On the second layer (Hive-Engine), the final transaction failed with the message:
In my case, two of the orders were canceled successfully, but one failed for no clear reason. Here is the transaction on HiveHub if you want to see it yourself:
https://hivehub.dev/tx/20b16c08891161a0157391acf058d0c0fe30a6c3
From a user experience perspective, this is very frustrating. I basically have to repeat the same process multiple times, writing multiple transactions to the blockchain, just to achieve something that should be done in one step.
To make it worse, there is no proper feedback inside Tribaldex. The frontend shows nothing about the failed part of the transaction. If you want to understand what happened, you need to go to a block explorer, where you only see a vague error message that does not really help.
For me, this is bad UX. At the very least, the frontend should give a clear error message so users know what went wrong. Even better would be a fix that allows canceling multiple orders without running into this strange fee or balance issue.
Has this happened to you too? Does it bother you? For me it is simply annoying. I really hope this can be adjusted because the way it works now makes no sense for everyday users.