synchronization stuck at 494782 | Bitcointalksearch.org

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

btc1 node currently gets stuck at block height 494782.

btc1 is literally incapable of going past block 494782 because that is when they forked (they also forked a block too early) and no one is even mining their blockchain and producing valid blocks to go past that height. You are synced as far as btc1 is able to go.

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

Switching to core node didn't help synchronization. Does anyone know how I can resolve this stuck issue without having to download the entire block chain again?

Install Core and do

Code:

reconsiderblock 000000000000000000386cd4605d5f2481dc5ff02f95b1a4a18749fe51ff90b7

cellard

legendary

Activity: 1372

Merit: 1252

Quote from: kahc on November 19, 2017, 03:49:42 PM

Quote from: tbonetony on November 19, 2017, 02:39:40 PM

Quote from: cellard on November 19, 2017, 02:22:25 PM

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

btc1 node currently gets stuck at block height 494782. Switching to core node didn't help synchronization. Does anyone know how I can resolve this stuck issue without having to download the entire block chain again?

Thanks.

Wait, isn't btc1 the segwit2x client? Why would you try to sync it? as far as I have understood from latest events, segwit2x failed to activate:

https://bitcoinmagazine.com/articles/now-segwit2x-hard-fork-has-really-failed-activate/

So this would mean that even if there were some people adamant to give up on the thing, when they actually tried to fork it was a mess of epic proportions because some bug didn't allow it to happen (so we dodged a bullet... a nuke may I say).

So I don't see the point in trying to sync the node, no exchanges even listed the token afaik.

yes btc1 is the s2x node. I was running btc1 node until it got stuck at 494782, then I switched to core 0.15.1 in hope that synchronization would continue but it didn't. I would like to know how can I fix it as I don't want to spend another 2 weeks downloading the entire chain.

I am currently trying with cmd "invalidateblock 0000000000000000011865af4122fe3b144e2cbeea86142e8ff2fb4107352d43" (block 478558) as per https://www.btcforkmonitor.info/ that s2x and core nodes were on the same ancestor block at then, if I understand it correctly. However, this is taking long time.

If anyone knows how this can be fixed, that would be much appreciated. There are a lot of articles online reporting the mess of btc1 screwed up at 494782, but I haven't found a solution for how this can be fixed.

The rogue developer jgarzik claims to have fixed the freeze bug, but the code is not reviewed by other developers. So use at your own discretion.
https://github.com/btc1/bitcoin/commit/d09f3decfa2806515a0504be927c4384d6241dba
https://github.com/btc1/bitcoin/releases

But I seriously doubt it will be working for long,if working at all. The other developers say that the code is full of bugs

Indeed, I wouldn't trust this code at all, same as I didn't trust Bitcoin Cash so I had to install it on a secondary computer.

OP I recommend you that you don't install this code on your main system or anywhere where your private keys are sitting. If you can't afford a secondary computer to install experimental wallets or in general software of obvious precedence, at least make the effort to set up a Virtual Machine to install it. Also never import private keys on other wallets, simply send the coins from wallet A to wallet B, remember that.

tbonetony

sr. member

Activity: 441

Merit: 250

No zuo no die why you try, u zuo u die dont be shy

Quote from: Foxpup on November 19, 2017, 10:13:42 PM

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

btc1 node currently gets stuck at block height 494782.

So? Everyone knew about this bug for months in advance and the "developers" (if they can so be called) never fixed it. Anyone who insists on using software known to be this incompetently developed deserves whatever they get, in my opinion.

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

Switching to core node didn't help synchronization.

The chainstates are incompatible. You will need to run Core with the -reindex-chainstate parameter to fix it. Don't ever run any two of SegWit2x, Bitcoin Cash, and Bitcoin Core with the same data directory. Nothing good will come of it.

Yes, I agree it's what I deserved for mistrusting them Sad

I am already re-running with reindex-chainstate since half a day ago. Was planning to run reindex if this doesn't help.

Thank you very much for your suggestion.

Foxpup

legendary

Activity: 4536

Merit: 3188

Vile Vixen and Miss Bitcointalk 2021-2023

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

btc1 node currently gets stuck at block height 494782.

So? Everyone knew about this bug for months in advance and the "developers" (if they can so be called) never fixed it. Anyone who insists on using software known to be this incompetently developed deserves whatever they get, in my opinion.

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

Switching to core node didn't help synchronization.

The chainstates are incompatible. You will need to run Core with the -reindex-chainstate parameter to fix it. Don't ever run any two of SegWit2x, Bitcoin Cash, and Bitcoin Core with the same data directory. Nothing good will come of it.

kahc

member

Activity: 350

Merit: 13

