BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

Yeah, to find out why it doesnt sync, you have to set debug=true and debugmaster=true first then look for the last line before repeating entries.

Unfortuantely 1051 has a breaking bug (growing pains of Temples I guess).  I cant guarantee the next version will solve everything.

But it appears the last version was capable of Paying temples, syncing When already synced, sharing info about the temples to the other sanctuaries, but where it hosed up, is during fresh syncs from zero and when its masternodes were not synced.

I have to go in baby steps because sometimes after we fix somethng it cascades to a new issue.

So All, please upgrade to 1052 now and lets try this again.  We will all need to reindex afterwards after upgrading  to ensure the blocks from 24 hours ago are pulled in the chain with headers.

The 1052 version is out now on github.

Updating right now

I added  debug=true and debugmaster=true to the biblepay.conf, but I'm not exactly sure what to look for in the log, or if I'm even in looking in the right place. But here is a log of a complete startup and shutdown:

Code: [Select]

2017-10-29 15:48:21 Biblepay Core version 1.0.4.8 (2017-10-06 11:29:31 -0500)
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -listen=0 -> setting -upnp=0
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -listen=0 -> setting -discover=0
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -listen=0 -> setting -listenonion=0
2017-10-29 15:48:21 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-10-29 15:48:21 GUI: libpng warning: bKGD: invalid
2017-10-29 15:48:21 GUI: setGeometryDp: Unable to set geometry 5x13+320+252 on QWidgetWindow/'QLabelClassWindow'. Resulting geometry:  116x13+320+252 (frame: 8, 30, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 0x0, maximum size: 16777215x16777215).
2017-10-29 15:48:21 ProdMode: Prod 0.000000GUI: "registerShutdownBlockReason: Successfully registered: Biblepay Core didn't yet exit safely..."
2017-10-29 15:48:22   thread
 category true
