I need some help getting my rig mining.
I have claimed some BURST on different faucets, but my address is still "not found" at
https://mining.burstcoin.io/Can someone send me some burstcoins, so that I can get started with mining...
Or am I wrong with this interpretation???
Thanks!
Did you make an outgoing transaction?
Thanks for the DB download.
I've been mining coins for quite a long time and have seen some pretty shitty forks, which usually result in the developers having to release a client that actually kills the bad forks. I don't understand why developers and people say 'just let it sort itself out', meanwhile countless users of the coin risk losing fuck tons and mining time by continuing to use essentially a broken coin?
Developers should be on top of this shit. They should immediately release a client that kills the old forks if it doesn't clear itself up in 3-6 hours. We've had this forking issues since the 1.2.1 release if I'm not mistaken, which happened on... friday? From what I understand, it's not hard to kill old forks either with a new client.
Forks are like a slow poison that work their way through a coin and really mess things up. If there is an exchange as big as Poloniex still on the wrong fork, there is definitely something wrong, regardless of how good the coin is. Tons of people exchange with poloniex and if they see their transactions going through, it'll perpetuate the circle.
There is essentially six pages of posts here trying to find ways to fix the fork, work on the fork, and eventually culminated in a 'community fix', which is transplanting someone elses DB to your computer, which you should never need to do if everything is working alright. Is releasing a new version of the wallet really 'that' bad compared to having people possibly sit on a fork for god knows how long?
I know, I know, forks happen, but pro-active development could really limit their impact.
While you do raise some valid points, what we've seen here is the instance of miner "voting", though not deliberate. Unfortunately, some larger players did not update and caused the issue. In such a case of voting there is not much a dev can do, shitty or not, that is just the nature of "consensus" systems. I think burstdev took all reasonable precautions here.
In any case, I thank the community for the workaround/fix. This is not a multimillion dollar endavor so you can expect to get an immediate response, and quite frankly you got a workaround within a very short time window. I do not believe many enterprises with paid staff would manage it in such a short time frame.
Hope this story will help in burst PR~~ 
