Quote from: eternalenvoy on July 20, 2019, 07:14:33 AM

Quote from: MIP on July 19, 2019, 07:38:35 AM

I would say http://explorer.biblepay.org:3001 is stuck in block 132234 (we are now like 436 blocks ahead that)

It's not forked because blockhashes match.

Official Explorer seem have problem since the block already @132880 now.
Also found it seem have a fork problem?Even I deleted all files and reindex, few days later , some wallet show different blockhash(config are same, maybe some nodes are moving on the wrong road, and some of my machines are coincidentally connected to the node which is on wrong direction.).

getblockhash 132863

(chainz.cryptoid.info is on this way)
f8ef624e2e81b666f48c6ecef6a18d5ec789c323b71f10d6b31911efe7db8457

186e46fb047626477e400f644497b85e7c202a7512301595c9269c774de5cff3

I just ran my global sanc report and 100% of the nodes are in agreement with Chainz and my local node and the pool:

getblockhash 132922

03fe0f4fbd2ab5848404eb4dfddc543a1f759711201d4841af0169e2d4467e31

In this case it looks like explorer.biblepay.org is wrong - please resync the chain with the -erasechain=1.
Ive seen this happen after a reindex (reindex is not good for Biblepay, we will need to address this right now for the next version. Im adding to my punchlist now).

If anyone ever goes out of sync, please start with -erasechain=1 and dont do the reindex suggestion that other communities use. (It does not clean up governance at all and cant handle compact blocks or non fin tx or prayers or SAN data leaving your node in a corrupt state).

EDIT: explorer.biblepay.org is not forked - its stuck on a block 500 blocks back (look at its hash)

I wonder if we should retire this explorer - if its going to be unreliable. Togo, can you reset it?