2017-10-29 15:48:22 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-10-29 15:48:22 Default data directory C:\Users\JAAP\AppData\Roaming\BiblepayCore
2017-10-29 15:48:22 Using data directory C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3
2017-10-29 15:48:22 Using config file C:\Users\JAAP\AppData\Roaming\BiblepayCore\biblepay.conf
2017-10-29 15:48:22 Using at most 256 connections (2048 file descriptors available)
2017-10-29 15:48:22 Using 4 threads for script verification
2017-10-29 15:48:22 scheduler thread start
2017-10-29 15:48:25 libevent: getaddrinfo: no address associated with nodename
2017-10-29 15:48:25 Binding RPC on address :: port 39001 failed.
2017-10-29 15:48:25 HTTP: creating work queue of depth 16
2017-10-29 15:48:25 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2017-10-29 15:48:25 HTTP: starting 4 worker threads
2017-10-29 15:48:25   thread  category true
2017-10-29 15:48:25 Creating backup of C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\wallet.dat -> C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\backups\wallet.dat.2017-10-29-15-48
2017-10-29 15:48:25 Using wallet wallet.dat
2017-10-29 15:48:25 init message: Verifying wallet...
2017-10-29 15:48:25 CDBEnv::Open: LogDir=C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\database ErrorFile=C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\db.log
2017-10-29 15:48:25 init message: Init KJV Bible...
2017-10-29 15:48:25 init message: Loading KJV Bible...
2017-10-29 15:48:25 s1 e5aff8cff54256fe8ee133467eed3af0, s2 e409eb2ba6eb6801f52763ae370c350e
2017-10-29 15:48:25 Cache configuration:
2017-10-29 15:48:25 * Using 12.5MiB for block index database
2017-10-29 15:48:25 * Using 29.9MiB for chain state database
2017-10-29 15:48:25 * Using 57.6MiB for in-memory UTXO set
2017-10-29 15:48:25 init message: Loading block index...
2017-10-29 15:48:25 Opening LevelDB in C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\blocks\index
2017-10-29 15:48:25 Opened LevelDB successfully
2017-10-29 15:48:25 Using obfuscation key for C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\blocks\index: 0000000000000000
2017-10-29 15:48:25 Opening LevelDB in C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\chainstate
2017-10-29 15:48:25 Opened LevelDB successfully
2017-10-29 15:48:25 Using obfuscation key for C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\chainstate: 5cd10f0687210f92
2017-10-29 15:48:27 LoadBlockIndexDB: last block file = 0
2017-10-29 15:48:27 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=25733, size=6380886, heights=0...25721, time=2017-06-01...2017-10-29)
2017-10-29 15:48:27 Checking all blk files are present...
2017-10-29 15:48:27 LoadBlockIndexDB: transaction index enabled
2017-10-29 15:48:27 LoadBlockIndexDB: address index disabled
2017-10-29 15:48:27 LoadBlockIndexDB: timestamp index disabled
2017-10-29 15:48:27 LoadBlockIndexDB: spent index disabled
2017-10-29 15:48:27 LoadBlockIndexDB: hashBestChain=40ba5c7e1abd08349294010793155e0aa371e7595267703c37b842041a12c085 height=25684 date=2017-10-28 16:16:51 progress=0.027892
2017-10-29 15:48:27 init message: Verifying blocks...
2017-10-29 15:48:27 Verifying last 288 blocks at level 3
2017-10-29 15:48:28 No coin database inconsistencies in last 289 blocks (294 transactions)
2017-10-29 15:48:28  block index            3550ms
2017-10-29 15:48:28 init message: Loading wallet...
2017-10-29 15:48:28 nKeysLeftSinceAutoBackup: 1001
2017-10-29 15:48:28 nFileVersion = 1000408
2017-10-29 15:48:28 Keys: 1072 plaintext, 0 encrypted, 1072 w/ metadata, 1072 total
2017-10-29 15:48:29  wallet                  234ms
2017-10-29 15:48:29 init message: Activating best chain...
2017-10-29 15:48:29 Using masternode config file C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\masternode.conf
2017-10-29 15:48:29 Locking Masternodes:
2017-10-29 15:48:29   a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4 1 - locked successfully
2017-10-29 15:48:29 fLiteMode 0
2017-10-29 15:48:29 nInstantSendDepth 5
2017-10-29 15:48:29 PrivateSend rounds 2
2017-10-29 15:48:29 PrivateSend amount 1000
2017-10-29 15:48:29 init message: Loading masternode cache...
2017-10-29 15:48:29 Reading info from mncache.dat...
2017-10-29 15:48:29 Loaded info from mncache.dat  0ms
2017-10-29 15:48:29      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:48:29 Read: Cleaning....
2017-10-29 15:48:29      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:48:29 init message: Masternode cache is empty, skipping payments and governance cache...
2017-10-29 15:48:29 init message: Loading fulfilled requests cache...
2017-10-29 15:48:29 Reading info from netfulfilled.dat...
2017-10-29 15:48:29 Loaded info from netfulfilled.dat  0ms
2017-10-29 15:48:29      Nodes with fulfilled requests: 3
2017-10-29 15:48:29 Read: Cleaning....
2017-10-29 15:48:29      Nodes with fulfilled requests: 1
2017-10-29 15:48:29 init message: Memorizing Prayers...
2017-10-29 15:48:30 CMasternodeSync::ProcessTick1 -- nTick 1 nRequestedMasternodeAssets 0 nRequestedMasternodeAttempt 0 nSyncProgress -0.250000
2017-10-29 15:48:30 CMasternodeSync::SwitchToNextAsset -- Starting MASTERNODE_SYNC_SPORKS
2017-10-29 15:48:36 CMasternodeSync::ProcessTick1 -- nTick 7 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:42 CMasternodeSync::ProcessTick1 -- nTick 13 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:44 mapBlockIndex.size() = 26284
2017-10-29 15:48:44 chainActive.Height() = 25684
2017-10-29 15:48:44 setKeyPool.size() = 1001
2017-10-29 15:48:44 mapWallet.size() = 2515
2017-10-29 15:48:44 mapAddressBook.size() = 7
2017-10-29 15:48:44 init message: Loading addresses...
2017-10-29 15:48:44 ERROR: Read: Failed to open file C:\Users\JAAP\AppData\Roaming\BiblepayCore\testnet3\banlist.dat
2017-10-29 15:48:44 Invalid or missing banlist.dat; recreating
2017-10-29 15:48:44 Loaded 221 addresses from peers.dat  0ms
2017-10-29 15:48:44 dnsseed thread start
2017-10-29 15:48:44 net thread start
2017-10-29 15:48:44 addcon thread start
2017-10-29 15:48:44 init message: Done loading
2017-10-29 15:48:44 msghand thread start
2017-10-29 15:48:44 opencon thread start
2017-10-29 15:48:44 mnbcon thread start
2017-10-29 15:48:44   thread  category true
2017-10-29 15:48:44 AddToWallet 2b9c7e1ce2cd5303e8e4094ffc0e3fbc727404544e6b4376dbb59f82f4231334 
2017-10-29 15:48:44   thread
 category true
