A Tribaldex / Hive-Engine Problem / Multiple 2n Layer Actions in one Transaction failing...
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.
Half of Tribaldex never loads for me no matter what node I have selected, so I stopped using it a while ago.
I think first tag should be #hive-engine instead of #hive-enine
lol, ur right.
I was going for HE for hive/hbd market maker
U changed my mind to stick to L1
By the way, I followed u after reading your comment under leo proposal
I noticed some strange things too on HE lately. For example, a jump in intra-day price without actual orders being executed or even new orders on the regular market being introduced to justify the price movement. If the price action was real, I had sell orders which should have been executed, and they weren't. At first, I thought it was a glitch on beeswap, but I checked Tribalbex and it showed the exact same green candle, which didn't appear to have anything backing it.
On another, less active token, I saw the limit orders seemed... out of order, but there may be an explanation in this case. I introduced a sell order which should have been a limit order, but found out it got executed right away, so I must've hit a buy order which wasn't displayed by the interface. At first, I thought it was possible the buy order was exactly the same amount and price and size as my sell order and got introduced maybe seconds before my order, and the new order wasn't updated by the interface until I entered mine. So, I repeated the process with the same amount, with the same result. Seemed like there was an invisible order that was there I couldn't see. There is maybe the possibility someone ran a bot and... when they picked up a sell order at a price they are comfortable with, they immediately introduced a buy order to accumulate that token. But I haven't looked into it to see if I discover more on a block explorer.
@louis88 I can totally understand your frustration. The idea of preventing spam transactions is good in theory, but it does become inconvenient when normal users face issues like this. Having to cancel and recreate orders should be a smooth process, especially when platforms like Tribaldex already allow multiple selections. Hopefully, improvements will be made to make it easier for regular users while still controlling spam.