Bible Pay

TestNet => Active Discussions => Topic started by: Rob Andrews on November 01, 2019, 08:31:27 AM

Title: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 01, 2019, 08:31:27 AM
PODC 2.0 (Proof of Distributed Computing)



Welcome to the PODC 2.0 Testing thread.

In this thread we will be testing the Dash 0.14 branch with PODC 2.0:

(Please ensure your version is greater than this, otherwise your testnet branch will not sync.  We are at block 14,000 as of Nov 1, 2019).


Testnet Download Links:

Windows v.1.4.6.7+: https://biblepay.org/biblepayevo32develop.exe
Linux PC 32bits Daemon: https://biblepay.org/biblepayd-evo-testnet-i686-pc-linux-gnu.tar.gz
Linux QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux PC 64bits Daemon: https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz

Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz
Linux ARM32 daemon: https://biblepay.org/biblepayd-evo-testnet-arm-linux-gnueabihf.tar.gz
MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg

To self compile:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt


The ETA for MainNet for PODC 2.0 is November 30th, 2019.



CONFIGURING FOR TESTNET:


Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepayevolution

Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepayevolution/testnet3 folder.




NOTE: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html




USAGE INSTRUCTIONS FOR PODC 2.0:

https://wiki.biblepay.org/PODC






Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 02, 2019, 09:21:42 AM
Test Cases:

1) Please ensure you have upgraded to 1.4.6.7+ (this was a mandatory upgrade).

2) Please ensure your sanctuary is not POSE banned.  If it is, you can easily unban it with this command:
exec revivesanc sanc_name

3) Please ensure you are synced on the correct chain in testnet.  The block # is about 14005:
getblockhash 14005       266323d2e7daa74d570577a667ad8ed536c622c1f0b286d39605a964eb5dce9a

4) Please ensure you have a CPK in testnet:  If you don't you can create one with:  exec cpk your_nickname

5) Start crunching WCG tasks, so that your RAC is building up.

6) Familiarize yourself with these commands:
https://wiki.biblepay.org/PODC

7) Ensure your external purse (Christian-Public-Key) is funded with enough TestNet collateral.  Please make a post here if you need tBBP.

8 ) Type 'exec rac' and verify no errors exist.

9) Verify the SendAllGSC's works from the main thread without the miner running.  At the correct height shown in 'exec rac'.

10) Verify the RAC in the leaderboard matches your BOINC WCG RAC.

11) Verify unbanked CPIDs get rewarded without posting daily collateral.

12) Verify the collateral requirement for RAC is correct.  You can do this by typing exec rac, verify the coin-age % req.  Issue a sendgscc wcg, then check again and verify the amount in the GSC transmission was the correct amount of escrow req.

13) Verify at the daily GSC height, the sendgsccs are automatically sent.

14) Verify GSCs are sent with an encrypted and locked wallet, from the external purse.

15) Test the ability to create a DWS (exec dws).  Verify the DWS is actually received (by recording the sent DWS amount and duration).  Verify the 'exec dwsquote' amount looks good.

Regression Testing Cases:
We also need to re-verify old features work properly:

R1) Sponsor a child with cameroon (sponsorchild authorize). 
R2) Make a post to Rob to add a simulated Payment for you (give us the check #, amount, and childid).  We will enter it into the Cameroon-One testnet simulation.
R3) Verify the cameroon-one payment amount.
R4) Verify the HEALING campaign payment amount.
R5) Add a diary entry in both the command line (sendgscc HEALING diary), test that, and also test the Send Money Diary entry.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 04, 2019, 01:31:52 PM
BiblePay
1.4.6.7-Mandatory Upgrade for TestNet

- Fix 'fail to sign' transaction bug.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 04:26:14 PM
Ive spun up a Vultr Ubuntu server, and compiled from source,
Im not getting any connections though, is there an addnode IP address I could use? Thanks
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 04:28:30 PM
Ive spun up a Vultr Ubuntu server, and compiled from source,
Im not getting any connections though, is there an addnode IP address I could use? Thanks

Ill check the dns records in a few mins, but in the mean time please try this:

addnode add 107.173.41.176:44610
addnode add 107.173.41.176:39999
addnode add 107.173.41.178:55584

Please try with onetry behind the command, also

EDIT:  I see our first dns record, testnet.biblepay.org is answering on 40001 please try that as addnode?  Ill have to check the code to see if that is still hardcoded in, but it appears to be working if you add it.

EDIT2:  Ok, I think our 2nd DNS server was pose banned, now I reinstated both testnet and testnet1 again, please try now.  (addnode testnet.biblepay.org, testnet1.biblepay.org)





Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 04:41:51 PM
BiblePay
1.4.6.7-Mandatory Upgrade for TestNet

- Fix 'fail to sign' transaction bug.

Hi Capulo, welcome aboard!

Binaries should be working and are in the OP post.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 04:44:03 PM
Ive spun up a Vultr Ubuntu server, and compiled from source,
Im not getting any connections though, is there an addnode IP address I could use? Thanks

Ive got to head out to a thing for my son, Togo do you have an address that needs tbbp, then you can give some to Capulo and MIP?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 04:52:55 PM
Ive spun up a Vultr Ubuntu server, and compiled from source,
Im not getting any connections though, is there an addnode IP address I could use? Thanks

Here is some free bbp for anyone who wants it :


16:51:54

dumpprivkey ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA


16:51:54

cUWA5YrRZteBEo1hnqWv3xquyDY4V9zyJTeSqHtFeiCmjJsTxVoT


To claim it, import the privkey with "importprivkey key".

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 05:22:25 PM
I still seem to have troubles getting connections

My Test server IP address is:  155.138.220.139

My biblepay.conf file is:

Code: [Select]
testnet=1
addnode=testnet.biblepay.org
addnode=testnet1.biblepay.org
addnode=107.173.41.176:44610
addnode=107.173.41.176:39999
addnode=107.173.41.178:55584

Ive just been using daemon, havent setup/run the gui yet

getinfo shows my version as: 1040502

I have done -erasechain a couple times,
Ive even gone in a manually deleted almost everything in the /testnet3 folder

Maybe I just need to use a precompiled version?
I am now noticing that you have 1.4.6.7 in the posts,
whoops! on my end, Im on 1.4.5.2 from source
Ill use one of the precompiles and report back


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 05:29:16 PM
I was able to download these two files using "wget URL" command:

Linux PC 64bits Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

But I had to remove the extra dash in evo--testnet for the daemon version

I was able to unzip with "tar xzvf FILE" command
I see biblepayd, biblepay-cli and biblepay-tx
Im running ./biblepayd with erasechain
and I ran getinfo and I see error message "Loading PODC Researchers..."

Now I have 3 connections and Im shooting up fast on blocks! Yay!
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 05:32:58 PM
I match this blockhash

getblockhash 14005       266323d2e7daa74d570577a667ad8ed536c622c1f0b286d39605a964eb5dce9a

and Im currently at:

./biblepay-cli getblockhash 14318
c88816f2f6836fc5a15b56764cb5c90e60437c5db13ca89537a8b052394d2afb

===

I was able to import the privkey!

./biblepay-cli importprivkey cUWA5YrRZteBEo1hnqWv3xquyDY4V9zyJTeSqHtFeiCmjJsTxVoT

and I now have 4,000,000 tBBP, Thanks!
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 05:39:06 PM
I assume since the privkey is public, anyone else could also claim those test coins,
Im trying to send them to a new address, but its saying "Signing transaction failed",
Maybe I have to wait a few confirmations?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 07:50:16 PM
I still seem to have troubles getting connections

My Test server IP address is:  155.138.220.139

My biblepay.conf file is:

Code: [Select]
testnet=1
addnode=testnet.biblepay.org
addnode=testnet1.biblepay.org
addnode=107.173.41.176:44610
addnode=107.173.41.176:39999
addnode=107.173.41.178:55584

Ive just been using daemon, havent setup/run the gui yet

getinfo shows my version as: 1040502

I have done -erasechain a couple times,
Ive even gone in a manually deleted almost everything in the /testnet3 folder

Maybe I just need to use a precompiled version?
I am now noticing that you have 1.4.6.7 in the posts,
whoops! on my end, Im on 1.4.5.2 from source
Ill use one of the precompiles and report back

Just to clarify this, especially for anyone trying to comprehend this, Note that any version within 1.4.5.0 - 1.4.5.9 is within the Prod (mainnet) branch - and we call this the 0.13 branch (it matches Dash's .13 branch).  This is the branch with hybrid sancs.  Note that that branch will not work in testnet at all; this is because in testnet - the .14 branch is 100% deterministic.

So for testnet, we must have the users run on 1.4.6.7 and up for these to sync.

Thats awesome you got the 1.4.6.7 up - and synced and match the hash.
I do recommend the GUI QT version for testing; as you can see a lot of these test cases are rather complicated.  They can probably be done within the daemon however.

So I do have a question though, we had a bug in 1.4.6.6 with the transaction signing.  MIP had reported that he deployed 1.4.6.7 where the fix is.  Could you please double check the reported version of your client?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 07:52:19 PM
I assume since the privkey is public, anyone else could also claim those test coins,
Im trying to send them to a new address, but its saying "Signing transaction failed",
Maybe I have to wait a few confirmations?

Yes anyone can claim them til they are gone, or you can keep them and share them, either way.   If you only spend half then other people could take some but otoh it might be better if you are more available to resend them, either way works.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 07:53:37 PM
I was able to download these two files using "wget URL" command:

Linux PC 64bits Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

But I had to remove the extra dash in evo--testnet for the daemon version

I was able to unzip with "tar xzvf FILE" command
I see biblepayd, biblepay-cli and biblepay-tx
Im running ./biblepayd with erasechain
and I ran getinfo and I see error message "Loading PODC Researchers..."

Now I have 3 connections and Im shooting up fast on blocks! Yay!

The "Loading PODC..." is the UI status message of where the daemon currently is in the load process.  Same as "Memorizing Prayers...".

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 08:09:23 PM
So I do have a question though, we had a bug in 1.4.6.6 with the transaction signing.  MIP had reported that he deployed 1.4.6.7 where the fix is.  Could you please double check the reported version of your client?

For sure, yes, I am on version 1.4.6.7 of the Linux 64 bit Daemon,
and I confirm that I cant send the coins to a new address
"Signing transaction failed"
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 08:11:51 PM
For sure, yes, I am on version 1.4.6.7 of the Linux 64 bit Daemon,
and I confirm that I cant send the coins to a new address
"Signing transaction failed"

Is the wallet unencrypted and unlocked?

and, B), when you type 'dumpprivkey key' does it re-dump for you?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 08:17:01 PM
Is the wallet unencrypted and unlocked?

and, B), when you type 'dumpprivkey key' does it re-dump for you?

Also in the mean time please give me your address and ill instant send more from the foundation wallet?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 08:18:06 PM
Here is debug log:

2019-11-06 02:11:32 ThreadRPCServer method=sendtoaddress
2019-11-06 02:11:32 Unable to calculate fee, signing failed for

Wallet is unencrypted and unlocked

Code: [Select]
./biblepay-cli listreceivedbyaddress
[
  {
    "address": "ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA",
    "account": "",
    "amount": 5947608.19497465,
    "confirmations": 31,

Code: [Select]
./biblepay-cli dumpprivkey ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA
error code: -4
error message:
Private key for address ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA is not known

Ive never dumped before so I am not sure if I am doing it right

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 05, 2019, 08:19:46 PM
Here is an empty tBBP address:  yQHcgNP61KhRBuSsE4SUL1iZ6DAZZ8Ab63
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 05, 2019, 08:29:22 PM
Here is debug log:

2019-11-06 02:11:32 ThreadRPCServer method=sendtoaddress
2019-11-06 02:11:32 Unable to calculate fee, signing failed for

Wallet is unencrypted and unlocked

Code: [Select]
./biblepay-cli listreceivedbyaddress
[
  {
    "address": "ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA",
    "account": "",
    "amount": 5947608.19497465,
    "confirmations": 31,

Code: [Select]
./biblepay-cli dumpprivkey ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA
error code: -4
error message:
Private key for address ygWv5C6vncjW9xZUC7cGkrFysswG1raMFA is not known

Ive never dumped before so I am not sure if I am doing it right

I don't think this signing error is related to our prior error; you are running the latest version and I have the impression everything is working fine in this version so far.

For some reason it looks like your private key is not really imported.
When I do the command above, I can see the private key for the ygW* (dumpprivkey ygW*) etc.

Lets skip that for now and go the classic route; I just sent you 7mil from the foundation.

If anyone wants to try to import the key tonight and claim the funds, try reloading the wallet afterward with "-rescan=1" and see if it picks up the funds?


EDIT:  I removed the extra hyphen in the op post - thanks.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 06, 2019, 02:43:11 PM
Hi Rob.
I want to try testnet WCG, but I'm stuck on the beginning :D
I've made a mistake.
I've read sequence in "exec rac" and it looks that it  was bad.
There is written" Step 3": "From our RPC console, type, exec join wcg your_username your_verification_code"", so I've made it.
Then wait 6 blocks and try "exec rac" again,but didn't happen.
Still "Error": "Not Linked.  First, you must link your researcher CPID in the chain using 'exec associate'.",
After that I've read PODC manual again and there was command "exec associate wcg_username wcg_verification_code"
I tried it and this is my result:
Code: [Select]
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)I don't know what to do. I'm in Biblepay team from beginning, so maybe there is something wrong and I don't know what.
Or it's enough to wait?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 03:17:40 PM
Hi Rob.
I want to try testnet WCG, but I'm stuck on the beginning :D
I've made a mistake.
I've read sequence in "exec rac" and it looks that it  was bad.
There is written" Step 3": "From our RPC console, type, exec join wcg your_username your_verification_code"", so I've made it.
Then wait 6 blocks and try "exec rac" again,but didn't happen.
Still "Error": "Not Linked.  First, you must link your researcher CPID in the chain using 'exec associate'.",
After that I've read PODC manual again and there was command "exec associate wcg_username wcg_verification_code"
I tried it and this is my result:
Code: [Select]
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)I don't know what to do. I'm in Biblepay team from beginning, so maybe there is something wrong and I don't know what.
Or it's enough to wait?

Hi Orbis, Welcome aboard !  Let's look forward to the new positive age of BiblePay.

Could you please give me your CPK (public key) so I can try to do some queries?

EDIT: I don't see your exec associate in the chain; when you did the associate, did you include the correct verification code, and after that did it emit your RAC?  Please paste cpid also.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 06, 2019, 03:18:29 PM
i started wallet, but it started from block 0 and i have 0 connections
andi mining every block alone now...
how to get on your chain?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 03:23:29 PM
i started wallet, but it started from block 0 and i have 0 connections
andi mining every block alone now...
how to get on your chain?

What version are you running and what platform and what type (QT/non-qt)?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 06, 2019, 03:36:40 PM
1.4.6.7 qt win 32bit
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 03:39:26 PM
1.4.6.7 qt win 32bit

Not sure why people r having this, cause I see our two dns seeds are compiled in for testnet but try this:

1) Ensure time & timezone are correct
2) addnode=testnet1.biblepay.org
addnode testnet1.biblepay.org onetry

Let me know what works?

telnet testnet1.biblepay.org 40001 works

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 06, 2019, 04:12:37 PM
no, does not help
still mining one by one block...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 06, 2019, 04:23:00 PM
no, does not help
still mining one by one block...


biblepay-qt --erasechain to start over


make sure biblepay.conf has gen=0 when you start.


Get peers and sync up to latest block height. You can make it gen=1 after you are synced to blockchain. If you mine blocks at block 0, you will never join peers on testnet since blockhash will not match.


this is only way I can get testnet to sync up. you will eventually find testnet peers.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 06, 2019, 04:33:19 PM
looks a bit better, now it want to sync over 2y long chain
but i had  0 connection so far
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 04:34:38 PM
looks a bit better, now it want to sync over 2y long chain
but i had  0 connection so far


Also try what Sun suggested, try this:

gen=0 in config

Then start with:

./biblepay-qt -erasechain=1

We only have 14k blocks in testnet, thats why I ask to paste the getinfo.

EDIT:
Btw, how many connections do you have, if you have more than 1 it is just a gen=0 issue, just erase the chain?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 06, 2019, 04:51:12 PM
Hi Orbis, Welcome aboard !  Let's look forward to the new positive age of BiblePay.

Could you please give me your CPK (public key) so I can try to do some queries?

EDIT: I don't see your exec associate in the chain; when you did the associate, did you include the correct verification code, and after that did it emit your RAC?  Please paste cpid also.
Hi,
my cpk: ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg
my CPID: 04fba56d89a5eb38b1b82f8a6240132c
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 04:56:33 PM
Hi,
my cpk: ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg
my CPID: 04fba56d89a5eb38b1b82f8a6240132c
I dont see your 'exec associate' in the chain; it looks like it has no verification code; please try 'exec associate wcg_username wcg_verificationcode true'.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 06, 2019, 05:00:11 PM
I dont see your 'exec associate' in the chain; it looks like it has no verification code; please try 'exec associate wcg_username wcg_verificationcode true'.
OK, I'll try it.
Meanwhile, which method is correct?
exec rac: " Step 3": "From our RPC console, type, exec join wcg your_username your_verification_code""
or PODC manual: "exec associate wcg_username wcg_verification_code"
It looks that PODC manual, or those method in exec RAC is something different?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 06, 2019, 05:01:40 PM
result:

00:00:45
exec associate orbis XXXXX true


00:00:46
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 05:06:56 PM
OK, I'll try it.
Meanwhile, which method is correct?
exec rac: " Step 3": "From our RPC console, type, exec join wcg your_username your_verification_code""
or PODC manual: "exec associate wcg_username wcg_verification_code"
It looks that PODC manual, or those method in exec RAC is something different?

Ok, this could be how you got hosed.

The core client should *not* say 'exec join' it should say 'exec associate' (per the wiki page).

I have just corrected the core client to say 'exec associate' for the next release.

UPDATE:  Please everyone, only follow the wiki page, not the 'exec join' from the helpful hint for now.

That explains how you got a partial record stored and got hosed into step 2 in exec rac.

Anyway, the exec associate should set you up as if you did it correctly (with that true) at the end.

So after 3 more blocks you should be able to proceed as normal.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 06, 2019, 05:10:56 PM
It clearly says in the PODC manual you have to wait 3 blocks after the registration before trying exec rac.

So now you have to wait (if the tx went out).
It didn't create any tx.
Just give me this error.
Only one tx created was from those "exec join wcg your_username your_verification_code" command.
It took me 5000tBBP in Christian Public Keypair Association tx: 41c946bb680e21fc56d44ad360e2b205fdcd376a6fa9af4fd2f50147de81759b
Since this tx there is only error message when I try "associate".
Ok, let it be for today. I'll check it tommorow, maybe it'll be OK.
Thanks
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 05:18:03 PM
It didn't create any tx.
Just give me this error.
Only one tx created was from those "exec join wcg your_username your_verification_code" command.
It took me 5000tBBP in Christian Public Keypair Association tx: 41c946bb680e21fc56d44ad360e2b205fdcd376a6fa9af4fd2f50147de81759b
Since this tx there is only error message when I try "associate".
Ok, let it be for today. I'll check it tommorow, maybe it'll be OK.
Thanks

Ok your right, there is a problem when people do the 'exec join' instead of 'exec associate' it puts you in a state you cannot escape from!  So I had to add a line of code to allow the wallet to honor the 'true' (force) to always re-send the association in the next version.

For now, could you please try this:  exec unjoin wcg
Then wait just 2 blocks, then do the 'exec associate' again?  (With force=true)?  Then I think it will go out.

You should not be sending 5000 bbp for association; could you please give me the txid so I can analyze how that occurred?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 05:20:29 PM
I think we need Oncoapop back, I see the POSE banned sancs are causing safe mode- Oncoapop are you available to unban?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 06, 2019, 06:17:56 PM
I think we need Oncoapop back, I see the POSE banned sancs are causing safe mode- Oncoapop are you available to unban?

I’m trying to restart them but i used the Dash DIP3 route and hence do not have a deterministric.conf
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 07:05:18 PM
I’m trying to restart them but i used the Dash DIP3 route and hence do not have a deterministric.conf

Glad you are back dude, hey you can type 'exec revivesanc' and it should have the instructional command.

If not, IE if you are missing the blsprivkey, Ive learned its also pretty easy to just spend the output and recreate the sanc.  But the bls priv key is in the sanc itself in the config file, and right clicking on the sanc in the home host reveals the pro-tx-id.  The Sanc IP is of course, public already.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 06, 2019, 07:06:15 PM
Once we get these 'quirks' out (regarding exec associate), Ill rerelease and we can do a dry run with this to ensure PODC 2.0 is a success in prod.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 07, 2019, 12:40:17 AM
Im not sure you are on the right version; what does getinfo say?

You mentioned 1467, can you please paste the output?

Also try what Sun suggested, try this:

gen=0 in config

Then start with:

./biblepay-qt -erasechain=1

We only have 14k blocks in testnet, thats why I ask to paste the getinfo.

EDIT:
Btw, how many connections do you have, if you have more than 1 it is just a gen=0 issue, just erase the chain?

0 connections so far
I have gen=0, 1467, tried erasechain ...

sometimes this happens also onnormal wallet that it could not start because it does not have connections... in that case I just need to copy peers file from working wallet and it starts working
could somebody send me peers.dat file? [email protected]
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 09:14:14 AM
0 connections so far
I have gen=0, 1467, tried erasechain ...

sometimes this happens also onnormal wallet that it could not start because it does not have connections... in that case I just need to copy peers file from working wallet and it starts working
could somebody send me peers.dat file? [email protected]
Haha this coin is being attacked by the devil in so many ways.
But Capulo thats not normal, I have multiple options for you - we know we can control what goes into the peers.dat.

First, I just reconfirmed testnet1.biblepay.org really does work.  Lets try this:

./biblepay-qt -connect=testnet1.biblepay.org

See if you can connect?  When I do that, I connect directly to testnet1 and have 1 connection.
Then you can add the two nodes (actually its nonsense because they are compiled in).

Please try deleting banlist.dat also.

Let me give a screen shot of Sancs also, you can manually add these addnodes (as sancs act as full nodes also):

Here you go  these sancs are connected, you can "addnode IP:PORT add" :


09:13:12

{
  "a46074dac98333269341fee5b712f795fdeaa615b276fee12175e1c537ce8a43-1": {
    "proTxHash": "4abca3eac4465618cc64c49be55dc2199429c6d3df2f0a3a806f99f668855c89",
    "address": "107.173.41.178:40001",
    "payee": "yVfoZ676zm9bjmU5qXbNe9TkGsHAxFYrDg",
    "status": "ENABLED",
    "lastpaidtime": 1573138265,
    "lastpaidblock": 14737,
    "owneraddress": "yVHDpb6mhCUofghKvv2er6rDDDF81fyWaE",
    "votingaddress": "yVHDpb6mhCUofghKvv2er6rDDDF81fyWaE",
    "collateraladdress": "yfi5p7iaYECqF2H9BQ3Ug1xoxmNuX3SzjU",
    "pubkeyoperator": "118e0a6eb14ba07147314e88e8b8fff0d98e362b2344c9d5c3b2282efdef6f377cb0286355aadee8b4d36eb0de2faf24"
  },
  "7570652f63502f29b610c4bf134f3d1d589c970c383b20a88545cd683c802130-1": {
    "proTxHash": "3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0",
    "address": "45.62.240.90:40001",
    "payee": "yXhRHuA2YsV44K5VZJyQSxZurQ8s7diKbq",
    "status": "POSE_BANNED",
    "lastpaidtime": 1571319397,
    "lastpaidblock": 10471,
    "owneraddress": "yUsK4HwXHY8X5AejKqXnA5SuydxGMyYuwC",
    "votingaddress": "yUsK4HwXHY8X5AejKqXnA5SuydxGMyYuwC",
    "collateraladdress": "yViEWMSQKhV3rkJPpRebSoUJcmHQAc7mmF",
    "pubkeyoperator": "0f89850a75396771518c92236f9a27ad42a4e735d3721b974fb86b92131a31754a25bf63098812321f75e826fecaae6a"
  },
  "efbe80743321967f9d94b124b6670e3d87492e711f34acbe6fdada608007e055-0": {
    "proTxHash": "586d88bcedba21fd291a8138279235e2e68bf399337a030307ead02062ce16bc",
    "address": "107.173.41.179:39998",
    "payee": "yMFgidsw7EgVRfTwFU1hPWLmrPYcT1Bq7s",
    "status": "ENABLED",
    "lastpaidtime": 1573137654,
    "lastpaidblock": 14735,
    "owneraddress": "yfecgJG6BxHWGubv7TYknHjJM2zdXUxRuN",
    "votingaddress": "yfecgJG6BxHWGubv7TYknHjJM2zdXUxRuN",
    "collateraladdress": "yWcmJfAuMXznZMHwvAssSjiZDV5KgVLTW8",
    "pubkeyoperator": "8f51e452410c72034d046d939bde4ae1575f78bcdabc4a85db80c7d308816eb81956a994595dbfc6f50fe83a9aac90df"
  },
  "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583-1": {
    "proTxHash": "71ac8f0a0b11a7070b4aa2e1862c19a8c5d5106bc5172502ebe8ce87772afc5d",
    "address": "104.167.116.179:8080",
    "payee": "yTwJA2VCYQWpWXH8HS7UvEpqRE3Aj5ciUV",
    "status": "ENABLED",
    "lastpaidtime": 1573137716,
    "lastpaidblock": 14736,
    "owneraddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "votingaddress": "yQkfqAeFpZzwHmpXti7avavNAu6etwCjAn",
    "collateraladdress": "ye1qsekeUyC2LpgLymLCremqCcjkLCgWpH",
    "pubkeyoperator": "139234c6a2d2f2f449fe5b25006fef684a5be440372756d903f1c793da49812202933c13a8d750ebeb270ea96b62480d"
  },
  "c49f6f1e8fc8829b048abc37e790f4d6fc6364e05b9c433b77838ba575c15477-0": {
    "proTxHash": "de494ea73d57e52f5a7fa4daebcdf1987871fafda267e8c01ea8fd441d718f97",
    "address": "107.173.41.176:39999",
    "payee": "yQQyE4Wv7hTvxQxCYAJQHJ3RYqp7p8ZM1U",
    "status": "ENABLED",
    "lastpaidtime": 1573137467,
    "lastpaidblock": 14734,
    "owneraddress": "yLpznVb2MNb3XxGyT149Xj9dAbqJZD56DA",
    "votingaddress": "yLpznVb2MNb3XxGyT149Xj9dAbqJZD56DA",
    "collateraladdress": "ygGKQR4bYwjGaEnX8KCyzEJhht4paYCiuo",
    "pubkeyoperator": "82fe87487aae31a997366cde135b00ebf2c8ef38254ebe8bd5303a620637c0aa1c6216f2d93943964f6afebf6a577a9f"
  },
  "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": {
    "proTxHash": "7b35f78ef2d601233e97fe16000d8f6d014070a65b47776d2d6e0dd1a4644f97",
    "address": "45.62.239.200:40001",
    "payee": "yXVCXKxDAwV6QVD1aQG1BZbh6uTCTSJBHw",
    "status": "POSE_BANNED",
    "lastpaidtime": 1572472153,
    "lastpaidblock": 13139,
    "owneraddress": "yjaKsxgaBUuFgeXFUz7ygumZBKsG1Txpao",
    "votingaddress": "yjaKsxgaBUuFgeXFUz7ygumZBKsG1Txpao",
    "collateraladdress": "yRTF8fswRZg7pCNBbtZTUVvRWBYCUi6PVK",
    "pubkeyoperator": "821500eb46d4a807e23d94978702ef263260ae27eaf0f8cd3d249e765a485cf80c6aecc327282ac1d0b833c64866160c"
  }
}



Dont use the ones that say POSE Banned though.

But overall - the connect idea should work fine.




Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 07, 2019, 11:33:20 AM
Ok your right, there is a problem when people do the 'exec join' instead of 'exec associate' it puts you in a state you cannot escape from!  So I had to add a line of code to allow the wallet to honor the 'true' (force) to always re-send the association in the next version.

For now, could you please try this:  exec unjoin wcg
Then wait just 2 blocks, then do the 'exec associate' again?  (With force=true)?  Then I think it will go out.

