Bible Pay

Read 160627 times

  • Rob Andrews
  • Administrator

    • 3858


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #405 on: November 28, 2017, 08:22:23 AM »
@Rob, found an easier way to do it without the rpc call. I will just swap it myself so I just need a list of all the abbreviations used by biblepay and their corresponding names.

Edit: Added something similar to reftagger.
https://testnet.biblepay-explorer.org/block/9ab71b36d99342ccd3db656e7804e84eec501b67b66ed983d915c5eac3aea15e

Edit2: Found the abbreviation list, will add them soon.

Edit3: Everything has been added. Pushed it to the prod explorer.

Dude, that is simply stunning!  I like the spinner that comes up while its retrieving the verse also!
I figured you would find the book list in the code LOL.

This is really what cryptoenthusiasts are looking for when I said we should find features to add value to BBP.
I know its only 16 hours of your work now, but Im telling you in the future, these type of things will be the cornerstone of biblepay if we dont go through the great trib soon.  Once we have enough organic users, people will be all over the internet mentioning things like this and driving us up to 80MM-120MM market cap.

Now I need to step up and add some myself :)

Ill mention this feature in our other forum now and then you can talk about it when people reply....

Thanks!



Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #406 on: November 28, 2017, 08:29:45 AM »
Haha Thanks, I'm trying to get the masternodes tab working now so the testnet explorer is going down every 2 min!

The verses feature is available on the prod explorer if somebody wants to look at it!

Edit: Btw, I just formatted the verses, the hover feature is all provided by biblegateway.
« Last Edit: November 28, 2017, 08:37:23 AM by Alex »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #407 on: November 28, 2017, 10:52:09 AM »
The masternode page is looking good and is pretty much done!

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


  • jaapgvk
  • Hero Member

    • 558


    • 31
    • September 01, 2017, 08:02:57 PM
    • Netherlands
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #408 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?


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #409 on: November 28, 2017, 05:05:56 PM »
Well that's something I haven't figured out yet :P I'm not sure how often these updates are broadcasted/refreshed.

For example, if you "start" a masternode from the controller wallet, the status of that masternode will change automatically to pre-enabled I believe as it locally knows that you clicked on start. So, it's changing the status based on something it locally knows instead of something it receives from the network. Even though it says "successful", it doesn't mean it actually successfully started the masternode as I think it only means there was no error with the conf file and that it found the appropriate escrow amount (no check about the masternode being started!).

If the masternode was actually successfully started, other nodes on the network will take some time before getting the new network state of your masternode and it can be quite long :P

That's why it can be nice to have another node to see if it sees your masternode enabled or not. However as I said, you probably should wait a few hours before looking at that.

Maybe Rob can help us figure out that.


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #410 on: November 28, 2017, 05:14:19 PM »
Oh also if I may add, you may still receive rewards even if your masternode "dies" / is not valid anymore (up to 36 hours after it dies).


  • klondike
  • Full Member

    • 157


    • -10
    • October 10, 2017, 09:00:24 AM
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #411 on: November 28, 2017, 05:25:48 PM »
1.starting masternode being few minutes for me between 45-100minutes
2.after offline msaternode,you will be still receiving rewards = its call falltime


  • Rob Andrews
  • Administrator

    • 3858


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #412 on: November 29, 2017, 06:21:24 AM »
Oh also if I may add, you may still receive rewards even if your masternode "dies" / is not valid anymore (up to 36 hours after it dies).
Yes, that masternode list looks great!   Well at least its pulling the view from the wallet, so that puts the onus on us here to figure the rest out regarding consistency.

Btw, did you ever figure out the exact hours elapsed when you stopped receiving payments?

I have a tad little bit of insight on the PRE-ENABLED flag.   If you blindly call masternode start-alias (as most people do) the command is sent over the P2P port (40001), reaches the actual masternode and the masternode logs something to the effect of "masternode sync data not synced yet" and no error is raised (and a log is logged on the masternode but only if debugmaster=true).  So yeah, its a nuisance, but no work was ever put into it because there is a workaround.  The workaround is you must first go to the masternode and type mnsync status and know that it only follows controller commands if mnsync status is 999.  So in real life, we basically just need to click on the peer height in your controller to see if the node is in sync and then issue the command 5 mins later.  Its just a pitfall we need to know about.

One other thing on this topic:  If the masternode made enemies with a section of the network (IE ddossed 3 out of 5 masternodes), it will no longer follow the same potential fork.  Thats probably what happened here when I shut down my vultr nodes, we lost 2 of 5, and a couple who were only peers of vultr started mining their own chain.  Their mnsync status is then different than the other masternodes (because their payment ranking is different), causing all kinds of potential problems.  So the expectation is, in prod, with over 100 masternodes we will be clinging to the same chain due to the supermajority being on the same sync height.



  • Rob Andrews
  • Administrator

    • 3858


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #413 on: November 29, 2017, 06:24:24 AM »
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?

Yeah, looking at Alex's testnet masternode list, something does look wrong....

Im showing you on my masternode list as enabled now (84.29.208.33).  First, you are right in that when you issue the command to start, the local wallet just changes the caption blindly.  However, the other values: watchdog_expired, Enabled, new_start_required should be network values. 

But looking at 45.76...64 and 45.76..42 those two are Enabled on my controller, my vultr, my other vultr, my dev machine but "Expired" in the explorer... Hmmmmm, explorer is synced though.  Thats strange.

