BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

Started by Rob Andrews, February 06, 2018, 04:00:36 PM

Previous topic - Next topic

Rob Andrews

Quote from: Rob A. on March 07, 2018, 10:31:04 AM
Yeah, thats normal until we create the first superblock - then the system assigns everyone a magnitude for the first time.

That reminds me, I need to see whats stopping us from creating a testvote in prod, let me check.

So things look semi-OK, I guess on a scale from 1-10, maybe a 5 for this go live.  Primarily low because none of our transactions are confirming.
So here is the first rock in the rocky start:
The exec testvote, this is used to "prime" our sancs for the first contract (no need to ever do this later once we are rolling), gave me an error- I cant paste it : Something to the effect of Unable to calculate magnitudes, project RAC below minimum.

Looking at this in detail, it appears this is because no one on the network really has any UTXO weight that is confirmed. 

So if you type exec datalist utxoweight, from a sanc (not from the machine that sent the UTXO), my Sancs list is empty.  The reason you see utxo weight locally, is because that orphaned tx, the one with the "?" around it - it is alive in your local wallet but not in the sanc (as it was not confirmed by the network).  So we will need to -zapwallettxes once we get past this mandatory cutover block, restart the clients, and do the 'exec podcupdate' again, to ensure we all have utxo weight.

Once that happens I believe then we can try the exec testvote from the sanc, and hopefully generate contract #1 in prod.


Rob Andrews

Quote from: Ichthus220 on March 07, 2018, 10:41:36 AM
My wallet says 33360, my 1BBP transaction now has confirmations, my utxo show 0 and my stakebalance shows 0, my CPID now shows up in exec getboincinfo. Is all this correct? I change polpercentage in the dat file to 100.
Can you paste your exec getboincinfo?  I can look up your CPID from my sanc.

You should have UTXO Weight: 100  if everything is well.


T-Mike

Quote from: Rob A. on March 07, 2018, 11:01:06 AM
So things look semi-OK, I guess on a scale from 1-10, maybe a 5 for this go live.  Primarily low because none of our transactions are confirming.
So here is the first rock in the rocky start:
The exec testvote, this is used to "prime" our sancs for the first contract (no need to ever do this later once we are rolling), gave me an error- I cant paste it : Something to the effect of Unable to calculate magnitudes, project RAC below minimum.

Looking at this in detail, it appears this is because no one on the network really has any UTXO weight that is confirmed. 

So if you type exec datalist utxoweight, from a sanc (not from the machine that sent the UTXO), my Sancs list is empty.  The reason you see utxo weight locally, is because that orphaned tx, the one with the "?" around it - it is alive in your local wallet but not in the sanc (as it was not confirmed by the network).  So we will need to -zapwallettxes once we get past this mandatory cutover block, restart the clients, and do the 'exec podcupdate' again, to ensure we all have utxo weight.

Once that happens I believe then we can try the exec testvote from the sanc, and hopefully generate contract #1 in prod.

Rob, I think we are on a different chain:


{
  "DataList": "UTXOWEIGHT",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-07-2018 14:44:31)": "100",
  "4004B7FEC94751F61FE9135977BAC553 (03-07-2018 13:38:25)": "100",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-07-2018 15:01:37)": "50",
  "6BCD1F25DC07679DB5AD812A012DF1A4 (03-07-2018 14:21:22)": "0",
  "84D803E4D82D3BDCDF8E2AB601E93E20 (03-07-2018 15:53:17)": "100",
  "8735CFE64D964416DBA6015EB414CF7E (03-07-2018 12:17:54)": "60",
  "8F273B30F8E0A298ED26E242762DF701 (03-07-2018 09:56:52)": "25",
  "940552F602F67A3CF57A452438F36EE9 (03-07-2018 05:44:28)": "25",
  "96892EC0FC8A2710FA84F26C9C84CD3E (03-07-2018 12:03:32)": "60",
  "968D0A04AA31FA9BBBFF2EB6A87B02F2 (03-07-2018 09:56:52)": "25",
  "A9420A038E44750C69CA4497FE08C2A9 (03-07-2018 15:01:37)": "60",
  "CA895B47AACFFBDBF906201821AF2F9F (03-07-2018 14:21:22)": "50",
  "D4E56169934BF307F145C75BCB2896A2 (03-07-2018 15:14:26)": "25",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-07-2018 08:33:51)": "100",
  "E6CE50042187D4B285568D86EF458F32 (03-07-2018 15:14:26)": "75",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (03-07-2018 16:26:29)": "100",
  "E94C1704C75F731F8BFDE303F08408EE (03-07-2018 13:01:08)": "75"
}

jaapgvk

Quote from: SimonSays on March 07, 2018, 11:09:36 AM
Hi,

Here is my boincinfo - does it look ok?


18:08:33

exec getboincinfo


18:08:35