You should not be sending 5000 bbp for association; could you please give me the txid so I can analyze how that occurred?
Here are my results :)
Code: [Select]
17:17:50  exec unjoin wcg
17:17:52
{
  "Command": "unjoin",
  "Results": true
}
So, it looks good.
Then, after 2 blocks, my first try:
Code: [Select]
17:22:47  exec associate orbis XXXXX true
17:22:47
Unable to find orbis.  Please type exec rac to see helpful hints to proceed.  (code -1)
So, I wasn't successful.
After 6+ blocks:
Code: [Select]
18:26:00 exec associate orbis XXXXX true
18:26:00
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)
Still unsuccessful :(
It looks, that I'll wait for new wallet version.
BTW: after "exec unjoin" there were -5000tBBP tx again: 875df26d46d3667f1443a5f3e13aedddad0a0142687faf28c893047e42ad6986
So, it looks, that "join" and "unjoin" tx are "paid".
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 07, 2019, 12:45:44 PM
nothing works, still 0 connections even with -connect parameter...
but i found something
i tried telnet again and it is not working now. when i tried it first i was on us vpn and it works, now i'm not on vpn and it is not working, so i think there is something what is blocking me :)
when i connect to vpn telnet works again...
but i cant install wallet here (work pc) so i cant try if wallet will work
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 02:40:34 PM
nothing works, still 0 connections even with -connect parameter...
but i found something
i tried telnet again and it is not working now. when i tried it first i was on us vpn and it works, now i'm not on vpn and it is not working, so i think there is something what is blocking me :)
when i connect to vpn telnet works again...
but i cant install wallet here (work pc) so i cant try if wallet will work

Just for sanity sake Im trying to get the root of the problem :),  I just deleted banlist on both DNS servers; can you please try your test again?



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 02:43:59 PM
Here are my results :)
Code: [Select]
17:17:50  exec unjoin wcg
17:17:52
{
  "Command": "unjoin",
  "Results": true
}
So, it looks good.
Then, after 2 blocks, my first try:
Code: [Select]
17:22:47  exec associate orbis XXXXX true
17:22:47
Unable to find orbis.  Please type exec rac to see helpful hints to proceed.  (code -1)
So, I wasn't successful.
After 6+ blocks:
Code: [Select]
18:26:00 exec associate orbis XXXXX true
18:26:00
Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)
Still unsuccessful :(
It looks, that I'll wait for new wallet version.
BTW: after "exec unjoin" there were -5000tBBP tx again: 875df26d46d3667f1443a5f3e13aedddad0a0142687faf28c893047e42ad6986
So, it looks, that "join" and "unjoin" tx are "paid".

I don't think we need a new release yet, because so far we just have the change for the one word - IE ask everyone to perform 'exec associate' instead of exec join, please let me look into this.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 02:59:12 PM
I don't think we need a new release yet, because so far we just have the change for the one word - IE ask everyone to perform 'exec associate' instead of exec join, please let me look into this.

No wonder you are having so many issues Orbis, you are on the wrong chain, please resync with "-erasechain=1" then verify this hash:

14:57:54

getblockhash 14700


14:57:54

92c8c16680413fb1f36bd8c9b389c5ad87cbf14f377a7936509656e714c11ea0



Then, start over with the 'exec cpk your_nickname' then the 'exec associate wcg_username wcg_verification_code' command, and see if that is successful?

I will not be able to track the 5K you refer to until you are on the same chain as me.  If it happens again please re-paste.




Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 07, 2019, 03:06:36 PM
I noticed for the Linux 64 bits QT link it says:
https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

But I think it should be:
https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz

I replaced i686 with x86_64 and it worked, running QT version now!

===

Here are my old notes on using GUI on Vultr server

1. Install Lubuntu GUI and Reboot
https://www.vultr.com/docs/install-gui-environment-for-ubuntu

Code: [Select]
apt-get update
apt-get install -y lubuntu-core
reboot

2. On Vultr Server Information page click "View Console" button in top right

3. Press Ctrl - Alt + T to open a Terminal

===

Ill setup a sanctuary now
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 03:10:04 PM
I noticed for the Linux 64 bits QT link it says:
https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

But I think it should be:
https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz

I replaced i686 with x86_64 and it worked, running QT version now!

===

Here are my old notes on using GUI on Vultr server

1. Install Lubuntu GUI and Reboot
https://www.vultr.com/docs/install-gui-environment-for-ubuntu

Code: [Select]
apt-get update
apt-get install -y lubuntu-core
reboot

2. On Vultr Server Information page click "View Console" button in top right

3. Press Ctrl - Alt + T to open a Terminal

===

Ill setup a sanctuary now

I like the notes about QT;  Ill look into changing this link next.

So on a side note, we could probably use an addl sanctuary since so many have been pose banned, and, in addition we can do some chainlocks testing toward the end of November- and we def could use healthy sancs for that (IE more than 4).  Right now we have 4 healthy and 2 unhealthy.


EDIT: Link fixed, thanks.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 07, 2019, 03:21:19 PM
Linux 64 bit QT, I got a signing transaction failed message,
I did an erasechain and a rescan

Im still getting signing transaction failed,
I tested with two different inputs by themselves sending to another address

getinfo shows version: 1040607

Debug log just shows:  "Unable to calculate fee, singing failed for"
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 03:32:26 PM
Linux 64 bit QT, I got a signing transaction failed message,
I did an erasechain and a rescan

Im still getting signing transaction failed,
I tested with two different inputs by themselves sending to another address

getinfo shows version: 1040607

Debug log just shows:  "Unable to calculate fee, singing failed for"

Where did you get the source funds?

And is it possible for you to dump the private key for the source address?

I recommend zapping the wallet txes and using the foundation funds only (IE funds from one of us) for this test.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 07, 2019, 03:44:21 PM
I performed a zapwallettxes

yQHcgNP61KhRBuSsE4SUL1iZ6DAZZ8Ab63
has 165 confirmations and 7,000,000 tBBP
I believe these are the coins you sent me yesterday

ygQv5C6vncjW9xZUC7cGkrFysswG1raMFA
has 11 confirmations and 1,000 tBBP
I'm not sure where this came from

I cant dumpprivkey for either address
"Private key for address X is not known"
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 07, 2019, 03:48:06 PM
My getblockhash matches

Code: [Select]
getblockhash 14700
92c8c16680413fb1f36bd8c9b389c5ad87cbf14f377a7936509656e714c11ea0

Hmmm, I could pass you the server credentials privately if you are interested to check it out directly
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 03:52:49 PM
I performed a zapwallettxes

yQHcgNP61KhRBuSsE4SUL1iZ6DAZZ8Ab63
has 165 confirmations and 7,000,000 tBBP
I believe these are the coins you sent me yesterday

ygQv5C6vncjW9xZUC7cGkrFysswG1raMFA
has 11 confirmations and 1,000 tBBP
I'm not sure where this came from

I cant dumpprivkey for either address
"Private key for address X is not known"

Yeah, could you send them?  I guess we need to see what is really going on here!

Thanks.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 07, 2019, 04:33:31 PM
For sure, sent you message on this forum and bitcointalk forum a little bit ago
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 07, 2019, 04:56:33 PM
Glad you are back dude, hey you can type 'exec revivesanc' and it should have the instructional command.

If not, IE if you are missing the blsprivkey, Ive learned its also pretty easy to just spend the output and recreate the sanc.  But the bls priv key is in the sanc itself in the config file, and right clicking on the sanc in the home host reveals the pro-tx-id.  The Sanc IP is of course, public already.

Sorry, I can’t revive my sanc Nor can I spend the transaction....

cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9
error code: -32603
error message:
No funds at specified address (special transaction error)

ok - I choose an address with funds
 "ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV": 9.93668000,

cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9 ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV
error code: -32603
error message:
Signing transaction failed

cli walletpassphrase
error code: -15
error message:
Error: running with an unencrypted wallet, but walletpassphrase was called.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 05:10:08 PM
For sure, sent you message on this forum and bitcointalk forum a little bit ago

Ok, so it looks like (I make the assumption) that all the builds are bad for 1.4.6.7 except the two windows builds.

So, let me look into releasing the thing that hung up Orbis next and incrementing to 1.4.6.8.  And we will have a rebuild.

In the mean time if you have time, you can try the windows version with your wallet.dat that you have now, and see if it succeeds?

EDIT:  Actually what might be better is just build the latest from source (git pull origin develop).
Then you will know you have the latest.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 05:11:35 PM
Sorry, I can’t revive my sanc Nor can I spend the transaction....

cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9
error code: -32603
error message:
No funds at specified address (special transaction error)

ok - I choose an address with funds
 "ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV": 9.93668000,

cli protx update_service 3a24f0ffe9b074abd5774d1c4e0627fc39a8a029f475f629cbcd52350e1455d0 45.62.239.200:40001 579fcbc90face5e28d5312a0e0df87606f67adf62d71305701c551133d75c9d9 ye9fvYw4vgHmSrVT8cd8wVLNmSBLZh7ikV
error code: -32603
error message:
Signing transaction failed

cli walletpassphrase
error code: -15
error message:
Error: running with an unencrypted wallet, but walletpassphrase was called.

Could you confirm what platform version this is, is this a linux qt build?  Or windows?

Self compiled or a binary?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 07, 2019, 05:18:16 PM
Could you confirm what platform version this is, is this a linux qt build?  Or windows?

Self compiled or a binary?

Linux command line
cli -version
BiblePay Core RPC client version 1.4.6.7

binaries from
https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz





Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 05:29:59 PM
Linux command line
cli -version
BiblePay Core RPC client version 1.4.6.7

binaries from
https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz

Ok, I make the assumption you are also affected by the problem I pasted for Togo, so if you want to work quickly please self-compile and then retry your sanctuary revive or spend;  or alternatively please wait for 1.4.6.8.


I will work on this now for new release.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 07, 2019, 05:40:03 PM
Just for sanity sake Im trying to get the root of the problem :),  I just deleted banlist on both DNS servers; can you please try your test again?

coool, now i have 5 connection and i'm on block 14807
seems we found rootcase :D
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 07, 2019, 05:48:53 PM
yWurZhEW51tyVGqgxMtYLmBFNHvAPcyeRu
this is my address, pls send me some coins
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 05:50:03 PM
coool, now i have 5 connection and i'm on block 14807
seems we found rootcase :D

Oh wow, so basically let me try to guess:

You connected early on in the game with the wallet defaults, and the wallet started mining at the genesis block.
It added 10 blocks or so very easily.
Then when you got a connection to the dns nodes, they banned you because you were trying to pass on invalid headers (this is a dash rule that gives you a very huge penalty for doing that).

So you probably then switched back to gen=0 but it was too late.
We will have to remember this for the future, as in testnet its easy to solve blocks because of that not-requiring-peers rule.

That reminds me, in prod, btw, you are not allowed to mine without peers, so this all makes sense now!

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 07, 2019, 05:54:33 PM
Ok, I make the assumption you are also affected by the problem I pasted for Togo, so if you want to work quickly please self-compile and then retry your sanctuary revive or spend;  or alternatively please wait for 1.4.6.8.


I will work on this now for new release.

I’ll wait as compiling failed....

In file included from bls/bls.cpp:5:0:
bls/bls.h:14:10: fatal error: chiabls/bls.hpp: No such file or directory
 #include <chiabls/bls.hpp>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:9965: recipe for target 'bls/libbiblepayconsensus_la-bls.lo' failed
make[1]: *** [bls/libbiblepayconsensus_la-bls.lo] Error 1
make[1]: Leaving directory '/home/bbp/biblepay-evolution/src'
Makefile:11637: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 07, 2019, 06:12:38 PM
Oh wow, so basically let me try to guess:

You connected early on in the game with the wallet defaults, and the wallet started mining at the genesis block.
It added 10 blocks or so very easily.
Then when you got a connection to the dns nodes, they banned you because you were trying to pass on invalid headers (this is a dash rule that gives you a very huge penalty for doing that).

So you probably then switched back to gen=0 but it was too late.
We will have to remember this for the future, as in testnet its easy to solve blocks because of that not-requiring-peers rule.

That reminds me, in prod, btw, you are not allowed to mine without peers, so this all makes sense now!

yes, it was this way :)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 07:31:36 PM
yWurZhEW51tyVGqgxMtYLmBFNHvAPcyeRu
this is my address, pls send me some coins

Sent!

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 07:33:19 PM
I’ll wait as compiling failed....

In file included from bls/bls.cpp:5:0:
bls/bls.h:14:10: fatal error: chiabls/bls.hpp: No such file or directory
 #include <chiabls/bls.hpp>
          ^~~~~~~~~~~~~~~~~
compilation terminated.
Makefile:9965: recipe for target 'bls/libbiblepayconsensus_la-bls.lo' failed
make[1]: *** [bls/libbiblepayconsensus_la-bls.lo] Error 1
make[1]: Leaving directory '/home/bbp/biblepay-evolution/src'
Makefile:11637: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

To get by that, you have to follow the compile instructions in the area that says "cd biblepay-evolution/depends", "make...":
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 07, 2019, 08:16:34 PM

03:14:11

exec associate capulo nnn


03:14:12

Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)


but i'm in biblepay team.. so? :)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 07, 2019, 10:01:11 PM
Hey All-

I see we have a very squirrely issue, its almost as if Im the only wallet that is miraculously working.

Ive been moving the wallet file to different servers and seeing a different result, so Ive come to the conclusion that we need a bug fixed.

Please stop testing until I can trace this root problem.

Thanks!


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 08, 2019, 04:04:18 PM
BiblePay
1.4.6.9 - Mandatory Upgrade for TestNet


- Fix key signing issue

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 08, 2019, 04:12:24 PM

03:14:11

exec associate capulo nnn


03:14:12

Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team.  Please join team BiblePay or team Gridcoin to proceed.  Please type 'exec rac' to see more helpful hints.  NOTE:  You may check back again once every 12 hours to see if you are on the team.  (code -1)


but i'm in biblepay team.. so? :)

I don't actually see your 'exec associate' in the chain; I assume it was the issue we had (where the wallet was not signing the tx).  Please try the exec associate again with the force true at the end?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 09, 2019, 11:48:16 AM
No wonder you are having so many issues Orbis, you are on the wrong chain, please resync with "-erasechain=1" then verify this hash:

getblockhash 14700
92c8c16680413fb1f36bd8c9b389c5ad87cbf14f377a7936509656e714c11ea0

Then, start over with the 'exec cpk your_nickname' then the 'exec associate wcg_username wcg_verification_code' command, and see if that is successful?

I will not be able to track the 5K you refer to until you are on the same chain as me.  If it happens again please re-paste.

Sorry, but I was few days away. Now It looks that I'm on right chain and associate was successful.
Code: [Select]
  "Command": "associate",
  "wcg_member_id": 1065540,
  "wcg_points": 55771096,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"
My associate TX was again with 5k tBBP. here is: 0fcb5b796acc141badc30954ac5fafa3d4d1fd458398b24cbde31ea2da0642a7
I sent all of my tBBP (75k) to external purse so I'll be waiting if it goes good. Thanks
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 09, 2019, 12:01:05 PM
Glad you were able to pinpoint the issue Rob! yay!

I downloaded v1.4.6.9, and I was able to successfully send coins!

How many coins are needed for a sanctuary?
I have 2,020,209.26 tBBP right now

Here is another receiving address:
ygkRiAMGaZaZM2ctREJ7mWRsFyG3emTtzt

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 09, 2019, 12:05:39 PM
Glad you were able to pinpoint the issue Rob! yay!

I downloaded v1.4.6.9, and I was able to successfully send coins!

How many coins are needed for a sanctuary?
I have 2,020,209.26 tBBP right now

Here is another receiving address:
ygkRiAMGaZaZM2ctREJ7mWRsFyG3emTtzt

Sent. 4,500,001 required for each DIP3 sanc. Glad to have you set up a couple.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 09, 2019, 12:47:35 PM
BTW, it's needed to run any command after associate (e.g. sendgscc) to run WCG within BBP network? Or it's enough to wait?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 09, 2019, 02:12:29 PM
Sorry, but I was few days away. Now It looks that I'm on right chain and associate was successful.
Code: [Select]
  "Command": "associate",
  "wcg_member_id": 1065540,
  "wcg_points": 55771096,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"
My associate TX was again with 5k tBBP. here is: 0fcb5b796acc141badc30954ac5fafa3d4d1fd458398b24cbde31ea2da0642a7
I sent all of my tBBP (75k) to external purse so I'll be waiting if it goes good. Thanks

Thats awesome on the partial success, Orbis.

I'm kind of surprised we are having so many small issues - its probably due to these partial successful associations etc.

What Im getting at is, for some reason, your WCG record was stored with no CPID.  I don't even see how that can happen because we do check for the length of it to be 32 before we save your record.

First let me answer your question:

The normal newbie would do this:
exec cpk nickname
wait 5 blocks
exec associate orbis wcg_userid wcg_code
wait 5 blocks
type :
exec rac

And see your rac.  But -- I think you re probably seeing 0 for the rac right now.  However, I do see that you are on the team and can see your cpid.

Can you do me a favor... please try the exec associate again with force=true after it, and see if it shows your CPID and RAC right after association?
CLARIFICATION:  Plz do it this way:
exec associate wcg_username wcg_verificationcode true

Ill have to try to reproduce this; so far Ive associated my cpid 4 times successfully.  Lets also see if anyone else has tested this yet.

Ill check into the 5k issue.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 09, 2019, 02:13:47 PM
BTW, it's needed to run any command after associate (e.g. sendgscc) to run WCG within BBP network? Or it's enough to wait?

Once you see that 'exec rac' is showing a RAC > 1, and, showing your CPID, then all you would need to do is this:
sendgscc wcg

And that would put you in the smart contract daily.  But, we have podc 2.0 designed to automatically do that once per day at a certain height (which I will explain later), but - you would have had to leave the controller running for 24 hours.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 09, 2019, 02:31:48 PM
Thats awesome on the partial success, Orbis.

I'm kind of surprised we are having so many small issues - its probably due to these partial successful associations etc.

What Im getting at is, for some reason, your WCG record was stored with no CPID.  I don't even see how that can happen because we do check for the length of it to be 32 before we save your record.

First let me answer your question:

The normal newbie would do this:
exec cpk nickname
wait 5 blocks
exec associate orbis wcg_userid wcg_code
wait 5 blocks
type :
exec rac

And see your rac.  But -- I think you re probably seeing 0 for the rac right now.  However, I do see that you are on the team and can see your cpid.

Can you do me a favor... please try the exec associate again with force=true after it, and see if it shows your CPID and RAC right after association?
CLARIFICATION:  Plz do it this way:
exec associate wcg_username wcg_verificationcode true

Ill have to try to reproduce this; so far Ive associated my cpid 4 times successfully.  Lets also see if anyone else has tested this yet.

Ill check into the 5k issue.

Hi Orbis,

I see that exec associate charges 0 + fees.  Are you sure you are typing exec associate to generate that transaction?

EDIT:  I did a reassociate; it charged me 0.  Your running a compiled version of bbp?



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 09, 2019, 03:38:25 PM
Can you do me a favor... please try the exec associate again with force=true after it, and see if it shows your CPID and RAC right after association?
CLARIFICATION:  Plz do it this way:
exec associate wcg_username wcg_verificationcode true

Ill have to try to reproduce this; so far Ive associated my cpid 4 times successfully.  Lets also see if anyone else has tested this yet.
So, it looks that I'm totally noob, because it still doesn't work.
Code: [Select]
21:32:50
exec associate orbis XXXXX true

21:32:53
{
  "Command": "associate",
  "wcg_member_id": 1065540,
  "wcg_points": 55771096,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"
}
After six block still nothing and here is result of exec rac:
Code: [Select]
  "Command": "rac",
  "Error": "Not Linked.  First, you must link your researcher CPID in the chain using 'exec associate'.",
I checked that associate  command many times, it looks good, but I'm now not sure because it still doesn't work :)
I read your posts again and I found, that in this post you wrote this:
The normal newbie would do this:
exec cpk nickname
wait 5 blocks
exec associate orbis wcg_userid wcg_code
wait 5 blocks
type :
exec rac
So, I tried it didn't help too (my nickname on WCG and CPK is the same "orbis"):
Code: [Select]
exec associate orbis orbis XXXX true
Unable to find orbis.  Please type exec rac to see helpful hints to proceed.  (code -1)
I really don't know what I'm doing bad :(
I'm using downloaded WIN wallet 1469.
BTW after each associate it still get 5k tBBP from me: https://prnt.sc/purfwj
I've tried do make "exec cpk orbis" again, but it didn't worked, because nickname is already taken.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 09, 2019, 03:46:26 PM
exec cpk togotesting
// worked, waited 4 confirmations then

exec associate Byteball_3b162762 X
// did not work

"Sorry, we found you as a researcher in WCG, but we were unable to locate you on the team. Please join team Biblepay or team Gridcoin to proceed."

on World Community Grid website, I see the "My Team" tab has BiblePay and I see my username in the list of Team BiblePay members
https://www.worldcommunitygrid.org/team/viewTeamMemberDetail.do?sort=name&teamId=JRD1XTFK92

Linux 64 bit QT v1.4.6.9

==

Also thank you oncoapop for the 10 million tBBP!
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 09, 2019, 04:17:28 PM
21:49:35

exec associate capulo NNNNNN true


21:49:37

{
  "Command": "associate",
  "wcg_member_id": 1066130,
  "wcg_points": 484299227,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"
}



23:16:19

exec rac


23:16:19

{
  "Command": "rac",
  "Error": "Not Linked.  First, you must link your researcher CPID in the chain using 'exec associate'.",
  "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": "From our RPC console, type, exec associate wcg your_username your_verification_code",
  "Step 4": "Wait for 5 blocks to pass.  Then type 'exec rac' again, and see if you are linked!  ",
  "Step 5": "Once you are linked you will receive daily rewards.  Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC"
}


any ideas?

i did associate with force true because normal wont work
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 09, 2019, 07:41:00 PM
So, it looks that I'm totally noob, because it still doesn't work.
Code: [Select]
21:32:50
exec associate orbis XXXXX true

21:32:53
{
  "Command": "associate",
  "wcg_member_id": 1065540,
  "wcg_points": 55771096,
  "cpid": "",
  "rac": 0,
  "researcher_nickname": "",
  "Purse Status": "Successful",
  "External Purse Address": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"
}
After six block still nothing and here is result of exec rac:
Code: [Select]
  "Command": "rac",
  "Error": "Not Linked.  First, you must link your researcher CPID in the chain using 'exec associate'.",
I checked that associate  command many times, it looks good, but I'm now not sure because it still doesn't work :)
I read your posts again and I found, that in this post you wrote this:So, I tried it didn't help too (my nickname on WCG and CPK is the same "orbis"):
Code: [Select]
exec associate orbis orbis XXXX true
Unable to find orbis.  Please type exec rac to see helpful hints to proceed.  (code -1)
I really don't know what I'm doing bad :(
I'm using downloaded WIN wallet 1469.
BTW after each associate it still get 5k tBBP from me: https://prnt.sc/purfwj
I've tried do make "exec cpk orbis" again, but it didn't worked, because nickname is already taken.

After looking at the code, I am very, very curious about fixing 2 things:  The 5001 (as I still dont see that) and the blank CPID being inserted in the chain only for Orbis:  Orbis can you please PM me your wcg code?  (It can always be changed later).

I need to reproduce!  Thanks.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 09, 2019, 08:49:01 PM
Ok, good news, I see the problem for Capulos, Togos, and most of Orbis'.

Good news is we don't need a sanctuary upgrade, but we do need a leisure!

Hang on...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 09, 2019, 09:10:41 PM
BiblePay
1.4.6.8g-Leisure Upgrade

- Fix issue preventing the proper exec associate save-in-chain for WCG
- Add underpinnings for DWS

** This is the windows version.  You can also optionally pull the latest and upgrade.  The linux binary will probably be tomorrow due to the time difference **

** You only need to upgrade if you are trying to associate the cpid, or use the controller wallet, sancs should not need to upgrade **

EDIT:  To know that you upgraded, type 'exec associate 0' and you will see "v1.2".

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 09, 2019, 11:01:04 PM
BiblePay
1.4.6.8g-Leisure Upgrade

- Fix issue preventing the proper exec associate save-in-chain for WCG
- Add underpinnings for DWS

** This is the windows version.  You can also optionally pull the latest and upgrade.  The linux binary will probably be tomorrow due to the time difference **

** You only need to upgrade if you are trying to associate the cpid, or use the controller wallet, sancs should not need to upgrade **

EDIT:  To know that you upgraded, type 'exec associate 0' and you will see "v1.2".

Association and correct assignment of cpid and rac appears to work! Thank you!

Linux command line cli -version
BiblePay Core RPC client version 1.4.6.9 (binaries)

                                                  (verification code from wcg profile)
>exec associate oncoapop xxxxxx780628399078d78f6f01xxxxxx true
Code: [Select]
{
  "Command": "associate",
  "wcg_member_id": xxxxxx,
  "wcg_points": xxxxxx,
  "cpid": "xxxxxc62b82fb40fa3db0d34605xxxxxx",
  "rac": 3932.33274,
  "researcher_nickname": "oncoapop",
  "Purse Status": "Successful",
  "External Purse Address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"

Checking 5 blocks later...

>exec rac

Code: [Select]
{
  "Command": "rac",
  "cpid": "xxxx62b82fb40fa3db0d34605xxxxxx",
  "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "oncoapop",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 4232866.94,
  "total_wcg_points": 29630068.58,
  "external_purse_total_coin_age": 2671285.637986111,
  "coin_age_percent_required": 0.02763295128696017,
  "coin_age_required": 47102.64952816543,
  "wcg_id": xxxxxxx,
  "rac": 3932.33274
}
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 10, 2019, 03:50:37 AM
So, after latest update I'm finally in :)
Thank you for catching it.
Code: [Select]
10:41:19 exec rac
10:41:19
{
  "Command": "rac",
  "cpid": "04fba56d89a5eb38b1b82f8a6240132c",
  "CPK": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "orbis",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 7973175.77,
  "total_wcg_points": 55812230.39,
  "external_purse_total_coin_age": 50251.48444444445,
  "coin_age_percent_required": 0.99,
  "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count.  (See current depth in coin control).",
  "coin_age_required": 81196.20475721419,
  "wcg_id": 1065540,
  "rac": 5978.138139
}

10:42:02 sendgscc wcg
10:42:03
{
  "Results": true
}
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 10, 2019, 04:04:24 AM
i'm in but i still see rac 0 hmm


10:58:00

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69197172.38,
  "total_wcg_points": 484380206.66,
  "external_purse_total_coin_age": 53716.43518518518,
  "coin_age_percent_required": 0,
  "coin_age_required": 0,
  "wcg_id": 1066130,
  "rac": 0
}
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 11:48:24 AM
Association and correct assignment of cpid and rac appears to work! Thank you!

Linux command line cli -version
BiblePay Core RPC client version 1.4.6.9 (binaries)

                                                  (verification code from wcg profile)
>exec associate oncoapop xxxxxx780628399078d78f6f01xxxxxx true
Code: [Select]
{
  "Command": "associate",
  "wcg_member_id": xxxxxx,
  "wcg_points": xxxxxx,
  "cpid": "xxxxxc62b82fb40fa3db0d34605xxxxxx",
  "rac": 3932.33274,
  "researcher_nickname": "oncoapop",
  "Purse Status": "Successful",
  "External Purse Address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
  "Remember": "Now you must fund your external address with enough capital to make daily PODC/GSC stakes.",
  "Results": true,
  "Welcome Aboard!": "You have successfully joined the BiblePay Proof Of Distributed Comuting (PODC) grid, and now you can help cure cancer, AIDS, and make the world a better place!  God Bless You!"

Checking 5 blocks later...

>exec rac

Code: [Select]
{
  "Command": "rac",
  "cpid": "xxxx62b82fb40fa3db0d34605xxxxxx",
  "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "oncoapop",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 4232866.94,
  "total_wcg_points": 29630068.58,
  "external_purse_total_coin_age": 2671285.637986111,
  "coin_age_percent_required": 0.02763295128696017,
  "coin_age_required": 47102.64952816543,
  "wcg_id": xxxxxxx,
  "rac": 3932.33274
}

Awesome.  I dont see you in the leaderboard yet though, although you can wait 24 hours, you can manually kick it off with 'sendgscc wcg'.

I see you have a lot of coin-age from above, so it should happen automatically.

Btw, notice the next podc_transmission block above is 15375.
Can you please check if the transmission went out at 15375?  Thats in 19 blocks it looks like.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 11:52:45 AM
So, after latest update I'm finally in :)
Thank you for catching it.
Code: [Select]
10:41:19 exec rac
10:41:19
{
  "Command": "rac",
  "cpid": "04fba56d89a5eb38b1b82f8a6240132c",
  "CPK": "ygjQUutb2MnpVJKyjQ3mTne4rg71FFPcwg",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "orbis",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 7973175.77,
  "total_wcg_points": 55812230.39,
  "external_purse_total_coin_age": 50251.48444444445,
  "coin_age_percent_required": 0.99,
  "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count.  (See current depth in coin control).",
  "coin_age_required": 81196.20475721419,
  "wcg_id": 1065540,
  "rac": 5978.138139
}

10:42:02 sendgscc wcg
10:42:03
{
  "Results": true
}

Thats good news, so far we have 2 more on board in testnet, but - when it sent the associate transmission was it 0 this time plus the tx fee?

I still dont see anywhere in the code that we will use up 5000, unless :  You use the dev spork command in Testnet only, which obviously Im sure you didnt do because that would not have sent an associate.

Ill check your rac out next.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 10, 2019, 12:34:57 PM
I updated to latest version with precompiled Linux 64 bit

exec associate 0
// returned: Unable to find 0.

exec associate Byteball_3b162762 XXXX
// I was able to associate successfully!

wcg_member_id:  1073152
wcg_points:  21186268
cpid:   93138f032bdd027fa3246b48bb715a77
rac:  294.861381

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 12:38:29 PM
I updated to latest version with precompiled Linux 64 bit

exec associate 0
// returned: Unable to find 0.

exec associate Byteball_3b162762 XXXX
// I was able to associate successfully!

wcg_member_id:  1073152
wcg_points:  21186268
cpid:   93138f032bdd027fa3246b48bb715a77
rac:  294.861381

Maybe try exec associate without zero?  I might have done it that way.

Excellent on the rac!

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 12:41:55 PM
i'm in but i still see rac 0 hmm


10:58:00

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69197172.38,
  "total_wcg_points": 484380206.66,
  "external_purse_total_coin_age": 53716.43518518518,
  "coin_age_percent_required": 0,
  "coin_age_required": 0,
  "wcg_id": 1066130,
  "rac": 0
}

Sweet that you got further.  I think in your case, the associate just had to mature.
I just added a new feature to the next version, where we can type 'exec rac' with an optional researcher nickname or cpid.
Looking at your rac now:


12:40:29

exec rac capulo


12:40:29

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yLbyhFoEurwToxcTrthXoX6Ln7ieMY3sM5",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 15375,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69208838.14,
  "total_wcg_points": 484461866.98,
  "external_purse_total_coin_age": 233767.0832175926,
  "coin_age_percent_required": 0.1226086780602041,
  "coin_age_required": 174598.0078998322,
  "wcg_id": 1066130,
  "rac": 10773.031035
}


I see rac now.  Can you please confirm your exec rac started populating?

Also lets see if your client sent out the 'sendgscc wcg' at the height of 15375 automatically?

(That is if your node is on right now).

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 10, 2019, 12:47:17 PM
exec associate
// returned: Associate v1.2

worked! Thanks!

===

Boinc has been a bit unstable for me (I think my computer is kind of dying a little lol), but it will freeze my machine up when running it for awhile (monitor will come on but Ill get no signal), Im going to test using the VirtualBox download
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 01:14:04 PM
exec associate
// returned: Associate v1.2

worked! Thanks!

===

Boinc has been a bit unstable for me (I think my computer is kind of dying a little lol), but it will freeze my machine up when running it for awhile (monitor will come on but Ill get no signal), Im going to test using the VirtualBox download

Maybe your fan is going, I had one where it would freeze when the cpu hit 100% to protect from thermal overload.
Id check the cpu fan to see if its sticking or maybe the case fans.
Also you can install a cpu monitor, i think cpu-z might show the temps.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 01:48:27 PM
BiblePay
1.4.6.8g-Leisure Upgrade

- Fix issue preventing the proper exec associate save-in-chain for WCG
- Add underpinnings for DWS

** This is the windows version.  You can also optionally pull the latest and upgrade.  The linux binary will probably be tomorrow due to the time difference **

** You only need to upgrade if you are trying to associate the cpid, or use the controller wallet, sancs should not need to upgrade **

EDIT:  To know that you upgraded, type 'exec associate 0' and you will see "v1.2".


Will the sancs please upgrade also?  It turns out we need this to process the wcg researchers in the GSC.

Sorry for the inconvenience!


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 10, 2019, 02:24:29 PM
cool , after 15375 i can see rac
 "rac": 11105.219523
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 10, 2019, 02:33:28 PM
I setup a masternode

I used these old testnet notes:
https://forum.biblepay.org/index.php?topic=108.msg1444#msg1444

I noticed I didnt have to run: masternode start-alias
and it seemed like its not a command anymore?

then I updated to deterministic
https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/

I see myself in the Sanctuaries tab!

===

Also I see a GSC Transmission just sent a block ago, Label: WCG for 10564.60703610 BBP

exec rac also works
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 07:31:07 PM
I setup a masternode

I used these old testnet notes:
https://forum.biblepay.org/index.php?topic=108.msg1444#msg1444

I noticed I didnt have to run: masternode start-alias
and it seemed like its not a command anymore?

then I updated to deterministic
https://www.reddit.com/r/BiblePay/comments/clyxyc/upgrading_masternodes_sanctuaries_to/

I see myself in the Sanctuaries tab!

===

Also I see a GSC Transmission just sent a block ago, Label: WCG for 10564.60703610 BBP

exec rac also works

Nice!  I see it now.

This is good, we are starting to get the Leaderboard filled.

Btw, for anyone who didnt notice, the WCG GSC "Points" column is equal to the Researchers RAC.

We automatically lower the RAC when the stake is not met.

I see Capulo for example is the only one on the board with a lower Points than his RAC, so he probably didnt stake enough.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 10, 2019, 07:32:54 PM
One more update on Biblepay Vs. Gridcoin.