2017-10-29 15:48:44 GUI: Platform customization: "windows"
2017-10-29 15:48:44 GUI: PaymentServer::LoadRootCAs: Loaded  49  root certificates
2017-10-29 15:48:45   thread  category true
2017-10-29 15:48:45   thread  category true
2017-10-29 15:48:45 receive version message: /Biblepay Core:1.0.4.8/: version 70708, blocks=25684, us=84.29.208.33:54553, peer=1
2017-10-29 15:48:48 CMasternodeSync::ProcessTick1 -- nTick 19 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:55 CMasternodeSync::ProcessTick1 -- nTick 25 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:48:55 Loading addresses from DNS seeds (could take a while)
2017-10-29 15:48:56 receive version message: /Biblepay Core:1.0.5.1/: version 70708, blocks=25752, us=84.29.208.33:54557, peer=2
2017-10-29 15:48:57 ERROR: AcceptBlockHeader: block is marked invalid
2017-10-29 15:48:57 ERROR: invalid header received 08fd212a444c97384e70f6ea93f96d6269e897dab68dd184769fa3b0ea7df3a8
2017-10-29 15:48:57 ProcessMessages(headers, 45039 bytes) FAILED peer=2
2017-10-29 15:48:57 receive version message: /Biblepay Core:1.0.5.1/: version 70708, blocks=26233, us=84.29.208.33:54558, peer=3
2017-10-29 15:48:58   thread  category true
2017-10-29 15:48:58 15 addresses found from DNS seeds
2017-10-29 15:48:58 dnsseed thread exit
2017-10-29 15:49:01 CMasternodeSync::ProcessTick1 -- nTick 31 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:01   thread ‰ˆˆˆ category true
2017-10-29 15:49:01 CMasternodeSync::ProcessTick4 -- nTick 31 nRequestedMasternodeAssets 1 -- requesting sporks from peer 2
2017-10-29 15:49:01 CMasternodeSync::ProcessTick4 -- nTick 31 nRequestedMasternodeAssets 1 -- requesting sporks from peer 3
2017-10-29 15:49:07 CMasternodeSync::ProcessTick1 -- nTick 37 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:14 CMasternodeSync::ProcessTick1 -- nTick 43 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:20 CMasternodeSync::ProcessTick1 -- nTick 49 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:26 CMasternodeSync::ProcessTick1 -- nTick 55 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:33 CMasternodeSync::ProcessTick1 -- nTick 61 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:33 CMasternodeSync::ProcessTick4 -- nTick 61 nRequestedMasternodeAssets 1 -- requesting sporks from peer 1
2017-10-29 15:49:39 CMasternodeSync::ProcessTick1 -- nTick 67 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:45 CMasternodeSync::ProcessTick1 -- nTick 73 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:51 CMasternodeSync::ProcessTick1 -- nTick 79 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:49:58 CMasternodeSync::ProcessTick1 -- nTick 85 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:04 CMasternodeSync::ProcessTick1 -- nTick 91 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:10 CMasternodeSync::ProcessTick1 -- nTick 97 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:17 CMasternodeSync::ProcessTick1 -- nTick 103 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:23 CMasternodeSync::ProcessTick1 -- nTick 109 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:29 CMasternodeSync::ProcessTick1 -- nTick 115 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:36 CMasternodeSync::ProcessTick1 -- nTick 121 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:42 CMasternodeSync::ProcessTick1 -- nTick 127 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:48 CMasternodeSync::ProcessTick1 -- nTick 133 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:50:54 CMasternodeSync::ProcessTick1 -- nTick 139 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:01 CMasternodeSync::ProcessTick1 -- nTick 145 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:07 CMasternodeSync::ProcessTick1 -- nTick 151 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:13 CMasternodeSync::ProcessTick1 -- nTick 157 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:20 CMasternodeSync::ProcessTick1 -- nTick 163 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:26 CMasternodeSync::ProcessTick1 -- nTick 169 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:32 CMasternodeSync::ProcessTick1 -- nTick 175 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:38 receive version message: /Biblepay Core:1.0.5.2/: version 70708, blocks=25752, us=84.29.208.33:54599, peer=4
2017-10-29 15:51:39 CMasternodeSync::ProcessTick1 -- nTick 181 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:39 CMasternodeSync::ProcessTick4 -- nTick 181 nRequestedMasternodeAssets 1 -- requesting sporks from peer 4
2017-10-29 15:51:45 CMasternodeSync::ProcessTick1 -- nTick 187 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:51 CMasternodeSync::ProcessTick1 -- nTick 193 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:51:57 CMasternodeSync::ProcessTick1 -- nTick 199 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:04 CMasternodeSync::ProcessTick1 -- nTick 205 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:10 CMasternodeSync::ProcessTick1 -- nTick 211 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:16 CMasternodeSync::ProcessTick1 -- nTick 217 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:23 CMasternodeSync::ProcessTick1 -- nTick 223 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:29 CMasternodeSync::ProcessTick1 -- nTick 229 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:35 CMasternodeSync::ProcessTick1 -- nTick 235 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:42 CMasternodeSync::ProcessTick1 -- nTick 241 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:48 CMasternodeSync::ProcessTick1 -- nTick 247 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:52:54 CMasternodeSync::ProcessTick1 -- nTick 253 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:00 CMasternodeSync::ProcessTick1 -- nTick 259 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:07 CMasternodeSync::ProcessTick1 -- nTick 265 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:13 CMasternodeSync::ProcessTick1 -- nTick 271 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:19 CMasternodeSync::ProcessTick1 -- nTick 277 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:26 CMasternodeSync::ProcessTick1 -- nTick 283 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:32 CMasternodeSync::ProcessTick1 -- nTick 289 nRequestedMasternodeAssets 1 nRequestedMasternodeAttempt 0 nSyncProgress 0.000000
2017-10-29 15:53:34 mnbcon thread interrupt
2017-10-29 15:53:34 addcon thread interrupt
2017-10-29 15:53:34 scheduler thread interrupt
2017-10-29 15:53:34 msghand thread interrupt
2017-10-29 15:53:34 net thread interrupt
2017-10-29 15:53:36 opencon thread interrupt
2017-10-29 15:53:36 PrepareShutdown: In progress...
2017-10-29 15:53:37 StopNode()
2017-10-29 15:53:37 Verifying mncache.dat format...
2017-10-29 15:53:37 Loaded info from mncache.dat  0ms
2017-10-29 15:53:37      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:53:37 Writting info to mncache.dat...
2017-10-29 15:53:37 Written info to mncache.dat  0ms
2017-10-29 15:53:37      Masternodes: 0, peers who asked us for Masternode list: 0, peers we asked for Masternode list: 0, entries in Masternode list we asked for: 0, masternode index size: 0, nDsqCount: 0
2017-10-29 15:53:37 mncache.dat dump finished  0ms
2017-10-29 15:53:37 Verifying mnpayments.dat format...
2017-10-29 15:53:37 Loaded info from mnpayments.dat  0ms
2017-10-29 15:53:37      Votes: 0, Blocks: 0
2017-10-29 15:53:37 Writting info to mnpayments.dat...
2017-10-29 15:53:37 Written info to mnpayments.dat  0ms
2017-10-29 15:53:37      Votes: 0, Blocks: 0
2017-10-29 15:53:37 mnpayments.dat dump finished  0ms
2017-10-29 15:53:37 Verifying governance.dat format...
2017-10-29 15:53:37 Loaded info from governance.dat  0ms
2017-10-29 15:53:37      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-10-29 15:53:37 Writting info to governance.dat...
2017-10-29 15:53:37 Written info to governance.dat  15ms
2017-10-29 15:53:37      Governance Objects: 0 (Proposals: 0, Triggers: 0, Watchdogs: 0/0, Other: 0; Seen: 0), Votes: 0
2017-10-29 15:53:37 governance.dat dump finished  15ms
2017-10-29 15:53:37 Verifying netfulfilled.dat format...
2017-10-29 15:53:37 Loaded info from netfulfilled.dat  0ms
2017-10-29 15:53:37      Nodes with fulfilled requests: 3
2017-10-29 15:53:37 Writting info to netfulfilled.dat...
2017-10-29 15:53:37 Written info to netfulfilled.dat  5ms
2017-10-29 15:53:37      Nodes with fulfilled requests: 4
2017-10-29 15:53:37 netfulfilled.dat dump finished  5ms
2017-10-29 15:53:38 Shutdown: done

