Bible Pay

Read 160634 times

Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #450 on: December 02, 2017, 07:36:13 AM »
Hahah no worries. I'm actually running a fork of bitcoin-seeder (https://github.com/sipa/bitcoin-seeder) adapted for biblepay which crawls the network and returns a list of reliable nodes which should be plenty!

Example:

Quote
; <<>> DiG 9.9.7-P3 <<>> A dnsseed.biblepay-explorer.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44541
;; flags: qr rd ra; QUERY: 1, ANSWER: 22, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;dnsseed.biblepay-explorer.org.   IN   A

;; ANSWER SECTION:
dnsseed.biblepay-explorer.org. 3599 IN   A   193.70.86.212
dnsseed.biblepay-explorer.org. 3599 IN   A   51.15.196.233
dnsseed.biblepay-explorer.org. 3599 IN   A   54.37.136.161
dnsseed.biblepay-explorer.org. 3599 IN   A   94.177.170.16
dnsseed.biblepay-explorer.org. 3599 IN   A   195.181.247.200
dnsseed.biblepay-explorer.org. 3599 IN   A   208.113.167.108
dnsseed.biblepay-explorer.org. 3599 IN   A   45.77.98.203
dnsseed.biblepay-explorer.org. 3599 IN   A   94.177.233.28
dnsseed.biblepay-explorer.org. 3599 IN   A   54.37.69.161
dnsseed.biblepay-explorer.org. 3599 IN   A   104.196.167.205
dnsseed.biblepay-explorer.org. 3599 IN   A   139.99.101.201
dnsseed.biblepay-explorer.org. 3599 IN   A   85.255.15.55
dnsseed.biblepay-explorer.org. 3599 IN   A   185.13.148.42
dnsseed.biblepay-explorer.org. 3599 IN   A   45.199.176.10
dnsseed.biblepay-explorer.org. 3599 IN   A   217.182.77.165
dnsseed.biblepay-explorer.org. 3599 IN   A   54.37.136.162
dnsseed.biblepay-explorer.org. 3599 IN   A   208.97.140.76
dnsseed.biblepay-explorer.org. 3599 IN   A   85.255.10.54
dnsseed.biblepay-explorer.org. 3599 IN   A   35.199.150.168
dnsseed.biblepay-explorer.org. 3599 IN   A   89.36.219.116
dnsseed.biblepay-explorer.org. 3599 IN   A   192.99.68.192
dnsseed.biblepay-explorer.org. 3599 IN   A   80.211.208.230


On another note, I managed to come back on the main chain but it took me two tries. I'm reindexing the db on the BX now.


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #451 on: December 02, 2017, 07:38:14 AM »
Oh also, that crawler allowed me to see that we have 70709 running on mainnet, is that normal?


  • 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 #452 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.






Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #453 on: December 02, 2017, 08:17:01 AM »
Yup that biblepay-seeder is really useful. It's tracking about 800 nodes right now and returning the best ones (and I limited the version to something recent).

Oh ok, understood for 70709 on mainnet.

That actually made me think of checking my (enabled) masternode and it was stuck on a fork way behind (54347) with everyone banned!
I have unbanned everyone but by looking at the logs, it looks like I need to resync it from the start as it's starting to ban again. I will do that now.

For the ecommerce feature, I think it could be really nice!
The main caveat I can think of is that people may be worried about sharing their personal information (especially nowadays with all these leaks/hacks/etc) and so that would probably need to be addressed (how it stored, security measures, who can access it, etc).

I have to go now but I can help with testing if you need testers later. I'm afraid looking through the code to try to find the issue is beyond my capabilities unfortunately so all our hope is with you haha!


  • 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 #454 on: December 02, 2017, 08:24:26 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?


  • 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 #455 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.



  • 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 #456 on: December 02, 2017, 08:54:03 AM »
So, I have a small amount of info as to what is happening:


08:47:13

getchaintips


08:47:13

[
  {
    "height": 56794,
    "hash": "b6309b95902c56470ef27a4442df5db0860e1cc3854db230cb6ede10eef6d906",
    "difficulty": 0.01837265411190288,
    "chainwork": "00000000000000000000000000000000000000000000000000002f88fdc59002",
    "branchlen": 0,
    "status": "active"
  },
  {
    "height": 56057,
    "hash": "6988dfa709707d99ae448da5984be132fdb7f13e274c00be9fb605f32dabac1f",
    "difficulty": 0.007104095844318024,
    "chainwork": "00000000000000000000000000000000000000000000000000002f80151d1740",
    "branchlen": 1708,
    "status": "headers-only"
  }
]

We have two chains : 56061 and 56794.
Heres what is funny about it:  The shorter chain has the masternodes synced on it and in agreement, but less chain work.
The longer chain has more chain work (notice its diff is .01 while the masternode chain is .007).  So the controller wallets pick the chain with more work, because thats part of the active-chain setbestchain rule, however the masternodes have banned those nodes already and prefer their own chain (primarily because of our rule to enforce sanctuary payees in a ranked list, which is part of Dash).

So its kind of interesting that the only way out is for me to blow the chain away and resync.

My question is, if we had the prod chain where obviously all the miners would be mining, and diff would be 10,000 instead of .01 will we stay synced on the chain with the most work in prod?  It SOUNDS like we would, but ..... lets keep thinking about this.



  • 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 #457 on: December 02, 2017, 08:55:39 AM »
