Bible Pay

Read 27910 times

  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #360 on: December 10, 2019, 10:52:43 AM »
Linux x64 testnet

>cli -version
BiblePay Core RPC client version 1.4.8.4

>cli getblockcount
21050
>cli getblockhash 21050
c050dc13103b96de932787ed502520654ea13ba013528ba10b39a97a63f67681

Mine does not agree with yours (I get e36 for that hash).

Ill resync a node and see what chain jumped; hang on.  This happens every mandatory upgrade due to private quorums, I believe.

EDIT: Ok, you guys apparently bounced the chain with much more hashpower than my piddly sancs had, so I had to resync my 4 nodes but now I agree with oncoas hash on 21050.

So, I just sent the revivesanc command to my 3 sancs, lets see if we unban ourselves now.


« Last Edit: December 10, 2019, 11:03:42 AM by Rob Andrews »


  • oncoapop
  • Full Member

    • 138


    • 14
    • October 23, 2018, 12:31:17 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #361 on: December 10, 2019, 12:25:40 PM »
Thanks on the multiplier.  On the team info name:

I actually had to take out the team name in this version for all teams except BiblePay due to size constraints, since we are now going to support 27,000 new possible researchers, adding things like their nickname and team name and start date and total points just bloated the vectors to a degree that slowed down biblepay, so I took this stance:  We provide all the info for BiblePay, but for other teams, we only know your CPID and your RAC (and things about your rac metrics).  Then each month, the wallet will start to whitelist popular non-bbp teams, as we do that, it will pick up your team name and nickname etc.  In the mean time we use your CPK nickname now (for non BBP CPIDs).

If you provide your CPID (which is public btw, you dont have to x it out necessarily), I can search the BOINC XML files and see that everything is working OK, but I believe it is.

CPID                                                                TEAM
168c62b82fb40fa3db0d34605439daa5    Biblepay
25a7e68bd686ffe82e00330f1390e003     Gridcoin
5f4e0dea9b0ddf2471cac1e9244a7026     Gridcoin


  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #362 on: December 10, 2019, 12:47:32 PM »
CPID                                                                TEAM
168c62b82fb40fa3db0d34605439daa5    Biblepay
25a7e68bd686ffe82e00330f1390e003     Gridcoin
5f4e0dea9b0ddf2471cac1e9244a7026     Gridcoin

Ok everything looks good; so right now, the only team name being displayed in the wallet in exec rac is "BiblePay".  So on your two GRC cpids, we don't yet show the TeamName.  However I whitelisted (that team) so in about 24 hours you should see the teamname show up (but note this doesn't affect anything in the whole system - including payments).

So people in an unknown team still get paid, and charged the correct escrow reqs.



  • sunk818
  • Sr. Member

    • 370


    • 17
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #363 on: December 11, 2019, 09:10:49 AM »

Is this supposed to mean 99% of coin age? Would it be difficult to include a comparison?


Currently, you will approximately receive xx% of your PoDC reward.


For 100% PoDC reward, you will need:
Team BiblePay: xxx BBP
Non-Team BiblePay: xxx BBP




07:07:48 sendgscc wcg
07:07:48
{
  "Warning!": "WARNING!  PODC is using 0.99% of your coin age.  This means your RAC may be reduced, resulting in a lower PODC reward. ",
  "Results": true
}



  • MIP
  • Developer

    • 244


    • 28
    • February 13, 2018, 11:55:52 AM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #364 on: December 11, 2019, 03:19:55 PM »
Upgraded all 3 of my test servers to v1.4.8.4

Im running privatesend on all of them, but no coins are mixing,
this is what I see in debug.log:
https://i.imgur.com/P2whFqB.png

This is my config on all of them:

enableprivatesend=1
privatesendamount=1000000
privatesendrounds=2

I commented out privatesendmultisession=1 for this round of testing

Im running each of them as QT GUI,
and I typed "privatesend start" into each console

When I check the coins in Send tab >> Inputs,
the denominated coins all show as 0 for "PS Rounds" column

I will reach you tomorrow so we can do some tests with private send on testnet.


  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #365 on: December 11, 2019, 04:23:20 PM »
I will reach you tomorrow so we can do some tests with private send on testnet.

Thanks, this will help sooo much.



  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #366 on: December 12, 2019, 04:21:33 PM »
Is this supposed to mean 99% of coin age? Would it be difficult to include a comparison?


Currently, you will approximately receive xx% of your PoDC reward.


For 100% PoDC reward, you will need:
Team BiblePay: xxx BBP
Non-Team BiblePay: xxx BBP




07:07:48 sendgscc wcg
07:07:48
{
  "Warning!": "WARNING!  PODC is using 0.99% of your coin age.  This means your RAC may be reduced, resulting in a lower PODC reward. ",
  "Results": true
}