Alex, what happens if you look at those 2 node statuses from the GUI?  Do they match the explorer?



« Last Edit: November 29, 2017, 06:27:06 AM by admin »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #414 on: November 29, 2017, 07:01:09 AM »
Let me check the timestamps and I will come back to you on when my masternode stopped receiving rewards after killing biblepayd (it looks like about 1 day - 1 day and a half)

Edit: Biblepayd killed on November 27 at 1am (CT) - Last reward received on November 28 at 12.29am (CT).

--

The masternode list is pulling data straight from the masternode list full command every time you call it so you get the most updated view that my node has every time.

For that specific node:

45.76.239.42 and 64 are showing as expired.

84.29.208.33 with new start required.

There's also an api call that gives the result of the masternode list full command on my node (the table is actually built from that):
https://testnet.biblepay-explorer.org/api/getsanctuaries

I know that it takes quite a lot of time for updates on status to be propagated. For example, my local testnet wallet is showing 64 as expired but 42 as new start required.
« Last Edit: November 29, 2017, 07:11:03 AM by Alex »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #415 on: November 29, 2017, 08:04:36 AM »
Just checked my logs and saw a spam of invalid block headers. I also noticed that there hasn't been any new block since the 28 lol. My explorer somehow went on a fork. I'm going to resync it now.

This is the last block it had:

biblepay-cli showblock 53062
{
  "hash": "6e9ffa1e3dcdd7e4bb71aac09ea7dded84fd60d8f03f9e82c24465049503386a",
  "confirmations": 1,
  "size": 299,
  "height": 53062,
  "version": 536870912,
  "merkleroot": "e587cae90aad4ca604309b0cef7e056ab243faf36d265a4ed8cd4199b99bcf08",
  "tx": [
    "e587cae90aad4ca604309b0cef7e056ab243faf36d265a4ed8cd4199b99bcf08"
  ],
  "time": 1511878192,
  "mediantime": 1511877871,
  "hrtime": "11-28-2017 14:09:52",
  "nonce": 4493,
  "bits": "1e008cae",
  "difficulty": 0.007108238289276392,
  "chainwork": "00000000000000000000000000000000000000000000000000002f38941f9161",
  "subsidy": 7524,
  "blockversion": "1.0.6.1",
  "masternodereward": 265834350462,
  "previousblockhash": "55a590732347a64b46eb06ab6ea5f3a451d5dd9eb9268b9e0b14a0e39b991f3d",
  "verses": "Pro|2|16| To deliver thee from the strange woman, even from the stranger which flattereth with her words;\r\nGen|25|29| And Jacob sod pottage: and Esau came from the field, and he was faint:\r\nJob|6|24| Teach me, and I will hold my tongue: and cause me to understand wherein I have erred.\r\nGen|13|10| And Lot lifted up his eyes, and beheld all the plain of Jordan, that it was well watered every where, before the LORD destroyed Sodom and Gomorrah, even as the garden of the LORD, like the land of Egypt, as thou comest unto Zoar.\r\nPsa|106|19| They made a calf in Horeb, and worshipped the molten image.\r\nExo|21|3| If he came in by himself, he shall go out by himself: if he were married, then his wife shall go out with him.\r\nJoh|20|17| Jesus saith unto her, Touch me not; for I am not yet ascended to my Father: but go to my brethren, and say unto them, I ascend unto my Father, and your Father; and to my God, and your God.\r\nCh2|20|36| And he joined himself with him to make ships to go to Tarshish: and they made the ships in Eziongaber.\r\n",
  "satisfiesbiblehash": "true",
  "biblehash": "00000034d22c72ed61b419b1eba74c1d7a93795445563f3d63dc80e069108c13",
  "prayers": ""
}
« Last Edit: November 29, 2017, 08:10:09 AM by Alex »


  • Rob Andrews
  • Administrator

    • 3858


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #416 on: November 29, 2017, 08:12:49 AM »
Just checked my logs and saw a spam of invalid block headers. I also noticed that there hasn't been any new block since the 28 lol. My explorer somehow went on a fork. I'm going to resync it now.

Yeah, btw, I have some inside info on why some forks start to occur (at least part of the problem).  If we have say 8 masternodes, and lets say 2 are only connected via 1 node to the rest, if that 1 node gets ddossed, that masternode will have a propensity to create its own chain (especially with our low diff on testnet).

Now the smoking gun here is our recent fix to the biblehash itself makes it much more likely that those running 1062 are all producing the same hashes.  So, somehow we should probably make an effort to ask everyone on testnet to upgrade to 1062.

What I can do from my side is force an upgrade to 1063, and force a protocol upgrade (meaning everyone lower than 1062 actually gets disconnected).  It might be worth doing between Dec 2 and Dec 20th just to ensure we dont have a lurking problem.

Let me take a look at the retirement issue before monkeying with it.  I think we were close on that but not quite done.

EDIT: BTW, you may have to delete your banlist.dat before resyncing to bring back all nodes into your testnet node.
« Last Edit: November 29, 2017, 08:15:06 AM by admin »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #417 on: November 29, 2017, 08:22:55 AM »
I thought I would need to do that too but apparently not. No one has been banned even thought I was receiving "bad headers". I didn't think it would on a fork with 20 connections :(

I also just checked my masternode and it went on a fork too so I'm resyncing it too :(

It prob would be nice to force the upgrade.


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #418 on: November 29, 2017, 08:33:57 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?



  • Rob Andrews
  • Administrator

    • 3858


    • 89
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #419 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.