To be unbanked you have to have less than 250 RAC and be part of BiblePay.

If RAC > 250, you must have the appropriate stake.

To be on Gridcoin, you must have the stake met AND have > 250 RAC, as we don't support unbanked non-bbp researchers.  (They aren't imported into our client, which keeps the network lean & fast).

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 10, 2019, 09:58:06 PM
Awesome.  I dont see you in the leaderboard yet though, although you can wait 24 hours, you can manually kick it off with 'sendgscc wcg'.

I see you have a lot of coin-age from above, so it should happen automatically.

Btw, notice the next podc_transmission block above is 15375.
Can you please check if the transmission went out at 15375?  Thats in 19 blocks it looks like.

I have 20 x GSC transmissions at 15375 (62 confirmations ago) similar to the one below.
Code: [Select]
--
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -22.50906346,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "fee": -0.00880000,
    "confirmations": 61,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "0ba03f7f4f7b84cf6a297a5da4e87b019afee2a648f67ed6016b67221ff18af9",
    "blockindex": 9,
    "blocktime": 1573417659,
    "txid": "128503ab7c59d4af7992a72ffa245196a7b967ccaf3393b9f2ba1343c1a2f648",
    "walletconflicts": [
    ],
    "time": 1573417187,
    "timereceived": 1573417187,
    "abandoned": false
  },

However, I was not appearing on the leader board as somehow the association with wcg was flaky and exec rac (later the following day) said I was not associated but from my earlier post, if was clear that I was.

However `sendgscc wcg` followed by `exec rac` as per your suggestion allowed me to now be in the leaderboard.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 10, 2019, 10:15:01 PM

20:12:23 exec associate wcg sunk818 verification_code
20:12:24 Unable to find wcg.  Please type exec rac to see helpful hints to proceed.  (code -1)

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 11, 2019, 06:44:51 AM
I have 20 x GSC transmissions at 15375 (62 confirmations ago) similar to the one below.
Code: [Select]
--
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -22.50906346,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "fee": -0.00880000,
    "confirmations": 61,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "0ba03f7f4f7b84cf6a297a5da4e87b019afee2a648f67ed6016b67221ff18af9",
    "blockindex": 9,
    "blocktime": 1573417659,
    "txid": "128503ab7c59d4af7992a72ffa245196a7b967ccaf3393b9f2ba1343c1a2f648",
    "walletconflicts": [
    ],
    "time": 1573417187,
    "timereceived": 1573417187,
    "abandoned": false
  },

However, I was not appearing on the leader board as somehow the association with wcg was flaky and exec rac (later the following day) said I was not associated but from my earlier post, if was clear that I was.

However `sendgscc wcg` followed by `exec rac` as per your suggestion allowed me to now be in the leaderboard.

Yeah, I was around that day and the problem was that I told people they didnt need to upgrade the sancs and they did; once they upgraded, the leaderboard started populating.

It was an issue where the contract was not being voted on; but everything looks fine now, so you should not see any flakiness in exec health.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 11, 2019, 06:46:29 AM
20:12:23 exec associate wcg sunk818 verification_code
20:12:24 Unable to find wcg.  Please type exec rac to see helpful hints to proceed.  (code -1)

Please see the help docs for the exec associate:  Please remove the word 'wcg' before sunk818.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 11, 2019, 09:20:06 AM
Code: [Select]
I have 20 x GSC transmissions at 15375 (62 confirmations ago) similar to the one below.

Wait, other than the original flakiness (which I believe is permanently fixed), did you say you had 20* 'sendgscc' transmissions at the height?
(Or do you mean, you had 20 in total).  I just want to make sure our wallet did not send your 'sendgscc wcg' transmission 20 times at the height automatically, it didnt do that right?

Looking at my last night submission, I see 1 for WCG and 1 for Cameroon at the height and looking at the code, we should only be trying once during the block passing?


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 11, 2019, 11:04:01 AM
Please see the help docs for the exec associate:  Please remove the word 'wcg' before sunk818.


when I typed exec rac in debug console, it says to use wcg . I'll look for wiki docs, I guess?





09:01:41

exec rac




09:01:41

{
  "Command": "rac",
  "Error": "Sorry, you do not have a CPK.  First please create your CPK by typing 'exec cpk your_nickname'.  This adds your CPK to the chain.  Please wait 3 or more blocks after adding your CPK before you move on to the next step. ",
  "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": "From our RPC console, type, exec associate wcg your_username your_verification_code",
  "Step 4": "Wait for 5 blocks to pass.  Then type 'exec rac' again, and see if you are linked!  ",
  "Step 5": "Once you are linked you will receive daily rewards.  Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC"
}

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 11, 2019, 12:06:54 PM
Wait, other than the original flakiness (which I believe is permanently fixed), did you say you had 20* 'sendgscc' transmissions at the height?
(Or do you mean, you had 20 in total).  I just want to make sure our wallet did not send your 'sendgscc wcg' transmission 20 times at the height automatically, it didnt do that right?

Looking at my last night submission, I see 1 for WCG and 1 for Cameroon at the height and looking at the code, we should only be trying once during the block passing?

Current block 15553 and 50 confirmations ago at 155503, I see 10 entries with the following condition ("GSC-Stake-Transmission": true,)

>listtransactions "" 100 | grep "GSC-Stake-Transmission" -A10 -B12 | grep 50, -A13 -B11

I see 10 almost identical (as far as I can tell) transactions....
I thought it looks like it is sending 10 coins of 8570 BBP as stake...  but I cannot see the corresponding consolidated amount returning. However, I do not what the expected behaviour is supposed to be in the external purse nor do I know the coin composition of the external purse....

Code: [Select]
{
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -8570.75104474,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 3,
    "fee": -0.05017000,
    "confirmations": 50,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "91eb12db434addf9cb0618ffc998b5e539c7c5a169d1b918310eafe194eb7ab7",
    "blockindex": 1,
    "blocktime": 1573474173,
    "txid": "baa77a343dd9f4bfa1348a3ebea6e1c6c54afb8722cf069a8ccdaba572f6ff6f",
    "walletconflicts": [
    ],
    "time": 1573473791,
    "timereceived": 1573473791,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -8570.75104474,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "fee": -0.05017000,
    "confirmations": 50,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "91eb12db434addf9cb0618ffc998b5e539c7c5a169d1b918310eafe194eb7ab7",
    "blockindex": 1,
    "blocktime": 1573474173,
    "txid": "baa77a343dd9f4bfa1348a3ebea6e1c6c54afb8722cf069a8ccdaba572f6ff6f",
    "walletconflicts": [
    ],
    "time": 1573473791,
    "timereceived": 1573473791,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -8570.75104474,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "fee": -0.05017000,
    "confirmations": 50,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "91eb12db434addf9cb0618ffc998b5e539c7c5a169d1b918310eafe194eb7ab7",
    "blockindex": 1,
    "blocktime": 1573474173,
    "txid": "baa77a343dd9f4bfa1348a3ebea6e1c6c54afb8722cf069a8ccdaba572f6ff6f",
    "walletconflicts": [
    ],
    "time": 1573473791,
    "timereceived": 1573473791,
    "abandoned": false
  },
(only pasted 3 consecutive transactions)







Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 11, 2019, 01:43:48 PM
Please see the help docs for the exec associate:  Please remove the word 'wcg' before sunk818.


I submitted a pull request to reflect the actual command you have to type when I run exec rac now


thanks.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 11, 2019, 01:45:25 PM

when I typed exec rac in debug console, it says to use wcg . I'll look for wiki docs, I guess?





09:01:41

exec rac




09:01:41

{
  "Command": "rac",
  "Error": "Sorry, you do not have a CPK.  First please create your CPK by typing 'exec cpk your_nickname'.  This adds your CPK to the chain.  Please wait 3 or more blocks after adding your CPK before you move on to the next step. ",
  "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": "From our RPC console, type, exec associate wcg your_username your_verification_code",
  "Step 4": "Wait for 5 blocks to pass.  Then type 'exec rac' again, and see if you are linked!  ",
  "Step 5": "Once you are linked you will receive daily rewards.  Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC"
}

Oh, sorry about that, I see we only fixed it in one place!

Fixed for the next version.

Please type:  exec associate your_username your_verification_code

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 11, 2019, 01:51:18 PM
Current block 15553 and 50 confirmations ago at 155503, I see 10 entries with the following condition ("GSC-Stake-Transmission": true,)

>listtransactions "" 100 | grep "GSC-Stake-Transmission" -A10 -B12 | grep 50, -A13 -B11

I see 10 almost identical (as far as I can tell) transactions....
I thought it looks like it is sending 10 coins of 8570 BBP as stake...  but I cannot see the corresponding consolidated amount returning. However, I do not what the expected behaviour is supposed to be in the external purse nor do I know the coin composition of the external purse....

Code: [Select]
{
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -8570.75104474,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 3,
    "fee": -0.05017000,
    "confirmations": 50,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "91eb12db434addf9cb0618ffc998b5e539c7c5a169d1b918310eafe194eb7ab7",
    "blockindex": 1,
    "blocktime": 1573474173,
    "txid": "baa77a343dd9f4bfa1348a3ebea6e1c6c54afb8722cf069a8ccdaba572f6ff6f",
    "walletconflicts": [
    ],
    "time": 1573473791,
    "timereceived": 1573473791,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -8570.75104474,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 2,
    "fee": -0.05017000,
    "confirmations": 50,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "91eb12db434addf9cb0618ffc998b5e539c7c5a169d1b918310eafe194eb7ab7",
    "blockindex": 1,
    "blocktime": 1573474173,
    "txid": "baa77a343dd9f4bfa1348a3ebea6e1c6c54afb8722cf069a8ccdaba572f6ff6f",
    "walletconflicts": [
    ],
    "time": 1573473791,
    "timereceived": 1573473791,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
    "category": "send",
    "amount": -8570.75104474,
    "label": "CHRISTIAN-PUBLIC-KEY",
    "vout": 1,
    "fee": -0.05017000,
    "confirmations": 50,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "GSC-Stake-Transmission": true,
    "blockhash": "91eb12db434addf9cb0618ffc998b5e539c7c5a169d1b918310eafe194eb7ab7",
    "blockindex": 1,
    "blocktime": 1573474173,
    "txid": "baa77a343dd9f4bfa1348a3ebea6e1c6c54afb8722cf069a8ccdaba572f6ff6f",
    "walletconflicts": [
    ],
    "time": 1573473791,
    "timereceived": 1573473791,
    "abandoned": false
  },
(only pasted 3 consecutive transactions)

Those are all the same transaction, which is normal.  (See the txid, with multiple vouts).
When the wallet makes a GSC transmission, it uses up as much coin age as necessary to compose the transaction.

If you type 'exec rac' you can see the percent of coin*age required to fill with many inputs.

Is it possible to test in QT until we are stable in testnet?  As QT is a lot easier to see the single transmission.

If you want you can simulate this by getting the coin*age required from exec rac, then type 'exec createabn N 1' where N is the amount of coin*age, and you can see the individual inputs required for that amount of age.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 11, 2019, 02:25:45 PM
will gen=1 still be required in the biblepay.conf to submit these wcg, pog, healing, occasionally? with the external miner, I wonder if gen=0 will be okay now...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 12, 2019, 12:03:14 AM
i got some smart contract reward overnight ;)

what means coin age percent required? because i dont have enough coin age but it says 0.99 (i think 99%), but i need about 200%
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 12, 2019, 01:39:29 AM
Those are all the same transaction, which is normal.  (See the txid, with multiple vouts).
When the wallet makes a GSC transmission, it uses up as much coin age as necessary to compose the transaction.

If you type 'exec rac' you can see the percent of coin*age required to fill with many inputs.

Is it possible to test in QT until we are stable in testnet?  As QT is a lot easier to see the single transmission.

If you want you can simulate this by getting the coin*age required from exec rac, then type 'exec createabn N 1' where N is the amount of coin*age, and you can see the individual inputs required for that amount of age.

Following your advice, I am using the QT version but it is painfully slow on my weak VPS (that's why I use command line text only). However, it is much easier to see what I think is the transaction (debit and credit is 108,344 tBBP and I can see all the individual coins that add up to this in one transaction). And I also get to see Gen 25:13-19.  is there any way to read the Bible from the command line (ie biblepayd)?

the createabn coinage gives a long list of coins as expected.

What is the frequency of the automatic `sendgscc wcg` command? I know the purse does not need to be unlocked but does the wallet need to be mining for the `sendgscc wcg` transaction to occur or does the purse stake when the wallet is on but not mining? What about when the wallet is offline?
 

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 12, 2019, 03:25:34 AM
Following your advice, I am using the QT version but it is painfully slow on my weak VPS (that's why I use command line text only). However, it is much easier to see what I think is the transaction (debit and credit is 108,344 tBBP and I can see all the individual coins that add up to this in one transaction). And I also get to see Gen 25:13-19.  is there any way to read the Bible from the command line (ie biblepayd)?

the createabn coinage gives a long list of coins as expected.

What is the frequency of the automatic `sendgscc wcg` command? I know the purse does not need to be unlocked but does the wallet need to be mining for the `sendgscc wcg` transaction to occur or does the purse stake when the wallet is on but not mining? What about when the wallet is offline?

I also noticed that every time the wallet is stopped and then restarted, `exec rac` initially shows that the external purse is empty and I would have to reassociate again before the external purse coins are recognized in `exec rac`. Is this intended behaviour?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 08:38:42 AM
will gen=1 still be required in the biblepay.conf to submit these wcg, pog, healing, occasionally? with the external miner, I wonder if gen=0 will be okay now...

No, this is one improvement in PODC 2.0. 
Now we moved the sendgscc process over to the main thread.
So now the miner can be off.
We also changed the architecture to use a single target block per day (this is primarily to make it more efficient on coin-age usage.  Another words, if a person only has just enough, we arent trying to stake every 12 hours, etc).
To see that block # type exec rac, and look for the wcg gsc transmission height.
(Actually an easy way to remember that height is we made it at the mid-point of each gsc contract, so its 102 blocks after the last gsc payment height).

At that height, once per day, we send all the gsc transmissions - one at a time.

I've tested cameroon-one a little but we could use your help testing it more thoroughly in testnet.  Please see the 2nd post after the op post.  I have a test cameroon environment up and I can enter debits and credits for cameroon in testnet if you give me the childid and payment amount.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 08:47:08 AM
Following your advice, I am using the QT version but it is painfully slow on my weak VPS (that's why I use command line text only). However, it is much easier to see what I think is the transaction (debit and credit is 108,344 tBBP and I can see all the individual coins that add up to this in one transaction). And I also get to see Gen 25:13-19.  is there any way to read the Bible from the command line (ie biblepayd)?

the createabn coinage gives a long list of coins as expected.

What is the frequency of the automatic `sendgscc wcg` command? I know the purse does not need to be unlocked but does the wallet need to be mining for the `sendgscc wcg` transaction to occur or does the purse stake when the wallet is on but not mining? What about when the wallet is offline?


1) On reading the bible from the command line, please see the rpc commands: 'books' (This list the books of the bible), 'bookname' this is just a cross reference command to get the long bookname from the BiblePay abbreviated bookname, and the main command: exec readverse.

2) Please see my last post to Sun, its once per day at the midpoint of the GSC contract now, and wallet can be locked - Yay.

3) Yes thats depressing on the speed.  Ive been using my old $1 per month hostbrz.com nodes for testnet (the ones Sun suggested a year ago) and QT is running very fast in there.  The only other option I can recommend, is running QT side by side one of your prod nodes.  Because, testnet actually does not interfere with prod (it has its own subdirectory and ports).  If you get any errors I can help you get by them.  Yeah, or you can go back to the command line once you feel comfortable, but, I still recommend we test cameroon one and some other things (DWS) in QT if possible, as it might reveal some behavior thats hard to debug on a small window.  (IE leaderboard outputs etc).

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 08:52:50 AM
I also noticed that every time the wallet is stopped and then restarted, `exec rac` initially shows that the external purse is empty and I would have to reassociate again before the external purse coins are recognized in `exec rac`. Is this intended behaviour?

No thats not intended at all, and you should only have to associate once forever, haha.
Interesting, well I cant reproduce that, I just did exec rac, and rebooted and exec rac - and Ive only associated once over the last 10 boots, thats not supposed to happen.

Are you sure you did not move the machine and delete the SAN directory?  Or the wallet.dat?  Because the SAN contains the association record, and once deleted, it will only regenerate during the next start (when prayers are re-synced) - but - without a reassociation it does regenerate. 
Also if you move wallet.dat, your external purse is not lost, but it is no longer linked.  It would take a new associate or an 'exec createpurse' to re-link it.  And that would also cause a temporary break in the CPK (wallet would recreate a new CPK, a different one, requiring a new associate).



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 08:59:42 AM
** DWS update (Dynamic Whale Staking) **

So I've been programming DWS in testnet and it is ready for a release.  (I realize we havent released the thread to discuss it and or vote on it yet, so know that as we test this, there is no intention at all to release this to prod - it will just stay in testnet indefinitely until we add a proposal to vote it in.  I will move the existing discussion thread to a proposal over the next few days anyway and we can vote on it.)

However note that DWS is going to require a mandatory in testnet!  So please be aware that we will have a mandatory upgrade for this.

Another thing going on is Kairos Childrens Fund is making very fast progress with POOM on their end, and I just heard from Andy this morning that he will be calling me to train him with integration reqs.  This means I need to merge code into testnet for Kairos also.  So be aware we have a lot going into testnet.  We will be pulling individual pieces out when we move to prod (IE the Kairos piece and the PODC 2.0 piece) for the next MainNet release.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 12, 2019, 01:39:10 PM
Wau, I received my first wcg reward :)
So, it looks that I've made it all good :)
I have few questions :)
1. Rob, what happens if my wallet will be closed during "next_podc_gsc_transmission"? Is it enough to send "sendgscc wcg" once per day?
2. When the wallet is open, it's needed to have it unlocked?
3. Will setautounlockpassword and -headlesspassword works if it's needed?
4. When I send "sendgscc wcg" manually e.g. 10 blocks before "next_podc_gsc_transmission" and I forget to close wallet will the gsc tx run again?
5. What happens if my coinage in that second tx will be lower then expected, but in first tx it was enough?
6. It's possible to associate more wcg accounts into one wallet?
Thanks
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 12, 2019, 01:41:38 PM
I can help with CameroonONE and Kairos integration. Not sure how I can help. More details is appreciated. I think I got WCG registered and working now. I'll check later and report if I'm still having issues.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 01:52:53 PM
I can help with CameroonONE and Kairos integration. Not sure how I can help. More details is appreciated. I think I got WCG registered and working now. I'll check later and report if I'm still having issues.

Yes, I will start giving many more details once the next release is checked in (in about an hour or so).
For now, you can definitely join cameroon with 'exec join cameroon-one', but please wait on kairos as the sporks are not finished.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 02:06:42 PM
Wau, I received my first wcg reward :)
So, it looks that I've made it all good :)
I have few questions :)

Thanks

Thats great Orbis!

Great questions btw.


1. Rob, what happens if my wallet will be closed during "next_podc_gsc_transmission"? Is it enough to send "sendgscc wcg" once per day?

-> So do remember, if you are unbanked (with RAC <= 250), the wallet does not need to run.  But for the banked, if you leave it off, and miss the PODC transmission, this would be a problem as you would fall out of the leaderboard for that day, and not get paid.  However, yes, you can just do the 'sendgscc wcg' once per day, and that will also keep you in (if you miss one). 

2. When the wallet is open, it's needed to have it unlocked?

->  Finally, in PODC 2.0, it does not need to be unlocked.  The funds for the GSC only come from the "Christian-Public-Key" now, which is now the external purse.  As a matter of fact, if you have 10 mil in your main wallet, and only 1000 bbp in your external purse, the GSC will fail - if you dont have enough coin age.  So we will need to ask people to fund their CPK address with enough coin-age.


3. Will setautounlockpassword and -headlesspassword works if it's needed?

->  I removed all of the places where we look at locking unlocking the wallet with the secure key.  So not anymore.  I suppose I need to remove those two commands also for sanitization/(and sanity).

4. When I send "sendgscc wcg" manually e.g. 10 blocks before "next_podc_gsc_transmission" and I forget to close wallet will the gsc tx run again?

->  Since the next_podc_gsc_transmission is at the midpoint of the contract, you can be off by up to 101 blocks in either direction, and your gsc would be "in" the leaderboard.  However if you open the wallet 1 block after the wcg height, and dont do the sendgscc, you would miss it because the wallet would not send it until the next wcg height.  We do have a key that lets you make those wallet sends more frequent; but then your coin-age would get used up faster etc - but - wcg does count cumulative coin-age, so that is a good option for some people who dont like to leave it running all the time.

5. What happens if my coinage in that second tx will be lower then expected, but in first tx it was enough?

->  This is OK.  We count the sum of the staked coin*age in the 205 block window, so, you would have enough over 2 transmissions.

6. It's possible to associate more wcg accounts into one wallet?

->  This is an interesting one.  So far, in 2.0, the rules are:  Each CPID is only counted once, and assigned to the most recent CPK->CPID association.  The exec rac command only displays data for One CPID (the first one it finds linked to your CPK).  However, there is no rule blocking you from associating your CPK with more than one CPID; however - its not been tested and Im not entirely sure if both CPIDs will be paid in the leaderboard.  This would be a good thing to test; if someone wants to raise up two cpids; then link two distinct CPIDs to one CPK, then wait and see what happens on our leaderboard.  If it works properly, I can potentially add code to allow iterating through them in 'exec rac'.  However note that exec rac does allow you type a cpid now (in the next version) and manually pull up the second rac, it just does not allow iteration automatically yet. <-- Either way this will be a good exercise to ensure there is no unintended behavior on the payment side so lets please test it.





Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 02:27:32 PM
And you know, on #6 in the prior post, I'm thinking its to our benefit not to support multiple CPIDs per CPK.
95% of our users are going to have one CPID and one CPK, and supporting more than one is giving them an easy way to attempt to circumvent our collateralization requirements, and adding complexity (it would mean I would not only need to iterate through CPIDs in every place, but also, where we send GSCs out for WCG, to gather the collateral requirements for each CPID) and that would be a nightmare - adding a huge amount of complexity for users who want it 'to just work' when they send their stake.

So I think I would like to take the stance:  Multiple CPIDs are not officially supported.    This keeps users from splitting CPIDs.

Im not concerned with the leaderboard, because I believe for the most part the 2nd-N CPID associated with one CPK will fail to be funded most of the time, as the collateral will not stake properly for it.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 12, 2019, 04:05:13 PM
Thanks for answers.
That question about more WCG accounts was just a curiosity.
I don't have more accounts, so I wouldn't be able even to test it. Thanks for clarification.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 04:06:49 PM
Thanks for answers.
That question about more WCG accounts was just a curiosity.
I don't have more accounts, so I wouldn't be able even to test it. Thanks for clarification.

Yeah, PODC 1.0 was able to do it, but for the above reasons we should probably become more 'iphone' like :).

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 04:07:12 PM
BiblePay
1.4.7.1-Mandatory Upgrade for TestNet

- Add Dynamic Whale Staking, added 'exec dws' and 'exec dwsquote'
- Add Kairos POOM Integration
- Modify Cameroon-One to be a generic part of POOM, and modify POOM to be more generic, modified paycameroon to become exec paysponsorship
- Added 'exec rac cpid_or_nickname'

* Windows ready, MIP is building the rest *
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 12, 2019, 07:06:04 PM
I can help with CameroonONE and Kairos integration. Not sure how I can help. More details is appreciated. I think I got WCG registered and working now. I'll check later and report if I'm still having issues.

To help with cameroon-one and Kairos, please sponsor a few random children with:
sponsorchild cameroon-one authorize
sponsorchild kairos authorize

Then paste me the childid's and Ill send a credit in through the testnet integration, and we can verify our payment amounts.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 13, 2019, 12:20:51 AM
To help with cameroon-one and Kairos, please sponsor a few random children with:
sponsorchild cameroon-one authorize
sponsorchild kairos authorize

Then paste me the childid's and Ill send a credit in through the testnet integration, and we can verify our payment amounts.


3d28e3d5 - cameroon-one
[/size]8fd8963b - kairos
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 13, 2019, 01:08:01 AM
"Notes 1": "Your new child ID is: 6d9e2b38",
"Notes 1": "Your new child ID is: ad7ec463",



08:06:50

exec dws 100000 2 1


08:06:51

{
  "Command": "dws",
  "Staking Amount": 100000,
  "Duration": 2,
  "Reclaim Date": "11-15-2019 07:06:50",
  "Return Address": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "ROI %": "98.1995",
  "Results": "Burn was successful.  You will receive your original BBP back on the Reclaim Date, plus the stake reward.  Please give the wallet an extra 24 hours after the reclaim date to process the return stake.  ",
  "TXID": "5ae00dfbffac0026649d00dcb777cb663e317b2876027847bb2c4afcc598aa32"
}
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 13, 2019, 07:45:06 AM
To help with cameroon-one and Kairos, please sponsor a few random children with:
sponsorchild cameroon-one authorize
sponsorchild kairos authorize

Then paste me the childid's and Ill send a credit in through the testnet integration, and we can verify our payment amounts.

Sorry I had to use command line as I could not copy and paste from the text from the X-window and could not get the paysponsorship to work in qt (works in command line though)

>exec paysponsorship cameroon-one 04b236ea 40 authorize
Code: [Select]

{
  "Command": "paysponsorship",
  "BBP/USD_Price": 0.0003067780730175,
  "txid": "232dd125f00f6e5246968d01fde98f1c35896f6a519e58a7be241bc5bbdbf433",
  "childid": "04b236ea",
  "BBPAmount": 130387.42,
  "USDAmount": 40
}

The authorization and payments seem to be correctly taken out of the wallet in testnet

Code: [Select]
{
    "account": "",
    "address": "yTrEKf8XQ7y7tychC2gWuGw1hsLqBybnEN",
    "category": "send",
    "amount": -50000.00000000,
    "vout": 1,
    "fee": -0.06125000,
    "confirmations": 0,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "Christian-Public-Key-Association": true,
    "trusted": true,
    "txid": "348a92b1c0c79ecb8f5b9f8ee9a34d054b9e4b00bd617d0937bb5d7e2969397f",
    "walletconflicts": [
    ],
    "time": 1573651212,
    "timereceived": 1573651212,
    "abandoned": false
  },
  {
    "account": "",
    "address": "yQE49VaaaF599dJgQzmFkHqjHp4xbQ2oAu",
    "category": "send",
    "amount": -130387.42000000,
    "vout": 1,
    "fee": -0.06422000,
    "confirmations": 0,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "trusted": false,
    "txid": "232dd125f00f6e5246968d01fde98f1c35896f6a519e58a7be241bc5bbdbf433",
    "walletconflicts": [
    ],
    "time": 1573651276,
    "timereceived": 1573651276,
    "abandoned": false
  }

I did this same for the two children (cameroon one) but do not yet see it updated

> cli listchildren
Code: [Select]
{
  "List Of": "POOM Children",
  "Charity": "cameroon-one",
  "Child ID": "04b236ea",
  "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
  "Biography": "https://biblepay.cameroonone.org/bios/04b236ea.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "---------": "--------------------------------------------------",
  "Charity": "cameroon-one",
  "Child ID": "f89f5a15",
  "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
  "Biography": "https://biblepay.cameroonone.org/bios/f89f5a15.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "---------": "--------------------------------------------------"
}

Ops - something screwed up here. confirmations= -3