Yeah, that would be pretty nice to show the user.

Ill look at this now.



  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #367 on: December 12, 2019, 04:23:30 PM »
All,

Since we need a full 14 day notice for the go live we are going to need to wrap up testing really really soon!

I have been testing prod successfully and last night I made it through the superblock (GSC height) without forking.

Can anyone think of anything mission critical that needs to be added to this branch?  Please, asap if you can think of anything.

I think we only have time for max one more test release, if that, and hopefully, we won't need that either, as things appear to be working.

We do need to add the Kairos sporks to mainnet, but we can do that at cutover time so that Cameroon one works with the legacy sancs up til Dec 24th.



  • oncoapop
  • Full Member

    • 138


    • 14
    • October 23, 2018, 12:31:17 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #368 on: December 12, 2019, 05:20:12 PM »
All,

Since we need a full 14 day notice for the go live we are going to need to wrap up testing really really soon!

I have been testing prod successfully and last night I made it through the superblock (GSC height) without forking.

Can anyone think of anything mission critical that needs to be added to this branch?  Please, asap if you can think of anything.

I think we only have time for max one more test release, if that, and hopefully, we won't need that either, as things appear to be working.

We do need to add the Kairos sporks to mainnet, but we can do that at cutover time so that Cameroon one works with the legacy sancs up til Dec 24th.

I have my VPS on but not in sanc mode (collateral still not spent)

Code: [Select]
ifconfig -a ens160 | grep inet
       inet 45.62.239.200  netmask 255.255.255.0  broadcast 45.62.239.255

sanc status
error code: -32603
error message:
This is not a masternode

I had this Condition since yesterday but it is still ENABLED on the sanc list

Code: [Select]
>sanc list full
(Last line is this particular sanc)

{
 "a46074dac98333269341fee5b712f795fdeaa615b276fee12175e1c537ce8a43-1": "           ENABLED yVfoZ676zm9bjmU5qXbNe9TkGsHAxFYrDg 1576191507  21620 155.138.228.109:8003",
 "efbe80743321967f9d94b124b6670e3d87492e711f34acbe6fdada608007e055-0": "       POSE_BANNED yMFgidsw7EgVRfTwFU1hPWLmrPYcT1Bq7s 1576145873  21513 155.138.228.109:8002",
 "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583-1": "           ENABLED yTwJA2VCYQWpWXH8HS7UvEpqRE3Aj5ciUV 1576191075  21618 104.167.116.179:8080",
 "7570652f63502f29b610c4bf134f3d1d589c970c383b20a88545cd683c802130-1": "           ENABLED yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq 1576191197  21619 45.62.240.90:40001",
 "7c30c4cf73a81ce8ebb90b3cd6bcda3c279d86fb044605b3f95f75a1657cd19e-1": "       POSE_BANNED yZ6pvVMxJ8qXE15J6sPssG83FE5wkSik3N 1575350464  19686 155.138.220.139:40001",
 "c49f6f1e8fc8829b048abc37e790f4d6fc6364e05b9c433b77838ba575c15477-0": "           ENABLED yQQyE4Wv7hTvxQxCYAJQHJ3RYqp7p8ZM1U 1576192130  21621 155.138.228.109:40001",
 "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": "           ENABLED yXVCXKxDAwV6QVD1aQG1BZbh6uTCTSJBHw 1576191014  21617 45.62.239.200:40001"
}

Is that a problem?


  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #369 on: December 12, 2019, 06:55:45 PM »
I have my VPS on but not in sanc mode (collateral still not spent)

Code: [Select]
ifconfig -a ens160 | grep inet
       inet 45.62.239.200  netmask 255.255.255.0  broadcast 45.62.239.255

sanc status
error code: -32603
error message:
This is not a masternode

I had this Condition since yesterday but it is still ENABLED on the sanc list

Code: [Select]
>sanc list full
(Last line is this particular sanc)

{
 "a46074dac98333269341fee5b712f795fdeaa615b276fee12175e1c537ce8a43-1": "           ENABLED yVfoZ676zm9bjmU5qXbNe9TkGsHAxFYrDg 1576191507  21620 155.138.228.109:8003",
 "efbe80743321967f9d94b124b6670e3d87492e711f34acbe6fdada608007e055-0": "       POSE_BANNED yMFgidsw7EgVRfTwFU1hPWLmrPYcT1Bq7s 1576145873  21513 155.138.228.109:8002",
 "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583-1": "           ENABLED yTwJA2VCYQWpWXH8HS7UvEpqRE3Aj5ciUV 1576191075  21618 104.167.116.179:8080",
 "7570652f63502f29b610c4bf134f3d1d589c970c383b20a88545cd683c802130-1": "           ENABLED yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq 1576191197  21619 45.62.240.90:40001",
 "7c30c4cf73a81ce8ebb90b3cd6bcda3c279d86fb044605b3f95f75a1657cd19e-1": "       POSE_BANNED yZ6pvVMxJ8qXE15J6sPssG83FE5wkSik3N 1575350464  19686 155.138.220.139:40001",
 "c49f6f1e8fc8829b048abc37e790f4d6fc6364e05b9c433b77838ba575c15477-0": "           ENABLED yQQyE4Wv7hTvxQxCYAJQHJ3RYqp7p8ZM1U 1576192130  21621 155.138.228.109:40001",
 "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": "           ENABLED yXVCXKxDAwV6QVD1aQG1BZbh6uTCTSJBHw 1576191014  21617 45.62.239.200:40001"
}

