Messages

526

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: November 28, 2017, 03:52:16 PM »

The masternode page is looking good and is pretty much done!

https://testnet.biblepay-explorer.org/sanctuaries

Awesome work Alex! Looking good

Looking at the masternode list, mine says 'NEW_START_REQUIRED' in your overview (84.29.208.33:40001). That's strange, because my masternode says 'ENABLED' when I call 'masternodelist' and my controller-wallet says 'WATCHDOG_EXPIRED'.

So I've got three different status-things going on with the same sanctuary :p I've been getting my payments and the both the sanctuary and controller-wallet are on the same chain:

Code: [Select]

22:40:29

getblockhash 53371


22:40:29

ad3302691447683831b4d4063211929960c4e3cb589e663119320979af1b2a21

What do you guys think this might mean?

527

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: November 26, 2017, 06:29:32 AM »

My laptop had some problems, so my masternode went down. But I am syncing as we speak, so I should be online again soon.

Aside from that, I'm taking a step back from the crypto world, for a while at least. In my experience, there is so much power and greed involved in bitcoin at the moment, that I feel I can't really cope with the pressure of 'keeping up with the news'. Core vs Jihan etc. So I'm blocking all bitcoin-related sites for a while.

This forum will be the only crypto-related thing I will be keeping an eye on. I will keep the masternode enabled to support our testnet, and if I find the time I will write a guide for the pool (I'm sorry I didn't get to that Rob, and if anyone else want to give it a go, be my guest).

528

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: November 16, 2017, 10:27:40 AM »

I've been trying to get my masternode up and running again (making sure watchdog is functioning).

My sanctuary wallet was indeed stuck on a certain block and wouldn't sync. But I've reindexed both and it seems I'm on the right chain right now (both wallets are on the same block).

Controller wallet:

Code: [Select]