Code: [Select]
  {
   {
    "account": "",
    "address": "yQE49VaaaF599dJgQzmFkHqjHp4xbQ2oAu",
    "category": "send",
    "amount": -130387.42000000,
    "vout": 1,
    "fee": -0.06422000,
    "confirmations": -3,
    "instantlock": false,
    "instantlock_internal": false,
    "chainlock": false,
    "trusted": false,
    "txid": "232dd125f00f6e5246968d01fde98f1c35896f6a519e58a7be241bc5bbdbf433",
    "walletconflicts": [
      "91bafd0f1fbea8e20f049a881604af161ec7980b338db6ca3f451c8ada2f228a",
      "ca0c14fe20735d0e73a469ce71e23d2ad89a8ad347a421eb61f3f2c24e07aca7",
      "04cd725198564fdd947095f17ffe09d751f55935ea189c695501176d121385e7"
    ],
    "time": 1573651276,
    "timereceived": 1573651276,
    "abandoned": false
  },

Anyway, please apply the following amounts to the children:
cameroon one
04b236ea  = $20 (underpayment)
f89f5a15    = $40 (correct payment)
kairos
d6ac6919   = $25 (correct payment)
8e697449   = $10 (underpayment)
5cf71b44    = $50 (overpayment)

Thank you.




Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 13, 2019, 09:09:28 AM
please send me funds yUKkAGGyGxBzR2SQBvzqpB7FNDkwZcteES
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 13, 2019, 10:45:35 AM
please send me funds yUKkAGGyGxBzR2SQBvzqpB7FNDkwZcteES

sent.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 13, 2019, 02:33:57 PM

3d28e3d5 - cameroon-one
[/size]8fd8963b - kairos

I credited these in TestNet with payments for each; please see if the balances are now negative.
Then please do the 'sendgscc kairos' and sendgscc cameroon-one, and lets see if we get paid.

NOTE: Since Kairos is a $25 child compared to CAMEROON-ONE which is a $40 child please verify the renumeration amount is correct.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 13, 2019, 02:38:01 PM
"Notes 1": "Your new child ID is: 6d9e2b38",
"Notes 1": "Your new child ID is: ad7ec463",



08:06:50

exec dws 100000 2 1


08:06:51

{
Code: [Select]
  "Command": "dws",
  "Staking Amount": 100000,
  "Duration": 2,
  "Reclaim Date": "11-15-2019 07:06:50",
  "Return Address": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "ROI %": "98.1995",
  "Results": "Burn was successful.  You will receive your original BBP back on the Reclaim Date, plus the stake reward.  Please give the wallet an extra 24 hours after the reclaim date to process the return stake.  ",
  "TXID": "5ae00dfbffac0026649d00dcb777cb663e317b2876027847bb2c4afcc598aa32"
}

Sweet.

I credited these two children, so please do the listchildren now and confirm you have credit balances, then you can also do the 'sendgscc kairos' and 'sendgscc cameroon-one' and see if we get paid?

10-4 on the burn, lets see if we get our whale steak back.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 13, 2019, 02:43:52 PM
Sorry I had to use command line as I could not copy and paste from the text from the X-window and could not get the paysponsorship to work in qt (works in command line though)

>exec paysponsorship cameroon-one 04b236ea 40 authorize
Code: [Select]



The authorization and payments seem to be correctly taken out of the wallet in testnet

Code: [Select]
{
    "account": "",
   
  }

I did this same for the two children (cameroon one) but do not yet see it updated

> cli listchildren
Code: [Select]
{
  "List Of": "POOM Children",
 
  "---------": "--------------------------------------------------"
}

Ops - something screwed up here. confirmations= -3

Code: [Select]
  {
   {
    "account": "",
    "address": "yQE49VaaaF599dJgQzmFkHqjHp4xbQ2oAu",
    "category": "send",
    "amount": -130387.42000000,
    "vout": 1,
    "fee": -0.06422000,
    "confirmations": -3,
    "instantlock": false,
   
    "walletconflicts": [
      "91bafd0f1fbea8e20f049a881604af161ec7980b338db6ca3f451c8ada2f228a",
      "ca0c14fe20735d0e73a469ce71e23d2ad89a8ad347a421eb61f3f2c24e07aca7",
      "04cd725198564fdd947095f17ffe09d751f55935ea189c695501176d121385e7"
    ],
    "time": 1573651276,
    "timereceived": 1573651276,
    "abandoned": false
  },

Anyway, please apply the following amounts to the children:
cameroon one
04b236ea  = $20 (underpayment)
f89f5a15    = $40 (correct payment)
kairos
d6ac6919   = $25 (correct payment)
8e697449   = $10 (underpayment)
5cf71b44    = $50 (overpayment)

Thank you.


10-4 on moving to CLI, thats cool.

So, on the POOM payments, I did apply the amounts you paid above.

10-4 on the -3 confirms on the third child; I make the assumption that the sponsoredchild record just wasnt 5 deep yet when viewing it; its probably OK by now, I assume.  Once the sponsorship record is > 3 or so, all the other wallets see it and should be able to do the 'listchildren' command etc.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 13, 2019, 04:15:44 PM
Sweet.

I credited these two children, so please do the listchildren now and confirm you have credit balances, then you can also do the 'sendgscc kairos' and 'sendgscc cameroon-one' and see if we get paid?

10-4 on the burn, lets see if we get our whale steak back.


23:13:54

{
  "List Of": "POOM Children",
  "Charity": "cameroon-one",
  "Child ID": "6d9e2b38",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://biblepay.cameroonone.org/bios/6d9e2b38.htm",
  "Balance": -44,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------",
  "Charity": "kairos",
  "Child ID": "ad7ec463",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://kairoschildrensfund.com/bios/ad7ec463.htm",
  "Balance": -60,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------"
}

23:15:01

sendgscc kairos


23:15:01

{
  "Error!": "Sorry, CPK is not enrolled in project. [User is not enrolled in CPK-KAIROS.].  Error 795. "
}


23:15:19

sendgscc cameroon-one


23:15:19

{
  "Error!": "Sorry, CPK is not enrolled in project. [User is not enrolled in CPK-CAMEROON-ONE.].  Error 795. "
}
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 13, 2019, 04:17:08 PM

10-4 on moving to CLI, thats cool.

So, on the POOM payments, I did apply the amounts you paid above.

10-4 on the -3 confirms on the third child; I make the assumption that the sponsoredchild record just wasnt 5 deep yet when viewing it; its probably OK by now, I assume.  Once the sponsorship record is > 3 or so, all the other wallets see it and should be able to do the 'listchildren' command etc.

good note

04b236ea $20 (underpayment) - shows 20 balance (but I paid $40 using `exec paysponsorship cameroon-one 04b236ea 40 authorize`)
f89f5a15   $40 (correct payment)  - shows 0 balance

d6ac6919 $25 (correct payment) - shows 0 balance
5cf71b44  $50 (overpayment) - shows -25 balance
8e697449 $20 (underpayment) - shows 15 balance

Code: [Select]
{
 "List Of": "POOM Children",
 "Charity": "cameroon-one",
 "Child ID": "04b236ea",
 "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
 "Biography": "https://biblepay.cameroonone.org/bios/04b236ea.htm",
 "Balance": 20,
 "Notes": "Child sponsorship is due.",
 "---------": "--------------------------------------------------",
 "Charity": "cameroon-one",
 "Child ID": "f89f5a15",
 "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
 "Biography": "https://biblepay.cameroonone.org/bios/f89f5a15.htm",
 "Balance": 0,
 "Notes": "Good job, nothing due!",
 "---------": "--------------------------------------------------",
 "Charity": "kairos",
 "Child ID": "d6ac6919",
 "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
 "Biography": "https://kairoschildrensfund.com/bios/d6ac6919.htm",
 "Balance": 0,
 "Notes": "Good job, nothing due!",
 "---------": "--------------------------------------------------",
 "Charity": "kairos",
 "Child ID": "5cf71b44",
 "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
 "Biography": "https://kairoschildrensfund.com/bios/5cf71b44.htm",
 "Balance": -25,
 "Notes": "Good job, nothing due!",
 "---------": "--------------------------------------------------",
 "Charity": "kairos",
 "Child ID": "8e697449",
 "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
 "Biography": "https://kairoschildrensfund.com/bios/8e697449.htm",
 "Balance": 15,
 "Notes": "Child sponsorship is due.",
 "---------": "--------------------------------------------------"
}

sendgscc cameroon-one
Code: [Select]
{
 "Results": true
}

sendgscc kairos
Code: [Select]
{
 "Results": true
}

1x cameroon-one recognized as balance <=0 , $1 =29.18 pts
2x kairos recognized as balance <=0, $1= 33.3 pts

 "Prominence v1.1": "Details",
 "CAMEROON-ONE: yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv [oncoapop], Pts: 1167.00": "0.32%",
 "KAIROS: yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv [oncoapop], Pts: 1667.00": "0.46%”,


as noted above, the payment I sent using BBP to cameroon-one (exec paysponsorship) is still stuck. It only registered the amount you applied.

Code: [Select]
{
   "account": "",
   "address": "yQE49VaaaF599dJgQzmFkHqjHp4xbQ2oAu",
   "category": "send",
   "amount": -130387.42000000,
   "vout": 1,
   "fee": -0.06422000,
   "confirmations": -66,
   "instantlock": false,
   "instantlock_internal": false,
   "chainlock": false,
   "trusted": false,
   "txid": "232dd125f00f6e5246968d01fde98f1c35896f6a519e58a7be241bc5bbdbf433",
   "walletconflicts": [
     "ad9f341ef0d38f4a5c7fccaea9ea14798727a9bfef4015fac9b33d350f8e673c",
     "91bafd0f1fbea8e20f049a881604af161ec7980b338db6ca3f451c8ada2f228a",
     "319557fb3a01afdc336c322519428cf935e87dffb1b03d47ae45c671b0b4fa96",
     "ca0c14fe20735d0e73a469ce71e23d2ad89a8ad347a421eb61f3f2c24e07aca7",
     "04cd725198564fdd947095f17ffe09d751f55935ea189c695501176d121385e7",
     "9605a0be9a4080b1b3a4a9ced399d60a9585dbe27490f16dbab189bf5c3d42f4"
   ],
   "time": 1573651276,
   "timereceived": 1573651276,
   "abandoned": false
 },
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 13, 2019, 04:17:34 PM

23:13:54

{
  "List Of": "POOM Children",
  "Charity": "cameroon-one",
  "Child ID": "6d9e2b38",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://biblepay.cameroonone.org/bios/6d9e2b38.htm",
  "Balance": -44,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------",
  "Charity": "kairos",
  "Child ID": "ad7ec463",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://kairoschildrensfund.com/bios/ad7ec463.htm",
  "Balance": -60,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------"
}

23:15:01

sendgscc kairos


23:15:01

{
  "Error!": "Sorry, CPK is not enrolled in project. [User is not enrolled in CPK-KAIROS.].  Error 795. "
}


23:15:19

sendgscc cameroon-one


23:15:19

{
  "Error!": "Sorry, CPK is not enrolled in project. [User is not enrolled in CPK-CAMEROON-ONE.].  Error 795. "
}

Great on part #1, now just enroll in both projects with:

exec join kairos
exec join cameroon-one


Then wait a few blocks, then you can send the gsc's.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 13, 2019, 04:21:09 PM

23:13:54

{
  "List Of": "POOM Children",
  "Charity": "cameroon-one",
  "Child ID": "6d9e2b38",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://biblepay.cameroonone.org/bios/6d9e2b38.htm",
  "Balance": -44,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------",
  "Charity": "kairos",
  "Child ID": "ad7ec463",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://kairoschildrensfund.com/bios/ad7ec463.htm",
  "Balance": -60,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------"
}

23:15:01

sendgscc kairos


23:15:01

{
  "Error!": "Sorry, CPK is not enrolled in project. [User is not enrolled in CPK-KAIROS.].  Error 795. "
}


23:15:19

sendgscc cameroon-one


23:15:19

{
  "Error!": "Sorry, CPK is not enrolled in project. [User is not enrolled in CPK-CAMEROON-ONE.].  Error 795. "
}

Did you do a ‘exec join cameroon-one’ ?
And a ‘exec join kairos’? I noticed that it allows us to contribute to the gscc project with having officially joined it and hence you won’t receive rewards for it.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 13, 2019, 04:25:00 PM
good note

04b236ea $20 (underpayment) - shows 20 balance (but I paid $40 using `exec paysponsorship cameroon-one 04b236ea 40 authorize`)
f89f5a15   $40 (correct payment)  - shows 0 balance

d6ac6919 $25 (correct payment) - shows 0 balance
5cf71b44  $50 (overpayment) - shows -25 balance
8e697449 $20 (underpayment) - shows 15 balance

Code: [Select]
{
 
 "Charity": "kairos",
 "Child ID": "8e697449",
 "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
 "Biography": "https://kairoschildrensfund.com/bios/8e697449.htm",
 "Balance": 15,
 "Notes": "Child sponsorship is due.",
 "---------": "--------------------------------------------------"
}

sendgscc cameroon-one
Code: [Select]
{
 "Results": true
}

sendgscc kairos
Code: [Select]
{
 "Results": true
}

Code: [Select]
{
   "ac
     "ca0c14fe20735d0e73a469ce71e23d2ad89a8ad347a421eb61f3f2c24e07aca7",
     "04cd725198564fdd947095f17ffe09d751f55935ea189c695501176d121385e7",
     "9605a0be9a4080b1b3a4a9ced399d60a9585dbe27490f16dbab189bf5c3d42f4"
   ],
   "time": 1573651276,
   "timereceived": 1573651276,
   "abandoned": false
 },


1) In Prod, we do recommend the paysponsorship, so there is a complete record of the payment.  And its up to kairos or cameroon to actually apply the balance.
But in the fake environment in testnet, I rely on what you guys tell me to apply; so the applied payments don't count the paysponsorship payments.
Although Im glad you tried to send them, because that helps test the actual usage of the spork (for the receive address).  As a matter of fact if I can get Kairos to create an account here, we will need to have him review that to post payments; so when we get to that phase Ill check with him and see if he can run the report on his end that shows what users have paid through that command.
So please just verify the payments were applied that you asked me to manually apply .

2) As far as the stuck outgoing transaction, that can happen if your wallet tried to double spend, not sure why it would, and that is very very rare.  The best advice I have for that is to restart the wallet with -zapwallettxes=1, verify the tx outbound is no longer stuck.  Then re-send it.  BBP is always either on your end or on the receiver end, but not lost.  In a nutshell, this failed outbound tx didn't cause any problems for our gsc's or our WCG testing though.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 13, 2019, 04:26:33 PM
Did you do a ‘exec join cameroon-one’ ?
And a ‘exec join kairos’? I noticed that it allows us to contribute to the gscc project with having officially joined it and hence you won’t receive rewards for it.

Sorry.... it should say “allows us to contribute without officially joining”...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 13, 2019, 04:27:04 PM
Did you do a ‘exec join cameroon-one’ ?
And a ‘exec join kairos’? I noticed that it allows us to contribute to the gscc project with having officially joined it and hence you won’t receive rewards for it.

Yeah, I confirm we dont check to see if a user is enrolled when we allow them to sponsor a child :), lol, but they will quickly find out when they are not getting paid.  Ill make a note to do something about that.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 13, 2019, 04:41:27 PM
Sorry.... it should say “allows us to contribute without officially joining”...

One of your payment comments made me thing of a pretty interesting idea for 'decentralizing orphans'.  If we had an array of orphan keys, and remember at the very beginning, we used to give every10th block reward to charity, (the miner mined it but didnt get a reward), it would be intersting if we considered rotating through a list of orphan keys, and rewarding the orphan address with the mining reward - and then giving the key to one of our charities.  Then we would have an algorithm that rotates, and requires the charity to keep a bio under the same name as the key.  (This would prove to us the sponsorship actually exists - and a page with stats to show the orphan is current by public key).    We would make it so we could automatically revoke or replenish a key by Sanctuary vote, so that the sancs still had control over the decision making process.  Then also the core wallet could expand and contract its key exposure as necessary to limit each orphan to $40 per month in BBP etc.    Just another concept to put under our belt for the future.   The idea that wins is probably the one that is trusted the most by the cryptocommunity at large, and scales well.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 13, 2019, 06:31:19 PM
on mac i got on command line saying..


  ****TINYFORMAT ERROR****
    err="tinyformat: Not enough conversion specifiers in format string"
    fmt="
VerifyDynamicWhaleStake::REJECTED, Burn time out of bounds."


****TINYFORMAT ERROR****
    err="tinyformat: Not enough conversion specifiers in format string"
    fmt="
VerifyDynamicWhaleStake::REJECTED, Burn time out of bounds."


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 14, 2019, 01:07:45 PM

 
Says the burn was successful, but gets rejected. The messaging is not clear. Ideally, no mempool creation should be created IMO.


Code: [Select]
   11:04:52    exec dws 1000000 1 1

    11:04:52    {
  "Command": "dws",
  "Staking Amount": 1000000,
  "Duration": 1,
  "Reclaim Date": "11-15-2019 19:04:52",
  "Return Address": "yTXhgST2JwaPM8XRwMng4fBZzgubx76cRB",
  "ROI %": "90.6013",
  "Results": "Burn was successful.  You will receive your original BBP back on the Reclaim Date, plus the stake reward.  Please give the wallet an extra 24 hours after the reclaim date to process the return stake.  ",
  "TXID": "ab5c992590f07e67d85d9495b91a943bd785aefa973cf17630cc76f818dbf3a8"
}




VerifyDynamicWhaleStake::REJECTED, Sorry, our daily whale commitments of 118557.355695 are higher than the acceptable maximum of 5000000.000000, please wait until tomorrow.AcceptToMemoryPool::Dynamic Whale Burn rejected 5b5ff5efda6d9b4cf110e2bb977f297347924429339ab8e34f9cd0cf2d2d6507
2019-11-14 19:05:50 CommitTransaction(): Transaction cannot be broadcast immediately,
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 14, 2019, 02:11:54 PM
what should i see? i did exec join and sendgscc then... and after 1 day:

21:09:04

listchildren


21:09:06

{
  "List Of": "POOM Children",
  "Charity": "cameroon-one",
  "Child ID": "6d9e2b38",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://biblepay.cameroonone.org/bios/6d9e2b38.htm",
  "Balance": -44,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------",
  "Charity": "kairos",
  "Child ID": "ad7ec463",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://kairoschildrensfund.com/bios/ad7ec463.htm",
  "Balance": -60,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------"
}

btw is there some command to list all my whale stakes?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 14, 2019, 03:33:11 PM
on mac i got on command line saying..


  ****TINYFORMAT ERROR****
    err="tinyformat: Not enough conversion specifiers in format string"
    fmt="
VerifyDynamicWhaleStake::REJECTED, Burn time out of bounds."


****TINYFORMAT ERROR****
    err="tinyformat: Not enough conversion specifiers in format string"
    fmt="
VerifyDynamicWhaleStake::REJECTED, Burn time out of bounds."

Ok, I found this on my node also, and fixed the problem for the next release; it turns out its not too important for now so it can wait for the next release.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 14, 2019, 03:35:57 PM

Says the burn was successful, but gets rejected. The messaging is not clear. Ideally, no mempool creation should be created IMO.


Code: [Select]
   11:04:52    exec dws 1000000 1 1

    11:04:52    {
  "Command": "dws",
  "Staking Amount": 1000000,
  "Duration": 1,
  "Reclaim Date": "11-15-2019 19:04:52",
  "Return Address": "yTXhgST2JwaPM8XRwMng4fBZzgubx76cRB",
  "ROI %": "90.6013",
  "Results": "Burn was successful.  You will receive your original BBP back on the Reclaim Date, plus the stake reward.  Please give the wallet an extra 24 hours after the reclaim date to process the return stake.  ",
  "TXID": "ab5c992590f07e67d85d9495b91a943bd785aefa973cf17630cc76f818dbf3a8"
}




VerifyDynamicWhaleStake::REJECTED, Sorry, our daily whale commitments of 118557.355695 are higher than the acceptable maximum of 5000000.000000, please wait until tomorrow.AcceptToMemoryPool::Dynamic Whale Burn rejected 5b5ff5efda6d9b4cf110e2bb977f297347924429339ab8e34f9cd0cf2d2d6507
2019-11-14 19:05:50 CommitTransaction(): Transaction cannot be broadcast immediately,

Right, we should be pre-testing this and rejecting it on the screen.  Ill fix this next.

Although I see 2 problems:  I believe we allow 5mil a day, so it should not have rejected 118K.  Ill look into that also.

Also, Ill add the Anti-Howey changes (DWS Units instead of ROI), and, a warning that as you burn the coins you are not promised a return at all.  Etc.  Something to make it clear that BBP is not promising an increase in value, but the opposite, we are warning you of a loss if you use this feature, etc.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 14, 2019, 03:39:18 PM
what should i see? i did exec join and sendgscc then... and after 1 day:

21:09:04

listchildren


21:09:06

{
  "List Of": "POOM Children",
  "Charity": "cameroon-one",
  "Child ID": "6d9e2b38",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://biblepay.cameroonone.org/bios/6d9e2b38.htm",
  "Balance": -44,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------",
  "Charity": "kairos",
  "Child ID": "ad7ec463",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://kairoschildrensfund.com/bios/ad7ec463.htm",
  "Balance": -60,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------"
}

btw is there some command to list all my whale stakes?


Great, this is good that you can see your balance(s).  But, after you do the 'exec sendgscc kairos', you should see yourself in the leaderboard.  To see that click Leaderboard | Details.  You will see a breakout next to kairos and a separate one next to cameroon-one.  (Or the leaderboard command).


On the whale stakes, that is a good idea.  All we have so far is 'exec dwsquote 1' which shows *all* the stakes.  Let me add a couple more things to the list I posted on Suns replay:

- Ability to see the Whale icon when you *receive* a stake - this was programmed but is broken
- Ability to list your own whale stakes
- Fix the 5mil limit error
- Reject the whale stake in the RPC, and show the error message now
- Add the anti-howey language
- Allow 48 hours for whale stake maturity (in contrast to 24 hours)

** NOTE:  I received my first two whale stake payments.  Note everyone:  the way the system works, its paying 48 hours later (not 24 hours later).  Keep that in mind.  Im going to update the RPC text **  Another thing:  The whale is missing in this version, on the payments.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 14, 2019, 04:45:31 PM
i can see myself in leaderboard for kairos and cameron but not for wcg hmm
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 14, 2019, 04:57:04 PM
i can see myself in leaderboard for kairos and cameron but not for wcg hmm

Just check your wallet and see if you sent the 'exec sendgscc wcg' out at the last height, or manually.
Ive been watching mine and mine went out automatically I believe it was 04:20AM.


You can type 'exec sendgscc wcg' right now and then wait a few blocks and then see yourself also.

Let me know if you dont and if you sent it and the txid, and Ill research if something went wrong.

Could be that you didnt have enough coin-age for your huge rac?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 14, 2019, 07:22:56 PM
i happens automaticaly about 14h ago together with kairos and cameron

yes i dont have coin age now, in this case no reward? i think it will be some lower % as in podc1

it did only 59bbp in tx, so is it works this way? if i dont have enough coinage, then only do update with small bbp amount and no reward? until i will have coin age?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 14, 2019, 07:49:21 PM
** DYNAMIC WHALE STAKING UPDATE **

Due to a change in the structure of each burn, we have to start the burns over.  (IE the old ones are now going to be unrecognized).
So please after you upgrade, please re-burn new DWSs.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 14, 2019, 07:54:20 PM
i happens automaticaly about 14h ago together with kairos and cameron

yes i dont have coin age now, in this case no reward? i think it will be some lower % as in podc1

it did only 59bbp in tx, so is it works this way? if i dont have enough coinage, then only do update with small bbp amount and no reward? until i will have coin age?

Well lets clarify this to make it easier to understand.
Lets say your CPID is 10,000 RAC, and we require 1 mil of coin-age. 
And in your external purse, you have exactly 500,000 of coin-age at the wcg-gsc-transmission-height available.
We would automatically use all of your coin-age, and, we would set you up with about 5,000 RAC.
So yes, you would get your tx in, and you would get about half the reward.

But, a person with only 59 bbp would fall below the minimum (I think of 1 RAC), and get nothing because the math would not reverse engineer all the way down to 1RAC.

So the main goal is to keep the external purse filled with coin-age for the midday block.
Now one more tip I remember, we did add code to ensure Kairos and Cameroon-One do not use much coin age and do not tithe.  So when you drill into those, you should see the absolute minimum spent in coin age from the purse.

The key to that requires doing the exec bankroll first to have some extra small bills around (in the external purse).

BTW:

You can type 'exec rac' to see the condition you are in.  The % of coin-age available comes out of that command now.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 14, 2019, 08:04:22 PM
BiblePay TestNet
1.4.7.2-Mandatory Upgrade for TestNet

- Add Howey verbiage to exec dws.  Rename all instances of ROI to DWU (Dynamic Whale Units).  Ensure burn errors are bubbled to the user immediately.  Ensure burns that exceed the daily limit are checked correctly and reported correctly.  Make the whale icon appear on DWS rewards.
- Ensure the CPID RAC is updated on all sancs every 14 blocks (if it changes) - this ensures a consistent GSC contract for WCG.
- Ensure the user is enrolled in Kairos or Cameroon-One before allowing sponsorship
- Fix tinyformat error
- Encrypt the WCG verification code

** This is the Windows release.  Its 3 AM in Spain so lets wait til tomorrow for the compiles.  You can still self-compile tonight.  **

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 15, 2019, 01:11:40 AM
Well lets clarify this to make it easier to understand.
Lets say your CPID is 10,000 RAC, and we require 1 mil of coin-age. 
And in your external purse, you have exactly 500,000 of coin-age at the wcg-gsc-transmission-height available.
We would automatically use all of your coin-age, and, we would set you up with about 5,000 RAC.
So yes, you would get your tx in, and you would get about half the reward.

But, a person with only 59 bbp would fall below the minimum (I think of 1 RAC), and get nothing because the math would not reverse engineer all the way down to 1RAC.

So the main goal is to keep the external purse filled with coin-age for the midday block.
Now one more tip I remember, we did add code to ensure Kairos and Cameroon-One do not use much coin age and do not tithe.  So when you drill into those, you should see the absolute minimum spent in coin age from the purse.

The key to that requires doing the exec bankroll first to have some extra small bills around (in the external purse).

BTW:

You can type 'exec rac' to see the condition you are in.  The % of coin-age available comes out of that command now.

i had 286k bbp in external purse

now
07:53:53

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16297,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69294160.40000001,
  "total_wcg_points": 485059122.8000001,
  "external_purse_total_coin_age": 363319.7254050925,
  "coin_age_percent_required": 0.7400380137787291,
  "coin_age_required": 265237.210701367,
  "wcg_id": 1066130,
  "rac": 14860.263202
}

so yesterday there must been about 100k coin age at wcg-gsc transmission time
but only 59bbp was taken

b88b8b5480f1ff6311c2fed1bc26052739b5aa19848f981501af0d5a00046580
Status: 167 confirmations, broadcast through 5 nodes
Date: 14. 11. 2019 11:21
Source: GSC-Transmission
Total debit: -59.27710240 tBBP
Total credit: 59.27710240 tBBP
Transaction fee: -0.03533000 tBBP
Net amount: -0.03533000 tBBP
Transaction ID: b88b8b5480f1ff6311c2fed1bc26052739b5aa19848f981501af0d5a00046580
Output index: 0
Transaction total size: 3526 bytes

Height: 16094
Difficulty: 34.61
Time: 11-14-2019 10:24:56
Subsidy: 3839.5479

Debit: -1457.48153815 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 1457.03486575 tBBP
To: ycPcPQ9bh45xUvMeBSHprdhvbKjTVxqTQX 1457.0000 BBP

btw why total credit debit is only 59 when there is credit/debit of 1457bbp also?

i'll see today in 3 hrs what happens...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 15, 2019, 06:49:25 AM
soo, coin age was not spent


13:42:52

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16297,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69335182.63,
  "total_wcg_points": 485346278.41,
  "external_purse_total_coin_age": 441222.8717592593,
  "coin_age_percent_required": 0.7435678336035351,
  "coin_age_required": 323666.9061727702,
  "wcg_id": 1066130,
  "rac": 17319.571826
}

but i'm now in leader table with wcg
Transaction ID: e3b4dcc778bb7676fac56af17b2ff47c3053e2f8892093e199263ef8c9f99a9c
seems like bbp (and coin age) was taken from normal wallet addres and sent to CPK address
is this ok?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 15, 2019, 09:40:16 AM
who owns the external purse? do we have access to it?


if we don't send a gscc daily, do we stop earning rewards? what do you think about a 7 day average? this way, even if we miss a day, we'll still earn rewards? I thought you mentioned something about 7 days, but I forgot what that was about...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 09:52:08 AM
who owns the external purse? do we have access to it?


if we don't send a gscc daily, do we stop earning rewards? what do you think about a 7 day average? this way, even if we miss a day, we'll still earn rewards? I thought you mentioned something about 7 days, but I forgot what that was about...
You own the external purse; its your Christian-public-key (private key) pair - so you can still access it via coin-control and send things into and out of it.

If you don't send a gscc for that day for cameroon-one or kairos, you would not get the reward.  As explained for WCG in one of the prior posts, if you are unbanked, you dont need to send the daily wcg.  But if you have > 250 rac, you do need to send the wcg.

I dont think I ever mentioned a 7 day average, cant recall anything about that.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 10:05:19 AM
soo, coin age was not spent


13:42:52

{
Code: [Select]
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16297,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69335182.63,
  "total_wcg_points": 485346278.41,
  "external_purse_total_coin_age": 441222.8717592593,
  "coin_age_percent_required": 0.7435678336035351,
  "coin_age_required": 323666.9061727702,
  "wcg_id": 1066130,
  "rac": 17319.571826
}

but i'm now in leader table with wcg

Transaction ID: e3b4dcc778bb7676fac56af17b2ff47c3053e2f8892093e199263ef8c9f99a9c

seems like bbp (and coin age) was taken from normal wallet addres and sent to CPK address
is this ok?

"seems like bbp (and coin age) was taken from normal wallet addres and sent to CPK address
is this ok?"
getrawtransaction e3b4dcc778bb7676fac56af17b2ff47c3053e2f8892093e199263ef8c9f99a9c 1

->  Why do you say it wasnt taken from your CPK external purse?  Looking at the vin of the transaction (i pasted above), its from your yi* address.  So it appears it was taken from your external purse.

->  Yes, coin age was spent.  You can type 'exec sentgscc' to see each time the coin-age was spent.

->  The only problem I see here, is why didn't we send your GSCC out yesterday if you had 330K coin age *at that time*?  That looks like a legitimate problem; I will be checking this next.




Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 10:09:45 AM
who owns the external purse? do we have access to it?


if we don't send a gscc daily, do we stop earning rewards? what do you think about a 7 day average? this way, even if we miss a day, we'll still earn rewards? I thought you mentioned something about 7 days, but I forgot what that was about...

On the 7 day idea, I think its too risky for daily mining rewards.  With the daily budget we require the coin-age to be staked within the last 205 blocks of the contract.  Moving to 7 days, then we have to make sancs assess different ranges than the daily contract reward range.  Doesn't sound possible without redesigning our entire GSC system.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 10:18:43 AM
i had 286k bbp in external purse

now
07:53:53
Code: [Select]
{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16297,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69294160.40000001,
  "total_wcg_points": 485059122.8000001,
  "external_purse_total_coin_age": 363319.7254050925,
  "coin_age_percent_required": 0.7400380137787291,
  "coin_age_required": 265237.210701367,
  "wcg_id": 1066130,
  "rac": 14860.263202
}
so yesterday there must been about 100k coin age at wcg-gsc transmission time
but only 59bbp was taken

b88b8b5480f1ff6311c2fed1bc26052739b5aa19848f981501af0d5a00046580
Status: 167 confirmations, broadcast through 5 nodes
Date: 14. 11. 2019 11:21
Source: GSC-Transmission
Total debit: -59.27710240 tBBP
Total credit: 59.27710240 tBBP
Transaction fee: -0.03533000 tBBP
Net amount: -0.03533000 tBBP
Code: [Select]
Transaction ID: b88b8b5480f1ff6311c2fed1bc26052739b5aa19848f981501af0d5a00046580
Output index: 0
Transaction total size: 3526 bytes

Height: 16094
Difficulty: 34.61
Time: 11-14-2019 10:24:56
Subsidy: 3839.5479

Debit: -1457.48153815 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 1457.03486575 tBBP
To: ycPcPQ9bh45xUvMeBSHprdhvbKjTVxqTQX 1457.0000 BBP
btw why total credit debit is only 59 when there is credit/debit of 1457bbp also?

i'll see today in 3 hrs what happens...

1) Could you please put long pastes inside code tags - thanks.
2) The reason you see a 1457 bbp debit, is because we broke the 1457 bbp bill from your external purse, and made the debits.  The credit back is your change.
(This happens in all tx's).

3)  I agree that it looks like you had coin-age on that day, but the wallet only saw 1457 bbp available to spend.  It thought you had "8 total" in coin-age at that exact time, from looking at the transaction I can see, that for WCG, we thought you had 8 total coin age available.


So, I believe the only problem we have is finding out why you had 8 in its view (instead of 335,000).

I have a hypothesis, how many minutes earlier was your transmission before WCG?

I have a feeling we don't detect the correct coin-age for 5 confirms *after* any gsc transmission.
I say this because I sent one manually, and then my 'exec rac' was wrong for 5 blocks.

So, I think you found a nice bug we can fix!

Anyone want to confirm that is the case for one manually?  Just sent a cameroon one then look at exec rac.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 01:39:32 PM
1) Could you please put long pastes inside code tags - thanks.
2) The reason you see a 1457 bbp debit, is because we broke the 1457 bbp bill from your external purse, and made the debits.  The credit back is your change.
(This happens in all tx's).

3)  I agree that it looks like you had coin-age on that day, but the wallet only saw 1457 bbp available to spend.  It thought you had "8 total" in coin-age at that exact time, from looking at the transaction I can see, that for WCG, we thought you had 8 total coin age available.


So, I believe the only problem we have is finding out why you had 8 in its view (instead of 335,000).

I have a hypothesis, how many minutes earlier was your transmission before WCG?

I have a feeling we don't detect the correct coin-age for 5 confirms *after* any gsc transmission.
I say this because I sent one manually, and then my 'exec rac' was wrong for 5 blocks.

So, I think you found a nice bug we can fix!

Anyone want to confirm that is the case for one manually?  Just sent a cameroon one then look at exec rac.

Ok, dont bother confirming that, I was able to reproduce it, although its not severely easy to reproduce as it does not happen in most circumstances.

The main issue is, we were allowing coins to be spent with any confirm level in Phase II, but only gathering coins (fully mature > 5) in Phase 1, and what we ended up doing is making this LESS depth required, but equal.  So in the future version we will only require 1 confirm per coin to be in a GSC, but we will also ensure this matches with what actually gets committed in the GSC.

This next version will not require a sanctuary update, just an end user update - it will be a leisure.

