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

so deleted db.log and masternode is alive..... ENABLED

but what i see that we are all stuck on block 54 349 

Yeah, it seems we're stuck...

Also, my masternode says 'UPDATE_REQUIRED' when I call 'masternodelist'. Never saw that before. I'm already on 1.0.6.3...

now all working.........hmm....... may be Rob started mining,cos if mining is cpuproclimit=0 and nobody mining, we will be stucking on same block.....
now start receiving rewards

now all working.........hmm....... may be Rob started mining,cos if mining is cpuproclimit=0 and nobody mining, we will be stucking on same block.....
now start receive rewards

Yeah, I started mining just to be sure I'm also getting rewards now.

Yeah, it seems we're stuck...

Also, my masternode says 'UPDATE_REQUIRED' when I call 'masternodelist'. Never saw that before. I'm already on 1.0.6.3...

UPDATE_REQUIRED seems to happen when your watchman database has your last protocol version active and enough time hasnt passed for it to know you upgraded.  If you were to delete mncache.dat and the watchman.db file, it should alleviate that.
But in reality no one does that, and it does get updated in 24 hours.  It should be fine now.

what block are you on? im watching in peer list and any MNodes is on differents blocks 

UPDATE_REQUIRED seems to happen when your watchman database has your last protocol version active and enough time hasnt passed for it to know you upgraded.  If you were to delete mncache.dat and the watchman.db file, it should alleviate that.
But in reality no one does that, and it does get updated in 24 hours.  It should be fine now.

Thank you for the clarification I'll just wait it out then.

@klondike: I'm at block 54408 now.

Code: [Select]

23:41:53

getblockhash 54408


23:41:53

d8e499d40537776d83bc9ad893a95c8f37c312abf5a3cd1d4adc7d393576914e


I received the Bible in the mail Tuesday morning and got it out today, Thank you Rob!

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "FILLING ORDER",
    "Status3": "USPS XXXXX",
    "Details": ""
  }
}

Hey Rob, I'm modifying some things and I can now provide a dns seed node for mainnnet and testnet (should be available soon).

mainnet:
dnsseed.biblepay-explorer.org

testnet:
test.dnsseed.biblepay-explorer.org

Edit: just to avoid the confusion, these will be dns seed nodes so they will just crawl the network and give back a list fo reliable nodes to connect to! I "may" also provide regular seed nodes.

jaapgvk your masternode "NEW_START_REQUIRED"

jaapgvk your masternode "NEW_START_REQUIRED"

Thanks! Tried a restart. Let's see what it does...

its normall,that my win-controller wallet jump to other chain?  ... will be this forks on PROD? i hope that no ...

On a good note, both my dns seeds are now up and running!

On a bad one, it looks like my BX went on a fork (stuck on block 55990 now). I'm restarting it now.

Hey Rob, I'm modifying some things and I can now provide a dns seed node for mainnnet and testnet (should be available soon).

mainnet:
dnsseed.biblepay-explorer.org

testnet:
test.dnsseed.biblepay-explorer.org

Edit: just to avoid the confusion, these will be dns seed nodes so they will just crawl the network and give back a list fo reliable nodes to connect to! I "may" also provide regular seed nodes.

Thanks a lot alex, I added your two DNS seed nodes to ThreadOpenAddedConnections.  This is called once when the wallet starts and does a one shot add of normal DNS addresses (we have 4 now in here):
      AddSeedNode("node.biblepay.org"); // Volunteers welcome to run external nodes and we will add during future releases
      AddSeedNode("99.198.174.212");    //PlainKoin
      AddSeedNode("dnsseed.biblepay-explorer.org");  // Alex
      if (!fProd) AddSeedNode("test.dnsseed.biblepay-explorer.org"); // Alex (TESTNET)


So thats great, that should give us start up stability for new users who open the wallet in fringe areas.  Or in AWS for example.

Yeah, dont worry about the elaborate requirement of bitcoin-seed nodes - that requires running another seed server.  These DNS seed nodes should cover us for the foreseeable (foreseedable LOL) future. 

I tested your node (telnet dnsseed.biblepay-explorer.org 40000) and its working.  Will be in the next release.

Thank you for your support .

I received the Bible in the mail Tuesday morning and got it out today, Thank you Rob!

./biblepay-cli exec orderstatus
{
  "Command": "orderstatus",
  "0718083296": {
    "Product ID": "0718083296",
    "Price": 12230,
    "Added": "",
    "Title": "The NKJV, Holy Bible, Larger Print, Paperback",
    "Status1": "PLACED",
    "Status2": "FILLING ORDER",
    "Status3": "USPS XXXXX",
    "Details": ""
  }
}

Thats great buddy!  So do you guys think this will be a hit in prod?

I have not received any orders in the pool itself (IE BiblePay Storefront) for anything yet.

We can of course add more items to the list for Prod.... Of course it would be nice to have a popup with an actual picture in an HTML frame, but Id like to see how popular this feature is first.

It will definitely accomplish one thing if used:  market depth - as the sales would create volume on the exchange, and thats what we need for debit card integration.

On a good note, both my dns seeds are now up and running!

On a bad one, it looks like my BX went on a fork (stuck on block 55990 now). I'm restarting it now.

Yeah, I see the same problem you and Klondike have- my main test nodes stayed on the right chain with the masternodes, my controller win wallet just went on a different chain.  Here is the chain I show the enabled masternodes running on:


getblockhash 56000
0f1f17e9bb4e0889b81794708f9bb16908ba2c2b0f5e34dc033d7d2e3d03bc95

Regarding the question about prod, it depends on why this is happening.  Ill look at my windows logs and see if it banned the rest of the network.

EDIT:

Lets try to get to the root of the problem with this one.
On my windows node, if you want to see if you have similar problem, go to peers and take a look at the banlist.  I banned every peer.

This time Im not reindexing the chain, Im going to unban peers and see if it catches up.