{
  "version": 1000506,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.6",
  "balance": 38514484.00745234,
  "privatesend_balance": 0.00000000,
  "blocks": 41330,
  "timeoffset": -2,
  "connections": 3,
  "proxy": "",
  "difficulty": 0.1980807012241197,
  "testnet": true,
  "keypoololdest": 1507285625,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Sanctuary wallet:

Code: [Select]

{
  "version": 1000508,
  "protocolversion": 70708,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.5.8",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "blocks": 41330,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.1980807012241197,
  "testnet": true,
  "keypoololdest": 1508425662,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

The only thing now is that the 'masternodelist' command gets different results on my controller and sanctuary wallet.

Controller wallet:

Code: [Select]

17:21:14

{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "NEW_START_REQUIRED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "NEW_START_REQUIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "ENABLED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "ENABLED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "ENABLED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "ENABLED"
}

Sanctuary wallet:

Code: [Select]

{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "NEW_START_REQUIRED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "NEW_START_REQUIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "NEW_START_REQUIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "NEW_START_REQUIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "NEW_START_REQUIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "NEW_START_REQUIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "ENABLED"
}

I am 'a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4' btw.

529

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: November 09, 2017, 02:44:03 AM »

Hi guys

I'm trying to set up a test sanctuary .

Can you send me 500K tBBP please :

yd4AaGDNstGbqFPknhAz7uYKHxAPEyqQya

thanks

Good to have another sanctuary tester on board. I have sent you some coins

530

TestNet Discussion Archive / Re: Biblepay Superblock Final Allocation Breakdown Modification Poll

« on: November 05, 2017, 11:00:12 AM »

I am not opposed to a larger chunk for development and PR.  I guess my real point is why earmark anything beyond the orphan fund and a "working" fund.  I'd be happy with 10% Orphan, 10% Working, 80% Miner/Sanctuary or really and number that makes the Miner/Sanctuary share between 75-85%.  The issue I see is if we say 5% is for PR, then we're likely to find times where we spend it wastefully.  Likewise if we say only 5% is for IT, what happens when we have a pressing need to spend on IT and are our of money, but have a balance in PR?   If you look at DASH, they don't differentiate where the coin share is spent, it can go for IT, PR or whatever.  And whatever doesn't get spent gets burnt.  Since the Sanctuaries will have to vote on all expenditures anyhow, it would be easier to only have two omnibus type funds, one for charity, and one "the coin".  Then the money can go where it is needed more so than to areas we though years ago would be where our future selves would want.

I think you make some very good observations here. And the idea of a budget that can be allocated according to the current needs attracts me. But will the Sanctuaries in the original idea be voting on all expenditures of just the allocation of the charity part?

I haven't voted yet by the way. Still poundering what would be the best way to go about this all...

531

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: November 01, 2017, 10:45:27 AM »

I was away for a few days, but I'm back and compiling as we speak

EDIT: my masternode shows 'PRE-ENABLED', so I guess I'll be back online soon

532

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 29, 2017, 02:56:03 PM »

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?

533

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 29, 2017, 11:16:27 AM »

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


534

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 29, 2017, 09:57:37 AM »

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

535

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 29, 2017, 04:55:21 AM »

Yeah, you can, but be aware there is a pitfall that affects all masternodes when rebroadcasting same public IP with new VIN.
I recommend spending the old vin first in coin control.  Enable coin control, from settings, go to send money, and spend the 500k.
Then, create your new vin except the only change being with 15MM BBP instead.  Also, make a new masternode privkey.  Restart the Temple.
Restart the controller.  Reactivate the temple (by sending the start command from the controller).  Then look at the logs in the temple and see if the new VIN was accepted.

So far, I just brought one temple online.  We have 4 people on 1049 and 2 on 1048.  Meaning that the supermajority has upgraded.
Now we have to see if these nodes vote that the temple is paid, so far I have not received a payment, but its only been an hour.

Thanks for the tip. I didn't know this. I've spend some other 500k masternode deposits (made 3 in total, while testing).

I'm first gonna try and start my sanctuary again, before moving on to the temple. It shows enabled right now, but my controller-wallet can't seem to sync to testnet (no block source available). Also, I saw there was an update to 1.0.5.1. so I'm gonna update first, before anything else.

Any clue on to why the controller wallet doesn't sync? It's on 1.0.4.8. btw.

536

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 28, 2017, 04:42:18 AM »

admin do guide for us please: where i can see newest wallet testnet? or how can i update to newest? please do it still otherwise it does not matter

It's in the reddit guide:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

Under the header 'UPDATE:'

(Also, you have to use the command './biblepay-cli -testnet stop' instead of './biblepay-cli stop', because you're on testnet).

537

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 28, 2017, 02:46:26 AM »

1.0.4.9 - Mandatory Upgrade for TESTNET

- Retirement accounts 1.0 (TESTNET)
- Trading Engine orderbook (TESTNET)
- Temples with 15MM BBP Requirement
- F8000 (TESTNET)
- Colored coins, complex transactions with escrow


All, please upgrade in testnet as Temples are a breaking change requiring a mandatory upgrade.

If anyone wants to test temples, follow the same hot wallet instructions except use 15,000,000 for escrow (as the e-commerce features are not integrated yet).

How can I 'update' from sanctuary to temple? Should I just generate another masternode key and use a new alias?

538

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 28, 2017, 02:07:23 AM »

1.0.4.9 - Mandatory Upgrade for TESTNET

- Retirement accounts 1.0 (TESTNET)
- Trading Engine orderbook (TESTNET)
- Temples with 15MM BBP Requirement
- F8000 (TESTNET)
- Colored coins, complex transactions with escrow


All, please upgrade in testnet as Temples are a breaking change requiring a mandatory upgrade.

If anyone wants to test temples, follow the same hot wallet instructions except use 15,000,000 for escrow (as the e-commerce features are not integrated yet).

I'll update today and try to start a temple if I have enough coins now

Offtopic: I want to write a full guide for the pool. But what's your opinion on what the content should be? Should I just write a first introduction on how to pool-mine (create account, name miners) and then create a glossary of all the menu options? And should I make it a wiki-page?

539

Archived Proposals / Re: New Logo Contest

« on: October 28, 2017, 02:02:47 AM »

I think 'Reimaged B' looks absolutely stunning, but I agree with sato_shi_ate that it looks too clutered. In my opinion the four quadrants with the dove etc take away the simplicity that most logos have. I tried photoshopping them away (making all quatrants plain yellow), but that also doesn't look really good. So I'm a bit stuck.

Maybe the answer is filling the lower two quadrants with a 'B' and 'P' (left and right) in the same fashion als de icons now used. That will also clarify that our coin is BiblePay.

But this is just my opinion, and I have no design experience. The logo really looks awesome and the artist sure knows what he's doing

540

TestNet Discussion Archive / Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS

« on: October 24, 2017, 12:22:44 PM »

hello, after restarted win testnet wallet i get this error



im stuck on this error and dont know where is problem


thanks for your help

I tried to help him, but this seems a strange error. Can't really find anything online. Thing is: he also does something with storj, and that's also on port 40001. But changing the port doesn't seem to help...