Re: BiblePay | 10% to Orphan-Charity | POBH CPU

is the chain healthy? some saying they got on a fork.

Yeah, diff is still 177,000.

I don't see any signs of it.

did you upgrade all your nodes to latest?
what about those that did not?

Looking at the Mandatory upgrade post, the cutover height is not until 166075.

I've been away and still running 1484. I saw that my wallet had a lot of mined blocks and these warnings saying blocks have unexpected version, bad lexical cast, and block heights that do not match explorer.biblepay.org nor chainz. I'm about 15 blocks behind.

I had 20 blocks that were found on the wrong chain: http://sunpool.whitewalr.us/tbs

The difficulty has been under 100k recently as far I can tell.

Apparently, there's been a spike of orphans lately too.

2019-12-22 20:20:28 {PNB}: ACC UpdateTip: new best=255568dadbe9913d94e18fa4378adc773d35643a4fbd7166877339cc02c04925 height=165102 version=0x20000000 log2_work=60.05644645 tx=1186215 date='2019-12-22 20:08:47' progress=0.999994 cache=0.0MiB(0txo) warning='4 of last 100 blocks have unexpected version'
2019-12-22 20:20:29 {PNB}: ACC caught cdbl bad lexical cast 1 from with 0.000000UpdateTip: new best=ce781a158c37e79d86340d70923030bedda334b57ffa80c7b1d55e51549d02ed height=165103 version=0x20000000 log2_work=60.05644873 tx=1186217 date='2019-12-22 20:22:47' progress=0.999999 cache=0.0MiB(0txo) warning='3 of last 100 blocks have unexpected version'
2019-12-22 20:23:48 {PNB}: ACC caught cdbl bad lexical cast 1 from with 0.000000Misbehaving: 45.76.120.35:40000 peer=17 (0 -> 1)
2019-12-22 20:19:12 ERROR: ConnectBlock(): ProcessSpecialTxsInBlock for block 81e8883fdb4c065ff6c6de64e169fa0730e8b15d3e3c7dc2988939cdbeab82bd failed with bad-qc-invalid-null (code 16)

Can you please try upgrading next? Ive already upgraded my sancs and home node, and the exchanges have upgraded, so at this point it would be counterproductive for me to downgrade just to see if they are on a fork. We can ask others, if anyone else is running the old version if they are going on a fork?

Whats very possible is that once 51% of the sancs moved to the new version (70750), it probably became the defacto. You can see if your 'exec health' disagrees on the old version with the new version, but I just recommend upgrading now.

Btw, I plan on enabling Kairos later today, so please watch so we can start sponsoring after that. As I feel we will have a lot to do starting tomorrow to roll out WCG. I plan on enabling WCG tomorrow.