Is that a problem?

Luckily Ive had my dev testnet node running for a couple days and I have you in my log;  It looks from my perspective we didnt see 239.200 as violating the rules for chainlocks or quorums until the last 4 hours ago:
2019-12-11 18:59:37 ERROR: AcceptBlockHeader: prev block ad556b39a713420cc879b19957c5080d19e4bed18d2fc3bdda2eca778c9617a1 conflicts with chainlock
2019-12-11 18:59:37 Misbehaving: 45.62.239.200:40001 peer=498 (70 -> 80)

I'm pretty confident your node will get POSE banned over the next 24 hours now that it is not in the quorums.  My sanc 228.109 is pose banned right now.  Ill go and try to revive it.

From what I know you have to violate the longer quorum (24 hours) before you start getting banned (or violate a chainlocks rule), then each of our sancs will vote you to 33% banned, then more and more etc.

But I believe its set up to pose ban with pretty solid decisions as no sanc can fake an LLMQ round.

Do you want to leave it down a little longer?





  • oncoapop
  • Full Member

    • 138


    • 14
    • October 23, 2018, 12:31:17 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #370 on: December 12, 2019, 07:38:14 PM »
Luckily Ive had my dev testnet node running for a couple days and I have you in my log;  It looks from my perspective we didnt see 239.200 as violating the rules for chainlocks or quorums until the last 4 hours ago:
2019-12-11 18:59:37 ERROR: AcceptBlockHeader: prev block ad556b39a713420cc879b19957c5080d19e4bed18d2fc3bdda2eca778c9617a1 conflicts with chainlock
2019-12-11 18:59:37 Misbehaving: 45.62.239.200:40001 peer=498 (70 -> 80)

I'm pretty confident your node will get POSE banned over the next 24 hours now that it is not in the quorums.  My sanc 228.109 is pose banned right now.  Ill go and try to revive it.

From what I know you have to violate the longer quorum (24 hours) before you start getting banned (or violate a chainlocks rule), then each of our sancs will vote you to 33% banned, then more and more etc.

But I believe its set up to pose ban with pretty solid decisions as no sanc can fake an LLMQ round.

Do you want to leave it down a little longer?

Yes leave it down until it is pose_banned and then revive it.


  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #371 on: December 12, 2019, 10:40:10 PM »
Yes leave it down until it is pose_banned and then revive it.

Aha!  You are getting Pose'd now :).


So its working, yay.  Btw, I revived mine an hour ago and Im back to 0, so that is working pretty good.



  • oncoapop
  • Full Member

    • 138


    • 14
    • October 23, 2018, 12:31:17 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #372 on: December 13, 2019, 04:08:27 AM »
Aha!  You are getting Pose'd now :).


So its working, yay.  Btw, I revived mine an hour ago and Im back to 0, so that is working pretty good.

I revived the sanc after it was confirmed to be banned on the sanc list. So it is good to know that the system works to rout out non-performing sancs by POSE_BANning them.

Code: [Select]

 "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": "           ENABLED yXVCXKxDAwV6QVD1aQG1BZbh6uTCTSJBHw 1576220632  21679 45.62.239.200:40001"



  • Rob Andrews
  • Administrator

    • 2346


    • 32
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #373 on: December 16, 2019, 10:58:37 AM »
Alright guys, thank you all for testing!

On behalf of BiblePay, and myself, we really appreciate all the help.

We're going to wrap this phase up.  From what I can see, everything is working OK.  Hopefully we won't have many surprises in prod-- and if we do, may they be cosmetic or very small issues that can be fixed with a leisure release.

At this point, I will start preparing a production release.

May Jesus be with us going forward!  And all Praise to Jesus for the knowledge and wisdom we have received up to this point in our project.

May you all have Jesus as your Lord and Savior.



  • sunk818
  • Sr. Member

    • 370


    • 17
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #374 on: December 17, 2019, 11:53:43 PM »
None of the CameroonONE kids are being recognized using TestNet RC1. They all say unprovisioned.