By now many people would have noticed already that Hive Engine is down and the witnesses are trying to catch up. It is expected that it can take at least a day or two for a fully functional Hive Engine as we don't have any concrete solution yet. There are a few proposals on what can be done to handle this but most of them also have their own advantages and disadvantages.
There are so many projects that are dependent on Hive Engine right now and the code optimization is very important for Hive Engine considering the fact that it is struggling to process blocks one by one. Another problem faced by Hive Engine team is that even if someone is interested to build something, there is not enough revenue being generated to compensate further development. Sometimes issue fixing also becomes a challenging one.
What happened?
Last night there was a heavy spamming happened where one specific account broadcasted hundreds of transactions trying to place some micro orders in the market. This caused a heavy delay in processing the hive blocks. The spam was done specifically by an account called @shaggroed which appeared like an intentional spamming. The good thing is that the spamming stopped at one point which is on block number 93051117. The witnessess will have to reach this block and only then the block processing will become faster.
There is a possibility that the spammer might get back to spamming after we are all caught up and the chain is back up again. So the only way to handle this would be to have the solution implemented so that in the future such things can be handled. The first solution would be to restrict the number of transactions per user which will be only 20. I guess I myself might have to update some of my bots if at all this change happens. The next change might be to add a number of market orders that caan be placed in the market. 250 open orders per user will be a decent value I believe.
Now we have to be patient until the issue gets resolved and the block processing gets back to normal. It is also advisable to no do any heavy activities on Hive for Hive Engine.
If you like what I'm doing on Hive, you can vote me as a witness with the links below.
 |
 |
 |
Posted Using INLEO
Well, thanks for the update!
This is certainly concerning, especially if you view this in the context of actually being a variety of DDOS attack... and it's a pretty good bet that "shaggroed" is driven by someone with a personal axe to grind against Hive-Engine co-founder "aggroed" if you extrapolate the greater meaning of "shag" from the perpetrator's name.
I'm sort of in favor of some "limits" on number of transactions... if we believe in the foundational notion that what we do here is ultimately "Proof Of Brain," then there's little need for any one account to transact more than once every few seconds. Or whatever interval seems reasonable. In other words, put a plug in the pipe upstream from where the chain can effectively become overloaded... a bit like a localized Cloudflare stop.
But I am not a technical person...
Your comment is upvoted by @topcomment
More info - Support @topcomment - Discord
Even beeswap.dcity.io together with tribaldex.com experience the same unpleasant impediment. Unbelievable what a single account set as a trading bot could do!!!
Now I got it and understood what is happening .
Restrictions the number of transactions per user seems a good solution .
When the user is more then this kind of problem is not a problem and it gets fixed in a couple of days it is a trusted platform.
At first I was so concerned about the situation. But I am so sure that it is under control and it will be resolved
Discord Server.This post has been manually curated by @steemflow from Indiaunited community. Join us on our
Do you know that you can earn a passive income by delegating to @indiaunited. We share more than 100 % of the curation rewards with the delegators in the form of IUC tokens. HP delegators and IUC token holders also get upto 20% additional vote weight.
Here are some handy links for delegations: 100HP, 250HP, 500HP, 1000HP.
100% of the rewards from this comment goes to the curator for their manual curation efforts. Please encourage the curator @steemflow by upvoting this comment and support the community by voting the posts made by @indiaunited..
This post received an extra 20.00% vote for delegating HP / holding IUC tokens.
Yes most of us are fully dependent on hive engine due to the layer to tokens and it feels weird if hive engine is down. I am sure the team will come up with something new and that is going to be helpful and beneficial for all the users who are here. Many peoples only do trading don't post and that is the only source of income they do have. I am sure they are having a lot of trouble then the past a few days and not sure how long it is going to take I hope in this will be all settled by the weekend thanks for the update great post as always. have a great day and weekend ahead.
Discord Server.This post has been manually curated by @bhattg from Indiaunited community. Join us on our
Do you know that you can earn a passive income by delegating your Leo power to @india-leo account? We share 100 % of the curation rewards with the delegators.
100% of the rewards from this comment goes to the curator for their manual curation efforts. Please encourage the curator @bhattg by upvoting this comment and support the community by voting the posts made by @indiaunited.
I wonder why BeeSwap is still working. I thought it is also dependent on Hive Engine.
Yucks! This is concerning.
add a delay between too many transactions could do too
Hive Engine should not be down, and every effort should be made to ensure that it does not happen again. Limits should be placed on transactions.
No wonder I've been having road blocks on keychain i hope it gets fix soon
No wonder
I tried opening Hive engine through the Keychain application and it wasn’t loading
I tried it so many times but it wasn’t going through
It's a tough situation, but with patience and the right solutions, we can look forward to a more resilient platform. Let's support the witnesses and developers as they work through this!