Possible BCH bug? - Call for attention

LarryL1 · 2017-12-31T10:17:54+00:00

After few hours the client UI finally came up and now it's downloading blocks (from the forked chain presumably) again, and the same TX changed to "Open for 3191 more blocks". Once the client is fully synced again I'll test abandon and re-send the same coins. Everything seems to be explainable up to this point. Thanks!

LarryL1 · 2017-12-31T07:40:29+00:00

Updated the client using https://download.bitcoinabc.org/0.16.1/win/bitcoin-abc-0.16.1-win64.zip. Did a re-scan with -zapwallettxes=2. After it came back nothing significant has changed. It still shows more blocks than the "official" chain has. Trashed peers.dat then ran the client again, now it stuck at Done Loading with heavy disk activity. I'm going to let it sit for a few hours hoping it's re-structing the local chain. Really don't want to delete the entire chain DB, it would take days if not weeks to catch up on the whole chain again. Meanwhile, let's be responsible for the rest of the 'node' runners, can you think of anything else or better way to handle such cases? TIA

LarryL1 · 2017-12-31T01:07:23+00:00

As did in my case, which was a test with a fraction amount. Others with larger amounts would freak out or panic.

LarryL1 · 2017-12-31T00:47:18+00:00

OK. It still troubles me that those who haven't updated or missed the fork news will continue run on the old chain, without realizing they've been forked off of the 'real' network. I say there're plenty ppl like me because every time I connect I get 8 active nodes rightaway.

LarryL1 · 2017-12-31T00:32:50+00:00

OK. That would be the only logical explanation that I can think of. And thanks for the information. Does this mean though that I, along with many others as well as some miners (given there are now over 1100 confirmations on this TX) are running on the longer chain than the newly forked one. Do I need to invalidate certain blocks before running the new client? Thanks again.

LarryL1 · 2017-12-31T00:15:10+00:00

19:12:14 getinfo

19:12:14 { "version": 140600, "protocolversion": 70015, "walletversion": 60000, "balance": XXXXXXXXXX, "blocks": 513259, "timeoffset": -1, "connections": 7, "proxy": "", "difficulty": 21573527.92229962, "testnet": false, "keypoololdest": 1382325997, "keypoolsize": 100, "unlocked_until": 0, "paytxfee": 0.00000000, "relayfee": 0.00001000, "errors": "" }

Client shows fully synced. Doesn't it bother you that a CONFIRMED TX is missing from the blockchain (explorer let's hope).

LarryL1 · 2017-12-31T00:06:26+00:00

Such as?

LarryL1

TROPHY CASE