TestNet - PODC 2.0 (Proof of Distributed Computing)

BiblePay
1.4.8.4 - Mandatory Upgrade for TestNet

- Remove biblepaypool fields in getmininginfo
- Make PODC team configuration configurable by spork.  Allow any teams CPID to 'associate' or 'rac'.  Calculate the coin-age collateral req. exponent based on the config.
- Adjust DWS burn params for prod release.  Add DWS safety layer to double check rewards when the block exceeds the original base limit.  Require DWS rewards to be in the superblock if they exist.
- Enhance exec dwsquote 1 1 report to show a more consolidated report.
- Adjust Prod params to ready for mainnet release on Christmas

** All versions ready **

NOTE:  This version will also allow us to sync against mainnet, mine against mainnet, and verify the gsc passes in mainnet.  This version is theoretically the mainnet Christmas release candidate #1 (RC1).

1) Is there a way to check for sendgscc that is tardy and auto send it after wallet is synced and send it out one minute after? (kairos, wcg, cameroon-one)


2) you change dynamic whale stake to 7 days?
2a) we still have to wait 2 extra days for payment?


3) I guess I need to sendgscc wcg for my cpid to be recognized again?


21:14:13 exec rac
21:14:13
{
  "Command": "rac",
  "cpid": "c3939b61e69c6bde1eddb06708e0f96e",
  "temporary_cpid": "c3939b61e69c6bde1eddb06708e0f96e",
  "Error": "Your CPID is linked to your CPK, but we are unable to find your research records in WCG; most likely because you are not in team BiblePay yet.",
  "Step 1": "Log into your WCG account at 'worldcommunitygrid.org' with your WCG E-mail address and WCG password.",
  "Step 2": "Click Settings | My Profile.  Record your 'Username' and 'Verification Code' and your 'CPID' (Cross-Project-ID).",
  "Step 3": "Click Settings | Data Sharing.  Ensure the 'Display my Data' radio button is selected.  Click Save. ",
  "Step 4": "Click My Contribution | My Team.  If you are not part of Team 'BiblePay' click Join Team | Search | BiblePay | Select BiblePay | Click Join Team | Save.",
  "Step 5": "NOTE: After choosing your team, and starting your research, please give WCG 24 hours for the CPID to propagate into BBP.  In the mean time you can start Boinc research - and ensure the computer is performing WCG tasks. ",
  "Step 6": "From our RPC console, type, exec associate your_username your_verification_code",
  "Step 7": "Wait for 5 blocks to pass.  Then type 'exec rac' again, and see if you are linked!  ",
  "Step 8": "Once you are linked you will receive daily rewards.  Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC"
}

I'm stuck at Loading PoDC Researchers... for some reason.


Tried --erasechain and stuck there again.

Is there a default value for the spork when start the blockchain from scratch?

https://github.com/biblepay/biblepay-evolution/commit/306653b982ee1907ac2b13e54030f131012aae2a#diff-a0c8f511d90e83aa9b5857e819ced344R3027

I'm stuck at Loading PoDC Researchers... for some reason.


Tried --erasechain and stuck there again.

What version are you running?

Is there a default value for the spork when start the blockchain from scratch?

https://github.com/biblepay/biblepay-evolution/commit/306653b982ee1907ac2b13e54030f131012aae2a#diff-a0c8f511d90e83aa9b5857e819ced344R3027

Yes, zero.

And the value is set to zero currently, so we are in "0" mode.

Yes, zero.

And the value is set to zero currently, so we are in "0" mode.

When my wallet was stuck at loading PoDC researchers, I thought I had a corrupt blockchain so I did the --erasechain option.


1484 doesn't go past this screen for me.


I can't exit BiblePay-qt.exe unless I end the task manually from Task Manager.


1483 didn't have this problem... this is why I looked at the code and asked about it because the screen is stuck on Loading PoDC researchers...

When my wallet was stuck at loading PoDC researchers, I thought I had a corrupt blockchain so I did the --erasechain option.


1484 doesn't go past this screen for me.


I can't exit BiblePay-qt.exe unless I end the task manually from Task Manager.


1483 didn't have this problem... this is why I looked at the code and asked about it because the screen is stuck on Loading PoDC researchers...

So which platform are you running 1484 on?
MIP said he just finished the compile, so does this mean you self compiled QT on linux?

Unable to reproduce:  On all four of my 1484 nodes, the researchers load.

I just tested on windows also, 1484 loads researchers on windows.

