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

[znffal]

Sorry I haven't had time to keep testing lately. V busy at work. I'll update asap. I have a couple months left over credit at some vps server providers so I will look to add these to Rosetta. I have no other use for them!

[Rob Andrews]

Hey guys, hold off on testing 1.0.9.5, I discovered a sync bug.

The good news is I think this has been causing problems in testnet.

Ill have this fixed in 30 minutes.

[jaapgvk]

Alright

[Rob Andrews]

Hey guys, hold off on testing 1.0.9.5, I discovered a sync bug.

The good news is I think this has been causing problems in testnet.

Ill have this fixed in 30 minutes.

Ok, all, sorry about that, fixed.

Now please upgrade to 1.0.9.5b and it should sync.

I also added 'exec racdecay' if you want to play around with that, if you run it without a parameter it gives a report on a machine that will have 1000 RAC on a steady basis after 30 days, if you run it with a parameter, enter the amount of new credit the machine will crunch each day and it will give you the corresponding RAC the machine will have in N days in the report.

[Rob Andrews]

Sorry I haven't had time to keep testing lately. V busy at work. I'll update asap. I have a couple months left over credit at some vps server providers so I will look to add these to Rosetta. I have no other use for them!

Sweet! 

[T-Mike]

Ok, all, sorry about that, fixed.

Now please upgrade to 1.0.9.5b and it should sync.

I also added 'exec racdecay' if you want to play around with that, if you run it without a parameter it gives a report on a machine that will have 1000 RAC on a steady basis after 30 days, if you run it with a parameter, enter the amount of new credit the machine will crunch each day and it will give you the corresponding RAC the machine will have in N days in the report.

Updated 4 nodes to 1.0.9.5b. Let us know when the windows wallets are ready. Thanks.

[Rob Andrews]

Updated 4 nodes to 1.0.9.5b. Let us know when the windows wallets are ready. Thanks.

Ok, deployed 1095b for windows, go for it.

[Rob Andrews]

As far as testing these things:
-  Allow unbanked to be compensated without PODC Updates
We need to ask Rastiks to not shut down the cell phone, and not add any non-ARM rac.
Looking in my Sanctuary for Rastiks, I dont see your CPID in the list : fe553a955f0e21d46724858870014cbe.  (I found your CPID by looking at the unbanked report in the pool), anyway I see Rastiks is on the team, but your not associated in Biblepay (exec associate).  I see this by typing exec datalist dcc and do not see your CPID.  This would be a nice feature to test, so if either Rastiks could you please associate your cpid or someone else could start an unbanked CPID also?


- Fixed prayers diaplay in overview page  (they were invisible)
  Most tested - I can see exec testprayers shows the prayers and now they rotate on the overview page


- Added UTXO weight and Task Weight to Distributed Computing Page GUI
Looks good so far



- Added 7 day Magnitude and 1 day magnitude to exec getboincinfo
Now you can see both in exec getboincinfo.  This is mostly useful for debugging and seeing the magnitude trend.



- Fixed DC Association process to throw the correct distinct errors for INVALID_CREDENTIALS or ALREADY_IN_CHAIN
* Someone needs to test this



- Added cache purging system (to prevent memory bloating in the future)
* I tested this by writing special RPC commands, and its working, memory should not bloat

[togoshigekata]

Updated and running my 2 Testnet sanctuaries v1.0.9.5b

Removed blocks and chainstate folders, deleted relevant .dat files and reindexed,
remembered to enable mining on the wallet with CPID associated/burned

./biblepay-cli getblockhash 9737
c8a46bfef7a3cb13bbfe34a4d768ba13c2bb7f1caebbb10bf4af230f377562a5

[T-Mike]

As far as testing these things:
-  Allow unbanked to be compensated without PODC Updates
We need to ask Rastiks to not shut down the cell phone, and not add any non-ARM rac.
Looking in my Sanctuary for Rastiks, I dont see your CPID in the list : fe553a955f0e21d46724858870014cbe.  (I found your CPID by looking at the unbanked report in the pool), anyway I see Rastiks is on the team, but your not associated in Biblepay (exec associate).  I see this by typing exec datalist dcc and do not see your CPID.  This would be a nice feature to test, so if either Rastiks could you please associate your cpid or someone else could start an unbanked CPID also?


