Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel*

So I took a look at the pool, and the reason most of the miners were showing a 99% error ratios is the pool went off on its own fork.

So I believe this happened because of the very low difficulty ABN affords us.

In light of that, I have decided to shut down ABN.

We have so many exciting things coming at the end of the year, ABN pales in comparison to those things anyway, and I really think we should not divert all of our attention and resources to ABN while we can improve BiblePay in those others areas, especially at the expense of security. (Also, we have chain locks coming, and we can improve our security with chainlocks and accomplish the same thing - roughly in a different way, in September).

SECURITY IS #1 WITH BIBLEPAY

In light of this, ABN is being retired for the time being.

The ABN weight requirement will dissapear in a few more blocks.

In the mean time, Im going to run a report network wide to verify that we have one heavy chain.

The pool is resyncing.

Rob, could you post here the current top block hash ?

I ran my global report, and see no forks at all, so maybe I jumped the gun, but the decision is already complete, I can't go back on it. Let's stay with pure POBH for now.

So the hash is :
getblockhash 128163
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe

Agreeing with our explorer:

https://chainz.cryptoid.info/bbp/block.dws?128163.htm

The pool has resynced to the same block as the explorer; so we don't actually have any forks.

does it mean my sanctuary is out of sync ?

Code:

"protocolversion": 70733,
"balance": 0.00032649,
"blocks": 128158,

# biblepay-cli getblockhash 128163
error code: -8
error message:
Block height out of range

biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7

Yes - please re-sync.

Please, anyone else that disagrees with the 128163 hash posted - please post. Id like to know that no one else other than Tiras' sanctuary disagrees.

Because I ran a report that showed 100% were in agreement to the 128163 hash - not one was out of sync across the world in all datacenters.

I emailed SX to check also.

resyncing controller MN

In the miners wallet though top block is matching your hash but 128158 is different from that on my sanctuary ...

it's unlikely sanctuary went on the fork , right ?

Miner:

Code:

15:43:45

getblockhash 128163
15:43:45
e83e3cd93e304e259b3adf287e79f08f058e9ae4fcc7633722d0146c2a3375fe
15:44:09

getblockhash 128158
15:44:09
92c5bb76c6c01fe1e2582452a223b6273a72cc0c8936c717f2b39c47fdf4161c

Sanc:

Code:

biblepay-cli getblockhash 128158
8fb8d976f0f16150a851605a5ea444ab5c6cf3ca014eea785508ac8e8959d1e7

The correct hash for 128158 was 92c5bb it looks like. I don't know why that sanc went off on a fork (unless it has a strange error in its log right before 128158 height).

But yeah looks like that 128158 sanc needs resynced.