So Capulo you are correct, we skipped by your WCG that day because we did not assess the age correctly, we assesed it at 8 coinage because we skiped by most of your coins.

In the new version, I think in the most complicated scenario, we will spend one coin for Cameroon and a 2nd coin for Kairos, leaving the rest with > 1 confirm for the WCG, and, we reflect this properly now in 'exec rac' also.  So I believe we fixed the bug.

We will have a leisure release in an hour.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 02:06:23 PM
BiblePay - TestNet
1.4.7.3-Leisure Upgrade


- Ensure Coin selection, tx creation and tx commit for GSC all use coins with > 0 depth

** Windows available; MIP is building the rest **
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 15, 2019, 04:12:36 PM
i think I did exec join wcg before I did exec associate sunk818 verify_code .


now, i can't seem to get my account linked.


I must have done something wrong or out of order.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 04:18:39 PM
i think I did exec join wcg before I did exec associate sunk818 verify_code .


now, i can't seem to get my account linked.


I must have done something wrong or out of order.

That should be OK.  The primary change is now you have to be upgraded to the latest to send an associate (as the latest version is different than the one 2 versions ago); have you sent the exec associate on this latest version?


(Otherwise it will be rejected in the mempool on the *foreign* nodes).

EDIT:  please fill me in on the history of the cpid; is it new, or has it been linked , etc?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 15, 2019, 04:24:02 PM
i'm still not sure if only coins from external purse was used, because i pasted here that i had 286k coins a day ago, now i still have 286k in cpk with 358 confirms and 10x 22311 bbp with 69 confirms

and in this tx e3b4dcc778bb7676fac56af17b2ff47c3053e2f8892093e199263ef8c9f99a9c i can see that debit/credit was 223k (10x 22311)
and i can see that outside cpk there are 3 addresses with 69 confirms (3x gsc = kairos, cameron, wcg)
if you check last credit of tx above, there is 187k to yP6... address and debits like -69k and -307k (how if i had only 286k in cpk)
it really seems that it was taken from normal address

now i have 509230 in cpk
will see tomorrow :)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 15, 2019, 08:02:20 PM
I pasted the Chinese script from a bible verse into the diary entry and it appears to work with only one malformed  character.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 08:30:06 PM
I pasted the Chinese script from a bible verse into the diary entry and it appears to work with only one malformed  character.
Yes thats interesting, because we do support the storage of unicode in BiblePay, and, QT can display the characters.

My wife said the sentence was probably missing this word : 没有   (Which I believe is NO).  That makes the entry Ephesians 5:3 right?
There should be no mention of sin, impurity of any kind or greed even mentioned among us - as we become saints?  Ill have to try to reproduce; maybe when you get a chance try to expiriment by breaking it up into two sentence etc.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 15, 2019, 08:38:42 PM
i'm still not sure if only coins from external purse was used, because i pasted here that i had 286k coins a day ago, now i still have 286k in cpk with 358 confirms and 10x 22311 bbp with 69 confirms

and in this tx e3b4dcc778bb7676fac56af17b2ff47c3053e2f8892093e199263ef8c9f99a9c i can see that debit/credit was 223k (10x 22311)
and i can see that outside cpk there are 3 addresses with 69 confirms (3x gsc = kairos, cameron, wcg)
if you check last credit of tx above, there is 187k to yP6... address and debits like -69k and -307k (how if i had only 286k in cpk)
it really seems that it was taken from normal address

now i have 509230 in cpk
will see tomorrow :)

Yes, external purse was used.  (Yi*).  (Also Im very confident its working that way because all GSC's in this new code branch all come from the purse, its coded that way and cant be working any other way).  This way, cameroon, kairos and wcg can be sent out silently in the night with the wallet locked, yay.  This is another test for you guys - encrypt the wallet, lock it and let it sit over night and we should see the 3 go out.

Let me give you an example of how you can see you spent it from your purse.  You typed in a txid above.  Type 'getrawtransaction txid 1'.  From the vin's, pick a random source of funds in the transaction (you used like 20 or so).  I picked the second one.  Then type 'getrawtransaction that_vin_txid 1'.  Then look and see if it was funded *to* your cpk.  It was funded to yi* its one of your exec bankrolls.  So its fine.

Next, the reason your CPK still has funds growing is because every sendgsc sends it back *to your external wallet* so yes, it always grows bigger.

Ive verified earlier today, when I type exec rac and write down the coin-age - then you send the sendgscc wcg, and then type exec rac, and look at it again you can clearly see the coin age has been deducted.  Please try that........ then you will know, please confirm .
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 15, 2019, 10:22:32 PM
Yes thats interesting, because we do support the storage of unicode in BiblePay, and, QT can display the characters.

My wife said the sentence was probably missing this word : 没有   (Which I believe is NO).  That makes the entry Ephesians 5:3 right?
There should be no mention of sin, impurity of any kind or greed even mentioned among us - as we become saints?  Ill have to try to reproduce; maybe when you get a chance try to expiriment by breaking it up into two sentence etc.

Yes that’s the verse! Is your wife Chinese?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 16, 2019, 02:16:30 AM
That should be OK.  The primary change is now you have to be upgraded to the latest to send an associate (as the latest version is different than the one 2 versions ago); have you sent the exec associate on this latest version?


(Otherwise it will be rejected in the mempool on the *foreign* nodes).

EDIT:  please fill me in on the history of the cpid; is it new, or has it been linked , etc?


i did exec associate sunk818 vccode


{
[/size]  "Command": "associate",
[/size]  "wcg_member_id": 1067915,
[/size]  "wcg_points": 146514500,
[/size]  "cpid": "c3939b61e69c6bde1eddb06708e0f96e",
[/size]  "rac": 6422.256021,
[/size]  "researcher_nickname": "sunk818",
[/size]  "Error": "ALREADY_IN_CHAIN"
[/size]}
[/size]
[/size]
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 16, 2019, 02:22:11 AM

Eventually, where does Kairos fit into this?


PoG will disappear, but healing stays...

https://wiki.biblepay.org/Economic_Changes_Dec_2019 (https://wiki.biblepay.org/Economic_Changes_Dec_2019)


By Jan 2020, it says the following:



   GSC Suballocations:
 
   25% for POOM-Cameroon One (this is 10% of our monthly emission for charity)
   5% for Healing
   70% for PODC
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 16, 2019, 07:54:55 AM
Yes, external purse was used.  (Yi*).  (Also Im very confident its working that way because all GSC's in this new code branch all come from the purse, its coded that way and cant be working any other way).  This way, cameroon, kairos and wcg can be sent out silently in the night with the wallet locked, yay.  This is another test for you guys - encrypt the wallet, lock it and let it sit over night and we should see the 3 go out.

Let me give you an example of how you can see you spent it from your purse.  You typed in a txid above.  Type 'getrawtransaction txid 1'.  From the vin's, pick a random source of funds in the transaction (you used like 20 or so).  I picked the second one.  Then type 'getrawtransaction that_vin_txid 1'.  Then look and see if it was funded *to* your cpk.  It was funded to yi* its one of your exec bankrolls.  So its fine.

Next, the reason your CPK still has funds growing is because every sendgsc sends it back *to your external wallet* so yes, it always grows bigger.

Ive verified earlier today, when I type exec rac and write down the coin-age - then you send the sendgscc wcg, and then type exec rac, and look at it again you can clearly see the coin age has been deducted.  Please try that........ then you will know, please confirm .

not sure where you see yi* because i cant see it

but here are somescreenshots
(https://i.imgur.com/S5sFmya.png)
(https://i.imgur.com/CqkbKuf.png)

Code: [Select]
14:17:51

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16502,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69376573.58,
  "total_wcg_points": 485636015.06,
  "external_purse_total_coin_age": 963515.4535069445,
  "coin_age_percent_required": 0.4039957165891909,
  "coin_age_required": 379620.9615492278,
  "wcg_id": 1066130,
  "rac": 19579.781208
}


14:21:40

sendgscc wcg


14:21:40

{
  "Results": true
}


14:21:47

exec rac


14:21:47

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16502,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69376573.58,
  "total_wcg_points": 485636015.06,
  "external_purse_total_coin_age": 727273.1985069445,
  "coin_age_percent_required": 0.5319784839157702,
  "coin_age_required": 379620.9615492278,
  "wcg_id": 1066130,
  "rac": 19579.781208
}

txid 6ca683c024cf65a0d1c69ce9d6ca198a1ee1b3a7259cecddc8becb6426fcd71f

as you can see, some coins was taken from cpk and some from normal address. and before i had 509k in cpk, and after 491k and 18k was moved to normal address

i think that if i moved 1m to cpk, then only these coins will be used as source for coin age and will not be mixed with other coins in any direction
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 16, 2019, 07:56:36 AM
Eventually, where does Kairos fit into this?


PoG will disappear, but healing stays...

https://wiki.biblepay.org/Economic_Changes_Dec_2019 (https://wiki.biblepay.org/Economic_Changes_Dec_2019)


By Jan 2020, it says the following:



   GSC Suballocations:
 
   25% for POOM-Cameroon One (this is 10% of our monthly emission for charity)
   5% for Healing
   70% for PODC

And know that this reply from me isn't driven by me making this decision; I took a look at the code, and found it would be very difficult to keep One POOM campaign, and iterate through children.  For the sake of elegance, our code currently only supports POOM vendors by requiring us to break POOM into multiple projects (which should be fine) - Im just pointing out it was more of an IT decision in this case.

So what we have to do is take a look at the 25% we have for POOMs budget and break it between cameroon-one and kairos.  I havent run the numbers yet, but it probably means carving out a split between the two, like for example, 19% to cameroon one and 6% to kairos (whatever % works the best).  Later as they expand we can vote sanctuary polls to change the percentages.  So POOM would have two campaigns:  Kairos and Cameroon-One.  With %s that add up to the grand total %.  So as soon as we deploy Kairos to prod, which will be the same date we roll out PODC 2.0 (probably Dec 15th), we would at the same time add the Kairos campaign, and adjust the total campaign %s to reflect the proper total POOM %.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 16, 2019, 07:57:57 AM
Yes that’s the verse! Is your wife Chinese?

Yes - from Qingdao.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 16, 2019, 08:00:23 AM

i did exec associate sunk818 vccode


{
[/size]  "Command": "associate",
[/size]  "wcg_member_id": 1067915,
[/size]  "wcg_points": 146514500,
[/size]  "cpid": "c3939b61e69c6bde1eddb06708e0f96e",
[/size]  "rac": 6422.256021,
[/size]  "researcher_nickname": "sunk818",
[/size]  "Error": "ALREADY_IN_CHAIN"
[/size]}
[/size]
[/size]

Please add true to the end and it should force it in.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 16, 2019, 10:14:53 AM
not sure where you see yi* because i cant see it

but here are somescreenshots
(https://i.imgur.com/S5sFmya.png)
(https://i.imgur.com/CqkbKuf.png)

Code: [Select]
14:17:51

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16502,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69376573.58,
  "total_wcg_points": 485636015.06,
  "external_purse_total_coin_age": 963515.4535069445,
  "coin_age_percent_required": 0.4039957165891909,
  "coin_age_required": 379620.9615492278,
  "wcg_id": 1066130,
  "rac": 19579.781208
}


14:21:40

sendgscc wcg


14:21:40

{
  "Results": true
}


14:21:47

exec rac


14:21:47

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16502,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69376573.58,
  "total_wcg_points": 485636015.06,
  "external_purse_total_coin_age": 727273.1985069445,
  "coin_age_percent_required": 0.5319784839157702,
  "coin_age_required": 379620.9615492278,
  "wcg_id": 1066130,
  "rac": 19579.781208
}

txid 6ca683c024cf65a0d1c69ce9d6ca198a1ee1b3a7259cecddc8becb6426fcd71f

as you can see, some coins was taken from cpk and some from normal address. and before i had 509k in cpk, and after 491k and 18k was moved to normal address

i think that if i moved 1m to cpk, then only these coins will be used as source for coin age and will not be mixed with other coins in any direction

Ok, I believe you do have a point, while looking at that txid you pasted, it does appear we were able to pull some coins out of the internal purse (probably because your wallet was not locked etc).  But that does bring up some interesting questions.

I wrote a utility for the next version that will make it easy to analyze the GSC transmission:


Code: [Select]


10:10:28

exec auditabntx 6ca683c024cf65a0d1c69ce9d6ca198a1ee1b3a7259cecddc8becb6426fcd71f


10:10:28

{
  "Command": "auditabntx",
  "audited_weight": 0,
  "Vin # 0": "3840.55bbp - yguukBLQKCVgxKAATEQUt4eND2pKWaJzKk",
  "Vin # 1": "3840.36bbp - yguukBLQKCVgxKAATEQUt4eND2pKWaJzKk",
  "Vin # 2": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 3": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 4": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 5": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 6": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 7": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 8": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 9": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 10": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 11": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 12": "1439.27bbp - yiQfq1B9fFTsXwtLsQcvumFGdmM81SFbTf",
  "Vin # 13": "3840.17bbp - yguukBLQKCVgxKAATEQUt4eND2pKWaJzKk",
  "Vin # 14": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 15": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 16": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 17": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 18": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 19": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 20": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 21": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 22": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 23": "2.96bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 24": "22.30bbp - ycdi7xhDayyuASRFMrqiqGXyn3LmGGZ41Z",
  "Vin # 25": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 26": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 27": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 28": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 29": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 30": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 31": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 32": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 33": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 34": "22311.59bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Vin # 35": "187231.71bbp - yP64vX6kzBz1EFHP8Urmkzdd3jJDj4QszM",
  "VOUT #0": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #1": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #2": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #3": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #4": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #5": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #6": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #7": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #8": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #9": "20532.77bbp - yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "VOUT #10": "218061.74bbp - yV7ogWWfjCLMot2mmiKckfKk67MtrVTuwY"
}




So looking at the transmission it has the following issues:

Vin # 0, 1, 13 were not taken from the CPK?  (Interesting).

Output #10 was sent back to you in the form of a new address, and it really should have gone to your CPK (to keep it recycling).


Ill look at these two issues next.


Thanks for pointing this out.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 16, 2019, 01:38:56 PM
BiblePay TestNet
1.4.7.4 - Leisure Upgrade

- Ensure all GSC transactions use the external purse only, and all change comes back to the external purse.
- Add 'exec auditabntx txid', to allow us to see the VIN source, amount, and coin*age, and the VOUT destination and change addresses.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 16, 2019, 04:43:20 PM
Please add true to the end and it should force it in.


I wonder if there's value in always forcing it true. Seems like a point of confusion to use true or not. Any harm in making it the default?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 16, 2019, 06:39:08 PM
Will someone please test unbanked, to ensure you get auto payments each day and dont need to post a stake?

Im going to start a 2nd cpid soon but havent got around to it.

You just need to lower your rac down to below 250 and above 1.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 17, 2019, 09:47:08 AM
What happens if we send funds to DWS but don't get it back? For example, in this last situation we lost all the test tBBP. Is there a way to recover in case of catastrophe?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 17, 2019, 11:44:16 AM
What happens if we send funds to DWS but don't get it back? For example, in this last situation we lost all the test tBBP. Is there a way to recover in case of catastrophe?

1) Yes we lost the tBBP, but thats because the test format changed; in prod that would never happen.  Obviously, we would not release the change without a smooth cutover between ended payments and new payments in prod.
2) As far as the question though, if there is a technical glitch or for some reason, the payment is not paid back, it would be lost.  There is no mechanism in BBP for it to re-send it if the sancs don't send it to you on the due date.  To clarify though, I originally planned on making the algo detect 'unpaid items that need paid today' and then I realized that adds risk.  Right now the sancs are forced to pay things that are due from a certain block range; and the only risk would be the GSC contract fails that day.  BBP only risks sending out a max of 5mil per day.  If I started adding in the "possibility" of missing a day and sending 2* the amount that opens us up to way too much capital risk.  I think 5mil deflating is manageable, since our great deflation lowers this continually.  And allowing 5 mil per day in burns is good enough for most of us etc.  So at this point I feel the simplicity is safer than the riskiness of adding complexity and capital risk.  I will continue to explore other options for prod, such as 'longer term maturing coinbases and timed transactions', but those are not guaranteed to work for this use case.

  Its currently a use-at-your-own-risk feature, and this way it passes the Howey test also.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 17, 2019, 11:46:54 AM
Will someone please test unbanked, to ensure you get auto payments each day and dont need to post a stake?

Im going to start a 2nd cpid soon but havent got around to it.

You just need to lower your rac down to below 250 and above 1.

I started an unbanked CPID; waiting for RAC to increase.

I noticed that on brand new WCG CPIDs, we cant associate them right away because there is a delay on the WCG side.  Ill see if I can detect the condition and maybe we can add one more result code - something at least explaining the expected amount of time to wait between a new account and the time the 'associate' will actually work.   I emailed IBM about it - from the boinc side I can see the CPID, from the WCG side - their XML api returns 'name does not exist' but from the WCG web page the name does exist.  I also will re-clarify what we need to do about the data export reqs.  Im still not 100% sure if we need to demand the radio button be set to export stats or not.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 17, 2019, 12:02:58 PM
I got my DWS rewards last night, but there is no whale icon.  So if you are looking for yours look for smart-contract-reward.

Ill look into this issue.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 17, 2019, 12:17:23 PM

I wonder if there's value in always forcing it true. Seems like a point of confusion to use true or not. Any harm in making it the default?
Yes, harm because forcing it negates the path of code that explains common reasons it failed, like username already taken, etc.
Force=true is only for reassociations already in the chain.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 17, 2019, 02:12:30 PM
I got my DWS rewards last night, but there is no whale icon.  So if you are looking for yours look for smart-contract-reward.

Ill look into this issue.

Ok whale icon fixed, will be in the next release.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 18, 2019, 05:05:09 AM
i cleaned up my cpk address so i had only 1x 1m coins there, but then at time of automatic gsc sends, it takes whole 1m for kairos and then nothing for wcg... :) so whole coin age was spent on nothing and not saved for wcg..
is it possible to reorder somehow that wcg will goes first?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 18, 2019, 09:27:38 AM
i cleaned up my cpk address so i had only 1x 1m coins there, but then at time of automatic gsc sends, it takes whole 1m for kairos and then nothing for wcg... :) so whole coin age was spent on nothing and not saved for wcg..
is it possible to reorder somehow that wcg will goes first?

Well to be entirely honest with you, I think that will do damage.  Since we will have 4 campaigns (Kairos, cameroon, wcg and maybe healing) I think it will still be key for the user to use bankroll command, if they have any type of massive RAC like you.

So as long as we do the bankroll, what will happen is Kairos or Cameroon *will* pick the smallest bill and only use one bill.  It is already programmed to pick the smallest coin age for each GSC transmission as possible.

So in this case I think the best answer is for all of us to run exec bankroll knowing that we may have more than one tx per night.


EDIT:

However we can reorder them also.  Remind me in prod if I forget, we do have control of the iteration order; in Prod when we set the spork, we can set it to : WCG (0), then Cameroon-One (1) ... etc.   Yes, no problem.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 18, 2019, 01:33:16 PM
None of my dynamic whale staking went through on the latest version. I don't know if all the slots are filled up already...?




I also could start the chain fresh and BBP would crash every time around 12k. I don't know if it was peers on old versions, but I kept getting invalid block errors. I thought we had mandatory, but I kept seeing 1.4.7.2 and 1.4.7.3 peers. Even testnet1.biblepay.org was on 1.4.7.2.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 18, 2019, 02:45:49 PM
None of my dynamic whale staking went through on the latest version. I don't know if all the slots are filled up already...?




I also could start the chain fresh and BBP would crash every time around 12k. I don't know if it was peers on old versions, but I kept getting invalid block errors. I thought we had mandatory, but I kept seeing 1.4.7.2 and 1.4.7.3 peers. Even testnet1.biblepay.org was on 1.4.7.2.

Could you please explain what you mean by "none went through"? 
(On a side note, now we show the user immediately if it is going to fail right in the rpc, you will receive a nice error message now).  I just burned one: successful.
You are probably running the pre 1.4.7.4 version; if you run an old version it tries to use the "old" dws format which is no good. 

In the mean time, Ill try to sync from zero on the latest version to verify it can sync.

Yes, also, 1.4.7.4 only sync with its peers; and the sancs must be on 1.4.7.4 too.  Was MIPs binary released yet?  Or are you on windows, it could be my issue? 

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 18, 2019, 03:42:05 PM
None of my dynamic whale staking went through on the latest version. I don't know if all the slots are filled up already...?




I also could start the chain fresh and BBP would crash every time around 12k. I don't know if it was peers on old versions, but I kept getting invalid block errors. I thought we had mandatory, but I kept seeing 1.4.7.2 and 1.4.7.3 peers. Even testnet1.biblepay.org was on 1.4.7.2.


Ok, I confirm the crash during sync from zero.  So, I debugged this issue and indeed we have a bug.

The fix is checked in.

We will release a leisure fix for this bug.

On the dws burn issue, I believe the answer on that is to just ensure the version is 1.4.7.4+. 


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 18, 2019, 03:59:45 PM
BiblePay - TestNet
1.4.7.5 - Leisure Upgrade


- Fix crash during sync from zero reported by Sun
- Add extra DWS BL rule to prevent stakes from exceeding 5 mil on any future date (in addition to 5 mil in new burns per day)
- Check in POBH R&D class for MIP and the GPU contractor
- Add help message notes in exec associate to explain the missing steps
- Show the whale icon on Received stakes

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 18, 2019, 08:10:43 PM

Some Dynamic Whale Stake took but not all.