So which platform are you running 1484 on?
MIP said he just finished the compile, so does this mean you self compiled QT on linux?

Unable to reproduce:  On all four of my 1484 nodes, the researchers load.

I just tested on windows also, 1484 loads researchers on windows.

Windows 10. I would have thought the EXE part and Task Manager would be hint enough. I'll try again tonight and let others chime in if they have an issue.

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

BiblePay
1.4.8.4 - Mandatory Upgrade for TestNet

- Remove biblepaypool fields in getmininginfo
- Make PODC team configuration configurable by spork.  Allow any teams CPID to 'associate' or 'rac'.  Calculate the coin-age collateral req. exponent based on the config.
- Adjust DWS burn params for prod release.  Add DWS safety layer to double check rewards when the block exceeds the original base limit.  Require DWS rewards to be in the superblock if they exist.
- Enhance exec dwsquote 1 1 report to show a more consolidated report.
- Adjust Prod params to ready for mainnet release on Christmas

** All versions ready **

NOTE:  This version will also allow us to sync against mainnet, mine against mainnet, and verify the gsc passes in mainnet.  This version is theoretically the mainnet Christmas release candidate #1 (RC1).

Linux x64 testnet

>cli -version
BiblePay Core RPC client version 1.4.8.4

>cli getblockcount
21050
>cli getblockhash 21050
c050dc13103b96de932787ed502520654ea13ba013528ba10b39a97a63f67681

sorry I sent the post prematurely. The CORRECT ratios are as follows:

TEAM           RAC       COINAGE REQD     RATIO
GRIDCOIN   6,023     1,116,115               185.3x
BIBLEPAY    9,569         149,679                15.6x

Output of exec rac

Code: [Select]

{
  "Command": "rac",
  "cpid": "xx003",
  "CPK": "xxb3d",
  "next_podc_gsc_transmission": 21217,
  "team_name": "Unknown",
  "external_purse_total_coin_age": 17926854.70136574,
  "coin_age_percent_required": 0.02855726425848298,
  "coin_age_required": 332673.380016672,
  "wcg_id": xxx83,
  "rac": 2826.58
}
{
  "Command": "rac",
  "cpid": "xxxaa5",
  "CPK": "xxxWPv",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 21217,
  "team_name": "Biblepay",
  "researcher_nickname": "oncoapop",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 4548281.74,
  "total_wcg_points": 31837972.18,
  "external_purse_total_coin_age": 20668208.12225695,
  "coin_age_percent_required": 0.0170824277899341,
  "coin_age_required": 146381.0915732143,
  "wcg_id": xxx773,
  "rac": 9406.974910000001
}

Team          Ratio
Gridcoin    117.69
Biblepay      15.56

Team info for team Gridcoin (and perhaps other team than Biblepay) not working.

I have tested 1.4.8.4 against mainnet and everything seems to sync properly (chain, sans, proposals, leaderboard...)

I have tested 1.4.8.4 against mainnet and everything seems to sync properly (chain, sans, proposals, leaderboard...)

Good.  And I started running one in the background and Ill leave it up.  So far it appears the governance info will sync through the next contract @162790, but we should watch it.  Ive solo mined successfully.  I tested nomp with it a few weeks ago also.

How about syncing in testnet, is that working for everyone?  I didnt have a problem upgrading or a researcher problem either.

I do see we have 3 POSE banned sancs; will the sancs please upgrade?  This way chainlocks wont blow out in testnet.

Output of exec rac

Code: [Select]

{
  "Command": "rac",
  "cpid": "xx003",
  "CPK": "xxb3d",
  "next_podc_gsc_transmission": 21217,
  "team_name": "Unknown",
  "external_purse_total_coin_age": 17926854.70136574,
  "coin_age_percent_required": 0.02855726425848298,
  "coin_age_required": 332673.380016672,
  "wcg_id": xxx83,
  "rac": 2826.58
}
{
  "Command": "rac",
  "cpid": "xxxaa5",
  "CPK": "xxxWPv",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 21217,
  "team_name": "Biblepay",
  "researcher_nickname": "oncoapop",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 4548281.74,
  "total_wcg_points": 31837972.18,
  "external_purse_total_coin_age": 20668208.12225695,
  "coin_age_percent_required": 0.0170824277899341,
  "coin_age_required": 146381.0915732143,
  "wcg_id": xxx773,
  "rac": 9406.974910000001
}

Team          Ratio
Gridcoin    117.69
Biblepay      15.56

Team info for team Gridcoin (and perhaps other team than Biblepay) not working.

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.