Wallet blocked again on a block
-
Pool.Burstcoin.de is up too
-
@ccminer Totally agree. I have invested a lot of money on HDDs, but when things like that happen, my HDDs are totally useless.
And the worst is no one really know why this happening.
-
@Jumper
I invested a bit and I was plannig to invest more in hdd's, I was even ready to purchase wholesale.
But this issue is blocking me :( . I really hope that the solutions will be good enough to let us gain faith on this project again!
I'm even ready to help if someone with more knowledge on this project will point me.
-
@Burstde said in Wallet blocked again on a block:
Pool.Burstcoin.de is up too
Did you change your server clock time to get it back running ?
-
Ok, I have PoOff the last 100 Blocks and now seems to be ok
However, it would be really nice if someone explain why this happens
-
This is crazy. Really need to rethink my investment in this coin. A simple time change shouldn't jam up the whole network.
-
@Jumper
I've manage to get 10 blocks more but stucked again by changing time on server, Im now loading a save from 1 day ago...
-
http://pool.burstcoin.party:8081/ is on Block: 289814, Scoop: 3246, Diff: 1405
The site is showing blocks on the pool and the site is updating. I also checked on the backend and didn't see any errors. Not sure what is going on but I'm sure once Haitch gets online it'll be sorted asap. :)
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.
Heck, Zcash is in experimental phase right now. I would bet the vast majority of people mining the coin don't even know that fact. Don't believe me, go here. Also, here are the security warnings with Zcash.
Every coin has hiccups and they get fixed. That's crypto. :)
-
@socalguy said in Wallet blocked again on a block:
http://pool.burstcoin.party:8081/ is on Block: 289814, Scoop: 3246, Diff: 1405
The site is showing blocks on the pool and the site is updating. I also checked on the backend and didn't see any errors. Not sure what is going on but I'm sure once Haitch gets online it'll be sorted asap. :)
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.
Heck, Zcash is in experimental phase right now. I would bet the vast majority of people mining the coin don't even know that fact. Don't believe me, go here. Also, here are the security warnings with Zcash.
Every coin has hiccups and they get fixed. That's crypto. :)
Thank you for pointing this out.
I just want to said like what you said but I cannot write as good like you.To OP : relax and take a break, nothing perfect, the devs will catch it up soon.
-
@socalguy i just left my miner mining at your pool if we are on right chain cool, if not well i dont loose much as i use my pc anyways :)
-
@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.
-
@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.
-
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.
-
@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.
-
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.. :)
-
@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.