- Fixed prayers diaplay in overview page  (they were invisible)
  Most tested - I can see exec testprayers shows the prayers and now they rotate on the overview page


- Added UTXO weight and Task Weight to Distributed Computing Page GUI
Looks good so far



- Added 7 day Magnitude and 1 day magnitude to exec getboincinfo
Now you can see both in exec getboincinfo.  This is mostly useful for debugging and seeing the magnitude trend.



- Fixed DC Association process to throw the correct distinct errors for INVALID_CREDENTIALS or ALREADY_IN_CHAIN
* Someone needs to test this



- Added cache purging system (to prevent memory bloating in the future)
* I tested this by writing special RPC commands, and its working, memory should not bloat

Dedicated Android Test Account:
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1985935
CPID: 4b7d2d64c88b32927a21ad20a57868e4

[jaapgvk]

Alright, I've updated both my Linux and Windows wallet. And both have their own CPID associated (a general one and an unbanked one). Sanctuary is also running.

Code Select Expand


09:52:35

getblockhash 9737


09:52:35

c8a46bfef7a3cb13bbfe34a4d768ba13c2bb7f1caebbb10bf4af230f377562a5


10:22:22

getblockhash 9938


10:22:22

a6763250717fd7b4b46e5c27a1cfc2832eb60991ccdca19574c8c42c3bf30519




As far as testing these things:
-  Allow unbanked to be compensated without PODC Updates
We need to ask Rastiks to not shut down the cell phone, and not add any non-ARM rac.

I've set up a separate account for my Android phone, to test the unbanked feature:

https://boinc.bakerlab.org/rosetta/show_user.php?userid=1985966


CPID: c852da1a620ad630b70c8ec1ccdee366

- Fixed prayers diaplay in overview page  (they were invisible)
  Most tested - I can see exec testprayers shows the prayers and now they rotate on the overview page

I tried a prayer Seems to be working fine again.

[klondike]

hi guys?

1. when ill update to new 195 linux testnet wallet, i lost all my tBBP?
2. why is my UTXOweight still 75 when i have 1.7M tBBP?
3. when i close my testnet-admin-linuxwallet and others rosetta machines will be continue= what happens

rosetta is big eater of RAM and internet datas i must to upgrade my RAM on my xeons machines

thx for answers

[jaapgvk]

hi guys?

1. when ill update to new 195 linux testnet wallet, i lost all my tBBP?
2. why is my UTXOweight still 75 when i have 1.7M tBBP?
3. when i close my testnet-admin-linuxwallet and others rosetta machines will be continue= what happens

thx for answers

1. I haven't lost any tBBP after updating. Did you by accident remove your wallet.dat? Try a reindex maybe?
2. About the UTXOweight, see this post: http://forum.biblepay.org/index.php?topic=108.msg1996#msg1996
3. I think that the current state of affairs is that you have to have your wallet online and mining to be able to receive rewards (except if you fall into the 'unbanked' category, which is when you mine ARM-only).

[Rob Andrews]

Side note all:
Starting at block 10,000 in testnet, we now enforce the distinct CPID signatures.  Looking at 'showblock 10001, 10002, 10003' etc shows that this is working.

[Rob Andrews]

As far as testing the sanctuary rank feature, this is used by the SanctuaryQuorum to determine your sanctuaries place in being called into service to process and vote on the filtered magnitude files.

Only do this if you are a synced sanctuary with a position in "masternode winners" report.  If you are not in winners, this command will be useless as we only choose sancs who have a rank.

If you have a place in the payment queue type 'exec testranks'. The tail end of this command shows the sanc count, and it looks like we have a piddly 4.  Anyway this means you should see (since we need a minimum of 2 voting sancs in testnet, 10% in prod with a minimum of 5 in prod), an alternating 50% chance of being called to filter or vote on a file, for every Other block number (since 2 minimum divided by 4 is a 50-50 chance per block).  So now look at your heights starting with the current height and go forward in the future - IE right now we are on block 10005 so go from 10005 to say 10025, and just see the pattern, is it 0%, 100%, 0%, 100%,100%, etc.  If so our rank is working. 

I am looking at my testranks report on my hot sanc and it appears this is working.  (The number is height,  percentage of being called, and Sanctuary Rank) in the report.