Ive got an idea to test fixing this.  Lets all turn mining ON on our masternodes.
Lets get the diff up above 2.0 on our masternode chain... and then see if we stay in sync....

EDIT: I do see a possible reason that started this.  On TestNet its OK to mine on an out of sync chain with no peers.  On Prod you have to have a synced chain and peers with you.  So thats a huge difference.  Technically, the controller wallets are missing 3 things:  They are synced to best height, but mnode data is NOT synced (that requires masternodes, and mnsync status 999), and they banned every masternode peer.... 

So this does sound like an important exercise for us.  Lets try to fix the sync manually on the non-conforming peers, reindex those, and drive the diff up on the masternodes.


Then regroup for 10 more days and see if we can break the stay-in-sync record (I think thats only 3 days long LOL).



« Last Edit: December 02, 2017, 09:03:17 AM by admin »


  • 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 #458 on: December 02, 2017, 09:00:56 AM »
then all is gone with my masernode+controller wallet?  :-[ im on 56799 bigger chain ...
and yes... my VPSlinux was on low chain and my controller is on bigger chain ... very interesting ...

how can i fix it now?

« Last Edit: December 02, 2017, 09:15:29 AM by klondike »


  • 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 #459 on: December 02, 2017, 09:07:57 AM »
then all is gone with my masernode+controller wallet?  :-[ im on 56799 bigger chain ...
and yes... my VPSlinux was on low chain and my controller is on bigger chain ... very interesting ...

how can i fix it now? ill try to ban all bigger nodes and allow all your MN nodes
Try starting with -reindex, and while reindexing ban any peer with a block height higher than the small chain.

Im mining on my 3 masternodes now - diff > .10 so far...

Once masternodes advance 700 more blocks it will be a moot point, but lets hope we stay in sync after we get this back.

Alternatively you can just shut off the nodes on the long chain and wait a day and turn on tomorrow with an empty chain.



  • 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 #460 on: December 02, 2017, 09:27:53 AM »
yes,.super..... on VPS and WIN i added bad IPs to banlist and resynced: working!!!

now my masternode immediately ENABLED  :-*
xx.xx.xx.106   vps
xx.xx.xx.58     home controller
now starting testing

now try running 2nd masternode to 1 controllerwallet

Robinho: can i ask,dont know this thing=  when i will be have in controller-wallet (1,550,001 BBP) and rewards ill be receiving: can i to withdraw any BBP from this controller wallet? the balance can not fall under 1,550,001 BBP?

thanks for this question...
« Last Edit: December 02, 2017, 11:10:03 AM by klondike »


  • 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 #461 on: December 02, 2017, 09:50:37 AM »
yes,.super..... on VPS and WIN i added bad IPs to banlist and resynced: working!!!

now my masternode immediately ENABLED  :-*
xx.xx.xx.106   vps
xx.xx.xx.58     home controller
now starting testing

Robinho: can i ask,dont know this thing=  when i will be have in controller-wallet (1,550,001 BBP) and rewards ill be receiving: can i withdraw any BBP from this controller wallet? the balance can not fall under 1,550,001 BBP?

thanks for this anwer...

Yeah on a side note, I see my controller wallet synced as soon as it saw the masternode chain was .11.  Interesting.  Im hoping that was the problem, knock on wood.  The wallets are designed to sync to the chain with the highest diff (IE the most work).

Anyway lets talk about the escrow now.

During the third week of December I plan on poring through the code and updating any code required for the mandatory for Us and for c-cex.  Obviously one thing is the higher sanctuary escrow requirement.

Lets say you have one controller with 4 million BBP in it, and you decide to start two masternodes.  That means you will dedicate 3100002 BBP over two transactions for the investment of two masternodes leaving 899.9K spendable.

The wallet has code in it that will lock the 3.1MM escrow so that it wont be spent by you under normal circumstances.  For example if you attempt to  spend it, it will balk at you and never select those coins , therefore you cannot spend more than 899.9K.

IF you want out, and you want to relinquish your rights to one of your masternodes, you have to do this to spend it:
You have to enable coin control, and deliberately unlock the escrow (by selecting it) and then deliberately spending the selected escrow.  Once even 1 BBP of it is spent, that particular masternode will never work again until new escrow is set up for it.  Once the escrow is disturbed to no longer be "1,550,001" the rewards stop....



« Last Edit: December 02, 2017, 09:52:48 AM by admin »


  • 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 #462 on: December 02, 2017, 11:51:53 AM »
otherwise:

i have in my masternode 2M BBP and when i will be want send 500k controller wallet disable my request?


  • 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 #463 on: December 02, 2017, 12:36:04 PM »
otherwise:

i have in my masternode 2M BBP and when i will be want send 500k controller wallet disable my request?
Just re-read what I wrote and then try it in testnet.

And then practice withdrawing as a masternode.


  • 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 #464 on: December 02, 2017, 12:37:07 PM »
I can only see one chain on both the sanctuary and controller-wallet:

Code: [Select]
19:31:52

getchaintips


19:31:52

[
  {
    "height": 56217,
    "hash": "5262f5c3a5f4dd6b233d4882aa84ab17a02cc9aced5cee1be6ad8aeccc5bc84b",
    "difficulty": 0.410893199744191,
    "chainwork": "00000000000000000000000000000000000000000000000000002f916df1cc2f",
    "branchlen": 0,
    "status": "active"
  }
]