{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422345,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 7786.68,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 7786.68,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


Best regards,
Simon

In general, it seems about the same as mine:


18:18:36

exec getboincinfo


18:18:38

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 422345,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 9859.25,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 0,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 0,
  "Total_RAC": 9859.25,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


But I do show up in Mike's list with an UTXOWeight of 100.

Rob Andrews

Quote from: T-Mike on March 07, 2018, 11:05:25 AM
Rob, I think we are on a different chain:


{
  "DataList": "UTXOWEIGHT",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-07-2018 14:44:31)": "100",
  "4004B7FEC94751F61FE9135977BAC553 (03-07-2018 13:38:25)": "100",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-07-2018 15:01:37)": "50",
  "6BCD1F25DC07679DB5AD812A012DF1A4 (03-07-2018 14:21:22)": "0",
  "84D803E4D82D3BDCDF8E2AB601E93E20 (03-07-2018 15:53:17)": "100",
  "8735CFE64D964416DBA6015EB414CF7E (03-07-2018 12:17:54)": "60",
  "8F273B30F8E0A298ED26E242762DF701 (03-07-2018 09:56:52)": "25",
  "940552F602F67A3CF57A452438F36EE9 (03-07-2018 05:44:28)": "25",
  "96892EC0FC8A2710FA84F26C9C84CD3E (03-07-2018 12:03:32)": "60",
  "968D0A04AA31FA9BBBFF2EB6A87B02F2 (03-07-2018 09:56:52)": "25",
  "A9420A038E44750C69CA4497FE08C2A9 (03-07-2018 15:01:37)": "60",
  "CA895B47AACFFBDBF906201821AF2F9F (03-07-2018 14:21:22)": "50",
  "D4E56169934BF307F145C75BCB2896A2 (03-07-2018 15:14:26)": "25",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-07-2018 08:33:51)": "100",
  "E6CE50042187D4B285568D86EF458F32 (03-07-2018 15:14:26)": "75",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (03-07-2018 16:26:29)": "100",
  "E94C1704C75F731F8BFDE303F08408EE (03-07-2018 13:01:08)": "75"
}


Yeah, were on a different chain, Im going to rebuild that particular sanc now.

Probably unfruitful to look at the blockhash right now, lets check them after 33440, and see if we can match up then.

Ichthus220

Hey Rob, here's the exec getboincinfo you requested:


11:56:35

exec getboincinfo


11:56:36

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422345,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2711.63,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2711.63,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


T-Mike

Quote from: Rob A. on March 07, 2018, 11:48:44 AM
Yeah, were on a different chain, Im going to rebuild that particular sanc now.

Probably unfruitful to look at the blockhash right now, lets check them after 33440, and see if we can match up then.

Sanc:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

Wallet:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f



Ichthus220

How do I add information in the boxes with the scroll bars? So I don't take up lots of post space.

Rob Andrews

Quote from: Ichthus220 on March 07, 2018, 12:08:55 PM
How do I add information in the boxes with the scroll bars? So I don't take up lots of post space.
Thanks, just surround it with
"[ code ]"

and

[ /code ]

Without the spaces in there.


Ichthus220

Quote from: Rob A. on March 07, 2018, 12:10:45 PM
Thanks, just surround it with
"[ code ]"

and

[ /code ]

Without the spaces in there.

Thanks, worked! My info is above somewhere. I appreciate everything you're doing Rob.

orbis

Quote from: T-Mike on March 07, 2018, 11:59:05 AM
Sanc:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

Wallet:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

I have same hash like you.
It looks good for me... 3 wallets on same chain (looks good because it is same as Mike and explorer :) )
My task and UTXO are 100 (after many hours, blood and sweat) :)
BUT... after getinfo I have in all of my wallets this message:
"errors": "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."

togoshigekata

Is there a way to view all the forked blockchains?
I tried running getchaintips command but it crashes my wallet LOL

Main Explorer is on 33438 (so is a wallet that I reindexed)
https://biblepay-explorer.org/

Backup Explorer is on 33407
http://explorer.biblepay.org:3001/

Which chain are we waiting to reach 33440?


T-Mike

Quote from: togoshigekata on March 07, 2018, 12:51:30 PM
Is there a way to view all the forked blockchains?
I tried running getchaintips command but it crashes my wallet LOL

Main Explorer is on 33438 (so is a wallet that I reindexed)
https://biblepay-explorer.org/

Backup Explorer is on 33407
http://explorer.biblepay.org:3001/

Which chain are we waiting to reach 33440?

I think we are waiting to see which one wins. The block has already passed, it was 33400.

Rob Andrews

Quote from: togoshigekata on March 07, 2018, 12:51:30 PM
Is there a way to view all the forked blockchains?
I tried running getchaintips command but it crashes my wallet LOL

Main Explorer is on 33438 (so is a wallet that I reindexed)
https://biblepay-explorer.org/

Backup Explorer is on 33407
http://explorer.biblepay.org:3001/

Which chain are we waiting to reach 33440?

The command is 'getchaintips' but its crashing my node.  Ill run valgrind on that command now.

So Im not really sure we have an answer yet as to which chain is correct, Ive reindexed a few times and ended at 33438.  I think the answer lies in after we establish at least 30 blocks or so after 33440,  we will then know the official chain hash, while the old chain dies off, then we can add a checkpoint which will cause everyone to always sync on the correct chain.  Im thinking maybe we run this for a few days, and around Friday night we add a checkpoint after verifying the whole system works - then go live on the exchanges.


orbis

Quote from: togoshigekata on March 07, 2018, 12:51:30 PM
Backup Explorer is on 33407


Which chain are we waiting to reach 33440?
My wallets are synced with this.
So I hope that it is correct.

BTW: I see some node with 1103 with same block as I. Oh and 1099 wallet is there too. Is it possible?