Wallet blocked again on a block


  • admin

    @socalguy I don't know what happened, but whatever it was it seemed to blow up pretty much most of the wallets on the network. I've got the pool wallets unjammed and syncing again, and it seems other wallets are catching up. If you're running a local wallet, I'd recommend restarting it - if it errors out delete the burst_db\*.* and resync from the start.



  • @haitch I have been monitoring my local wallet and blocking anyone that has not updated to version 1.2.6, and allowed around 50 connections with my ip broadcasted. I have seen multiple GB of ppl getting their db downloaded through me.

    I have found that this helps, my wallet has been running for weeks without problem. I see sometimes that blocks are rejected even.

    Wish we could have an auto fail-over to solo type of deal.

    Just a note is all, hope it helps in someway!



  • Guys, the blockchain needs only one miner/pool to move on, the difficulty is re calibrated each block. So if some pools are down it does not necessarily mean that the network is totally destroyed, the project is failed and you must hang yourself. :)



  • @socalguy said in Wallet blocked again on a block:

    As far as some losing faith in the coin, just wow. I can't believe a little hiccup and folks are ready to jump ship and proclaim that the coin is a failed project. Show me another coin and I'll show you their recent issues. Every coin out there currently has, or in the past, has experienced issues. Even Bitcoin has issues every now and then.

    Well, It is not the first time happened and none of the time it happened was really explained why it did happened and how to avoid it. So it is up to you to keep your faith in whatever you believe in, but do not judge people if they feel this is insecure.


  • admin

    @Jumper When I first saw all my pools down my initial thought was a DoS attack on my pools - then I saw pretty much all the pools/wallets were down. I don't know what happened, but my best guess is that some sort of invalid transaction was submitted to the blockchain, and all the wallets got stuck on it until the transaction errored out. The wallets are becoming unblocked and catching up again - it may require some wallets to be restarted, but overall - something pretty significant temporarily broke the network, but it recovered on it's own and is working as designed.



  • @haitch

    Yes, that is correct. It is working now, for sure, and as you are saying, possibly corrected itself by design.

    However, I still feel that it would be great to know what exactly caused it and to do something to prevent it.

    I started Burst mining about 2 months ago and experienced at least 5 time so far when my wallet did not synced. None of the time I was able to get the root cause.

    So as an example of today, issue lasted about 8 hours, which is quite high.

    While any Cryptocurrency can and will have some issue, I have never seen one which have issue so often without knowing exactly what causing it.

    But anyway, it is working now , at least for me, but had to PopOff some blocks to make my wallet working again.


  • admin

    @Jumper Hopefully someone that can read the transactions in the Blockchain will be able to go back and find the root cause, and the wallet code can be updated to prevent it happening again. But we also need everyone running old versions of the wallet to update to the current version. We can fix the issues that cause the problems, but if there are a lot of instances of old code running, fixed issues can still break the network through un-updated wallets.



  • @haitch

    What about forcing an update? I am programer myself and I know that old clients could be limited how long it works until update is mandatory. Just an idea.. :)


  • admin

    @Jumper potentially it would be possible to get the wallet to ignore nodes running older code, but that runs the risk of there being two "valid" blockchains, one on new code, the other on old code. That's not a desirable situation either. I don't have the answer to the best way to fix the problem, but I implore people to get onto the current code base - there are still a lot of 1.2.3 wallets out there that need to upgrade.



  • @haitch Yeap, I guess you are right.



  • @haitch @Jumper

    I guess that a mandatory update of the wallet could help as well as recognize the problem in order to avoid future similar issues.
    I guess that if we want a solid coin and a constant grow, we can not simply say "it recovered on it's own and is working as designed.".

    I hope to read here in the next hours/days why the problem appeared today :)



  • I vote for ignoring older versions. That's what other coins do. As long as all the pools and exchanges are notified and changed, then it should work. Anyone on the old chain would eventually not be able to do anything and be forced to update.



  • @crutsy yeah also like this is a sort of mandatory update! Maybe just a bit brutal ;)


  • admin

    When only the solo miners and some smaller pools are left mining, the blocktime can increase to several hours. I think this happened as a side effect.

    We are investigating what actually crashed that many wallets. I think we are on the right track but if we knew it without doubt, it would be solved yesterday.
    The Burst network and protocol are only two years old. There will be more friction on the way. If it is too much heat for some of you - I can understand it.
    Please consider that high growth rate and gains are always coupled with higher risks. There are other ways to invest your hard earned money and get a interest rate of 3% a year in a less risky and volatile project.
    It is also unfair to compare Bitcoin with Burstcoin. Bitcoin is 100 times larger in Market Cap and four times older - and they had and have their famous bugs regularly, too.

    No money was lost - maybe some pools made some wrong pay outs and some solo miners had their lucky day, but nothing noticeable.

    Someone said: the longer the chain, the higher the value of the network. I think this is very true. There is a long and sometimes bumpy road in front of us.



  • @daWallet
    Thank you for your update on the issue.

    I didn't understand your first sentence

    "When only the solo miners and some smaller pools are left mining, the blocktime can increase to several hours. I think this happened as a side effect."

    If you can could you kindly explain?

    Could you also inform us on what you think is the reason behind it.. "I think we are on the right track"
    Maybe some of us could help as well if we have more details.

    thank you again!


  • admin

    @ccminer If the big pools go down at once, the left mining power is only a fraction. The time of a block determined by how many plots are sending their results of an equation. If e.g. only 30% of the network sends a result (the deadline) the best deadline can be two hours long.
    After this long block is solved the difficulty equilibrates to the new network situation and the next block will be solved (probably) closer to the targeted 4 minutes. The difficulty of mining always adjusts some blocks later..

    This explanation is simplified, but that is how most of the crypto currencies work.



  • @daWallet

    I know how the difficulty is retargeted in the cryptocurrency mining.
    Do you think is this that happened today?


Log in to reply
 

Looks like your connection to Burst - Efficient HDD Mining was lost, please wait while we try to reconnect.