|
Title: Segwit 2x activation today??? Post by: filharvey on November 17, 2017, 01:21:13 PM It is said that some small group of miners and some crypto traders, who have already converted their bitcoins in to B2X futures have decided to continue with segwit 2x activation.GDAX and coinbase have already announced that they would temporarily freeze the bitcoin transactions for 6 hours.It is said that this was also a reason for bitcoin rally today.It is said that even if segwit2x coins are received freely,coinbase will not allow to trade or withdraw these coins due to the lack of miner support.The fork is expected to take place when blockchain reaches the block number 494,784
.Let us wait and see the consequences. Title: Re: Segwit 2x activation today??? Post by: ladydark on November 18, 2017, 02:06:47 PM The attempt for Segwit2 activation yesterday finally failed.Its mainly due to the lack of base block larger than 1 MB size.But due to so called off by error,segwit2x blocks started rejecting smaller blocks at block 494,783 instead of 494,784 where hard fork was expected to occur.Even another btc bug1 also prevented miners from mining bigger block.That's the reason for falure of another attempt.
Title: Re: Segwit 2x activation today??? Post by: Marileno on November 18, 2017, 02:10:27 PM It is not going ahead. There were errors in the code. This is widely publicised.
Title: Re: Segwit 2x activation today??? Post by: BrewMaster on November 18, 2017, 02:12:17 PM ts mainly due to the lack of base block larger than 1 MB size. there is no lack of transactions for sure this time ;)Quote But due to so called off by error,segwit2x blocks started rejecting smaller blocks at block 494,783 instead of 494,784 where hard fork was expected to occur.Even another btc bug1 also prevented miners from mining bigger block.That's the reason for falure of another attempt. what is this error you are talking about? there is no hashrate to mine a block! or in other words none of the miners are mining bigger blocks on SegWit2x so far that is why there has not been any new blocks there, i am not aware of any bugs. please explain if i am missing something. Title: Re: Segwit 2x activation today??? Post by: RockDaddy on November 18, 2017, 04:14:43 PM ts mainly due to the lack of base block larger than 1 MB size. there is no lack of transactions for sure this time ;)Quote But due to so called off by error,segwit2x blocks started rejecting smaller blocks at block 494,783 instead of 494,784 where hard fork was expected to occur.Even another btc bug1 also prevented miners from mining bigger block.That's the reason for falure of another attempt. what is this error you are talking about? there is no hashrate to mine a block! or in other words none of the miners are mining bigger blocks on SegWit2x so far that is why there has not been any new blocks there, i am not aware of any bugs. please explain if i am missing something. Yes you are missing something. Simply google it. Title: Re: Segwit 2x activation today??? Post by: TryNinja on November 18, 2017, 04:33:26 PM what is this error you are talking about? there is no hashrate to mine a block! or in other words none of the miners are mining bigger blocks on SegWit2x so far that is why there has not been any new blocks there, i am not aware of any bugs. please explain if i am missing something. Quote For some reason all btc1/B2X nodes seem stuck at block height 494782 instead of 494783. (The fork was supposed to occur at 494784, so btc1/B2X nodes should have accepted block 494783 as normal.) https://twitter.com/AaronvanW/status/931513254861471749Quote tl;dr: @jgarzik's 2x HF just failed due to an off-by-one error, w/ the root cause being the idiotic "activation block must be >1MB" HF logic (already failed before in a similar way on testnet). https://twitter.com/petertoddbtc/status/931547098625052672Fact is, no competent devs worked on 2x, b/c competent devs know it's a dumb idea. Title: Re: Segwit 2x activation today??? Post by: mrayazgul on November 18, 2017, 04:38:19 PM It is said that some small group of miners and some crypto traders, who have already converted their bitcoins in to B2X futures have decided to continue with segwit 2x activation.GDAX and coinbase have already announced that they would temporarily freeze the bitcoin transactions for 6 hours.It is said that this was also a reason for bitcoin rally today.It is said that even if segwit2x coins are received freely,coinbase will not allow to trade or withdraw these coins due to the lack of miner support.The fork is expected to take place when blockchain reaches the block number 494,784 .Let us wait and see the consequences. I think it will not succeed due to lack of miner support but even though it succeed for fork, and as coinbase told they wont support it, they are indeed wrong. If you remember, when bitcoin was fork with bitcoin cash , coinbase did not also support it at first. But then they had to admit it and gave their consumers the BCH. Similarly if the fork ever happens again, coinbase users need not to worry. They will get the forked coins if not on the same day but after a few days. Title: Re: Segwit 2x activation today??? Post by: Reid on November 18, 2017, 04:57:36 PM It is said that some small group of miners and some crypto traders, who have already converted their bitcoins in to B2X futures have decided to continue with segwit 2x activation.GDAX and coinbase have already announced that they would temporarily freeze the bitcoin transactions for 6 hours.It is said that this was also a reason for bitcoin rally today.It is said that even if segwit2x coins are received freely,coinbase will not allow to trade or withdraw these coins due to the lack of miner support.The fork is expected to take place when blockchain reaches the block number 494,784 .Let us wait and see the consequences. Why are they forcing it? Links for the certain talk about this please? Crypto traders can decide if it will go on or not? What the hell is happening? They cancelled it so shouldnt it be from them also that will say it will continue or be resumed. I am not basher but I find this thread questionable or just a FUD. |