i tried mining on testnet wallet 152 on linux VPS but without chance ... chain is broken

all my win wallets testnet no syncing

i tried mining on testnet wallet 152 on linux VPS but without chance ... chain is broken

all my win wallets testnet no syncing

I actually think the linux wallet is fine. I've been mining for a few minutes:

Code: [Select]

jaap-ubuntu@jaapubuntu-HP-Pavilion-dm1-Notebook-PC:~/biblepay/src$ ./biblepay-cli -testnet getwalletinfo
{
  "walletversion": 61000,
  "balance": 0.00000000,
  "retirement_account_balance": 242.23500000,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 88013.36721135,
  "txcount": 9,
  "keypoololdest": 1508425662,
  "keypoolsize": 1001,
  "keys_left": 1000,
  "paytxfee": 0.00000000


what is correct biblepay.config for mining?

testnet=1
genproclimit=8

enough? cos before working,not now

ADMIN: can you explain where is problem with stuck syncing win-controller wallets?

what is correct biblepay.config for mining?

testnet=1
genproclimit=8

enough? cos before working,not now

ADMIN: can you explain where is problem with stuck syncing win-controller wallets?

Do you also have 'gen=1' in your config?

no........after add gen=1 synced:

so problem was in gen=1 or admin fixed it?

edit:// all blockchain is dead ... with my friend tried sync independent syncing:

my VPS is on others blocks like 2 other PCs

Oh yeah, I see the problem, the controller wallets, duh. Sorry.

Yeah, I was trying to avoid releasing the code to prod, because it has untested things in it, but double checking, everything is pushed off until block 400,000 so I think we are OK to push this out to the download site.  Lets cross our fingers and pray.   Please all let me know if this breaks anyone.  The miner is stll f7000, sanctuaries are disabled, and all the features are delayed in prod.

So go ahead and upgrade the controller wallets next.  From the download site.

Yes, it makes sense the chain is hosed in testnet, because we have a high % of controller wallets causing forks.  There are so many different rules in that 1047-1048 its not worth trying to run a fractured net.

how can we upgrade our controller win wallets when exists only 148 and its broken? we cant syncing ... give us any solution .. im downloaded any new wallet from main web=but it still 148 and still no syncing
im only 1 guy who will trying run it? 

Looks like we are getting closer now.  The primary issue is we need a rule that prevents a temple from staking during the same block as a superblock.

2017-10-30 13:38:39 coinbase pays too much at height 25700 (actual=9601632816378 vs limit=8660296265738), exceeded superblock max valueHeight 25700.000000, Amount 96016.328164
ERROR: ConnectBlock(biblepay): coinbase pays too much at height 25700 (actual=9601632816378 vs limit=8660296265738), exceeded superblock max value
2017-10-30 13:38:39 InvalidChainFound: invalid block=9cb8783758718a7ebc74bf456f59aeec825444b0954781e612432ea2ef7116cb  height=25700  log2_work=45.197793  date=2017-10-29 02:52:01


Looks like one of the two temples staked at block 25700 which is the same block as our superblock, which has a max payment of 72,000. 

In the mean time to get around this, everyone should reindex your block file.  See if you can get past block 25700 after a reindex.  If you are already above height  25700, delete your whole blocks file and chainstate and restart.  We need to get past the bad block at 25700.

Ill work on adding a rule in the mean time, but if we all sync and drop that bad block then we can at least continue testing on 1052.

All-

Please upgrade to 1.0.5.3 on linux, then delete your chainstate and blocks file and restart.

Windows is compiling now.

   what blocks is last?

All,

I have discovered one issue with Temples related to security that I dont really like, and although we could probably work through it, I think at this point it would be stronger for us to roll back the temples out of the code and cancel them, and consider other options such as paying for the specific service through a budget in the future.

Sorry for the inconvenience guys, but I think this will be more straightforward.  Please hold off on testing until the new version is available.

Alright 1.0.5.4 is out there, please upgrade.  Windows is still compiling.

Note that after we all get together with 1054, we have a little work to do on the masternodes.  Part o the reason we couldnt sync is some have banned each other and whats really exact with MNs, is they have an iterative payment schedule depending on who was paid last.  Meaning that if one node knows of A&B, and another B&C, those schedules will not agree.  So please delete your peers.dat, banlist.dat, mncache.dat, and blocks and chainstate and database and resync, we will need to re-seed the mncache data after we all upgrade.

PS Temples have been removed.  You can still have a 10 MM sanctuary right now, but it will not pay you any more than the 500k sanctuary so it is of no benefit. 

Ok Windows is out for download (1.0.5.4) please delete all your .dat files including mnpayments.dat and mncache.dat, resync your chain, upgrade, and if you have a masternode, set masternode=0 before resyncing then back to masternode=1 after syncing then we should all be able to bootstrap our sanctuaries again.

Robert,nice synced: but can i mining on testnet? cos doesnt working
i set in my config this:

testnet=1
genproclimit=24
gen=1

thanks for help