(https://i.imgur.com/lhDHP7U.jpg)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 18, 2019, 08:42:22 PM
I don't know how I ended up on a fork? But have half a dozen peers.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on November 19, 2019, 03:01:35 AM
Does anyone have an IP to use in addnode for this testnet? seems the one I had from past test is no longer valid.
Thanks.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 19, 2019, 08:58:10 AM
Some Dynamic Whale Stake took but not all.

(https://i.imgur.com/lhDHP7U.jpg)

Ok, so you mean 'I tried to send out multiple whale stakes from the rpc in succession, and they returned from the console successfully, but were not picked up by any of the other nodes - and - the status of the transaciton when I double click is Offline'.  Ok, this usually happens when the coins are locked by the prior transaction and the wallet prevents the next successive transaction against double spending those.  To find out if this is the exact cause copy the transactionID to the clipboard (after double clicking the transaction on the gui row).

Then do a 'cat debug.log | grep txid'.  It should say something like attempt to spend locked (or already spent) coins.  This is primarily a new feature in the .14 branch because Dash tries to autolock coins now for free instantsends. 

You can then recover by restarting with -zapwallettxes=1 and they will dissapear.

This is not really related to sending DWS's.

I maintain that we bubble the DWS error to the console now.

On DWS, we should wait until we see "In memory pool - broadcast through N nodes" before sending another one.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 19, 2019, 09:01:26 AM
I don't know how I ended up on a fork? But have half a dozen peers.

Check your log to see if you rejected the last superblock?  You can do this by getting the height of it (exec health, go to last block height) and analyze very close to that height and see if block rejects started to happen at that point.  If not find the exact height your rejects started.  That usually is one of the superblock heights.  If it is it means the node version you were running was probably running the old rules.  (Or, the node had gobject propagation issues).  You can also type 'gobject count' and make sure your gobject count is roughly what the other nodes are; and exec health should have the same number of votes as the other nodes.

Looking at the infrastructure now I dont see a fork.  All the sancs made it and my node is still in sync.

One nice thing about LLMQs is when a fork occurs, they start pose-banning each other very quickly (cause they cant hold the quorum), so technically the deterministic sancs should be a benefit to us in the next version.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 19, 2019, 10:27:44 AM
Does anyone have an IP to use in addnode for this testnet? seems the one I had from past test is no longer valid.
Thanks.

We had our primary DNS server->node for testnet running on the wrong port.

Fixed.  Now we have two running on the right port.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 19, 2019, 11:02:07 AM
one of my test wallet was stuck on block before superblock. other one was fine.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 19, 2019, 02:31:35 PM
I voted for the Kanye West proposal:

gobject list all proposals

Let me know if you receive the funds.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 19, 2019, 07:15:39 PM
** SPORK_19 : CHAINLOCKS HAS BEEN ENABLED FOR BIBLEPAY TESTNET ! **


- Now that we have 7 running sancs in testnet (we need a minimum of 3), theoretically we will keep the chainlocks LLMQ quorum.
- Chainlocks theoretically makes it almost impossible to perform a 51% attack on BBP.  This is because the chain will no longer be allowed to "roll-back" for reorgs.  Because, each sanctuary will be assessing the chain block by block.
- Additionally, biblepay should have higher security.  This is because not only do we have POW security, but sanctuary security.  An example here would be someone trying to alter the business logic in a fraudulent client.  The sanctuary quorum will already have each official block memorized that has been seen.
- Therefore, we now benefit by not only proof-of-work (strongest decentralized hashes provide security) but we also benefit from a form of proof-of-stake (because you must have capital to control N # of sancs).  This gives us a much higher total level of decentralized security than POW or POS alone.
- Because of this, BiblePay's GSCs just became stronger.  In addition, we can do "cool" things now, such as save energy, or provide subsidies for future items such as letter writing that simply were almost impossible or dangerous without chainlocks.
- Exchange Security:  Theoretically, with instant send autolocks and chainlocks, our exchange security just rose by a magnitude.  We will technically not need to have more than 7 block confirmations, since rollback risk is almost eliminated with chainlocks.
- What happens instead of reorgs now:  One strange side effect of chainlocks is the POSE ban sanc effect.  Theoretically what will happen in place of a fork is :  Sanctuaries will POSE ban each other and many small chains will exist.  This should not happen in prod, because of the massive number of sanctuaries (any number > 10 or so will keep the main chain rolling forward).  However in testnet, if we take down 75% of the sancs, we should see the chain split into multiple small and useless forks (meaning that they will be harmless).  This is in contrast to two big forks in pure POW mode.  Why is this?  This is because the chainlocks rules dictate that when a quorum cannot be maintained, the network will keep trying.  This prevents reorgs, and keeps everyone on a harmless "segment".



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 19, 2019, 08:44:54 PM

2019-11-20 02:28:28 UpdateTip: new best=609dd6f5a03962ad5313f4f7a9a1ffc945a0ae8d4e4578f3ae972ccab3e3cebd height=17211 version=0x20000001 log2_work=45.77639859 tx=26702 date='2019-11-20 02:28:18' progress=0.249753 cache=0.1MiB(448txo)
2019-11-20 02:28:28 {PNB}: ACC  {PNB}: ACC  ERROR: AcceptBlockHeader: prev block f449b1b97feddb3869fc604682355eefb80d35186d853bf678ff49daee7feecb conflicts with chainlock

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 20, 2019, 07:50:55 AM
2019-11-20 02:28:28 UpdateTip: new best=609dd6f5a03962ad5313f4f7a9a1ffc945a0ae8d4e4578f3ae972ccab3e3cebd height=17211 version=0x20000001 log2_work=45.77639859 tx=26702 date='2019-11-20 02:28:18' progress=0.249753 cache=0.1MiB(448txo)
2019-11-20 02:28:28 {PNB}: ACC  {PNB}: ACC  ERROR: AcceptBlockHeader: prev block f449b1b97feddb3869fc604682355eefb80d35186d853bf678ff49daee7feecb conflicts with chainlock


Seems to be okay now, I quit the testnet wallet and tried again and both are on 17308:
"hash": "0975df866939ada03b79d06fc5a087178b3f89931105ec5aaa02cd57345b8a78",
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 20, 2019, 01:25:33 PM

Seems to be okay now, I quit the testnet wallet and tried again and both are on 17308:
"hash": "0975df866939ada03b79d06fc5a087178b3f89931105ec5aaa02cd57345b8a78",

I grepped my dev log and don't see any chainlock errors, and it looks like our quorum is holding up from the sanc perspective so far.  No sancs are POSE banning each other.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 20, 2019, 03:01:17 PM
I voted for the Kanye West proposal:

gobject list all proposals

Let me know if you receive the funds.

I do not believe I got the funds for this proposal, looks like superblock passed recently,
I believe the proposal had 4-5 yes votes and 0 no votes,
I do still see the proposal in the proposals tab, hmmm

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 20, 2019, 03:06:50 PM
BiblePay - TestNet
1.4.7.7 - Mandatory Upgrade for TestNet

- Add mandatory (prod) cutover height 166,000 for PODC 2.0
- Increase deflation to 20.04% after PODC2.0 cutover height, and, enable DWS.  Ensure we have a spending cap in prod for each DWS day.  Add anti-fork DWS rules.  Ensure burn payments never exceed the cap (decrease them if this happens).
- Fix instantsend lock behavior
- Fix privatesend mixing denominations and mixing behavior
- Remove QT
- (MIP): Merge in all Dash prod changes from July up to the current date

** Windows is ready, the rest are compiling **

Please note:  All sancs and the entire network must upgrade as this includes all the Dash changes up to the current date and a consensus change.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 20, 2019, 03:09:48 PM
I do not believe I got the funds for this proposal, looks like superblock passed recently,
I believe the proposal had 4-5 yes votes and 0 no votes,
I do still see the proposal in the proposals tab, hmmm

I took a look at it this morning when the monthly budget was about to pass, and I believe what happened is the proposal was entered a couple blocks after the late-duration cut off - this is the cut off where its too late to create a trigger for payment.
So I copied the proposal into a new one, and now we know its at the beginning of the cycle again; lets see if this one pays.

Part of the challenge in testnet is the cycle is 4* per month instead of 1, so Im confident if it picks it up this time it was just the late-duration cut off issue.
(Especially since we had 7 sancs running at that time).

Lets defintely follow this through though.  I did test a few proposals in this branch a while back (back when we had 3 sancs) and they all paid, so I don't "believe" we have a payment issue with watchman but nevertheless lets watch it.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 20, 2019, 07:01:06 PM
I do not believe I got the funds for this proposal, looks like superblock passed recently,
I believe the proposal had 4-5 yes votes and 0 no votes,
I do still see the proposal in the proposals tab, hmmm

Togo, will you please test the Private Send mixing in testnet to ensure denominations are now correct, and mixing is faster and correct?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 20, 2019, 08:33:16 PM
All, lets please test instantsend thoroughly, lets verify the quality of IS is what we expect for prod in testnet?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 21, 2019, 07:48:03 AM

If we repeatedly send dws - there's no way to prevent this message? I can foresee a lot of tech support around this. You can tell people to send only one tx, but you know that will not happen. With PoG v1, people sent multiple tithes in a block... same scenario here.


2019-11-21 13:44:39 ERROR: AcceptToMemoryPool : Transaction b869f42c5188368c5f9a8541b48f384e6bbf79fed89f7d38f437161bc731956e conflicts with completed Transaction Lock ef650256b9e1d1fcb79f138f53baa5220bdc28d13f0c42dfce5db0eab4360616
2019-11-21 13:44:39 CommitTransaction(): Transaction cannot be broadcast immediately, tx-txlock-conflict



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 21, 2019, 08:27:37 AM
If we repeatedly send dws - there's no way to prevent this message? I can foresee a lot of tech support around this. You can tell people to send only one tx, but you know that will not happen. With PoG v1, people sent multiple tithes in a block... same scenario here.


2019-11-21 13:44:39 ERROR: AcceptToMemoryPool : Transaction b869f42c5188368c5f9a8541b48f384e6bbf79fed89f7d38f437161bc731956e conflicts with completed Transaction Lock ef650256b9e1d1fcb79f138f53baa5220bdc28d13f0c42dfce5db0eab4360616
2019-11-21 13:44:39 CommitTransaction(): Transaction cannot be broadcast immediately, tx-txlock-conflict


We could probably prevent this by requiring coins with at least 1 confirm for DWS.

Let me look into this.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 21, 2019, 09:37:43 AM

We could probably prevent this by requiring coins with at least 1 confirm for DWS.

Let me look into this.

Ok everyone please stop testing the DWS burns until the next version, I added a couple more rules.

Lets test everything else.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 21, 2019, 09:44:41 AM
So I updated the test cases in Post #2.  Please let me know if you all can think of any more test cases reqd.  You can also execute the test cases that we have not executed.

I also started an unbanked researcher with 90 rac. 

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 21, 2019, 01:11:20 PM
Hey Rob and MIP,

Im trying to download
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz
But I think its a 0kb file right now?
Tested on Ubuntu with wget and downloading through web browser on Windows
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 21, 2019, 03:38:54 PM
Ok everyone please stop testing the DWS burns until the next version, I added a couple more rules.

Lets test everything else.


For PoDC 2.0, I was thinking of hopping back and forth between team BiblePay and another team (GRC or OByte). Was thinking I could time bouncing back and forth somehow to double dip.


Just thinking back to the days where PoDC users shifted BBP between wallets to perform their PoDC updates and stake far less than required. I think you are using coinage somehow so the wallet shifting wouldn't work, but still trying to figure out any potential exploits.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: klondike on November 21, 2019, 04:49:36 PM
Windows v.1.4.6.7+: https://biblepay.org/biblepayevo32develop.exe

what is 32?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 21, 2019, 08:25:29 PM
Hey Rob and MIP,

Im trying to download
Linux 64 bits QT: https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz
But I think its a 0kb file right now?
Tested on Ubuntu with wget and downloading through web browser on Windows

I've got one for deployment coming in a little bit; so we can keep testing DWS; let me finish it up tomorrow morning and then we can redeploy.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 21, 2019, 09:22:49 PM
BiblePay
1.4.7.8 - Mandatory Upgrade for TestNet

- Require depth of at least 1 for new DWS stakes, Enforce DWS max limit in every area to ensure the burn can't enter the chain resulting in an overlimit condition (and include memory pool totals)
- Add spork rejecting new child sponsorships when there are none available


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 23, 2019, 01:53:41 PM
I couldn't do mixing with my 1 masternode server, it gives an error, I guess masternodes cant mix?,
"client side mixing is not supported on masternodes"
so I have it down while I use another data directory and wallet for mixing,
in addition I also spun up 2 other servers

I'm getting this message on all 3 servers:

Code: [Select]
2019-11-23 19:42:35 CPrivateSendClientManager::GetRandomNotUsedMasternode -- 7 enabled masternodes, 0 masternodes to choose from
2019-11-23 19:42:35 CPrivateSendClientSession::StartNewQueue -- Can't find random masternode!

biblepay.conf settings:
Code: [Select]
enableprivatesend=1
privatesendamount=1000000
privatesendrounds=2
privatesendmultisession=1
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 23, 2019, 03:50:19 PM
I couldn't do mixing with my 1 masternode server, it gives an error, I guess masternodes cant mix?,
"client side mixing is not supported on masternodes"
so I have it down while I use another data directory and wallet for mixing,
in addition I also spun up 2 other servers

I'm getting this message on all 3 servers:

Code: [Select]
2019-11-23 19:42:35 CPrivateSendClientManager::GetRandomNotUsedMasternode -- 7 enabled masternodes, 0 masternodes to choose from
2019-11-23 19:42:35 CPrivateSendClientSession::StartNewQueue -- Can't find random masternode!

biblepay.conf settings:
Code: [Select]
enableprivatesend=1
privatesendamount=1000000
privatesendrounds=2
privatesendmultisession=1

Ok, I see the problem.

Yes, we need a fix for this, and I have a couple more rules I added in for DWS; and something is coming for POBH in testnet ;

Please let me release a new release.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 23, 2019, 04:43:15 PM
BiblePay
1.4.7.9 - Mandatory Upgrade for TestNet

- Fix privatesend denominations mismatch, and increase privatesend defaults, and allow up to 5mil instandsend in the QT gui
- Increase solominer's efficiency, to approx 90% of the external miner
- Improve instantiation of a new DWS to be atomic.  Ensure all nodes assess the DWS metrics live (from the memory pool).
- Free up RAM used by Pobh.h for MIP

* This is the windows release; MIP will be compiling all the rest asap.  Please post when ready, MIP.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 24, 2019, 09:43:50 AM
BiblePay
1.4.7.9 - Mandatory Upgrade for TestNet

- Fix privatesend denominations mismatch, and increase privatesend defaults, and allow up to 5mil instandsend in the QT gui
- Increase solominer's efficiency, to approx 90% of the external miner
- Improve instantiation of a new DWS to be atomic.  Ensure all nodes assess the DWS metrics live (from the memory pool).
- Free up RAM used by Pobh.h for MIP

* This is the windows release; MIP will be compiling all the rest asap.  Please post when ready, MIP.


Just to save everyones time:  Dash just released two PrivateSend fixes into prod that are required to be merged in, so please don't test this version of privatesend. 


A new version should be out within 2 days.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 24, 2019, 10:31:53 AM
Will we have InstantSend default or ChainLocks in the recent merges?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 24, 2019, 10:45:55 AM
did we need something in our biblepay.conf to send out wcg tx regularly?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 24, 2019, 01:44:16 PM
sorry guys, i dont have time now, i'm redesigning house so whole day without pc ... :D
but i think i'm on some fork now... downloaded new version and did reindex, will see tomorrow...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 24, 2019, 09:51:47 PM
BiblePay - TestNet
1.4.8.1 - Mandatory Upgrade for TestNet


- Update private send denominations
- Ensure exec bankroll spends coins with depth > 0
- Release dash 0.14.0.4 :  https://blog.dash.org/product-update-november-22-2019-1dc02575ce58

** This is the windows release only. **
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 25, 2019, 12:21:24 PM
I'm still having same issue with mixing, cant find random masternode

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1170

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1040

How does vecMasternodesUsed variable work?

Code: [Select]
int nCountEnabled = mnList.GetValidMNsCount();
int nCountNotExcluded = nCountEnabled - vecMasternodesUsed.size();

LogPrintf("CPrivateSendClientManager::%s -- %d enabled masternodes, %d masternodes to choose from\n", __func__, nCountEnabled, nCountNotExcluded);
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 25, 2019, 01:46:07 PM
Hi all,
I was out for a moment, but it looks, that it's all working good for me.
What is needed to test? Some special scenarios? (but except MN)
It looks that taking tBBP to WCG only from CPK address is working for me good.
But I don't know if it's instantsend working good.
When I sent tBBP to myself, it everytime needs 6 block to confirm.
BTW. It'
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: orbis on November 25, 2019, 01:51:35 PM
BTW: It's possible to put Smart-Contract reward on main screen recent tx?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 25, 2019, 03:35:31 PM
I'm still having same issue with mixing, cant find random masternode

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1170

https://github.com/biblepay/biblepay-evolution/blob/develop/src/privatesend-client.cpp#L1040

How does vecMasternodesUsed variable work?

Code: [Select]
int nCountEnabled = mnList.GetValidMNsCount();
int nCountNotExcluded = nCountEnabled - vecMasternodesUsed.size();

LogPrintf("CPrivateSendClientManager::%s -- %d enabled masternodes, %d masternodes to choose from\n", __func__, nCountEnabled, nCountNotExcluded);

We first need to verify every sanctuary upgraded to the new version, then we can re-try private send mixing.

I recommend trying the mixing from a new wallet (so we dont intermingle the new external purse and PODC testing with this).

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 25, 2019, 04:19:06 PM
Hi all,
I was out for a moment, but it looks, that it's all working good for me.
What is needed to test? Some special scenarios? (but except MN)
It looks that taking tBBP to WCG only from CPK address is working for me good.
But I don't know if it's instantsend working good.
When I sent tBBP to myself, it everytime needs 6 block to confirm.
BTW. It'

We need to verify the sancs have upgraded before we re-test IX.

These sancs who are running a lower protocol version will refuse to handle the IX request.

You can also help by verifying that we covered the other test cases in post #2.  I think you can safely skip by Kairos for now, as Kairos is about to go online in testnet with Andys side, so dont test that and also dont test Cameroon One.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 25, 2019, 04:21:12 PM
Will we have InstantSend default or ChainLocks in the recent merges?

Yes, now InstantSend autolocks is on by default, and also, chainlocks is on permanently now (in testnet).

But all sancs need to be on the highest protoversion first, and I see one of my sancs failed to upgrade.

Lets re-test hashes once we all do that, lets post here if your sanc is running 1.4.8.1.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 25, 2019, 04:21:54 PM
did we need something in our biblepay.conf to send out wcg tx regularly?

No, nothing.  If you type 'exec rac' it should reveal the height in which the daily tx goes out (automatically).

PODC_Height:
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 25, 2019, 04:25:09 PM
sorry guys, i dont have time now, i'm redesigning house so whole day without pc ... :D
but i think i'm on some fork now... downloaded new version and did reindex, will see tomorrow...

We seem to get a fork at the GSC height after every mandatory upgrade.

I have a hypothesis for this:  When I put it out it usually takes 12 hours for MIP to compile it, and then maybe about 24 hours longer for the sancs to upgrade.
During that span, if we miss the "common voting" on the GSC contract, this causes the POW miners to mine a POW block in place of the gsc.

Other miners probably mine their own view of a block with the GSC voted in - hard to say which side of the network wins.

Then we all resync and end up on the chain with the most work.
I am still thinking about this dirtyblockindex; not sure if its doing more harm than good for us.  It is the reason we need to resync when our node has one bad block in the chain.

Ill talk to MIP about this logic.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 25, 2019, 04:54:55 PM
We seem to get a fork at the GSC height after every mandatory upgrade.

I have a hypothesis for this:  When I put it out it usually takes 12 hours for MIP to compile it, and then maybe about 24 hours longer for the sancs to upgrade.
During that span, if we miss the "common voting" on the GSC contract, this causes the POW miners to mine a POW block in place of the gsc.

Other miners probably mine their own view of a block with the GSC voted in - hard to say which side of the network wins.

Then we all resync and end up on the chain with the most work.
I am still thinking about this dirtyblockindex; not sure if its doing more harm than good for us.  It is the reason we need to resync when our node has one bad block in the chain.

Ill talk to MIP about this logic.


So as we get a little more complicated our checklist is increasing.

In my case, I was able to overcome the fork by doing this:

rm instantsend.dat
restart client
exec reassesschains


The problem was the instantsend transmissions done between mandatory upgrades were memorized as IX locks.

Now my 3 sancs are syncing to the same height.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 25, 2019, 08:31:34 PM
Ok, my 3 sancs are on 1.4.8.1 now;  if we can get a confirmation that Oncoapops are on 1.4.8.1 then I think we can test IX and PS.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 25, 2019, 10:08:49 PM
Ok, my 3 sancs are on 1.4.8.1 now;  if we can get a confirmation that Oncoapops are on 1.4.8.1 then I think we can test IX and PS.

My 3 sancs are on 1.4.8.1
As you previously observed, my sancs are all running Linux and it does take time for the linux binaries to be available for download. My machines are also not powerful ones so they take an age to compile them from source. With all these said, mine are now current.

Is there a command to see which version the sancs are running without logging into the sancs themselves? Like version report for sancs?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 09:19:08 AM
My 3 sancs are on 1.4.8.1
As you previously observed, my sancs are all running Linux and it does take time for the linux binaries to be available for download. My machines are also not powerful ones so they take an age to compile them from source. With all these said, mine are now current.

Is there a command to see which version the sancs are running without logging into the sancs themselves? Like version report for sancs?

Unfortunately, Dash took out the masternode version in the deterministic branch, so now we have no way to tell what version they are running.

I tried to put it back in 'masternodelist all', but it is actually missing everywhere in the code.

10-4 on the upgrade speed; Im pretty much in the same boat with my QT sancs, because I self compile and it puts a strain on this small hosting companies server.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 10:03:14 AM
I just tested 5 IX tx's from 100 bbp to 100,000 bbp and they were all successful.

Note that as long as you see the Key and the Check (IX verified) next to the transaction, that is all that needs to be done (and optionally check on the receiving side to verify the IX funds were received).  The QT wallet still goes through the 6 normal confirms before showing "confirmed", but that does not mean IX is taking 6 confirms.  Because stores who accept IS funds have a boolean available to see if the funds were IS sent and they can optionally accept the funds immediately.  Some wait til the funds are IS sent and in a block, but that is up to each retailer.

I believe IX is working properly in testnet.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 12:45:50 PM
So in the spirit of my last bitcointalk post, I feel God wants me to focus in on giving the users the ability to : instantiate a treasure trove item, and see the list of treasure trove videos that have been archived (with high scalability).  I have a plan to offer very high scalability even with our feeble network.  Basically I plan on making a cloudflare account, and through some type of abstraction we will give the ability to archive a copy of a youtube Christian video (with permission) into a cloudflare servers mp4 storage "stream" version, so we can host the cloudflare version through DSQL.  This would theoretically stay live even if google or youtube goes down - since the idea with cloudflare is to be part of the backbone of the net.  More on this later.

But first, the highest priority.  I feel like Satan has been running rampant through this project trying to paralyze us.  I saw all these issues over the last few days, with sancs going into new start required, with gobject propagation appearing to be on the feeble side, with the bad sanc list increasing in prod (now fixed), and just in general, things I feel should not be happening in prod.

This leads me to the state we are in- we must have a solid future version that is fork free permanently, that has perfect GSC blocks, perfect gobject propagation, and none of these sanctuary expired issues, or instantsend problems etc.

So, I feel we really must slow down and fix this right now, as production support and maintenance stops new development (and gives us a black eye) etc.

In light of this Im going to stop everything to take a look again at gobject propagation, superblock heights, and how we make the calls.
What I really would like to see, is the ability for our nodes to recover by themselves onto the chain with the most work.
Im questioning whether this dirty block index rule is doing more harm than good.

My goal is to add some code to testnet that can theoretically handle a situation for example, a mandatory upgrade, where the node can auto-recover after the supermajority upgrades (in contrast to sitting on a private chain, due to having a bad block in memory).



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 12:49:08 PM
All,

Now that everyone is on the new version, go ahead and pound DWS.
Do whatever you want to try to break it.
It should be able to handle overlimit conditions, and should pay back everything burned each day (as long as the GSCs are voted in).  And on a side note, these have always been voted in prod.  I think we missed 1 in two years (due to having no sancs or something in the middle of PODC 1.0). 

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 26, 2019, 01:43:13 PM
So in the spirit of my last bitcointalk post, I feel God wants me to focus in on giving the users the ability to : instantiate a treasure trove item, and see the list of treasure trove videos that have been archived (with high scalability).  I have a plan to offer very high scalability even with our feeble network.  Basically I plan on making a cloudflare account, and through some type of abstraction we will give the ability to archive a copy of a youtube Christian video (with permission) into a cloudflare servers mp4 storage "stream" version, so we can host the cloudflare version through DSQL.  This would theoretically stay live even if google or youtube goes down - since the idea with cloudflare is to be part of the backbone of the net.  More on this later.

But first, the highest priority.  I feel like Satan has been running rampant through this project trying to paralyze us.  I saw all these issues over the last few days, with sancs going into new start required, with gobject propagation appearing to be on the feeble side, with the bad sanc list increasing in prod (now fixed), and just in general, things I feel should not be happening in prod.

This leads me to the state we are in- we must have a solid future version that is fork free permanently, that has perfect GSC blocks, perfect gobject propagation, and none of these sanctuary expired issues, or instantsend problems etc.

So, I feel we really must slow down and fix this right now, as production support and maintenance stops new development (and gives us a black eye) etc.

In light of this Im going to stop everything to take a look again at gobject propagation, superblock heights, and how we make the calls.
What I really would like to see, is the ability for our nodes to recover by themselves onto the chain with the most work.
Im questioning whether this dirty block index rule is doing more harm than good.

My goal is to add some code to testnet that can theoretically handle a situation for example, a mandatory upgrade, where the node can auto-recover after the supermajority upgrades (in contrast to sitting on a private chain, due to having a bad block in memory).

I do support slowing down. When I upgraded all my sancs and clients were on the same testnet chain.

Today two were not running when I checked and the others were on different hashes for the same block but all sancs still appeared to be enabled on the masternode list. It should noted that previous versions could be left unattended for days.

Maybe its my VPS machines, I cannot tell, but stability has be altered since the last upgrade, whether it is due to the temporal instability in network, I cannot conclude either as there is no way I can discern the state of the network beyond the servers I control.

In addition the masternode list currently is in contrast to the non DIP3 sanc situation where the state of the network could be quickly and rather accurately discerned from the masternode list.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: capo on November 26, 2019, 02:00:39 PM
am i on correct chain?

20:59:05

getblockhash 18428


20:59:05

0fa85496c3c05dc10054905e4b0daf41bd4bafdec2f828765a504d992192ecb3


i'm not sure... but i cant do dws. it just do nothing...



21:00:09

exec dws 100000 2 1


21:00:10

{
  "Command": "dws",
  "Staking Amount": 100000,
  "Duration": 2,
  "Reclaim Date": "11-28-2019 20:00:10",
  "Return Address": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "DWU": "91.9857",
  "Test Mode": "By typing I_AGREE in uppercase, you agree to the following conditions:\n1.  I AM MAKING A SELF DIRECTED DECISION TO BURN THIS BIBLEPAY, AND DO NOT EXPECT AN INCREASE IN VALUE.\n2.  I HAVE NOT BEEN PROMISED A PROFIT, AND BIBLEPAY IS NOT PROMISING ME ANY HOPES OF PROFIT IN ANY WAY.\n3.  BIBLEPAY IS NOT ACTING AS A COMMON ENTERPRISE OR THIRD PARTY IN THIS ENDEAVOR.\n4.  I HOLD BIBLEPAY AS A HARMLESS UTILITY.\n5.  I REALIZE I AM RISKING 100% OF MY CRYPTO-HOLDINGS BY BURNING IT, AND BIBLEPAY IS NOT OBLIGATED TO REFUND MY CRYPTO-HOLDINGS OR GIVE ME ANY REWARD."
}

and no tx created
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 02:02:50 PM
I do support slowing down. When I upgraded all my sancs and clients were on the same testnet chain.

Today two were not running when I checked and the others were on different hashes for the same block but all sancs still appeared to be enabled on the masternode list. It should noted that previous versions could be left unattended for days.

Maybe its my VPS machines, I cannot tell, but stability has be altered since the last upgrade, whether it is due to the temporal instability in network, I cannot conclude either as there is no way I can discern the state of the network beyond the servers I control.

In addition the masternode list currently is in contrast to the non DIP3 sanc situation where the state of the network could be quickly and rather accurately discerned from the masternode list.

Well although we lost some of the fields, I do think there will be alternatives to the same info for example we have to consider these LLMQ quorums are only supposed to work within the quorum group themself who are creating the quorum from the currently allowed protoversion (another words, after a mandatory, when I increase the minimum govnance version, only those sancs can participate in the LLMQ, so theoretically, the lower sancs would fall out of the quorum and get POSE banned).

But first could we check those two as guinea pigs that have the wrong hashes?  Id really like to get to the root of the problem so we can always blame it on one specific thing.  Up til today, I blamed a chain fork on failure to pass the last gsc height.  It was not til this version where I saw all these instantsend autolock failures.

Could you please try this:
On one, try 'exec reassesschains' and on the other, delete the instantsend.dat, then try exec reassesschains?  Lets see what fixes each one?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 26, 2019, 02:17:50 PM
No, nothing.  If you type 'exec rac' it should reveal the height in which the daily tx goes out (automatically).

PODC_Height:


When I type exec rac, I don't see podc_height.


I see a next_podc_gsc_transmission. the block is 18347, but I think we are on 18422 (although I could be on the wrong chain).



  "next_podc_gsc_transmission": 18347,
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 26, 2019, 02:25:39 PM
Well although we lost some of the fields, I do think there will be alternatives to the same info for example we have to consider these LLMQ quorums are only supposed to work within the quorum group themself who are creating the quorum from the currently allowed protoversion (another words, after a mandatory, when I increase the minimum govnance version, only those sancs can participate in the LLMQ, so theoretically, the lower sancs would fall out of the quorum and get POSE banned).

But first could we check those two as guinea pigs that have the wrong hashes?  Id really like to get to the root of the problem so we can always blame it on one specific thing.  Up til today, I blamed a chain fork on failure to pass the last gsc height.  It was not til this version where I saw all these instantsend autolock failures.

Could you please try this:
On one, try 'exec reassesschains' and on the other, delete the instantsend.dat, then try exec reassesschains?  Lets see what fixes each one?

Don’t know how long I have to wait after reassesschains.

VPS1

Code: [Select]
cligetblockcount
18431
cli getblockhash 18431
7a28fc55fb6ac41d1987c2b93d093d8302526b63ef4a26ea67547aaeb895e14b
cli exec reassesschains
{
 "Command": "reassesschains",
 "progress": 11
}
cli getblockcount
18433
cli getblockhash 18433
5e76b6e223aafa7ceb64e7bf187454425ba7856828974f05d104ed41d07c4f9d

VPS2

Code: [Select]
cli getblockcount
18446
cli getblockhash 18431
3ee3f6e9dae4761c0f4f90707dd928bb5b336a470f9ca430f983bb54e48290f2
rm ~/.biblepayevolution/instantsend.dat

cli exec reassesschains
{
 "Command": "reassesschains",
 "progress": 69
}
cli getblockcount
18447
cli getblockhash 18431
3ee3f6e9dae4761c0f4f90707dd928bb5b336a470f9ca430f983bb54e48290f2
cli getblockhash 18433
b8b7e44b896afceda97a4bfa20c187db4ec582b61be6942028d096855ae0399f



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 02:33:05 PM
Don’t know how long I have to wait after reassesschains.

VPS1

Code: [Select]
cligetblockcount
18431
cli getblockhash 18431
7a28fc55fb6ac41d1987c2b93d093d8302526b63ef4a26ea67547aaeb895e14b
cli exec reassesschains
{
 "Command": "reassesschains",
 "progress": 11
}
cli getblockcount
18433
cli getblockhash 18433
5e76b6e223aafa7ceb64e7bf187454425ba7856828974f05d104ed41d07c4f9d

VPS2

Code: [Select]
cli getblockcount
18446
cli getblockhash 18431
3ee3f6e9dae4761c0f4f90707dd928bb5b336a470f9ca430f983bb54e48290f2
rm ~/.biblepayevolution/instantsend.dat

cli exec reassesschains
{
 "Command": "reassesschains",
 "progress": 69
}
cli getblockcount
18447
cli getblockhash 18431
3ee3f6e9dae4761c0f4f90707dd928bb5b336a470f9ca430f983bb54e48290f2
cli getblockhash 18433
b8b7e44b896afceda97a4bfa20c187db4ec582b61be6942028d096855ae0399f


Ok, I think we are on to something.
Your second node is now in sync with my nodes  - getblockhash 18433:
b8b7e44b896afceda97a4bfa20c187db4ec582b61be6942028d096855ae0399f


Try this now on the first node:

Stop it
then delete
~/.biblepayevolution/testnet3/instantsend.dat
Restart it
then exec reassesschains
And see if it matches?


On a side note guys, I found out that Dash prod is using the switch IX_LLMQ_BASED , and we were not.
So I am setting that now, to enable it .

Lets go in baby steps 2, first Oncoapop, please tell me what hapens with this one, then we can regroup.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 02:35:50 PM
am i on correct chain?

20:59:05

getblockhash 18428


20:59:05

0fa85496c3c05dc10054905e4b0daf41bd4bafdec2f828765a504d992192ecb3


i'm not sure... but i cant do dws. it just do nothing...



21:00:09

exec dws 100000 2 1


21:00:10

{
Code: [Select]
  "Command": "dws",
  "Staking Amount": 100000,
  "Duration": 2,
  "Reclaim Date": "11-28-2019 20:00:10",
  "Return Address": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "DWU": "91.9857",
  "Test Mode": "By typing I_AGREE in uppercase, you agree to the following conditions:\n1.  I AM MAKING A SELF DIRECTED DECISION TO BURN THIS BIBLEPAY, AND DO NOT EXPECT AN INCREASE IN VALUE.\n2.  I HAVE NOT BEEN PROMISED A PROFIT, AND BIBLEPAY IS NOT PROMISING ME ANY HOPES OF PROFIT IN ANY WAY.\n3.  BIBLEPAY IS NOT ACTING AS A COMMON ENTERPRISE OR THIRD PARTY IN THIS ENDEAVOR.\n4.  I HOLD BIBLEPAY AS A HARMLESS UTILITY.\n5.  I REALIZE I AM RISKING 100% OF MY CRYPTO-HOLDINGS BY BURNING IT, AND BIBLEPAY IS NOT OBLIGATED TO REFUND MY CRYPTO-HOLDINGS OR GIVE ME ANY REWARD."
}

and no tx created

First I think you are on the wrong chain - not your fault, most likely this IX issue.  Please delete "testnet3/instantsend.dat" then restart, then type exec reassesschains?

Then check to see the hash matches the oncapop hash?

As far as the burn itself, you have to add "I_AGREE" to the last param to get it to go, otherwise it just prints out the current quote.
So that part is OK.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 26, 2019, 02:51:06 PM
i erase the chain started over... now exec rac says


looks like I missed the one in between



"next_podc_gsc_transmission": 18552,
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 26, 2019, 02:54:04 PM
other than healing and pog (or dws) which are manual transactions anyways... it makes sense to to add POOM to auto payments like WCG? If the accounting is correct and you trust the oracle data, then I don't think it should matter whether it is BOINC data or POOM data.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 03:19:59 PM
other than healing and pog (or dws) which are manual transactions anyways... it makes sense to to add POOM to auto payments like WCG? If the accounting is correct and you trust the oracle data, then I don't think it should matter whether it is BOINC data or POOM data.

Yes, poom makes auto gsc transmissions now, but it requires the transaction fee amount.

All GSCs are sent at the WCG height.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 03:25:04 PM
I find it very odd that we have 21 testnet nodes, all on the newest version I see.

This last release does not feel right.  After deleting instantsend Im getting different heights now on my sancs.

I'm dissapointed in the latest stable branch.  Right now we are running what Dash prod is running.
Looks like we need to dig deeper into the problem.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 26, 2019, 04:09:54 PM
had to erasechain and delete instantsend.dat - settled on 18446. was on 18459



2019-11-26 21:41:27 UpdateTip: new best=8b1ad9df4a08823a7b1cb36c7671d21e8b549334e322ff6e1bfebfaf0e7e8170 height=18459 version=0x20000001 log2_work=46.18226809 tx=29113 date='2019-11-26 21:29:42' progress=0.258118 cache=0.1MiB(897txo) evodb_cache=0.0MiB
2019-11-26 21:41:27 CheckForkWarningConditions: Warning: Found invalid chain which has higher work (at least ~6 blocks worth of work) than our best chain.




If I had the foresight, I would have saved the old instandsend.dat and current so you could do some binary comparison.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 26, 2019, 04:18:33 PM
I find it very odd that we have 21 testnet nodes, all on the newest version I see.

This last release does not feel right.  After deleting instantsend Im getting different heights now on my sancs.

I'm dissapointed in the latest stable branch.  Right now we are running what Dash prod is running.
Looks like we need to dig deeper into the problem.

After deleting instandsend.dat, and restarting I can only get to height 18380 even after reassesschains.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 26, 2019, 04:19:27 PM
After deleting instandsend.dat, and restarting I can only get to height 18380 even after reassesschains.

Sorry i meant instantsend.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 26, 2019, 04:34:40 PM
After deleting instandsend.dat, and restarting I can only get to height 18380 even after reassesschains.

I realized that I reported too soon... reassess got me to a higher height.

Code: [Select]
getblockcount
18380
cli getblockhash 18433
error code: -8
error message:
Block height out of range

cli exec reassesschains
{
 "Command": "reassesschains",
 "progress": 65
}
cli mnsync status
{
 "AssetID": 0,
 "AssetName": "MASTERNODE_SYNC_INITIAL",
 "AssetStartTime": 1574804204,
 "Attempt": 0,
 "IsBlockchainSynced": false,
 "IsSynced": false,
 "IsFailed": false
}

wait for sync to complete.

Code: [Select]
cli mnsync status
{
 "AssetID": 999,
 "AssetName": "MASTERNODE_SYNC_FINISHED",
 "AssetStartTime": 1574807022,
 "Attempt": 0,
 "IsBlockchainSynced": true,
 "IsSynced": true,
 "IsFailed": false
}
cli getblockhash 18433
5e76b6e223aafa7ceb64e7bf187454425ba7856828974f05d104ed41d07c4f9d
Getblockcount
18448

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 04:50:09 PM
I realized that I reported too soon... reassess got me to a higher height.

Code: [Select]
getblockcount
18380
cli getblockhash 18433
error code: -8
error message:
Block height out of range

cli exec reassesschains
{
 "Command": "reassesschains",
 "progress": 65
}
cli mnsync status
{
 "AssetID": 0,
 "AssetName": "MASTERNODE_SYNC_INITIAL",
 "AssetStartTime": 1574804204,
 "Attempt": 0,
 "IsBlockchainSynced": false,
 "IsSynced": false,
 "IsFailed": false
}

wait for sync to complete.

Code: [Select]
cli mnsync status
{
 "AssetID": 999,
 "AssetName": "MASTERNODE_SYNC_FINISHED",
 "AssetStartTime": 1574807022,
 "Attempt": 0,
 "IsBlockchainSynced": true,
 "IsSynced": true,
 "IsFailed": false
}
cli getblockhash 18433
5e76b6e223aafa7ceb64e7bf187454425ba7856828974f05d104ed41d07c4f9d
Getblockcount
18448

Yeah, Im looking through the heights on my node that has 21 connections and everyone is at a different height, so its not the GSC block at all, it points to LLMQ and IX locks.

Unfortunately what it looks like is something like this:
Half of the sancs were forming their own version of the LLMQ quorum, so they have a different cache of IX locks.
The other half, has a different quorum.
The reason I can tell, is I found I can end up on a different height after erasing the chain twice, and, I can see what height some of the sancs are at by looking them up by IP.

This is interesting because it appears that the chain you end up on depends on which governance data you synced from.

So let me look deeper into the issue.  The answer is probably going to be marking a checkpoint block, and then ensuring our LLMQ all adheres to one chain after we upgrade.

This is much more complicated than plain old POW in bitcoin.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 26, 2019, 05:22:41 PM
Yeah, Im looking through the heights on my node that has 21 connections and everyone is at a different height, so its not the GSC block at all, it points to LLMQ and IX locks.

Unfortunately what it looks like is something like this:
Half of the sancs were forming their own version of the LLMQ quorum, so they have a different cache of IX locks.
The other half, has a different quorum.
The reason I can tell, is I found I can end up on a different height after erasing the chain twice, and, I can see what height some of the sancs are at by looking them up by IP.

This is interesting because it appears that the chain you end up on depends on which governance data you synced from.

So let me look deeper into the issue.  The answer is probably going to be marking a checkpoint block, and then ensuring our LLMQ all adheres to one chain after we upgrade.

This is much more complicated than plain old POW in bitcoin.

Thank you, Rob.

Whatever you did appeared to bring some stability to the network as sampled by my VPSs on the testnet chain, after deletion of instantsend.dat, exec reassesschains and waiting for mnsync status to finish.

currently, all my clients and sancs appear to be on the same chain

https://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml





Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 05:40:48 PM
Thank you, Rob.

Whatever you did appeared to bring some stability to the network as sampled by my VPSs on the testnet chain, after deletion of instantsend.dat, exec reassesschains and waiting for mnsync status to finish.

currently, all my clients and sancs appear to be on the same chain

https://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

I turned off the IX autolocks spork, then sent out a reconsiderlast 100 blocks spork, and now I see that your sanc page matches my hash also.

Lets let it run on this version overnight, until we surpass the highest bad block that these other straggling nodes have.

Ill keep looking into this issue deeper :).

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on November 26, 2019, 06:14:14 PM
I kept trying to erasechain but kept getting to a lower block height than you guys
I had to totally nuke my testnet3 folder (delete everything except the biblepay.conf, deterministic.conf, masternode.conf and wallet.dat files)

So now my 2 nodes and my 1 masternode are all synced with oncoapop
https://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 26, 2019, 06:15:57 PM
I kept trying to erasechain but kept getting to a lower block height than you guys
I had to totally nuke my testnet3 folder (delete everything except the biblepay.conf, deterministic.conf, masternode.conf and wallet.dat files)

So now my 2 nodes and my 1 masternode are all synced with oncoapop
https://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

Yeah, the issue is -erasechain=1 does not erase instantsend.dat.
So I added that into the next version.

Cool that you are synced now.

I suppose we need to find reliability in testnet before we consider this version to be stable.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 26, 2019, 06:44:48 PM
InstantSend (IX) used to say 5 out of 6 confirmations. Now it is just 1 out of 6, but with the key checkbox icon in the column? I notice the transaction line continues to be blue.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 26, 2019, 07:50:49 PM
Yeah, the issue is -erasechain=1 does not erase instantsend.dat.
So I added that into the next version.

Cool that you are synced now.

I suppose we need to find reliability in testnet before we consider this version to be stable.

Hmm, blockhashes appear to diverge from block 18475 on testchain. No intervention on my part.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 27, 2019, 01:02:03 AM
Hmm, blockhashes appear to diverge from block 18475 on testchain. No intervention on my part.

at Block 18514,
exec reassesschains
wait for mnsync status to finish

>cli getblockhash 18514
1f280bd0f1bb8796980493b54ed71c7fb5f35d16400ad0e3f0bca7d774f5e93d

So all wallets are back in sync again.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 27, 2019, 08:41:10 AM
InstantSend (IX) used to say 5 out of 6 confirmations. Now it is just 1 out of 6, but with the key checkbox icon in the column? I notice the transaction line continues to be blue.
That should be OK, there is a separate path in the code for the base confirms - and we can fix the final value, either way the result is the same:
https://forum.biblepay.org/index.php?topic=465.msg6701#msg6701
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 27, 2019, 08:46:57 AM
at Block 18514,
exec reassesschains
wait for mnsync status to finish

>cli getblockhash 18514
1f280bd0f1bb8796980493b54ed71c7fb5f35d16400ad0e3f0bca7d774f5e93d

So all wallets are back in sync again.

I was not awake at that particular height, but looking at my 4 wallets (I have 3 sancs) they all agree with your getblockhash 18514.
So the height you mentioned - 18475 - thats right after the last GSC.

Was it just one of your 3 sancs that went out and required manual intervention, and after that, did all 3 stay in sync?

Yes, we really need to get to the root of this and prevent this entirely, it might require me adding a checkpoint and all of us doing some testing from a certain height forward.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 27, 2019, 11:44:39 AM
I was not awake at that particular height, but looking at my 4 wallets (I have 3 sancs) they all agree with your getblockhash 18514.
So the height you mentioned - 18475 - thats right after the last GSC.

Was it just one of your 3 sancs that went out and required manual intervention, and after that, did all 3 stay in sync?

Yes, we really need to get to the root of this and prevent this entirely, it might require me adding a checkpoint and all of us doing some testing from a certain height forward.

2/3 sancs went on a parallel chain diverging at the block 18475, in fact both these appeared to be stuck on the previous block for some time after the two (1 sanc and 1 wallet) already accepted the block.

I left them till block 18514 to see if they will correct themselves but they did not and hence manually intervened to reassesschains.

All 3/3 sancs and the controller wallet have been in sync since block 18514.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 27, 2019, 12:08:36 PM
Togo, the Kanye proposal looks like it will pay this time, please double check @ 18655.

The prior proposal just missed the automatic trigger, but I see the trigger was created this time.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 27, 2019, 12:13:43 PM
2/3 sancs went on a parallel chain diverging at the block 18475, in fact both these appeared to be stuck on the previous block for some time after the two (1 sanc and 1 wallet) already accepted the block.

I left them till block 18514 to see if they will correct themselves but they did not and hence manually intervened to reassesschains.

All 3/3 sancs and the controller wallet have been in sync since block 18514.

Ok, thanks.  I will add a checkpoint, and, I will look into possibilities to prevent this next.
I would like to POSE ban the sancs who are below the minimum governance protocol version, but it looks hard for us to do now, but Im still investigating this among other things.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 27, 2019, 12:28:56 PM
I see one more change that is to be in the next version is increasing the GRC exponent requirement:
https://forum.biblepay.org/index.php?topic=476.new#new

Do we have any volunteer that wants to switch over to team Gridcoin, so we can test the coin-age-requirement is correct in the next version?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 27, 2019, 12:32:37 PM
Unfortunately, Dash took out the masternode version in the deterministic branch, so now we have no way to tell what version they are running.

I tried to put it back in 'masternodelist all', but it is actually missing everywhere in the code.

10-4 on the upgrade speed; Im pretty much in the same boat with my QT sancs, because I self compile and it puts a strain on this small hosting companies server.

One cannot tell the version of sanc other than if you are in control of the server running the sanc? I thought DIP3 the owner and operator could be separate parties. Surely one should be able to verify that information?

Also in the classic, when a sanc was on a different chain or offline, watchman would cause it to appear in a state other than ENABLED.

I still do not know how PoSE works on DIP3 sancs? Previously they were reported enabled when the servers were off. Then they began to be PoSE banned even though as far as i could tell they were on the same chain. Now even though the 2 sancs were clearly on a different chain, they appeared ENABLED when checked from the sanc on the main testchain.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 27, 2019, 12:39:00 PM
One cannot tell the version of sanc other than if you are in control of the server running the sanc? I thought DIP3 the owner and operator could be separate parties. Surely one should be able to verify that information?

Also in the classic, when a sanc was on a different chain or offline, watchman would cause it to appear in a state other than ENABLED.

I still do not know how PoSE works on DIP3 sancs? Previously they were reported enabled when the servers were off. Then they began to be PoSE banned even though as far as i could tell they were on the same chain. Now even though the 2 sancs were clearly on a different chain, they appeared ENABLED when checked from the sanc on the main testchain.



"One cannot tell the version of sanc other than if you are in control of the server running the sanc? I thought DIP3 the owner and operator could be separate parties. Surely one should be able to verify that information?"
-> No, the only info available to a deterministic viewer, are the fields in 'masternode status' that you see on your own sanc.  Governance protoversion is not one.

Also in the classic, when a sanc was on a different chain or offline, watchman would cause it to appear in a state other than ENABLED.

->  Yes, classic version used pings, and each node kept track of its own status, but in DM, they do not use pings, so all of those fields have been removed.

I still do not know how PoSE works on DIP3 sancs? Previously they were reported enabled when the servers were off. Then they began to be PoSE banned even though as far as i could tell they were on the same chain. Now even though the 2 sancs were clearly on a different chain, they appeared ENABLED when checked from the sanc on the main testchain.

->  You can be POSE banned in DM whether on the right chain or not, as now, POSE works by checking to see if your BLS key signed the current rounds quorum.   So imagine if us three create a secret club, with a seed number, only us 3 can sign with the BLS key and only the insiders will succeed in continuing that quorum for chainlocks.  So POSE is saying:  I will not ban you if you can continue creating good quorums, one per frequency (I think these are roughly one per hour, actually there are 3 frequencies, but for all intents and purposes its about every 7 blocks).

Yeah, I checked also and we cant ban by proto version, but we can kick the sanc out of the quorum, and also offline if they dont have the min protoversion so Im going to go to this method next.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 27, 2019, 01:42:12 PM
1.4.8.2 - BiblePay
Mandatory Upgrade for TestNet


- Add Checkpoint at 18610, bump up min_governance_proto_version to 70749, set IX confirms required to 1
- Set GRC Req Researcher coin age to ^1.6, and BBP ^1.3, and reject other teams from the GSC
- During cold boot, reassess chains if necessary, and, during GSC checks (this is after a bad block is received, but no more than once per hour)
- Change the GSC block rejection rule to freeze the network for up to 8 hours if the GSC is not being generated (this keeps forks from forming, and also makes it more lkely to pay all DWSs).
- Remove the monthly superblock from the daily GSC rejection rule
- Remove Log Spam
- Do not reject IX autolock block failures unless the IX block filter is on and the autolocks are on
- Change the DM snapshot size to 205 (BBPs daily block size)

** Ready **


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: talisman on November 28, 2019, 07:58:29 AM
I see one more change that is to be in the next version is increasing the GRC exponent requirement:
https://forum.biblepay.org/index.php?topic=476.new#new

Do we have any volunteer that wants to switch over to team Gridcoin, so we can test the coin-age-requirement is correct in the next version?

I am in with a Gridcoin account. Exponent seems to be working. Here is the output of exec rac:

"Command": "rac",
  "cpid": "82e63a509a38e2201f08c819457df57f",
  "CPK": "ybf862FujX5RZ2G3ENTzNmywA58xkHjL3m",
  "wcg_teamid": 30513,
  "next_podc_gsc_transmission": 18757,
  "team_name": "Gridcoin",
  "researcher_nickname": "amygdala",
  "total_wcg_boinc_credit": 57690.09,
  "total_wcg_points": 403830.63,
  "external_purse_total_coin_age": 0,
  "coin_age_percent_required": 0,
  "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count.  (See current depth in coin control).",
  "coin_age_required": 286924.2504116587,
  "wcg_id": 1027347,
  "rac": 2576.941353
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 28, 2019, 09:35:35 AM
I am in with a Gridcoin account. Exponent seems to be working. Here is the output of exec rac:

"Command": "rac",
  "cpid": "82e63a509a38e2201f08c819457df57f",
  "CPK": "ybf862FujX5RZ2G3ENTzNmywA58xkHjL3m",
  "wcg_teamid": 30513,
  "next_podc_gsc_transmission": 18757,
  "team_name": "Gridcoin",
  "researcher_nickname": "amygdala",
  "total_wcg_boinc_credit": 57690.09,
  "total_wcg_points": 403830.63,
  "external_purse_total_coin_age": 0,
  "coin_age_percent_required": 0,
  "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count.  (See current depth in coin control).",
  "coin_age_required": 286924.2504116587,
  "wcg_id": 1027347,
  "rac": 2576.941353

Thank you sir,

Do you need any extra tBBP for more testing?
EDIT: I sent you 3 mil.




Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: talisman on November 28, 2019, 10:14:39 AM
Thanks for the funds, Rob ! Otherwise I would have to mine for a couple of days while testing the minimum coinage requirements for a reward  ;D

Do I have to send a manual PODCupdate to show up in the leaderboard?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 28, 2019, 10:52:42 AM
Thanks for the funds, Rob ! Otherwise I would have to mine for a couple of days while testing the minimum coinage requirements for a reward  ;D

Do I have to send a manual PODCupdate to show up in the leaderboard?
Sure, and I will reply asap to the message btw.

On appearing in the leaderboard, the researcher will appear about 5 blocks after a PODC transmission is made; but now the way it works is, if you type exec rac, note how it says 18757 is the next wcg transmission (Fixed), add 205 to that, thats when the wallet sends out the PODC transmission automatically.  But, you will have to see if exec rac shows that you have the coin*age. 

So same issue, if you manually type 'sendgscc wcg' now, the coin age will not be sufficient (until you let it grow a little more).  You know we should also tell the user that (duh) upon manually completing that command.  EDIT:  Ok, the next version will actually give you a reply if you don't have enough coin-age, with a warning, explaining that the RAC may be reduced resulting in a lower reward. 

EDIT: But btw, when a user stakes insufficient collateral, we do reverse engineer it down to the amount staked, and lower the leaderboard RAC, so if you want to try now, you can then look at the leaderboard and see a reduced RAC.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: talisman on November 28, 2019, 12:15:43 PM
Sure, and I will reply asap to the message btw.

On appearing in the leaderboard, the researcher will appear about 5 blocks after a PODC transmission is made; but now the way it works is, if you type exec rac, note how it says 18757 is the next wcg transmission (Fixed), add 205 to that, thats when the wallet sends out the PODC transmission automatically.  But, you will have to see if exec rac shows that you have the coin*age. 

So same issue, if you manually type 'sendgscc wcg' now, the coin age will not be sufficient (until you let it grow a little more).  You know we should also tell the user that (duh) upon manually completing that command.  EDIT:  Ok, the next version will actually give you a reply if you don't have enough coin-age, with a warning, explaining that the RAC may be reduced resulting in a lower reward. 

EDIT: But btw, when a user stakes insufficient collateral, we do reverse engineer it down to the amount staked, and lower the leaderboard RAC, so if you want to try now, you can then look at the leaderboard and see a reduced RAC.

OK, sent a GSC transmission. Required coin-age was 324.976, and I had 200.833. Let's see how it rolls out.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 28, 2019, 11:07:27 PM
couldn't the wallet version be enough to ban sanctuaries not on that version as well?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 29, 2019, 10:28:04 AM
couldn't the wallet version be enough to ban sanctuaries not on that version as well?
No, actually, in dashcore, we know both the governance protocol version and the wallet version.
So, no that wont work either.

But I believe the last release did fix it.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 29, 2019, 10:28:39 AM
OK, sent a GSC transmission. Required coin-age was 324.976, and I had 200.833. Let's see how it rolls out.

Yeah, I saw yesterday you did have reduced RAC.  1 point in the leaderboard equals 1 rac currently.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 29, 2019, 07:02:33 PM
i'm giving up. I can't get my cpid registered. tried several times now.


exec rac works but haven't gotten a podc payments for days now.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 29, 2019, 07:11:10 PM
i'm giving up. I can't get my cpid registered. tried several times now.


exec rac works but haven't gotten a podc payments for days now.
I will need the full exec associate command you typed so I can reproduce.  Unless you are saying your 'exec associate' was successful days ago, then I only need your CPK and CPID.

And also your CPK and CPID would be helpful.

EDIT:  And also if you successfully performed exec join wcg and also if you successfully performed exec associate, and also your block # and blockhash currently.

Also, what is the last txid of your WCG GSC transmission?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 29, 2019, 08:33:39 PM
I've been following BiblePay for the last 18 months, but if I'm having a difficulty time getting this work... this does not bode well for new members. Maybe I'm just dumb... Usability is critical, but adding complexity has only made the product more difficult to use.


I DMed you my exec rac output.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 29, 2019, 08:38:42 PM
I've been following BiblePay for the last 18 months, but if I'm having a difficulty time getting this work... this does not bode well for new members. Maybe I'm just dumb... Usability is critical, but adding complexity has only made the product more difficult to use.


I DMed you my exec rac output.

Obviously PODC 2.0 is supposed to be easier to set up than PODC, so I'm not sure how you can come to that conclusion. 

But a non-working PODC transmission does not equal hard-to-use software. 



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 29, 2019, 08:57:45 PM
I've been following BiblePay for the last 18 months, but if I'm having a difficulty time getting this work... this does not bode well for new members. Maybe I'm just dumb... Usability is critical, but adding complexity has only made the product more difficult to use.


I DMed you my exec rac output.
So it looks like you only staked 65 total coin age two days ago (not enough to meet the minimums), then 6 coin age today.

The problem appears to be in your total external purse balance.
(The exec rac for example, shows a 0 total coin age - that is part of the issue).

But more specifically, in this version of BBP, you must load your external purse with funds in order to have enough coin-age built up to send PODC transmissions.

Check your 'CPK' address, and see what total bbp you have in there?

EDIT:  Btw, in the next upcoming version we did add a warning message- when a user manually sends a GSC for WCG, and the wallet detects not enough coin-age, it does throw a WARNING:  Explaining that the rewards were reduced for PODC.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 29, 2019, 09:28:44 PM
If you feel it is easy enough to use, then it must be me. I'll sit out testing as I personally feel all these steps are too hard for me to understand and follow.  :D
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 30, 2019, 07:41:22 AM
If you feel it is easy enough to use, then it must be me. I'll sit out testing as I personally feel all these steps are too hard for me to understand and follow.  :D


It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 30, 2019, 07:44:04 AM

It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.


My biblepay.conf kept saving as Mac format after the externalprivatekey got inserted by the biblepay code. saving it back as windows (crlf) seems to triggered a gsc tramission for cameroon-one, kairos, and wcg as soon as I opened the wallet again.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 08:20:57 AM

My biblepay.conf kept saving as Mac format after the externalprivatekey got inserted by the biblepay code. saving it back as windows (crlf) seems to triggered a gsc tramission for cameroon-one, kairos, and wcg as soon as I opened the wallet again.

I don't think there is a Mac format; we have linux and windows file formats; To my knowledge MAC has migrated to the linux format; MIP has confirmed this is working.

Please work with MIP on this.  He's staking collateral successfully.

Edit:  Obviously the purse must be working because you sent out collateral before.  Can you please paste the output of 'exec boinc1'?  This tests the purse.  I think you are reading too much into the purse, and making an assumption.  Don't spend any time on the assumption, just paste exec boinc1 and we will go from there.  Macs file writing format works fine.

Btw, we no longer trigger sendgsc when the wallet opens.  Its only sent at the height shown in 'exec rac'.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 08:52:23 AM

It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.

In PODC 2.0, it is the users responsibility to maintain sufficient staking collateral inside the "Christian-Public-Key" address. 

So here is the easiest way to check that:

- Check and see if you are in the leaderboard 5 blocks after you send a WCG GSC
- If not, check your CPK balance.  It should have about 10 bills in it (to ensure small breakable bills exist for Cameroon one and Kairos), and it should have sufficient balance of coin-age (shown in exec rac).

I will now add more warnings to 'exec rac' to make this a little more apparent.

1) You can see your balance in Coin Control (associated with Christian Public Key), and you can see the external purse balance in 'exec rac'
2) You can make banknotes with 'exec bankroll'.  These now get paid back to the CPK, so these are PODC 2.0 friendly.
3) You can see if you are in the leaderboard a few blocks after a GSC is sent.  If not, something is wrong.