Quote from: tbonetony on November 19, 2017, 02:39:40 PM

Quote from: cellard on November 19, 2017, 02:22:25 PM

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

btc1 node currently gets stuck at block height 494782. Switching to core node didn't help synchronization. Does anyone know how I can resolve this stuck issue without having to download the entire block chain again?

Thanks.

Wait, isn't btc1 the segwit2x client? Why would you try to sync it? as far as I have understood from latest events, segwit2x failed to activate:

https://bitcoinmagazine.com/articles/now-segwit2x-hard-fork-has-really-failed-activate/

So this would mean that even if there were some people adamant to give up on the thing, when they actually tried to fork it was a mess of epic proportions because some bug didn't allow it to happen (so we dodged a bullet... a nuke may I say).

So I don't see the point in trying to sync the node, no exchanges even listed the token afaik.

yes btc1 is the s2x node. I was running btc1 node until it got stuck at 494782, then I switched to core 0.15.1 in hope that synchronization would continue but it didn't. I would like to know how can I fix it as I don't want to spend another 2 weeks downloading the entire chain.

I am currently trying with cmd "invalidateblock 0000000000000000011865af4122fe3b144e2cbeea86142e8ff2fb4107352d43" (block 478558) as per https://www.btcforkmonitor.info/ that s2x and core nodes were on the same ancestor block at then, if I understand it correctly. However, this is taking long time.

If anyone knows how this can be fixed, that would be much appreciated. There are a lot of articles online reporting the mess of btc1 screwed up at 494782, but I haven't found a solution for how this can be fixed.

The rogue developer jgarzik claims to have fixed the freeze bug, but the code is not reviewed by other developers. So use at your own discretion.
https://github.com/btc1/bitcoin/commit/d09f3decfa2806515a0504be927c4384d6241dba
https://github.com/btc1/bitcoin/releases

But I seriously doubt it will be working for long,if working at all. The other developers say that the code is full of bugs

tbonetony

sr. member

Activity: 441

Merit: 250

No zuo no die why you try, u zuo u die dont be shy

Quote from: cellard on November 19, 2017, 02:22:25 PM

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

btc1 node currently gets stuck at block height 494782. Switching to core node didn't help synchronization. Does anyone know how I can resolve this stuck issue without having to download the entire block chain again?

Thanks.

Wait, isn't btc1 the segwit2x client? Why would you try to sync it? as far as I have understood from latest events, segwit2x failed to activate:

https://bitcoinmagazine.com/articles/now-segwit2x-hard-fork-has-really-failed-activate/

So this would mean that even if there were some people adamant to give up on the thing, when they actually tried to fork it was a mess of epic proportions because some bug didn't allow it to happen (so we dodged a bullet... a nuke may I say).

So I don't see the point in trying to sync the node, no exchanges even listed the token afaik.

yes btc1 is the s2x node. I was running btc1 node until it got stuck at 494782, then I switched to core 0.15.1 in hope that synchronization would continue but it didn't. I would like to know how can I fix it as I don't want to spend another 2 weeks downloading the entire chain.

I am currently trying with cmd "invalidateblock 0000000000000000011865af4122fe3b144e2cbeea86142e8ff2fb4107352d43" (block 478558) as per https://www.btcforkmonitor.info/ that s2x and core nodes were on the same ancestor block at then, if I understand it correctly. However, this is taking long time.

If anyone knows how this can be fixed, that would be much appreciated. There are a lot of articles online reporting the mess of btc1 screwed up at 494782, but I haven't found a solution for how this can be fixed.

cellard

legendary

Activity: 1372

Merit: 1252

Quote from: tbonetony on November 19, 2017, 02:14:21 PM

btc1 node currently gets stuck at block height 494782. Switching to core node didn't help synchronization. Does anyone know how I can resolve this stuck issue without having to download the entire block chain again?

Thanks.

Wait, isn't btc1 the segwit2x client? Why would you try to sync it? as far as I have understood from latest events, segwit2x failed to activate:

https://bitcoinmagazine.com/articles/now-segwit2x-hard-fork-has-really-failed-activate/

So this would mean that even if there were some people adamant to give up on the thing, when they actually tried to fork it was a mess of epic proportions because some bug didn't allow it to happen (so we dodged a bullet... a nuke may I say).

So I don't see the point in trying to sync the node, no exchanges even listed the token afaik.

tbonetony

sr. member

Activity: 441

Merit: 250

No zuo no die why you try, u zuo u die dont be shy

btc1 node currently gets stuck at block height 494782. Switching to core node didn't help synchronization. Does anyone know how I can resolve this stuck issue without having to download the entire block chain again?

Thanks.

Topic: synchronization stuck at 494782 (Read 429 times)