I haven't found a block in a few days, does that have something to do with the 1.2.1 update?
Also interesting, it seems as though the majority of the hashing power for Burst lies with a few individuals and forks happening because of outdated wallets by them.
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 457. (Read 2170648 times)
January 25, 2015, 03:49:07 PM
January 25, 2015, 03:47:53 PM
Im back on Burst.ga US pool...everything working great now.
My other pool was pool.burstmining.com( beta), and it is still 59798 as the other is 59812.
My other pool was pool.burstmining.com( beta), and it is still 59798 as the other is 59812.
My guess is that an outdated node (or many) was the link between two subsets of the network and these 2 subsets started building their own chain.
January 25, 2015, 03:46:42 PM
I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.
my guess too, but i don't know either. Anyways, i've stopped my 3 wallets now - no need to put work into a blockchain that is behind and with lower hash rate. when i got out basetarget was 4.8mln at height 597798
i'll rename the burst_db on one of them, and try to start it with a copy of the 1.2 database from before i updated some days ago. who knows, perhaps it will go get the best blockchain. worth a try.
It can't hurt to try, we'll see how the situation develops.
My chain on 59813, 2893829
January 25, 2015, 03:44:19 PM
Im back on Burst.ga US pool...everything working great now.
My other pool was pool.burstmining.com( beta), and it is still 59798 as the other is 59812.
My other pool was pool.burstmining.com( beta), and it is still 59798 as the other is 59812.
January 25, 2015, 03:41:54 PM
I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.
my guess too, but i don't know either. Anyways, i've stopped my 3 wallets now - no need to put work into a blockchain that is behind and with lower hash rate. when i got out basetarget was 4.8mln at height 597798
i'll rename the burst_db on one of them, and try to start it with a copy of the 1.2 database from before i updated some days ago. who knows, perhaps it will go get the best blockchain. worth a try.
January 25, 2015, 03:39:26 PM
I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.
The longest chain should win yes. I haven't seen an issue such as this with burst before so unfortunately I cannot help either :/
EDIT: Obligatory poor joke: vbcs broke the chains
Hahaha .. you found me!!
January 25, 2015, 03:36:09 PM
I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.
The longest chain should win yes. I haven't seen an issue such as this with burst before so unfortunately I cannot help either :/
EDIT: Obligatory poor joke: vbcs broke the chains
January 25, 2015, 03:34:28 PM
I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.
January 25, 2015, 03:31:40 PM
Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
my wallets are now working on block 59797
others report being over 59800 already
i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.
anyone having wallets that are on 59800+ and what basetarget do you have?
59809
basetarget 2657240
I see 59806 and basetarget 2362468
okay, seems like you have the chain with the most processing power behind it.
Any suggestions on how i can shift over? or do you know if the wallets will figure it out by themselves at some point? i'm all 1.2.1 on all 3 pc's
January 25, 2015, 03:28:42 PM
Just got block 59807 with basetarget 2828857
59809, basetarget 2772743
Looks like we got multiples
January 25, 2015, 03:26:37 PM
Just got block 59807 with basetarget 2828857
January 25, 2015, 03:22:32 PM
Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
my wallets are now working on block 59797
others report being over 59800 already
i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.
anyone having wallets that are on 59800+ and what basetarget do you have?
59809
basetarget 2657240
I see 59806 and basetarget 2362468
January 25, 2015, 03:20:45 PM
Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
my wallets are now working on block 59797
others report being over 59800 already
i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.
anyone having wallets that are on 59800+ and what basetarget do you have?
59809
basetarget 2657240
January 25, 2015, 03:18:27 PM
Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
my wallets are now working on block 59797
others report being over 59800 already
i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.
anyone having wallets that are on 59800+ and what basetarget do you have?
January 25, 2015, 03:09:46 PM
1.2.1 here, on burst.ga. No issues on my end so far. Block 59805
burstcoin.eu seems out of sync right now!!!
i can read 59793
i can read 59794 now!!!
Yes, I cannot see my outgoing TX for the Lottery on Burstcoin.eu.
http://burst.cryptoport.io/ seems to be on block 59791
January 25, 2015, 03:04:49 PM
1.2.1 here, on burst.ga. No issues on my end so far. Block 59805
burstcoin.eu seems out of sync right now!!!
i can read 59793
i can read 59794 now!!!
January 25, 2015, 03:04:23 PM
1.2.1 here, on burst.ga. No issues on my end so far. Block 59805
burstcoin.eu seems out of sync right now!!!
i can read 59793
January 25, 2015, 03:03:21 PM
Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
all my 3 wallets on 3 machines, 1.2.1 are having problems with a block, however it seems like they are only printing out an exception and then continuing to work. the printout :
Code:
2015-01-25 19:43:08 INFO: get timestamp for tx with id -4762078490203704075 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.processFork(BlockchainProcessorImpl.java:323)
at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:191)
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)
2015-01-25 19:43:09 INFO: tx with id -4762078490203704075 found
2015-01-25 19:43:09 INFO: get timestamp for tx with id -4762078490203704075 found
it seems the problem started somewhere between block 59761 and 59771
all 3 wallets on all 3 different machines give the same error. i would assume something got in via the network, that the software stumbles upon.
That error was caused from a miner that had outdated version. If you restart the wallets you probably will be good
but do you mean there are somebody who is mining in solo with old wallet?
and this cause the fork?
This is very risky
i hope dev can implement a petch to avoid this in futures...
January 25, 2015, 03:02:14 PM
1.2.1 here, on burst.ga. No issues on my end so far. Block 59805
January 25, 2015, 03:01:40 PM
Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....
Yes, everyone has to update to the latest version 1.2.1. Else the AT will cause them to "die". Burstdev gave a lot of time to update to the latest version.
trying to sync with 1.2.1...
i already have updated wallet when it was released...
i will report here...
Jump to: