[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[mmmaybe]

Not really good but better than 1.2.0...?


Updated db folder on mega:
https://mega.co.nz/#!J8hyHDjI!lx0o_Ei1p4a3QIgeZ-s8z8hkG-BoUKFx11FvXiNc1GI

[1714318463]

1714318463

[1714318463]

1714318463

[1714318463]

1714318463

[1714318463]

1714318463

[osvald]

Hello all!
Now pool cryptomining.farm work incorrect.
He find block 60022.
Polls burst.ga and other find block 60025.

[pinballdude]

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.

1.2.1 was the fix. It was released 6 days ago.

1.2.1 won't sync to the 1.2.0 fork, and 1.2.0 won't sync to the 1.2.1 fork, however 1.2.1 can get stuck for a little while at the fork point if it can't find the 1.2.1 fork right away due to all the 1.2.0 spam.

The only problem in play right now is the number of 1.2.0 clients around and amount of hashrate still on 1.2.0 keeping that fork running and widely available. Sure an update could be released to blacklist the 1.2.0 fork, but the 1.2.0 fork fails validation in 1.2.1 anyway, so it wouldn't change anything. The only fix is having a larger percent of the network on 1.2.1, and time and publicity are the only things that help that out.

Personally I've yet to see any significant issues getting onto the correct fork when using 1.2.1, although it depends a lot on which/how many peers you are connected to. I had 4 instances of 1.2.1 running from separate locations from before the fork, and they all followed onto the correct one without issue. I've also synced up to date in 1.2.1 from old blockchain copies I had, and from fully synced 1.2.0 from the bad fork, and nothing took more than a few minutes to figure out which the correct chain was.

things worked fine for my wallets too, but at 59800 something broke, and i went on a bad fork, i tried to restart many many times, and waited for hours. my wallets were stuck on the shorter chain, and there were these notifications of exceptions as shown previously. i didn't have the experience that my 1.2.1s went to the longer chain by themselves in any kind of hurry.

after having downloaded the right fork things worked for a while again, but right now, my wallets seem to post an error every 15 seconds, along the lines of :

2015-01-26 10:46:15 INFO: tx with id -1019205954960601549 found
2015-01-26 10:46:15 INFO: get timestamp for tx with id -1019205954960601549 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

i am working on block 60018 on all 3 wallets (all 3 showing above info message, with various intervals from seconds to minutes)
basetarget 2027904 height 60018 indicates i am on the right chain right now i would assume, but i fear we might have forked again around 60017 +/- as the last fork started with a similar error beginning to show on the bad fork.

Must admit that i *am* running a version i compiled myself, so i might have done something wrong in the build, in which case i should be the only one seeing above error. When i'm back from work tonight, i'll try to use the original 1.2.1 and see if that makes a difference.

[mig6r]

My Wallet is on the 60027

[smic]

8pool update wallet 1.2.1
pool is down for update system

http://burst8pool.dtdns.net:88
(port 8124 or 88)

[duncan_idaho]

I have no idea what is going on:
Block explorer shows balance = 2108
http://burstcoin.eu/address/10709331655304380457

but in my personal wallet my balance is 1178

And information from uray pool

Deadline
794419
9 days
avg 6 days
Share
0.526%
score 0.0003
avg 0.0021
Balance
1403.00
5677/day
avg 15.77/blk
Last Payout
0.00
#0
45 years ago

[yellowduck2]

did top 5 pool update their wallet ?

[oktay50000]

wallet.burstcoin.io is down?
any working web wallet?

[yellowduck2]

this top pools is on the same chain. They can be use as a reference for correct chain i think

http://cryptomining.farm

http://178.62.39.204:8121

https://mining.burstcoin.io/

Also, block explore http://burstcoin.eu is also showing the same block number as the above 3 pools.

[burstcoin]

after having downloaded the right fork things worked for a while again, but right now, my wallets seem to post an error every 15 seconds, along the lines of :

2015-01-26 10:46:15 INFO: tx with id -1019205954960601549 found
2015-01-26 10:46:15 INFO: get timestamp for tx with id -1019205954960601549 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

i am working on block 60018 on all 3 wallets (all 3 showing above info message, with various intervals from seconds to minutes)
basetarget 2027904 height 60018 indicates i am on the right chain right now i would assume, but i fear we might have forked again around 60017 +/- as the last fork started with a similar error beginning to show on the bad fork.

Must admit that i *am* running a version i compiled myself, so i might have done something wrong in the build, in which case i should be the only one seeing above error. When i'm back from work tonight, i'll try to use the original 1.2.1 and see if that makes a difference.

That exception is fine, it's throwing that when rejecting blocks from the 1.2.0 fork, and it's caught in block validation. I had it dumping the stack trace for debugging purposes, but now I should probably change it to a simple log message.

[adaseb]

I tried searching and reading but with the current rate. How much BTC per day do I earn with a 1TB harddrive?

[duncan_idaho]

My personal wallet is on the same block with pool.burstcoin.io and burstcoin.eu
But last transaction in my wallet is
http://burstcoin.eu/transaction/14537972800162209272
i dont see rest of transactions which is visible here:
http://burstcoin.eu/address/10709331655304380457

[vaxman]

I tried searching and reading but with the current rate. How much BTC per day do I earn with a 1TB harddrive?

Calculator: http://burstcoin.eu/calculator
yield is 323 Burst/day for 1 TB, or at the current exchange rate(s) ~17 US$-cents.
That's ~5 USD per month.

[mmmaybe]

this top pools is on the same chain. They can be use as a reference for correct chain i think

http://cryptomining.farm

http://178.62.39.204:8121

https://mining.burstcoin.io/

Also, block explore http://burstcoin.eu is also showing the same block number as the above 3 pools.

Thanks, for the time being miners should re-download or delete their DB and join one of those pools.

[xizmax]

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.

[duncan_idaho]

can someone write a little xplanation what is goin on? I dont know if i am on good fork and i dont want to mine my burst to /dev/null

[seasonw]

I'm having problem with my payment from pool... I saw 3 payments in "Recent Payments" column, but when I click on it, burstcoin.eu shows <Transaction not found>. First payment with problem is 24 hours ago. Is this pool or burst server issue?

BTW, I also found payment to other members in the pool having the same problem, but I did not record their transactions, so I don't if they get paid now. Or this is a normal process (I'm newbie to burstcoin, basically I'm newbie to cryptocurrency  )?

[xizmax]

can someone write a little xplanation what is goin on? I dont know if i am on good fork and i dont want to mine my burst to /dev/null

What is your latest block? Currently the last is 60063

I'm having problem with my payment from pool... I saw 3 payments in "Recent Payments" column, but when I click on it, burstcoin.eu shows <Transaction not found>. First payment with problem is 24 hours ago. Is this pool or burst server issue?

BTW, I also found payment to other members in the pool having the same problem, but I did not record their transactions, so I don't if they get paid now. Or this is a normal process (I'm newbie to burstcoin, basically I'm newbie to cryptocurrency  )?

What pool are you on, what is your latest block no?

[seasonw]

I'm having problem with my payment from pool... I saw 3 payments in "Recent Payments" column, but when I click on it, burstcoin.eu shows <Transaction not found>. First payment with problem is 24 hours ago. Is this pool or burst server issue?

BTW, I also found payment to other members in the pool having the same problem, but I did not record their transactions, so I don't if they get paid now. Or this is a normal process (I'm newbie to burstcoin, basically I'm newbie to cryptocurrency  )?

What pool are you on, what is your latest block no?

burst.ga, now is 60065

[duncan_idaho]

I'm having problem with my payment from pool... I saw 3 payments in "Recent Payments" column, but when I click on it, burstcoin.eu shows <Transaction not found>. First payment with problem is 24 hours ago. Is this pool or burst server issue?

BTW, I also found payment to other members in the pool having the same problem, but I did not record their transactions, so I don't if they get paid now. Or this is a normal process (I'm newbie to burstcoin, basically I'm newbie to cryptocurrency  )?

What pool are you on, what is your latest block no?

burst.ga, now is 60065

Wallet in my comp shows 60065
My pool poll.burstcoin.eu shows 60066

i dont see transactions from block explorer burstcoin.eu in my wallet
one of my address: BURST-923B-ETN6-TDNW-BJT9B