In the next version, as I stated earlier, the 'sendgscc wcg' does throw a warning if the user didnt have enough coin-age.





Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 30, 2019, 08:57:39 AM
Code: [Select]
{
  "Command": "rac",
  "cpid": "xxx",
  "CPK": "xxx",
  "wcg_teamid": 30513,
  "next_podc_gsc_transmission": 19167,
  "team_name": "Gridcoin",
  "researcher_nickname": "xxx",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 509461.35,
  "total_wcg_points": 3566229.45,
  "external_purse_total_coin_age": 6501.996296296297,
  "coin_age_percent_required": 0.99,
  "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count.  (See current depth in coin control).",
  "coin_age_required": 1116115.243997492,
  "wcg_id": xxx,
  "rac": 6023.073319
}

{
  "Command": "rac",
  "cpid": "xxx",
  "CPK": "xxx",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 19167,
  "team_name": "Biblepay",
  "researcher_nickname": "xxx",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 4457712.47,
  "total_wcg_points": 31203987.29,
  "external_purse_total_coin_age": 5410402.656666667,
  "coin_age_percent_required": 0.03766507675813258,
  "coin_age_required": 149679.2047890878,
  "wcg_id": xxx,
  "rac": 9569.592315
}

TEAM           RAC       COINAGE REQD     RATIO
GRIDCOIN   6,023     1,116,115               19.2x
BIBLEPAY    9,569         149,679               15.6x
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 30, 2019, 09:02:06 AM
Code: [Select]
{
  "Command": "rac",
  "cpid": "xxx",
  "CPK": "xxx",
  "wcg_teamid": 30513,
  "next_podc_gsc_transmission": 19167,
  "team_name": "Gridcoin",
  "researcher_nickname": "xxx",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 509461.35,
  "total_wcg_points": 3566229.45,
  "external_purse_total_coin_age": 6501.996296296297,
  "coin_age_percent_required": 0.99,
  "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count.  (See current depth in coin control).",
  "coin_age_required": 1116115.243997492,
  "wcg_id": xxx,
  "rac": 6023.073319
}

{
  "Command": "rac",
  "cpid": "xxx",
  "CPK": "xxx",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 19167,
  "team_name": "Biblepay",
  "researcher_nickname": "xxx",
  "researcher_country": "CANADA",
  "total_wcg_boinc_credit": 4457712.47,
  "total_wcg_points": 31203987.29,
  "external_purse_total_coin_age": 5410402.656666667,
  "coin_age_percent_required": 0.03766507675813258,
  "coin_age_required": 149679.2047890878,
  "wcg_id": xxx,
  "rac": 9569.592315
}

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

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
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 09:03:59 AM
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

Very impressive!

Yes this looks like it matches what we would expect too!

Could you please keep us informed to tell us how well the Gridcoin CPID works out?  IE that its RAC gets reduced today but you still enter the leaderboard and then if you ultimately get paid?

Thanks!

EDIT:  Also, when you reboot your sancs on the new version, could you please tell me if they sync right up to the top block?

Let me post a hash:

getblockhash 19180
a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616b

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 09:14:40 AM
And just so everyone knows that progress is not stalling in testnet, the only two or three changes for the next version are cosmetic helpful hints-  so we are in no hurry to make another release (until we either find a bug or merge something else in).  In testing my unbanked CPID, it does have a minor bug - but that can also wait until the next release.

However one very, very important endeavor I wanted to mention that we need to schedule very soon is testing this 0.14 TestNet branch against prod.  I realize we did mine against prod a long time ago, and that worked until we found we forked after a GSC block.  On that endeavor, heres what we need to do:  Since this branch will only communicate with deterministic and higher version sancs, we need to actually release a patch for MainNet, and one of our guinea pigs (IE : ME), will upgrade 10 sancs to that version.  Then we will circle back and test TestNet against prod and verify we mine again and do not fork through the GSC block.  We'll do that very very soon, but please wait until I give the OK that the code is released in mainnet, etc.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 30, 2019, 09:42:15 AM
Very impressive!

Yes this looks like it matches what we would expect too!

Could you please keep us informed to tell us how well the Gridcoin CPID works out?  IE that its RAC gets reduced today but you still enter the leaderboard and then if you ultimately get paid?

Thanks!

EDIT:  Also, when you reboot your sancs on the new version, could you please tell me if they sync right up to the top block?

Let me post a hash:

getblockhash 19180
a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616b

Sorry, I had trouble with the re-syncing of two of those sancs following the recent upgrade. I had to delete the whole biblepay-evolution folder suggesting that there was some issue with the compilation which allowed me to start the wallet but somehow failed to sync after days... I have now just used the pre-compiled binaries and it is working fine as all of my testnet servers are at the top of the chain and can confirm your hash.

>cli getblockhash 19180
a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616b

Since one of those wallets that would not sync was my controlling wallet, I could not perform an update_service to the POSE_BANNED sancs which I have now done and as far as I can see all 7 sancs on testnet are ENABLED.

>list status
{
  "a46074dac98333269341fee5b712f795fdeaa615b276fee12175e1c537ce8a43-1": "ENABLED",
  "efbe80743321967f9d94b124b6670e3d87492e711f34acbe6fdada608007e055-0": "ENABLED",
  "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583-1": "ENABLED",
  "7570652f63502f29b610c4bf134f3d1d589c970c383b20a88545cd683c802130-1": "ENABLED",
  "7c30c4cf73a81ce8ebb90b3cd6bcda3c279d86fb044605b3f95f75a1657cd19e-1": "ENABLED",
  "c49f6f1e8fc8829b048abc37e790f4d6fc6364e05b9c433b77838ba575c15477-0": "ENABLED",
  "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": "ENABLED"
}

Finally, the Gridcoin RAC has been accumulating similarly to Biblepay RAC since the start of testnet PODCv2. I just noticed the higher coinage requirement and lower points on the leaderboard with the recent spork to add a higher requirement to gridcoin team members.

 





Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 30, 2019, 09:42:36 AM



07:40:41

exec boinc1




07:40:41

{
  "Command": "boinc1",
  "purse amount matched": 599938.99127,
  "purse total": 645074.51811888,
  "txid": "b52b5a341e644a68823e3076b68b918325e11a9cb0e7ae3dfa795bef8a676e5a"
}

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 30, 2019, 09:47:51 AM
I don't think there is a Mac format; we have linux and windows file formats; To my knowledge MAC has migrated to the linux format; MIP has confirmed this is working.

Please work with MIP on this.  He's staking collateral successfully.

Edit:  Obviously the purse must be working because you sent out collateral before.  Can you please paste the output of 'exec boinc1'?  This tests the purse.  I think you are reading too much into the purse, and making an assumption.  Don't spend any time on the assumption, just paste exec boinc1 and we will go from there.  Macs file writing format works fine.

Btw, we no longer trigger sendgsc when the wallet opens.  Its only sent at the height shown in 'exec rac'.


biblepay.conf is in Mac format according to Notepad++. This is on my Windows 10 64-bit Home edition.


I can send you the file after I do exec createpurse.


the line ending is 0d0d0a instead of 0d0a . I think I mentioned this in the github. I didn't mention it because it didn't seem relevant, but if wallet is not reading biblepay.conf that creates all sorts of Issues I noticed in the past.


