Messages

3916

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

« on: December 02, 2017, 08:50:39 AM »

now what block is OK... im resync and my linux wallet sync with same block like controller wallet



Rob,which IP is your? exists any correct chain?

im 97.99.69, and the two 45.x.x's.

We have one shorter chain (block 56061) that seems to be the one with all our masternodes on it.

3917

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

« on: December 02, 2017, 07:53:05 AM »

Oh also, that crawler allowed me to see that we have 70709 running on mainnet, is that normal?

Wow thats great on the crawler, yeah, on 70709, yes, because the wallet supports some advanced rules.  I copied the prod rules to testnet first before doing this:

On testnet, the minimum required version is 70709, that ultimately forced the upgrade and instructs peers to hang up on peers with a lower protocol version.

On mainnet, the minimum version required is 70708, but it is OK to run a higher version.  After Christmas though, the mandatory would have something like "required minimum version 70709" in it (otherwise peers disconnect).

So thats OK for now.

Im working on the out-of sync condition, we need to get to the bottom of this thing.

I see that it occurred on block 54360 on my win node:

2017-12-02 00:10:19 IsBlockPayeeValid -- ERROR: Invalid masternode payment detected at height 54360: CTransaction(hash=2bbbb94c92, ver=1, vin.size=1, vout.size=3, nLockTime=0)
 

So basically the group of masternodes themselves did not experience this issue, but my win node refused block 54360.  I see that it did not create 54360.  Weve got to think of why did its view of payees differ from the main group (as this happened before the banned nodes occurred).  It banned every other node After this.

3918

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

« on: December 02, 2017, 07:35:53 AM »

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.

3919

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

« on: December 02, 2017, 07:30:12 AM »

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.

3920

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

« on: December 02, 2017, 07:26:02 AM »

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 .

3921

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

« on: November 30, 2017, 03:46:00 PM »

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.

3922

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

« on: November 30, 2017, 06:41:57 AM »

Rob: ouch  didnt know that we have calculator internet traffic in win: thanks:nice

Rob: im deleted peers.dat mncache and sync and still im on bad chain: banlist i hadnt in folder

EDIT:// im offline and received 2 rewards ... something is wrong after last update wallet

Ive gone through this before and something is either cached in your mncache, peers (a ddossed node) or chainstate.

To be on the safe side :
cd \testnet3
rm blocks -R
rm chainstate -R
rm mncache.dat
rm peers.dat
rm banlist.dat

Then remove any extra .dat file for governance
Then resync.  I do not think you will end on the wrong chain after that as we have 6 masternodes on the chain with higher work now.

3923

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

« on: November 29, 2017, 09:47:34 PM »

wut? do you know what is traffic? how big will be internet traffic for 1 month? will be enough 500GB traffic?

im stuck ...

EDIT:// 1st im deleted mncache.dat and resyncing nad stuck still

EDIT:// 2nd test and still im on bad chain and stuck still

EDIT://3rd test and still on bad chain= deleted chainstate+blocks+peers.dat and stuck still

i gave up

I think you forgot to describe your question.  Just click Tools | Network Traffic and monitor it for a while.

Just delete your banlist.dat and your peers.dat and your mncache.dat and then sync.

3924

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

« on: November 29, 2017, 01:55:36 PM »

A couple more tips:
If your getchaintips is not clean, restart with -reindex flag, and resync.

Next, if your sanctuary list differs from Alex, delete your mncache.dat and restart.

=-=-=-=-=

Windows compile of 1.0.6.3 is out there now, feel free to upgrade controllers.

3925

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

« on: November 29, 2017, 12:17:20 PM »

The testnet BX has been upgraded.

Success!

Upgraded all 3:

12:16:30

getchaintips


12:16:30

[
  {
    "height": 54194,
    "hash": "9a412d5c7faee2f5048a0dec4ba6ed45b81e595a834e43eef9c64a65d38700ac",
    "difficulty": 0.01934920419809971,
    "chainwork": "00000000000000000000000000000000000000000000000000002f6df8bc31f4",
    "branchlen": 0,
    "status": "active"
  }
]

Chaintips is clean!

Crossing fingers this trend continues til Christmas...

Still waiting for windows to finish compiling....

3926

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

« on: November 29, 2017, 12:05:00 PM »

how big will be traffic on VPS for masternodes?

Not much, masternodes only take up 10% more than bitcoin.

3927

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

« on: November 29, 2017, 10:57:13 AM »

1.0.6.3-Mandatory Upgrade for TESTNET

Please all, in testnet, please upgrade to 1.0.6.3.

The entire network is down until we upgrade.

Building windows for controllers now...

3928

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

« on: November 29, 2017, 09:33:53 AM »

Oh ok. What is weird though is that I was still connected to 20 nodes and receiving bad headers before I resynced.

I'm now on the good chain and I am pretty sure I am connected to the same 20 nodes. (also isn't one of your node the seed node?). So it looks like I didn't ban anyone and no one banned me?

Yes true, but it is also possible my node.biblepay.org only banned you for 1-8 hours (IE one d-dos level 1 ban per bad header received) putting you on a bad fork and while we were looking at it its possible the ban expired.

Anyway I was going to say this is such a critical test, before Christmas, I think we really need to fix the chaintip issue and force a protocol upgrade to 70709, just to ensure we have a long span of uptime for all of our core masternodes.

Just a heads up everyone, I am writing the code to force a network upgrade on testnet only, so please be ready to upgrade as during the next upgrade, all the nodes will disconnect on each other if they are running a prior to 1.0.6.3 version.

It should be out in about 30 mins....

3929

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

« on: November 29, 2017, 09:10:17 AM »

I just deleted blocks and chainstates and it's resyncing right now (the testnet explorer is actually already synced. It just takes a few minutes for the mongo database to reindex everything).

Somehow my nodes never banned anyone.

I just checked and I also have ad4510d1c7fa0ca1cda93c4119581374612737ea41fa5e9e338c65ebd273308a for 54088.

Its possible my nodes banned you when you went on the fork originally (as you would be voting to not pay my 3 masternodes , thats why it gets so severe.  Your nodes say No Im not going to add a payee that I dont know about.  My nodes say you must pay these 5 nodes, in this order.

Alright I added checkpoints, and I counted 50 forks in getchaintips Before checkpoints.  Let me see how many we have now after checkpoints.

3930

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

« on: November 29, 2017, 08:43:02 AM »

I decided to look at the peers I was connected to using getpeerinfo and I think a lot of them are on a different chain (with the latest block being 53062).
Could you have a look at that on your own nodes Rob?

Hmm, I see a huge problem in getchaintips.  We have about 30 prior forks due to all those bad headers.
I think if I make a release with a few testnet checkpoints we can eliminte 99% of that  problem.

For now, Im seeing 54088:

08:41:19

getblockhash 54088

ad4510d1c7fa0ca1cda93c4119581374612737ea41fa5e9e338c65ebd273308a


Alex, try deleting mncache.dat on your 3 testnet nodes and banlist.dat and chainstate and blocks and resyncing?


Ill work on adding a few checkpoints now so we can all clear out our chaintips problems.