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

[pinballdude]

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....

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?

[xizmax]

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....

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

[vbcs]

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....

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

[vbcs]

Just got block 59807 with basetarget 2828857

[xizmax]

Just got block 59807 with basetarget 2828857

59809, basetarget 2772743

Looks like we got multiples

[pinballdude]

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....

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

[vbcs]

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.

[xizmax]

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

[vbcs]

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!!   

[pinballdude]

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.

[DazzlinDave™]

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.

[xizmax]

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

[vbcs]

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 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.

[bensam123]

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.

[mmmaybe]

1.2.1 here, on burst.ga. No issues on my end so far. Block 59805

The same. Solo and on dev's pool.

Bought some more tickets too.

[xizmax]

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 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.

Sounds like a reasonable explanation. One could speculate on who owns those nodes

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.

It is not hard to imagine that one could have a significant portion of power if he has access to lots of storage (like the alleged datacenter speculated to be responsible for diff swings), especially since the network isn't overly large

1.2.1 here, on burst.ga. No issues on my end so far. Block 59805

The same. Solo and on dev's pool.

Bought some more tickets too.

Man, you so gonna win this

[mmmaybe]

This was just released from the PR Team:

Press Release: An historic event in cryptocurrency: BURST successively launched a Smart Contract

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are utterly delighted to follow up on our press release on BURST’s implementation of Smart Contracts (2015-01-22), with a depiction of an actual case where these innovations are utilized. Due to their many areas of implementation and strong security, Smart Contracts (SC), sometimes referred to as Automated Transactions (AT), has recently become the center of discussions and development in the world of crypto.

Should this technology spread, it is not unimaginable that the financial sector will need to reorganize to a certain degree. Simply put, SC enable numerous and various operations to be run on a traditional blockchain – created by ordinary users without institutions and intermediaries. Cryptocurrencies Counterparty and Ethereum have eagerly tried to develop SCs, but so far failed.

Today, 2015-01-25, at 01:24:10 PM (GMT), a completely decentralized Lottery was launched on BURST's blockchain. Holders of the BURST currency, which is traded at poloniex.com and bittrex.com, could shortly thereafter buy tickets for 2000 a piece (appr. 0.00344 BTC). The bought tickets are processed by the preprogrammed code on the blockchain and will both automatically and completely randomly chose a winner as well as transfer the whole sum of all sold tickets to the winner's BURST account.

This proofs that BURST not only in theory, as reported earlier, but also in reality has successively developed the highly advanced SC technology. Although the BURST lottery will continue to run on a weekly basis for everyone to take part in, the lottery case will lay ground for much more advanced SCs.

More details are found in the below press release and the supplied references, where also contact details are found:

http://burstcoin.info/sc/TheLotteryCase.pdf

The earlier press release on BURST's SCs is found here:
http://burstcoin.info/SmartContracts.pdf

Looking forward to hear from you!

Regards,
BURST's PR Team
-----BEGIN PGP SIGNATURE-----

[xizmax]

This was just released from the PR Team:

Press Release: An historic event in cryptocurrency: BURST successively launched a Smart Contract

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

We are utterly delighted to follow up on our press release on BURST’s implementation of Smart Contracts (2015-01-22), with a depiction of an actual case where these innovations are utilized. Due to their many areas of implementation and strong security, Smart Contracts (SC), sometimes referred to as Automated Transactions (AT), has recently become the center of discussions and development in the world of crypto.

Should this technology spread, it is not unimaginable that the financial sector will need to reorganize to a certain degree. Simply put, SC enable numerous and various operations to be run on a traditional blockchain – created by ordinary users without institutions and intermediaries. Cryptocurrencies Counterparty and Ethereum have eagerly tried to develop SCs, but so far failed.

Today, 2015-01-25, at 01:24:10 PM (GMT), a completely decentralized Lottery was launched on BURST's blockchain. Holders of the BURST currency, which is traded at poloniex.com and bittrex.com, could shortly thereafter buy tickets for 2000 a piece (appr. 0.00344 BTC). The bought tickets are processed by the preprogrammed code on the blockchain and will both automatically and completely randomly chose a winner as well as transfer the whole sum of all sold tickets to the winner's BURST account.

This proofs that BURST not only in theory, as reported earlier, but also in reality has successively developed the highly advanced SC technology. Although the BURST lottery will continue to run on a weekly basis for everyone to take part in, the lottery case will lay ground for much more advanced SCs.

More details are found in the below press release and the supplied references, where also contact details are found:

http://burstcoin.info/sc/TheLotteryCase.pdf

The earlier press release on BURST's SCs is found here:
http://burstcoin.info/SmartContracts.pdf

Looking forward to hear from you!

Regards,
BURST's PR Team
-----BEGIN PGP SIGNATURE-----

Awesome work, thanks to all who made this possible!

[elturco]

hi all

im getting "unable to get mining info from wallet" error. im using devs pool v2. and wallet 1.2.1 not sync now. what is the problem. how can i fix this.

thanks.

[pinballdude]

i restarted my wallets and they updated, but they still (all 3 of them) caught the same alternative chain.

The chain i have has the last transaction now as 59801  basetarget is 6956490

anyone else on this chain, and importantly, anyone managed to get over to the new one?

on 59801 i have this transaction, amongst others :

08:00:05 222.36306539 1  BURST-BHR8-54QN-J99D-B8KZ6  from  BURST-LGKU-3UUM-M6Q5-86SLK

back on 59770 my blocks matches burst explorer http://burst.cryptoport.io/   but it seems to have stopped there and is not showing newer blocks.

my wallets still report the tx with id -4762078490203704075 error, but it seems that they manage to get updated with new blocks (from the wrong chain) anyways.


amongst my peers i have wallet.burstcoin.io and burstcoin.eu  should they not be up to date? perhaps not the first is 1.1.5 the next is 1.2.0

also connected to CLVN.PRIVATEDNS.ORG:8123 and rsr.asuscommo.com  and burst.shmtech.biz

the others are just plain ip addresses. most are running 1.2.1

seems like it is hard to leave the wrong chain, but i guess all i can do is try to restart until the wallet decides to catch on to the other chain. Any other suggestions?