TestNet - PODC 2.0 (Proof of Distributed Computing)

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?

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

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'.

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?

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)

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.

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

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?

I think we need Oncoapop back, I see the POSE banned sancs are causing safe mode- Oncoapop are you available to unban?

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

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.

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.

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]

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.

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".