(https://i.imgur.com/kmWbADP.jpg)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 09:51:48 AM
Sorry, I had trouble with the re-syncing of two of those sancs following the recent upgrade. I had to delete the whole biblepay-evolution folder suggesting that there was some issue with the compilation which allowed me to start the wallet but somehow failed to sync after days... I have now just used the pre-compiled binaries and it is working fine as all of my testnet servers are at the top of the chain and can confirm your hash.

>cli getblockhash 19180
a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616b

Since one of those wallets that would not sync was my controlling wallet, I could not perform an update_service to the POSE_BANNED sancs which I have now done and as far as I can see all 7 sancs on testnet are ENABLED.

>list status
{
  "a46074dac98333269341fee5b712f795fdeaa615b276fee12175e1c537ce8a43-1": "ENABLED",
  "efbe80743321967f9d94b124b6670e3d87492e711f34acbe6fdada608007e055-0": "ENABLED",
  "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583-1": "ENABLED",
  "7570652f63502f29b610c4bf134f3d1d589c970c383b20a88545cd683c802130-1": "ENABLED",
  "7c30c4cf73a81ce8ebb90b3cd6bcda3c279d86fb044605b3f95f75a1657cd19e-1": "ENABLED",
  "c49f6f1e8fc8829b048abc37e790f4d6fc6364e05b9c433b77838ba575c15477-0": "ENABLED",
  "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": "ENABLED"
}

Finally, the Gridcoin RAC has been accumulating similarly to Biblepay RAC since the start of testnet PODCv2. I just noticed the higher coinage requirement and lower points on the leaderboard with the recent spork to add a higher requirement to gridcoin team members.


Ok, good overall I suppose.  Thats great that GRC's points are showing in the leaderboard; just please let us know if it follows through with a payment too.  I assume it will.

On this sanctuary compile debacle, I have a hypothesis on that, because I have a similar problem compiling on my low end boxes.  I have a couple low-end for testnet and they are so low end they sometimes cant even finish the compile.  I can say this with certainty:  If cc1plus gets killed in the middle of a compile due to lack of ram, many times, the binary will already have the higher protocol version and the lower code (which is absolutely bad when you run it).  The way I personally had to solve this is make a compile script with 'cpulimit -l 45' (or something to that effect, if you want it I can post it) and it causes the compile to finish without getting killed.  Try that next time with a make clean first.  After that Ive had much better luck running it and leaving and then it starts back up successfully.

EDIT:  Just to clarify though, when I post a release the code is the latest; so it sounds like it *was* a compile issue.  (MIP then builds the linux binaries after the release is posted here).

EDIT2:  Starting with the last version, you can use -erasechain=1 again (we now delete all the files including instantsend.dat).  But, you shouldnt have to, unless we have a fork, and thats what we are trying to certify we dont have any more.  For example after this last release I did not erase my chain I just restarted the client.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 30, 2019, 09:52:25 AM
Ideally, I'd like to just do an exec associate user verification code and that's all I need to do to join podc 2.0.


i prefer everything else is done for me (create cpk, joining wcg, etc) and it sends out the daily podc update as long I have the wallet running.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 09:55:11 AM

biblepay.conf is in Mac format according to Notepad++. This is on my Windows 10 64-bit Home edition.


I can send you the file after I do exec createpurse.


the line ending is 0d0d0a instead of 0d0a . I think I mentioned this in the github. I didn't mention it because it didn't seem relevant, but if wallet is not reading biblepay.conf that creates all sorts of Issues I noticed in the past.


(https://i.imgur.com/kmWbADP.jpg)

I already posted my reply about this. 

Lets not spend more time on this or make assumptions.

Do the following:

Start a new wallet
Type 'exec createpurse'
Type 'exec boinc1' and paste the output.


Your current wallet is already successful.  Try with a new one - and do not manually edit the biblepay.conf file this time.

Do not paste third party representations of the data for the test.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 30, 2019, 10:13:27 AM
nevermind, I'm out of testing. This is no way to treat your testers.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 10:19:55 AM
nevermind, I'm out of testing. This is no way to treat your testers.

Just to clarify though Sun, you have been entering tickets in github with a lot of issues that have taken a siginficant amount of time, and some ended up turning into non issues.  MIP and I have taken a look at this and already explained that there is no "Mac" format and his external purse collateral works fine on his macs.

You should be more respectful of our time.  I only asked for a regimented test because we have spent a considerable amount of time on these things in total.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on November 30, 2019, 11:25:28 AM

Just to clarify though Sun, you have been entering tickets in github with a lot of issues that have taken a significant [sic] amount of time that always ended up turning into non issues.  MIP and I have taken a look at this and already explained that there is no "Mac" format and his external purse collateral works fine on his macs.


You should be more respectful of our time.  I only asked for a regimented test because we have spent a considerable amount of time on these things in total.


I will admit some posted issues have been duds. We can't be 100%  ;D  all the time -- only Jesus. If you feel some issues are not worth investigating, then it is your job to prioritize or ignore them. I hope you can appreciate just how many issues don't reach you because many of us address it before it gets to you.


> always ended up turning into non issues.


Why would say "always". That sounds very dismissive of my contributions. I got tired so I had to stop before finishing...


Here are some issues I posted in the past that required fixing...


GSC Transmission for CameroonONE occurs even with -1
https://github.com/biblepay/biblepay-evolution/issues/26


One Click Mining Configuration corrupts biblepay.conf
https://github.com/biblepay/biblepay-evolution/issues/21


InstantSend not working - always confirms to 1 of 6
https://github.com/biblepay/biblepay-evolution/issues/17


Superblock Payment shows matured but requires 102 confirmations
https://github.com/biblepay/biblepay-evolution/issues/10


Runaway exception: bad lexical cast: source type value could not be interpreted as target
https://github.com/biblepay/biblepay/issues/102


One Click Miner Configuration writes tithing=1 instead of tithe=1
https://github.com/biblepay/biblepay/pull/87


exec bankroll: Signing transaction failed on locked wallet
https://github.com/biblepay/biblepay/issues/83


Invalid-tithe found from address xxx for amount of xxx
https://github.com/biblepay/biblepay/issues/81


Unable to mine... Cant sign block template with CPID - Error
https://github.com/biblepay/biblepay/issues/80


The auto-tithe feature was only tithing 90%.
https://github.com/biblepay/biblepay/issues/78


viewing PoG leaderboard causes crash if syncing blockchain <100k (pre-PoG)
https://github.com/biblepay/biblepay/issues/74


PoG Leaderboard - right click View makes QT wallet gets stuck
https://github.com/biblepay/biblepay/issues/73


PoG continues to auto tithe even though daily ~50k BBP donation was exceeded
https://github.com/biblepay/biblepay/issues/71


PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.
https://github.com/biblepay/biblepay/issues/70


PoG Leadboard does show up in production
https://github.com/biblepay/biblepay/issues/67


1.1.5.4: InstantSend error: InstantSend doesn't support sending values that high yet.
https://github.com/biblepay/biblepay/issues/44
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 12:09:32 PM

I will admit some posted issues have been duds. We can't be 100%  ;D  all the time -- only Jesus. If you feel some issues are not worth investigating, then it is your job to prioritize or ignore them. I hope you can appreciate just how many issues don't reach you because many of us address it before it gets to you.


> always ended up turning into non issues.


Why would say "always". That sounds very dismissive of my contributions. I got tired so I had to stop before finishing...


Here are some issues I posted in the past that required fixing...


GSC Transmission for CameroonONE occurs even with -1
https://github.com/biblepay/biblepay-evolution/issues/26


One Click Mining Configuration corrupts biblepay.conf
https://github.com/biblepay/biblepay-evolution/issues/21


InstantSend not working - always confirms to 1 of 6
https://github.com/biblepay/biblepay-evolution/issues/17


Superblock Payment shows matured but requires 102 confirmations
https://github.com/biblepay/biblepay-evolution/issues/10


Runaway exception: bad lexical cast: source type value could not be interpreted as target
https://github.com/biblepay/biblepay/issues/102


One Click Miner Configuration writes tithing=1 instead of tithe=1
https://github.com/biblepay/biblepay/pull/87


exec bankroll: Signing transaction failed on locked wallet
https://github.com/biblepay/biblepay/issues/83


Invalid-tithe found from address xxx for amount of xxx
https://github.com/biblepay/biblepay/issues/81


Unable to mine... Cant sign block template with CPID - Error
https://github.com/biblepay/biblepay/issues/80


The auto-tithe feature was only tithing 90%.
https://github.com/biblepay/biblepay/issues/78


viewing PoG leaderboard causes crash if syncing blockchain <100k (pre-PoG)
https://github.com/biblepay/biblepay/issues/74


PoG Leaderboard - right click View makes QT wallet gets stuck
https://github.com/biblepay/biblepay/issues/73


PoG continues to auto tithe even though daily ~50k BBP donation was exceeded
https://github.com/biblepay/biblepay/issues/71


PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.
https://github.com/biblepay/biblepay/issues/70


PoG Leadboard does show up in production
https://github.com/biblepay/biblepay/issues/67


1.1.5.4: InstantSend error: InstantSend doesn't support sending values that high yet.
https://github.com/biblepay/biblepay/issues/44


Yes, you are right, sorry, I just read what I wrote and corrected it to say "some".

Sorry, I apologize for coming across with that impression to you.

Actually to clarify, all of your support contributions have been very welcome and helpful in detecting, diagnosing, and solving the bugs we had over the entire duration of BiblePay.

Thank you for what you have already contributed.

Hopefully we will be working together in this endeavor.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on November 30, 2019, 03:13:22 PM
I am trying to sync testnet but I am stuck at block 17444. I see many peers so I don't know how to get it updated.
I will try to rescan and come back when ready
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 03:37:56 PM
I am trying to sync testnet but I am stuck at block 17444. I see many peers so I don't know how to get it updated.
I will try to rescan and come back when ready

Actually if you are on 1.4.8.2, double check that, then delete 'instantsend.dat' and restart, and let us know?

Let me know if it still re-hangs.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on November 30, 2019, 04:08:03 PM
Actually if you are on 1.4.8.2, double check that, then delete 'instantsend.dat' and restart, and let us know?

Let me know if it still re-hangs.

it's the latest version I compiled myself. I tried to delete bnstantsend.dat and rescan but still at 17444.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 04:17:08 PM
it's the latest version I compiled myself. I tried to delete bnstantsend.dat and rescan but still at 17444.

Ok, your right, sorry, I did not realize we introduced a bug in the latest version that prevents syncing from zero.

Please stand by for a new leisure upgrade.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on November 30, 2019, 05:01:54 PM
Ok, your right, sorry, I did not realize we introduced a bug in the latest version that prevents syncing from zero.

Please stand by for a new leisure upgrade.

new version synced ok in my mac.

What can I test?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 05:24:41 PM
BiblePay
1.4.8.3 - Leisure Upgrade for TestNet

- Fix bug preventing syncing from 0
- Fix 'exec rac' PODC transmission height
- Enhance 'exec sentgsc' to allow a CPK parameter to audit sent gscs by CPK
- Fix bug ensuring that unbanked cpids are included in the GSC
- Add warning when user executes sendgscc, if coin-age is low, that PODC rewards will be reduced.  Also add a warning to exec rac.

** This is the windows & self-compiled release **

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on November 30, 2019, 05:28:32 PM
new version synced ok in my mac.

What can I test?

You can test the test cases in post #2.  Except, we don't need to test Cameroon-One or Kairos at this time (as Kairos is integrating now and expirimenting on their server).  We also don't need an extra sanc right now since we appear to have 7 going, but do monitor the situation if we get down to 3 again.

We primarily need to test PODC 2.0 and DWS.

I'll update when we are ready to test this branch against Prod; its not ready yet.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on November 30, 2019, 09:09:26 PM
Yes, you are right, sorry, I just read what I wrote and corrected it to say "some".

Sorry, I apologize for coming across with that impression to you.

Actually to clarify, all of your support contributions have been very welcome and helpful in detecting, diagnosing, and solving the bugs we had over the entire duration of BiblePay.

Thank you for what you have already contributed.

Hopefully we will be working together in this endeavor.

I second what Rob said: your contributions are appreciated and acknowledged, Sunk And I am very happy that we will *all* be working together in bringing glory to our Lord and Saviour, Jesus Christ.




Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on December 01, 2019, 01:58:37 PM
BiblePay
1.4.8.3 - Leisure Upgrade for TestNet

- Fix bug preventing syncing from 0
- Fix 'exec rac' PODC transmission height
- Enhance 'exec sentgsc' to allow a CPK parameter to audit sent gscs by CPK
- Fix bug ensuring that unbanked cpids are included in the GSC
- Add warning when user executes sendgscc, if coin-age is low, that PODC rewards will be reduced.  Also add a warning to exec rac .

** This is the windows & self-compiled release **

Testnet MacOS and Linux binaries also available

So far I could associate the user and everything went smoothly

I will wait for some blocks to run exec rac and post results
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 02, 2019, 01:21:18 PM
What is the correct chain?

I have 3 nodes on block 19600

getblockhash 19600
cc6e4******137806

I kept trying to get another node to sync up to that, but it kept syncing to block 17444 or so,
even when I deleted everything in the data folder twice, and did addnodes for oncoapops IPs
https://oncoapop.sdf.org/biblepaytest/testnet_chainstate.shtml

Ill try again
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 02, 2019, 02:43:42 PM
Happened again, only got to block 17444
Im updating to v1.4.8.3
Ok that worked, Im synced up now!
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 02:47:12 PM
Happened again, only got to block 17444
Im updating to v1.4.8.3
Ok that worked, Im synced up now!

Yeah, 1.4.8.2 didnt support syncing from 0, but 1.4.8.3 does.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 03:11:44 PM
Happened again, only got to block 17444
Im updating to v1.4.8.3
Ok that worked, Im synced up now!

Btw, did you get paid for the Kanye proposal?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 02, 2019, 03:26:38 PM
I do not believe I received the Kanye proposal funding,
I just created another proposal, should show up soon

===

All 3 nodes are running PrivateSend now

Im seeing this, havent seen any mixing yet:
https://i.imgur.com/FXI92Y3.png
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 02, 2019, 04:38:26 PM
Im testing Dynamic Whale Staking, I just ran:

Code: [Select]
exec dws 100000 3 I_AGREE yXfpgvjvNJ5aURRQ6porVHSPJzWdiWvk9i
The DWU is 91.1005, does that mean I multiple by 1.0911005 to calculate what I will receive back?

DWS Reference: https://forum.biblepay.org/index.php?topic=468.0

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 02, 2019, 04:38:57 PM
I do not believe I received the Kanye proposal funding,
I just created another proposal, should show up soon

===

All 3 nodes are running PrivateSend now

Im seeing this, havent seen any mixing yet:
https://i.imgur.com/FXI92Y3.png (https://i.imgur.com/FXI92Y3.png)


I think we should get rid of PrivateSend. Who uses PrivateSend besides you? If many of the BBP features are based on coin age, PrivateSend mixing conflicts with those features (e.g. PoDC 2.0, Healing, PoG/Dynamic Whale Staking). How much development and support time is spent on this feature while the percentage of use is extremely low? If God knows everything we do, what do we need to keep private/obfuscated on the blockchain?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 02, 2019, 05:16:31 PM
I do not believe I received the Kanye proposal funding,
I just created another proposal, should show up soon

I believe I was looking at the wrong wallet,
I see that I received 1 million BBP at address: yVqyMZPPUw6JrASEgfWsRns7rDkRQFQbVF
on 11/28/19 00:20, Height: 18655
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 06:26:26 PM
I believe I was looking at the wrong wallet,
I see that I received 1 million BBP at address: yVqyMZPPUw6JrASEgfWsRns7rDkRQFQbVF
on 11/28/19 00:20, Height: 18655

Good, thats the one I reentered.  Im fairly certain Watchman is working, because it is the same code ported over from prod.
So Im relatively sure superblocks are going to work.

Ill enter another extra proposal now.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 06:33:34 PM
Im testing Dynamic Whale Staking, I just ran:

Code: [Select]
exec dws 100000 3 I_AGREE yXfpgvjvNJ5aURRQ6porVHSPJzWdiWvk9i
The DWU is 91.1005, does that mean I multiple by 1.0911005 to calculate what I will receive back?

DWS Reference: https://forum.biblepay.org/index.php?topic=468.0

So just to clarify, we use Dynamic Whale Units so as to not make any promise of a return in standard banking terms, IE this is more of a staking term.
Another thing to clarify, note that if the screen quote (from exec dws) shows DWU 95 for 30 days), your actual DWU (of 91.1005 above) is based on '3 days' and that is derived from the 30 day duration (we get less DWU for shorter burns, more DWU for longer, and even much more as you can see for locking up for 365 days). 

So to calculate the stake reward you can multiply .911005 * original burn divided by 365 (annualize it) * the duration in days, and that is the Dynamic whale reward amount (plus the original burn amount).

Also you can type 'exec dwsquote 1 1' to see your own burns, with details containing the future maturity date and total calculated amount.


Hey guys, lets test at least 10 burns each if possible, put in an easy to use suffix on the amount like '10001.10' '10002.20' or whatever you prefer and you will easily see you get back 10 in the future- i recommend doing shorter terms because we only have 15 more days of testing left.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 02, 2019, 06:37:58 PM
Thank you for explaining DWS Rob, I think its a cool feature (I like HEX coin)

I think I got confused from this example on the DWS proposal thread:
https://forum.biblepay.org/index.php?topic=468.0

Quote
getdwsquote
Amount staked: 1,000,000
Dynamic-whale-unit reward: 15
This means the user would potentially receive 15000 bbp in reward one year after the coins are burned.

15,000 should be 150,000?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 06:42:26 PM
I do not believe I received the Kanye proposal funding,
I just created another proposal, should show up soon

===

All 3 nodes are running PrivateSend now

Im seeing this, havent seen any mixing yet:
https://i.imgur.com/FXI92Y3.png

Well on a side note I do recommend using a dedicated wallet for mixing; we definitely should not ask the user to intermingle the CPK PODC wallet with the PS inputs/outputs as I think that will just be asking for trouble.  If you could please test this in a wallet that you are not testing the 'exec rac' on that would be very helpful.

I think your PS might be working now; its showing that out of the 7 nodes, 3 are willing to mix.
That means if you let it run for a while (try the command line, privatesend start)?  see if it mixes over night.
We increased the denoms by 100* so it should consume less bills now.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 06:46:03 PM
Thank you for explaining DWS Rob, I think its a cool feature (I like HEX coin)

I think I got confused from this example on the DWS proposal thread:
https://forum.biblepay.org/index.php?topic=468.0

15,000 should be 150,000?
Oh sorry, your exactly right - it should have been 150K.  I edited it in 2 places just now.

Is HEX very similar to this feature?  And did they also make it staking so they can be howy compliant?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 02, 2019, 06:59:35 PM
This is HEX telegram bot response to howey:
https://pastebin.com/h7k9PM4A

Theyre about to launch pretty soon, was supposed to go live already an hour ago,
I plan to put $150 of Ethereum into it today, and then sign (prove) I own Bitcoin tomorrow,
and then I plan to stake the coins for 6 years LOL

I dont mean to advertise, and I have no idea if it will go up in value,
but Im a fan of Richard Hearts youtube videos,
even though he can be a bit harsh and I disagree with him on some things,
(before this he really wanted to make a science coin and then gave up b/c it was too hard,
I think he put a good amount of time into it, it was called CFD token (CFD for Computational Fluid Dynamics))
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 07:18:17 PM
Testnet MacOS and Linux binaries also available

So far I could associate the user and everything went smoothly

I will wait for some blocks to run exec rac and post results

Ok good, and btw, we can use help with DWS also.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 02, 2019, 07:24:16 PM
This is HEX telegram bot response to howey:
https://pastebin.com/h7k9PM4A

Theyre about to launch pretty soon, was supposed to go live already an hour ago,
I plan to put $150 of Ethereum into it today, and then sign (prove) I own Bitcoin tomorrow,
and then I plan to stake the coins for 6 years LOL

I dont mean to advertise, and I have no idea if it will go up in value,
but Im a fan of Richard Hearts youtube videos,
even though he can be a bit harsh and I disagree with him on some things,
(before this he really wanted to make a science coin and then gave up b/c it was too hard,
I think he put a good amount of time into it, it was called CFD token (CFD for Computational Fluid Dynamics))

Its fascinating how close the feature is to his description coming from absolutely unknown perspectives from each other.
Ours purely was born out of the desire to attract more new users (plus an e-mail that same night from coinbase: we are now offering a return-staking-reward on POS balances held at coinbase) and I was thinking you know we should make this based on burns (purely because that would make it hassle free).  Its also interesting how the Howey ended up relatively similar - of course that makes sense based on what expectations you are making clear the user should not expect.

Cool well good luck with the investment; I hope for an expanding market share with no slowing down.

Ill have to watch his youtube video, he looks a little familiar to me.



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on December 03, 2019, 09:05:42 AM
Tested PoDC during a couple of days and

- GSC transmission working fine
- PoDC reward received correctly.

I will test DWS now
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 04, 2019, 09:26:24 AM

Stays unconfirmed in the QT wallet. Can't abandon. I have to Wallet Repair, Recover Transactions 1 to remove it.


2019-12-04 15:22:12
VerifyDynamicWhaleStake ACCEPTED :  Amount 100000.000000, Duration 1, SatPercentAnnual 0.008545, SatPercentMonthly 0.090695, Projected DWU 1.818611, Burn DWU 1.818600GUI: Platform customization: "windows"

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 04, 2019, 10:43:28 AM
Stays unconfirmed in the QT wallet. Can't abandon. I have to Wallet Repair, Recover Transactions 1 to remove it.


2019-12-04 15:22:12
VerifyDynamicWhaleStake ACCEPTED :  Amount 100000.000000, Duration 1, SatPercentAnnual 0.008545, SatPercentMonthly 0.090695, Projected DWU 1.818611, Burn DWU 1.818600GUI: Platform customization: "windows"
What is the TXID?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 04, 2019, 04:57:18 PM
What is the TXID?


Sorry, like I said, I removed the TX. If I run into again, I'll relay it.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 05, 2019, 09:12:26 AM

Sorry, like I said, I removed the TX. If I run into again, I'll relay it.

How many did you successfully test before that?  Were you inserting a lot of DWS inside the same block, or trying to break it, or what lead up to the failed DWS transaction exactly?

Most likely you were able to get it transmitted locally because it passed all checks at that very second, but the other nodes on the network didnt like it (due to it being out of bounds by a certain parameter).  Once we have a future txid, I can tell you what the parameter was.

But after looking at the code, I dont see any flaws the way it is.  We do check the transaction before accepting it now, so it is not a matter of becoming an orphan because of the biblepay validator.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 05, 2019, 08:36:26 PM
Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00821000 tBBP
Net amount: -11 000.00821000 tBBP
Transaction ID: c76dc628ab85cd1eefea170d649bb92aabf085c2a12b84b9d34a25518e6ec05c
Output index: 1
Transaction total size: 821 bytes

Code: [Select]
Debit: -3767.05326650 tBBP
Debit: -3773.29547908 tBBP
Debit: -5065.13451406 tBBP
Credit: 1605.47504964 tBBP
To: yLdnz7dQxUZCpcX1Z9bcBbFz2QBRQgMGZn 1605.0000 BBP

Transaction:
CTransaction(hash=c76dc628ab, ver=1, type=0, vin.size=3, vout.size=2, nLockTime=20102, vExtraPayload.size=0)
    CTxIn(COutPoint(7a4804ef0b14b94c37ca5083dc1675ef3c0d11637282529850c50263e2bc8202, 0), scriptSig=483045022100bde976efea0e, nSequence=4294967294)
    CTxIn(COutPoint(bde5dba4fc908e2fe106e5e5040dc213fae425b243a617f0ef6c793c220a2ebc, 0), scriptSig=483045022100a770d7458985, nSequence=4294967294)
    CTxIn(COutPoint(c241737398b8becad573bb9887cc659f3705ec684c24ff134e30bba034ef2668, 10), scriptSig=483045022100ffea81996b77, nSequence=4294967294)
    CTxOut(nValue=1605.47504964, scriptPubKey=76a91403784bdd3a4cf73272b0bcf3)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)

DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294901.8160312-08-2019 07:04:5011000.00





Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00821000 tBBP
Net amount: -11 000.00821000 tBBP
Transaction ID: ab6b451724d48b7204ccd5eedad550c2548fac764450f840e8ad14ac28e96a85
Output index: 1
Transaction total size: 819 bytes


Debit: -3779.16221232 tBBP
Debit: -5707.10526530 tBBP
Debit: -3780.86439835 tBBP
Credit: 2267.12366597 tBBP
To: yQzXVa2uKZf1ZvhPnf2WEmPVh9Lx3Q8YYY 2267.0000 BBP

Transaction:
CTransaction(hash=ab6b451724, ver=1, type=0, vin.size=3, vout.size=2, nLockTime=20043, vExtraPayload.size=0)
    CTxIn(COutPoint(34a9e058211f4b6b722b4d26ed096b2dcdcff482f11a6d75b7f1ae0fa4ae5fed, 0), scriptSig=4730440220199ae942e147ad, nSequence=4294967294)
    CTxIn(COutPoint(5e0a114a3c01706e76f06f8fb80557323b0b8af25f519585d00ab40afaf954d1, 10), scriptSig=473044022034d0f8f879de64, nSequence=4294967294)
    CTxIn(COutPoint(cf7001bdf3774d64d01832f79df9914d24c641ca14fa7d7742c698941a49d6af, 0), scriptSig=483045022100f16448095e47, nSequence=4294967294)
    CTxOut(nValue=2267.12366597, scriptPubKey=76a91433449a3c30ed33871f3d12f2)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)

DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294911.8159312-08-2019 07:04:5111000.00





Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00593000 tBBP
Net amount: -11 000.00593000 tBBP
Transaction ID: 4787a76368dd0715c36c90d02c9f7a65149d63646ab69ffdaf0155cc6231cd88
Output index: 0
Transaction total size: 593 bytes



Debit: -503 588.99953448 tBBP
Credit: 492 588.99360448 tBBP
To: yP5GznAJMkYnxggE3BM74FMGrWm2ZFCJML 492588.0000 BBP

Transaction:
CTransaction(hash=4787a76368, ver=1, type=0, vin.size=1, vout.size=2, nLockTime=20045, vExtraPayload.size=0)
    CTxIn(COutPoint(0b62094692049e33fcf3bc7eccb48ee02ae0cb3b9d087ac68cbc3d71b8a95203, 1), scriptSig=483045022100de2345fa4db9, nSequence=4294967294)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)
    CTxOut(nValue=492588.99360448, scriptPubKey=76a9141e3a5469ec7d6141cdf494dd)
DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294911.8158312-08-2019 07:04:5111000.00



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 06, 2019, 08:18:24 AM
Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00821000 tBBP
Net amount: -11 000.00821000 tBBP
Transaction ID: c76dc628ab85cd1eefea170d649bb92aabf085c2a12b84b9d34a25518e6ec05c
Output index: 1
Transaction total size: 821 bytes

Code: [Select]
Debit: -3767.05326650 tBBP
Debit: -3773.29547908 tBBP
Debit: -5065.13451406 tBBP
Credit: 1605.47504964 tBBP
To: yLdnz7dQxUZCpcX1Z9bcBbFz2QBRQgMGZn 1605.0000 BBP

Transaction:
CTransaction(hash=c76dc628ab, ver=1, type=0, vin.size=3, vout.size=2, nLockTime=20102, vExtraPayload.size=0)
    CTxIn(COutPoint(7a4804ef0b14b94c37ca5083dc1675ef3c0d11637282529850c50263e2bc8202, 0), scriptSig=483045022100bde976efea0e, nSequence=4294967294)
    CTxIn(COutPoint(bde5dba4fc908e2fe106e5e5040dc213fae425b243a617f0ef6c793c220a2ebc, 0), scriptSig=483045022100a770d7458985, nSequence=4294967294)
    CTxIn(COutPoint(c241737398b8becad573bb9887cc659f3705ec684c24ff134e30bba034ef2668, 10), scriptSig=483045022100ffea81996b77, nSequence=4294967294)
    CTxOut(nValue=1605.47504964, scriptPubKey=76a91403784bdd3a4cf73272b0bcf3)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)

DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294901.8160312-08-2019 07:04:5011000.00





Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00821000 tBBP
Net amount: -11 000.00821000 tBBP
Transaction ID: ab6b451724d48b7204ccd5eedad550c2548fac764450f840e8ad14ac28e96a85
Output index: 1
Transaction total size: 819 bytes


Debit: -3779.16221232 tBBP
Debit: -5707.10526530 tBBP
Debit: -3780.86439835 tBBP
Credit: 2267.12366597 tBBP
To: yQzXVa2uKZf1ZvhPnf2WEmPVh9Lx3Q8YYY 2267.0000 BBP

Transaction:
CTransaction(hash=ab6b451724, ver=1, type=0, vin.size=3, vout.size=2, nLockTime=20043, vExtraPayload.size=0)
    CTxIn(COutPoint(34a9e058211f4b6b722b4d26ed096b2dcdcff482f11a6d75b7f1ae0fa4ae5fed, 0), scriptSig=4730440220199ae942e147ad, nSequence=4294967294)
    CTxIn(COutPoint(5e0a114a3c01706e76f06f8fb80557323b0b8af25f519585d00ab40afaf954d1, 10), scriptSig=473044022034d0f8f879de64, nSequence=4294967294)
    CTxIn(COutPoint(cf7001bdf3774d64d01832f79df9914d24c641ca14fa7d7742c698941a49d6af, 0), scriptSig=483045022100f16448095e47, nSequence=4294967294)
    CTxOut(nValue=2267.12366597, scriptPubKey=76a91433449a3c30ed33871f3d12f2)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)

DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294911.8159312-08-2019 07:04:5111000.00





Status: 0/unconfirmed, not in memory pool
Date: 12/4/2019 23:04
To: yLKSrCjLQFsfVgX8RjdctZ797d54atPjnV
Debit: -11 000.00000000 tBBP
Transaction fee: -0.00593000 tBBP
Net amount: -11 000.00593000 tBBP
Transaction ID: 4787a76368dd0715c36c90d02c9f7a65149d63646ab69ffdaf0155cc6231cd88
Output index: 0
Transaction total size: 593 bytes



Debit: -503 588.99953448 tBBP
Credit: 492 588.99360448 tBBP
To: yP5GznAJMkYnxggE3BM74FMGrWm2ZFCJML 492588.0000 BBP

Transaction:
CTransaction(hash=4787a76368, ver=1, type=0, vin.size=1, vout.size=2, nLockTime=20045, vExtraPayload.size=0)
    CTxIn(COutPoint(0b62094692049e33fcf3bc7eccb48ee02ae0cb3b9d087ac68cbc3d71b8a95203, 1), scriptSig=483045022100de2345fa4db9, nSequence=4294967294)
    CTxOut(nValue=11000.00000000, scriptPubKey=76a914000000000000000000000000)
    CTxOut(nValue=492588.99360448, scriptPubKey=76a9141e3a5469ec7d6141cdf494dd)
DWS: yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm120102yjMPYG1qXYf2qWU2z1yMtfiSCx7cYcvMm115755294911.8158312-08-2019 07:04:5111000.00

Please encapsulate long 'pastes' within code tags.

Were you going to answer the other questions in my post?

Next, try to grep your own debug.log like this:
cd testnet3
cat debug.log | grep c76dc628ab85cd1eefea170d649bb92aabf085c2a12b84b9d34a25518e6ec05c

Please paste the error here.

Your burn is not on my sanctuary log, or in my dev node, so it did not make it onto the network.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 06, 2019, 08:40:11 AM
> How many did you successfully test before that? 
[/size]> Were you inserting a lot of DWS inside the same block, or trying to break it, or what lead up to the failed DWS transaction exactly?[/color]
[/size][/color]
[/size]Yes, i submitted three inside same block. Sometimes it works, and sometimes it doesn't. We'll just have to see in production I guess.[/color]
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 06, 2019, 05:47:26 PM
** HOST BRZ (www.hostbrz.com) UPDATE/GOING OUT OF BUSINESS **


Dear Customer,

Over the past few months we have been met with many challenges within the hosting business. Some that have not been overcome.
As result of this we will be closing our doors.  We will be shutting down this Monday 12/9/2019.  We are taking this time to let our customers know so that they may backup and retrieve all of their data before then.
We deeply apologize for this inconvenience.
Thank You.
 
Management

NOTE:  Hostbrz is only giving valuable customers 3 days to remove their data.  I believe they will be keeping the excess hosting fees and not offering a refund.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 06, 2019, 08:52:06 PM
they did a crypto bridge on you
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on December 07, 2019, 02:10:54 AM
It seems the DWS worked fine, I got the payout in time as expected (staked 12000 obtained 1800 for 24h).

I will create a new one taking a bit longer
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 08, 2019, 10:14:28 AM
** TestNet Update **

- TestNet seems relatively stable.  I've burned about 50 DWS (and received them back) with 100% success.  I havent had any memory pool rejects in the latest version.  PODC appears to be working.  Unbanked appears to be working. 
- I see this poll: [https://forum.biblepay.org/index.php?topic=476.new;topicseen#new  ]  shows  a  potential interest in allowing all teams in, including GRC, with ^1.6.  I believe in light of this potential outcome, it would be prudent for us to create the code necessary for this, and have it ready within 2 days.  Ill be working on this later today, and making this into a spork for testnet.
- I have a minor change to check in for TestNets branch to run against prod; but Ill wait until I get the above release ready.  The current branch has been mining against prod, and keeping in sync with prod with the patch involved (but you do need the upcoming patch to run this branch against prod so please dont try it yet).





Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 08, 2019, 04:59:13 PM
Could someone please join that is outside GRC & BBP?

The next version should be ready in a few hours; we need to test a non-grc non-bbp cpid in podc2.0 to ensure the rewards come through.
Btw, your RAC has to be higher than 256 for this to work.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 08, 2019, 06:01:27 PM
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).

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 08, 2019, 11:22:09 PM

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"
}

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 08, 2019, 11:46:23 PM
I'm stuck at Loading PoDC Researchers... for some reason.


Tried --erasechain and stuck there again.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 08, 2019, 11:56:53 PM

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

https://github.com/biblepay/biblepay-evolution/commit/306653b982ee1907ac2b13e54030f131012aae2a#diff-a0c8f511d90e83aa9b5857e819ced344R3027 (https://github.com/biblepay/biblepay-evolution/commit/306653b982ee1907ac2b13e54030f131012aae2a#diff-a0c8f511d90e83aa9b5857e819ced344R3027)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 09, 2019, 09:56:13 AM
I'm stuck at Loading PoDC Researchers... for some reason.


Tried --erasechain and stuck there again.

What version are you running?

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 09, 2019, 09:56:57 AM
Is there a default value for the spork when start the blockchain from scratch?

https://github.com/biblepay/biblepay-evolution/commit/306653b982ee1907ac2b13e54030f131012aae2a#diff-a0c8f511d90e83aa9b5857e819ced344R3027 (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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 09, 2019, 10:50:26 AM
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...
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 09, 2019, 02:58:06 PM

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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 09, 2019, 04:06:31 PM
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.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: togoshigekata on December 09, 2019, 05:54:26 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
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on December 09, 2019, 07:52:29 PM
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
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop on December 09, 2019, 08:24:05 PM
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.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP on December 10, 2019, 08:53:46 AM
I have tested 1.4.8.4 against mainnet and everything seems to sync properly (chain, sans, proposals, leaderboard...)
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 10, 2019, 10:44:53 AM
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.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on December 10, 2019, 10:49:41 AM
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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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.


Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop 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
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 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
}

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: MIP 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.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop 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?
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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?



Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop 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.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: oncoapop 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"

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews 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.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 17, 2019, 11:53:43 PM
None of the CameroonONE kids are being recognized using TestNet RC1. They all say unprovisioned.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: sunk818 on December 18, 2019, 08:09:38 AM
would you consider making the max block time shorter? maybe 49 minutes (7x7)? something even smaller like 28 minutes (7x4) would be good too.
Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on February 07, 2020, 10:14:18 AM
would you consider making the max block time shorter? maybe 49 minutes (7x7)? something even smaller like 28 minutes (7x4) would be good too.

In RX it is 30 minutes, so that should be much better.

Title: Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
Post by: Rob Andrews on February 07, 2020, 10:15:01 AM
None of the CameroonONE kids are being recognized using TestNet RC1. They all say unprovisioned.

That was intentional, we were switching domains back and forth to prove it was out of my control once given to cameroon.