BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[MIP]

So is everyone stuck on 107030?

getblockhash 107030 f17997e81295b768dc801e8d3a3ca15f7e14dc3161dfec45c32da25d0876b7b5

Yep... we probably don't have enough mining power until diff level goes down.

[sunk818]

So is everyone stuck on 107030?

getblockhash 107030 f17997e81295b768dc801e8d3a3ca15f7e14dc3161dfec45c32da25d0876b7b5

Block 107030 would have been the PoG reward block.

If getblockhash 107030 is 744ec6d8871ce4bc627ff6d5cd1ba58f7f36329bcb4f2ca4ac4d965d2b59b493 --- then you're on the 1198 fork.

So is everyone stuck on 107030?

getblockhash 107030 f17997e81295b768dc801e8d3a3ca15f7e14dc3161dfec45c32da25d0876b7b5

Yep... we probably don't have enough mining power until diff level goes down.

Why are 1198 peers connecting to my 1199 client? Shouldn't they be disconnected? If I manually ban 1198 peer, I can get to height 107031

[capulo]

installed from ppa, stucked here. also version only 1.1.9.8:
{
  "version": 1010908,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.9.8",
  "subversion": "/Biblepay Main - Praise Jesus:1.1.9.8/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 33619,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0,
  "testnet": false,
  "keypoololdest": 1552545325,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

[dave_bbp]

Tried resyncing version 1199 on windows and linux, but  all wallets are stuck at 107029 (hash f230b225783f479af743f4dc0fadb732cc633c18030617cfee270356129242fd). Then after a while my windows wallet restarts itself with the following log:

Code:

ERROR: Found invalid chain with higher work (ChainState database corruption likely)
2019-03-14 06:56:00 ERROR: ConnectTip(): ConnectBlock b004cf0af87f1074542b0491123370ac179d2e4f2e4cb25be92a5e9c078aa207 failed
2019-03-14 06:56:00 InvalidChainFound: invalid block=aff336d0359664970b0e1c1599f3fd513904ad19a70d1e351c35ff91761aae6c  height=107020  log2_work=59.188157  date=2019-03-14 01:04:00
2019-03-14 06:56:00 InvalidChainFound:  current best=b58132e1ce51df1fe192c860f404bdf200fd66cf53d1929c7a25588eb7977240  height=107029  log2_work=59.188159  date=2019-03-14 02:04:46
2019-03-14 06:56:00 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2019-03-14 06:56:00
 ERROR: Found invalid chain with higher work (ChainState database corruption likely)
2019-03-14 06:56:00 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2019-03-14 06:56:00
 ERROR: Found invalid chain with higher work (ChainState database corruption likely)
2019-03-14 06:56:00 ProcessNewBlock : ACCEPTED
2019-03-14 06:56:00

 ** Erasing Chain and Rebooting Wallet Now **

Linux wallets just crash like this:

Code:

Written info to mncache.dat  26ms
2019-03-14 07:12:16      Masternodes: 529, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 7, entries in Masternode list we asked for: 22, masternode index size: 529, nDsqCount: 0
2019-03-14 07:12:16 mncache.dat dump finished  30ms
2019-03-14 07:12:16 Verifying mnpayments.dat format...
2019-03-14 07:12:16 ERROR: Read: Failed to open file /home/david/.biblepaycore/mnpayments.dat
2019-03-14 07:12:16 Missing file mnpayments.dat, will try to recreate
2019-03-14 07:12:16 Writting info to mnpayments.dat...
2019-03-14 07:12:16
BiblepayMiner -- terminated
2019-03-14 07:12:17 Written info to mnpayments.dat  338ms
2019-03-14 07:12:17      Votes: 49991, Blocks: 4964
2019-03-14 07:12:17 mnpayments.dat dump finished  372ms
2019-03-14 07:12:17 Verifying governance.dat format...
2019-03-14 07:12:17 ERROR: Read: Failed to open file /home/david/.biblepaycore/governance.dat
2019-03-14 07:12:17 Missing file governance.dat, will try to recreate
2019-03-14 07:12:17 Writting info to governance.dat...
2019-03-14 07:12:17 Written info to governance.dat  147ms
2019-03-14 07:12:17      Governance Objects: 410 (Proposals: 104, Triggers: 305, Watchdogs: 1/1, Other: 0; Seen: 412), Votes: 7961
2019-03-14 07:12:17 governance.dat dump finished  162ms
2019-03-14 07:12:17 Verifying netfulfilled.dat format...
2019-03-14 07:12:17 ERROR: Read: Failed to open file /home/david/.biblepaycore/netfulfilled.dat
2019-03-14 07:12:17 Missing file netfulfilled.dat, will try to recreate
2019-03-14 07:12:17 Writting info to netfulfilled.dat...
2019-03-14 07:12:17 Written info to netfulfilled.dat  1ms
2019-03-14 07:12:17      Nodes with fulfilled requests: 14
2019-03-14 07:12:17 netfulfilled.dat dump finished  1ms
2019-03-14 07:12:17  dumped database files ...

I give up for now and will come back tomorrow to see if everything is running again ...

[vahtis]

installed from ppa, stucked here. also version only 1.1.9.8:
{
  "version": 1010908,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.9.8",
  "subversion": "/Biblepay Main - Praise Jesus:1.1.9.8/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 33619,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0,
  "testnet": false,
  "keypoololdest": 1552545325,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

I did upgrade and it worked ok

Code:

biblepayd --version
Biblepay Core Daemon version 1.1.9.9

[shorty34]

Linux 1.1.9.9 keeps crashing, I get this error:

biblepayd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.

[capulo]

installed from ppa, stucked here. also version only 1.1.9.8:
{
  "version": 1010908,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.9.8",
  "subversion": "/Biblepay Main - Praise Jesus:1.1.9.8/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 33619,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0,
  "testnet": false,
  "keypoololdest": 1552545325,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

I did upgrade and it worked ok

Code:

biblepayd --version
Biblepay Core Daemon version 1.1.9.9

still 1.1.9.8 after upgrade
ubuntu 16.04

Preparing to unpack .../biblepayd_1.1.9.8-xenial1_amd64.deb ...
Unpacking biblepayd (1.1.9.8-xenial1) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up biblepayd (1.1.9.8-xenial1) ...

 apt-cache madison biblepayd
 biblepayd | 1.1.9.8-xenial1 | http://ppa.launchpad.net/biblepay/stable/ubuntu xenial/main amd64 Packages

there is only 9.8 in xenial repo

[eternalenvoy]

In fact, there are now multiple forks and I don't know which one is the right block.
Not just the client wallet, even MN is very confused now. 

[capulo]

finaly 1.1.9.9.from ppa, but still stucked:

{
  "version": 1010909,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.9.9",
  "subversion": "/Biblepay Core:1.1.9.9/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 33619,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 1172.058320117926,
  "testnet": false,
  "keypoololdest": 1552545327,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

[vahtis]

finaly 1.1.9.9.from ppa, but still stucked:

{
  "version": 1010909,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.9.9",
  "subversion": "/Biblepay Core:1.1.9.9/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 33619,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 1172.058320117926,
  "testnet": false,
  "keypoololdest": 1552545327,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

You need to ban all except 1199 nodes to have decent progress

[bible_pay]

Linux 1.1.9.9 keeps crashing, I get this error:

biblepayd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:113: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.

Please resync from block 0; that is a sign you have a block from 1198 stuck in there.

[vahtis]

Most of us cannot get past block 107029.
Wallets get stuck and reboots after a while.
I have deleted blocks and chainstate

[bible_pay]

finaly 1.1.9.9.from ppa, but still stucked:

{
  "version": 1010909,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.9.9",
  "subversion": "/Biblepay Core:1.1.9.9/",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 33619,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 1172.058320117926,
  "testnet": false,
  "keypoololdest": 1552545327,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

You need to ban all except 1199 nodes to have decent progress

Yes, we had that rule in 1199 at first, but I had to comment it out to allow the blocks to sync.

However, things are not as bad as they appear...  Let me make a few comments.

[bible_pay]

Most of us cannot get past block 107029.
Wallets get stuck and reboots after a while.
I have deleted blocks and chainstate

So lets solve this issue in steps, I am positive we can get past it as we've been here before.

First of all:  Anyone who upgraded to 1199 that is past block 107031, Please erase your chain and .dat files (except wallet.dat and .conf file) and restart.
Thats the first problem - you guys are trying to add hashpower to the chain with POG.

I'll comment on the reboot in a minute.

On a side note the client will not reboot if we solve a few blocks on the main chain within the threshhold.  The biggest part of the reboot issue is we only solved one block on the main chain in 8 hours.

[bible_pay]

Ill make a leisure release now with:

- Reboot disabled
- Drop all connections below 1199

In the mean time if we can solve a few blocks on the main chain, all these problems will resolve by themself.

[bible_pay]

We had a feature in called HealthCheckup that would only reboot in the circumstance (where the block spacing > one hour, has not been checked for an hour, and the side chain has more work than the main chain, and the main chain diff is low);

This feature normally will only Reboot Once, but what happened in 1199, since the users on a version < 1199 are still adhering to pog rules, that chain still continues to remain longer (IE with more work), so hence the continual re-assessment and re-boot nuisance.

(Another words, the feature would have worked in normal circumstances, if rebooting caused the client to jump on the longer chain after resyncing but it cant because the longer is invalid now).

So in light of this Im making a new leisure now; the old version is still fine for others once the main chain gets longer.

Compiling...

[bible_pay]

Note:  A reboot is not a crash.

[thesnat21]

We had a feature in called HealthCheckup that would only reboot in the circumstance (where the block spacing > one hour, has not been checked for an hour, and the side chain has more work than the main chain, and the main chain diff is low);

This feature normally will only Reboot Once, but what happened in 1199, since the users on a version < 1199 are still adhering to pog rules, that chain still continues to remain longer (IE with more work), so hence the continual re-assessment and re-boot nuisance.

(Another words, the feature would have worked in normal circumstances, if rebooting caused the client to jump on the longer chain after resyncing but it cant because the longer is invalid now).

So in light of this Im making a new leisure now; the old version is still fine for others once the main chain gets longer.

Compiling...

Are there any "known good" seed nodes currently?

[afeno]

When pureloop will be updated? All miners (42) in the pool are stuck until the pool is updated.

[alm-2000]

I have download new 1.1.9.9 x64 wallet for windows from https://www.biblepay.org/wallet/ . Next clear all (except wallet.dat) anc synchronize. It download all block and start synchronize additional information. When it is completed - the wallet rebooted and began to synchronize again.