Bible Pay

BiblePay - TestNet Testing Thread => BiblePay - TestNet Testing Thread => Topic started by: Rob A. on February 06, 2018, 04:00:36 pm

Title: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 04:00:36 pm
Please join us in testing Proof-of-Distributed-Computing, a new consensus algorithm for Biblepay.

This algorithm is designed to divert proof-of-work clock-cycles (heat mining) into cancer-mining-clock-cycles through Rosetta@Home, performing useful work.

Testnet release date :  February 6th, 2018  @   15:58:00.

Windows is still compiling.  Will update when ready.
Please compile Linux from source :  https://github.com/biblepay/biblepay
Version: 1.0.8.8k - Leisure

NOTE:

Testnet has changed severely.  Please :
rm blocks -r
rm chainstate -r
rm mnc*.dat
rm gov*.dat
rm banlist.dat

Restart client.


To get started with Proof of Distributed Computing:

See Background info on distributed-computing first:
http://wiki.biblepay.org/Distributed_Computing

See guide:

How to Get Started with Distributed-Computing:
http://wiki.biblepay.org/Distributed_Computing_Start_Guide


**NOTE:  So far, the guide shows how to run Rosetta on Windows (as your cancer miner), and your biblepay wallet on linux (compiled from github).

 I am still in the process of documenting how to install Rosetta on linux ** (Its easy, if you are daring, please check the windows instructions in the guide and give it a shot on linux using the apt-get boinc commands )



PS All credit for this project goes to Jesus.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 06, 2018, 05:17:04 pm
working it with lichsucher PPA?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 05:30:23 pm
Awesome! Ill be testing in a bit,
Do we need any testnet sanctuaries running? I have one available
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 05:33:34 pm
Awesome! Ill be testing in a bit,
Do we need any testnet sanctuaries running? I have one available

Yes.  But chain needs erased so that will take down your sanc.  Please recreate it.

Yeah, we need a Sanctuary Quorum.

The code automatically chooses 10% of the sancs and marks them for duty.

All we have to do is type exec testvote after 500 more blocks and see if the quorum is Live.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 06:09:07 pm
Of course, two key pieces of info we will need to add to the help guide is:

1) How do I find out how much RAC (recent average credit) my CPID has for Rosetta?
   Go to the BOINC manager (on your PC), click on Projects, and on the row with Rosetta, take a look at the RAC field.
  That is the number Biblepay uses to calculate your Magnitude in the wallet once per day.

2) How do I view my CPID and magnitude in the wallet?
   The first way is to click the Distributed Computing tab in the GUI and view the bottom left "CPID" and"Magnitude" values.
 (This requires 1.0.8.8i+).
  The second way is to click on the RPC, and type 'exec getboincinfo'


NOTE:

If you are a new researcher, you will have to wait about 24 hours to see your RAC accumulate in BOINC.


PS To find the next superblock in Biblepay, type exec testvote, look for Next Superblock Height.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 07:05:05 pm
To find out if you are synced with the new chain:


getblockhash 2576


8ad6d439bb77b4304a34497183a16e4256f39dce990906f97e89ac602dcd4a50

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 07:18:17 pm
And here is another item for our Wiki:

How to install Rosetta on linux:  Follow these instructions to install graphical BOINC:
http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu

On my Debian sanctuary, all I had to do was:
apt-get install boinc-manager boinc-client

Click Activites | Search | Boinc | Run Boinc
Add Rosetta - Use existing User

Done.  Now my linux sanctuary is computing cancer research and credits are going to biblepays single CPID!

NOTE:  The easy way to get started is launch the boinc manager, click Tools | Advanced View, click Projects, click Rosetta, and you will see the same familiar layout you see in windows - with a display of your RAC.  Once you become more advanced, you can run it in headless mode.

Whats nice about Rosetta is they have tons of options to manage your CPU use, so we can support massive amounts of tailored configuration for our miners now.  Including android phones.  And gamers machines.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 07:48:44 pm
I read the Start Guide http://wiki.biblepay.org/Distributed_Computing_Start_Guide
and installed BOINC on Windows

it then popped up BOINC Manager saying "Choose a project"
Clicked Rosetta@home >>> "Communicating with Project" >>>
"Identify your account at Rosetta@home, Are you already running this Project? No, new user - Yes, existing user" >>>
No >>> Email address, password, confirm password >>> Next >>> "Communicating with Project" >>>
"Project added" >>> Finish >>> Opens web page "Finish account setup" >>> Nickname >>>
"Find a team"

Should I search for a team or click "Im not interested in joining a team"?

==========

Also, just a note for others, I forgot testnet has its own folder inside of ~/.biblepaycore called testnet3,
so when cleaning up my old testnet files I had to cd into ~/.biblepaycore/testnet3
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 07:55:49 pm
I read the Start Guide http://wiki.biblepay.org/Distributed_Computing_Start_Guide
and installed BOINC on Windows

it then popped up BOINC Manager saying "Choose a project"
Clicked Rosetta@home >>> "Communicating with Project" >>>
"Identify your account at Rosetta@home, Are you already running this Project? No, new user - Yes, existing user" >>>
No >>> Email address, password, confirm password >>> Next >>> "Communicating with Project" >>>
"Project added" >>> Finish >>> Opens web page "Finish account setup" >>> Nickname >>>
"Find a team"

Should I search for a team or click "Im not interested in joining a team"?

==========

Also, just a note for others, I forgot testnet has its own folder inside of ./biblepaycore called testnet3,
so when cleaning up my old testnet files I had to cd into ./biblepaycore/testnet3

Great!  Your almost there.

On the team, you can click not interested in team and skip for now.

However, we might want to launch a campaign when we move to prod to *suggest* joing team Biblepay, just so that we as a team can move up the Global Statistics Ladder, and be a force to be reckoned with for Good, IE if our 12,000 researchers are on one team, we can then use that statistic for PR purposes, commercials etc.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 08:00:49 pm
Great!  Your almost there.

On the team, you can click not interested in team and skip for now.

However, we might want to launch a campaign when we move to prod to *suggest* joing team Biblepay, just so that we as a team can move up the Global Statistics Ladder, and be a force to be reckoned with for Good, IE if our 12,000 researchers are on one team, we can then use that statistic for PR purposes, commercials etc.



Ok guys, you can now join team "Biblepay" if you wish.  (https://boinc.bakerlab.org/rosetta/team_display.php?teamid=15044)

Remember, being on our team is not required to be paid, as we want to target a PR campaign to invite every rosetta researcher in the world to join Biblepay, and they are not required to leave their team to join forces with us.

However, it is recommended to join the team so we can share our global progress & global statistics.

Charts are available for the team, and a leaderboard, etc.


EDIT:  If you are already a Rosetta researcher, you can log in here and edit your team:
https://boinc.bakerlab.org/rosetta/home.php


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 08:03:59 pm
https://boinc.berkeley.edu/wiki/Teams

Ok cool, joined!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 08:06:35 pm
https://boinc.berkeley.edu/wiki/Teams

Ok cool, joined!

Sweet, I see you in the team:
https://boinc.bakerlab.org/rosetta/team_display.php?teamid=15044

Did you associate your Rosetta CPID with biblepay yet btw?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 08:11:01 pm
On my BOINC homepage: https://boinc.bakerlab.org/rosetta/home.php
I see in the "Computing and credit" section inside of "Cross-project statistics" there is "Cross-project ID"
Is that what I need?

I also noticed my BOINC Manager started doing stuff a little while ago on its own,
says Elapsed 00:16:22 and Remaining 05:04:03, Status: Running

So I have BOINC on Windows,
I have latest BiblePay installed on Linux remote machine (command line) running on tesnet on correct chain,
and now I have a BOINC account

So it looks like next step is to do this burn transaction thing with my CPID? and it looks like I need a GUI wallet for that?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 08:16:32 pm
On my BOINC homepage: https://boinc.bakerlab.org/rosetta/home.php
I see in the "Computing and credit" section inside of "Cross-project statistics" there is "Cross-project ID"
Is that what I need?

I also noticed my BOINC Manager started doing stuff a little while ago on its own,
says Elapsed 00:16:22 and Remaining 05:04:03, Status: Running

So I have BOINC on Windows,
I have latest BiblePay installed on Linux remote machine (command line) running on tesnet on correct chain,
and now I have a BOINC account

Sweet, so two things:
On windows boinc, click View | Advanced view.  Click on the Projects Tab.  View the Rosetta row.  Notice the value for "Avg Work Done".  That is your RAC.  You really have to wait for that to get above like 5 to see anything big in BBP.

But in the mean time, the other thing, on finding your CPID - in your Rosetta web account (the linked one you linked), search for : cross-project id in the stats section.  Thats your CPID - it will stick with you forever, even if you launch 1000 machines.  But you dont need to type it into biblepy.  But please paste it in notepad for this exercise.

In BBP, now you should go to the Distributed Computing page, and type in the rosetta user & password and click associate.

Then wait for 6 blocks for confirm to occur.  Then type 'exec getboincinfo'..  If everything worked, your CPID will match the one in notepad.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 06, 2018, 08:19:50 pm
Compiling the source code and installed BOINC. How do I obtain some tBBP for running a masternode?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 08:22:29 pm
Compiling the source code and installed BOINC. How do I obtain some tBBP for running a masternode?

Please post address and I will Rapture it.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 08:28:37 pm
The analogy is kind of funny... Just as bitcoin + sha miners needed cgminer, our miner is rosetta. 

It might be easier to set our system up (on multiple machines) than most obscure mining setups. 

I think we really have something here.  We dont have to worry about an entity porting rosetta to GPU because the program is so complicated it cant be done (it would be done if it could, actually they are trying) but nothing for us to worry about as BOINC figures out the relevant rewards in cobblestones per cycle. 

This feels better already....


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 08:31:49 pm
Sweet, so two things:
On windows boinc, click View | Advanced view.  Click on the Projects Tab.  View the Rosetta row.  Notice the value for "Avg Work Done".  That is your RAC.  You really have to wait for that to get above like 5 to see anything big in BBP.

Cool, I see the project, it had my initial account name,
but once I clicked Properties command it updated and has the correct account name now,
also see: Disk Usage 4.27GB

Projects Tab:
Project: Rosetta@home, Account: togoshigekata, Team: BiblePay, Work done 0, Avg work done 0, Resource Shares 100%,

Theres a Tasks tab, Application Rosetta 4.06 and Roestta Mini 3.78,
most are in "Ready to start" state, a few are "Running" with really small percentages,
randomly they all got "Suspended" for a few seconds, Cpu busy

Tasks that are running look like theyve been running for 32 minutes now, but are only 4-5% done

But in the mean time, the other thing, on finding your CPID - in your Rosetta web account (the linked one you linked), search for : cross-project id in the stats section.  Thats your CPID - it will stick with you forever, even if you launch 1000 machines.  But you dont need to type it into biblepy.  But please paste it in notepad for this exercise.

In BBP, now you should go to the Distributed Computing page, and type in the rosetta user & password and click associate.

Then wait for 6 blocks for confirm to occur.  Then type 'exec getboincinfo'..  If everything worked, your CPID will match the one in notepad.

So I have BiblePay on a remote Linux machine through Putty/SSH (command line) on testnet chain,
and I have BOINC on local Windows Machine,

Do I need to now install latest BiblePay for Windows and run it in testnet to do the above?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 06, 2018, 08:55:06 pm
Rob, do you have an article explaining how it works? I don't understand how we are creating blocks or processing transactions if we are doing distributed computing.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 09:06:07 pm
Cool, I see the project, it had my initial account name,
but once I clicked Properties command it updated and has the correct account name now,
also see: Disk Usage 4.27GB

Projects Tab:
Project: Rosetta@home, Account: togoshigekata, Team: BiblePay, Work done 0, Avg work done 0, Resource Shares 100%,

Theres a Tasks tab, Application Rosetta 4.06 and Roestta Mini 3.78,
most are in "Ready to start" state, a few are "Running" with really small percentages,
randomly they all got "Suspended" for a few seconds, Cpu busy

Tasks that are running look like theyve been running for 32 minutes now, but are only 4-5% done

So I have BiblePay on a remote Linux machine through Putty/SSH (command line) on testnet chain,
and I have BOINC on local Windows Machine,

Do I need to now install latest BiblePay for Windows and run it in testnet to do the above?

Right, I didnt add in the headless option yet.  OK:  Added.

Go ahead and grab 1.0.8.8l and now if you want to do this from headless go to rpc:

exec associate rosetta_email_address rosetta_password

And it should reply with the correct errors.  Note:  You need at least 1 bbp to perform the association.

In windows, we have a UI for this, along with UI for magnitude and CPID list.

I just received notification that the windows build is not complete yet- Ill work on that issue next.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 09:07:19 pm
Rob, do you have an article explaining how it works? I don't understand how we are creating blocks or processing transactions if we are doing distributed computing.

You already read the two wikis at the top, correct?  (Did you see the Payments section)?


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 06, 2018, 09:10:46 pm
Not all of it yet, will keep reading. I'm assuming those options are in the linux qt right? Because I'm compiling the -k version at the moment.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 06, 2018, 09:33:44 pm
You already read the two wikis at the top, correct?  (Did you see the Payments section)?

I see that 90% is PODC and 10% POL/POW, how is the POW work being commenced? Or what is mining that 10%? So the testnet is also testing the POL code also right? It is my understand that it does not exist right now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 09:34:09 pm
Not all of it yet, will keep reading. I'm assuming those options are in the linux qt right? Because I'm compiling the -k version at the moment.

Which options?

(All features in windows are in linux, and all features in QT are in headless, except headless does not have a GUI - but instead has a different way of doing things).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 09:37:56 pm
I see that 90% is PODC and 10% POL/POW, how is the POW work being commenced? Or what is mining that 10%? So the testnet is also testing the POL code also right? It is my understand that it does not exist right now.

The blocks are being solved by the controller wallet using POBh (POW), for a 10% reward, the other 90% is going toward the proof-of-dc budget for the daily superblock.  (These figures dont include our existing 20% budget, I was just trying to simplify the answer).

POL is disabled for two reasons:  (Trying to avoid forks - as POW is better for chainwork and security, and trying to avoid creating a business logic rule for the T-6 weight problem), secondly, I dont think we need it - as I think PODC starves off the botnet.  Its better to have a resilient reliable syncing chain.  (I dont want to bash it, its still a possibility if the issues are fixed - but Id rather error on the cautious side and evaluate this ecosystem first).








Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 09:42:37 pm
So it looks like the windows build is missing an icon, so it probably wont be ready before I go to sleep tonight.  Ill look at that issue in the morning. 

In the mean time, anyone who compiled the *nix version can still install graphics on their nix box and launch ./biblepay-qt and see the DC tab.

Btw, if anyone is mining in prod and wants to run testnet side by side your prod masternode, just do this:

./biblepay-qt -testnet -masternode=0 -rpcport=45000

That will allow it to boot side by side without taking your prod node down.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 06, 2018, 09:52:00 pm
The blocks are being solved by the controller wallet using POBh (POW), for a 10% reward, the other 90% is going toward the proof-of-dc budget for the daily superblock.  (These figures dont include our existing 20% budget, I was just trying to simplify the answer).

POL is disabled for two reasons:  (Trying to avoid forks - as POW is better for chainwork and security, and trying to avoid creating a business logic rule for the T-6 weight problem), secondly, I dont think we need it - as I think PODC starves off the botnet.  Its better to have a resilient reliable syncing chain.  (I dont want to bash it, its still a possibility if the issues are fixed - but Id rather error on the cautious side and evaluate this ecosystem first).

Thanks for the explaination, I understand now. I asekd about the POL because you wrote "The payment system pays out 90% of the available block subsidy to proof-of-dc, and 10% to proof-of-loyalty/proof-of-work." Hope testing goes well!

I'll run the testnet on my masternode tomorrow like you suggested.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 10:01:29 pm
I think v1.0.8.8 upped the protocol version from 70715 to 70716?
https://github.com/biblepay/biblepay/blob/master/src/version.h#L13

Sorry was setting up / updating a mainnet sanctuary at the same time as this BOINC stuff,
ran into incorrect protocol version error, Ill warn the others to use git checkout to v1.0.8.7

====

I got my Linux testnet wallet updated,
Ill try the RPC command to associate,
just need to clean my Windows wallet for testnet and send some tBBP from it, will report back!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 10:25:35 pm
I think v1.0.8.8 upped the protocol version from 70715 to 70716?
https://github.com/biblepay/biblepay/blob/master/src/version.h#L13

Sorry was setting up / updating a mainnet sanctuary at the same time as this BOINC stuff,
ran into incorrect protocol version error, Ill warn the others to use git checkout to v1.0.8.7

====

I got my Linux testnet wallet updated,
Ill try the RPC command to associate,
just need to clean my Windows wallet for testnet and send some tBBP from it, will report back!

1088 indeed ups the protocol version to 70716 - but it is still compatible in prod.
This should not hurt prod...As prod accepts anything 70714+.


But in testnet we do require 70716.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 10:36:51 pm
I need tBBP for address:  yQooaKF2sH3MqeqfFamycsMTaGtSkwc464
Enough to create a santuary and pay 1 BBP for the association

EDIT: Thanks got 1,000,000 tBBP Balance now

Looks like my Windows testnet sent all my tBBP

Is there a testnet block explorer? Found it:
https://testnet.biblepay-explorer.org
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 10:48:44 pm
I need tBBP for address:  yQooaKF2sH3MqeqfFamycsMTaGtSkwc464
Enough to create a santuary and pay 1 BBP for the association

EDIT: Thanks got 1,000,000 tBBP Balance now

Looks like my Windows testnet sent all my tBBP

Is there a testnet block explorer? Found it:
https://testnet.biblepay-explorer.org

Looks like Alex is still on 1086.

Im on block 2721?  Hash:068ac664afb4c3cf21137c50fe0e4496305d29a21fb682d1a164c49b08e9212d



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 10:50:57 pm
 ./biblepay-cli exec associate togoshigekata@gmail.com XXXXXXXXX
{
  "Command": "associate",
  "E-Mail": "togoshigekata@gmail.com",
  "Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"
}

Im also on block 2721
./biblepay-cli getblockhash 2721
068ac664afb4c3cf21137c50fe0e4496305d29a21fb682d1a164c49b08e9212d

999998.99983900 BBP left after running the associate command (had 1,000,000), so it used 1.00016100 BBP

===

So what ended up happening with that, I linked my Rosetta Account / CPID with that BiblePay Wallet?,
Is it just a certain address from the wallet? (the one that paid the burn fee?)
all current addresses of the wallet? future addresses generated by the wallet?

Will the address in this wallet be the one that receives funds from the daily superblock (assuming I did enough CPU research that day to get paid)?

What happens if I want to change the wallet that should receive the funds? Will I have to do the burn thing again but from the new/other wallet?

====

It looks like the BOINC tasks are these like 5 - 5 1/2 hour tasks that you have 8 days to complete,
Do you only get credit once  you complete a task? (My work done still says 0, but my tasks are each only 26-28% complete)

====

How many tBBP do I need for a test sanctuary? I think I remember reading 500,000?
http://wiki.biblepay.org/Create_Masternode#BiblePay_Sanctuaries_Setup_-_Linux_Server

Ok looks like 500,000 is correct:
https://github.com/biblepay/biblepay/blob/3c41da883d57d313febeed8129dae25d56195891/src/init.cpp#L1101
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 11:07:54 pm
./biblepay-cli exec associate togoshigekata@gmail.com XXXXXXXXX
{
  "Command": "associate",
  "E-Mail": "togoshigekata@gmail.com",
  "Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"
}

Im also on block 2721
./biblepay-cli getblockhash 2721
068ac664afb4c3cf21137c50fe0e4496305d29a21fb682d1a164c49b08e9212d

999998.99983900 BBP left after running the associate command (had 1,000,000), so it used 1.00016100 BBP


->  The rest is the TxFee the Miner gets to mine your Burn Tx

===

So what ended up happening with that, I linked my Rosetta Account / CPID with that BiblePay Wallet?,
Is it just a certain address from the wallet? (the one that paid the burn fee?)
all current addresses of the wallet? future addresses generated by the wallet?

->  You linked the biblepay wallet address (to receive rewards for dc computing) to rosetta.  Yes, one address, but not the one that paid the fee.
Please type exec getboincinfo to see which one the wallet chose.




Will the address in this wallet be the one that receives funds from the daily superblock (assuming I did enough CPU research that day to get paid)?

-> Yes, daily.  Since testnet has 1 min blocks, you should receive rewards a few times a day.  See exec getboincinfo for the superblock schedule.


What happens if I want to change the wallet that should receive the funds? Will I have to do the burn thing again but from the new/other wallet?
->  I am working on a LIFO system now, this will let you move your Rosetta CPID to another wallet.  In the mean time, the only way to move it is to copy wallet.dat to the new controller machine.  LOL.  That will be done before March though.

====

It looks like the BOINC tasks are these like 5 - 5 1/2 hour tasks that you have 8 days to complete,
Do you only get credit once  you complete a task? (My work done still says 0, but my tasks are each only 26-28% complete)

->  You only get credit once task is completed.  Your RAC will start rising hourly.  Im up to something like 200 rac.  Btw there are ways to choose smaller workunits on rosetta, but lets talk about that tomorrow as we should look at all their work types first.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 06, 2018, 11:10:47 pm
Thanks Rob, youre awesome!  8)
Look forward to testing more!

./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "Magnitude": 0,
  "LastSuperblockHeight": 2673,
  "NextSuperblockHeight": 2772
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 06, 2018, 11:13:28 pm
Thanks Rob, youre awesome!  8)
Look forward to testing more!

Thanks, you too.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 07, 2018, 01:46:30 am
I'm currently compiling on a fairly unique situation with an ARM64 processor.  I hope to have enough notes to walk through the process (and hope it is applicable to other ARM platforms) including using the BOINC command line tool exclusively.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 07, 2018, 03:15:15 am
Ahhh, I installed the new BBP wallet, went to testnet and all of my old tBBP were gone.
Could someone please send me a few so I can do a burn transaction?

Thanks :)

yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 07:09:31 am
Hi Rob,

I'm back from the previous time, since I saw the announcement for PoDC I stopped calculating the numbers for PoL, I've read the new proposol for PoDC and have some concerns.

First of all, I think it's a great idea to want to help scientific research, however I don't think the current proposel meets the criterea to remain a fair crypto currency. Relying on a single entity like BOINC to maintain a database of shares for mining even when verfied by a consensus system like masternodes would centralise the crypto currency and would allow hackers to unfairly edit the blockchain.

Not only does this open the risk for BiblePay to be compromised, it also makes BOINC a target for hackers looking to make money, you mention in the wiki that you the developer will intervere if something doesn't seem right in the BOINC data however this would still centralise the coin around you (not that I don't like you or trust you Rob it's just a bad idea from a security point of view).

The current proposal is untennable it centralises the blockchain in an unhealthy way around BOINC and the developer; Satoshi Nakamoto wrote Bitcoin the way it is because a crypto-currency should require no trust it should be verifiable and decentralised in my professional opinion the current proposal unfortunatly does not meet these criteria.

I am however a big fan of using blockchain technology to help scientific research, we could perhaps integrate such functionality in to the pool (subsidising those who do research), or perhaps we could open a contest to see what ideas the community have in order to further the goal of helping scientific research without bringing the network in danger.

Hi Swongel,

Thanks for the concerns.  Yes, I have addressed all of these (no new concerns posted here), and will give an opinion on each risk.

"I don't think the current proposel meets the criterea to remain a fair crypto currency. "
-> Assuming you mean using proof-of-dc as a consensus would not allow us to be mined fairly

"Relying on a single entity like BOINC to maintain a database of shares for mining even when verfied by
 a consensus system like masternodes would centralise the crypto currency and would allow hackers to unfairly edit the blockchain."

-> I've studied this for years now (no seriously, Ive beein a boinc researcher for over 5 years and used Gridcoin for mining for years before creating Biblepay), and have come to the conclusion the risk of hacking into the Rosetta SQL server is low.  (It has NOT happened to Gridcoin yet- all that happened to them was something to do with neural consensus security).  Also let us clarify 'single entity', as Rosetta has tens of management servers, and we gather the credits from the daily Rosetta credit dump files on their web farm, not from a single centralized entity other than Rosetta.  There is no way for me, Togo, any Biblepay admin to edit this file, and it is downloaded by 10% of Biblepays Sanctuaries and voted on by the Sancs, and it is downloaded from the Rosetta farm, not from a single entity.

In addition, I assert that the way we pull the daily total credit and RAC numbers, we could detect and eliminate most hacking attempts (where numbers have been modified, as the constituents per host wont add up to the last totals or avg RAC), and if a layman were to hack in to the Rosetta SQL credit servers, that is most likely what would happen.  I havent seen it happen yet. 

"it also makes BOINC a target for hackers looking to make money, you mention in the wiki that you the developer will intervere if something doesn't seem right in the BOINC data however this would still centralise the coin around you (not that I don't like you or trust you Rob it's just a bad idea from a security point of view).
"

I don't see a risk here, because Rosetta is serving millions of users, and the integrity of their SQL server is paramount.  If its been hacked, it will become obvious in our reports, as something will not match.  Id rather focus on writing reports that ensure all the numbers roll up correctly. 


In summary, I view the use of Rosetta/BOINC a good tool to divert wasted heat from POW mining to something useful, the RAC we harvest in the Sanctuary Quorum accurate per researcher, and very hard to hack (as hard as someone hacking into Kelloggs to change the cornflake text)

and finally this is the big one:
Comparing pure-POW, DC, and POL:  DC beats pure-POW with the botnet any day, as right now in Prod, using the holy grail of security (IE the Status Quo, Bitcoin-heat mining) we have 93% of our traffic being solved on an "anonymous botnet" some where between Russia and China and our pool of registered users only solves 7% of the traffic.  Meaning that technically 93% of our POW budget is going down the toilet.

Even if the DC system was hacked twice a year and I had some extravagant report detecting and kicking off anyone with more than 100 machines in cancer research I argue that would be 10* better than what we have (it would be over 90% accurate), we would have diverted 90% of the heat into useful science. 

And finally, its easier to be nimble with DC than with POW.  The cat & mouse game is almost impossible with a hard fork miner.  With DC we have years of work being poured into the CPU algorithm, that is almost impossible to duplicate the work unit scanning result of a protien fold.  What am I talking about?  Im saying that 100 developers spent 5 years of time and effort to stack libs on top of medical libs into the 79 meg EXE, to calculate the results of a protein fold.  Those results are sent to the rosetta server for analysis.  Rosetta only approves the work units that pass vigorous testing.  Thats like having a team of 100 devs + 10 admins running the decentralized "credit checking algorithm" of an advanced scientific cancer-mining system offloaded from our core.  Give it a chance, I think time will bear out the fruits of the system.

And finally there is no way for me to step in and edit anything - 10% of the sancs pull the file from Rosetta, and hash it, and vote on it.  All I can do is send a SPORK in to disable PODC (thats if we find out Rosetta was compromised).  Then I can re-enable it when we find the system is back up.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 07:54:00 am

Hi Rob,


"I don't see a risk here, because Rosetta is serving millions of users, and the integrity of their SQL server is paramount.  If its been hacked, it will become obvious in our reports, as something will not match.  Id rather focus on writing reports that ensure all the numbers roll up correctly.  "

This is not verifiable we'd have to take your word for it, also this still means the network will be centralised. Why even make a cryptocurrency if we're going to trust a centralised system we might as well just use VISA or MasterCard and simply donate 10% to orphans.
Allowing this change of the consensus algorithm would break the trustless nature of crypto currency as put forth by Satoshi Nakamoto as described in the original Bitcoin Whitepaper.

We cannot give up the fundamental principles of crypto currency to stop this bot net even if it would benefit scientific research it would be breaking the fundamental decentralised nature of crypto currency.

We cannot trust BOINC not to be hacked
We cannot trust BOINC not to alter results
We cannot trust BOINC not to block account
We cannot trust you or whomever soley to steer the blockchain (even if only intended in case of system failure).

Additionally this will make BOINC a target for hackers not only to infiltrate but also to  launch other exploits such as social engineering and denial of service attacks negatively impacting them especially when BiblePay will grow.

It is my professional opinion that a system wherein we depend on a third party for record keeping even if validated is fundamentally flawed and unsuitable for block chain consensus.

I would study the BOINC system a little more before fluffing them off as an entity that can be hacked.

I believe this system is going to maintain an accuracy level of 99.9% over time, and that as compared to pure-POW with a botnet stealing 93% of our valuable users hashpower is a 93% improvement.

I agree that POL may solve the botnet problem, but POL does not solve the heat problem, but Rosetta solves both.  So it still trumps both systems.

PODC is still the best for the future of Biblepay.

If there is an actual hacking target vector, please do the exact research on it and lets try to hack it.  There is not a high risk target hack vector here.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 07:58:32 am
It looks like Gridcoin is now #1 in the world (by RAC):

https://boincstats.com/en/stats/-1/team/detail/118094994/charts

With over 60,000 servers connected to BOINC.

What do you say if we give them a little healthy competition with Cancer Research boys?

#1 in the world:
https://boincstats.com/en/stats/-1/team/detail/118094994/overview


I think we can overtake the US Navy if we try.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 08:46:38 am

"If there is an actual hacking target vector, please do the exact research on it and lets try to hack it.  There is not a high risk target hack vector here."

We cannot trust this because we cannot verify this.
Trusting a single system is against the fundamentals of Crypto Currency:

I quote from Satoshi Nakamoto's Bitcoin white paper:

Trusting a single third-party is a violation of these fundamentals, I urge you to reconsider the ramifications this will have.

I argue that coinbase transactions (novel mining rewards) are a different animal than peer to peer transactions in the wallet.

Besides, we still have pobh for the core consensus for block security, however the lions share of the mining are airdropped in a superblock for PODC, to encourage cancer mining instead of scaling up the heat mining side.

I believe the tenants of Satoshis paper are still being upheld.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 09:08:39 am
The resource to print new Bible Pay, in this proposal partially delegated to BOINC is one of the resources which should be protected by the block chain, in this proposal this is not true therefor it breaks the tenants of Satoshi's white paper.

Further more this wouldn't stop bot nets since they could just as easily switch to the new BOINC alogrithm as well still keeping their current computing resources relative to the rest of the network.

Again trusting a third party for anything in the block chain it being the ability to print money, verify transactions or communications is against the fundamentals of the decentralised nature of block chain technology.

 

It is fine if botnets want to participate in cancer research.  And by giving the botnet a CPID and allowing us to see how many CPUs and CPUtypes and clockcycles and revisions are running it gives us valuable insight into the botnet, therefore, it is entirely different than we have now, and with that activity, I argue that it is beneficial, and no longer a nuisance, therefore I would not call it a botnet at that point. 

I jokingly say botnet because we have no control over their upgrades, however with Rosetta, they are at the mercy of using Rosetta, making my terminonly no longer refer to them as "nefarious" at that point.

Novel rewards through a daily superblock is not the same as minting.  Therefore this system is within the covenants of our design - and is an extension to what satoshi originally envisioned in the protocol.

Im sorry that you feel threatened by this idea for some reason, but I strongly believe the good in this outweighs the risk by a magnitude.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 07, 2018, 11:01:51 am
FoldingCoin - HackerNews
https://news.ycombinator.com/item?id=8962896

Gridcoin - The Bad
https://web-in-security.blogspot.ca/2017/08/gridcoin-bad.html
https://github.com/Erkan-Yilmaz/GRC/issues/34

How does GRC "securely" reward BOINC computations?
https://www.reddit.com/r/gridcoin/comments/5w4v4i/how_does_grc_securely_reward_boinc_computations/

"nevertheless destroyable by a malicious actor with reasonable funding, since it relies on a centralized service to distribute its data."
"there is some concern about Gridcoin's dependency on a second outside network (the various BOINC projects and statistics collections and so on) which could be an issue for people who believe that it negatively impacts Gridcoin's decentralization as compared to Bitcoin, which has no such external dependencies."
https://bitcoin.stackexchange.com/questions/37276/why-cant-bitcoin-switch-over-to-gridcoins-proof-of-work-system

Gridcoin vs Golem
http://www.natesimpson.com/blog/archives/2017/05/21/why-gridcoin-beats-golem-hands-down/

===

I definitely see Swongels point and agree with his reasoning about decentralization,

But also going along that line of thinking, how truly decentralized is Bitcoin?
Theres a group of devs called Bitcoin Core that control commit access,
theres no inherent way to pay the Devs from Bitcoin itself and so they get funding from outside investors/donators that most likely have strings attached,
theres also the issue of mining becoming more and more centralized with ASICs with a few major players/groups controlling the majority of the network hash power,
Is Bitcoin decentralized?

How secure is the hardware that runs miners and nodes and wallets? Are there government backdoors built in?
How many people actually read the code that gets added to Bitcoin, How many have the skill to understand it?
Could someone pay off/bribe/blackmail all the Bitcoin devs?
Could someone hack 51% of Bitcoin's 11,000 full nodes?

Could a supercomputer come about that makes SHA 256 obsolete? How soon would we know about it?
What if the internet and computer use becomes extremely censored and monitored?
What happens if electricity across the world gets shut down?
What if the government prints more money and buys 51% of the currency?

How much does the average cryptocurrency investor or average person truly understand and care about 100% decentralization?
Ethereum vs Ethereum Classic, Ripple vs Stellar

Also its kind of funny, whenever there are any issues in the crypto space (coin fork/clone, trade scam, coin scam, exchange scam, etc),
theres tons of people who want the government to step in or want to add regulation

Is rewarding scientific research worth the risk of some centralization?
Is there any way to reward science research without centralization?

Im still quite new to cryptocurrency and I only know a little, just thinking out loud, I look forward to learning more!

I think the mining cycles going towards research is pretty awesome,
though I am also slightly worried about potential security concerns,
but Im down to see how it plays out.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 07, 2018, 01:56:01 pm

Hi Rob,


"I don't see a risk here, because Rosetta is serving millions of users, and the integrity of their SQL server is paramount.  If its been hacked, it will become obvious in our reports, as something will not match.  Id rather focus on writing reports that ensure all the numbers roll up correctly.  "

This is not verifiable we'd have to take your word for it, also this still means the network will be centralised. Why even make a cryptocurrency if we're going to trust a centralised system we might as well just use VISA or MasterCard and simply donate 10% to orphans.
Allowing this change of the consensus algorithm would break the trustless nature of crypto currency as put forth by Satoshi Nakamoto as described in the original Bitcoin Whitepaper.

We cannot give up the fundamental principles of crypto currency to stop this bot net even if it would benefit scientific research it would be breaking the fundamental decentralised nature of crypto currency.

We cannot trust BOINC not to be hacked
We cannot trust BOINC not to alter results
We cannot trust BOINC not to block account
We cannot trust you or whomever soley to steer the blockchain (even if only intended in case of system failure).

Additionally this will make BOINC a target for hackers not only to infiltrate but also to  launch other exploits such as social engineering and denial of service attacks negatively impacting them especially when BiblePay will grow.

It is my professional opinion that a system wherein we depend on a third party for record keeping even if validated is fundamentally flawed and unsuitable for block chain consensus.

Hi Swongel,
Great to see you are passionate! I am not an expert in centralised/decentralised anything! But I just thought I'd add my two cents.

"We cannot give up the fundamental principles of crypto currency to stop this bot net"

For me I would say that we can't give up on our fundamental principles as Christians to help where we can, even at the cost of some centralisation. For me personally, if it is a choice between a level of centralisation and the ability to contribute to finding the cure for cancer, then I will always choose the latter.

I agree with you that the botnets could just simply switch over to boinc, but if they did so, at least they we are adding power to Rosetta. Also I hadn't thought of the point Rob raised, that they will lose some level of anonymity in doing so.   

Anyway, that is all I am able to add without passing my ability level!
Thanks for taking the time to read and I hope you will help us work out some of these issues.


p.s. thanks to whoever (Rob?) sent me some tBBP, I think I'm all going now :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on February 07, 2018, 03:16:05 pm
Updated the testnet explorer. Any reason there are blocks with 6k reward for miners and others with 600?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Swongel on February 07, 2018, 03:36:23 pm
FoldingCoin - HackerNews
https://news.ycombinator.com/item?id=8962896

Gridcoin - The Bad
https://web-in-security.blogspot.ca/2017/08/gridcoin-bad.html
https://github.com/Erkan-Yilmaz/GRC/issues/34

How does GRC "securely" reward BOINC computations?
https://www.reddit.com/r/gridcoin/comments/5w4v4i/how_does_grc_securely_reward_boinc_computations/

"nevertheless destroyable by a malicious actor with reasonable funding, since it relies on a centralized service to distribute its data."
"there is some concern about Gridcoin's dependency on a second outside network (the various BOINC projects and statistics collections and so on) which could be an issue for people who believe that it negatively impacts Gridcoin's decentralization as compared to Bitcoin, which has no such external dependencies."
https://bitcoin.stackexchange.com/questions/37276/why-cant-bitcoin-switch-over-to-gridcoins-proof-of-work-system

Gridcoin vs Golem
http://www.natesimpson.com/blog/archives/2017/05/21/why-gridcoin-beats-golem-hands-down/

===

I definitely see Swongels point and agree with his reasoning about decentralization,

But also going along that line of thinking, how truly decentralized is Bitcoin?
Theres a group of devs called Bitcoin Core that control commit access,
theres no inherent way to pay the Devs from Bitcoin itself and so they get funding from outside investors/donators that most likely have strings attached,
theres also the issue of mining becoming more and more centralized with ASICs with a few major players/groups controlling the majority of the network hash power,
Is Bitcoin decentralized?

How secure is the hardware that runs miners and nodes and wallets? Are there government backdoors built in?
How many people actually read the code that gets added to Bitcoin, How many have the skill to understand it?
Could someone pay off/bribe/blackmail all the Bitcoin devs?
Could someone hack 51% of Bitcoin's 11,000 full nodes?

Could a supercomputer come about that makes SHA 256 obsolete? How soon would we know about it?
What if the internet and computer use becomes extremely censored and monitored?
What happens if electricity across the world gets shut down?
What if the government prints more money and buys 51% of the currency?

How much does the average cryptocurrency investor or average person truly understand and care about 100% decentralization?
Ethereum vs Ethereum Classic, Ripple vs Stellar

Also its kind of funny, whenever there are any issues in the crypto space (coin fork/clone, trade scam, coin scam, exchange scam, etc),
theres tons of people who want the government to step in or want to add regulation

Is rewarding scientific research worth the risk of some centralization?
Is there any way to reward science research without centralization?

Im still quite new to cryptocurrency and I only know a little, just thinking out loud, I look forward to learning more!

I think the mining cycles going towards research is pretty awesome,
though I am also slightly worried about potential security concerns,
but Im down to see how it plays out.

Hi Togo,

I'll gladly answer some of your questions:

But also going along that line of thinking, how truly decentralized is Bitcoin?

"Theres a group of devs called Bitcoin Core that control commit access,
theres no inherent way to pay the Devs from Bitcoin itself and so they get funding from outside investors/donators that most likely have strings attached,
theres also the issue of mining becoming more and more centralized with ASICs with a few major players/groups controlling the majority of the network hash power,
Is Bitcoin decentralized?"

How do get open source developers paid for their work?
First of all I'll give you a link to a Wikipedia going into detail: https://en.wikipedia.org/wiki/Business_models_for_open-source_software
But personally I would use the reputation and experience from contributing to Bitcoin software in order to get jobs or provide services to companies interested in deploying Block Chain technology this can be very lucrative. (Companies such as Red Hat and Canoncical run off this business-model).

"theres also the issue of mining becoming more and more centralized with ASICs with a few major players/groups controlling the majority of the network hash power"

Yes, unfortunatly for Bitcoin ASICS make the amount of stakeholders in mining smaller than perhaps desirable, however there are still mutliple miners who all have the incentive to act in a good way there is an financial incentive for them not to join an attack (as they might lose mined bitcoins, Section 6 of the original Bitcoin white paper: https://bitcoin.org/bitcoin.pdf).


"How secure is the hardware that runs miners and nodes and wallets?"

Software security is defined by against which threat-model a system is protected, all Intel processors for instance contain Intel Managment Engine allowing for anyone with the key to take over.  However Bitcoin is ported to many different hardware types, hardware wallets running open-hardware MIPS processors for instance would be incredibly hard to remotely exploit. Nevertheless security will and can never be completely guarenteed (anyone who does lies), however this doesn't mean all threats are equal.

"How many people actually read the code that gets added to Bitcoin, How many have the skill to understand it?"

Many people have read the original Bitcoin client source code and audited it, however Bitcoin is not software it's a protocol; there are multiple implementations audited made by different people. Most are open source, some are not; this however means that the source code cannot be changed by a single person a change in protocol must be implemented by all software implementations of Bitcoin.

Anyone understanding C++ can read the C++ implementation of Bitcoin, there are however implementations availible in Java and Python (read more: https://www.reddit.com/r/Bitcoin/comments/213pxw/what_programming_language_is_bitcoin_written_in/)


"Could someone pay off/bribe/blackmail all the Bitcoin devs?"

Unlikely but not impossible, however if people decide that a new version of the protocol is harmful they can choose to fork (such as Bitcoin Cash and Bitcoin Gold) this way the coin splits in two with the community choosing which version they like best and choose to use that one.

"Could someone hack 51% of Bitcoin's 11,000 full nodes?"

Yes, one would have to hack 51% of the miners however, these miners all use different software in highly secured environments, if they were to be hacked they'd notice (by missing expected Bitcoins) and look in to the problem. One would have to do a great amount of hacking in order to get 51% of all the mining capacity hacked. (in contrast to just 1 instance when using a centralised system).


"Could a supercomputer come about that makes SHA 256 obsolete? How soon would we know about it?"

This is a really hard problem in Computer Science/Maths called P!=NP, In short all modern encryption and computer security depends on this rule being true. Breaking SHA256 (I would interpret as making it trivial to reverse the hashing operation) would have huge implications to all systems (not only crypto currency, but traditional finance, government, armed forces, etc.)


"What if the internet and computer use becomes extremely censored and monitored?"

If this happens, finance is no longer of importance, freedom of communication is a basic human right worth more than any monetary amount will ever be.


"What happens if electricity across the world gets shut down?"

Solar panels and wind mills will get more expensive, money will dissapear (I personally use very little cash these days anymore with electronic payment systems being wide spread). https://www.quora.com/What-percentage-of-the-worlds-money-is-digital


"What if the government prints more money and buys 51% of the currency?"

Crypto prices will rise during this buying, unless 51% chooses to sell their crypto for now useless and inflation torn fiat currency this cannot happen. https://www.economicshelp.org/blog/634/economics/the-problem-with-printing-money/


"How much does the average cryptocurrency investor or average person truly understand and care about 100% decentralization?
Ethereum vs Ethereum Classic, Ripple vs Stellar"

Less than they should, decentralised trustless consensus is the basis on which crypto currency is built. How many people understand encryption? Very few, many profit from it though removing encryption from online banking for example would negatively impact all users.
That's why people like me very much try to make noise when such a thing is planned.
People holding Bible Pay share my interest of keeping the coin decentralised regardless if they understand the underlying technology, if you're interested about why this is important I recommend reading the original Bitcoin white paper of watching a video going through it in layman terms. For example: https://www.youtube.com/watch?v=l9jOJk30eQs


"Is rewarding scientific research worth the risk of some centralization?"

No, this update might very realistically destroy the network which will have as a consequence that people will stop mining which will not only destroy the coin and take away money from orphans it will also make the added amount of compute power to research dissapear.

"Is there any way to reward science research without centralization?"

Yes, we could for example set another tithe for scientific research and donate the money to the project directly via the decentralised charity committee (master node voting). Directly rewarding researchers and allowing them to best allocate the funds to help scientific research.

I hope these answers clear up some of the questions you and others may have about this change and why there's a need to keep crypto currency decentralised.


 



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 07, 2018, 03:51:07 pm
How many tBBP should i send the the sanctuary wallet? I'm going to try doing a hot wallet sanctuary. Is the windows wallet ready yet? Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 03:53:30 pm
I haven't looked into how PDC is being implemented but I would agree with Swongel on the principle. It is not advisable for a decentralised trust system to be relying/trusting a single external system. Biblepay would then become quite centralised.

Its quite centralized now with a botnet, and quite decentralized with PODC mining.

Sorry to disagree, but obviously you dont understand what you are talking about.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 03:53:58 pm
How many tBBP should i send the the sanctuary wallet? I'm going to try doing a hot wallet sanctuary. Is the windows wallet ready yet? Thanks.
Its 500,000 in testnet.  Windows: No.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 07, 2018, 04:00:40 pm
The DC side doesn't really affect the blockchain though. If the DC side goes down, the blockchain is still running because the POW is what keeps it going. If there are safeguards in place to insure the magnitudes are truthful I don't see a problem. Plus, perhaps the software can auto switch to 100% POW if certain criteria are met.

I'm not really an expert so please correct me if I'm wrong.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 07, 2018, 04:03:46 pm
Its 500,000 in testnet.  Windows: No.

I recovered the 200k you sent me but I guess I will have to mine for more unless you can send me another 300k to yXbN5kN9kJiKNU5W7PGd4MFBe8rAM5baxF.

Thanks!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 04:08:12 pm
The DC side doesn't really affect the blockchain though. If the DC side goes down, the blockchain is still running because the POW is what keeps it going. If there are safeguards in place to insure the magnitudes are truthful I don't see a problem. Plus, perhaps the software can auto switch to 100% POW if certain criteria are met.

I'm not really an expert so please correct me if I'm wrong.


Thats exactly right.

Were going from using 12,000 computers that generate random numbers and have others check the number is actually lower than the target, to executing a cancer program, that was written by more devs than ever worked on bitcoin combined, and checking the results by a decentralized team with over 1 million host participants.  To me, that is more decentralized than our fledgling little PC base.

And yes, on the disaster recover, we fall back to pure POW if DC is down.

Like I said, we could get hacked once a month and have a higher accuracy ratio than we do with POW being distributed to 7% of our non-greed based network.

I'm going to be drawing the line with the bashing.  If you dont like the design of PODC you are going to need to find another community.

Its very obvious that Swongel is biased, as every answer to Togo was based on a one-sided view.  Christians are about compromising and giving and making it happen and working hard.  If I say that I will develop a NEW algorithm, then so be it.  If you are not with me on changing the rules and going against the grain then please, dont stick around and drag all the rest of us down. 

FIND A SOLUTION IF YOU THINK ITS TOO CENTRALIZED.  I DONT.  CANCER MINING IS A NET POSITIVE FOR BIBLEPAY.  THIS IS GOING TO SHOW WHEN WE VOTE ON IT, AND IT WILL BE A SANCTUARY VOTE.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 07, 2018, 04:10:34 pm
I recovered the 200k you sent me but I guess I will have to mine for more unless you can send me another 300k to yXbN5kN9kJiKNU5W7PGd4MFBe8rAM5baxF.

Thanks!

I sent 300k
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 04:21:17 pm
Togo: the two articles you posted with gridcoin hacks actually contain a pointer to the same hack.  That whole thing is inflated.
Its a replay attack.  All that actually was broken in gridcoin was the advertisement beacon relied on the blockhash for its nonce, and that allowed a hacker to send in a beacon as a "replay attack".  In practice, its not that easy, costs money, and is very apparent to the researcher that you stole from (as their rewards stop).  They fixed it within 1 day of lead dev being notified.

The main problem as I mentioned in the wiki that gridcoin has is their neural network has trouble emitting the daily magnitudes so I see forking and stuff, but from what I understand its pretty much under control now, but all of these issues they had are not flaws or vulnerabilities in either boinc or the boinc projects.  They are just growth pains in a very complicated crypto project, with new business logic.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 07, 2018, 04:28:16 pm
Hi all,

Please let's take a breath, a step back and remember that we are all brothers and sisters who love the Lord.

I was thinking about the falling back to PoBH mining in the case of an issue with boinc and I have a (possibly naive) suggestion. What do you think of

1. Create a proposal for voting, that we appoint a moderator between BiblePay and Rosetta (likely Rob, but could be voted on to be anyone who is "qualified"). This moderator has the power to suspend boinc payments to BBP users if it seems like something nefarious is going on. In this case mining reverts to 100% PoBH.
2. If the moderator suspends boinc payments then they must provide a full report to the community. There must be a proposal added before the next superblock with a solution to the issue, or we revert back to 100% PoBH until a solution can be determined

In theory we could vote on who that moderator is so it solves/reduces one aspect of the centralisation, or there could be a team of moderators...


What do you think?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 07, 2018, 04:58:21 pm
I'm not sure if you saw the question related to the variance in blocks reward.

I agree that the botnet is an issue and I think you and I talked about it extensively in slack at some point.

Now i think you're the one who doesn't know what he is talking about if you think there is such a thing as a single "un-hackable" system.  Even if there was, the people controlling that system are not! The more (financial) incentives you add to corrupt said system and the more likely someone is going to find a way to corrupt that system. That's the beauty of blockchain and decentralisation; you're not relying on a single system, entity, person.

Now we can argue about the probabilities for something like that to happen (which are higher than what you think they are) but I find it highly dangerous to dismiss that risk altogether. Also, it doesn't fix the centralisation issue of a powerful botnet, it is merely shifting it to BOINC which we can argue might be a better option...but it is still centralised.

The issue is not about PoDC going down or not, but PoDC potentially being corrupted.

As I said, we can argue if the risk is worth the potential reward which is a possible argument.

I don't think it is bashing but merely raising concerns about something so that we can all find a solution together.

Point taken on having to find a new community .

I think the real answer is which is more likely hackable?  A small coin with really only one or two principle coders and gatekeepers or a massive system already in use by thousands times more users with hundreds more developers?  Put another way, Gridcoin has a marketcap of $23 M, we have a market cap of <$1 M.  Gridcoins problems have not been due to BOINC but their own software.  BOINC gathers research which in private hands has the potential to be worth millions to billions in the hands of big pharma.  Yet, so far, no major issue with BOINC, Gridcoin is faltering due to their vulnerabilities and we're suffering with a botnet.   Right now we basically rely on Rob, if he put out a mandatory that drained everyone's wallets in 30 days, we'd likely not catch it.  So really, right now, we're far more vulnerable than BOINC.

The only other viable option is right now is PoL and I cannot see a way where it would effectively hamper the botnets without severely affecting new or small users (or really why it should be used with PoW and not just throw in the towel and move to pure PoS).  The problem is a CPU coin is too tempting a target to botnets, but is too important a goal to merely abandon.  PiVX tried to hamper the botnets and failed, and decided to shift to PoS.  Most other CPU coins quickly jump to GPU or fall into disuse before their value is enough to be targeted.  PoDC is the major chance to not have to be PoS (or de facto PoS) without making a central "mining hub" that is overseen by the Masternodes and protected through non-open source obfuscation.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 07, 2018, 06:38:49 pm
I'm having some trouble getting the masternode running.

masternode list-conf says:
  "masternode": {
    "alias": "t_1",
    "address": "35.227.54.27:40001",
    "privateKey": "...BCXZC",
    "txHash": "...ebda4",
    "outputIndex": "1",
    "status": "PRE_ENABLED"
  }

but masternode status says:
error code: -32603
error message:
This is not a masternode

How do I debug this? I'm using a hot wallet so I set up masternode.conf and biblepay.conf as below:

masternode.conf:
t_1 35.227.54.27:40001 ...BCXZC ...ebda4 1

biblepay.conf:
rpcuser=t
rpcpassword=x
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
logtimestamps=1
externalip=35.227.54.27
maxconnections=256
masternode=1
masternodeprivkey=...BCXZC

I'm also having trouble setting up the watchman:

[Errno 111] Connection refused
Cannot connect to biblepayd. Please ensure biblepayd is running and the JSONRPC port is open to watchman.

I have commented out the mainnet and un-commented testnet in watchman.conf
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 07, 2018, 06:42:35 pm
Thanks for the responses Spongel! I just got into cryptocurrency the end of this summer, this is all very interesting.
Ill have to spend some time and read the Bitcoin whitepaper.

On another note, a lot of the crypto community thinks Masternode coins are fairly centralized,
for example the head Bitcointalk Forum admin Theymos rejected us from his semi weekly banner auction (he doesnt allow ICOs)
"the architecture is maybe quite centralized (masternodes) perhaps it could be considered "an ICO with more steps""
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 07, 2018, 06:45:56 pm
(https://i.imgur.com/9fCvPnR.png) (https://i.imgur.com/DCcoSYL.png)

I had a BOINC screensaver pop up when I was idle, was cool to see,
You can also click on each task and theres a "Show graphics" command
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 07, 2018, 06:49:51 pm
I fired up two PCs for testnet. Will configure them tomorrow.

Personally, I think that the biggest thread for biblepay at this moment is the botnet (of which I'm almost totally sure it really exists). I also think that decentralization should be maintained where possible.

Sometimes is hard for me to see all the angles with problems like the botnet vs centralization. I'm reading everything, but I don't feel like I have enough expertise to really give good input.

And I think everyone in this topic is talking with good intentions.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 07:26:24 pm
"
If you decide to continue I ask you to announce a reasonable amount in advance as to give anyone wanting to fork off time to prepare, I might very well consider joining such an effort as it would line up better with my beliefs.

I hope the maintainers of the masternodes won't vote in favour of this proposal for reasons I have stated and we would be able to find a better way to help scientific research and or pursue other charitable actions.
"

Sorry to see you go, I take your input very seriously for POL.  For DC, your view is too constrained and biased to be taken seriously.

I think you have a certain belief system pegged with DC, and can't really envision it working the way I can.

For example, I think you believe Rosetta is a single "corporate" entity with 500 servers and an IT admin that might jack up his credits in BOINC.
However, its really 1 million global hosts who are taking turns turning in complex folding solutions through BOINC, and BOINC is so huge, as 616W just pointed out, that little tiny fish like us are not going to influence the SQL database.  Granted there is an SQL database where credits get updated, but there are over 1 million hosts in it along with us.

What I want to see is the complaint being escalated to me, such as :  How are we going to mitigate this particular centralization risk, and then we develop the IT solution that goes in biblepay to combat such issue.  To me, the issue is : analyzing the rolled up RAC, Total Credit Delta, Daily dump files, CPIDs, and at worst: putting some type of max CPU count cap on each CPID (so as to prevent one single CPID from hogging more than a 100 machine share), etc.   

But to argue that the current status quo with bitcoin is actually better than this is hilarious.  In my eyes, this system is so far superior to heat generating mining we should be a clear winner in the mainstream, and as I said on the other thread, pulling this off gives us intrinsic value.  And that is important, because if we securely check DC work units, from a black-box point of view, the community is far more valuable than bitcoin.

I can design a system that places a smart contract inside the researchers boinc account once per superblock, I can broadcast a payment from boinc back to biblepay once per day to prove that I am a cancer researcher with a certain UTXO  (for example placing a script with UTXOs inside the days
 boinc work), I dont really care what it takes, this is a creative effort.

As far as lead time:  Im shooting for going live with cancer-mining on March 31st, in Prod.  Ill enter the vote for this system before this Saturday.

So you have 50 days notice.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 07, 2018, 07:37:09 pm
Well, my oddball ARM64 machine won't support BOINC or at least not the rosetta project.

That said, one point that has been brought up on Slack is why do we not have separate Development and Production branches of Biblepay?  The heartache of the PoL payments showing up in main net would not occur, and rapid fire upgrades in Development aren't going to look bad on us like they do in Production.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 07:41:03 pm
Well, my oddball ARM64 machine won't support BOINC or at least not the rosetta project.

That said, one point that has been brought up on Slack is why do we not have separate Development and Production branches of Biblepay?  The heartache of the PoL payments showing up in main net would not occur, and rapid fire upgrades in Development aren't going to look bad on us like they do in Production.

Ok, cool,  I guess try a different device then.

To answer your question plainly:  We would not have POL at all, or DC at all if we had more than one branch.  Because I wouldnt be doing all this work.  It takes a lot of hours to maintain each branch. 

I guess we wouldnt have a pool either.

Hopefully you would rather have biblepay in its current form that not have biblepay.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: strayapple on February 07, 2018, 08:49:27 pm
just compiled 1.0.8.8 sourcecode,but can't sync blocks.
it's still not working after i added these node:
addnode=node.biblepay.org
addnode=vultr4.biblepay.org
addnode=vultr5.biblepay.org

any other node ?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 07, 2018, 10:03:01 pm
Figured it out, the testnet also uses the biblepay.conf in the /.biblepaycore folder, not the /.biblepaycore/testnet3 folder.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 07, 2018, 10:08:24 pm
Just got an error while sitting in console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE       
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"       
biblepay in ProcessMessages()       

It keeps coming up over and over again.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 07, 2018, 11:43:02 pm
Just got an error while sitting in console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE       
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"       
biblepay in ProcessMessages()       

It keeps coming up over and over again.

Hmm, do you have any special permissions set up or is biblepay running as root?

Try creating /home/biblepay/.biblepaycore/SAN and see if it goes away?

Ill check this issue out also...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 08, 2018, 12:11:01 am
HOW TO SETUP HOT TESTNET LINUX SANCTUARY (MASTERNODE)

References:
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/
http://wiki.biblepay.org/Create_Masternode#BiblePay_Sanctuaries_Setup_-_Linux_Server
http://wiki.biblepay.org/Create_Sanctuary_2

=====================================================

A. Setup Remote Linux Server
http://wiki.biblepay.org/Create_Sanctuary_2#PART_B_-_Rent_Linux_Cloud_Machine

B. Install, Run and Stop BiblePay
http://wiki.biblepay.org/Create_Sanctuary_2#PART_C_-_Install_Sanctuary_Linux_Wallet
https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

C. Set Wallet to Testnet
cd ~/.biblepaycore
vi biblepay.conf
testnet=1
:wq

cd home/biblepay/src
./biblepayd -daemon

=====================================================

1. Ask for 500,005 tBBP (test BiblePay) on the forum, post your address:
./biblepay-cli getaccountaddress ""

2. Create a new address to send escrow to:
./biblepay-cli getaccountaddress MN1

Copy the Address Output
yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo

3. Send 500,000 tBBP to escrow address:
./biblepay-cli sendtoaddress yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo 500000

Copy the TXID Output
da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772

4. Turn on mining for a few minutes to make blocks advance
./biblepay-cli setgenerate true 1
./biblepay-cli getinfo
./biblepay-cli getmininginfo
./biblepay-cli setgenerate false

5. Get the VOUT
./biblepay-cli masternode outputs

Copy the VOUT Output
1 or 0

6. Get the Private Key
./biblepay-cli masternode genkey

Copy the Private Key Output
92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

7. Stop BiblePay
./biblepay-cli stop

7. Add Sanctuary to masternode.conf
cd ~/.biblepaycore/testnet3
vi masternode.conf  (i insert, :wq to write and quit)

[SANCTUARY_ALIAS] SPACE [SANCTUARY_PUBLIC_IP:40001] SPACE [SANCTUARY_PRIVATE_KEY] SPACE [ESCROW_TXID] SPACE [ESCROW_VOUT]

MN1 34.208.206.95:40001 92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772 1

8 Add flags to biblepay.conf:
Note: I added same to both biblepay.conf files, in main folder and in testnet3

rpcuser=RandomUsername
rpcpassword=RandomPassword
rpcallowip=127.0.0.1
rpcport=9998
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
externalip=34.208.206.95
masternode=1
masternodeprivkey=92gwjXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

9. Open Ports in Firewall
sudo apt-get update
sudo apt-get install ufw
sudo ufw allow ssh/tcp
sudo ufw limit ssh/tcp
sudo ufw allow 40001/tcp
sudo ufw allow 9998/tcp
sudo ufw logging on
sudo ufw enable
sudo ufw status

10. Start masternode
./biblepay-cli masternode start-alias MN1
NOTE: Weird mine was already started somehow

11. Masternode Debugging
./biblepay-cli mnsync status
./biblepay-cli masternode list
./biblepay-cli masternode status

Wait for Masternode info to sync, AssetID 999 MASTERNODE_SYNC_FINISHED:
./biblepay-cli mnsync status

12. Install Watchman
sudo apt update
sudo apt -y install git python-virtualenv virtualenv
cd ~/.biblepaycore
git clone https://github.com/biblepay/watchman.git
cd watchman
virtualenv venv
venv/bin/pip install -r requirements.txt

13. Set Watchman to Testnet
vi watchman.conf
Comment network=mainnet  (add # in front)
Uncomment network=testnet (remove # in front)
:wq

cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py

Make sure this command gives no output and then add it to crontab

crontab -e

# i insert
* * * * * cd ~/.biblepaycore/watchman && ./venv/bin/python bin/watchman.py >/dev/null 2>&1
# :wq

14. Wait for Masternode Status to go from PRE_ENABLED to ENABLED,
turn on mining if no one is mining
./biblepay-cli masternode list

=====================================================

Let me know if this is correct, seems to be working for me so far, but Im still in PRE_ENABLED state
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 08, 2018, 12:28:41 am
Im also getting this message randomly in my console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE
boost::filesystem::last_write_time: No such file or directory: "/home/ubuntu/.biblepaycore/SAN/magnitude"
biblepay in ProcessMessages()

Try creating /home/biblepay/.biblepaycore/SAN and see if it goes away?

cd ~/.biblepaycore
ls SAN

Looks like SAN directory exists, but its empty, so I guess it cant write the magnitude file?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: strayapple on February 08, 2018, 02:12:13 am
Who can send me 1 test bbp to my address yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh

I wan to associate my boinc account with biblepay,but it said Balance too low to advertise DCC, 1 BBP minimum is required.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 08, 2018, 02:42:55 am
Who can send me 1 test bbp to my address yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh

I wan to associate my boinc account with biblepay,but it said Balance too low to advertise DCC, 1 BBP minimum is required.
I sent some. Hope it worked buddy!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: strayapple on February 08, 2018, 05:08:39 am
I sent some. Hope it worked buddy!
thanks very much,it worked!

"Results": "Successfully advertised DC-Key.  Type exec getboincinfo to find more researcher information.  Welcome Aboard!  Thank you for donating your clock-cycles to help cure cancer!"
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 07:42:05 am
Finally, windows is ready.  Turned out that "cancer" image caused all kinds of problems in the build. 

Summary of what has changed:

1.0.8.8p - Windows & Linux - Leisure for Testnet

- Since protocol version has been increased, you will need 1088p (Windows) to start/stop a 1088 sanctuary
- Added more features to the rpc command : exec getboincinfo.  It now loops through all your cpids, and shows the RAC of each cpid and the total magnitude.  It also finds the last superblock you were in and prints some info about that (like total payments).
- Added the ability to Re-Associate a CPID with a new wallet.  This is Only if you lose your wallet or want to move your CPID to a brand new wallet.  Most of the time if you keep your wallet.dat you will never want to do this.  But if lets say you throw away your old PC and move, and buy a new PC, yet your existing CPID has say 100,000 credits, and you just want to associate that old CPID with a brand new wallet, Biblepay would say "Already_In_Chain".  To perform this action type : exec associate rosetta_email rosetta_pass force.  This will forcefully kill the old burn transaction and reassociate you. 
- Note the windows wallet has a GUI for DC association.
- Fixed the issue 616w mentioned where we show the POL weight info in prod (removed in prod), and Also verified that DC is not visible in Prod

** I have not looked at the SAN/Magnitude ST13 error yet, I will be looking at that next **

** I apologize to everyone I offended.  I want to take a breather and start over, but I want you all to keep an open mind and give DC a chance before disregarding it.  Lets test it, Ill add a vote for it, and if it fails the litmus test and the vote Ill go back to supporting POL/POBH fully.  But until then I feel we have created a feature that is #1 in crypto, especially when you take into consideration the security issue that has been solved in Biblepay (Sanctuary Quorum) **
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 07:47:35 am
Finally, windows is ready.  Turned out that "cancer" image caused all kinds of problems in the build. 

Summary of what has changed:

1.0.8.8p - Windows & Linux - Leisure for Testnet

- Since protocol version has been increased, you will need 1088p (Windows) to start/stop a 1088 sanctuary
- Added more features to the rpc command : exec getboincinfo.  It now loops through all your cpids, and shows the RAC of each cpid and the total magnitude.  It also finds the last superblock you were in and prints some info about that (like total payments).
- Added the ability to Re-Associate a CPID with a new wallet.  This is Only if you lose your wallet or want to move your CPID to a brand new wallet.  Most of the time if you keep your wallet.dat you will never want to do this.  But if lets say you throw away your old PC and move, and buy a new PC, yet your existing CPID has say 100,000 credits, and you just want to associate that old CPID with a brand new wallet, Biblepay would say "Already_In_Chain".  To perform this action type : exec associate rosetta_email rosetta_pass force.  This will forcefully kill the old burn transaction and reassociate you. 
- Note the windows wallet has a GUI for DC association.
- Fixed the issue 616w mentioned where we show the POL weight info in prod (removed in prod), and Also verified that DC is not visible in Prod

** I have not looked at the SAN/Magnitude ST13 error yet, I will be looking at that next **

** I apologize to everyone I offended.  I want to take a breather and start over, but I want you all to keep an open mind and give DC a chance before disregarding it.  Lets test it, Ill add a vote for it, and if it fails the litmus test and the vote Ill go back to supporting POL/POBH fully.  But until then I feel we have created a feature that is #1 in crypto, especially when you take into consideration the security issue that has been solved in Biblepay (Sanctuary Quorum) **

That's great! Will test it out.

Thanks for apologizing, let's continue to work on this as a body.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 07:48:06 am
Im also getting this message randomly in my console:

************************
EXCEPTION: N5boost10filesystem16filesystem_errorE
boost::filesystem::last_write_time: No such file or directory: "/home/ubuntu/.biblepaycore/SAN/magnitude"
biblepay in ProcessMessages()

cd ~/.biblepaycore
ls SAN

Looks like SAN directory exists, but its empty, so I guess it cant write the magnitude file?

Before I break this, anyone who is having this issue, Id like to ask one test first.

Could you please go to the console and type 'exec dcc'
Then wait about 15 seconds and see what is in :
~/.biblepaycore/SAN

Please post the ls -l from that directory?

Also, please tell me if you are a sanc and if your 'masternode status' is enabled?  This procedure is only supposed to run on the "chosen sancs".  Those are the ones with a rank less than 10:1.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 07:54:12 am
Before I break this, anyone who is having this issue, Id like to ask one test first.

Could you please go to the console and type 'exec dcc'
Then wait about 15 seconds and see what is in :
~/.biblepaycore/SAN

Please post the ls -l from that directory?

Also, please tell me if you are a sanc and if your 'masternode status' is enabled?  This procedure is only supposed to run on the "chosen sancs".  Those are the ones with a rank less than 10:1.

list -l
total 0

Mine says enabled.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 07:55:09 am
By the way, I installed the new Windows wallet but I'm getting a smartscreen error saying the file is potentially dangerous.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 07:58:41 am
Thanks for the Hot Sanctuary guide Togo - so just to confirm - the Hot sanctuary is all you need in testnet.  We dont need to deal with starting and stopping those from the controller wallet or protecting the funds.

(Its a funny analogy that I envision the Controller wallet to be the only one running the POW-pobh algo in the next revision, but that is for prod.  The controller wallet would be your wallet to send/receive funds, run POBH on one thread, and start-stop sancs).

Alex asked a question yesterday about the rewards.
In Testnet, the Heat miners (if you solve a block with POBh) only receive about 550 BBP.  The Sanc reward is about 5500 BBP. 
The DC Reward is 1.2 MILLION per day divided by the researchers Share (This is equal to TotalDailyEmission minus 20% standard budget minus sanctuary rewards minus heat rewards).   All figures above assume that our normal 20% budget has been held back from every block (for the monthly budget).



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:01:40 am
By the way, I installed the new Windows wallet but I'm getting a smartscreen error saying the file is potentially dangerous.

Its possible that it massively changed enough for google to remove it from the safe cache list.  (I remember we needed 500 downloads originally to get in the list).

Its also possible the new image files triggered it - but they are only pngs. 

Whats interesting is all the new code has nothing to do with mining, so thats kind of strange, because proof-of-dc is all business logic.

All I can say is I just installed it and Im running it - and to possibly scan it, on a 3rd party site first, and let me know how the result is?

My build environment is *very* secure.  Nothing comes into it but the existing opensource builds, and no dependencies have changed.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:03:31 am
Its possible that it massively changed enough for google to remove it from the safe cache list.  (I remember we needed 500 downloads originally to get in the list).

Its also possible the new image files triggered it - but they are only pngs. 

Whats interesting is all the new code has nothing to do with mining, so thats kind of strange, because proof-of-dc is all business logic.

All I can say is I just installed it and Im running it - and to possibly scan it, on a 3rd party site first, and let me know how the result is?

My build environment is *very* secure.  Nothing comes into it but the existing opensource builds, and no dependencies have changed.

The cache may be what is causing it, I'm not too worried, just letting you know.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:09:09 am
list -l
total 0

Mine says enabled.

Thanks!  When you did the 'exec dcc' did it say 1?  Also could you please try again while tailing the log and see if there is a bug in there (an error)?

Thanks!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:09:19 am
Can I monitor the hot Sanctuary from my windows wallet? Do I just need to fill in biblepay.conf or masternode.conf or both? Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:13:29 am
Thanks!  When you did the 'exec dcc' did it say 1?  Also could you please try again while tailing the log and see if there is a bug in there (an error)?

Thanks!

Yes, it said 1.

Do you meen the debug.log?

2018-02-07 19:41:41 Biblepay Core version 1.0.8.8 (2018-02-07 07:42:02 -0600)
2018-02-07 19:41:41 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2018-02-07 19:41:41 ***************************************** BIBLEPAY  ***************************************************
2018-02-07 19:41:41 ProdMode: Prod 0.000000Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2018-02-07 19:41:41 BiblePayVersion 1.0.8.8 (2018-02-07 07:42:02 -0600)
2018-02-07 19:41:41 Using OpenSSL version OpenSSL 1.0.2g  1 Mar 2016
2018-02-07 19:41:41 Default data directory /home/biblepay/.biblepaycore
2018-02-07 19:41:41 Using data directory /home/biblepay/.biblepaycore/testnet3
2018-02-07 19:41:41 Using config file /home/biblepay/.biblepaycore/biblepay.conf
2018-02-07 19:41:41 Using at most 125 connections (1024 file descriptors available)
2018-02-07 19:41:41 Using 0 threads for script verification
2018-02-07 19:41:41 scheduler thread start
2018-02-07 19:41:41 HTTP: creating work queue of depth 16
2018-02-07 19:41:41 No rpcpassword set - using random cookie authentication
2018-02-07 19:41:41 Generated RPC authentication cookie /home/biblepay/.biblepaycore/testnet3/.cookie
2018-02-07 19:41:41 HTTP: starting 4 worker threads
2018-02-07 19:41:41 Creating backup folder /home/biblepay/.biblepaycore/testnet3/backups
2018-02-07 19:41:41 Using wallet wallet.dat
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:15:08 am
The error stopped by the way, haven't seen one today although there is still no file in SAN.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:19:54 am
Can I monitor the hot Sanctuary from my windows wallet? Do I just need to fill in biblepay.conf or masternode.conf or both? Thanks.
On the hot sanc, all you really have to do is send the collateral to yourself (the 500,000 even), then add:
masternode=1
masternodeprivkey=yyyyy

In the biblepay.conf, and leave the masternode.conf alone.  (On the testnet sanctuary itself).

You could monitor it in windows, but since testnet is so small I would just click on Sanctuaries on the windows wallet and look by IP.

I dont know if the hot sanc vout will be possible to add to your Win pc, but if you wanted to try : you would copy the 'masternode output' (from the sanctuary itself) TXID & VOUT n to your notepad, then construct the masternode.conf file on the windows PC to include it.  Probably not worth it as it might hose your prod file, etc.  I would just look for the sanc in the list.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:21:07 am
The error stopped by the way, haven't seen one today although there is still no file in SAN.

Hmm, trying to reproduce now by killing my setup...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:25:11 am
On the hot sanc, all you really have to do is send the collateral to yourself (the 500,000 even), then add:
masternode=1
masternodeprivkey=yyyyy

In the biblepay.conf, and leave the masternode.conf alone.  (On the testnet sanctuary itself).

You could monitor it in windows, but since testnet is so small I would just click on Sanctuaries on the windows wallet and look by IP.

I dont know if the hot sanc vout will be possible to add to your Win pc, but if you wanted to try : you would copy the 'masternode output' (from the sanctuary itself) TXID & VOUT n to your notepad, then construct the masternode.conf file on the windows PC to include it.  Probably not worth it as it might hose your prod file, etc.  I would just look for the sanc in the list.

Alright, I'm not going to try it. I literally spend all day setting up the testnet masternode yesterday. How many masternodes do we need? I can potentially host 10 of them by cloning but I don't want to do that until it's needed.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:27:38 am
Hmm, trying to reproduce now by killing my setup...

Aha!  Ok the st13 last_writetime_error is fixed for the next testnet version later today.

In the mean time, anyone who has either run into the problem , or never experienced the problem type:
exec dcc

You should see "1".
This fixes the problem temporarily until the next release.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:30:34 am
Aha!  Ok the st13 last_writetime_error is fixed for the next testnet version later today.

In the mean time, anyone who has either run into the problem , or never experienced the problem type:
exec dcc

You should see "1".
This fixes the problem temporarily until the next release.

Great! Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:31:11 am
Alright, I'm not going to try it. I literally spend all day setting up the testnet masternode yesterday. How many masternodes do we need? I can potentially host 10 of them by cloning but I don't want to do that until it's needed.

LOL, yeah the first couple I set up were tricky now for some reason they seem easy. 
Uhh, I would just be happy if you did a couple, because I think we only need 10 total sancs in testnet to prove the quorum side features are all working correctly, lets talk about that soon.
But in the mean time, I would definitely like to get 50 boinc cpids out here, because not only do I want to get a feel and give everyone a taste of what we would be doing, but also to test the superblock frequency and verify the payments per mangitude and all the security.

I have 2 running, so if you did 2 + Togos, we would be halfway there.

Ill start getting the commands to show what rules the sancs go through in the morning.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:33:25 am
Great! Thanks.
Actually a live quorum test might explain 75% of the process, since your DCC is working now.

Could you post the result of 'exec testvote'?

Your SAN directory should have something in it now - the Filtered file should be 1281 bytes (thats our Biblepay researcher list)

The exec testvote, file hash "filehash" for the DCC filehash, should be:
000000000000000000000000000000008d18b23d463c9e866cb5db0f02262506

?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:35:45 am
LOL, yeah the first couple I set up were tricky now for some reason they seem easy. 
Uhh, I would just be happy if you did a couple, because I think we only need 10 total sancs in testnet to prove the quorum side features are all working correctly, lets talk about that soon.
But in the mean time, I would definitely like to get 50 boinc cpids out here, because not only do I want to get a feel and give everyone a taste of what we would be doing, but also to test the superblock frequency and verify the payments per mangitude and all the security.

I have 2 running, so if you did 2 + Togos, we would be halfway there.

Ill start getting the commands to show what rules the sancs go through in the morning.

Sure, just let me know when. The only problem right now is I only have enough tBBP for one more. You have my e-mail, it's a headache trying to keep up with the forum. How many cpids are running right now?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:38:22 am
Sure, just let me know when. The only problem right now is I only have enough tBBP for one more. You have my e-mail, it's a headache trying to keep up with the forum. How many cpids are running right now?

Looks like 4 cpids.

Well I mean we could do it in 5 mins and make it a learning experience for everyone to understand the high security in place.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:40:48 am
Actually a live quorum test might explain 75% of the process, since your DCC is working now.

Could you post the result of 'exec testvote'?

Your SAN directory should have something in it now - the Filtered file should be 1281 bytes (thats our Biblepay researcher list)

The exec testvote, file hash "filehash" for the DCC filehash, should be:
000000000000000000000000000000008d18b23d463c9e866cb5db0f02262506

?

Hmm, it says:
error code: -1
error message:
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"

MY sanctuary is this one by the way:
"749df434020e56e87a48607eaa1cbd504fcc62eb90056a39d2d58c315b9ebda4-1": "ENABLED",
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:42:50 am
Actually a live quorum test might explain 75% of the process, since your DCC is working now.

Could you post the result of 'exec testvote'?

Your SAN directory should have something in it now - the Filtered file should be 1281 bytes (thats our Biblepay researcher list)

The exec testvote, file hash "filehash" for the DCC filehash, should be:
000000000000000000000000000000008d18b23d463c9e866cb5db0f02262506

?

Oh btw, the exec testvote, and all DCC file hash testing must be done on the hot sanc.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:43:35 am
Hmm, it says:
error code: -1
error message:
boost::filesystem::last_write_time: No such file or directory: "/home/biblepay/.biblepaycore/SAN/magnitude"

Which flavor OS is your hot sanc?  Also, do you now have a user file in /SAN?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:44:18 am
Oh btw, the exec testvote, and all DCC file hash testing must be done on the hot sanc.

Yes, I'm running all the commands on the hot sanctuary.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:46:45 am
Which flavor OS is your hot sanc?  Also, do you now have a user file in /SAN?

Still no file. Ubuntu 16.04.3 LTS, kernel version 4.13.0-1008-gcp.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 08:50:33 am
Still no file. Ubuntu 16.04.3 LTS, kernel version 4.13.0-1008-gcp.

Hmm, I just remembered something, there is a very complex command in the DCC Filter, something that is done in QT (otherwise we need a new lib in headless, and the exchanges dont like unecessary libs on their native machines) so I did it in QT.. Im thinking, we may need to have you run your hot sanc in -qt mode.  Do you have graphics on that ubuntu box, and can you launch the hot sanc like this:
./biblepay-qt -testnet

?

Need to rule that out.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 08:53:55 am
Hmm, I just remembered something, there is a very complex command in the DCC Filter, something that is done in QT (otherwise we need a new lib in headless, and the exchanges dont like unecessary libs on their native machines) so I did it in QT.. Im thinking, we may need to have you run your hot sanc in -qt mode.  Do you have graphics on that ubuntu box, and can you launch the hot sanc like this:
./biblepay-qt -testnet

?

Need to rule that out.

I can try, it's on a VPS so I need to install x on it or something. I'll let you know.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 09:06:27 am
I can try, it's on a VPS so I need to install x on it or something. I'll let you know.

Yeah, I installed graphics on all my VMS, that would make this easier.  Thanks!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 09:16:14 am
Rob,

This is interesting because now for the people that were running Rosetta already, they just need to install the wallet and link their CPID. They can now turn their number crunching into money if so desired. In fact, it is so easy to install the wallet that it's a no brainer. If half of the computational power signs up for Biblepay, what do you estimate the payout to be for one normal computer? Like an i5 or i7 processor. I'm thinking the payout will be very small then.

I have one suggestion, since you have contacts with the people behind BOINC. Can you e-mail then to have some of them install the wallet? That would probably get you many CPIDs on the testnet fast adn it doesn't really cost them anything.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 10:34:57 am
Yeah, I installed graphics on all my VMS, that would make this easier.  Thanks!

Rob, I just realized this will take a while since i have to recompile to source code with QT.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 11:36:43 am
Rob,

This is interesting because now for the people that were running Rosetta already, they just need to install the wallet and link their CPID. They can now turn their number crunching into money if so desired. In fact, it is so easy to install the wallet that it's a no brainer. If half of the computational power signs up for Biblepay, what do you estimate the payout to be for one normal computer? Like an i5 or i7 processor. I'm thinking the payout will be very small then.

I have one suggestion, since you have contacts with the people behind BOINC. Can you e-mail then to have some of them install the wallet? That would probably get you many CPIDs on the testnet fast adn it doesn't really cost them anything.

Yeah, I know, thats why Im so frustrated.  We dont enforce the team, and we would have a huge legion of 50,000+ researchers who would gladly make BBP for crunching, and it would grow the coin for good.  Its such a huge no brainer.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 11:48:51 am
Rob,

This is interesting because now for the people that were running Rosetta already, they just need to install the wallet and link their CPID. They can now turn their number crunching into money if so desired. In fact, it is so easy to install the wallet that it's a no brainer. If half of the computational power signs up for Biblepay, what do you estimate the payout to be for one normal computer? Like an i5 or i7 processor. I'm thinking the payout will be very small then.

I have one suggestion, since you have contacts with the people behind BOINC. Can you e-mail then to have some of them install the wallet? That would probably get you many CPIDs on the testnet fast adn it doesn't really cost them anything.


I have a few other suggestions too that could propel us to the top and silence a lot of naysayers, but I cant do it all myself, so some of these I will hold til we hire the devs:

- Recompiling our own custom version of boinc with our custom biblepay-cancer graphics
- Integrating boinc code into biblepay-qt
- One click set up with no questions for the user
- Making the rosetta cancer-miner part of biblepay pobh algorithm inside the wallet , IE one program
- Adding a POL script into each rosetta workunit, thereby making rewards based slightly on POL + cancer research
(Might help us in the sense that we can filter out future cancer botnet)
- Reconciling a researcher embedded UTXO in a cancer workunit back to daily Magnitude reports
(This would prove each researchers indivdual wallet has some coin*age in it, would be really great for integrity)

This stuff would be massive....

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 01:29:19 pm
Rob,

When I try to run -qt through the vnc session i get Invalid MIT-MAGIC-COOKIE-1 keyQXcbConnection: Could not connect to display :1.0.

Do you know how to fix this?

Thanks.

-tmike
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 01:51:14 pm
Rob,

When I try to run -qt through the vnc session i get Invalid MIT-MAGIC-COOKIE-1 keyQXcbConnection: Could not connect to display :1.0.

Do you know how to fix this?

Thanks.

-tmike
Hi Mike,

I didnt have that, but I see someone else did here :

https://bbs.archlinux.org/viewtopic.php?id=230828

Rob

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 02:21:22 pm
Hi Mike,

I didnt have that, but I see someone else did here :

https://bbs.archlinux.org/viewtopic.php?id=230828

Rob

Figured it out, had to start the vncserver from the same account as the biblepay daemon.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 02:25:06 pm
Figured it out, had to start the vncserver from the same account as the biblepay daemon.


Oh awesome, good.  Would you like to test it now?

masternode status
Should return Active?

Then post 'exec testvote'

Your on the latest, 1088q correct?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 02:27:35 pm

Oh awesome, good.  Would you like to test it now?

masternode status
Should return Active?

Then post 'exec testvote'

Your on the latest, 1088q correct?

I'm having a slight problem because I used a new wallet. The force command doesnt seem to be working when using my old rosetta account. it still says already in chain. ie. exec associate email pass force
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 02:29:33 pm
I'm having a slight problem because I used a new wallet. The force command doesnt seem to be working when using my old rosetta account. it still says already in chain. ie. exec associate email pass force

Try changing force to true.  I might have not interpreted the word correctly.

In the mean time Ill check.

EDIT: Yeah, try associate email pass true

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 02:33:54 pm
Try changing force to true.  I might have not interpreted the word correctly.

In the mean time Ill check.

EDIT: Yeah, try associate email pass true

Odd, says RPC error. Going to install watchman first.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 02:37:08 pm
I'm having a slight problem because I used a new wallet. The force command doesnt seem to be working when using my old rosetta account. it still says already in chain. ie. exec associate email pass force

Actually this will be a good exercise (to know if force works).  I just did it along with you.

Now we need to ensure it worked.  After 3 confirms, type 'exec listdccs'.  That shows the CPID's in the chain.
Please verify you are only in the list once?  (Look at the first 32 bytes for a CPID match).

To find your cpid type 'exec getboincinfo' first.

Btw, biblepay works with multiple cpids now also.  Its not recommended, but I have 2 so Im testing with 2.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 02:38:37 pm
Odd, says RPC error. Going to install watchman first.

I think that means it could not send the 1.1 bbp out.  Is wallet unlocked and unencrypted and has funds available?  Try
sendtoaddress BBPAddress 1
Also, see if that command actually sends?

(Where bbpaddress is To You)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 02:39:08 pm
Actually this will be a good exercise (to know if force works).  I just did it along with you.

Now we need to ensure it worked.  After 3 confirms, type 'exec listdccs'.  That shows the CPID's in the chain.
Please verify you are only in the list once?  (Look at the first 32 bytes for a CPID match).

To find your cpid type 'exec getboincinfo' first.

Btw, biblepay works with multiple cpids now also.  Its not recommended, but I have 2 so Im testing with 2.

I'm getting RPC error when i ran the force associate with true. Let me see if watchman will run. If it doesn't work I'll just create another account first.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 02:40:35 pm
I think that means it could not send the 1.1 bbp out.  Is wallet unlocked and unencrypted and has funds available?  Try
sendtoaddress BBPAddress 1
Also, see if that command actually sends?

(Where bbpaddress is To You)

That's probably it. I have exactly 500k in the new account. It still says my new mastermode is pre_enabled but I'm getting a lot of rewards right now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 02:42:54 pm
That's probably it. I have exactly 500k in the new account. It still says my new mastermode is pre_enabled but I'm getting a lot of rewards right now.

Yeah, 500k is auto-locked for hot sanc.  Whats your address, Ill send?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 02:49:08 pm
Yeah, 500k is auto-locked for hot sanc.  Whats your address, Ill send?

Is there an easier way to communicate? I have a lot now, sending to self. Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 02:55:45 pm
Actually this will be a good exercise (to know if force works).  I just did it along with you.

Now we need to ensure it worked.  After 3 confirms, type 'exec listdccs'.  That shows the CPID's in the chain.
Please verify you are only in the list once?  (Look at the first 32 bytes for a CPID match).

To find your cpid type 'exec getboincinfo' first.

Btw, biblepay works with multiple cpids now also.  Its not recommended, but I have 2 so Im testing with 2.

Ok both commands work and I confirmed my CPID is only in the list once.

And by the way there are now 3 files in the SAN folder.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 03:15:38 pm
Ok both commands work and I confirmed my CPID is only in the list once.

And by the way there are now 3 files in the SAN folder.
I'm trying to help train Togo as we go LOL, he might write some of this up.

exec testvote

Lets see file hash stuff

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 03:20:48 pm
I'm trying to help train Togo as we go LOL, he might write some of this up.

exec testvote

Lets see file hash stuff


21:19:05

exec testvote


21:19:05

{
  "Command": "testvote",
  "fileage": 1574,
  "filehash": "00000000000000000000000000000000b612b685f313b46becb5447a7904e81e",
  "contract": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "pam_hash": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "govobjhash": "b7122d5d7aea5b0b872a78ced81be1186a135639dd5d62d51579ba70363de404",
  "Addresses": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh|yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc|yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "Amounts": "345363.23|165460.56|288066.03|433193.99|153915.19",
  "pam_hash2": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "votes_for_my_contract": 3,
  "contract1": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "RequiredVotes": 1,
  "last_superblock": 4356,
  "next_superblock": 4455,
  "next_superblock_triggered": true,
  "vote1": true,
  "vote1error": "",
  "serial": "",
  "verified_sigs": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 03:58:28 pm

21:19:05

exec testvote


21:19:05

{
  "Command": "testvote",
  "fileage": 1574,
  "filehash": "00000000000000000000000000000000b612b685f313b46becb5447a7904e81e",
  "contract": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "pam_hash": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "govobjhash": "b7122d5d7aea5b0b872a78ced81be1186a135639dd5d62d51579ba70363de404",
  "Addresses": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh|yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc|yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "Amounts": "345363.23|165460.56|288066.03|433193.99|153915.19",
  "pam_hash2": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "votes_for_my_contract": 3,
  "contract1": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "RequiredVotes": 1,
  "last_superblock": 4356,
  "next_superblock": 4455,
  "next_superblock_triggered": true,
  "vote1": true,
  "vote1error": "",
  "serial": "",
  "verified_sigs": 0
}

Sweet, working perfectly.

You have the same filehash as me (b612).
I see 3 of our sancs have voted for this file for the next superblock (block 4455).

Now just wait until 4456, then type exec getboincinfo, and see if your payment was in 4455, as long as you have magnitude >0.
What is your magnitude?

I have to jump outside while its light, be back in a couple hours.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 04:19:34 pm
Sweet, working perfectly.

You have the same filehash as me (b612).
I see 3 of our sancs have voted for this file for the next superblock (block 4455).

Now just wait until 4456, then type exec getboincinfo, and see if your payment was in 4455, as long as you have magnitude >0.
What is your magnitude?

I have to jump outside while its light, be back in a couple hours.

Magnitude is 0 right now. I have been running Rosetta but I think you mentioned it only updates once a day. My RAC is 93.76 at the moment.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 05:31:14 pm
Magnitude is 0 right now. I have been running Rosetta but I think you mentioned it only updates once a day. My RAC is 93.76 at the moment.

Yeah, not sure when their distributed linux servers dump the new file, but about an hour after that our Sancs will pick up the changes and start voting it in.  At that point your in-client magnitude will rise above 0.

In getboincinfo, and in the Distributed Computing tab UI.  Its also on the front page now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 08, 2018, 06:35:03 pm
Okay, I think I got my first testnet rig up and running. Everything went smooth and easy. Great work Rob!

Code: [Select]
01:19:19

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yZxWkM7dpwbuuiUPUhysRENzGVCUM5S4DT",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "NextSuperblockHeight": 4554,
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 0,
  "LastSuperblockHeight": 4455,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}

Will start a sanctuary testnet rig in the beginning of next week.

Sorry if I missed this, but the controller wallet needs to be up and running at all times, right?

Also, I've been following the discussion between you (Rob) and Swongel on bitcointalk. He is - also - a knowledgeable guy in my opinion, but I understand why you call it FUD. I liked that you posted the 'FUD rules' post, with an example of an unbiased statement, because that explained to me why you called Swongels posts FUD, where at first I didn't see it.

I'm not knowledgeable enough on the subject to have any worthwhile input, but I'm studying everything so I can make an as much informed decision as possible.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 08, 2018, 06:43:06 pm
Okay, I think I got my first testnet rig up and running. Everything went smooth and easy. Great work Rob!

Code: [Select]
01:19:19

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yZxWkM7dpwbuuiUPUhysRENzGVCUM5S4DT",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "NextSuperblockHeight": 4554,
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 0,
  "LastSuperblockHeight": 4455,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}

Will start a sanctuary testnet rig in the beginning of next week.

Sorry if I missed this, but the controller wallet needs to be up and running at all times, right?

Also, I've been following the discussion between you (Rob) and Swongel on bitcointalk. He is - also - a knowledgeable guy in my opinion, but I understand why you call it FUD. I liked that you posted the 'FUD rules' post, with an example of an unbiased statement, because that explained to me why you called Swongels posts FUD, where at first I didn't see it.

I'm not knowledgeable enough on the subject to have any worthwhile input, but I'm studying everything so I can make an as much informed decision as possible.

You only need the controller wallet to activate the sanctuary. later you can close it.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 08, 2018, 06:53:13 pm
Okay, I think I got my first testnet rig up and running. Everything went smooth and easy. Great work Rob!

Code: [Select]
01:19:19

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yZxWkM7dpwbuuiUPUhysRENzGVCUM5S4DT",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "NextSuperblockHeight": 4554,
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 0,
  "LastSuperblockHeight": 4455,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}

Will start a sanctuary testnet rig in the beginning of next week.

Sorry if I missed this, but the controller wallet needs to be up and running at all times, right?

Also, I've been following the discussion between you (Rob) and Swongel on bitcointalk. He is - also - a knowledgeable guy in my opinion, but I understand why you call it FUD. I liked that you posted the 'FUD rules' post, with an example of an unbiased statement, because that explained to me why you called Swongels posts FUD, where at first I didn't see it.

I'm not knowledgeable enough on the subject to have any worthwhile input, but I'm studying everything so I can make an as much informed decision as possible.

Thanks.  Well the issue is it affects the ability to invest appropriately.  Im definitely not here to misrepresent Biblepay, but when I argue points I am careful to be honest and neutral.  Swongel is smart, but he is approaching this entirely from an atomic perspective, but I argue there are many ways to make third party distributed computing systems more trustable, like for example if biblepay had 5 reference machines running rosetta, maybe we pay a reward to audit the reference machines (sort of like testing the scales), etc.  We can put a code in random work units and audit them.  Etc.  The upside to the endeavor is huge, the current quality of the status quo is low.  What are we putting trust in now on the mining side?  That the coins are dissapearing?



EDIT:  Im glad you are up and running!  Great!


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 08, 2018, 11:36:13 pm
COMPILED NOTES:

==============================
===== Proof of Distributed Computing (PODC)

How to Get Started with Distributed-Computing:
http://wiki.biblepay.org/Distributed_Computing_Start_Guide

Distributed Computing:
http://wiki.biblepay.org/Distributed_Computing

BOINC Team BiblePay:
https://boinc.bakerlab.org/rosetta/team_display.php?teamid=15044
https://boincstats.com/en/stats/-1/team/detail/831912762/overview


Testnet Thread:
http://forum.biblepay.org/index.php?topic=108.msg1362#msg1362

Testnet Block Explorer:
https://testnet.biblepay-explorer.org



==============================
===== A. Install Rosetta

== Linux GUI

http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu

apt-get install boinc-manager boinc-client

Click Activites >>> Search >>> Boinc >>> Run Boinc >>> Add Rosetta - Use existing User

== Windows

https://boinc.berkeley.edu/download_all.php

1. Click on Recommended Version - Install the 9.56 Meg version without VirtualBox (VirtualBox is not necessary)

NOTE: If you do not trust the software, you may install the Virtual Box Version - this runs the miner in a sandbox, but it runs slower and is a 98 meg download

After Installing BOINC Manager will open

2. "Choose a project" >>> Select "Rosetta@home"

3. "Identify your account" >>> Create an account

4. Set your Nickname

5. "Find a team" >>> Search for "BiblePay"



==============================
===== B. Setup BiblePay in Testnet

1. Install BiblePay
Windows: http://biblepay.org/#wallets-section
Linux: https://www.reddit.com/r/BiblePay/comments/6ummuj/how_to_mine_biblepay_on_linux/

2. Run BiblePay in Testnet
Add testnet=1 in biblepay.conf or can run exe/daemon with -testnet flag

NOTE: Testnet has its own folder inside of /.biblepaycore named /testnet3

3. Check if Synced on Correct chain:

getblockhash 2576

8ad6d439bb77b4304a34497183a16e4256f39dce990906f97e89ac602dcd4a50

4. (OPTIONAL) Clean out old chain data

Bottom of post - "CLEAN UP AFTER INSTALL"
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/



==============================
===== C. Link BOINC Account to BiblePay

=== GUI
Go to Distributed Computing page, and type in the rosetta user & password and click associate.

=== Command Line
exec associate rosetta_email_address rosetta_password


Then wait for 6 blocks for confirm to occur. 
Then type 'exec getboincinfo'
If everything worked, your CPID will match the one in notepad.


NOTE: "Please wait 24 hours to see yesterdays boinc RAC and magnitude in Biblepay"


How to re-associate my CPID to a new wallet?

This is Only if you lose your wallet or want to move your CPID to a brand new wallet.
Most of the time if you keep your wallet.dat you will never want to do this.
But if lets say you throw away your old PC and move, and buy a new PC, yet your existing CPID has say 100,000 credits, and you just want to associate that old CPID with a brand new wallet, Biblepay would say "Already_In_Chain". 
To perform this action type:

   exec associate rosetta_email rosetta_pass force

This will forcefully kill the old burn transaction and reassociate you. 



==============================
===== D. (OPTIONAL) Setup Sanctuary (Masternode) in Testnet

500,000 tBBP Collateral/Escrow Required

1. Setup Hot Sanctuary
http://forum.biblepay.org/index.php?topic=108.msg1444#msg1444


NOTE: "the Hot sanctuary is all you need in testnet. We dont need to deal with starting and stopping those from the controller wallet or protecting the funds."

NOTE: "On the hot sanc, all you really have to do is
send the collateral to yourself (the 500,000 even), then add:
masternode=1
masternodeprivkey=yyyyy

In the biblepay.conf, and leave the masternode.conf alone. 
(On the testnet sanctuary itself)."

NOTE: If anyone is mining in prod and wants to run testnet side by side your prod masternode, just do this:

./biblepay-qt -testnet -masternode=0 -rpcport=45000

That will allow it to boot side by side without taking your prod node down.


2. Run in QT (GUI) Mode

NOTE: QT (GUI) is needed for PODC SanctuaryQuorum, sanctuaries must execute QT functions to process the Rosetta credits files.

TMIKE: I'm running the sanctuary on a shared vCPU with 0.6GB of ram and using xfce.
Try this (I used vncserver in place of tightvnc): https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-16-04

ROB: Im still using vultr for my sancs, so what I did is installed graphics on the machine (using Mike-Ts similar info post),
then I just VNC in using the inbuilt vnc viewer (they have a link to VNC viewer on each server in the web list).

===

? ? ?

exec getboincinfo

exec testvote

exec listdccs


==============================
===== E. FAQ:

1) How do I find out how much RAC (recent average credit) my CPID has for Rosetta?

Go to the BOINC manager (on your PC), click on Projects, and on the row with Rosetta, take a look at the RAC field.

That is the number Biblepay uses to calculate your Magnitude in the wallet once per day.


2) How do I view my CPID and magnitude in the wallet?

A. The first way is to click the Distributed Computing tab in the GUI and view the bottom left "CPID" and"Magnitude" values.(This requires 1.0.8.8i+).

B. The second way is to click on the RPC, and type 'exec getboincinfo'

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 08, 2018, 11:58:01 pm
Hi,
i need some help from you.
I've tried to set up testnet and roseta@home, but I wasn't success.
I have WIN QT 1.0.8.8.q wallet. First there was problem that I hadn't login for roseta, so I've downloaded Boinc manager and create acc within the app. I saw a Biblepay group on roseta@home, so I think that it is good, but...
When i try to login to distributed computing within wallet it give me error mesage:
(https://i.snag.gy/kKw3aN.jpg)
I gave there mail and password from BOINC and then click on "Add me as Distributed Computer Researcher".
Is it possible to put login info into biblepay.conf?
I saw Togo's manual right now, so it seems, that I've made it correctly.
Thanks a lot.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 08:03:22 am
any tBBP yfeQhLLmTapeZCJG4pQt2NJjzKMJ2ha2RA


thanks....i try it
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:04:07 am
It appears the magnitude is still not updating.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:07:03 am
any tBBP yfeQhLLmTapeZCJG4pQt2NJjzKMJ2ha2RA


thanks....i try it

Sent. Let me know if you are setting up a testnet sanctuary.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:16:39 am
Latest testvote:

14:07:35

exec testvote


14:07:35

{
  "Command": "testvote",
  "fileage": 2234,
  "filehash": "00000000000000000000000000000000b612b685f313b46becb5447a7904e81e",
  "contract": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "pam_hash": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "govobjhash": "44ef150a01e62829383c017a540121a84b52312a70e2a8266b1e2f2354d2fbaa",
  "Addresses": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh|yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc|yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "Amounts": "345363.23|165460.56|288066.03|433193.99|153915.19",
  "pam_hash2": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "votes_for_my_contract": 2,
  "contract1": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "RequiredVotes": 1,
  "last_superblock": 5049,
  "next_superblock": 5148,
  "next_superblock_triggered": true,
  "vote1": true,
  "vote1error": "",
  "serial": "",
  "verified_sigs": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 08:19:32 am
thanks: received 700k

i wanna try BOINC system mining:

are you have problem with masternode setuping?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:20:11 am
Hi,
i need some help from you.
I've tried to set up testnet and roseta@home, but I wasn't success.
I have WIN QT 1.0.8.8.q wallet. First there was problem that I hadn't login for roseta, so I've downloaded Boinc manager and create acc within the app. I saw a Biblepay group on roseta@home, so I think that it is good, but...
When i try to login to distributed computing within wallet it give me error mesage:
(https://i.snag.gy/kKw3aN.jpg)
I gave there mail and password from BOINC and then click on "Add me as Distributed Computer Researcher".
Is it possible to put login info into biblepay.conf?
I saw Togo's manual right now, so it seems, that I've made it correctly.
Thanks a lot.


Thats awesome you got it working.  So what was the actual root of the problem why couldnt it sign your cpid?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:21:11 am
thanks: received 700k

i wanna try BOINC system mining:

are you have problem with masternode setuping?

You can just boinc mine if you want, adding a sanc is optional.  Im running a hot sanc.  They are extremely easy to set up.  Just follow togos hot sanctuary instructions.

The main thing we need to test is how people like Rosetta mining, and checking the rewards and seeing the magnitude.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:22:42 am
It appears the magnitude is still not updating.

Good morning, just getting checked in here.

Could you please check all your mags, could you please paste the 'exec getboincinfo?' The other cosmetic mags in the client pull off of that last value.
The other thing I wonder, on your rosetta cpid, what is your rac up too?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:25:15 am

Thats awesome you got it working.  So what was the actual root of the problem why couldnt it sign your cpid?

Orbis, looking at the code, it looks like that happens when you either have your wallet encrypted and locked, Or if you modified the code to hide your boinc private key somehow (the one it signs with).... LOL, doesnt seem like this can happen to a "normal" user.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 08:27:08 am
You can just boinc mine if you want, adding a sanc is optional.  Im running a hot sanc.  They are extremely easy to set up.  Just follow togos hot sanctuary instructions.

The main thing we need to test is how people like Rosetta mining, and checking the rewards and seeing the magnitude.
that BOINC sw is need open in tray? cos that SW loading my CPU 100% and my mining is stoped, i have to shut down it?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:29:49 am
Latest testvote:

14:07:35

exec testvote

Code: [Select]
{
  "Command": "testvote",
  "fileage": 2234,
  "filehash": "00000000000000000000000000000000b612b685f313b46becb5447a7904e81e",
  "contract": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "pam_hash": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "govobjhash": "44ef150a01e62829383c017a540121a84b52312a70e2a8266b1e2f2354d2fbaa",
  "Addresses": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb|yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh|yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc|yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "Amounts": "345363.23|165460.56|288066.03|433193.99|153915.19",
  "pam_hash2": "00000000000000000000000000000000a7eda64161e7a14caec32800e29c0df9",
  "votes_for_my_contract": 2,
  "contract1": "yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,ca895b47aacffbdbf906201821af2f9f,249.18<ROW>yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb,c9085154b7cc0ca2b5189672559dd6d8,119.38<ROW>yZ7Gqa8sikKsT8L211JRRqur1LEZXPZ1Nh,4004b7fec94751f61fe9135977bac553,207.84<ROW>yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc,93138f032bdd027fa3246b48bb715a77,312.55<ROW>yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh,8f273b30f8e0a298ed26e242762df701,111.05<ROW>\n",
  "RequiredVotes": 1,
  "last_superblock": 5049,
  "next_superblock": 5148,
  "next_superblock_triggered": true,
  "vote1": true,
  "vote1error": "",
  "serial": "",
  "verified_sigs": 0
}


Ok, yes, the b612 looks good, looks like we are the only ones voting on it ( My hot sanc + Mikes hot sanc).


Guys - we need to ask the hot sancs to run in ./biblepay-qt mode so we can expand our SanctuaryQuorum.

Id like to see more like 6-7 votes on the daily file, so we can prove some of the ground rules, like Am I in the 10% of the Quorum, and also, so I can increase the minimum testnet quorum level for a better test in the next release.

So anyone running the hot sanc in headless mode, can you please switch over to running in ./biblepay-qt (GUI) mode?

This is because the hot sanc must execute QT functions to process the Rosetta credits files.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:32:03 am
that BOINC sw is need open in tray? cos that SW loading my CPU 100% and my mining is stoped, i have to shut down it?
Boinc has a plethora of options to control if it behaves by minimizing in the tray or as a service, and many CPU throttling functions.

You have to go to preferences.  For example I have my dev machine set to use 50% of the processing power only if the computer is Not busy.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 08:39:29 am
my 4 rewards is 599
magnitude=0
i set 25% for BOINC

hmmm.... so 75% will be mining for BBP and 25% for 3D protein WASHINGTON UNIVERSITY, right?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:48:18 am
my 4 rewards is 599
magnitude=0
i set 25% for BOINC

hmmm.... so 75% will be mining for BBP and 25% for 3D protein WASHINGTON UNIVERSITY, right?

David Baker started it (at Univ of Washington) now its this project as a whole:
https://en.wikipedia.org/wiki/Rosetta@home

You have to wait til your Rosetta "RAC" (average-work done in boinc) is > 1, let us know when you have some Boinc RAC

Basically, the daily budget for Rosetta rewards is about 1.2 Million.  Thats what we pay the heat miners now.
The heat miners drop to 10% of that, Rosetta gets the rest in this scenario.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:57:45 am
Good morning, just getting checked in here.

Could you please check all your mags, could you please paste the 'exec getboincinfo?' The other cosmetic mags in the client pull off of that last value.
The other thing I wonder, on your rosetta cpid, what is your rac up too?


14:53:58

exec getboincinfo


14:53:58

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yiqLtGKtrDykVqrFREoZ8B5mhRE66s4cw8",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "NextSuperblockHeight": 5148,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 170.18,
  "LastSuperblockHeight": 5049,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}

I'm at 170.18 in the BOINC app.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 09:09:54 am

14:53:58

exec getboincinfo


14:53:58

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yiqLtGKtrDykVqrFREoZ8B5mhRE66s4cw8",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "NextSuperblockHeight": 5148,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 170.18,
  "LastSuperblockHeight": 5049,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}

I'm at 170.18 in the BOINC app.

Hi Mike,

Is this you T Compustick?

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

So right now it shows 0 RAC in the Rosetta project for you .
This is normal, because your local client gets more feedback from the work - queue machine immediately to appease the local user.
However, the back-end of boinc works off of backlogged distributed info.  We also "latch" on to that info to create our daily magnitude file to make this more resilient. That explains why we still have 0 RAC and hence 0 Mag in the local Biblepay client for you.

I wanted to mention, there is a way to cattle prod more RAC quicker, but it only works sometimes (as boinc network throttles requests to like one per hour), so you can try: click on the UPDATE button in Boinc after highlighting rosetta, then after its done go back to the URL i pasted above and see if any RAC appears in your account.


If that works let me know and I can tell you how Biblepay reacts to that situation.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 09:14:45 am
Hi Mike,

Is this you T Compustick?

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

So right now it shows 0 RAC in the Rosetta project for you .
This is normal, because your local client gets more feedback from the work - queue machine immediately to appease the local user.
However, the back-end of boinc works off of backlogged distributed info.  We also "latch" on to that info to create our daily magnitude file to make this more resilient. That explains why we still have 0 RAC and hence 0 Mag in the local Biblepay client for you.

I wanted to mention, there is a way to cattle prod more RAC quicker, but it only works sometimes (as boinc network throttles requests to like one per hour), so you can try: click on the UPDATE button in Boinc after highlighting rosetta, then after its done go back to the URL i pasted above and see if any RAC appears in your account.


If that works let me know and I can tell you how Biblepay reacts to that situation.

Rob, that's my other account. I will create a new CPID whenever I have a new machine up and running so we can have more CPIDs in the system. The one that I posted for BOINC info is https://boinc.bakerlab.org/rosetta/show_user.php?userid=1981209, which in the getboincinfo actually does give me a RAC value.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 09:17:02 am
Can someone send me 300k tBBP? I want to start a masternode but don't have enough:
ySW8n3Ld4x7SMPTsnFbzKAwKbwbmku7woe
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 09:20:11 am
Code: [Select]
16:18:39

exec getboincinfo


16:18:40

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "yZxWkM7dpwbuuiUPUhysRENzGVCUM5S4DT",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "NextSuperblockHeight": 5148,
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 82,
  "LastSuperblockHeight": 5049,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}

points total: 832
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 09:20:45 am
Can someone send me 300k tBBP? I want to start a masternode but don't have enough:
ySW8n3Ld4x7SMPTsnFbzKAwKbwbmku7woe

Done.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 09:23:27 am
Done.

That was fast! Thx :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 09:25:53 am
That was fast! Thx :)

No problem, The more people set up sanctuaries the better.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 09:33:30 am
Rob, am I missing something here or is there something wrong with these stats.

The top one, E5-2630 v2 @ 2.60GHz gets 3x times the amount of GFLOPS/core. And then when you go down the list the i5's are beating the i7's?

https://boinc.bakerlab.org/rosetta/cpu_list.php
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 09, 2018, 09:33:43 am

Ok, yes, the b612 looks good, looks like we are the only ones voting on it ( My hot sanc + Mikes hot sanc).


Guys - we need to ask the hot sancs to run in ./biblepay-qt mode so we can expand our SanctuaryQuorum.

Id like to see more like 6-7 votes on the daily file, so we can prove some of the ground rules, like Am I in the 10% of the Quorum, and also, so I can increase the minimum testnet quorum level for a better test in the next release.

So anyone running the hot sanc in headless mode, can you please switch over to running in ./biblepay-qt (GUI) mode?

This is because the hot sanc must execute QT functions to process the Rosetta credits files.

Ok so sanctuaries need to run as GUI (QT),
With Windows I just use Remote Desktop,
For Linux I will have to google solution, and hopefully 1GB RAM Vultr server will support GUI?

Quick search, I am seeing many solutions: xRDP, VNC, X11, Blackbox, Ubuntu Desktop, Any recommended?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 09:35:30 am
Ok so sanctuaries need to run as GUI (QT),
With Windows I just use Remote Desktop,
For Linux I will have to google solution, and hopefully 1GB RAM Vultr server will support GUI?

Quick search, I am seeing many solutions: xRDP, VNC, X11, Blackbox, Ubuntu Desktop, Any recommended?

Shouldn't be too hard to set up. I'm running the sanctuary on a shared vCPU with 0.6GB of ram and using xfce.

Try this (I used vncserver in place of tightvnc): https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-16-04

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 09:58:19 am
Rob, that's my other account. I will create a new CPID whenever I have a new machine up and running so we can have more CPIDs in the system. The one that I posted for BOINC info is https://boinc.bakerlab.org/rosetta/show_user.php?userid=1981209, which in the getboincinfo actually does give me a RAC value.
Oh good, OK, so your rosetta account ending in 1981209, it has a CPID that is in 'list dccs', has RAC in the rosetta web URL but so far 0 magnitude in Biblepay?  Yeah, that sounds like the normal 24 hour lag issue, where Rosetta has not dumped the unix file yet (that we vote on), so to find out for sure, just go to your SAN directory and do 'cat filtered', and see if your CPID is in that list.  If its missing, this is just the 24 hour rosetta lag.

We can succintify, or sanctify all this later by A) Adding another Info variable to getboincinfo, and B) Asking Togo to summarize this in a sentence such as "Please wait 24 hours to see yesterdays boinc RAC and magnitude in Biblepay" but of course we want to make sure things are working perfectly first.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 10:02:30 am
Ok so sanctuaries need to run as GUI (QT),
With Windows I just use Remote Desktop,
For Linux I will have to google solution, and hopefully 1GB RAM Vultr server will support GUI?

Quick search, I am seeing many solutions: xRDP, VNC, X11, Blackbox, Ubuntu Desktop, Any recommended?

Yeah, believe me I will go out of my way to try to get this magfilter working on headless, but the issue is not small, so for now this is still the best course, is to ask half of our prod sanctuaries to run in ./biblapy-qt mode if-when this system is deployed to prod.

Im still using vultr for my sancs, so what I did is installed graphics on the machine (using Mike-Ts similar info post), then I just VNC in using the inbuilt vnc viewer (they have a link to VNC viewer on each server in the web list).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 10:03:16 am
only 599 rewards for block?
i have to be 24hours on mining?

stil dont understand how it working .... any schema?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 10:09:50 am
only 599 rewards for block?
i have to be 24hours on mining?

stil dont understand how it working .... any schema?

What are you trying to acheive? The BBP you see is from PoBH mining and is right. You will not see the Rosetta rewards until a day or 2 later.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 10:11:42 am
thx MIKE, this i had to listen.....and will be any rewards for ROSETTA? didnt know ...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 10:20:16 am
Okay, my GUI mode masternode is set-up and in 'PRE-ENABLED' mode  :)

Everything seems to be working.

Also getting the 'exception' others reported btw:
Code: [Select]
EXCEPTION: N5boost10filesystem16filesystem_errorE       
boost::filesystem::last_write_time: No such file or directory: "/home/jaap-ubuntu/.biblepaycore/SAN/magnitude"       
biblepay in ProcessMessages()

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 10:21:44 am
thx MIKE, this i had to listen.....and will be any rewards for ROSETTA? didnt know ...

Yes 10% will be for PoW, 90% for PoDC (Rosetta). 10% of +-6000 is +-600, and that's what you are mining.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 10:25:45 am
Rob, am I missing something here or is there something wrong with these stats.

The top one, E5-2630 v2 @ 2.60GHz gets 3x times the amount of GFLOPS/core. And then when you go down the list the i5's are beating the i7's?

https://boinc.bakerlab.org/rosetta/cpu_list.php

Hi Mike,

Consider these two aspects also in that list:
1) The list is an average of gigaflops measured per machine per core, but no indication how long each machine runs per day.  So in this case, I could see the i5's beating the i7's if those particular owners run them 24-7.  (This is just a guess).  Feel free to research this more.

2) Although I have been fervently searching for people who run rosetta on a GPU and cannot find any evidence of GPU on rosetta, please feel free to search, It is possible Rosettas complex protein folding software libs may run better on machines with certain graphics coprocessor brands.
I searched for the top dog out of the 48,000 hosts, who accumulates More RAC in his class take a look at this guy:
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=2301665

Look at the Coprocessors Row:
Coprocessors   NVIDIA GeForce GTX 750 Ti (2048MB) driver: 388.13 OpenCL: 1.2

It could very well be that those machines with Nvidia GeForce video cards crunch 4-5* faster than those without, even though the software is not specifically using a GPU.  This is a new world of expirimentation and learning.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 10:31:09 am
Okay, my GUI mode masternode is set-up and in 'PRE-ENABLED' mode  :)

Everything seems to be working.

Also getting the 'exception' others reported btw:
Code: [Select]
EXCEPTION: N5boost10filesystem16filesystem_errorE       
boost::filesystem::last_write_time: No such file or directory: "/home/jaap-ubuntu/.biblepaycore/SAN/magnitude"       
biblepay in ProcessMessages()

1) Great!  We are getting there now, this is heating up!  I see 7 or so team members have also joined.

2) I thought we fixed this in 1088q,  btw are you running 1088q with this one?

3) If so,please type 'exec dcc', then cd to ~/.biblepaycore/SAN
lets see if you have a magnitude file now?

If so I may need to add one more line of code.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 10:33:12 am
1) Great!  We are getting there now, this is heating up!  I see 7 or so team members have also joined.

2) I thought we fixed this in 1088q,  btw are you running 1088q with this one?

3) If so,please type 'exec dcc', then cd to ~/.biblepaycore/SAN
lets see if you have a magnitude file now?

If so I may need to add one more line of code.

Oops, haha! I'm still on the older version. Will update.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 10:33:49 am
Ok so sanctuaries need to run as GUI (QT),
With Windows I just use Remote Desktop,
For Linux I will have to google solution, and hopefully 1GB RAM Vultr server will support GUI?

Quick search, I am seeing many solutions: xRDP, VNC, X11, Blackbox, Ubuntu Desktop, Any recommended?
Awesome guide btw Togo, thanks!

Hey, did your exec getboincinfo ever start showing magnitude for you?  Lets let these guys understand when the mag rises in the client?

For me it took about 24 hours. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 10:39:38 am
Quote
17:38:54
exec getboincinfo
17:38:55
{
  "Command": "getboincinfo",
  "CPID": "b4da941b1677220ab7dbb8701b3da10c",
  "Address": "yfeQhLLmTapeZCJG4pQt2NJjzKMJ2ha2RA",
  "CPIDS": "b4da941b1677220ab7dbb8701b3da10c;",
  "NextSuperblockHeight": 5247,
  "b4da941b1677220ab7dbb8701b3da10c_RAC": 0,
  "LastSuperblockHeight": 5148,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 09, 2018, 10:40:11 am
./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "Magnitude": 312.55,
  "LastSuperblockHeight": 5148,
  "NextSuperblockHeight": 5247
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 10:55:20 am
./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "Magnitude": 312.55,
  "LastSuperblockHeight": 5148,
  "NextSuperblockHeight": 5247
}

I have about the same magnitude (360).  So since you have magnitude, you should have received about 31% of the rewards in the last superblock.
Did you have a 330,000 reward in last superblock?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 11:00:03 am
Awesome guide btw Togo, thanks!

Yes, absolutely! Thanks Togo.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 11:11:07 am
Hi Mike,

Consider these two aspects also in that list:
1) The list is an average of gigaflops measured per machine per core, but no indication how long each machine runs per day.  So in this case, I could see the i5's beating the i7's if those particular owners run them 24-7.  (This is just a guess).  Feel free to research this more.

2) Although I have been fervently searching for people who run rosetta on a GPU and cannot find any evidence of GPU on rosetta, please feel free to search, It is possible Rosettas complex protein folding software libs may run better on machines with certain graphics coprocessor brands.
I searched for the top dog out of the 48,000 hosts, who accumulates More RAC in his class take a look at this guy:
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=2301665

Look at the Coprocessors Row:
Coprocessors   NVIDIA GeForce GTX 750 Ti (2048MB) driver: 388.13 OpenCL: 1.2

It could very well be that those machines with Nvidia GeForce video cards crunch 4-5* faster than those without, even though the software is not specifically using a GPU.  This is a new world of expirimentation and learning.

Rob, do you know if the Measured floating point speed on the stat page is for 1 processor or for 32 as he has? According to the cpu list that CPU should be getting 3 GFLOPS per core and that processor has 8 cores. If that score is per core then he is right on target.

Now if I click on applications list, you can see every instance is about 3 GFLOPS. I'm wondering if he has 1 instance on each core because that would be right.

On cpubenchmark.net:
Dual E5-2630 v2 - 16,123
Dual Xeon X5660 - 11,719

Both of these have 6 cores but the score on the cpu list for a 6 core E5-2630 v2 is 338 GFLOPS and a 12 core X5660 is 175 GFLOPS. That makes the E5-2630 v2 4 times faster then the X5660 which doesn't make any sense. I think the number of cores for the E5-2630 v2 is listed wrong, should be 12. Is there someone you can ask about that? Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 09, 2018, 11:23:55 am
I have about the same magnitude (360).  So since you have magnitude, you should have received about 31% of the rewards in the last superblock.
Did you have a 330,000 reward in last superblock?

How do I check the superblock?

I had 1 million tBBP starting out, and now I have  about 7.85 million tBBP, I have only mined a few minutes, so I assume the rest is from Research

./biblepay-cli getgovernanceinfo
{
  "governanceminquorum": 1,
  "masternodewatchdogmaxseconds": 57600,
  "proposalfee": 5.00000000,
  "superblockcycle": 1435,
  "lastsuperblock": 4305,
  "nextsuperblock": 5740
}

https://testnet.biblepay-explorer.org/block/4305
https://testnet.biblepay-explorer.org/tx/18611b21c5c0b024cf168a6cc4b79563d9aacb02c916498f9117ef414b3d21d4

Oh wait we have daily superblocks right?

My testnet sanctuary (masternode) address is: yh4nfiwoS94uqR7yMibib6UDe7kqxXRyCe

My masternode in masternode list: "da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772-1"

Im looking through blocks, mostly see 599BBP payouts: https://testnet.biblepay-explorer.org/blocks

I do see a 5,997 payout at block 5148 and 5136

./biblepay-cli listaddressgroupings

      "yNBPNx4EtgrMSpe6AbYkc5711Jd1bB1c6b",
      499996.99974740

      "yZ6E3AZkkiqNdv2LyzYYQDQtvHjqRw4Hpn",
      7199.34000000

      "yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo",
      2055036.92236124,
      "MN1"
https://testnet.biblepay-explorer.org/address/yaSJC1njhL6aMgVcVSUFLVujegXDG73uYo

      "ydye9XwJiHvRVDqgxxsM3cxssfBWgLAVmK",
      7799.55000000

      "yentn3QieYbHpDTSVRctMTttEGoqAtyV7o",
      6599.70000000

      "ygg9E71X7gfB7ep258kuQNhYvwvGzb1vyq",
      5999.40000000

      "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
      5285715.08000000,
https://testnet.biblepay-explorer.org/address/yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc

Removed all the 0 addresses


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 11:49:44 am
How do I check the superblock?

I had 1 million tBBP starting out, and now I have  about 7.85 million tBBP, I have only mined a few minutes, so I assume the rest is from Research

./biblepay-cli getgovernanceinfo
{
  "governanceminquorum": 1,
  "masternodewatchdogmaxseconds": 57600,
  "proposalfee": 5.00000000,
  "superblockcycle": 1435,
  "lastsuperblock": 4305,
  "nextsuperblock": 5740
}

https://testnet.biblepay-explorer.org/block/4305
https://testnet.biblepay-explorer.org/tx/18611b21c5c0b024cf168a6cc4b79563d9aacb02c916498f9117ef414b3d21d4

Oh wait we have daily superblocks right?

My testnet sanctuary (masternode) address is: yh4nfiwoS94uqR7yMibib6UDe7kqxXRyCe

My masternode in masternode list: "da2c3baaec7206bc1ea01df1f230e4c4dfa77a5a37ce3a9bf3a078078664c772-1"

Im looking through blocks, mostly see 599BBP payouts: https://testnet.biblepay-explorer.org/blocks

I do see a 5,997 payout at block 5148 and 5136

Hi Togo,
Looks like you are running an old version, cause 1088q+ shows payments in 'exec getboincinfo.
The  5997 payment is the masternode payment.  The large # of 599 payments is pow-pobh-heat miner payments.

Your Large Payment of 300K or so per payment should be in your transaction list somewhere, going to the Wallet address associated with the cpid. You can see that address in 'exec getboincinfo. 


Hey Guys, now that I need to ensure everyone is on 1089 in prod (or less than 1088) so we can get prod voting working, I had to check in 1089 which is the "old" protocol version.  Now I cant connect in testnet.

Could everyone please Upgrade to 1089 , especially sancs?

We need to anyway as there is a rule change in 1089 requiring 2 Or More sanctuaries in Testnet to agree on the SanctauryQuorum vote.  (Before it was just 1 to get us started).


Thanks,
Rob

EDIT: Windows is almost ready... standby about 30 more mins for windows...



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 11:58:50 am
Im trying to go back through and answer anything I missed:

1) Daily Superblocks and payment frequency:
In Prod its set for Daily, @202 blocks per day.  Remember we are going to adjust the DGW width in Prod to give us 7 min superblocks, so that should be daily in prod.
However in testnet, our blocks are 1 minute, so we really have about 6 superblocks per day in testnet. 

But we can still verify the exact accuracy, by looking at individual superblocks.  We should verify:  Are we hitting all of them, are the amounts correct and are the totals correct.

2) How to look at a superblock:  After exec getboincinfo, then you know the last superblock height.

Type 'showblock lastsuperblockheight'
Get the first coinbase txid from the showblock into clipboard
Type
getrawtransaction txid 1
Look at each payment

Ensure block is > 1 million payout, then you know its a superblock.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 12:16:24 pm
Rob, do you know if the Measured floating point speed on the stat page is for 1 processor or for 32 as he has? According to the cpu list that CPU should be getting 3 GFLOPS per core and that processor has 8 cores. If that score is per core then he is right on target.

Now if I click on applications list, you can see every instance is about 3 GFLOPS. I'm wondering if he has 1 instance on each core because that would be right.

On cpubenchmark.net:
Dual E5-2630 v2 - 16,123
Dual Xeon X5660 - 11,719

Both of these have 6 cores but the score on the cpu list for a 6 core E5-2630 v2 is 338 GFLOPS and a 12 core X5660 is 175 GFLOPS. That makes the E5-2630 v2 4 times faster then the X5660 which doesn't make any sense. I think the number of cores for the E5-2630 v2 is listed wrong, should be 12. Is there someone you can ask about that? Thanks.

Hi Mike, Ill probably be able to put some time and effort into building a faster personal rosetta miner over here in a couple months but for now its probably best to post this in the Rosetta forum.  Now that you have a Rosetta-boinc account you can post it there.  Im trying to push out the workload a little to everyone now so we can grow to be a professional org.   The people from boinc wont reply to this as they have gone into retirement, but the community is large and thriving.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 12:41:20 pm
Scholarly Assumptions regarding Cancer-Mining:

1- With the CPID-heat-mining rule, the botnet is busted, as you must have a CPID with RAC to heat mine in the future.
2- An unbanked person in a 3rd world country can potentially mine on an ARM-tablet or ARM-cellphone, and earn enough to buy a loaf of bread, without owning a home PC, each week.
3- With PODC enabled and POL disabled and CPID-heat-mining (with POBH of course) enabled, the rich do not get richer, but instead wealth is
 transferred to cancer researchers.

I think the unnoticed effect here, #2, is tightly aligned with our humanitarian mission for the unbanked.

It is even possible, if our value rises, with currencies that are worth 10* less that the unbanked may make more money from BBP cancer mining than they do in hard labor.  Dont some countries pay $.50 cents an hour for minimum wage?  Thats $28 a week.  I argue that it is *possible* to feed a whole family if cancer mining pays $100 a month. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 01:05:26 pm
I see someone just upgraded to 1089 (I have one 1089 peer), can I ask a favor, could you please type :
showblock 5228
And paste what is in 'blockmessage'?
Im trying to implement the botnet busting rule in testnet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 09, 2018, 01:16:28 pm
./biblepay-cli getinfo
{
  "version": 1000809,


./biblepay-cli showblock 5228
{
  "hash": "abe2b88fcf2505896d298cc87e1e5973521232f5d6af1ee097ec1173bfd073bb",
  "confirmations": 8,
  "size": 1615,
  "version": 536870912,
  "merkleroot": "a65f1111d885d724417a228d043d0c83e85b42aef315b869f59805a46f8a321a",
  "tx": [
    "04a0fd4c6794e68eba2f16dc8d731c65fe228b3eea288457f7606a19c70333c9",
    "9dbcb31961ab09fc341818942d2a0144c811bbb5fe5f582f6c34b2c06c5ee33e"
  ],
  "time": 1518202881,
  "height": 5228,
  "mediantime": 1518198342,
  "difficulty": 0.02803181858428088,
  "chainwork": "00000000000000000000000000000000000000000000000000000073b95df414",
  "hrtime": "02-09-2018 19:01:21",
  "nonce": 5494,
  "bits": "1d23ac57",
  "subsidy": 599,
  "blockversion": "1.0.8.9",
  "masternodereward": 1399860000000,
  "previousblockhash": "e3b542c31394ccf6c7d16cd0f7cdcc7959dcac6099ffc3a2f017962770f5decf",
  "blockmessage": "",
  "satisfiesbiblehash": "true",
  "biblehash": "00000007e43283f41962ffde2f5fb75a1b96df8775009548dda93c62c7183d74",
  "prayers": "",
  "nextblockhash": "60a47dbedcc91a80c6a5c0a5b81febf119aabae6f27e180f29a27c3616334391"
}

===

I wasnt sure with protocol downgrade if I need to start the masternode again, so I started again anyways, its in PRE_ENABLED state now

Whoops I still need to run it as GUI, its non-GUI still, will report back
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 09, 2018, 01:57:25 pm

Thats awesome you got it working.  So what was the actual root of the problem why couldnt it sign your cpid?

Hi, it still dont work for me. I've tried Togo's "force" command and it still gave me this message: 
"Results": "Unable to sign CPID 04fba56d89a5eb38b1b82f8a6240132c"
If I run it on BOINC sw it goes well, but inside BBP it didn't work...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 02:34:51 pm
Hi, it still dont work for me. I've tried Togo's "force" command and it still gave me this message: 
"Results": "Unable to sign CPID 04fba56d89a5eb38b1b82f8a6240132c"
If I run it on BOINC sw it goes well, but inside BBP it didn't work...
The force command is only if you are moving your wallet.

So this particular error occurs if you have an ecrypted locked wallet.
Could you please ensure you have more than 5 bbp available, wallet is unencrypted and unlocked, and that you have receiveing addresses available?
Then once you have one type:
sendtoaddress bbp_address 1

Let me know if that goes through properly?

Have you done anything strange to the wallet?
What version you running, headless or qt, and what OS?

One more question, what happens when you type:
signmessage bbp_address CPID1
(only replace bbp_address with your bbp_address)?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 09, 2018, 02:37:39 pm
my win wallet 189 still crashin when syncing
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 02:39:45 pm
my win wallet 189 still crashin when syncing
Without a debug log, no chance of looking at the problem.

I have 25 instances running and havent crashed.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 09, 2018, 02:48:07 pm
The force command is only if you are moving your wallet.

So this particular error occurs if you have an ecrypted locked wallet.
Could you please ensure you have more than 5 bbp available, wallet is unencrypted and unlocked, and that you have receiveing addresses available?
Then once you have one type:
sendtoaddress bbp_address 1

Let me know if that goes through properly?

Have you done anything strange to the wallet?
What version you running, headless or qt, and what OS?

One more question, what happens when you type:
signmessage bbp_address CPID1
(only replace bbp_address with your bbp_address)?

Thanks Rob.
I've unlocked wallet and create receive address. I have more than 50000 tBBP mined, but I didn't create any receive address before.
Now it is working and I'm on chain ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 09, 2018, 03:59:53 pm
Updated both my testnet wallets to 1.0.8.9

showblock 5228:
Code: [Select]
"blockmessage": "",
  "satisfiesbiblehash": "true",
  "biblehash": "0000000af3d9ac2d23b4eef3f5b0fd9303e6ca61b432fe2a15e5dbf50ce72bc7",
  "prayers": "",
  "nextblockhash": "449ff8cb60b4ce68691add717ebdd8980e3ea22716db8bd761bc523b1d1e9a87"
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 09, 2018, 05:12:52 pm
My rewards seem to be around 150K at present


12:10:24

exec getboincinfo

12:10:25

{
  "Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "NextSuperblockHeight": 5445,
  "8f273b30f8e0a298ed26e242762df701_RAC": 453.53,
  "LastSuperblockHeight": 5346,
  "Payments": 153915,
  "Budget": 1386000,
  "Magnitude": 111.0497835497836
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 07:11:16 pm
Updated both my testnet wallets to 1.0.8.9

showblock 5228:
Code: [Select]
"blockmessage": "",
  "satisfiesbiblehash": "true",
  "biblehash": "0000000af3d9ac2d23b4eef3f5b0fd9303e6ca61b432fe2a15e5dbf50ce72bc7",
  "prayers": "",
  "nextblockhash": "449ff8cb60b4ce68691add717ebdd8980e3ea22716db8bd761bc523b1d1e9a87"
}

Thanks, Ill work on that botnet-busting feature a different way, so dont worry about the blockmessage for now, it needs a change.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 07:14:45 pm
My rewards seem to be around 150K at present


12:10:24

exec getboincinfo

12:10:25

{
  "Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "yMC3QWwddFKgQGbMdJnZ9zZRCStj87Apvh",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "NextSuperblockHeight": 5445,
  "8f273b30f8e0a298ed26e242762df701_RAC": 453.53,
  "LastSuperblockHeight": 5346,
  "Payments": 153915,
  "Budget": 1386000,
  "Magnitude": 111.0497835497836
}

Glad to hear your being PAID!  Nice!
And heres a little more info on mag:
The magnitude is a value between 1-1000, with 1000 being the highest you can achieve in Biblepay (its impossible because 1000 means you are doing all the work).

Anyway if you divide the mag by 10, its equal to Your Share of the Last SUperblock.

So in Lukes case, he should receive 11% of the 1.386MM coins.  Looks like he did:  153K is 11% of the superblock.


So far so good all.... I like this, and I also like the plethora of tweaks a miner can make to their clock speeds and system boot options (mining as a service, running cross platform, mining multi machines against one CPID), sleep options, etc. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 07:25:02 pm
Have 2 masternodes running on 1.0.8.9 now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 07:31:21 pm
Have 2 masternodes running on 1.0.8.9 now.
I accidentally spent my hot masternode funds...recreating now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 07:36:59 pm
Have 2 masternodes running on 1.0.8.9 now.

Ok, Im back and I see 2 of you did vote on the contract while I was down, which is great, in last superblock.
Why dont we try checking this next contract out without forcing it?

Mike are you online?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 07:46:37 pm
Ok, Im back and I see 2 of you did vote on the contract while I was down, which is great, in last superblock.
Why dont we try checking this next contract out without forcing it?

Mike are you online?
So I kind of answered my own question.  What I meant by force, was if users keep typing exec testvote, they are forcing a vote for their contract hash (which the code will do anyway, once per block).
So checking to see what kind of support we have for the  next superblock (without typing exec testvote),  you can type
cat debug.log | grep ExecuteDistributed -A5
And you will see what your node thinks its doing as blocks click by.  In my case it says "PENDING SUPERBLOCK", meaning two Sancs already voted on block #5643, telling me there will be a superblock.

Each Sancs vote only counts once per filehash.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 07:49:56 pm
Ok, Im back and I see 2 of you did vote on the contract while I was down, which is great, in last superblock.
Why dont we try checking this next contract out without forcing it?

Mike are you online?

Yeah, just finished settings up the 3rd one.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:06:40 pm
So I kind of answered my own question.  What I meant by force, was if users keep typing exec testvote, they are forcing a vote for their contract hash (which the code will do anyway, once per block).
So checking to see what kind of support we have for the  next superblock (without typing exec testvote),  you can type
cat debug.log | grep ExecuteDistributed -A5
And you will see what your node thinks its doing as blocks click by.  In my case it says "PENDING SUPERBLOCK", meaning two Sancs already voted on block #5643, telling me there will be a superblock.

Each Sancs vote only counts once per filehash.

Mine says:
AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK .
2018-02-10 02:05:00 UpdateTip: new best=6ee2dc9bc66a6310009d192ea9c6f67a4bd29e8efa17f92e2046374f8311281e  height=5571  log2_work=39.043051  tx=7504  date=2018-02-10 02:04:59 progress=0.031810  cache=0.1MiB(594tx)
2018-02-10 02:05:00 AddToWallet 5b3f2d75a103ead2d58a5ef32a41a41ff00e48d10b3f9726e0a92b915c3f21d9  new
2018-02-10 02:05:00 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 8b2affbe3d46b48ec87e6e6115f06e511a9673697f647b8ef1aa25172e14175b-1 -- found new 5571.000000
2018-02-10 02:05:00 ProcessNewBlock : ACCEPTED
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:12:01 pm
Mine says:
AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK .
2018-02-10 02:05:00 UpdateTip: new best=6ee2dc9bc66a6310009d192ea9c6f67a4bd29e8efa17f92e2046374f8311281e  height=5571  log2_work=39.043051  tx=7504  date=2018-02-10 02:04:59 progress=0.031810  cache=0.1MiB(594tx)
2018-02-10 02:05:00 AddToWallet 5b3f2d75a103ead2d58a5ef32a41a41ff00e48d10b3f9726e0a92b915c3f21d9  new
2018-02-10 02:05:00 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 8b2affbe3d46b48ec87e6e6115f06e511a9673697f647b8ef1aa25172e14175b-1 -- found new 5571.000000
2018-02-10 02:05:00 ProcessNewBlock : ACCEPTED

Sweet,  so really things seem to be working properly.

Tomorrow I will move the distinct CPID rule to the blockcheck for testnet and have a release (Ill wait til something else can be merged with it before releasing another testnet release).

Does anyone have any security questions, or any questions about anything DC related?

Maybe I should add a feature to show total payments over 7 days, then we can do some math also.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:13:10 pm
Glad to hear your being PAID!  Nice!
And heres a little more info on mag:
The magnitude is a value between 1-1000, with 1000 being the highest you can achieve in Biblepay (its impossible because 1000 means you are doing all the work).

Anyway if you divide the mag by 10, its equal to Your Share of the Last SUperblock.

So in Lukes case, he should receive 11% of the 1.386MM coins.  Looks like he did:  153K is 11% of the superblock.


So far so good all.... I like this, and I also like the plethora of tweaks a miner can make to their clock speeds and system boot options (mining as a service, running cross platform, mining multi machines against one CPID), sleep options, etc.

Rob, when my mag actually had a number earlier today, I didn't see a payment for it.  How do I check?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:18:10 pm
Rob, when my mag actually had a number earlier today, I didn't see a payment for it.  How do I check?
If your mag had a number earlier it should still have a number, why no number now, did you move wallets?

The easiest way is to just scroll through your transaction history, look for anying over 20k in the last 24hours?

Since we have 7 superblocks a day, you'd really have to figure the spacing math (exec getboincinfo, see the difference between the 2) then showblock each prior block for 24 hours to check manually, but from what I remember, you didnt have a mag all day, this morning you were not in the list, what is your cpid?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:26:08 pm
If your mag had a number earlier it should still have a number, why no number now, did you move wallets?

The easiest way is to just scroll through your transaction history, look for anying over 20k in the last 24hours?

Since we have 7 superblocks a day, you'd really have to figure the spacing math (exec getboincinfo, see the difference between the 2) then showblock each prior block for 24 hours to check manually, but from what I remember, you didnt have a mag all day, this morning you were not in the list, what is your cpid?

CPID: e94c1704c75f731f8bfde303f08408ee

Before I took the node down about 3 hours ago I saw a number on the front page but now it's 0. I did not change wallets.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:31:52 pm
CPID: e94c1704c75f731f8bfde303f08408ee

Before I took the node down about 3 hours ago I saw a number on the front page but now it's 0.

*update

I looked through all the transactions today and didn't find the payment.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:32:24 pm
CPID: e94c1704c75f731f8bfde303f08408ee

Before I took the node down about 3 hours ago I saw a number on the front page but now it's 0.
I think you saw your CPID appear on the front page but not magnitude, since you are still not in the san\filtered file yet (that will always only get bigger).  Yeah your not in yet, so you should have 0 payments.

Also, 'exec getboincinfo' shows your up to date RAC and should show 0 mag.  Do u have RAC yet?


Maybe we should move to once per day superblocks in testnet so we dont have to check as many.  We need some type of report you can run that shows every cpid and payment in the last superblock.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:34:36 pm
I think you saw your CPID appear on the front page but not magnitude, since you are still not in the san\filtered file yet (that will always only get bigger).  Yeah your not in yet, so you should have 0 payments.

Also, 'exec getboincinfo' shows your up to date RAC and should show 0 mag.  Do u have RAC yet?


Maybe we should move to once per day superblocks in testnet so we dont have to check as many.  We need some type of report you can run that shows every cpid and payment in the last superblock.

It's at 247 now. I think we need to have better status update or we will have lots of the same questions to answer regarding RAC and payment. When I said I saw a RAC number I meant I saw it on the front page.


02:33:37

exec getboincinfo


02:33:38

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yiqLtGKtrDykVqrFREoZ8B5mhRE66s4cw8",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "NextSuperblockHeight": 5643,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 247.62,
  "LastSuperblockHeight": 5247,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:45:11 pm
It's at 247 now. I think we need to have better status update or we will have lots of the same questions to answer regarding RAC and payment. When I said I saw a RAC number I meant I saw it on the front page.


02:33:37

exec getboincinfo


02:33:38

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yiqLtGKtrDykVqrFREoZ8B5mhRE66s4cw8",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "NextSuperblockHeight": 5643,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 247.62,
  "LastSuperblockHeight": 5247,
  "Payments": 0,
  "Budget": 1386000,
  "Magnitude": 0
}

I think what we need is a sentence saying Please wait 24 hours for magnitude to populate.... I think I can query when a person associated their CPID, and if its < 24 hours, maybe place a warning in the getboincinfo : Warning CPID associated 14 hours ago, please wait 24 hours for magnitude to populate.  If the magnitude is 0 on the front page, thats normal for the first 24 hours.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:48:31 pm
I think what we need is a sentence saying Please wait 24 hours for magnitude to populate.... I think I can query when a person associated their CPID, and if its < 24 hours, maybe place a warning in the getboincinfo : Warning CPID associated 14 hours ago, please wait 24 hours for magnitude to populate.  If the magnitude is 0 on the front page, thats normal for the first 24 hours.

Yeah, I would like to get to the bottom of my missing payment, not sure what went wrong. It could be that I read wrong but...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 08:53:04 pm
Yeah, I would like to get to the bottom of my missing payment, not sure what went wrong. It could be that I read wrong but...

Maybe we misunderstood each other - I am saying you definitely didnt see a magnitude earlier, because you are not (definitely not) in the SAN/filtered file.

If you want to see the file, please cd /SAN and cat filtered.

It only grows in size, it does not shrink.

Therefore you were never with magnitude, and therefore would have no payments.

Your CPID association was < 24 hours ago, you are last in the list of dccs:  exec list dccs

To help cut the confusion down, I just added a feature to show the Warning I mentioned in the previous post.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 08:58:31 pm
Maybe we misunderstood each other - I am saying you definitely didnt see a magnitude earlier, because you are not (definitely not) in the SAN/filtered file.

If you want to see the file, please cd /SAN and cat filtered.

It only grows in size, it does not shrink.

Therefore you were never with magnitude, and therefore would have no payments.

Your CPID association was < 24 hours ago, you are last in the list of dccs:  exec list dccs

To help cut the confusion down, I just added a feature to show the Warning I mentioned in the previous post.

Rob, OK I understand now. Thanks for showing me how to check on my own. Good work on the integration by the way.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 09:00:49 pm
Rob, OK I understand now. Thanks for showing me how to check on my own. Good work on the integration by the way.

Thanks dude.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 09, 2018, 09:18:00 pm
I think tomorrow I will add:

Total payments to CPID over 7 day period, and a list of superblocks with payments comma separated over 7 days, those two fields to exec getboincinfo.

Then it should pretty much tell us the accuracy level we are hitting.

I could also add a ratio column : superblock hit vs not hit. (IE Hit Ratio : 75%).  That just tells us how many failed to be voted in.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 09, 2018, 09:22:47 pm
I think tomorrow I will add:

Total payments to CPID over 7 day period, and a list of superblocks with payments comma separated over 7 days, those two fields to exec getboincinfo.

Then it should pretty much tell us the accuracy level we are hitting.

I could also add a ratio column : superblock hit vs not hit. (IE Hit Ratio : 75%).  That just tells us how many failed to be voted in.

Sounds good. are you expecting some to not be voted in?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 07:37:36 am
Sounds good. are you expecting some to not be voted in?

In Prod:  Rarely.  I think with 130 sancs, as long as the quorum percent is correct (10%, thats 13 votes) then I think they will be voted in. 
 If Rosetta or boinc go down in prod, I have some advanced rules set up.  If the file is either corrupted, or empty, or unfilterable, or contains no magnitude or less than X researchers in prod (thats 5 right now in the code), the file hash is set to 0x0, and the sancs will not vote on 0x0.  So that is the most likely scenario in prod if we miss a superblock, maybe it will happen once a year.

In Test:  We started out with a 65% hit ratio (I added the feature and just ran it) and thats primarily because we didnt tell the sancs to run in -qt mode.   We can monitor it and see if we rise in test.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Kismar on February 10, 2018, 08:23:05 am
got my researcher/wallet running yesterday in testnet, confirmed payments this morning with getboincinfo and transaction history.  one thing i've had happen a couple times is that the wallet has banned all the peers i'd been connected to and i have to restart the wallet and unban everyone to reconnect to the network.

any thoughts?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 08:27:48 am
got my researcher/wallet running yesterday in testnet, confirmed payments this morning with getboincinfo and transaction history.  one thing i've had happen a couple times is that the wallet has banned all the peers i'd been connected to and i have to restart the wallet and unban everyone to reconnect to the network.

any thoughts?

I think I know whats going on - Im the main seed node (node.biblepay.org) in testnet and Im down, Im currently adding a new rule in the code.

There are many old testers on old versions.  Did you sync to block 6076?  Try clicking each peer and see if the are on 1089 in the gui version?
If so your good for now, but Ill probably be down for one more hour.  Then ill give you more live insight.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Kismar on February 10, 2018, 08:52:48 am
I think I know whats going on - Im the main seed node (node.biblepay.org) in testnet and Im down, Im currently adding a new rule in the code.

There are many old testers on old versions.  Did you sync to block 6076?  Try clicking each peer and see if the are on 1089 in the gui version?
If so your good for now, but Ill probably be down for one more hour.  Then ill give you more live insight.



myself and the 5 peers i'm connected to are all running 1.0.8.9, but after my most recent restart there's no blocksource available and i'm only up to block 6016.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 08:55:22 am
myself and the 5 peers i'm connected to are all running 1.0.8.9, but after my most recent restart there's no blocksource available and i'm only up to block 6016.

If you have ever had any blocks or chainstate prior to v1.0.8.8, you probably got banned.
Please try:
rm chainstate -r
rm blocks -r

Then resync.  Im up now so you should be able to resync now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 08:55:44 am
If you have ever had any blocks or chainstate prior to v1.0.8.8, you probably got banned.
Please try:
rm chainstate -r
rm blocks -r

Then resync.  Im up now so you should be able to resync now.
Btw:  Please do this in the \testnet3 folder, not in the prod folder.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Kismar on February 10, 2018, 09:09:51 am
Btw:  Please do this in the \testnet3 folder, not in the prod folder.

ok, cleared and resync'd, says current block as of this message is 6107, I'll update if anything weird happens.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 10:51:10 am
Looks like we have 15 CPIDs crunching in Test!  Awesome.

Lets keep going, lets shoot for 50!  This way we can huddle together in a few weeks and make a determination call on PODC- to go with it in prod or not go with it. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 12:00:54 pm
1.0.8.9c - Leisure Upgrade
For Testnet

- Added botnet busting rule ( provides debug info for us, but not enforced in testnet yet ) - this will provide info necessary to move closer to implementing the distinct CPID rule in testnet
- Added more fields to getboincinfo, to show the researchers weekly payments, daily payments, etc.  Also added the newbie warning.

Windows is compiling...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 10, 2018, 12:10:52 pm
1.0.8.9c - Leisure Upgrade
For Testnet

- Added botnet busting rule ( provides debug info for us, but not enforced in testnet yet ) - this will provide info necessary to move closer to implementing the distinct CPID rule in testnet
- Added more fields to getboincinfo, to show the researchers weekly payments, daily payments, etc.  Also added the newbie warning.

Windows is compiling...

Rob, my goal it to create 10 sanctuaries and 50 CPIDs, let me know when I have to update the sanctuaries as it will take a while so only when it's necessary please.

*Update

Do the CPIDs need to on seperate wallets or all on the same wallet is fine?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 10, 2018, 01:43:09 pm
i hope that linux masternode will be working on linux classic way and now any crap gui  :o
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 01:48:39 pm
i hope that linux masternode will be working on linux classic way and now any crap gui  :o

What does this mean?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 01:49:59 pm
Rob, my goal it to create 10 sanctuaries and 50 CPIDs, let me know when I have to update the sanctuaries as it will take a while so only when it's necessary please.

*Update

Do the CPIDs need to on seperate wallets or all on the same wallet is fine?

Id like to have at least 300 RAC per CPID though so we can ensure real world testing, maybe just do half if you have 25 machines?

I guess you could put 25 cpids against one controller wallet if you want, it will help immensely...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 10, 2018, 02:00:41 pm
Id like to have at least 300 RAC per CPID though so we can ensure real world testing, maybe just do half if you have 25 machines?

I guess you could put 25 cpids against one controller wallet if you want, it will help immensely...

I will tie them to the same wallet. 300 RAC is going to be a difficult though.

*Update
How do you add multiple Rosetta accounts? I tried adding one and it said invalid credentials.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 10, 2018, 02:16:06 pm
What does this mean?
im read something about linux wallet-gui with xfce,kde etc .... for what omg?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 10, 2018, 02:19:38 pm
im read something about linux wallet-gui with xfce,kde etc .... for what omg?

That's for setting up linux with GUI for running the wallet with -qt.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 02:24:16 pm
I will tie them to the same wallet. 300 RAC is going to be a difficult though.

*Update
How do you add multiple Rosetta accounts? I tried adding one and it said invalid credentials.

You would have to actually make 25 rosetta accounts, lol.
Because otherwise, you will be adding instances to one CPID.

Once you have a second Rosetta account, you can associate another CPID to your biblepay wallet (I have 2 running now).

Must have been a bad set of credentials.
Try logging into Rosetta Web URI with them.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 02:26:34 pm
im read something about linux wallet-gui with xfce,kde etc .... for what omg?

Yeah, we are going to require half of the prod network to run masternodes in ./biblepay-qt (GUI) mode, until we can find another way to perform the QT function in headless.  Its important we leave it as-is so the exchanges dont get mad.  Its a big deal, because I was already talking to Bittrex about this a couple years ago, and they will actually deny the coin to be listed there if we were to add a "questionable" dependency to the headless side.

So for now our best option is to require prod sanctuaries, at least half of them, to run in QT mode.

Maybe Ill add a rule to not pay them if they cant execute the same QT function.

We'll see.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 02:34:07 pm
Yeah, we are going to require half of the prod network to run masternodes in ./biblepay-qt (GUI) mode, until we can find another way to perform the QT function in headless.  Its important we leave it as-is so the exchanges dont get mad.  Its a big deal, because I was already talking to Bittrex about this a couple years ago, and they will actually deny the coin to be listed there if we were to add a "questionable" dependency to the headless side.

So for now our best option is to require prod sanctuaries, at least half of them, to run in QT mode.

Maybe Ill add a rule to not pay them if they cant execute the same QT function.

We'll see.


I think what we will do is "recommend" a prod sanctuary owner to run in QT mode, and Ill make it kill the node (IE the node will die) if its a chosen sanc and cant process the file.  Then if the owner does not reboot it they will eventually not get paid or have to manually restart it.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 10, 2018, 02:39:32 pm
You would have to actually make 25 rosetta accounts, lol.
Because otherwise, you will be adding instances to one CPID.

Once you have a second Rosetta account, you can associate another CPID to your biblepay wallet (I have 2 running now).

Must have been a bad set of credentials.
Try logging into Rosetta Web URI with them.

Yeah, I already started doing that. Checked the account on the rosetta website twice, still doesn't work. Do you think it's because I'm using a + sign in the email address? i.e. abc+123@gmail.com.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 02:52:39 pm
Yeah, I already started doing that. Checked the account on the rosetta website twice, still doesn't work. Do you think it's because I'm using a + sign in the email address? i.e. abc+123@gmail.com.

Yes, thats the problem, + and ; and = is found in the signature.  Maybe we will base64 encode it, but that could take a while.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 10, 2018, 02:55:09 pm
Yes, thats the problem, + and ; and = is found in the signature.  Maybe we will base64 encode it, but that could take a while.

Would it work from the GUI? I'm thinking no, it looks like it's how the variable was set up or something.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 02:58:51 pm
Would it work from the GUI? I'm thinking no, it looks like it's how the variable was set up or something.

The only difference from the RPC are the spaces, so RPC Or Gui are equally bad.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 10, 2018, 03:04:24 pm
The only difference from the RPC are the spaces, so RPC Or Gui are equally bad.

It's ok, it looks like I can just use fake e-mail address, the only downside is I won't be able to recover my account probably but that's ok.

By the way, I have 6 sanctuaries up and running now. I can make more if you want to send me some tBBp. I need 2mil more for 4 more sanctuaries. Address: yiqLtGKtrDykVqrFREoZ8B5mhRE66s4cw8
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 03:25:17 pm
It's ok, it looks like I can just use fake e-mail address, the only downside is I won't be able to recover my account probably but that's ok.

By the way, I have 6 sanctuaries up and running now. I can make more if you want to send me some tBBp. I need 2mil more for 4 more sanctuaries. Address: yiqLtGKtrDykVqrFREoZ8B5mhRE66s4cw8

Yeah, just to clarify, your not using a fake rosetta account, your using a valid rosetta account with an unconfirmed e-mail address, and associating biblepay with a valid username + password that you can still log in to access and edit the account.  I dont want anyone to think they can make a CPID with a fake email address.

BOINC allows that for anonymity reasons, so that one can crunch without having to actually have a confirmed e-mail account to start crunching.

I think you have enough, but thanks for setting all that up!  Id like to get a good broad base going so we can really hit all the intricacies in our testing.

EDIT: Sent 1 mil more just in case.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 10, 2018, 05:43:37 pm

I think what we will do is "recommend" a prod sanctuary owner to run in QT mode, and Ill make it kill the node (IE the node will die) if its a chosen sanc and cant process the file.  Then if the owner does not reboot it they will eventually not get paid or have to manually restart it.

Is this for after PoDC is implemented or should I look to do this now?
How do I run qt in headless mode (I am on a vultr virtual machine).
Thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 05:58:43 pm
Is this for after PoDC is implemented or should I look to do this now?
How do I run qt in headless mode (I am on a vultr virtual machine).
Thanks

This is for after we go live, now that I think of it... We will need to ask everyone to do it at that point, because over 10 days, everyone will get "hit" with the call of duty (to process the file).

On vultr, you can just VNC in (using the built in viewer) and then install graphics from the command line.  It really depends on your flavor, I have Debian but I dont know the command right off but its pretty easy if you google it.  Once the graphics manager is installed, you can launch QT like this

cd /src/qt
./biblepay-qt

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 10, 2018, 06:05:19 pm
Ok cool, when it is closer to the time I will figure out how to do that.

On another note, it seems another advantage of PoDC may be solving the multiwallet issue.

I'm still testing and I want to give it a few days, but running a 4 core physical machine (with a pretty old/slow cpu) and comparing it to two different VPS, I am getting much much better Average Credit from the physical machine (even though on the pool the hps wasn't that much greater than the vps server).

I'll give it a few days to average out then present my findings
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 10, 2018, 06:19:30 pm
Ok cool, when it is closer to the time I will figure out how to do that.

On another note, it seems another advantage of PoDC may be solving the multiwallet issue.

I'm still testing and I want to give it a few days, but running a 4 core physical machine (with a pretty old/slow cpu) and comparing it to two different VPS, I am getting much much better Average Credit from the physical machine (even though on the pool the hps wasn't that much greater than the vps server).

I'll give it a few days to average out then present my findings

Your right!  That solves that pesky issue too.  I think I said that to someone in a PM but I forgot about that bonus.

Yeah, It would be nice to just mine BBP on one thread in the controller wallet and max out every machine with Rosetta.

I believe it- since Boinc has a plethora of management options, we inherit all the benefits of respecting a users computing preferences and networking preferences also.

One other side benefit of this that is huge to the coin as a whole is modular programming.  Effectively if Rosetta works as our miner, that means any cat & mouse related upgrades are not necessary on our side, and all of Rosettas updates happen invisibly (as they are constantly adding more complex problems to their code on the healthcare side - and boinc takes care of upgrading those libs and they are guaranteed not to break us, because they must be boinc compatible), so I like the fact that we inherit a better cancer miner, and yet that side of the house upgrades itself.  Then we can focus on what we do best- working on Stratis, reports, and gospel features, etc.  It seems like a win-win, but I am obviously considering all of the integrity aspects of PODC workunits also, so Id like to build a team that is committed to "proving" the integrity of PODC work units, with some hybrid idea as I mentioned maybe placing a Biblepay script inside work units - and spend the stake as miners "solve" these, at least that proves they received a work unit, inserted a POS script, and solved the work unit live.  If people trust stake coins, why wouldnt they trust stake on steroids inside a cancer miner?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 10, 2018, 10:25:56 pm
Yeah, just to clarify, your not using a fake rosetta account, your using a valid rosetta account with an unconfirmed e-mail address, and associating biblepay with a valid username + password that you can still log in to access and edit the account.  I dont want anyone to think they can make a CPID with a fake email address.

BOINC allows that for anonymity reasons, so that one can crunch without having to actually have a confirmed e-mail account to start crunching.

I think you have enough, but thanks for setting all that up!  Id like to get a good broad base going so we can really hit all the intricacies in our testing.

EDIT: Sent 1 mil more just in case.

Yeah there is no security issue.

Thanks for the extra tBBP, I have 10 testnet masternodes running now. Over the next week I will add more CPIDs for testing.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 11, 2018, 03:29:32 am
we need desktop for linux for masternode in future?

my questions is only this:

1.when i sent exec getboincinfo : missing CPID, addresses ...  its need SYNC or where is bug?
2.can i set 50% cpu for rosetta and 50% for mining bbp?   more power to rosetta more magnitude more rewards from superblock?
3. where i can to setup this divide-contribute power in linux?  or how in boinc manager in windows

thanks

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 06:58:51 am
we need desktop for linux for masternode in future?

my questions is only this:

1.when i sent exec getboincinfo : missing CPID, addresses ...  its need SYNC or where is bug?
2.can i set 50% cpu for rosetta and 50% for mining bbp?   more power to rosetta more magnitude more rewards from superblock?
3. where i can to setup this divide-contribute power in linux?  or how in boinc manager in windows

thanks
0) Yeah, at this time, we will need sanctuaries to run in ./biblepay-qt mode.  They need the qt libs to perform the advanced file filtering.

***  This is only for the sanctuaries.  Anyone else on linux can still run in headless mode if they want ***

1) Please ensure you are on 1089 as I added more info, then paste your exec getboincinfo.  Without seeing that it could be anything.  I assume your CPID is associated already to boinc. 
2) You could do 50% rosetta, but it would be a waste.  You really should do 90% rosetta and just let bbp mine on one thread in the controller, as mining only pays 10%.  You get more magnitude when your cancer miner does more average work per day.
3) For boinc on linux, I just installed it on a few debian sancs very easily and now they are crunching, follow this guide: http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu
I recommend installing it then running boinc manager from your graphics launcher, then click advanced view, and then it looks just like the windows version.  Once you are an expert, you can also do boinc ops in headless mode (like headless biblepay).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 08:32:10 am
we need desktop for linux for masternode in future?

my questions is only this:

1.when i sent exec getboincinfo : missing CPID, addresses ...  its need SYNC or where is bug?
2.can i set 50% cpu for rosetta and 50% for mining bbp?   more power to rosetta more magnitude more rewards from superblock?
3. where i can to setup this divide-contribute power in linux?  or how in boinc manager in windows

thanks


I accidentally delete your last post, my mistake.


You were asking how do you give 10% to POBH, 10% to Yourself and 80% to boinc.

Its possible to do that:

1) Run biblepay-qt with 1 thread - 'genproclimit=1'
2) In Boinc, go to options, computing preferences, set Use no more that 80% computing power, and say suspend tasks when computer is busy


SOLVED


As far as the manual, I disagree, its 90% there for anyone with intelligence enough to read, and knows anything basic about basic IT administration.

All we need is a few more nuances to address uncommon problems, linux administration, and what Togo thinks is Wise.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 09:01:29 am

I accidentally delete your last post, my mistake.


You were asking how do you give 10% to POBH, 10% to Yourself and 80% to boinc.

Its possible to do that:

1) Run biblepay-qt with 1 thread - 'genproclimit=1'
2) In Boinc, go to options, computing preferences, set Use no more that 80% computing power, and say suspend tasks when computer is busy


SOLVED


As far as the manual, I disagree, its 90% there for anyone with intelligence enough to read, and knows anything basic about basic IT administration.

All we need is a few more nuances to address uncommon problems, linux administration, and what Togo thinks is Wise.


With boinc you can not only throttle by user preference you can even throttle by CPU temperature:

https://efmer.com/


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on February 11, 2018, 09:16:15 am
I have just tried running boinc on ARM. Not successful though, I'm not getting any tasks :

11-Feb-2018 15:15:24 [Rosetta@home] Sending scheduler request: To fetch work.
11-Feb-2018 15:15:24 [Rosetta@home] Requesting new tasks for CPU
11-Feb-2018 15:15:27 [Rosetta@home] Scheduler request completed: got 0 new tasks
11-Feb-2018 15:15:27 [Rosetta@home] This project doesn't support computers of type aarch64-unknown-linux-gnu

Anyone  else tried ARM (e.g. Raspberry?)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 09:50:01 am
I have just tried running boinc on ARM. Not successful though, I'm not getting any tasks :

11-Feb-2018 15:15:24 [Rosetta@home] Sending scheduler request: To fetch work.
11-Feb-2018 15:15:24 [Rosetta@home] Requesting new tasks for CPU
11-Feb-2018 15:15:27 [Rosetta@home] Scheduler request completed: got 0 new tasks
11-Feb-2018 15:15:27 [Rosetta@home] This project doesn't support computers of type aarch64-unknown-linux-gnu

Anyone  else tried ARM (e.g. Raspberry?)
Thanks for trying dude, yea it will be highly beneficial if someone figures out a model of cell phone or tablet that actually runs it.
You might have to google the Rosetta forums to find one particular flavor that actually works...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 11, 2018, 09:51:45 am
Rob: your response was for windows: i mean how set in linux that boinc manager/ only client

ouch:  we will be using genproclimit on our machines=1?  right?

xeon=24cores  ==  genproclimit=1    1core for BBP and 23cores for rosetta will be automaticly?

im trying understand how it working  linux vs windows

news interesting that i was hit superblock 7128?  5907 tBBP

ROB im using 2 machines for test 3dprotein=  HTPC+GAMER PC=  both 189 version: both i see on rosetta info:

when i getboincinfo on Ryzen= i see parameters,but when i getboincinfo on HTPC machine i see this
(https://i.imgur.com/X9AwqrZ.png)



thanks for help guys
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 10:04:41 am
So Ive been pondering this morning on what can I do to give PODC the highest credibility with the masses - in order to give PODC a run for its money against the heat mining big dogs, like bitcoin.  Some features that verifiably prove with 99% accuracy that the work being performed (in the cancer mining subsystem) is actually being performed in exchange for the BBP.

So far here is what I came up with:
- Each time a miner asks Rosetta for work, Rosetta awards the user with a Task (and that task contains multiple workunits)
- Each TaskID is assigned to a HostID (that is equivalent to one PC in your UserId)
- Each UserId has multiple HostIDs running multiple TaskIds which have multiple WorkUnits

However, a host always takes a certain amount of time to crunch a Task.

So if we choose random CPIDs in the Biblepay rosetta team, as reference machines first, then

If we had a table like this in the pool:
Id, CPID, UserId, TaskId, StartTime, EndTime, ValidatedByRosetta, Updated, Added, POL-Script-In, UTXOOut

Then we could write a report that runs in real time in the pool that shows at any given time what a given Users Hosts are working on IE 4 active tasks, average solution time per task, etc.

And if we start adding a POL script into the User, it adds integrity to the report, because it proves the user (is real and staking a certain number of coins per task-set).  This basically says a miner must stake X amount per day to prove they are cancer researching and the coins are attached to Y tasks.

The report would show live activity - so anyone saying How do I know this is really happening, if they were to monitor the activity of a random host, they would see the host finish actual Single work units, and ask for more. 

We could create a metric, for average solution time per task also, to prove that tasks take time across hundreds of researchers, therefore the system is not being falsified by a small group of hackers.  If some end up being solved quicker by a certain account we could then flag that account for potential fraud, but if they are not, we would know with relative certainty the systems integrity level.  Then we make a global metric called Integrity, and calculate it based on all these figures, and use that integrity level for PODC overall integrity.

Then we expose the reports to a new menu in the pool in the "accountability.biblepay.org" domain.

Would that help us?  Is it worth all the work?

It would take me about 50 hours to write all this for the pool.

Im thinking the pool will be less useful as a heat-mining pool when we transitiion to PODC, but, these reports could be added to the pool to increase the integrity of PODC for the World, globally, viewing this as "the new way" and the Light of cryptocurrencies as a whole.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 10:07:20 am
Rob: your response was for windows: i mean how set in linux that boinc manager/ only client

ouch:  we will be using genproclimit on our machines=1?  right?

xeon=24cores  ==  genproclimit=1    1core for BBP and 23cores for rosetta will be automaticly?

im trying understand how it working  linux vs windows

news interesting that i was hit superblock 7128?  5907 tBBP

ROB im using 2 machines for test 3dprotein=  HTPC+GAMER PC=  both 189 version: both i see on rosetta info:

when i getboincinfo on Ryzen= i see parameters,but when i getboincinfo on HTPC machine i see this
(https://i.imgur.com/X9AwqrZ.png)



thanks for help guys

Two problems:

Your not running 1089 on that machine- got to run the latest software to test the features.
2) You should only run getboincinfo on the machine you associated the cpid with.


Then paste output.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 10:14:23 am
Some will say to my post, but wait, how do you actually trust rosetta with the solution validation?
We can construct an equation that addresses that:
1) The 'reference machine' must mirror the difficulty of the average solve time by more than one standard deviation (68% + )
2) No account may solve a task quicker per measured processor gigahertz than other users in the measured pool
3) Random results will be audited by someone at biblepay on a regular basis

In my opinion if these 3 things were performed, it would prove a certain level of reliability and integrity exists.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 11, 2018, 11:43:33 am
Some will say to my post, but wait, how do you actually trust rosetta with the solution validation?
We can construct an equation that addresses that:
1) The 'reference machine' must mirror the difficulty of the average solve time by more than one standard deviation (68% + )
2) No account may solve a task quicker per measured processor gigahertz than other users in the measured pool
How will you obtain the processor gigahertz? If you can obtain that from public data, I'm not sure it's correct at the moment as per the discussion I had with you regarding the cpu list.

3) Random results will be audited by someone at biblepay on a regular basis
I'm interested in doing the auditing.

In my opinion if these 3 things were performed, it would prove a certain level of reliability and integrity exists.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 11, 2018, 12:08:33 pm
ROB

machine 1 = ryzen upgrade wallet from 187 to 189 via git pull master origin
machine 2 = htpc   newest installation wallet 189 from web

both of these machines is on same chain

on rosetta web i see machine 1+2 ...

getboincinfo must be working on both machine in debug window?

and next question:  we sending real power to rosetta now in testnet mode?

when i have next machine: i can to add to rosetta with same email+password via wallet?

thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 01:03:15 pm
ROB

machine 1 = ryzen upgrade wallet from 187 to 189 via git pull master origin
machine 2 = htpc   newest installation wallet 189 from web

both of these machines is on same chain

on rosetta web i see machine 1+2 ...

getboincinfo must be working on both machine in debug window?

and next question:  we sending real power to rosetta now in testnet mode?

when i have next machine: i can to add to rosetta with same email+password via wallet?

thanks
exec getboincinfo should only work on the controller wallet.  Pick one controller wallet and then stick to it.

For machine # 2,3,4,5,6,7 you should be adding Boinc only, and when you add Rosetta to Boinc, you use the existing same email & pass you used for machine #1.  This way you have 7 machines connected to 1 CPID (like the instructions in the wiki say).

Btw, the boinc GUI (its called Boinc Manager in linux) is the same as (look & feel) of windows boinc manager.  I recommend using that in linux.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 01:08:13 pm
Some will say to my post, but wait, how do you actually trust rosetta with the solution validation?
We can construct an equation that addresses that:
1) The 'reference machine' must mirror the difficulty of the average solve time by more than one standard deviation (68% + )
2) No account may solve a task quicker per measured processor gigahertz than other users in the measured pool
How will you obtain the processor gigahertz? If you can obtain that from public data, I'm not sure it's correct at the moment as per the discussion I had with you regarding the cpu list.

3) Random results will be audited by someone at biblepay on a regular basis
I'm interested in doing the auditing.

In my opinion if these 3 things were performed, it would prove a certain level of reliability and integrity exists.


Ive got a long history of boinc on other projects from back in the day and I assert that whatever we were looking at on that web report is a Rosetta Reporting problem (or report duration issue).  And thats pretty common, because the people that run the Server side webrpc software dont really care about it.

But I assert that the boinc side, the side that measures the CPU gigahertz and cobbles per core, is Very exact.  We just need to be pulling those figures:  Host information from Boinc, cobblestones per second from boinc, cores per motherboard from boinc, etc. 

Of course you have a point, that in a public project there is no way to trust that info.  But there are some things we can do.  We can ask the auditors - like you - to run a piece of biblepay software that gets it from the horses mouth and hashes it, and basically we say - this certifies the scales from the auditors point of view, and, I think we *can* trust boinc to a certain degree, because out of 100 hosts, its a true statement that the supermajority are most likely Not running hacked versions of boinc, and that compiled client is very complex, so on average, we can trust a cross section of boinc CPU info.

So I think we do have something to work with.  I would like to help to a certain degree, to where we put out enough software to raise the integrity level to above 90. 

Im going to start tonight on writing an SQL injection routine that allows the pool to report on certain things per host per work unit.

We can talk about designing something inside biblepay that helps certify the scales also.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 11, 2018, 01:44:45 pm
exec getboincinfo should only work on the controller wallet.  Pick one controller wallet and then stick to it.

For machine # 2,3,4,5,6,7 you should be adding Boinc only, and when you add Rosetta to Boinc, you use the existing same email & pass you used for machine #1.  This way you have 7 machines connected to 1 CPID (like the instructions in the wiki say).

Btw, the boinc GUI (its called Boinc Manager in linux) is the same as (look & feel) of windows boinc manager.  I recommend using that in linux.

after update to 189 i did this on RYZEN 1700 UBUNTU 16.04:

a) install boinc

sudo apt-get install boinc-client

b) create Rosetta account with email, password, username

boinccmd --create_account https://boinc.bakerlab.org/rosetta/ EMAIL PWD USRNAME

c) Check that it worked==It will return your account key that you need to copy

boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ EMAIL PWD

d) attach machine to Rosetta account to begin working on solving computations

boinccmd --project_attach https://boinc.bakerlab.org/rosetta/ ACCOUNT_KEY

e) Now associate your BBP testnet wallet with Rosetta. Open wallet in testnet. It costs a couple of tBBP (since we are in testnet) to associate your BBP wallet to Rosetta.

exec associate rosetta_email_address rosetta_password


and on RYZEN this working excellent= exec getboincinfo i have all informations.....


and i reading this


Quote
4. So you do the steps above and it works in linux. Note that you only need 1 machine with BBP wallet (running in testnet), then boinc on all machines you want to add to Rosetta mining (to count towards daily superblock).

1st RYZEN is main Linux BBP wallet genproclimit= 15 (getboincinfo receiving in debug windows)

example
2,3,4,5 will be windows wallets ..... enough in DC bookmark in wallet add  email+password and i have to do exec assocation email+pass in debug win too? 

i have mess from all this setuping :( and dont  have taste last days with BBP something to do

we need helps  Rob,Togo,Znfall,virus,westwarmoth etc

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 01:54:21 pm
after update to 189 i did this on RYZEN 1700 UBUNTU 16.04:

a) install boinc

sudo apt-get install boinc-client

b) create Rosetta account with email, password, username

boinccmd --create_account https://boinc.bakerlab.org/rosetta/ EMAIL PWD USRNAME

c) Check that it worked==It will return your account key that you need to copy

boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ EMAIL PWD

d) attach machine to Rosetta account to begin working on solving computations

boinccmd --project_attach https://boinc.bakerlab.org/rosetta/ ACCOUNT_KEY

e) Now associate your BBP testnet wallet with Rosetta. Open wallet in testnet. It costs a couple of tBBP (since we are in testnet) to associate your BBP wallet to Rosetta.

exec associate rosetta_email_address rosetta_password


and on RYZEN this working excellent= exec getboincinfo i have all informations.....


and i reading this


1st RYZEN is main Linux BBP wallet genproclimit= 15 (getboincinfo receiving in debug windows)

example
2,3,4,5 will be win wallets ..... enough in DC bookmark in wallet add  email+password and i have to do exec assocation email+pass in debug win too? 

i have mess from all this setuping :( and dont  have taste last days with BBP something do

we need helps  Rob,Togo,Znfall,virus,westwarmoth etc



I just want to point out a few things so you dont fly blind:


1)  Log In To Web Rosetta from here:
https://boinc.bakerlab.org/rosetta/home.php

Use your Rosetta boinc credentials.

Search the page for "Cross-project ID:"  Write the value down in notepad.
That is your CPID and it will never change.


2)  You said you associated (using exec associate) a couple days ago already.  You only do this once per lifetime of researcher.
So that wallet was already associated.  If you did it again today, with Ryzen, then you are now re-associated with Ryzen, dont change it.
(Biblepay will only Honor the Last Burn Tx in the chain for you, so now that CPID in #1 is associated with the ryzen)


3)  For machines 2,3,4,5,6,7,8,9 etc, you only install bonc, and use the credentials in step #1.  This will cause Multiple Machines to crunch for rosetta on ONE cpid.  All rewards will go to the Ryzen.  You do Not want to run the 'exec associate' command again on any of those machines, or install bbp on them.


4) You can lower genproclimit =1  on the ryzen if you want,  as Im pushing low competition on the heat side in the future.

Thanks,
Rob

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 11, 2018, 02:00:37 pm

Ive got a long history of boinc on other projects from back in the day and I assert that whatever we were looking at on that web report is a Rosetta Reporting problem (or report duration issue).  And thats pretty common, because the people that run the Server side webrpc software dont really care about it.

But I assert that the boinc side, the side that measures the CPU gigahertz and cobbles per core, is Very exact.  We just need to be pulling those figures:  Host information from Boinc, cobblestones per second from boinc, cores per motherboard from boinc, etc. 

Of course you have a point, that in a public project there is no way to trust that info.  But there are some things we can do.  We can ask the auditors - like you - to run a piece of biblepay software that gets it from the horses mouth and hashes it, and basically we say - this certifies the scales from the auditors point of view, and, I think we *can* trust boinc to a certain degree, because out of 100 hosts, its a true statement that the supermajority are most likely Not running hacked versions of boinc, and that compiled client is very complex, so on average, we can trust a cross section of boinc CPU info.

So I think we do have something to work with.  I would like to help to a certain degree, to where we put out enough software to raise the integrity level to above 90. 

Im going to start tonight on writing an SQL injection routine that allows the pool to report on certain things per host per work unit.

We can talk about designing something inside biblepay that helps certify the scales also.

I'm having a hard time processing all this information to see the overall solution, I'll have to think about it through out the week. Let's keep working on this.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 02:09:41 pm
I'm having a hard time processing all this information to see the overall solution, I'll have to think about it through out the week. Let's keep working on this.
Indeed, lets come up with a solution.  Because heres basically where we are:  The public trusts DC enough to value Golem, FAHCoin, Mediccoin and Gridcoin around 20 mil each.  Id like us to be a blessing to 10,000 orphans a month, so we need to be worth 200-300 million.  If we can come up with a solution together for this problem we could then hire 100 devs working around the clock and then be up in the top 10 (with the Billion $ coins) as this issue is seriously going to give the status quo, the heat miners a real option to jump ship and become a PODC miner.

One thing you can take a look at is all the logs that boinc emits (search the drive for client_state.xml).  You can scrape info out of the XML file that gives what boinc thinks about your machine.  Go ahead and see if you like what it says about you - cores - ghz - motherboard info etc.

Tonight Ill work on importing a researchers host record and tasks into the pool sql server.  Maybe we can start with a report that shows task durations per CPID.

But as we work on this problem, think of ways we can provably show a hosts speed and work activity per task per reward.

Casinos prove to us they stole peoples money with their RTG gaming reports, they show the dice are not loaded and prove the numbers were random
 and their mathematical edges obtained by actual measured outcomes.  Sounds to me we should be able to prove the PODC system was not fraudulently hacked over a certain number of measured outcomes.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 11, 2018, 02:10:23 pm
HOLY HEAVEN
so will be enough 1 wallet on ryzen and all other my machines enough to install only boinc and add to group?   :o

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 02:13:16 pm
so will be enough 1 wallet on ryzen and all others my machines enough install only boinc and add to group?   :o

Yes, exactly.  You can have 1000 PCs mining against one cpid, and 10 tablets and 5 phones on the same cpid. You can still drill into the devices from the BoincStats and the Team info, so you lose no visibility on RAC per device. 

BBP calculates the Magnitude from the CPID total RAC per day.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 11, 2018, 02:15:43 pm
HOLY HEAVEN
so will be enough 1 wallet on ryzen and all other my machines enough to install only boinc and add to group?   :o

Yes, 1 wallet on Ryzen.

On other machines just do

1) sudo apt-get install boinc-client

2) boinccmd --project_attach https://boinc.bakerlab.org/rosetta/ ACCOUNT_KEY


Then all machines are on same Rosetta account (same CPID) and you get all payments to 1 BBP wallet on your Ryzen
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 11, 2018, 02:33:13 pm
HOLY HEAVEN
so will be enough 1 wallet on ryzen and all other my machines enough to install only boinc and add to group?   :o

You can add many Rosetta accounts to the same wallet. On the bottom it will show all the CPIDs once you restart the GUI.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 02:48:42 pm
You can add many Rosetta accounts to the same wallet. On the bottom it will show all the CPIDs once you restart the GUI.

But we recommend one cpid, the only way you have multiple CPIDs is if you create multiple rosetta accounts.
I just have two because im testing two cpids.

99.9% of the users should have one cpid per wallet and multiple machines crunching.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on February 11, 2018, 03:00:56 pm
Some more info about Rosetta on ARM platform. I was able to run Rosetta@Home on my Samsung Android tablet (ARMv7) with the app from the Google Play Store!
But it seems that Rosetta@Home does not support ARM on Linux (e.g. Rapsberry running Ubuntu Linux), only Android.
Some other Boinc projects do support that, e.g. Einstein@Home.

Logs from the same ARM Linux machine:


11-Feb-2018 20:20:15 [Rosetta@home] Scheduler request completed: got 0 new tasks
11-Feb-2018 20:20:15 [Rosetta@home] This project doesn't support computers of type arm-unknown-linux-gnueabihf


11-Feb-2018 20:38:41 [Einstein@Home] Scheduler request completed: got 7 new tasks
11-Feb-2018 20:38:34 [Einstein@Home] Sending scheduler request: To fetch work.
11-Feb-2018 20:38:34 [Einstein@Home] Requesting new tasks for CPU
11-Feb-2018 20:38:45 [Einstein@Home] Computation for task p2030.20161119.G201.74-00.63.S.b2s0g0.00000_2499_0 finished


This list of projects shows what platforms are supported by what projects, ad it seems that ARM+Linux is not supported by Rosetta:
https://boinc.berkeley.edu/projects.php

Do we have some contact on Rosetta@Home devs/admins? If they support ARM on Android, I do not see a reason for not supporting ARM on Linux, it must be just a server setting...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 11, 2018, 03:01:32 pm
WOHOOOOOOO .... PEEEEEEEERFECT!!!!

im curious what will be with our botnet..... may be botnet will be best for us .. hehehe


1. ryzen working on virtual box: when i set genproclimit=1 my CPU laterz overload to 100%= may be ROSETTA
2. can i to use on Windows boinc-manager for virtual? i want to reduce loading my CPU or i have to set in boinc-client any command?


thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 11, 2018, 03:46:05 pm
WOHOOOOOOO .... PEEEEEEEERFECT!!!!

im curious what will be with our botnet..... may be botnet will be best for us .. hehehe


1. ryzen working on virtual box: when i set genproclimit=1 my CPU laterz overload to 100%= may be ROSETTA
2. can i to use on Windows boinc-manager for virtual? i want to reduce loading my CPU or i have to set in boinc-client any command?


thanks


It has to be Rosetta, as BBP probably uses about 20% with 1 proc set.  We can add a default to bbp to sleep for 1ms per biblehash when we deploy this, unless user sets fullbore=true in the config, that will allow 99% cpu usage in the future for rosetta.

Anyway you will have to google how to control Boincs configurations.  I recommend installing"boinc manager" from the wiki on post #1, then you can click the menu option to tailor the preferences.

It runs on linux and windows.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 12, 2018, 03:16:06 am
my RAC and magnitude is still 0  ???
its working very weird :
what is minirosetta ? i see it in processes

rosetta using only physical core? whats with logical?

edit:// now using all logical cores...it needs any time
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 07:49:26 am
my RAC and magnitude is still 0  ???
its working very weird :
what is minirosetta ? i see it in processes

rosetta using only physical core? whats with logical?

edit:// now using all logical cores...it needs any time
What is your CPID?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 08:47:16 am
Not sure what happened, half of the vms had some sort of problem this morning, vncserver not working, biblepay-qt closed. Just restarted them all again. I wonder if it's because I'm using 0.6GB VMs with shared vcpus.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 12, 2018, 09:05:32 am
What is your CPID?

dde30f3ef57ed2df69ecbc687db75e46
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 09:33:32 am
dde30f3ef57ed2df69ecbc687db75e46

Your doing something wrong; your not in the magnitude file, your not in the filtered file, your not even in the boinc global stats anywhere:
http://boinc.netsoft-online.com/e107_plugins/boinc/get_user.php?cpid=6785ded1f65063ef8f01f42deb31cf1d

(Change your friend from Slovakia CPID to your CPID in the above query)

Please work with Mike-T to get your system working.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 09:34:45 am
Not sure what happened, half of the vms had some sort of problem this morning, vncserver not working, biblepay-qt closed. Just restarted them all again. I wonder if it's because I'm using 0.6GB VMs with shared vcpus.

Im not seeing that problem on my end, my hosts are all still running, but I am seeing my dev testnet node went out of sync.  Let me do some testing on this end regarding that now.

On your side though I think you might have maxxed out resources with too much boinc.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 09:49:52 am
dde30f3ef57ed2df69ecbc687db75e46

Did you get it working?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 09:54:53 am
Did you get it working?

One helpful hint I want to share with you all:  After you associate a CPID and while you still have 0 magnitude, If you can get the newbie to relay to you the amount of RAC from his boinc screen it should match the:
CPID_RAC: XXX  message in 'exec getboincinfo'.  This is going to be extermely helpful in debugging people who are < 24 hours old.  Obviously since he didnt paste his exec getboincinfo like we asked him a few times, hes obviously not even reading anything here.

So have him paste that and look at the line with "_RAC:" in it , and that shows progress between 0 hrs and 24 hours.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 10:17:45 am
One helpful hint I want to share with you all:  After you associate a CPID and while you still have 0 magnitude, If you can get the newbie to relay to you the amount of RAC from his boinc screen it should match the:
CPID_RAC: XXX  message in 'exec getboincinfo'.  This is going to be extermely helpful in debugging people who are < 24 hours old.  Obviously since he didnt paste his exec getboincinfo like we asked him a few times, hes obviously not even reading anything here.

So have him paste that and look at the line with "_RAC:" in it , and that shows progress between 0 hrs and 24 hours.

Yes, that's a good idea.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 12, 2018, 11:20:06 am
ROB what are you talking about... who is imrich?

im here

https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=1982089


is this true?

10% Charity
10% IT/PR/P2P

35% Sanctuary
35% BOINC Rosetta Resarching Mining
10% POW Heat Mining
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 11:58:53 am
ROB what are you talking about... who is imrich?

im here

https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=1982089


is this true?

10% Charity
10% IT/PR/P2P

35% Sanctuary
35% BOINC Rosetta Resarching Mining
10% POW Heat Mining

That is the plan for the percentages.

Did you add your Rosetta account to your wallet? Please post "exec getboincinfo" and what is your RAC on the BOINC program?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 12:26:34 pm
Thanks for trying dude, yea it will be highly beneficial if someone figures out a model of cell phone or tablet that actually runs it.
You might have to google the Rosetta forums to find one particular flavor that actually works...
Hi, I've tried boinc on my ARM based Samsung Galaxy S7... It works fine, after approx. 9 hours it solves 4 tasks (I set up 4 cores) with approx. 60 credits/task.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 12:36:43 pm
ROB what are you talking about... who is imrich?

im here

https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=1982089


is this true?

10% Charity
10% IT/PR/P2P

35% Sanctuary
35% BOINC Rosetta Resarching Mining
10% POW Heat Mining

So you lied about your CPID.   If the link you posted is correct your cpid is actually:
e420467693e9d8c8f163e283bef5068a

LOL,  Why even answer any questions if you wont tell the truth about the most basic starting point.

LOL
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 12:37:37 pm
So you lied about your CPID.   If the link you posted is correct your cpid is actually:
e420467693e9d8c8f163e283bef5068a

LOL,  Why even answer any questions if you wont tell the truth about the most basic starting point.

LOL

Rob, I think I already helped him solver the problem over discord. Maybe there is some sort of communication roadblock.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 12:38:39 pm
Hi, I've tried boinc on my ARM based Samsung Galaxy S7... It works fine, after approx. 9 hours it solves 4 tasks (I set up 4 cores) with approx. 60 credits/task.

Thats awesome dude, this is extremely good to know. 

I wonder what the S7 will earn someone in a full month by itself in 90 days... 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 12:41:55 pm
Rob, I think I already helped him solver the problem over discord. Maybe there is some sort of communication roadblock.
Yeah he probably started more than one CPID anyway.

Irmisch was your friends CPID on our team.

I just wanted to show how to pull up RAC by a CPID on the web.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 12:42:30 pm
Thats awesome dude, this is extremely good to know. 

I wonder what the S7 will earn someone in a full month by itself in 90 days...

Yes, that will be interresting to know... S7 has 8 cores, I just tried 4 of them. I set up it to work only when charging. Maybe I will leave it and we will see in a month what results that gives. But, it is sometimes overheating ;) But there is a option to stop it on overheat, so it can be safe, but maybe not too powerful.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 12, 2018, 01:43:29 pm
So you lied about your CPID.   If the link you posted is correct your cpid is actually:
e420467693e9d8c8f163e283bef5068a

LOL,  Why even answer any questions if you wont tell the truth about the most basic starting point.

LOL
  are you on DRUGS?  who is IMRICH SCHINDLER what you posted

this is me
(https://i.imgur.com/m9LE1jv.png)



Yeah he probably started more than one CPID anyway.

Irmisch was your friends CPID on our team.

I just wanted to show how to pull up RAC by a CPID on the web.

im started only 1 CPID my lover ....
and next time 18 pages about 4 steps installation? damn it ...


again horrible tutorial.....

good tutorial starts this:


1. enough only 1 bbp wallet=    call it  admin-BBP-wallet ... best way is windows wallet
2. reg on rosetta  email+pass, then this command use in admin-BBP-wallet=   exec associate email+pass
3. on all machines enough to install boinc-client (linux) or boinc-manager (windows) and attach to project via AUTH_KEY (linux)  or connect in boinc-manager with email+pass (windows)


a) windows wallet will be main-admin-hot
b,c,d... others machines will be only boinc-clients without BBP wallets

thats all


or do any video like exists on other coins


ORBIS+TMIKE thanks for you help and time.... all my steps was correctly and good ... i had to wait few hours



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 01:50:23 pm
Im a Linux n00b, so it took me awhile to figure out how to use GUI on Linux
(I gave up trying to do it on AWS)

With Vultr I used this guide
https://www.vultr.com/docs/install-gui-environment-for-ubuntu

1. Install Lubuntu GUI and Reboot

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

2. Open server from Vultr Interface and Login:

https://www.vultr.com/
I used Vultr interface, clicked on the server and clicked "View Console" button
I logged in with root credentials

3. Open Terminal:
To open terminal I clicked keys: 

Code: [Select]
CTRL + ALT + T
4. Run BiblePay QT (GUI)

Code: [Select]
cd home/biblepay/src/qt
./biblepay-qt
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 01:52:23 pm
I have a Wiki Guide for PODC I started working on:
http://wiki.biblepay.org/Distributed_Computing_2

If anyone would like to give feedback or add to it, or edit, please do!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 02:26:54 pm
I have a Wiki Guide for PODC I started working on:


If anyone would like to give feedback or add to it, or edit, please do!
I have a question, GUI mode for sanctuary is needed only in testnet or it will be necessary also in prod version when it will be live?
And why it is necessary?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 02:29:54 pm
The GUI is neccessary for Sanctuaries (Masternodes) right now because some of the code we need is in the GUI libraries is my understading
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 02:30:11 pm
I was little bit afraid because of boinc GPU support, but then I've found this thread https://boinc.bakerlab.org/forum_thread.php?id=6475 (https://boinc.bakerlab.org/forum_thread.php?id=6475) and I'm calm again :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 02:32:13 pm
The GUI is neccessary for Sanctuaries (Masternodes) right now because some of the code we need is in the GUI libraries is my understading
Ok, but you can install gui libraries also in command line, or it is not enough?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 02:45:32 pm
Ok, but you can install gui libraries also in command line, or it is not enough?

You will need to have some sort of remote desktop working as Togo mentioned if you want to use the Biblepay GUI.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 02:55:23 pm
You will need to have some sort of remote desktop working as Togo mentioned if you want to use the Biblepay GUI.
I understand, but why it is needed to have gui mode, if you can install gui mode and libraries on command line too.
So will it be necessary in prod version too, or it is just temporary?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 03:03:02 pm
I understand, but why it is needed to have gui mode, if you can install gui mode and libraries on command line too.
So will it be necessary in prod version too, or it is just temporary?

Oh, so in the gui code when it's running, not just installed, it processes the files from Rosetta.

Rob, are you still working on the code to run in headless?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 03:14:43 pm
Oh, so in the gui code when it's running, not just installed, it processes the files from Rosetta.

Rob, are you still working on the code to run in headless?
Thanks... Now I understand.. So we will be waiting if it will be possible to implement without gui.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 03:24:12 pm
Thanks... Now I understand.. So we will be waiting if it will be possible to implement without gui.

That's correct. Did you need help setting up remote desktop on your sanctuary?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 04:15:41 pm
I have a QT (GUI) Sanctuary running now  8)

Address:  144.202.68.232:40001
Payee:  yVdN2ZDGAZ8QnPwfk8cp9L5h1mW9CnewLY
6d1da4.....ce78-1: "PRE_ENABLED"

===

Im going to now test installing and running BOINC on my Linux machine,
and then later I may test re-linking my BOINC credentials to my main machine

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 04:18:59 pm
I have a QT (GUI) Sanctuary running now  8)

Address:  144.202.68.232:40001
Payee:  yVdN2ZDGAZ8QnPwfk8cp9L5h1mW9CnewLY
6d1da4.....ce78-1: "PRE_ENABLED"

===

Im going to now test installing and running BOINC on my Linux machine,
and then later I may test re-linking my BOINC credentials to my main machine

Cool!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 04:48:22 pm
I was little bit afraid because of boinc GPU support, but then I've found this thread https://boinc.bakerlab.org/forum_thread.php?id=6475 (https://boinc.bakerlab.org/forum_thread.php?id=6475) and I'm calm again :D

I'm glad you found that thread!  Thats awesome.  That brings up two Extremely important points we can add to our arsenal, yes three:

Headcount of high paid developers working on rosetta commons Protein Docking Research:
There are 150 developers in 23 universities and laboratories working on various aspects of the coding (Rosetta Commons). So, the idea has been considered from many many perspectives. And, as you quoted, some serious efforts have been made to utilize GPUs.  (In contrast to a few who worked on pow initially, and it is not nearly as elaborate).

No edge for GPUs yet:
Because of the low memory per core, running Rosetta in GPUs takes a little longer than on the CPU.

Anti-hack limiter:
The scientist said that they reject bad or tampered with results, and increment the cpids error count.  If I remember correctly, a few years ago when I ran my boinc project (a quant project for distributed hedge fund analysis), you would be disqualified for asking for more work if you kept sending us bad results (for a certain amount of hours, called the back-off period).  So that is also Stunning, because if Swongles hacker were to try to falsify protein fold results, they would find themselves unable to download new work.

This project is getting better every day :).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 04:52:57 pm
I understand, but why it is needed to have gui mode, if you can install gui mode and libraries on command line too.
So will it be necessary in prod version too, or it is just temporary?

Its different, because headless doesnt compile against the QT5 libs.


The Sanctuaries have to process the PODC files, so they need the QT libs in memory.

Im working on the integrity side now, Im trying to create a pool report that shows some type of integrity level per researcher.
EDIT:  Im going to work on headless PODC now...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 04:58:12 pm
I was able to setup Linux machine with BOINC with 3 commands!

togoshigekata BOINC:
https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=1981221

sudo apt install boinc-client boinc-manager
boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ EMAIL PWD
boinccmd --project_attach https://boinc.bakerlab.org/rosetta/ ACCOUNTKEY

and I used top command to look at CPU usage, and the CPU was auto used up by BOINC

Thanks Luke!

Boinccmd tool:
http://boinc.berkeley.edu/wiki/Boinccmd_tool
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 05:05:00 pm
That's correct. Did you need help setting up remote desktop on your sanctuary?
No, thanks. I think, that I will make it with Togo's manual, but I don't need it. I don't own MN in testnet neither in prod :D That was just for understand things ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 05:06:15 pm
So.... in that case, I have a few other questions :D
1. when will PODC go live? :) EDIT: ok... i saw your post higher Rob, thanks
2. what will happened with credits from rosetta earned in testnet when it goes live?
3. If it will be fresh start (everyone with 0 RAC and magnitude), block will be solved after that 31 minutes rule, but what will be with "rosetta's block" reward within first day or two?
4. How we will change our control wallet from testnet to prod? With "exec associate rosetta_email rosetta_pass force"?
5. How it is magnitude exactly counted?
6. I understand, that there are bilions of combinations needed to be counted, but what if rosetta fullfil their mission?
7. Will be PODC prod update mandatory to all?
Thanks a lot for fullfiling my curiosity :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 12, 2018, 05:10:14 pm
I was able to setup Linux machine with BOINC with 3 commands!

togoshigekata BOINC:


sudo apt install boinc-client boinc-manager
boinccmd --lookup_account  EMAIL PWD
boinccmd --project_attach  ACCOUNTKEY

and I used top command to look at CPU usage, and the CPU was auto used up by BOINC

Thanks Luke!

Boinccmd tool:


Togo, i think that this command
Code: [Select]
boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ EMAIL PWDis useless if you know your CPID.
And it is better to not post your EMAIL and PWD to console ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 05:19:08 pm
EDIT:  Never mind, I decided Im going to jump on working on headless PODC now... It will be more professional...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 05:23:40 pm
Togo, i think that this command
Code: [Select]
boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ EMAIL PWDis useless if you know your CPID.
And it is better to not post your EMAIL and PWD to console ;)

Sure lol, It looks like it needs your Account Key,
I dug into it some more and you can find that here:

Log into: https://boinc.bakerlab.org/rosetta/home.php
Account information >>> Account Keys >>> View OR https://boinc.bakerlab.org/rosetta/weak_auth.php

Updated the guide to reflect that: http://wiki.biblepay.org/Distributed_Computing_2
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 12, 2018, 05:46:46 pm
Hello from Slovakia,  my name is Imrich Schindler :)  (for klondike)
First, thanks to all, which cooperate on this nice idea(Rob, Togo, Alex, Lichtuscher .....) It is great and hard  job.
 I am minnig biblepay since december 2017. I like idea of Biblepay and I'm continualy reading main bitcointalk thread and now this one about PODC testing.

I am testing PODC in testnet on linux. I have installed biblepay 1.0.8.9 from  Lichtsucher ppa(very usefull) and BOINC manager on ubuntu 17.10 .
Testing BOINC on android too (honor 6X)
From my side of view all is working.

Excuse my English, my children are better in english then me :).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 06:09:15 pm
Rob, I'm not sure how far along you've gotten with the validation but I think the best way to do this is to have our own Rosetta manager. I know your aware that there are many task managers out there and they all call out the Rosetta client to do the computational work. From there, you can tie in a piece of code that tells Bible pay that the client is actually running and keep track of the tasks run. From our own manager, you can then also send out the performance data for validation use.

That is what I've come up with after thinking about it through out the day. Then, the only piece left that is not currently in our control is the Rosetta and Rosetta mini clients.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 06:10:35 pm
Hello from Slovakia,  my name is Imrich Schindler :)  (for klondike)
First, thanks to all, which cooperate on this nice idea(Rob, Togo, Alex, Lichtuscher .....) It is great and hard  job.
 I am minnig biblepay since december 2017. I like idea of Biblepay and I'm continualy reading main bitcointalk thread and now this one about PODC testing.

I am testing PODC in testnet on linux. I have installed biblepay 1.0.8.9 from  Lichtsucher ppa(very usefull) and BOINC manager on ubuntu 17.10 .
Testing BOINC on android too (honor 6X)
From my side of view all is working.

Excuse my English, my children are better in english then me :).

Hello! It's good to have you participate in the testnet with us!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: aikida3k on February 12, 2018, 08:28:56 pm
Okay, I am trying to associate my testnet BBP wallet with my Rosetta account.  If someone would send some tBBP, that would be great.  Address
yeqg7xVzYKimDfk5r7FavzWum4XMcJ1AoZ

Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 08:31:45 pm
Sent 5 tBBP your way!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: aikida3k on February 12, 2018, 08:41:46 pm
"Successfully advertised DC-Key"  Cool.  Thanks, Togo!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 09:34:48 pm
Rob, I'm not sure how far along you've gotten with the validation but I think the best way to do this is to have our own Rosetta manager. I know your aware that there are many task managers out there and they all call out the Rosetta client to do the computational work. From there, you can tie in a piece of code that tells Bible pay that the client is actually running and keep track of the tasks run. From our own manager, you can then also send out the performance data for validation use.

That is what I've come up with after thinking about it through out the day. Then, the only piece left that is not currently in our control is the Rosetta and Rosetta mini clients.


Possibly.  I think I can actually scrape all that intercommunication between rosetta and boinc anyway (using the opensource boinc protocol), but I was thinking of that part of it, and whether we trust that log or trust our auditor - Im wondering if we start by assigning an auditor, thats you, we create some web reports (thinks like task turnaround speed per machine, ghz & cores per machine, with some metrics) and make the auditors record the "reference machine"for biblepay.  You can read your row and "certify"it (thats our scale).

Then I base the integrity value on other rolled up users values vs. the auditors.  Then we look at it and try to figure ways to improve it - and try to figure out how "weak"it actually is.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 09:38:27 pm
Hello from Slovakia,  my name is Imrich Schindler :)  (for klondike)
First, thanks to all, which cooperate on this nice idea(Rob, Togo, Alex, Lichtuscher .....) It is great and hard  job.
 I am minnig biblepay since december 2017. I like idea of Biblepay and I'm continualy reading main bitcointalk thread and now this one about PODC testing.

I am testing PODC in testnet on linux. I have installed biblepay 1.0.8.9 from  Lichtsucher ppa(very usefull) and BOINC manager on ubuntu 17.10 .
Testing BOINC on android too (honor 6X)
From my side of view all is working.

Excuse my English, my children are better in english then me :).

Welcome aboard!

Glad to have you here, now we have users from High Tatras, Skok, Sucha Bela, and Bratislava!  Its an honor to have you here, we roll out the red carpet.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 12, 2018, 09:40:53 pm
EDIT:  Never mind, I decided Im going to jump on working on headless PODC now... It will be more professional...

Alright, finally cracked it.  Starting tomorrow we can have headless Sanctuaries again.

Ill get this networking file manager and CPID business logic rule tested in the morning then we will need a mandatory testnet upgrade so we can all test the enforcement of the botnet busting rules (and test the headless).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 09:52:42 pm
Alright, finally cracked it.  Starting tomorrow we can have headless Sanctuaries again.

Ill get this networking file manager and CPID business logic rule tested in the morning then we will need a mandatory testnet upgrade so we can all test the enforcement of the botnet busting rules (and test the headless).

Fantastic work Rob! 8)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 09:58:43 pm
Alright, finally cracked it.  Starting tomorrow we can have headless Sanctuaries again.

Ill get this networking file manager and CPID business logic rule tested in the morning then we will need a mandatory testnet upgrade so we can all test the enforcement of the botnet busting rules (and test the headless).

That's great! And the exchanges can have a different version of the daemon to run without the additional libraries?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 10:05:08 pm

Possibly.  I think I can actually scrape all that intercommunication between rosetta and boinc anyway (using the opensource boinc protocol), but I was thinking of that part of it, and whether we trust that log or trust our auditor - Im wondering if we start by assigning an auditor, thats you, we create some web reports (thinks like task turnaround speed per machine, ghz & cores per machine, with some metrics) and make the auditors record the "reference machine"for biblepay.  You can read your row and "certify"it (thats our scale).

Then I base the integrity value on other rolled up users values vs. the auditors.  Then we look at it and try to figure ways to improve it - and try to figure out how "weak"it actually is.

Yes Rob, it would be difficult to do so many things at once, let's start with the auditing. I'll think about what would be the way to expose altered data from the client data being sent to the servers. I did notice that on the BOINC website you can disable showing your computer details but we still have access to it through the files from the BOINC servers?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 10:12:47 pm
Interesting, the 32-bit clients seem to be faster than the 64-bit ones.

https://boinc.bakerlab.org/rosetta/host_app_versions.php?hostid=3349357
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 12, 2018, 10:31:28 pm
Anyone know how to maximize BOINC CPU in command line on Linux?

I just checked on my Linux machine with top command noticed only 7 boinc/rosetta threads running at 100% CPU,
when I was expecting to see 16 threads at 100% CPU (like I saw after first installing BOINC and linking Rosetta)

I found some config files in the /etc/boinc-client folder: cc_config.xml and global_prefs_override.xml

References:
http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu
https://boinc.berkeley.edu/wiki/BOINC_Data_directory
http://boinc.berkeley.edu/wiki/Boinccmd_tool
http://boinc.berkeley.edu/wiki/Client_configuration

This guide shows a giant config file:
https://www.digitalocean.com/community/tutorials/how-to-set-up-seti-home-on-ubuntu-14-04-or-debian-7
cpu_usage_limit option stands out

Ill poke around some more tomorrow
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 12, 2018, 10:33:51 pm
Why do they make RAC decrease by a factor of 2 every week. So even if I'm doing 200 cobblestones a week the next week it's a 100 RAC?

http://boinc.berkeley.edu/wiki/Computation_credit
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 12, 2018, 11:36:21 pm
I have just tried running boinc on ARM. Not successful though, I'm not getting any tasks :

11-Feb-2018 15:15:24 [Rosetta@home] Sending scheduler request: To fetch work.
11-Feb-2018 15:15:24 [Rosetta@home] Requesting new tasks for CPU
11-Feb-2018 15:15:27 [Rosetta@home] Scheduler request completed: got 0 new tasks
11-Feb-2018 15:15:27 [Rosetta@home] This project doesn't support computers of type aarch64-unknown-linux-gnu

Anyone  else tried ARM (e.g. Raspberry?)

The first machine I tried was an ARM (aarch64) and didn't work.  This is because, I believe, Rosetta does not craft their work units to process correctly in ARM.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 13, 2018, 12:21:38 am
I was able to setup Linux machine with BOINC with 3 commands!

togoshigekata BOINC:
https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=1981221

sudo apt install boinc-client boinc-manager
boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ EMAIL PWD
boinccmd --project_attach https://boinc.bakerlab.org/rosetta/ ACCOUNTKEY

and I used top command to look at CPU usage, and the CPU was auto used up by BOINC

Thanks Luke!

Boinccmd tool:
http://boinc.berkeley.edu/wiki/Boinccmd_tool

You're better off going to the website at https://boinc.bakerlab.org/rosetta, click on the link by Account Keys that says "View" and copy your "weak" password.  Then use that "weak" password on shared computers or really everywhere!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on February 13, 2018, 01:43:34 am
The first machine I tried was an ARM (aarch64) and didn't work.  This is because, I believe, Rosetta does not craft their work units to process correctly in ARM.

That is a shame - I actually do have several ARM servers that I use to mine BBP currently. I would love to use them for rosetta too. Not mentioning all the Raspberry/Bananapi/Odroid computers that geeks like me usually have at home :) and could be leveraged.

As I wrote, if ARM works with Android (working on my tablet), it should work with Linux - I guess it just needs to be set up at rosetta servers.. And it works for some other boinc projects, e.g. Einstein (https://boinc.berkeley.edu/projects.php). If there is a good point of contact for Rosetta, I would try to reach them and ask for adding ARM+Linux support.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 07:46:03 am
Anyone know how to maximize BOINC CPU in command line on Linux?

I just checked on my Linux machine with top command noticed only 7 boinc/rosetta threads running at 100% CPU,
when I was expecting to see 16 threads at 100% CPU (like I saw after first installing BOINC and linking Rosetta)

I found some config files in the /etc/boinc-client folder: cc_config.xml and global_prefs_override.xml

References:
http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu
https://boinc.berkeley.edu/wiki/BOINC_Data_directory
http://boinc.berkeley.edu/wiki/Boinccmd_tool
http://boinc.berkeley.edu/wiki/Client_configuration

This guide shows a giant config file:
https://www.digitalocean.com/community/tutorials/how-to-set-up-seti-home-on-ubuntu-14-04-or-debian-7
cpu_usage_limit option stands out

Ill poke around some more tomorrow
Just an fyi btw, another way to do it is to copy the client_state.xml in linux to a backup, then install boinc manager GUI on linx (apt-get install boinc-manager), then run the boinc-manager from the linux desktop (requires graphics) then go into Advanced mode from Tools | Advanced, then make the changes using the settings and preferences, then take a diff of client_state.xml (see what changed) then export those keys to a file, then you will know what to change on every new box in the future.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 07:49:34 am
That's great! And the exchanges can have a different version of the daemon to run without the additional libraries?
I was able to do it with Open SSL, so they dont need anything.  I made sure to say around our function - If this is Not a Sanctuary - exit immediately.  This way when Bittrex audits our code and says what is this for, they wont get question listing us, as they are highly suspicious of anything that has outside access inside an exchange.  As long as they are not a sanctuary, their node will not do anything funny.  It should pass code review.

But anyway, no they (and we) don't need any additional software libs now.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 07:53:00 am
https://en.wikipedia.org/wiki/BOINC_Credit_System

Please read the part on RAC, is there any information on exactly how it's calculated? Even though the statement needs verification on the wiki, I think we should calculate our own from the credits of each task which would be more accurate. If the statement is true, it looks like maybe you can trick the RAC to being higher possibly by having a higher benchmark score. I will also try to find out how the credits are calculated.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 07:56:21 am
Why do they make RAC decrease by a factor of 2 every week. So even if I'm doing 200 cobblestones a week the next week it's a 100 RAC?

http://boinc.berkeley.edu/wiki/Computation_credit
RAC is a very cool float.  Think of it as the half life of a piece of uranium.  It takes computing power to build it up, then it decays over a one month period with the half life being 2 weeks.  Its very useful to show exactly where a researcher is in the work curve.  If you have been researching for one month solid before you come to Biblepay, we know with certainty how much effort you already put in and can confidently pay you in the next superblock based on your RAC.  It ends up being a perfect representation to rank Rosetta users side by side using disparate equipment.  ( Our biblepay magnitude is also based on the sum of Rosetta RAC and our available budget, so your in-client magnitude is Your next DC superblock share as a percent * 10).

If you want to see work done over a one day period, you can instead look at total credit delta.  Look at todays total credit minus yesterdays total credit.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 08:01:38 am
The first machine I tried was an ARM (aarch64) and didn't work.  This is because, I believe, Rosetta does not craft their work units to process correctly in ARM.

Yeah, I can add a couple additional things need done to host an ARM project on boinc.  Its not a limitation of Boinc or the Rosetta Project.

Basically, the Build of Rosetta produces a long compatibility string, something such as "Linux 64 - ARM - Kaeplin" and when the Rosetta developer finds that string, they have to ask Rosetta web admin to add it as a project type (So then Rosetta supports Windows, Mac, Linux, Arm Kaeplin).  After that nothing works yet.  Then they have to have config manager build a Kaeplin build.  Then Network manager configure the outputs to go in the Kaeplin directory.  Then enable Boinc Rosetta to serve those workunits.  Then script a program to Create work units for Kaeplin. 

So its everything from a custom build for that proc to enabling that proc for the project.  They probably only support one Arm build at this time, whatever one is in the google play store that works on the galaxy s7.

You can make posts in the Rosetta forums asking them to support more Arm flavors.   You can get the string from the task scheduler error, where it says Project has no tasks available for "Arm xxxxxx".

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 08:04:00 am
https://en.wikipedia.org/wiki/BOINC_Credit_System

Please read the part on RAC, is there any information on exactly how it's calculated? Even though the statement needs verification on the wiki, I think we should calculate our own from the credits of each task which would be more accurate. If the statement is true, it looks like maybe you can trick the RAC to being higher possibly by having a higher benchmark score. I will also try to find out how the credits are calculated.
Its just the half life of your recent credit added in the last month.  Actually its very accurate. 
I dont understand why you would want something different - how could anyone tamper with it?  Its not possible.  No researcher has access to the Rosetta validator or write access to the boinc network.

Its already more accurate than anyone would ever need.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 08:53:01 am
Its just the half life of your recent credit added in the last month.  Actually its very accurate. 
I dont understand why you would want something different - how could anyone tamper with it?  Its not possible.  No researcher has access to the Rosetta validator or write access to the boinc network.

Its already more accurate than anyone would ever need.

I understand the decreasing by a factor of 2 part now. That's for the old number and then the new current RAC is added to it.

I was just trying to see if the RAC and credit given was fair and not easy to manipulate. I read the paragraph again and understand it a little better now, it does not appear the RAC is tamperable so far.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 09:32:56 am
It appears every project has a different credit system. Rosetta's credit system seems pretty good so far.

https://boinc.bakerlab.org/forum_thread.php?id=2194
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 10:04:59 am
1.0.9.0b-Mandatory Upgrade for Testnet

- Allow headless to participate in SanctuaryQuorum
- Enabled CPID botnet busting rule (requires each block to have signed and associated CPIDs with Magnitude in order to mine (and we enforce distinct CPIDs over 5 block periods))

* Windows is still compiling *



*** ALL : I have discovered that by moving up to version 1.0.9.0 and enforcing it (since we don't want to touch the Protocol Version in Prod) for some reason, the nodes are now interpreting "1090" as "109".  Therefore, I had to check in some code to allow the wallet to understand we are on 1090.  Please upgrade to 1090b in Testnet and please discard the last 1090 version.  (Otherwise, we cant connect).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 13, 2018, 10:32:09 am
it looks, that rosetta is too much for VPS. I'm testing it on one of my VPS and in last two days it freeze up 3 times. No respond from VPS and only solution was restart. Then it works for some time and freeze again.. I must find solution how to limit cpu resources :) Is here anyone else testing VPS?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 10:45:54 am
it looks, that rosetta is too much for VPS. I'm testing it on one of my VPS and in last two days it freeze up 3 times. No respond from VPS and only solution was restart. Then it works for some time and freeze again.. I must find solution how to limit cpu resources :) Is here anyone else testing VPS?

Did you try something similar to this yet?
https://boinc.berkeley.edu/dev/forum_thread.php?id=3113

Or you can do this for any process:
https://www.tecmint.com/cputool-limit-linux-process-cpu-usage-load/
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 11:29:03 am
1.0.9.0b-Mandatory Upgrade for Testnet

- Allow headless to participate in SanctuaryQuorum
- Enabled CPID botnet busting rule (requires each block to have signed and associated CPIDs with Magnitude in order to mine (and we enforce distinct CPIDs over 5 block periods))

* Windows is still compiling *



*** ALL : I have discovered that by moving up to version 1.0.9.0 and enforcing it (since we don't want to touch the Protocol Version in Prod) for some reason, the nodes are now interpreting "1090" as "109".  Therefore, I had to check in some code to allow the wallet to understand we are on 1090.  Please upgrade to 1090b in Testnet and please discard the last 1090 version.  (Otherwise, we cant connect).


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 11:38:55 am
1.0.9.0b-Mandatory Upgrade for Testnet

- Allow headless to participate in SanctuaryQuorum
- Enabled CPID botnet busting rule (requires each block to have signed and associated CPIDs with Magnitude in order to mine (and we enforce distinct CPIDs over 5 block periods))

* Windows is still compiling *


*** ALL : I have discovered that by moving up to version 1.0.9.0 and enforcing it (since we don't want to touch the Protocol Version in Prod) for some reason, the nodes are now interpreting "1090" as "109".  Therefore, I had to check in some code to allow the wallet to understand we are on 1090.  Please upgrade to 1090b in Testnet and please discard the last 1090 version.  (Otherwise, we cant connect).


Updating all node, not sure if some are compiling 1.0.9.0b though. WIll check after they are done.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 13, 2018, 11:56:45 am
Did you try something similar to this yet?


Or you can do this for any process:

Thanks. I've tried those config options, but didn't work for me. I've used "cpulimit" before, so it seems to be my way :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 13, 2018, 12:07:43 pm
1.0.9.0b-Mandatory Upgrade for Testnet

- Allow headless to participate in SanctuaryQuorum
- Enabled CPID botnet busting rule (requires each block to have signed and associated CPIDs with Magnitude in order to mine (and we enforce distinct CPIDs over 5 block periods))

* Windows is still compiling *



*** ALL : I have discovered that by moving up to version 1.0.9.0 and enforcing it (since we don't want to touch the Protocol Version in Prod) for some reason, the nodes are now interpreting "1090" as "109".  Therefore, I had to check in some code to allow the wallet to understand we are on 1090.  Please upgrade to 1090b in Testnet and please discard the last 1090 version.  (Otherwise, we cant connect).

Rob, this is great work and you were really fast to make Sanctuaries headless.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 12:40:06 pm
Rob, this is great work and you were really fast to make Sanctuaries headless.

Thanks.
Hey guys, there is something up with 1090b.  Im working on it now.  If you cant connect please standby...

Some bug in here dealing with the connection string still.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on February 13, 2018, 12:59:31 pm
Hello all, I want to contribute to this PoDC testing effort.

Could you please send some tBBP to

yWKX5CXuPCJNLLSwUjqwQcUifnYToco1zM

Thank you very much.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 01:07:40 pm
Hello all, I want to contribute to this PoDC testing effort.

Could you please send some tBBP to

yWKX5CXuPCJNLLSwUjqwQcUifnYToco1zM

Thank you very much.

Sent 1 mil, but youll probably have to upgrade in about 15 mins, as I did discover a bug.


Will update everyone ASAP.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 01:14:26 pm
Thanks.
Hey guys, there is something up with 1090b.  Im working on it now.  If you cant connect please standby...

Some bug in here dealing with the connection string still.

I believe the problem is fixed.  Everyone must upgrade though.  Please upgrade to 1090f.

Windows is now rebuilding.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 01:19:51 pm
Some more info about Rosetta on ARM platform. I was able to run Rosetta@Home on my Samsung Android tablet (ARMv7) with the app from the Google Play Store!
But it seems that Rosetta@Home does not support ARM on Linux (e.g. Rapsberry running Ubuntu Linux), only Android.
Some other Boinc projects do support that, e.g. Einstein@Home.

Logs from the same ARM Linux machine:


11-Feb-2018 20:20:15 [Rosetta@home] Scheduler request completed: got 0 new tasks
11-Feb-2018 20:20:15 [Rosetta@home] This project doesn't support computers of type arm-unknown-linux-gnueabihf


11-Feb-2018 20:38:41 [Einstein@Home] Scheduler request completed: got 7 new tasks
11-Feb-2018 20:38:34 [Einstein@Home] Sending scheduler request: To fetch work.
11-Feb-2018 20:38:34 [Einstein@Home] Requesting new tasks for CPU
11-Feb-2018 20:38:45 [Einstein@Home] Computation for task p2030.20161119.G201.74-00.63.S.b2s0g0.00000_2499_0 finished


This list of projects shows what platforms are supported by what projects, ad it seems that ARM+Linux is not supported by Rosetta:
https://boinc.berkeley.edu/projects.php

Do we have some contact on Rosetta@Home devs/admins? If they support ARM on Android, I do not see a reason for not supporting ARM on Linux, it must be just a server setting...

Hi, could you tell me how many cores your using on your ARM device for Rosetta? Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 13, 2018, 01:33:00 pm
I believe the problem is fixed.  Everyone must upgrade though.  Please upgrade to 1090f.

Windows is now rebuilding.

Upgrading...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 13, 2018, 02:21:40 pm
Ive upgraded to 1.0.8.9f and have 2 sanctuaries in PRE_ENABLED state :)

I checked my BOINCing Linux machine and it was down to 3 threads at 100%, Ill install a GUI package and play with the manager and report back
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 13, 2018, 02:49:12 pm
I upgraded just now. But I cannot find a block source.
How can I fix this?
Thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on February 13, 2018, 02:54:11 pm
Hi, could you tell me how many cores your using on your ARM device for Rosetta? Thanks.

None. Rosetta does not work on ARM on Linux:

13-Feb-2018 20:43:01 [Rosetta@home] This project doesn't support computers of type arm-unknown-linux-gnueabihf
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 03:02:17 pm
I upgraded just now. But I cannot find a block source.
How can I fix this?
Thanks

Please try deleting banlist.dat, (in \testnet3) and restart? Ill unban all nodes now also.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 03:05:11 pm
None. Rosetta does not work on ARM on Linux:

13-Feb-2018 20:43:01 [Rosetta@home] This project doesn't support computers of type arm-unknown-linux-gnueabihf

Sorry, I meant your android device. It is also an ARM device.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 03:12:21 pm
Ok I see 13 of us are synced again, nice job!

So what we have to double check regarding this CPID signature feature :

1) That we have not introduced instability.  Your node should not crash when syncing.
2) You should not be able to mine unless you have an active CPID on that node.  You can type 'exec getboincinfo' - we use the cpid from the "CPID:" column to sign the block.  That CPID also must be in the chain (in the 'exec listdccs' in column 1, that means the CPID is securely associated).  If you can mine without a CPID something is wrong.  Note on masternodes mining does not start until chain is synced so please be patient.  Ensure HPS > 0 in getmininginfo if you have a CPID.
3) You should see the CPID and the signature on almost every block now.  Type 'showblock height'.  The column CPID is the signed CPID that mined the block.  The Signature: true/false is if it passed the signature and the magnitude test (we require a distinct CPID that has magnitude).

4) Note: The only exception is if the block span is > 15 mins (the new late block threshhold, this means no one has solved a block in 15 mins in testnet), we do accept the block from anyone- that keeps the chain from sticking if Rosetta is down, or if no other miner with a CPID is around.
So, if you find a showblock with a missing CPID, check the HRTime and subtract that HRTime from the previous block HRTime and it should be > 15 mins.  If so, things are still OK and working.


 I appreciate if people can test this with me relatively thoroughly so we have no surprises in prod, lets bust that botnet successfully in one shot.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on February 13, 2018, 03:14:04 pm
Sorry, I meant your android device. It is also an ARM device.

ah, yeah. It seems that just half of them, 4 out of 8.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 03:15:47 pm
I believe the problem is fixed.  Everyone must upgrade though.  Please upgrade to 1090f.

Windows is now rebuilding.

Rob, I just finished updating my 10 nodes.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 03:16:38 pm
ah, yeah. It seems that just half of them, 4 out of 8.

Thanks man. Trying to figure out which device is best for Rosetta.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 13, 2018, 03:18:49 pm
https://boinc.bakerlab.org/rosetta/stats.php >>> Top Computers  and CPU Performance
Looks interesting
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 03:18:55 pm
Rob, I just finished updating my 10 nodes.
Wow thats a lot.  Sweet.
So you would be one really with an extensive getboincinfo.  Do your rewards look OK when you add all the RAC together in getboincinfo, your magnitude is probably 500-700.  Mine is about 350 (now that it has been declining daily due to the increased participation).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 13, 2018, 03:21:46 pm
https://boinc.bakerlab.org/rosetta/stats.php >>> Top Computers  and CPU Performance
Looks interesting

Yeah, the top dog has 120 procs.  His RAC is 59* what mine is, so it sounds correct.
Brings up the point though, when one of those big dogs find out they can be paid by BBP, one with hog up about the equivalent of 59 PC's in power.
The question is, will they buy BBP on the market to be investors?  Maybe a certain % will.  Eventually with this "integrity" system we may want to include some element of POS in PODC, and that will encourage some of these pure researchers to buy some BBP to "mine" with.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on February 13, 2018, 03:26:30 pm
Sent 1 mil, but youll probably have to upgrade in about 15 mins, as I did discover a bug.


Will update everyone ASAP.

Thank you. I'll wait until it's ready.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 03:29:09 pm
Wow thats a lot.  Sweet.
So you would be one really with an extensive getboincinfo.  Do your rewards look OK when you add all the RAC together in getboincinfo, your magnitude is probably 500-700.  Mine is about 350 (now that it has been declining daily due to the increased participation).

"Command": "getboincinfo",
  "CPID": "f80ab050ab53459ec937879a046d603e",
  "Address": "yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;71f1f1f46deb2f25961c7d9af06f2b31;95a79cd5829e8315b0b946709930df18;c
c37d0ef74a621379974484f43d3b1c5;f80ab050ab53459ec937879a046d603e;",
  "CPID-Age (hours)": 421821,
  "NextSuperblockHeight": 9207,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 450586762905843,
  "71f1f1f46deb2f25961c7d9af06f2b31_RAC": 82778636,
  "95a79cd5829e8315b0b946709930df18_RAC": 51586493,
  "cc37d0ef74a621379974484f43d3b1c5_RAC": 90685327,
  "f80ab050ab53459ec937879a046d603e_RAC": 50242464,
  "Total Payments (One Day)": 175686,
  "Total Payments (One Week)": 1394916,
  "Total Budget (One Day)": 2730420,
  "Total Budget (One Week)": 55107360,
  "Superblock Count (One Week)": 68,
  "Superblock Hit Count (One Week)": 41,
  "Superblock List": "9108,8613,8217,8118,8019,7821,7425,7326,7128,7029,6831,6732,6633,6534,6435,6336,6138,5940,
5841,5742,5643,5247,5148,5049,4950,4851,4752,4653,4554,4455,4356,4257,4158,3762,3465,3168,3069,2772,2673,2574,24
75",
  "Last Superblock Budget": 1386000,
  "Last Superblock Height": 9108,
  "Last Superblock Payment": 30879,
  "Magnitude": 25.31269870304076

Can you explain all the items here briefly? Togo can use this information to add to the wiki. Like why is the RAC number different compared to the BOINC RAC.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 13, 2018, 03:41:28 pm
Sorry, I meant your android device. It is also an ARM device.
Mike, I have ARM based Galaxy S7. I run rosetta with 4 cores. I tested 8 cores too, but phone was too hot :) it seems that 6 cores will be fine too. But my phone has 4GB RAM.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 03:54:08 pm
Looks like I've been alternating with someone else signing blocks from 9186 - 9190. Are you not allowed to sign 2 blocks consecutively? I have also confirmed that the miner works on a wallet that has a CPID tied to it and does not mine on one that doesn't.

I forgot to delete the wallet from my controller instance when I made the clones so now it looks like I can mine with all the other instances as well. I did delete the wallet on one of them to see if it would mine, it would not mine.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 03:59:20 pm
Mike, I have ARM based Galaxy S7. I run rosetta with 4 cores. I tested 8 cores too, but phone was too hot :) it seems that 6 cores will be fine too. But my phone has 4GB RAM.

Per my calculations right now, you would need 4~8 more recent android phones to match the computing power of a dual Xeon E7-4820 server which currently runs about $1,000USD used.

Now you would save a lot of power, each phone uses about 5W compared to the server mentioned which probably uses about 350W. If you had 8 phones that would be 40W, about a 10th of the power of the server, That alone is a $27 different in electricity cost per month. In one year you would be spending $324 more on the server. It might be work looking into a phone and tablet mining rig.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 04:14:29 pm
Let's all stop mining on the wallet and see what happens. I have one miner turned on that doesn't have a CPID associated with it.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 13, 2018, 04:16:54 pm
Per my calculations right now, you would need 4~8 more recent android phones to match the computing power of a dual Xeon E7-4820 server which currently runs about $1,000USD used.
It is possible. On my phone calculations run only on charger, so not more than 6-8 hours/day :) so it is only "for fun".
Here are some stats: avg. speed 2.27 GFLOPS, avg time/task 9 hours with 4 hours cpu time, avg. credit/task 65 ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 04:22:20 pm
It is possible. On my phone calculations run only on charger, so not more than 6-8 hours/day :) so it is only "for fun".
Here are some stats: avg. speed 2.27 GFLOPS, avg time/task 9 hours with 4 hours cpu time, avg. credit/task 65 ;)

I stopped looking at the GLOPS because it doesn't make any sense if you compare the numbers to other processors. Only the benchmark MFLOPS made sense but it could change depending on what the computer is doing at the time of the benchmark. So you say you have 4 cores running with each task earning 65 credits every 4 hours. That would make it so you need 4x Galaxy S7s running at the same time to match the referenced server.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 04:30:04 pm
Block 9218 was not signed, time difference compared to previous block was >15min.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 13, 2018, 05:03:46 pm
If anyone wants to edit the guide Ive written for PODC (Proof of Distributed Computing), please do!
http://wiki.biblepay.org/Distributed_Computing_2

I just wrote it so there'd be step by step instructions for noobs like me to start research mining (and helping test)

I believe anyone can create a wiki account :)

Id have to probably read through this whole thread a few times to understand it all,
I understand on the surface level most of what Rob says but there is definitely some deep knowledge here

Rob's guides have a lot of good content:

How to Get Started with Distributed-Computing:
http://wiki.biblepay.org/Distributed_Computing_Start_Guide

Distributed Computing:
http://wiki.biblepay.org/Distributed_Computing
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 13, 2018, 05:05:20 pm
Please try deleting banlist.dat, (in \testnet3) and restart? Ill unban all nodes now also.

Thanks Rob, I am back up and running now!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 13, 2018, 08:39:20 pm
Did something happen? There was only one masternode in the list and I had to restart all of mine.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: aikida3k on February 13, 2018, 10:45:49 pm
I don't have time to chase down why my RAC and Magnitude are zero.  How long does it take for these to ramp up?  It took somewhere around a day for the VPS to show under the "Your Computers" page.  Anyway, thanks for any help or input.   

"Command": "getboincinfo",
  "CPID": "84d803e4d82d3bdcdf8e2ab601e93e20",
  "Address": "yeqg7xVzYKimDfk5r7FavzWum4XMcJ1AoZ",
  "CPIDS": "84d803e4d82d3bdcdf8e2ab601e93e20;",
  "CPID-Age (hours)": 421828,
  "NextSuperblockHeight": 9603,
  "84d803e4d82d3bdcdf8e2ab601e93e20_RAC": 0,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2730420,
  "Total Budget (One Week)": 52335360,
  "Superblock Count (One Week)": 70,
  "Superblock Hit Count (One Week)": 39,
  "Superblock List": "9108,8613,8217,8118,8019,7821,7425,7326,7128,7029,6831,6733168,3069,2772,2673",
  "Last Superblock Budget": 1386000,
  "Last Superblock Height": 9504,
  "Last Superblock Payment": -1,
  "Magnitude": 0
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 14, 2018, 12:15:08 am
Anyone know how to maximize BOINC CPU in command line on Linux?

I just checked on my Linux machine with top command noticed only 7 boinc/rosetta threads running at 100% CPU,
when I was expecting to see 16 threads at 100% CPU (like I saw after first installing BOINC and linking Rosetta)

I found some config files in the /etc/boinc-client folder: cc_config.xml and global_prefs_override.xml

References:
http://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu
https://boinc.berkeley.edu/wiki/BOINC_Data_directory
http://boinc.berkeley.edu/wiki/Boinccmd_tool
http://boinc.berkeley.edu/wiki/Client_configuration

This guide shows a giant config file:
https://www.digitalocean.com/community/tutorials/how-to-set-up-seti-home-on-ubuntu-14-04-or-debian-7
cpu_usage_limit option stands out

Ill poke around some more tomorrow

I installed lubuntu-core and was able to open the BOINC Manager GUI and set my Options >>> Computing Preferences

Is 4GB RAM enough for Rosetta@home?

Also other than those crazy $3k server processors it looks like the AMD Threadripper 1950X for $900 is the best CPU to use, not sure how it plays out budget wise when you also factor in a more expensive motherboard and liquid cooling though. Curious how the power usage/electricity costs play out as well.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 14, 2018, 12:18:12 am
TMike are your sanctuaries all in state: WATCHDOG_EXPIRED?

If needed I can spin up some more testnet sanctuaries but it seems like you got it covered :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 14, 2018, 12:57:05 am
I installed lubuntu-core and was able to open the BOINC Manager GUI and set my Options >>> Computing Preferences

Is 4GB RAM enough for Rosetta@home?

Also other than those crazy $3k server processors it looks like the AMD Threadripper 1950X for $900 is the best CPU to use, not sure how it plays out budget wise when you also factor in a more expensive motherboard and liquid cooling though. Curious how the power usage/electricity costs play out as well.

I've been playing around with it but right now my T3500 with an X5650 is doing pretty decent although your I7-2600K looks like its a monster by comparison (which I wouldn't have guessed by comparing the two CPU on CPUBoss)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 14, 2018, 02:21:55 am
Am I on the right chain guys?

Code: [Select]
09:18:21

getblockhash 9205

09:18:22

6a89484d1a5f0cc703b299f32c1e46584d8aa39ace84bf0f6100c14b08f5ce7d

Also, how to I check the exact version number? 'getinfo'  only says:
Code: [Select]
  "wallet_fullversion": "1.0.9.0",

I'm using boinc on an Android phone now too. Great feature :)

Oh, and the Windows version isn't ready yet, right?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:27:25 am
Forgot to answer this post yesterday sorry,
Please see inline:

So.... in that case, I have a few other questions :D

2. what will happened with credits from rosetta earned in testnet when it goes live?
-> For these credits, or for existing Rosetta researchers who come as new users to BBP, we honor their RAC, their current 2 week average, so technically, you are compensated for work done over the last 2 week period when we go live in prod.

3. If it will be fresh start (everyone with 0 RAC and magnitude), block will be solved after that 31 minutes rule, but what will be with "rosetta's block" reward within first day or two?
-> The people with RAC will have quite an edge in prod against the new users with 0 rac, but remember, anyone from the outside with RAC can take a share right off the bat if they know the project is going live

4. How we will change our control wallet from testnet to prod? With "exec associate rosetta_email rosetta_pass force"?
->  Yes, that is necessary in prod since we have to send out a burn transaction, therefore your CPID goes into the Prod Chain

5. How it is magnitude exactly counted?
->  We harvest a list of DC CPID's in the chain as of the superblock, for each CPID: we sum the current RAC for Rosetta, we sum the Total Rosetta RAC for Biblepay, we divide the Researcher RAC by the Total RAC, yielding a %, this % multipled * 1000 = magnitude. 

6. I understand, that there are bilions of combinations needed to be counted, but what if rosetta fullfil their mission?
-> If Rosetta decides to go out of business, I think first we look at the rest of the boinc projects for something noble, like AIDS, Alzheimers, and we look to adapt the project to their project.

7. Will be PODC prod update mandatory to all?
-> Yes, looks like the community likes it (from the governance vote).



Thanks a lot for fullfiling my curiosity :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:32:51 am
Did something happen? There was only one masternode in the list and I had to restart all of mine.
I think something happened, I must have been dreaming of something "failing" as its 230 AM here and I woke up and thought it was 6AM and started working, I see the hard disk is full in testnet, full of errors, and 2 of my vultr Prod nodes have "Emergency Failures" (this is on the vultr side, they said Non Recoverable), LOL, start of a great morning. 

I need to filter out the log to see whats going on.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:35:54 am
Block 9218 was not signed, time difference compared to previous block was >15min.

Good, that part seems to be working.
As far as How many consecutive can be solved by CPID, right now its set for 4 in prod and 1 in testnet, so a CPID cant be in the last 4 in Prod, and cant be in the Last 1 in testnet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:40:05 am
I don't have time to chase down why my RAC and Magnitude are zero.  How long does it take for these to ramp up?  It took somewhere around a day for the VPS to show under the "Your Computers" page.  Anyway, thanks for any help or input.   

"Command": "getboincinfo",
  "CPID": "84d803e4d82d3bdcdf8e2ab601e93e20",
  "Address": "yeqg7xVzYKimDfk5r7FavzWum4XMcJ1AoZ",
  "CPIDS": "84d803e4d82d3bdcdf8e2ab601e93e20;",
  "CPID-Age (hours)": 421828,
  "NextSuperblockHeight": 9603,
  "84d803e4d82d3bdcdf8e2ab601e93e20_RAC": 0,
  "Total Payments (One Day)": 0,
 
  "Last Superblock Height": 9504,
  "Last Superblock Payment": -1,
  "Magnitude": 0


It generally takes about 24 hours to start seeing things in Biblepay, but lets also tell the users this very important point:
On the boinc side, they can install boinc manager (they probably already did if they are in windows), click View | Advanced View.  View the Rosetta Row. Take a look at the RAC column.  That gives you an idea what your RAC is before it hits biblepay.  Then 6 hours later or so, the RAC in BBP should be close to that figure.  Another way to do it is to log into your Rosetta account, and take a look at your RAC.   Youll probably find it was Zero on the web page also at that particular time.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on February 14, 2018, 02:50:36 am
Do we have Windows version already for 1090f? If you are too busy I can try compile it myself.
Thank you very much
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:52:07 am
Can you explain all the items here briefly? Togo can use this information to add to the wiki. Like why is the RAC number different compared to the BOINC RAC.

Please see inline:

"Command": "getboincinfo",
  "CPID": "f80ab050ab53459ec937879a046d603e",

This is the Primary CPID of the researcher, used on the overview page and for future cosmetic features.
It does not restrict a users payments down to one CPID, but it lets us do things with it like the iPhone does (Sleek features).

  "Address": "yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84",
This is the public bbp receive address associated with the CPID - this is also where rewards will flow into.

  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;71f1f1f46deb2f25961c7d9af06f2b31;95a79cd5829e8315b0b946709930df18;c

c37d0ef74a621379974484f43d3b1c5;f80ab050ab53459ec937879a046d603e;",

This is a list of CPIDs, if you have more than one CPID associated with this wallet.dat.  We iterate through this list in superblock payments to make sure you get full compensation.

  "CPID-Age (hours)": 421821,
This is how many hours your CPID has been alive.  This is useful if you are brand new and waiting for first reward.
We can then show messages like newbie warnings.
  "NextSuperblockHeight": 9207,
This is when the next payment is scheduled.
  "e94c1704c75f731f8bfde303f08408ee_RAC": 450586762905843,
Here, we loop through each of your CPIDs, notice the prefix, and we tally your individual RAC per CPID.
This number should match the BOINC rac on the Rosetta row in the advanced view or in the web portal.

  "f80ab050ab53459ec937879a046d603e_RAC": 50242464,
  "Total Payments (One Day)": 175686,
This is how much BBP you received over 24 hours for researching

  "Total Payments (One Week)": 1394916,
This is how much over one week
  "Total Budget (One Day)": 2730420,
This is how much was available in the budget for 24 hours for researching
  "Total Budget (One Week)": 55107360,
This is how much budget was available in 7 days for researchers
  "Superblock Count (One Week)": 68,
This is the count of PODC Superblocks that passed in one week, whether filled or not filled
  "Superblock Hit Count (One Week)": 41,
This is the number of PODC superblocks that had research payments in them in one week.
** NOTE: The primary reason we missed a superblock is we did not have enough votes in the SanctuaryQuorum,
and that is most likely because some were either off line or not running in QT mode, but now we no longer require QT mode **
  "Superblock List": "9108,8613,8217,8118,8019,7821,7425,7326,7128,7029,6831,6732,6633,6534,6435,6336,6138,5940,
5841,5742,5643,5247,5148,5049,4950,4851,4752,4653,4554,4455,4356,4257,4158,3762,3465,3168,3069,2772,2673,2574,24
75",
This is a list of superblocks with Research payments, very useful for finding a missing payment for a researcher
  "Last Superblock Budget": 1386000,
  "Last Superblock Height": 9108,
  "Last Superblock Payment": 30879,
This is the amount you were compensated in the last superblock
  "Magnitude": 25.31269870304076
Finally this is your magnitude, which is YourRAC/TotalProjectRac * 1000
[/quote]

*** NOTE:
You asked why your _RAC rows were so high and did not match Boinc.

It appears to be a bug and it appears to be affecting people with Multple CPIDs.  Those RACs should match.  It does not appear to be affecting the payments, so its just a display issue.  Ill look at that today.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:58:21 am
Do we have Windows version already for 1090f? If you are too busy I can try compile it myself.
Thank you very much

Sorry, I did compile it but it appears to be buggy, there is something going on in testnet that is emitting huge logs.  So I cant release it.
It looks like the best thing to do if you can is build it on *nix for now.   Later today once we resolve this, Ill rebuild win again.  (The current windows release - that is out there now - is not good for testnet btw).


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 03:55:39 am
1.0.9.1-Mandatory Upgrade for Testnet


- Fix RAC display issues in exec getboincinfo
- Fix runaway connection issues
- Remove unecessary logging
- Fix float precision issue


** Windows is compiling **

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 14, 2018, 04:10:34 am
Ok, I think one nice thing about the PoDC is that we will reduce the number of VPS servers (which were really efficient at PoBH mining). Although I personally used vps to mine PoBH, I think in the long term it is better to rely on physical machines.

So a few stats

Physical server: Dell Power Edge: Xeon(R) CPU E5335 @ 2.00GHz, Quad Core:
                             On PoBH was getting HPS roughly 1000
                              On Rosetta, RAC = roughly 800

Vultr server: 1 cpu (not sure make model etc)
                            On PoBH was getting roughly 700 HPS
                            On Rosetta, RAC = roughly 350.


So the vps was ~70% of the physical server on PoBH, but ~45% on Rosetta.
So it seems, advantage physical machines (And that server I have is old, I imagine a newer i7 will kill a vps)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 07:05:42 am
I think something happened, I must have been dreaming of something "failing" as its 230 AM here and I woke up and thought it was 6AM and started working, I see the hard disk is full in testnet, full of errors, and 2 of my vultr Prod nodes have "Emergency Failures" (this is on the vultr side, they said Non Recoverable), LOL, start of a great morning. 

I need to filter out the log to see whats going on.

Glad you got it fixed, I will compile the new version and wait a day before I deploy the other 9 nodes. It takes me about 2 hours to start all the nodes. No problem, it's just part of testing.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 08:37:33 am
Glad you got it fixed, I will compile the new version and wait a day before I deploy the other 9 nodes. It takes me about 2 hours to start all the nodes. No problem, it's just part of testing.
Cool, I think its working now, Im not seeing anything unusual in the logs. 

I forgot to mention the newest version does have the 100ms sleep feature in the miner, so technically BBP should be using 1% cpu power when mining unless you set 'fullspeed=true'.  This is defaulted to true in prod, of course.

Im the only miner mining right now in testned (ca89*).

So the blocks are taking 15 mins each...


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 08:44:18 am
Cool, I think its working now, Im not seeing anything unusual in the logs. 

I forgot to mention the newest version does have the 100ms sleep feature in the miner, so technically BBP should be using 1% cpu power when mining unless you set 'fullspeed=true'.  This is defaulted to true in prod, of course.

Im the only miner mining right now in testned (ca89*).

So the blocks are taking 15 mins each...

Did you need me to turn on the mining? I think it would be helpful if the sleep feature was a variable from 0-100 so people can adjust it according to their needs.

What else do we need to test right now?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 08:56:19 am
Did you need me to turn on the mining? I think it would be helpful if the sleep feature was a variable from 0-100 so people can adjust it according to their needs.

What else do we need to test right now?

Not sure if it matters though, its on by default, and makes the miner run at 100 HPS or so.  If they turn it off, they can use genproclimit to mine as fast as they want if thats what they insist on.

Uhh, we definitely need to test headless's ability to download the file.  Could you run headless, and do a 'exec dcc' and see if it updates the /SAN files to current timestamp?

Then do an exec testvote also and lets see if we both vote on the same file.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 09:47:56 am
Not sure if it matters though, its on by default, and makes the miner run at 100 HPS or so.  If they turn it off, they can use genproclimit to mine as fast as they want if thats what they insist on.

Uhh, we definitely need to test headless's ability to download the file.  Could you run headless, and do a 'exec dcc' and see if it updates the /SAN files to current timestamp?

Then do an exec testvote also and lets see if we both vote on the same file.

"Command": "testvote",
  "fileage": 303,
  "filehash": "00000000000000000000000000000000747be9068b0b5ae2ae03be8dd0900019",
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 14, 2018, 10:37:39 am
Upgrading my 2 testnet sanctuaries now, one of them I had to totally clean the .dat files and blocks and chainstate folders,
the other one disconnected when compiling

How to Update and Clean Wallets
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on February 14, 2018, 10:41:40 am
Do we have the latest windows version compiled already? I cannot compile it myself even in linux as all my boxes don't have QT installed at the moment so no gui available for me.
Thank you.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 10:58:41 am
Do we have the latest windows version compiled already? I cannot compile it myself even in linux as all my boxes don't have QT installed at the moment so no gui available for me.
Thank you.

With the newest version QT is not required anymore. You just need to compile and run the daemon.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 11:02:40 am
Do we have the latest windows version compiled already? I cannot compile it myself even in linux as all my boxes don't have QT installed at the moment so no gui available for me.
Thank you.


Yeah, it looks like 1.0.9.1 is OK to release.

Windows is out there now guys.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 11:03:12 am
"Command": "testvote",
  "fileage": 303,
  "filehash": "00000000000000000000000000000000747be9068b0b5ae2ae03be8dd0900019",

Looks like we matched, great!

But we will need more hashers out here with CPIDs to speed up these blocks....

Edit: It looks like Im the only one mining.  The mining feature is working, Im mining at 1 HPS!  This is cool, 99.9% available for Rosetta....
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 11:14:56 am
Looks like we matched, great!

But we will need more hashers out here with CPIDs to speed up these blocks....

Edit: It looks like Im the only one mining.  The mining feature is working, Im mining at 1 HPS!  This is cool, 99.9% available for Rosetta....

Yeah, I started the mining, 0.84hps. How much mining power do we need to keep the network operating with 500k transactions per day? I mean, for bitcoin, if there was only 10 people mining, could it process 500k transactions per day?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 11:19:04 am
Yeah, I started the mining, 0.84hps. How much mining power do we need to keep the network operating with 500k transactions per day? I mean, for bitcoin, if there was only 10 people mining, could it process 500k transactions per day?
But lets clarify one thing quickly first, its 1 HPS because we are sleeping, it rises up to more like 100 HPS when the CPID is actually available in an open spot (to mine the next block). 

As far as Tx per day, we would be able to process 32,767 per block * 202 per day, max.  But you would see very high fees after the 7000'th transaction because the size of the block would be very large.  Otoh, our fees are so small, compared to bitcoin, a 1000 bbp fee is still only .20 cent compared to bitcoin $17 fee.

Really you dont need much mining power as long as we are not getting attacked.  DGW kicks in when people throw a lot of hash our way.
In some POS coins like blackcoin, diff can stay at 5.0 for a whole day if hardly anyone is staking, and security is not suffering (as long as they have a wide distribution of holders).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 11:34:21 am
But lets clarify one thing quickly first, its 1 HPS because we are sleeping, it rises up to more like 100 HPS when the CPID is actually available in an open spot (to mine the next block). 

As far as Tx per day, we would be able to process 32,767 per block * 202 per day, max.  But you would see very high fees after the 7000'th transaction because the size of the block would be very large.  Otoh, our fees are so small, compared to bitcoin, a 1000 bbp fee is still only .20 cent compared to bitcoin $17 fee.

Really you dont need much mining power as long as we are not getting attacked.  DGW kicks in when people throw a lot of hash our way.
In some POS coins like blackcoin, diff can stay at 5.0 for a whole day if hardly anyone is staking, and security is not suffering (as long as they have a wide distribution of holders).

Rob, how did you arrive at those numbers in the calculation? So is the fee based on processing time? Like what makes a big block more expensive. Sorry for the NOOB questions.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 11:37:28 am
Rob, how did you arrive at those numbers in the calculation? So is the fee based on processing time? Like what makes a big block more expensive. Sorry for the NOOB questions.
32767 is the biggest transaction vout size that can fit in a block, and after the block gets above 1 Meg in bytes, fees start to get around 100bbp per transaction after 2 meg its more like 1000bbp per tx.  Warnings start appearing on the UI for every tx sent warning you would you like to add this fee to your Tx, or decline and wait?   Its not really based on time, its based on size.  Its always possible some clown electronically pumps in 5,000 tx in one minute right when a new block hits.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 11:40:46 am
32767 is the biggest transaction vout size that can fit in a block, and after the block gets above 1 Meg in bytes, fees start to get around 100bbp per transaction after 2 meg its more like 1000bbp per tx.  Warnings start appearing on the UI for every tx sent warning you would you like to add this fee to your Tx, or decline and wait?   Its not really based on time, its based on size.  Its always possible some clown electronically pumps in 5,000 tx in one minute right when a new block hits.

I see, thanks. So do any of the crypto currencies out there have a way of protecting against that?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 11:43:19 am
I see, thanks. So do any of the crypto currencies out there have a way of protecting against that?
That is the protection, the fee increases higher and higher according to the block size.  To my knowledge all the berkeleydb coins do the same thing, but I dont know how Ethereum works in this respect.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 11:45:59 am
That is the protection, the fee increases higher and higher according to the block size.  To my knowledge all the berkeleydb coins do the same thing, but I dont know how Ethereum works in this respect.

Oh, I meant the clown situation. But I guess that clown would have to be rich or just want to waste coins if he wants to do that to every block and make everyone's fees really high.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 14, 2018, 12:08:47 pm
HI all, I have compiled 1091 on linux.
I have some questions.
1. When I started biblepay-qt after compilation, in one second was added 15 transactions from mined blocks. It is correct?  I attach my transaction log.
2. Some mined block have 5900 tBBP but the majority of blocks have cca 590 tBBP. it is ok ?
3. How the tBBP from PODC are sent? If I understand, from each DC superblock by actual magnitude.   

Thanks for answer.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 14, 2018, 12:20:57 pm
Question out of PODC.
I tried to see the transifex page for biblepay but does'n exist. In slovak language have ? character for some special characters. I see corrupted (? character in words) biblepay_sk.ts file. I mean same problem are in another files(chinese for example)

It is possible run biblepay-qt in english (with some commandline parameter) ovveride system locale ?

Thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 01:24:39 pm
Oh, I meant the clown situation. But I guess that clown would have to be rich or just want to waste coins if he wants to do that to every block and make everyone's fees really high.

Yes but the clown would lose money too, as the fee is modest but still adds up after the first 20 or so tx in the block.  Its something like .000100 BBP at that level, so 500 tx would still cost a few hundred BBP to spam the chain, once it gets past that it gets exponentially higher, youd have to look at the algorithm that charges higher tx fees for each memory pool tx.

The only legitimate reason I can think of doing that for is store some real data in the chain.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 01:38:27 pm
Question out of PODC.
I tried to see the transifex page for biblepay but does'n exist. In slovak language have ? character for some special characters. I see corrupted (? character in words) biblepay_sk.ts file. I mean same problem are in another files(chinese for example)

It is possible run biblepay-qt in english (with some commandline parameter) ovveride system locale ?

Thanks

Try going to Settings | Options | Display and changing default language to another language first.

The .01 bbp to you is just a remnant of POL, that is going away soon.
The 581 reward is a heat-mining reward.
The 5800 reward is a sanctuary reward.
Anything over 6000 bbp is a PODC reward.
Tx list looks good.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 14, 2018, 01:46:35 pm
Try going to Settings | Options | Display and changing default language to another language first.

The .01 bbp to you is just a remnant of POL, that is going away soon.
The 581 reward is a heat-mining reward.
The 5800 reward is a sanctuary reward.
Anything over 6000 bbp is a PODC reward.
Tx list looks good.

Thank you very much, for answer.

Switch to english is ok
But why I have sanctuary rewards when I have not sanctuary created ? It is only on testnet (each node is sanctuary)?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 01:52:38 pm
Try going to Settings | Options | Display and changing default language to another language first.

The .01 bbp to you is just a remnant of POL, that is going away soon.
The 581 reward is a heat-mining reward.
The 5800 reward is a sanctuary reward.
Anything over 6000 bbp is a PODC reward.
Tx list looks good.

Is there a way to check the RAC of the Biblepay network so I can see if my magnitude is correct? Also, on the wiki, it says mangitude = RAC * 1000, that doesn't seem to be the case anymore right?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on February 14, 2018, 02:41:45 pm
I'm on the move!

This is what I see:

{
  "Command": "getboincinfo",
  "CPID": "xxxxx",
  "Address": "yWKX5CXuPCJNLLSwUjqwQcUifnYToco1zM",
  "CPIDS": "xxxxx;",
  "CPID-Age (hours)": 421844,
  "NextSuperblockHeight": 9900,
  "xxxxx_RAC": 13.23,
  "Total_RAC": 13.23,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 1365210,
  "Total Budget (One Week)": 49542570,
  "Superblock Count (One Week)": 68,
  "Superblock Hit Count (One Week)": 37,
  "Superblock List": "9702,9108,8613,8217,8118,8019,7821,7425,7326,7128,7029,6831,6732,6633,6534,6435,6336,6138,5940,5841,5742,5643,5247,5148,5049,4950,4851,4752,4653,4554,4455,4356,4257,4158,3762,3465,3168",
  "Last Superblock Budget": 1386000,
  "Last Superblock Height": 9801,
  "Last Superblock Payment": -1,
  "Magnitude": 0
}

I guess that I can "copy" the wallet.dat file to other computer and continue testing, can't I?


Thank you for all your efforts Rob.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:46:45 pm
Thank you very much, for answer.

Switch to english is ok
But why I have sanctuary rewards when I have not sanctuary created ? It is only on testnet (each node is sanctuary)?
Looking at your spreadsheet, I only see the 591s and the .01s.  Are you looking at your own sheet, Where do you see sanctuary rewards on your node?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:47:51 pm
I'm on the move!

This is what I see:

{
  "Command": "getboincinfo",
  "CPID": "xxxxx",
  "Address": "yWKX5CXuPCJNLLSwUjqwQcUifnYToco1zM",
  "CPIDS": "xxxxx;",
  "CPID-Age (hours)": 421844,
  "NextSuperblockHeight": 9900,
  "xxxxx_RAC": 13.23,
  "Total_RAC": 13.23,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 1365210,
  "Total Budget (One Week)": 49542570,
  "Superblock Count (One Week)": 68,
  "Superblock Hit Count (One Week)": 37,
  "Superblock List": "9702,9108,8613,8217,8118,8019,7821,7425,7326,7128,7029,6831,6732,6633,6534,6435,6336,6138,5940,5841,5742,5643,5247,5148,5049,4950,4851,4752,4653,4554,4455,4356,4257,4158,3762,3465,3168",
  "Last Superblock Budget": 1386000,
  "Last Superblock Height": 9801,
  "Last Superblock Payment": -1,
  "Magnitude": 0
}

I guess that I can "copy" the wallet.dat file to other computer and continue testing, can't I?

Thank you for all your efforts Rob.


Yes, you can just copy the wallet.dat to another machine and continue testing.

Or you can re-associate the CPID on the new machine and it moves after 6 confirms.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:48:56 pm
Is there a way to check the RAC of the Biblepay network so I can see if my magnitude is correct? Also, on the wiki, it says mangitude = RAC * 1000, that doesn't seem to be the case anymore right?

You can verify your RAC against the Rosetta UI, or against the many Boinc credit providers or against the row in Boinc Manager.

No, we never said Magnitude is RAC * 1000.

We said Magnitude = RAC/TotalProjectRAC * 1000.

I can put the TotalProjectRAC in getboincinfo.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on February 14, 2018, 02:51:50 pm

Another question: do we have to "setgenerate true" in the controller wallet, or classical BoPh churning it's not needed any more? What happens if we do/don't do it?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 02:55:18 pm
Another question: do we have to "setgenerate true" in the controller wallet, or classical BoPh churning it's not needed any more? What happens if we do/don't do it?
I should make the controller wallet mine on one thread by default, to increase network security, but anyway, yes its recommended that the controller wallet is setgenerate=true, genproclimit=1.

If you do it you have a chance of heat mining a block If you have a CPID and since we enforce distinct CPIDs now, a very good chance of mining a block regardless of hashpower.

If you dont do it you forgo rewards and we rely more on other cpids for block security.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 03:18:54 pm
You can verify your RAC against the Rosetta UI, or against the many Boinc credit providers or against the row in Boinc Manager.

No, we never said Magnitude is RAC * 1000.

We said Magnitude = RAC/TotalProjectRAC * 1000.

I can put the TotalProjectRAC in getboincinfo.

TotalProjectRAC would be great. In the wiki it says "(Magnitude is computed by assessing the Individual Researchers Share of RAC * 1000)" I missed the words "share of" in that sentence. Did you consider using "Pie%" by doing x100 instead of x1000? I personally would like percentage better, it makes more sense to me.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 03:27:22 pm
TotalProjectRAC would be great. In the wiki it says "(Magnitude is computed by assessing the Individual Researchers Share of RAC * 1000)" I missed the words "share of" in that sentence. Did you consider using "Pie%" by doing x100 instead of x1000? I personally would like percentage better, it makes more sense to me.

Im sticking with 1000 cap-limit for the magnitude for now, as I want it to be a granular float from 0-1000 meaning your position in team Biblepay.  Its certainly equivalent to a percent of the superblock, but Magnitude is meant to be the total "weight" you have in our leaderboard and I have the gut feeling people who compete like large numbers.

This will come into play when we have 5000-10000 researchers (we will), and the granularity will be very small between some.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 03:34:18 pm
Ill modify the wiki.  I mentioned Magnitude somewhere in this thread a little better with a different equation.

Im sticking with 1000 cap-limit for the magnitude for now, as I want it to be a granular float from 0-1000 meaning your position in team Biblepay.  Its certainly equivalent to a percent of the superblock, but Magnitude is meant to be the total "weight" you have in our leaderboard and I have the gut feeling people who compete like large numbers.

This will come into play when we have 5000-10000 researchers (we will), and the granularity will be very small between some.

EDIT: Heres where the confusion came from - you said the wiki said "it says mangitude = RAC * 1000", but the wiki says "the Individual Researchers Share of RAC * 1000".  The individual researchers share of RAC * 1000 is the magnitude.  The wiki is correct, your quote was missing the word "share".

Yes, I did think you might have wanted the number to be bigger. Yeah, I mentioned I missed the word "share".
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 03:36:14 pm
Yes, I did think you might have wanted the number to be bigger. Yeah, I mentioned I missed the word "share".
Sorry, I just noticed that when I re-read it and deleted my post   :P

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 03:39:11 pm
Yes, I did think you might have wanted the number to be bigger. Yeah, I mentioned I missed the word "share".


I did think of a simple "pie" thing, and its good, dont get me wrong but there was one other consideration other than large numbers.
There is a chance that when biblepay grows, we might make biblepay consider more than one projects RAC, for example 30% from Alzheimers research and 70% from cancer. 

Magnitude is a term I am coining for "consolidated project effectiveness as a researcher" so its slightly different than a pure percent when you consider the possibility of blending two projects together.

I deliberately kept the system simple in that it only works with Rosetta, but PODC is generic in the back end enough to potentially go with more than one blended project in the future.

If that ever happens your magnitude is the single number as a researcher across all biblepay projects.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 14, 2018, 03:54:17 pm
Looking at your spreadsheet, I only see the 591s and the .01s.  Are you looking at your own sheet, Where do you see sanctuary rewards on your node?

I see for example this:
false   14.02.18 18:45   Vy?ažené      yRThhHMA5rQqz5GTp37Ttn2dXajxpjKec8   5910.00000000   ebd77507e4e6aa1d6a2db1bb7d4eb226530255e2a55c05ddc2daf8207241a447-000
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 03:54:51 pm

I did think of a simple "pie" thing, and its good, dont get me wrong but there was one other consideration other than large numbers.
There is a chance that when biblepay grows, we might make biblepay consider more than one projects RAC, for example 30% from Alzheimers research and 70% from cancer. 

Magnitude is a term I am coining for "consolidated project effectiveness as a researcher" so its slightly different than a pure percent when you consider the possibility of blending two projects together.

I deliberately kept the system simple in that it only works with Rosetta, but PODC is generic in the back end enough to potentially go with more than one blended project in the future.

If that ever happens your magnitude is the single number as a researcher across all biblepay projects.

I see, sounds good Rob. If all goes well I'll clone up 9 more nodes tomorrow.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 14, 2018, 04:15:39 pm
Forgot to answer this post yesterday sorry,
Please see inline:

I was busy today, but thanks a lot for your answer Rob. And thanks for "getboincinfo" explanation too.
Those answers definitely fulfill my curiosity :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 04:32:31 pm
I see for example this:
false   14.02.18 18:45   Vy?ažené      yRThhHMA5rQqz5GTp37Ttn2dXajxpjKec8   5910.00000000   ebd77507e4e6aa1d6a2db1bb7d4eb226530255e2a55c05ddc2daf8207241a447-000
Oh yes, I didnt see that one!

That is certainly a rare one.  I looked up the issue on that one and it wont happen in prod.  What happened was masternode winners didnt have enough support for block 9694, so when that block came along you mined the entire budget ( masternode + heat reward) for yourself and the network accepted it.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 04:35:31 pm
I see, sounds good Rob. If all goes well I'll clone up 9 more nodes tomorrow.
Awesome, lets see if your new getboincinfo looks good now, ie rac numbers came down to be accurate?  I just thought of something, we need a tool to see an in - wallet leaderboard report, like exec leaderboard, so we can see "cpid, magnitde" ranked from top to bottom, that will reveal any strange anomolies also...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 14, 2018, 06:47:53 pm
Awesome, lets see if your new getboincinfo looks good now, ie rac numbers came down to be accurate?  I just thought of something, we need a tool to see an in - wallet leaderboard report, like exec leaderboard, so we can see "cpid, magnitde" ranked from top to bottom, that will reveal any strange anomolies also...

Rob, the information looks great now.

"Command": "getboincinfo",
  "CPID": "f80ab050ab53459ec937879a046d603e",
  "Address": "yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;71f1f1f46deb2f25961c7d9af06f2b31;95a79cd5829e8315b0b946709930df18;cc37d0ef74a621379974484f43d3b1c5;f80ab050ab53459ec937879a046d603e;",
  "CPID-Age (hours)": 421848,
  "NextSuperblockHeight": 9999,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 438.68,
  "71f1f1f46deb2f25961c7d9af06f2b31_RAC": 180.95,
  "95a79cd5829e8315b0b946709930df18_RAC": 151.15,
  "cc37d0ef74a621379974484f43d3b1c5_RAC": 185.96,
  "f80ab050ab53459ec937879a046d603e_RAC": 151.9,
  "Total_RAC": 1108.64,
  "Total Payments (One Day)": 71927,
  "Total Payments (One Week)": 1482797,
  "Total Budget (One Day)": 1365210,
  "Total Budget (One Week)": 48156570,
  "Superblock Count (One Week)": 66,
  "Superblock Hit Count (One Week)": 36,
  "Superblock List": "9702,9108,8613,8217,8118,8019,7821,7425,7326,7128,7029,6831,6732,6633,6534,6435,6336,6138,5940,5841,5742,5643,5247,5148,5049,4950,4851,4752,4653,4554,4455,4356,4257,4158,3762,3465",
  "Last Superblock Budget": 1386000,
  "Last Superblock Height": 9900,
  "Last Superblock Payment": -1,
  "Magnitude": 30.79116722806462
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 14, 2018, 07:43:44 pm
One concern brought up in Slack was "double dipping" with Gridcoin and Biblepay.  After looking around, it appears that is thankfully not easily done, and may be impossible.

One other thought that did come up on Slack was the reduction in hash power needed to do a 51% attack on PoW.  I'm not saying it is correct, since Gridcoin manages to secure their block chain with just the BOINC hashing.  My question then is would it be possible or practical to take the PoL work and instead of using Coin Age as a hash rate modifier (or difficulty modifier), would it be practical to use the RAC somehow to perform that function?  My thought is it would build upon the PoL work that has been done, might not diminish the number of blocks created by PoW and thus might preserve the high barrier for a 51% attack. 

The other concern brought up was if there might be a project similar in mission to BOINC but strictly for Christian researchers?  I was unaware of any.  However, it made me ponder the possibilities that some point down the road, if BBP becomes a major force where we sponsor thousands of orphans and do the miraculous, feeding widows and orphans from the virtual proceedings...think about the loaves and the fishes and you see where my mind picks up this as analogous, then perhaps this coin can merit some standing to create a portal for scientists who are Christians and doing Godly research.

Just some thoughts on the matter as things move forward.  It's tremendously exciting!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 14, 2018, 10:03:39 pm
Please see inline:

One concern brought up in Slack was "double dipping" with Gridcoin and Biblepay.  After looking around, it appears that is thankfully not easily done, and may be impossible.

->  We're on different blockchains, so I don't understand what double dipping would be.  If both chains paid for the same research it would influence the global arb rate for that project.  Gridcoin requires the researcher to be on their Boinc team (called team gridcoin, or you dont get paid) while we dont require a team - I did that intentionally so we can market biblepay to all existing Rosetta researchers. (Since we have unlimited scalability now)..


One other thought that did come up on Slack was the reduction in hash power needed to do a 51% attack on PoW.  I'm not saying it is correct, since Gridcoin manages to secure their block chain with just the BOINC hashing.  My question then is would it be possible or practical to take the PoL work and instead of using Coin Age as a hash rate modifier (or difficulty modifier), would it be practical to use the RAC somehow to perform that function?  My thought is it would build upon the PoL work that has been done, might not diminish the number of blocks created by PoW and thus might preserve the high barrier for a 51% attack. 

-> Gridcoin is on POS, were on POW so there is no relationship, they have more of a propensity of a 51% attack by the buying vector, we have more of one from the brute force side (although I say for us- lower than most other coins after the cpid rule is in).  When we move to signed cpids, we have a reduction in hashpower but also a reduction in random unknown hashpower.  That does not increase the chances of a 51% attack it decreases it.   RAC has no relationship to hashpower, so adding RAC would not decrease the liklihood of a 51% attack (a person with high rac does not have high hashpower - we dont know what they have) - although adding a distinct CPID With RAC (which we did, makes it impossible to launch a horizontal cpid attack- thats one where you try to create many cpids- that rule is in testnet now, we require the CPID to be paid in the prior superblock with RAC & magnitude in order to mine).  We still have DGW in place to prevent 51% attacks, so that makes it extremely hard to perform.


The other concern brought up was if there might be a project similar in mission to BOINC but strictly for Christian researchers?  I was unaware of any.  However, it made me ponder the possibilities that some point down the road, if BBP becomes a major force where we sponsor thousands of orphans and do the miraculous, feeding widows and orphans from the virtual proceedings...think about the loaves and the fishes and you see where my mind picks up this as analogous, then perhaps this coin can merit some standing to create a portal for scientists who are Christians and doing Godly research.

->  One could create a boinc project more aligned with Jesus, but I dont know what that would be.  The biggest problem I see with that in contrast to Rosetta: Rosetta has 150 paid scientists on payroll so they are developing an extraordinarily complex program, where a homegrown "new"boinc project probably wouldnt do much, but its certainly worth exploring if someone comes up with a groundbreaking idea.


Just some thoughts on the matter as things move forward.  It's tremendously exciting!


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 15, 2018, 03:40:40 am
I think the Windows wallet is still mining as 'strong' as ever. On a 4-core  4-thread system, when I use 'setgenerate true 1', the wallet uses about 25% of the cpu-power (as it's always been). On my Linux testrig, it's way less since the latest updates.

I read somewhere in the thread that 'setgenerate true 1' should create a lot less hashpower than before (1% of what it would be previously?). So on Linux it seems to be working, but on Windows I'm not sure.

Both are 1.0.9.1. wallets btw.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 15, 2018, 08:03:24 am
I think the Windows wallet is still mining as 'strong' as ever. On a 4-core  4-thread system, when I use 'setgenerate true 1', the wallet uses about 25% of the cpu-power (as it's always been). On my Linux testrig, it's way less since the latest updates.

I read somewhere in the thread that 'setgenerate true 1' should create a lot less hashpower than before (1% of what it would be previously?). So on Linux it seems to be working, but on Windows I'm not sure.

Both are 1.0.9.1. wallets btw.

Its possible that I built windows on 1091a and it missed the feature.  Ill look into that and let you know when I build the next windows and we can re-test. Thanks for pointing that out.

Nice to know linux is only using 1%.  Thats a very green and nice thing to know, as that means our efficiency just increased massively.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 15, 2018, 09:35:12 am
All 10 nodes on 1.0.9.1 now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on February 16, 2018, 01:21:31 am
From my side it seems it's working as expected, I get some payments although I can't evaluate whether they are correct or not-

I got 8 payments of 841 tBBP yesterday and 3 of 16259 tBBP each today.

{
  "Command": "getboincinfo",
  "CPID": "xxxxx",
  "Address": "yWKX5CXuPCJNLLSwUjqwQcUifnYToco1zM",
  "CPIDS": "xxxxx;",
  "CPID-Age (hours)": 421879,
  "NextSuperblockHeight": 11286,
  "xxxxx_RAC": 451.65,
  "Total_RAC": 451.65,
  "Total Payments (One Day)": 54699,
  "Total Payments (One Week)": 55545,
  "Total Budget (One Day)": 13652100,
  "Total Budget (One Week)": 52085880,
  "Superblock Count (One Week)": 66,
  "Superblock Hit Count (One Week)": 39,
  "Superblock List": "11187,11088,10989,10890,10791,10692,10593,10494,10395,10296,10098,9702,9108,8613,8217,8118,8019,7821,7425,7326,7128,7029,6831,6732,6633,6534,6435,6336,6138,5940,5841,5742,5643,5247,5148,5049,4950,4851,4752",
  "Last Superblock Budget": 1386000,
  "Last Superblock Height": 11187,
  "Last Superblock Payment": 16259,
  "Magnitude": 1.066411856725854
}

I hope this info is useful
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 16, 2018, 01:54:05 am
I erased Ubuntu Server with Lubuntu and replaced with Ubuntu, (I am not a fan of Lubuntu now LOL)
I downloaded Ubuntu ISO and put it on a flash drive with program called Rufus (on Windows), and booted from the flash drive to install Ubuntu

After Installing BOINC, The BOINC Manager didnt have a menu, had to use SHIFT + ALT + A to switch to Advanced View,
then I read that you have to full screen the program to see the Menu, which worked, weird

I read in Rosetta forums that average Rosetta Work Unit (Task?) needs 0.5 GB RAM, not sure if its true, I was worried that was my issue of why I was seeing less tasks running, but I think I just had general issues with Lubuntu LOL, I bought another stick of RAM just in case since the machine in question only has 4GB RAM.

The Options >> Computing Preferences is actually really nice, much more functionality than just setting number of mining threads like in POW

Also my significant other has enjoyed seeing the proteins folding in the screensaver and is now okay with BOINC being installed on her PC (whereas earlier with POW she was against BiblePay being mined on her PC LOL)

I haven't been mining BiblePay for over a month or two, but this Rosetta@home stuff is really cool and has me back in, Im even tempted to get another PC for it!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 16, 2018, 08:06:36 am
I erased Ubuntu Server with Lubuntu and replaced with Ubuntu, (I am not a fan of Lubuntu now LOL)
I downloaded Ubuntu ISO and put it on a flash drive with program called Rufus (on Windows), and booted from the flash drive to install Ubuntu

After Installing BOINC, The BOINC Manager didnt have a menu, had to use SHIFT + ALT + A to switch to Advanced View,
then I read that you have to full screen the program to see the Menu, which worked, weird

I read in Rosetta forums that average Rosetta Work Unit (Task?) needs 0.5 GB RAM, not sure if its true, I was worried that was my issue of why I was seeing less tasks running, but I think I just had general issues with Lubuntu LOL, I bought another stick of RAM just in case since the machine in question only has 4GB RAM.

The Options >> Computing Preferences is actually really nice, much more functionality than just setting number of mining threads like in POW

Also my significant other has enjoyed seeing the proteins folding in the screensaver and is now okay with BOINC being installed on her PC (whereas earlier with POW she was against BiblePay being mined on her PC LOL)

I haven't been mining BiblePay for over a month or two, but this Rosetta@home stuff is really cool and has me back in, Im even tempted to get another PC for it!

Thats a cool story!  Yes I like how the competition "feels good" compared to mining.

Im going to do a side by side test at home- I ordered a Ryzen 8 core barebones system, Im going to measure RAC per Watt on the power hungry machine.

I found these highly efficient relatively inexpensive machines on ebay:

https://www.ebay.com/itm/ZOTAC-C-Series-ZBOX-CI327-NANO-Palm-Sized-Passive-Cooled-Mini-PC-Intel-N3450-Q/292139099729?epid=18003069933&hash=item4404d8e651:g:lCgAAOSw63FZ8JKk

These Zotacs pull between 30-40 watts, they use a laptop power supply.  They are about 1.8 ghz and quad core.  Im going to order one and measure Rosetta RAC per watt on this thing as Reference machine 2.  (It would be neat to have a solar powered zotac).  I remember finding a mini laptop a few years back that only consumed about 6 watts - that would be the ideal solar powered laptop... Its RAC per watt is probably 10* the zotac and 100* the ryzen.  The dell mini laptop and acer mini I think pulled about 10 watts or less.  Would be great for a solar project.  Run the wires in the house and you can set it up on your kitchen table and tell your guests its completely power free and generating income... lol...



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 16, 2018, 08:34:49 am
From my side it seems it's working as expected, I get some payments although I can't evaluate whether they are correct or not-

I got 8 payments of 841 tBBP yesterday and 3 of 16259 tBBP each today.

{
  "Command": "getboincinfo",
  "CPID": "xxxxx",
  "Address": "yWKX5CXuPCJNLLSwUjqwQcUifnYToco1zM",
  "CPIDS": "xxxxx;",
  "CPID-Age (hours)": 421879,
  "NextSuperblockHeight": 11286,
  "xxxxx_RAC": 451.65,
  "Total_RAC": 451.65,
  "Last Superblock Height": 11187,
  "Last Superblock Payment": 16259,
  "Magnitude": 1.066411856725854
}

I hope this info is useful


I just wanted to mention FYI:  You don't need to hide your CPID as it is public (its equivalent to your BBP public receiving address), as this CPID will get pulled around the world and pushed into all the boinc aggregator credit sites (such as team stats, boincstats, etc), and if you want to stay anonymous, you will need to create a Rosetta account using anonymous Username, city, etc, then when people click on your CPID they will only tie you to an anonymous user.

Anyway looks like your mag is showing as 1.06 for 451 rac with a payment of 16259 out of a budget of 10921680, yes that looks correct.  Magnitude is equivalent to your share of the pie * 1000.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 16, 2018, 08:40:04 am
Update on the PODC project:

I have not found any new bugs.  The CPID signature rule seems to be working correctly.
The chain is syncing from zero correctly.  The quorum votes are behaving correctly.
The headless version is filtering the files correctly.
Any concerns or feature requests?

Last night I added an in-wallet leaderboard (exec leaderboard).  It shows CPID, Magnitude by magnitude descending.
Im holding off to check it in until we team it up with another change.

So far, this looks very promising for Prod on March 15th....

EDIT: I also added two reports to the pool:  Once per day, we gather the data.  Rosetta Machine Leaderboard and Rosetta Project Leaderboard.
Its gleaning the data from the Biblepay team, so if you arent in the team the leaderboard misses you. 

(We still allow Rosetta crunchers outside of the team, to receive compensation and this is for future PR.  Im envisioning that we make a post in the
 Rosetta forums eventually and invite those users over.  Or pay for a banner ad out of our PR budget on the boincstats site.  (There are some veteran Rosetta crunchers with billions of credits who belong to a certain team - so they may not want to drop their team - but if they are not required to, they may join us and become part of our community - and be part of our community in other ways).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 16, 2018, 08:54:21 am

08:52:59

exec leaderboard


08:52:59

{
  "Leaderboard Report": 1518792787,
  "Height": 11484,
  "Total Block": 1365199,
  "93138f032bdd027fa3246b48bb715a77": 167.4210121204234,
  "4004b7fec94751f61fe9135977bac553": 150.9508859078355,
  "c9085154b7cc0ca2b5189672559dd6d8": 98.73066052106205,
  "8735cfe64d964416dba6015eb414cf7e": 94.17015325846157,
  "7c9264559fef3c1c689ee9fc3ff42494": 66.62984614968333,
  "8f273b30f8e0a298ed26e242762df701": 51.81002878107859,
  "e7ae6abd6284b05f3fd5f7c780e60bc7": 45.15019389004685,
  "d9b22fccfae5582d4ee7838883aaa3cf": 42.22021813508347,
  "6cf45c3b54ef7c08d15838446a98ef24": 41.56024109627797,
  "1e7184e17377549d5a7d7a2edfb51017": 39.35982930430048,
  "dde30f3ef57ed2df69ecbc687db75e46": 34.20966442101361,
  "6785ded1f65063ef8f01f42deb31cf1d": 27.37989093619398,
  "ca895b47aacffbdbf906201821af2f9f": 24.15984758148924,
  "4fd1bf6c6900d92b226e16c6a6935661": 20.03004675486836,
  "04fba56d89a5eb38b1b82f8a6240132c": 19.77001140661536,
  "e94c1704c75f731f8bfde303f08408ee": 17.16965792408537,
  "96892ec0fc8a2710fa84f26c9c84cd3e": 11.90961894998737,
  "71f1f1f46deb2f25961c7d9af06f2b31": 9.689429821663875,
  "e7c056024cd3b781edd5af37965c652c": 8.910056270843619,
  "95a79cd5829e8315b0b946709930df18": 8.759895013401746,
  "f80ab050ab53459ec937879a046d603e": 6.219606033848502,
  "84d803e4d82d3bdcdf8e2ab601e93e20": 5.769854755461624,
  "cc37d0ef74a621379974484f43d3b1c5": 5.079845465167748,
  "fe553a955f0e21d46724858870014cbe": 2.939498176167004
}


This report shows the descending magnitude from the last superblock, and the CPIDs.  You can see our magnitudes always add up to 1000.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 16, 2018, 11:03:14 am
why missing nicks in leaderboard?  ::)  thanks

me, orbis etc
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 16, 2018, 12:27:20 pm
why missing nicks in leaderboard?  ::)  thanks

me, orbis etc

Do you mean you can't find your CPID?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 16, 2018, 12:51:49 pm
Do you mean you can't find your CPID?
No. We aren't on Rosetta Machine Leaderboard and Rosetta Project Leaderboard on BBP pool and I don't see myself in Rob's leaderboard post neither.
But I'm in Biblepay team in Rosetta and I get payment for every superblock. It's weird.
Any idea?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 16, 2018, 01:47:59 pm
No. We aren't on Rosetta Machine Leaderboard and Rosetta Project Leaderboard on BBP pool and I don't see myself in Rob's leaderboard post neither.
But I'm in Biblepay team in Rosetta and I get payment for every superblock. It's weird.
Any idea?

That's weird indeed... I'm sorry, but I don't know how to help you, but I hope Rob can :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 16, 2018, 02:48:34 pm
I run a popular videogame server on a dedicated machine I rent, and it only uses 20-25% of the CPU,
I wanted to run Rosetta alongside it without interfering with the game's CPU, I looked into CPU Affinity for BOINC and there are no options for it,
But on Windows I was able to go into Task Manager >>> Details >> Right Click  boinc.exe and boincmgr.exe >>> Set Affinity
And I was able to set which CPU Cores these should use, after that I added the Rosetta Project, and the Rosetta Tasks created only used those cores  :)
If the computer restarts the affinity settings will get reset, but I only restart the machine every 2-3 months or so LOL
Its probably possible to write a .bat file to set the affinity, but eh, works good enough for me so far

Rob is there anything else you need tested? Ive just been dabbling with BOINC and getting it setup everywhere I can.
Sounds like testing has so far gone very well 8)

===

Also yeah once PODC is released will be nice to advertise/market BiblePay to users of BOINC, Rosetta, Gridcoin, Curecoin, Foldingcoin, Mediccoin, etc

We can look at how Gridcoin is advertising:
https://cryptocurrencytalk.com/topic/48655-boincstats-advertising/
https://steemit.com/gridcoin/@vortac/gridcoin-advertsing-2-expanding-our-google-adwords-budget
https://www.reddit.com/r/gridcoin/comments/4oy9w5/new_advertising_campaign_on_boincstatscom/

Looks like Banner ad on BoincStats is 300 Euros? so $370? How long does it stay up?

Id love to start playing with Google Adwords
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 16, 2018, 04:04:36 pm
why missing nicks in leaderboard?  ::)  thanks

me, orbis etc
You are in there - but the problem with Orbis is his computers are hidden.  Orbis you have to unhide computers to be in the leaderboard.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 16, 2018, 04:26:00 pm
You are in there - but the problem with Orbis is his computers are hidden.  Orbis you have to unhide computers to be in the leaderboard.
ok. I must check the settings and find it... But maybe it doesnt matter anymore, because all my VPS are ending today :)
So I will be without any "external help"...
My only 24/7 device will be my old Nexus 4 ;) and maybe this will be interresting for you Rob.
It is old phone, comparable to nowaday mid range.

I test it for 2 days now. There were some problems on beginning and I've found that I need to use only 2 of 4 cores to run it properly.
After two days: Total credit   1015 ; Average credit   89.93
https://boinc.bakerlab.org/rosetta/results.php?hostid=3352819
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 16, 2018, 04:38:45 pm
I run a popular videogame server on a dedicated machine I rent, and it only uses 20-25% of the CPU,
I wanted to run Rosetta alongside it without interfering with the game's CPU, I looked into CPU Affinity for BOINC and there are no options for it,
But on Windows I was able to go into Task Manager >>> Details >> Right Click  boinc.exe and boincmgr.exe >>> Set Affinity
And I was able to set which CPU Cores these should use, after that I added the Rosetta Project, and the Rosetta Tasks created only used those cores  :)
If the computer restarts the affinity settings will get reset, but I only restart the machine every 2-3 months or so LOL
Its probably possible to write a .bat file to set the affinity, but eh, works good enough for me so far

Rob is there anything else you need tested? Ive just been dabbling with BOINC and getting it setup everywhere I can.
Sounds like testing has so far gone very well 8)

===

Also yeah once PODC is released will be nice to advertise/market BiblePay to users of BOINC, Rosetta, Gridcoin, Curecoin, Foldingcoin, Mediccoin, etc

We can look at how Gridcoin is advertising:
https://cryptocurrencytalk.com/topic/48655-boincstats-advertising/
https://steemit.com/gridcoin/@vortac/gridcoin-advertsing-2-expanding-our-google-adwords-budget
https://www.reddit.com/r/gridcoin/comments/4oy9w5/new_advertising_campaign_on_boincstatscom/

Looks like Banner ad on BoincStats is 300 Euros? so $370? How long does it stay up?

Id love to start playing with Google Adwords

I think most of the ad-sites will negotiate a deal, and sometimes offer a discount for quarterly over monthly.  Im not sure of the term for $370 but its probably a monthly quote.  Yeah, we should definitely look into PR budget for that.

On testing, Ive got the larger Private Send denominations in the next version, the exec leaderboard, and I havent changed max sigs yet for Instantsend, waiting on feedback to see if we need to.

Let me think about more testing ideas, right now I think we have covered the bases.

Regarding one potential feature for the integrity idea, I was thinking, if there is a way to concentrate and anonymize all cancer tasks, for example if we gave the job to the sanctuaries to issue cancer tasks, and those sancs monitored return traffic for anonymous validation, maybe we could "certify" the rosetta traffic that way.  Another words, only issue paid traffic if it flows through a sanctuary.  If we were able to monitor the traffic from a sanc, we could tally the workunits issued and validated, and the duration, and prove that those workunits were indeed solved - but I think for this idea to work, the workunits need anonymized, and more than one sig would be required on the validated work... Very tricky stuff... (It proves that workunit XYZ was submitted at timestamp 12345 and validated by Rosetta without rosetta knowing the CPID, and then validated back in Biblepay for workunit XYZ for duration ZZZ).






Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 16, 2018, 04:41:02 pm
ok. I must check the settings and find it... But maybe it doesnt matter anymore, because all my VPS are ending today :)
So I will be without any "external help"...
My only 24/7 device will be my old Nexus 4 ;) and maybe this will be interresting for you Rob.
It is old phone, comparable to nowaday mid range.

I test it for 2 days now. There were some problems on beginning and I've found that I need to use only 2 of 4 cores to run it properly.
After two days: Total credit   1015 ; Average credit   89.93
https://boinc.bakerlab.org/rosetta/results.php?hostid=3352819

Good to know dude.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 16, 2018, 05:19:46 pm
ok. I must check the settings and find it... But maybe it doesnt matter anymore, because all my VPS are ending today :)
So I will be without any "external help"...
My only 24/7 device will be my old Nexus 4 ;) and maybe this will be interresting for you Rob.
It is old phone, comparable to nowaday mid range.

I test it for 2 days now. There were some problems on beginning and I've found that I need to use only 2 of 4 cores to run it properly.
After two days: Total credit   1015 ; Average credit   89.93
https://boinc.bakerlab.org/rosetta/results.php?hostid=3352819

Did you have to do anything to get your phone to run 24/7? I have mine plugged in but it will only work for a few hours then it will suspend it self. I have to manually start it again afterwards.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 16, 2018, 06:39:37 pm
I think most of the ad-sites will negotiate a deal, and sometimes offer a discount for quarterly over monthly.  Im not sure of the term for $370 but its probably a monthly quote.  Yeah, we should definitely look into PR budget for that.

On testing, Ive got the larger Private Send denominations in the next version, the exec leaderboard, and I havent changed max sigs yet for Instantsend, waiting on feedback to see if we need to.

Let me think about more testing ideas, right now I think we have covered the bases.

Regarding one potential feature for the integrity idea, I was thinking, if there is a way to concentrate and anonymize all cancer tasks, for example if we gave the job to the sanctuaries to issue cancer tasks, and those sancs monitored return traffic for anonymous validation, maybe we could "certify" the rosetta traffic that way.  Another words, only issue paid traffic if it flows through a sanctuary.  If we were able to monitor the traffic from a sanc, we could tally the workunits issued and validated, and the duration, and prove that those workunits were indeed solved - but I think for this idea to work, the workunits need anonymized, and more than one sig would be required on the validated work... Very tricky stuff... (It proves that workunit XYZ was submitted at timestamp 12345 and validated by Rosetta without rosetta knowing the CPID, and then validated back in Biblepay for workunit XYZ for duration ZZZ).




Regarding one potential feature for the integrity idea, I was thinking, if there is a way to concentrate and anonymize all cancer tasks, for example if we gave the job to the sanctuaries to issue cancer tasks, and those sancs monitored return traffic for anonymous validation, maybe we could "certify" the rosetta traffic that way.  Another words, only issue paid traffic if it flows through a sanctuary.  If we were able to monitor the traffic from a sanc, we could tally the workunits issued and validated, and the duration, and prove that those workunits were indeed solved - but I think for this idea to work, the workunits need anonymized, and more than one sig would be required on the validated work... Very tricky stuff... (It proves that workunit XYZ was submitted at timestamp 12345 and validated by Rosetta without rosetta knowing the CPID, and then validated back in Biblepay for workunit XYZ for duration ZZZ).


Hi Rob,

Just a quick question regarding this. How much Gb of traffic do you think this would use? Would it still be OK to use a VPS like Vultr if this was implemented, or would the traffic be more than the cap they give you per month?

Thanks :)

PoDC is awesome, I can't wait for March!

Thanks
Luke

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 17, 2018, 12:54:32 am
Update on the PODC project:

I have not found any new bugs.  The CPID signature rule seems to be working correctly.
The chain is syncing from zero correctly.  The quorum votes are behaving correctly.
The headless version is filtering the files correctly.
Any concerns or feature requests?

Last night I added an in-wallet leaderboard (exec leaderboard).  It shows CPID, Magnitude by magnitude descending.
Im holding off to check it in until we team it up with another change.

So far, this looks very promising for Prod on March 15th....

EDIT: I also added two reports to the pool:  Once per day, we gather the data.  Rosetta Machine Leaderboard and Rosetta Project Leaderboard.
Its gleaning the data from the Biblepay team, so if you arent in the team the leaderboard misses you. 

(We still allow Rosetta crunchers outside of the team, to receive compensation and this is for future PR.  Im envisioning that we make a post in the
 Rosetta forums eventually and invite those users over.  Or pay for a banner ad out of our PR budget on the boincstats site.  (There are some veteran Rosetta crunchers with billions of credits who belong to a certain team - so they may not want to drop their team - but if they are not required to, they may join us and become part of our community - and be part of our community in other ways).

One request that I would like to see considered.  Require team Biblepay to receive rewards.

Currently, we are open to exploit by a botnet.  Its believed we are losing a large and measurable percentage to botnet(s) and it's not inconceivable it could exceed 50% with little difficulty, since this is what Monero, the hybrid CPU/GPU coin is suspected to be at.

Right now, Team Biblepay is 76th, with RAC of 30K, the top team is Team Gridcoin with 4.8M RAC.  I understand the desire to reach out and open the door for more users, but I worry that the current proposal of allowing anyone to receive rewards regardless of team, allows for Gridcoin users to effectively get credit at Gridcoin as well as at Biblepay for no more work (since they can be Team Gridcoin for Gridcoin rewards, and use just their user Account Key to get BBP).  Since Gridcoin users are on some level participating in R@h for Cryptocurrency rewards, it seems reasonable to think many, if not most, will gravitate to BBP since they can buy 1 BBP to receive rewards.  If, and I say IF, they are there solely for the reward and we cannot minister to them, then they are no better to our core users than the botnet.  If we reached the 1% ranking, we'd have roughly 100K RAC, if 25% of the Gridcoin users started with BBP, they'd have 1M RAC, and so if we could not convert them as genuine users, we'd be back to a 10% - 90% split with the majority of the coins going to people outside our user base.  Additionally, by not requiring team Biblepay membership, we lose a valuable asset which is the PR benefit from the overall ranking on R@h which could very easily be top 10 to maybe top 5 in a very short period of time.  Because without requiring to be a part of team Biblepay, most of our users I believe will end up on team Gridcoin as that would make the most financial sense.

I believe the goal to move to PoDC is a good one.  This particular piece of the puzzle however, I am concerned about and think needs addressed before the implementation.

In the end, the question to me boils down to, are there many R@h users we can reach out to that would not join us if they had to leave their current teams.  If so, can we reach more users with our own higher ranking team?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 07:18:48 am
One request that I would like to see considered.  Require team Biblepay to receive rewards.

Currently, we are open to exploit by a botnet.  Its believed we are losing a large and measurable percentage to botnet(s) and it's not inconceivable it could exceed 50% with little difficulty, since this is what Monero, the hybrid CPU/GPU coin is suspected to be at.

Right now, Team Biblepay is 76th, with RAC of 30K, the top team is Team Gridcoin with 4.8M RAC.  I understand the desire to reach out and open the door for more users, but I worry that the current proposal of allowing anyone to receive rewards regardless of team, allows for Gridcoin users to effectively get credit at Gridcoin as well as at Biblepay for no more work (since they can be Team Gridcoin for Gridcoin rewards, and use just their user Account Key to get BBP).  Since Gridcoin users are on some level participating in R@h for Cryptocurrency rewards, it seems reasonable to think many, if not most, will gravitate to BBP since they can buy 1 BBP to receive rewards.  If, and I say IF, they are there solely for the reward and we cannot minister to them, then they are no better to our core users than the botnet.  If we reached the 1% ranking, we'd have roughly 100K RAC, if 25% of the Gridcoin users started with BBP, they'd have 1M RAC, and so if we could not convert them as genuine users, we'd be back to a 10% - 90% split with the majority of the coins going to people outside our user base.  Additionally, by not requiring team Biblepay membership, we lose a valuable asset which is the PR benefit from the overall ranking on R@h which could very easily be top 10 to maybe top 5 in a very short period of time.  Because without requiring to be a part of team Biblepay, most of our users I believe will end up on team Gridcoin as that would make the most financial sense.

I believe the goal to move to PoDC is a good one.  This particular piece of the puzzle however, I am concerned about and think needs addressed before the implementation.

In the end, the question to me boils down to, are there many R@h users we can reach out to that would not join us if they had to leave their current teams.  If so, can we reach more users with our own higher ranking team?


Yes, you have valid concerns.  I have always actually been on the side of the fence where the least the researcher can do is join the team in order to receive rewards.  I have held Rob Halfords perspective on double dipping, back when Ripple offered a chance to receive Ripple rewards for boinc users, if they crunch a certain project- at that time one of the same projects Gridcoin users crunched.  The rule in Gridcoin was those users must be within the team in order to receive rewards, and that prevented double rewards from both Ripple and Gridcoin.

However I saw a lot of scalability arguments against the team requirement and I guess I originally thought, hey lets solve that problem with Biblepay!  Lets make a feature where we have unlimited scalability and open the door to the massive Boinc Userbase (of over 1 million accounts).  So, under the hood Biblepay is now prepared for that.  We can literally handle the entire Boinc userbase if necessary (it requires us to increment a flag to send out multiple superblock payments per day, but we dont have to monkey with that feature until we have more than 32767 researchers on board).

But honing in on this issue Ive actually always been on the side of the fence where a miner should provide some value for us, and with that, they receive rewards, and have more of a propensity to buy and hold BBP for the long term - and be a loyal user (in contrast to a miner who comes and uses us, and pumps n dumps the coin).

So, in light of that view, I think we need to support requiring the team in order to mine biblepay.  We still support unlimited users, but the user must jump in and modify the team from the Rosetta account and join our team to receive rewards.

This way, when we go live, we will not only eliminate the botnet, but we will only have loyal users pulling slices of the BBP pie per day.  This will allow us to grow slowly in an organic Christian way, we can reach out to small swaths at a time and promote Christian values and see if we scare them away.

Great idea, Im going to add two features to the core client:
1) A system wide spork, to hold the Team Required Value (our team=15044 btw, Biblepay).
2) If the spork is active, PODC payments require Team Biblepay
3) The SanctuaryQuorum will be modified to log the users team in the contract
4) The exec getboincinfo will be modified to display the team, and display a corresponding warning if the team is required, enabled, and the user is not part of the team:  Warning - This CPID is not part of team Biblepay - This CPID is not receiving rewards for research work

Etc

We will need everyone to upgrade to test this.


Client will be ready in 2 hours.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 17, 2018, 08:35:25 am
I'm happy to read about the latest implementation which ads the 'biblepay team' requirement. I already read Wests post, but I didn't find the space in myself to react till now.

I like the saying: "If you build it, they will come." And if we have a well thought out 'product' (I don't know better word at this time), I think people who's ideals align with those of Biblepay and happen to stumble upon us, will probably stick around.

Another thing I just wanted to say: I'm still positive about this project. What makes me uncomfortable from time to time though, is the - in my opinion - well meaning people leaving this project in discontent. There are a lot of variables at play here, so I want to stay as neutral as possible (people are people, and they act like people, as they have done for millennia). But I would personally would feel more comfortable in this community if there would be a bit more room for everyone's views, even if they don't align with the route this project is taking. But that's just my view ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 10:05:18 am
I'm happy to read about the latest implementation which ads the 'biblepay team' requirement. I already read Wests post, but I didn't find the space in myself to react till now.

I like the saying: "If you build it, they will come." And if we have a well thought out 'product' (I don't know better word at this time), I think people who's ideals align with those of Biblepay and happen to stumble upon us, will probably stick around.

Another thing I just wanted to say: I'm still positive about this project. What makes me uncomfortable from time to time though, is the - in my opinion - well meaning people leaving this project in discontent. There are a lot of variables at play here, so I want to stay as neutral as possible (people are people, and they act like people, as they have done for millennia). But I would personally would feel more comfortable in this community if there would be a bit more room for everyone's views, even if they don't align with the route this project is taking. But that's just my view ;)

I'm glad you like the team requirement.

I'm not sure if you are referring to me, for not being patient enough to deal with some naysayers about this project or if you are referring to the people who left the project because they couldnt stand my response.

I'll tell you specifically what Im not going to tolerate in either of the forums (I could care less what people post outside of the BTCTalk/Forum.biblepay.org).   Any single individual who makes inaccurate and strong statements - such as "this is this way" and "this will do this" but is actually of an individual opinion (of one who may not even own a single sanctuary), where part or all of the content is questionable or not true.  And in that case No, they do NOT have the best interests in mind for this project.  Burito has a hidden agenda, and others who have left made the mistake of not being careful enough to raise concerns the correct polite way and admit they have no clue what they are talking about.  I have patience for those people, but I dont have patience for people who are ultimately destroying us and the old ladies investments because they singlehandedly feel they are the cross section of BBP.  Anyone can enter a proposal for 2500 BBP and create a soap box for change and let the sancs vote where the money is.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 10:09:15 am
Biblepay
1.0.9.2-Mandatory Upgrade for TestNet


- Add Spork for Team Biblepay Requirement for PODC
- Enforce Team requirement in PODC Contract
- Add PODC Difficulty Measurement for getmininginfo, and add exec podcdifficulty RPC command
- Extend instantsend signing timeout to allow higher transmission amounts
- Increase PrivateSend Mixing Denominations by 1000
- Add team value and warning to exec getboincinfo
- Added exec leaderboard

** Windows is Compiling **

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 17, 2018, 11:08:38 am
Biblepay
1.0.9.2-Mandatory Upgrade for TestNet


- Add Spork for Team Biblepay Requirement for PODC
- Enforce Team requirement in PODC Contract
- Add PODC Difficulty Measurement for getmininginfo, and add exec podcdifficulty RPC command
- Extend instantsend signing timeout to allow higher transmission amounts
- Increase PrivateSend Mixing Denominations by 1000
- Add team value and warning to exec getboincinfo

** Windows is Compiling **

Rob, updating one node now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 17, 2018, 01:05:34 pm
Did you have to do anything to get your phone to run 24/7? I have mine plugged in but it will only work for a few hours then it will suspend it self. I have to manually start it again afterwards.
Hi, like I said, I had many problems with it. Even when the phone was on charger it still had problem and wanted to plug in the power source. At the end my settings are approx like this: battery as power source, 0% min. battery, 2 CPU cores (2 of 4), 100% CPU limit, stop with CPU usage ove 80%. Now it is working almost perfectly with some small issues yesterday.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 17, 2018, 01:52:21 pm
I'm glad you like the team requirement.

I'm not sure if you are referring to me, for not being patient enough to deal with some naysayers about this project or if you are referring to the people who left the project because they couldnt stand my response.

I'll tell you specifically what Im not going to tolerate in either of the forums (I could care less what people post outside of the BTCTalk/Forum.biblepay.org).   Any single individual who makes inaccurate and strong statements - such as "this is this way" and "this will do this" but is actually of an individual opinion (of one who may not even own a single sanctuary), where part or all of the content is questionable or not true.  And in that case No, they do NOT have the best interests in mind for this project.  Burito has a hidden agenda, and others who have left made the mistake of not being careful enough to raise concerns the correct polite way and admit they have no clue what they are talking about.  I have patience for those people, but I dont have patience for people who are ultimately destroying us and the old ladies investments because they singlehandedly feel they are the cross section of BBP.  Anyone can enter a proposal for 2500 BBP and create a soap box for change and let the sancs vote where the money is.

Thank you for you reply Rob! I don't want to pollute this thread, so I'll try and keep it short. I often try to understand why people react in certain ways. I try to understand why people like Slovakia and nerfherder react in a certain way, so I try and talk to them (if they want). And yes, sometimes I'm also trying to figure out why you react in a certain way. In the case of Burito, I took his post and held your 'FUD rules' alongside it, and I couldn't figure out what was wrong with his post. But now you posted this reply for clarification, I understand: he made a strong statement which was in fact just an opinion (or something he couldn't say for a fact). Now I understand this, I also understand why you deleted his post.

That being said: I'm gonna update my testnet nodes now  :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 17, 2018, 01:54:11 pm
Hmmm I thought we wanted to avoid having a team requirement?
so that anyone can mine Rosetta without having to leave their research team?

Im pretty much okay with Gridcoin users getting BiblePay and Gridcoin,
but given the incentives in place for that, It would be in my best interest as a researcher to end up joining Team Gridcoin so I could get the rewards for both Gridcoin and BiblePay

What other possible solutions are there?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 17, 2018, 02:28:09 pm
Hi Rob, please, I can't compile biblepay for testnet on linux. I have this error:

rpcblockchain.cpp: In function ‘bool FilterFile(int, std::__cxx11::string&)’:
rpcblockchain.cpp:4473:52: error: cannot convert ‘std::basic_istream<char>’ to ‘bool’ in initialization
        bool bAddlData = std::getline(streamIn, line);
                                                    ^
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 17, 2018, 02:48:18 pm
ischindl Imro pridaj si ma na rosette: a poslal som ti na email zhrnutie nasej MNky: kamarat orbis(svk) spravil pre nas pekny sheet

Imro: pouzivas ubuntu/debian?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 03:11:15 pm
Hmmm I thought we wanted to avoid having a team requirement?
so that anyone can mine Rosetta without having to leave their research team?

Im pretty much okay with Gridcoin users getting BiblePay and Gridcoin,
but given the incentives in place for that, It would be in my best interest as a researcher to end up joining Team Gridcoin so I could get the rewards for both Gridcoin and BiblePay

What other possible solutions are there?

I think the only way to handle this is to put a poll in for it...  Im relatively neutral, and now leaning towards requiring the team so that we dont give away all our rewards to every stranger so quickly.  But I can see part of the other side, where we want to appeal to the masses. 

Could you create a forum topic and put a proposal vote in for it?  Maybe for 2500 BBP so that you get reimbursed for the proposal?

Then I guess whatever way it ends it ends.

The code in testnet is set up so the team can be disabled if we set the team spork to 0.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 17, 2018, 03:12:56 pm
Hi, like I said, I had many problems with it. Even when the phone was on charger it still had problem and wanted to plug in the power source. At the end my settings are approx like this: battery as power source, 0% min. battery, 2 CPU cores (2 of 4), 100% CPU limit, stop with CPU usage ove 80%. Now it is working almost perfectly with some small issues yesterday.

I see, I will play around with it some more. Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 03:20:38 pm
Hi Rob, please, I can't compile biblepay for testnet on linux. I have this error:

rpcblockchain.cpp: In function ‘bool FilterFile(int, std::__cxx11::string&)’:
rpcblockchain.cpp:4473:52: error: cannot convert ‘std::basic_istream<char>’ to ‘bool’ in initialization
        bool bAddlData = std::getline(streamIn, line);
                                                    ^

Could you please grab 1092b and try now?

I believe this syntax is required for cross platform compatibility.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 17, 2018, 03:39:07 pm
I updated my node but it doesn't appear to be syncing. I ran

rm blocks -R
rm chainstate -R
rm banlist.dat fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat peers.dat db.log debug.log

before starting the daemon.

"version": 1000902,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.2",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 692,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 0.002553704361813557,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true

Debug.log:
2018-02-17 21:41:59 26 addresses found from DNS seeds
2018-02-17 21:41:59 dnsseed thread exit
2018-02-17 21:41:59 Misbehaving: 195.201.30.231:60418 (0 -> 10)
2018-02-17 21:44:57 Misbehaving: 94.130.53.103:38154 (0 -> 10)
2018-02-17 21:47:46 Misbehaving: 38.21.22.209:42302 (0 -> 10)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 17, 2018, 04:23:42 pm
Could you please grab 1092b and try now?

I believe this syntax is required for cross platform compatibility.

Thanks Rob, now is ok.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 04:28:21 pm
I updated my node but it doesn't appear to be syncing. I ran

rm blocks -R
rm chainstate -R
rm banlist.dat fee_estimates.dat governance.dat mncache.dat mnpayments.dat netfulfilled.dat peers.dat db.log debug.log

before starting the daemon.

"version": 1000902,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.2",
  "balance": 0.00000000,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 692,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 0.002553704361813557,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true

Debug.log:
2018-02-17 21:41:59 26 addresses found from DNS seeds
2018-02-17 21:41:59 dnsseed thread exit
2018-02-17 21:41:59 Misbehaving: 195.201.30.231:60418 (0 -> 10)
2018-02-17 21:44:57 Misbehaving: 94.130.53.103:38154 (0 -> 10)
2018-02-17 21:47:46 Misbehaving: 38.21.22.209:42302 (0 -> 10)


Yeah, this version has really shaken things up...

Can you all please upgrade to 1092c now.... and try syncing again please.



Windows is rebuilding now...





Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 04:46:38 pm
Ok it looks like the latest version syncs now - we are at 12098.  I need to step out for a few hours, will send Windows out tonight after its tested.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 17, 2018, 05:15:22 pm
Biblepay
1.0.9.2-Mandatory Upgrade for TestNet


- Add Spork for Team Biblepay Requirement for PODC
- Enforce Team requirement in PODC Contract
- Add PODC Difficulty Measurement for getmininginfo, and add exec podcdifficulty RPC command
- Extend instantsend signing timeout to allow higher transmission amounts
- Increase PrivateSend Mixing Denominations by 1000
- Add team value and warning to exec getboincinfo
- Added exec leaderboard

** Windows is Compiling **

Yeah, this version has really shaken things up...

Can you all please upgrade to 1092c now.... and try syncing again please.

Windows is rebuilding now...

Got one sanctuary updated and running and the other is still updating :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 17, 2018, 05:52:21 pm

Yeah, this version has really shaken things up...

Can you all please upgrade to 1092c now.... and try syncing again please.



Windows is rebuilding now...

Rob, appears to be working good now. Great job!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 06:11:20 pm
Got one sanctuary updated and running and the other is still updating :)

Great!  Were you going to enter a proposal to vote on the team requirement, or are we going with it?

It might be a good idea, so that is part of the accepted transition of power to PODC.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 17, 2018, 06:14:09 pm
Im pretty neutral, Id have to think about it more and also check Gridcoin and their pros/cons of the team requirement

I have 2 testnet sanctuaries up!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 17, 2018, 06:31:44 pm
Im pretty neutral, Id have to think about it more and also check Gridcoin and their pros/cons of the team requirement

I have 2 testnet sanctuaries up!

Honestly, I didn't really want everyone flooding in to take a share of the pie, but that's just being greedy. So if helping with cancer research is our top goal, then it doesn't really matter if people are double dipping or triple dipping. Now if we want to advertise ourselves, we could always use the combined RAC and have a counter on the website. I think there is more to think about here so we should let it churn a little more.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 06:54:05 pm
Im pretty neutral, Id have to think about it more and also check Gridcoin and their pros/cons of the team requirement

I have 2 testnet sanctuaries up!


Ok cool.

So on the superblock creator in prod, I originally convinced myself that dash-central hidden PHP created the superblocks, LOL, so that particular weekend, I wrote the superblock hex creator, hence the reason we arent using the watchman superblock creator that ranks the proposals by vote descending .

So I took a look at that function and I think it looks pretty valuable, so Im going to work on enabling it in testnet over the next few days.  It appears we have two changes necessary to make it work:  1) The biblepay address validator needs one character updated in Watchman, and the superblock proposal ranker requires proposal start and end dates to be really exact, unbelievinably exact, so we need to change the code to allow a fudge of like a week for the target superblock (since we have slow blocks in prod), so Ill make these two changes, then we will need to update our Testnet watchmen, restart them, and create a testnet proposal in the pool.

Ill update more on this as I get closer to being ready to test it.

The advantage here is I believe the triggers will create themselves, and vote on themselves (IE we may not have to vote on the budget anymore).  I think I created that process inadvertently (thinking we had to), but we shall see.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 17, 2018, 08:06:34 pm
Anyone waiting for Windows version in testnet:

1092 is now available.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 17, 2018, 08:23:37 pm

Ok cool.

So on the superblock creator in prod, I originally convinced myself that dash-central hidden PHP created the superblocks, LOL, so that particular weekend, I wrote the superblock hex creator, hence the reason we arent using the watchman superblock creator that ranks the proposals by vote descending .

So I took a look at that function and I think it looks pretty valuable, so Im going to work on enabling it in testnet over the next few days.  It appears we have two changes necessary to make it work:  1) The biblepay address validator needs one character updated in Watchman, and the superblock proposal ranker requires proposal start and end dates to be really exact, unbelievinably exact, so we need to change the code to allow a fudge of like a week for the target superblock (since we have slow blocks in prod), so Ill make these two changes, then we will need to update our Testnet watchmen, restart them, and create a testnet proposal in the pool.

Ill update more on this as I get closer to being ready to test it.

The advantage here is I believe the triggers will create themselves, and vote on themselves (IE we may not have to vote on the budget anymore).  I think I created that process inadvertently (thinking we had to), but we shall see.

Awesome!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 18, 2018, 03:45:15 am
One request that I would like to see considered.  Require team Biblepay to receive rewards.

Currently, we are open to exploit by a botnet.  Its believed we are losing a large and measurable percentage to botnet(s) and it's not inconceivable it could exceed 50% with little difficulty, since this is what Monero, the hybrid CPU/GPU coin is suspected to be at.

Right now, Team Biblepay is 76th, with RAC of 30K, the top team is Team Gridcoin with 4.8M RAC.  I understand the desire to reach out and open the door for more users, but I worry that the current proposal of allowing anyone to receive rewards regardless of team, allows for Gridcoin users to effectively get credit at Gridcoin as well as at Biblepay for no more work (since they can be Team Gridcoin for Gridcoin rewards, and use just their user Account Key to get BBP).  Since Gridcoin users are on some level participating in R@h for Cryptocurrency rewards, it seems reasonable to think many, if not most, will gravitate to BBP since they can buy 1 BBP to receive rewards.  If, and I say IF, they are there solely for the reward and we cannot minister to them, then they are no better to our core users than the botnet.  If we reached the 1% ranking, we'd have roughly 100K RAC, if 25% of the Gridcoin users started with BBP, they'd have 1M RAC, and so if we could not convert them as genuine users, we'd be back to a 10% - 90% split with the majority of the coins going to people outside our user base.  Additionally, by not requiring team Biblepay membership, we lose a valuable asset which is the PR benefit from the overall ranking on R@h which could very easily be top 10 to maybe top 5 in a very short period of time.  Because without requiring to be a part of team Biblepay, most of our users I believe will end up on team Gridcoin as that would make the most financial sense.

I believe the goal to move to PoDC is a good one.  This particular piece of the puzzle however, I am concerned about and think needs addressed before the implementation.

In the end, the question to me boils down to, are there many R@h users we can reach out to that would not join us if they had to leave their current teams.  If so, can we reach more users with our own higher ranking team?

Yes, you have valid concerns.  I have always actually been on the side of the fence where the least the researcher can do is join the team in order to receive rewards.  I have held Rob Halfords perspective on double dipping, back when Ripple offered a chance to receive Ripple rewards for boinc users, if they crunch a certain project- at that time one of the same projects Gridcoin users crunched.  The rule in Gridcoin was those users must be within the team in order to receive rewards, and that prevented double rewards from both Ripple and Gridcoin.

However I saw a lot of scalability arguments against the team requirement and I guess I originally thought, hey lets solve that problem with Biblepay!  Lets make a feature where we have unlimited scalability and open the door to the massive Boinc Userbase (of over 1 million accounts).  So, under the hood Biblepay is now prepared for that.  We can literally handle the entire Boinc userbase if necessary (it requires us to increment a flag to send out multiple superblock payments per day, but we dont have to monkey with that feature until we have more than 32767 researchers on board).

But honing in on this issue Ive actually always been on the side of the fence where a miner should provide some value for us, and with that, they receive rewards, and have more of a propensity to buy and hold BBP for the long term - and be a loyal user (in contrast to a miner who comes and uses us, and pumps n dumps the coin).

So, in light of that view, I think we need to support requiring the team in order to mine biblepay.  We still support unlimited users, but the user must jump in and modify the team from the Rosetta account and join our team to receive rewards.

This way, when we go live, we will not only eliminate the botnet, but we will only have loyal users pulling slices of the BBP pie per day.  This will allow us to grow slowly in an organic Christian way, we can reach out to small swaths at a time and promote Christian values and see if we scare them away.

Great idea, Im going to add two features to the core client:
1) A system wide spork, to hold the Team Required Value (our team=15044 btw, Biblepay).
2) If the spork is active, PODC payments require Team Biblepay
3) The SanctuaryQuorum will be modified to log the users team in the contract
4) The exec getboincinfo will be modified to display the team, and display a corresponding warning if the team is required, enabled, and the user is not part of the team:  Warning - This CPID is not part of team Biblepay - This CPID is not receiving rewards for research work

Biblepay
1.0.9.2-Mandatory Upgrade for TestNet


- Add Spork for Team Biblepay Requirement for PODC
- Enforce Team requirement in PODC Contract
- Add PODC Difficulty Measurement for getmininginfo, and add exec podcdifficulty RPC command
- Extend instantsend signing timeout to allow higher transmission amounts
- Increase PrivateSend Mixing Denominations by 1000
- Add team value and warning to exec getboincinfo
- Added exec leaderboard

** Windows is Compiling **

Hmmm I thought we wanted to avoid having a team requirement?
so that anyone can mine Rosetta without having to leave their research team?

Im pretty much okay with Gridcoin users getting BiblePay and Gridcoin,
but given the incentives in place for that, It would be in my best interest as a researcher to end up joining Team Gridcoin so I could get the rewards for both Gridcoin and BiblePay

What other possible solutions are there?

I think the only way to handle this is to put a poll in for it...  Im relatively neutral, and now leaning towards requiring the team so that we dont give away all our rewards to every stranger so quickly.  But I can see part of the other side, where we want to appeal to the masses. 

Could you create a forum topic and put a proposal vote in for it?  Maybe for 2500 BBP so that you get reimbursed for the proposal?

Then I guess whatever way it ends it ends.

The code in testnet is set up so the team can be disabled if we set the team spork to 0.

Were you going to enter a proposal to vote on the team requirement, or are we going with it?

It might be a good idea, so that is part of the accepted transition of power to PODC.

Im pretty neutral, Id have to think about it more and also check Gridcoin and their pros/cons of the team requirement

Honestly, I didn't really want everyone flooding in to take a share of the pie, but that's just being greedy. So if helping with cancer research is our top goal, then it doesn't really matter if people are double dipping or triple dipping. Now if we want to advertise ourselves, we could always use the combined RAC and have a counter on the website. I think there is more to think about here so we should let it churn a little more.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 18, 2018, 03:45:44 am
"As a long term BOINCer, I know may users are very dedicated to their teams, and would never change. If we waived this requirement the number of GRC users will increase significantly." -Fuzzy Duck

"I don't think that if we delete this requirement, BOINC projects will get more crunchers. It would be much more important to bring Bitcoiners and Alt-coiners (=non boincers) to Gridcoin. For such people, the team requirement wouldn't be a problem" - DC7D

"The main reasons I'm in favour of removing the requirement is because of the 'team poaching' issue when discussing Gridcoin on BOINC team forums/Tech forums (very negative reactions to team poaching derails any discussion of gridcoin with potential target audience), and beause I believe it may increase the effectiveness of boincstats advertising

"On one hand sure recruiting existing BOINC users to gridcoin isn't introducing new users to BOINC, but if existing users can offset the cost of electricity they may be able to justify increasing their computing capabilities for BOINC" -C.M

"at first after deleting the requirement, existing users will get less GRC due to the (significant?) increasing number of new members. Therefore, maybe some will stop crunching," -DC7D

"The number of GRC earned via PoR will reduce. However, the value of the GRC will increase due to supply and demand" -Fuzzy Duck

https://cryptocurrencytalk.com/topic/44260-discussion-mandatory-team-gridcoin-membership-requirement/?page=2&tab=comments#comment-206758

https://cryptocurrencytalk.com/topic/44260-discussion-mandatory-team-gridcoin-membership-requirement/?page=2&tab=comments#comment-206789

https://cryptocurrencytalk.com/topic/44260-discussion-mandatory-team-gridcoin-membership-requirement/?page=3&tab=comments#comment-207164

"If we remove the team requirements we won't be able to determine what percentage of all Boinc work Gridcoin participants are donating"

==

"I've thought about it for a while and came up with this possible solution: how about not changing Gridcoin but BOINC? By letting the BOINC user join two teams instead of one people could easily stay in their beloved team and join Team Gridcoin beside it. This way they can continue to crunch for their teams and earn"

==

https://www.reddit.com/r/gridcoin/comments/6mq3tu/new_blockchain_poll_impact_to_price_of_grc_if/dkdisz0/

https://www.reddit.com/r/gridcoin/comments/6mq3tu/new_blockchain_poll_impact_to_price_of_grc_if/dkdo1b8/

==

"What will really happen to the price of GRC if the team requirement is lifted?

The common belief by people who want to see the team requirement lifted is that we would be unlocking the growth potential of Gridcoin mining, and since miners have various incentives to hold GRC (voting weight, frequency of staking, interest) we should see increased demand for GRC and thus increased price


What is the argument for why the price of GRC might be reduced if the team requirement is lifted?

NeuralMiner believes that by adding potentially thousands of pure "mine and dump" type miners who don't care about Gridcoin as a currency, we will actually increase selling pressure of the coin because these miners will be minting some of the coins that "mine and HODLers" like NeuralMiner and myself currently receive on a daily basis.

I thought that was a very intelligent point, and it is well-taken. My counter-argument.... really more of a counter-question was: for every 100 "mine and dump" type miners, how many "mine and HODL" type miners will we potentially add? How many people might we add (like myself) who will invest their own money into the coin?"

==

https://steemit.com/gridcoin/@cm-steem/gridcoin-s-mandatory-team-requirement-should-it-stay-or-should-it-go

"2. To prevent BOINC users from "Double-dipping"
During the early days of Gridcoin's existence (before the introduction of the team requirement), Ripple was distributing Ripple to BOINC users within their Ripple Labs team.

We found that several users crunching for the Ripple Labs team were also claiming Gridcoin rewards. This discovery was negatively perceived as "Double-dipping" (getting rewarded twice for their work done), and was leading motivation for the introduction of the mandatory team 'Gridcoin' requirement to prevent this occurring again in the future.


Statistics websites are obsolete, we have a Neural Network!
We now store all of the important statistics within the client (NN), so when asked how much BOINC computation is being rewarded by Gridcoin we can simply point them towards neural network statistics instead of towards our team statistic pages on Boincstats."

=================================================

References:

https://cryptocurrencytalk.com/topic/44260-discussion-mandatory-team-gridcoin-membership-requirement/

https://docs.google.com/document/d/15sEYTzJIROmReCWGAQTZie0Il7NIURUANozKYhR8gus/pub

https://gridcoinstats.eu/poll/technical_poll_:_what_should_we_do_regarding_the_mandatory_team_requirement

https://github.com/Erkan-Yilmaz/Gridcoin-tasks/issues/94

https://www.reddit.com/r/gridcoin/comments/6mq3tu/new_blockchain_poll_impact_to_price_of_grc_if/

https://www.reddit.com/r/gridcoin/comments/41efuo/discussion_mandatory_team_gridcoin_membership/

https://steemit.com/beyondbitcoin/@xaqfields/the-great-debate-lifting-the-gridcoin-team-requirement

https://steemit.com/gridcoin/@cm-steem/gridcoin-s-mandatory-team-requirement-should-it-stay-or-should-it-go
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 18, 2018, 03:52:48 am
Thanks for compiling that list Togo. It doesn't make the decision easier for me, but it does give me more perspective :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 18, 2018, 04:30:32 am
Overall it seems like the Gridcoin community is split on the issue, and there are good points on both sides of the debate

Im still on the fence
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 18, 2018, 07:05:25 am
Overall it seems like the Gridcoin community is split on the issue, and there are good points on both sides of the debate

Im still on the fence

Basically, to summarize the pros and cons, and remove wives tails:

By enforcing the team, we provably become a boincstats competing force, a driving team with more total RAC on the aggregator sites, and more credibility (from an auditing perspective), and we are not open to the masses receiving a piece of the 1.3MM daily pie, without joining the team.  There seems to be more of a propensity of being a loyal BBP community member if one were to join the team.

By not enforcing the team, we provide more free PR for the coin, because the word will spread all by itself, hey you can receive BBP by Rosetta mining, you dont even have to change your team.  The issue is we will receive thousands of researchers who are loyal to places like US Navy and Overclocking forums,  and we worry that maybe they will mine-n-dump us.  The wives tail here is they are crashing the coin because they are using us and not investing long term, but in reality they are potentially providing selling pressure on our price and that means others can *buy* BBP cheap with this effect.

So it really is a 50-50 hardline deal.    (IE its 0 compensation for non team members as is now).


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 18, 2018, 09:02:48 am
I recommend that we keep enforcing the team for now. 

Swongle is posting in the PODC consensus algo thread some lower risk attack vectors that GRC, Boinc, Asics and bitcoin go/went through, and so far from a high level, these are all already known and accounted for in Biblepay in this PODC algorithm, however I dont think its a good idea to open the floodgates for every single boinc user at this time until we address those in more detail over time.

I do however think the system is solid enough for a March go live, for our community and members of team biblepay.

What I think we should do however, is address the finer issues raised and become the first cryptocurrency to actually Solve the problem.  Lets make PODC computing secure and trustable to the 99% level - above where it currently is (in the 90% trust level).

It sounds to me like the only relevant attack vectors raised have to do with: sql tampering for boincside credit falsification (lying about work performed), 3rd party workunit validation (Rosetta being stood up at gunpoint to validate all workunits), centralization (a centralized authority validating workunits).

RISK 1 - CENTRALIZATION:

I believe we have overcome the centralization risk, based on a 99.9% uptime of boinc/rosetta, since both entities have multiple servers on each level, my assumption here is we can deal with a day of downtime while executing our disaster recovery plan (we enter DR mode when boinc or rosetta is down).  We live with a day of downtime a year (as a crypto), since we have POBH for front line block security.  The overall good work outweighs the bad single day of outage, and the net result is we have a year of cancer research in exchange for a day of downtime centralization risk.  This is why I summarize this particular risk to be mitigated.  In addition, if we do create a concentrated cancer proxy account, centralization risk drops even further.  (This would be to anonymize cancer tasks).

TRUSTING A THIRD PARTY FOR WORKUNIT VALIDATION:

I believe this is an accepted and fundamentally known requirement for a project like Rosetta, because the software is client server, meaning it is so complicated, it is developed by 150 scientists and hundreds of programmers, each module is testing protein folds and compiling the results in a way that can only be checked by the corresponding closed source server validation system.  There is no way to keep up with an opensource version of the software to validate workunits without creating more hacking vectors.  I view this as a low risk and a known tradeoff to use a high level analysis program for mining.


WORK UNIT TAMPERING:

Im sure there are many potential risks here, from coercion and corruption inside Rosetta, coercion at gunpoint, tampering of the SQL database, mass credit validation, however, the key here lies in catching a forward only anonymous system in a tampered state.  Right now we know the state of the researchers total credit as they ask for more work.  I think we can solve this problem by detecting when a CPID-MachineID total credit changes in a way that is tampered, and mark it as Broken and cancel it until the CPID is reset.  Right now we rely on Rosetta telling us the truth about : Work unit Is validated, How long it took, Credit rewarded, and BOINC calculates the RAC based on all that info.  We can only detect tampering from the standpoint of do the numbers roll up.   This is the one area where I think we can make a difference by investigating the potential idea of proxying and anonmyzing cancer tasks through a sanctuary, having the sanctuary reward a static reward (not based on task duration, based on Rosettas validation call).  That would eliminate the "lying" vector on task duration by machine.  I view this risk as the only relatively weak risk in the system and one that we should address over the long term.

EDIT:  So Im auditing the inner workings of the Rosetta task to see what kind of "lying vector" risk we have for RAC awarded per task.  I see the Rosetta cancer server gives each researcher a 400 megabyte database of protiens and a lot of medical tables with strange names for each molecule and the results are sent in base64 encoded format with rows per protein decoy and energy to be analyzed on the server side.  The great news is, I see Rosetta rewards are based on how many protien decoys are generated - but not specifically based on the CPU time required to generate the decoys - meaning that some workunits yield more credit than others, but credit cant be exaggerated due to long processing times.   This means that we have one less thing to worry about in that respect - we only need to monitor the validation event per task, and monitor the credit delta changes.   

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 18, 2018, 03:42:56 pm
./biblepay-cli getinfo

"errors": "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."

Im seeing this on both of my testnet sanctuaries
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 18, 2018, 04:08:04 pm
./biblepay-cli getinfo

"errors": "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."

Im seeing this on both of my testnet sanctuaries

Lets see if there are any errors in the log, and what block # and hash are you on?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 18, 2018, 04:17:07 pm
both on block: #11978

I think we lost our testnet explorer,
I can spin up another vultr and set one up, I assume we need one still?

cd ~/.biblepaycore
cd testnet3/
tail debug.log

2018-02-18 22:04:45 Misbehaving: 38.21.22.209:4643 (0 -> 14)
2018-02-18 22:07:39 Misbehaving: 195.201.30.231:42166 (0 -> 14)
2018-02-18 22:07:48 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:09:50 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:12:45 Misbehaving: 95.91.244.91:57302 (0 -> 14)
2018-02-18 22:13:01 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:13:01 Misbehaving: 47.189.53.97:54037 (0 -> 12)
2018-02-18 22:14:27 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:14:27 Misbehaving: 47.189.53.97:54070 (0 -> 12)
2018-02-18 22:14:48 Misbehaving: 38.21.22.209:4808 (0 -> 14)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 18, 2018, 10:03:23 pm
both on block: #11978

I think we lost our testnet explorer,
I can spin up another vultr and set one up, I assume we need one still?

cd ~/.biblepaycore
cd testnet3/
tail debug.log


I get the same error.

2018-02-19 03:34:15 Misbehaving: 94.130.53.103:35416 (0 -> 14)
2018-02-19 03:37:20 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-19 03:38:04 Misbehaving: 195.201.30.231:34442 (0 -> 14)
2018-02-19 03:40:09 Misbehaving: 38.21.22.209:12281 (0 -> 14)
2018-02-19 03:44:50 Misbehaving: 91.219.3.153:53440 (0 -> 14)
2018-02-19 03:48:22 Misbehaving: 195.201.30.231:38404 (0 -> 14)
2018-02-19 03:48:56 Misbehaving: 94.130.53.103:35844 (0 -> 14)
2018-02-19 03:50:13 Misbehaving: 38.21.22.209:12452 (0 -> 14)
2018-02-19 03:54:26 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-19 03:55:37 Misbehaving: 91.219.3.153:53568 (0 -> 14)
2018-02-18 22:04:45 Misbehaving: 38.21.22.209:4643 (0 -> 14)
2018-02-18 22:07:39 Misbehaving: 195.201.30.231:42166 (0 -> 14)
2018-02-18 22:07:48 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:09:50 Misbehaving: 94.130.53.103:40001 (0 -> 14)
2018-02-18 22:12:45 Misbehaving: 95.91.244.91:57302 (0 -> 14)
2018-02-18 22:13:01 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:13:01 Misbehaving: 47.189.53.97:54037 (0 -> 12)
2018-02-18 22:14:27 Disconnecting unauthorized peer with Network Time off by 548.000000 seconds!
2018-02-18 22:14:27 Misbehaving: 47.189.53.97:54070 (0 -> 12)
2018-02-18 22:14:48 Misbehaving: 38.21.22.209:4808 (0 -> 14)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 19, 2018, 05:25:25 am
I get the same error.


I also got the same error yesterday, and only on my masternode, not on my normal miner. But I messed something up with my masternode, now I re-installed it and everything seems fine again :)

Also, the windows wallet now also seems to mine with 1% of it's original HPS if you use one tread, so that's nice.

And the things you said about PODC are still crunching in my head Rob. Might take a little while to take it all in.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 07:42:52 am
Hi Guys! Good Morning!

So unfortunately yesterday we had a Chinese New Year celebration that I had to attend so most of the evening was hogged.  Sorry.

Anyway, I did start looking at the issues last night that all 3 of you reported.  And I believe I see the problem, but its very boring and quite complicated to explain.  I'm thinking its best for us to roll the blockchain back to around block 2000 just for safety (Ill explain why) - this is in Testnet only of course.

So I remember we made an adjustment somewhere between block 2000 & 8000 with a core difficulty parameter which changed the max superblock (getsuperblockbudget N) by an amount that ends up "looking" like a masternode payment, and through all this syncing, we never marked the prior blocks as dirty (you dont encounter that until you reindex), and I had a rule in the code for testnet to "ällow" those (thats called grandfathering in by height).  So now that I see it was a parameter change, that makes me feel a little uneasy (about keeping the current chain) as I want a pristine test result so we have no surprises later - we need to isolate any issues with PODC alone so we can hit all the notes before March 15th.  Anyway the next thing we definitely ran into is between block 8000 and 10000 we had people lagging to upgrade, creating blocks on the wrong client version, and I see a couple old bad superblock amounts (apparently based on the old params). 

So in this new version Im going to enforce the testnet block version and the testnet App version.

Im testing now in testnet alone, once I feel this baby is syncing Ill release it.

I believe the only nuisance we have to go through is setting up some of our hot sancs again.  In my case I just send 500K hot to myself and it recovers... Not sure if you all tried that...

I should be done with this within an hour....

So in summary, please stop testing 1092 and wait and upgrade 1093 system wide.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 10:04:57 am
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 19, 2018, 10:15:09 am
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.

Nice work! Upgrading now...

I'll just have to see where I was as block 2000 and get my sanctuary up and running again.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 19, 2018, 10:16:43 am
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.

Also remember that the blocks and chainstate folders and *.dat files are in testnet3 folder since we are in testnet

How to Update and Clean Wallets
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 19, 2018, 11:17:54 am
I updated my 2 testnet machines, theyre both on block 922, is that correct?
block numbers keep going up, so I guess some are mining
my balances are empty,

Should I start mining?
Also do we need a testnet explorer?

Ill set up both my sanctuaries later today
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 11:27:49 am
I updated my 2 testnet machines, theyre both on block 922, is that correct?
block numbers keep going up, so I guess some are mining
my balances are empty,

Should I start mining?
Also do we need a testnet explorer?

Ill set up both my sanctuaries later today

Yes sure you can start mining, here is the blockhash:


getblockhash 950

c2e419d2e90547325f9c133f9b19986626a0cfbcf172f505564cc41436584884


So I have 1000 magnitude right now as I am the Sole cpid.  Ive solved 4 superblocks so far and verified the amounts emitted match the expected creation amounts - so far so good.

The reason why the blocks are clicking by so fast is I have the CPID check shut off until block 10000.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 19, 2018, 11:41:17 am
Ok I am on the correct chain, awesome,
setting both machines to mine with 1 thread

then Ill re-do the CPID burn,
and then set up the sancturaires
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 11:54:18 am
So Ive been thinking of ideas for raising the integrity of PODC, and here is one I came up with that at least feels promising but its in its infancy still.
Just to be clear I dont propose we stop PODC testing and implement this; I would rather finish testing this version as a unit and ensure it works with no bad superblock amounts - and as we enter the CPID phase no bad syncing before we add anything else to PODC.

Also keep in mind, that I know there might be better ideas that come to mind, but this idea comes from what *can* be done technologically that is reasonable, that allows miners on PCs tablets and Phones to execute the idea, in contrast to ideas that might fathomably be possible but would either be too hard to implement or would potentially not work on that Carribean cell phone.

So here it is:
I was thinking of preventing SQL tampering and increasing PODC integrity.  Possibly this way:
We make the controller wallet monitor your devices, those would be considered:  CPIDHASH-MACHINEHASH devices, in laymans terms that means your CPID as a Researcher Plus your first PC for example is that machine hash of your first device, it would iterate through the list of your devices and gather your Rosetta tasks that you are to be crunching.  It would be specifically interested in the starttime of the taskid, and would create a list of tasks that are unanounced to the network.  We would then take one UTXO (thats an unspent coin), and broadcast the cpidhash-machinehash-taskhash-taskid-utxo to the network, and allow biblepay to track the starttime of the tasks.  Then instead of rewarding you with RAC in the superblock we reward you with coin*age*rac, for each individual completed task that was provably started at a specific timestamp.

In this way, we can say that my machine asserts via signed CPID for this message that I own this task and I started it at Y unix timestamp.  Other nodes would verify this timestamp to see if you really started the task at that time.  (Boinc has that info live). 

Then in addition when the task is completed, you receive coin*age * RAC , meaning that there will now be a relationship between your machine, its task, its owner cpid, and the coins spent, and the corresponding public key of the owners wallet.

This would give a level of integrity that would be hard to crack because if SQL tampering is to occur, lets say at gunpoint most likely the perpetrator would be updating many records at once, affecting hundreds of tasks timestamps.  These boinc tasks fortunately are create before they are given out to researchers so if they do a mass update it would hose those records *after* our network said they were started (which would show tampering).  Or, if they update many as validated at once, our report would detect timestamp altering (because now we are tracking info in real time).

Then we could add a report to the core wallet to show this info daily and have it so we can export the RPC report to Excel. Maybe we make our wallet export excel reports to the drive from the controller wallet.

Another way to look at this is, at the very least it brings PODC up and past the trust level of POS, because some communities already trust POS coin consensus, this way PODC would have not only cancer research in real time, but proof-of-utxo-spending as well, tying spent coins to RAC.

The small devices would still work, but this would require a controller wallet running to know when the small device starts hashing.

Thinking about this a little deeper,  that might be a big boon for biblepay.  This would mean to get paid you need to keep your controller wallet running so it can send messages that your devices are starting tasks.  Thats a plus for our security , as that means our networking full node count is higher and the POW-heat side would not be virtually zero.  So this is actually a reasonable and positive requirement....

Lets think about this.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 19, 2018, 12:13:09 pm
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.

Windows is still compiling.

Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.

Also remember that the blocks and chainstate folders and *.dat files are in testnet3 folder since we are in testnet

How to Update and Clean Wallets
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

To re-associate your BOINC CPID:
http://wiki.biblepay.org/Distributed_Computing_2#PART_C._Link_BOINC_Account_to_BiblePay
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 01:00:36 pm
1.0.9.3 - Mandatory Upgrade for Testnet

- Added PODC bounds checks to prevent invalid superblocks


Note:  Everyone will have to reassociate their CPIDs in Biblepay, and re-create hot sancs.



Team enforcement is enabled in testnet.

Please delete blocks, chainstate, and mn*.dat files before resyncing.


Windows has been deployed!    1.0.9.3:

https://www.biblepay.org
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 01:39:15 pm
Rob, how did you send the tBBP to yourself, Before I updated, it gave me that peers warning message when I tried to look up my addresses.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 01:52:13 pm
Rob, how did you send the tBBP to yourself, Before I updated, it gave me that peers warning message when I tried to look up my addresses.

I had to mine a few hundred blocks in order to have enough to start a hot sanc.  Do u need some tBbp?

The peers warning should be gone now; it comes up when all your peers have different block heights.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 01:55:25 pm
I had to mine a few hundred blocks in order to have enough to start a hot sanc.  Do u need some tBbp?

The peers warning should be gone now; it comes up when all your peers have different block heights.

Yeah, if you have any, thanks. I'm still aiming for 10 nodes.

yZoJUy6JzbPahVW4zq2UWJCgKTMv6SUCjh
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 02:26:18 pm
Pre-enabled but stuck here:

"AssetID": 3,
  "AssetName": "MASTERNODE_SYNC_MNW",
  "Attempt": 12,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": true,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true
Code: [Select]

Debug.log:
2018-02-19 20:24:10 Misbehaving: 144.202.17.17:46840 (0 -> 14)
2018-02-19 20:24:14 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=0e4$
2018-02-19 20:24:14 AddToWallet 3ea3e5192c0d5a61091d6537daa5b53e239a58d1d3d1213ba6e46e3cb06ecd83  new
2018-02-19 20:24:14 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:18 Misbehaving: 206.125.154.17:27637 (0 -> 14)
2018-02-19 20:24:36 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=52f$
2018-02-19 20:24:36 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:39 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=911$
2018-02-19 20:24:39 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:43 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=7f0$
2018-02-19 20:24:43 ProcessNewBlock : ACCEPTED
2018-02-19 20:24:54 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=d05$
2018-02-19 20:24:54 ProcessNewBlock : ACCEPTED
2018-02-19 20:25:00 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=e74$
2018-02-19 20:25:00 ProcessNewBlock : ACCEPTED
2018-02-19 20:25:25 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=d4f$
2018-02-19 20:25:25 ProcessNewBlock : ACCEPTED
2018-02-19 20:25:34 We have a pending superblock at height 1980.000000  AcceptBlock::ExecuteDistributedComputingSanctuaryQuorumProcess PENDING_SUPERBLOCK UpdateTip: new best=9f7$
2018-02-19 20:25:34 ProcessNewBlock : ACCEPTED


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 19, 2018, 02:31:28 pm
One of my wallets was stuck syncing the masternode info for a little bit but it finally fully synced,
Got 2 Sanctuaries running now!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 02:32:21 pm
Pre-enabled but stuck here:

"AssetID": 3,
  "AssetName": "MASTERNODE_SYNC_MNW",
  "Attempt": 12,
  "IsBlockchainSynced": true,
  "IsMasternodeListSynced": true,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true
Code: [Select]

Debug.log:
2018-02-19 20:24:10 Misbehaving: 144.202.17.17:46840 (0 -> 14)
2018-02-19 20:24
2018-02-19 20:25:34 ProcessNewBlock : ACCEPTED



I think you are OK - sometimes new masternodes take a few hours to sync.  Could you please see if your blocks are still moving on that node- past block 2005?  And then type:
mnsync reset

And lets see if it makes it to 999?

Log looks OK.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 02:34:24 pm
One of my wallets was stuck syncing the masternode info for a little bit but it finally fully synced,
Got 2 Sanctuaries running now!
Yeah, I see my mag dropped to 774, you must have hogged all my mag!
JK, anyway I see we solved 16 of the 16 superblocks this time.

I just remembered, we should all post the sanctuary_rank from exec testvote.  But lets wait til we have at least 5 sancs...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 02:47:28 pm

I think you are OK - sometimes new masternodes take a few hours to sync.  Could you please see if your blocks are still moving on that node- past block 2005?  And then type:
mnsync reset

And lets see if it makes it to 999?

Log looks OK.

It's synced now. It took much longer than I was used to so that's why I posted it.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 19, 2018, 04:44:49 pm
The small devices would still work, but this would require a controller wallet running to know when the small device starts hashing.

Thinking about this a little deeper,  that might be a big boon for biblepay.  This would mean to get paid you need to keep your controller wallet running so it can send messages that your devices are starting tasks.  Thats a plus for our security , as that means our networking full node count is higher and the POW-heat side would not be virtually zero.  So this is actually a reasonable and positive requirement....

Lets think about this.
This would be a big minus for me. My controller wallet is on my notebook, which is my only one PC and that is not running 24/7. I really don't like an idea to put my wallet somewhere to run it 24/7 (e.g. VPS). I like current state :) It is ideal for me. OK, i'm just a small fish here, but I think, that you want to point this coin to people like me too. If there will be mobile phone wallet with this option, it wouldn't be so bad. This would be acceptable to almost everyone. There will be just another problem. You must be still online :) , so you need to pay mobile data. In developing countries it may be problem too. OK. I must stop writing, I'm really not optimistic :) But I like a PoDC a lot.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 04:51:40 pm
This would be a big minus for me. My controller wallet is on my notebook, which is my only one PC and that is not running 24/7. I really don't like an idea to put my wallet somewhere to run it 24/7 (e.g. VPS). I like current state :) It is ideal for me. OK, i'm just a small fish here, but I think, that you want to point this coin to people like me too. If there will be mobile phone wallet with this option, it wouldn't be so bad. This would be acceptable to almost everyone. There will be just another problem. You must be still online :) , so you need to pay mobile data. In developing countries it may be problem too. OK. I must stop writing, I'm really not optimistic :) But I like a PoDC a lot.

I catch your drift, but I think security and integrity trumps usability in this case.  I believe we should do everything possible to keep the system working for tablets and phones, and also, keep it acceissble for people in the unbanked world where they cant afford stakes to use it (IE dont make the rich richer).

Im thinking of ways to make that happen, but so far all I have are two modifications:
1) The "controller" wallet can run on any of your boincing pcs (IE if you send the wallet to the boinc PC, it doesnt necessarily mean your home PC has to stay on), but yes, so far at least one biblepay node has to stay up at all times
2) We can make the coin_amount*age modifier relatively small, but definitely intact.  What this would do is going back to the botnet issue, require a mining org to have BBP at stake to receive research rewards.  However in sympathy to 3rd world users mining to pay for a loaf of bread, we should require a pretty low stake amount, say < 99,000 bbp or something.  (I mean any amount would work, but dont give Huge benefits to people with a lot of coin age, or then the rich get richer).  Im thinking CoinAmount*CoinAge*RAC = Reward, but the CoinAmount*CoinAge is limited and capped to something like 7 days of coin age @ 250,000 BBP. Etc.

Im open to suggestions, but driving our price up due to a breakthrough feature, and helping 100,000 orphans is much much more important.  If our price goes up, people will find a way to leave a controller wallet running and then mine on multiple tablets :).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 05:02:13 pm
I catch your drift, but I think security and integrity trumps usability in this case.  I believe we should do everything possible to keep the system working for tablets and phones, and also, keep it acceissble for people in the unbanked world where they cant afford stakes to use it (IE dont make the rich richer).

Im thinking of ways to make that happen, but so far all I have are two modifications:
1) The "controller" wallet can run on any of your boincing pcs (IE if you send the wallet to the boinc PC, it doesnt necessarily mean your home PC has to stay on), but yes, so far at least one biblepay node has to stay up at all times
2) We can make the coin_amount*age modifier relatively small, but definitely intact.  What this would do is going back to the botnet issue, require a mining org to have BBP at stake to receive research rewards.  However in sympathy to 3rd world users mining to pay for a loaf of bread, we should require a pretty low stake amount, say < 99,000 bbp or something.  (I mean any amount would work, but dont give Huge benefits to people with a lot of coin age, or then the rich get richer).  Im thinking CoinAmount*CoinAge*RAC = Reward, but the CoinAmount*CoinAge is limited and capped to something like 7 days of coin age @ 250,000 BBP. Etc.

Im open to suggestions, but driving our price up due to a breakthrough feature, and helping 100,000 orphans is much much more important.  If our price goes up, people will find a way to leave a controller wallet running and then mine on multiple tablets :).


Thinking more about this I think we can have our cake and eat it too.  As long as the CPID does not have any computers on the CPID.

We can say : If the CPID is only phones & tablets, allow it in with no penalty with a stake age of 1 day @ 10000 bbp. 

Otherwise, require proof of every task, every task start time, and a UTXO.  So for the small fish in the block (usually < 100 RAC or so) we could let them in.    I wouldnt mind programming that in, especially for usability in 3rd world countries.

It makes sense, because the power users are the hogs, and those are the ones we check fully.  Then we still have our integrity and competition etc.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 19, 2018, 05:07:38 pm
I catch your drift, but I think security and integrity trumps usability in this case. 

Im open to suggestions, but driving our price up due to a breakthrough feature, and helping 100,000 orphans is much much more important.  If our price goes up, people will find a way to leave a controller wallet running and then mine on multiple tablets :).
I agree with you. I just wanted to point on another point of view :) You're making great job and I'm impressed with yours fast making concept/programming ability. Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 05:10:16 pm
I agree with you. I just wanted to point on another point of view :) You're making great job and I'm impressed with yours fast making concept/programming ability. Thanks.
Thanks Orbis, if it works then all credit to Yeshua.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 19, 2018, 05:25:44 pm
Ok. Now to testing :) After update I've must to start mining to have some tBBP to join Rosetta. Now I'm in, but my magnitude is 0. It all starts from zero after update?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 06:01:10 pm
Ok. Now to testing :) After update I've must to start mining to have some tBBP to join Rosetta. Now I'm in, but my magnitude is 0. It all starts from zero after update?

No, whenever it gets the data file from Rosetta it will update your mag.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 07:06:02 pm
No, whenever it gets the data file from Rosetta it will update your mag.

Well actually since we have been in business a few days it already knows all of our CPIDs on the sanc side, but you need to reassociate your CPID.

After 6 confirms, you should see your mag reappear.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 08:11:32 pm
My node was synced but now it's not, is that normal? I do see the blocks going up.

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true

"version": 1000903,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.3",
  "balance": 3198180.27801030,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 2688,
  "timeoffset": 0,
  "connections": 10,
  "proxy": "",
  "difficulty": 0.07714083926784768,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 08:17:16 pm
My node was synced but now it's not, is that normal? I do see the blocks going up.

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",
  "Attempt": 0,
  "IsBlockchainSynced": false,
  "IsMasternodeListSynced": false,
  "IsWinnersListSynced": false,
  "IsSynced": false,
  "IsFailed": false,
  "MasternodesEnabled": true

"version": 1000903,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.3",
  "balance": 3198180.27801030,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 2688,
  "timeoffset": 0,
  "connections": 10,
  "proxy": "",
  "difficulty": 0.07714083926784768,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""


Sounds like a sanctuary sync issue (not a chain sync problem), which I feel pretty good about because we havent fundamentally changed the sanctuary code.  Your probably OK, lets check some others sancs and ensure they are 999 also.  Ill check mine in a few mins.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 08:25:53 pm
I see someone is trying to hack my CPID in testnet.  I see the users testnet bbp address is yRo7XJD3rWw88DuaHsu5VkXnMwtbn4mqv5.  I just sent you 125 bbp with a message Happy Hacking!  Its probably Swongle.

Thanks for testing that for us.  I see the network rejected the fraudulent transaction.

(The hacker was trying to insert a fraudulent burn in the chain with my CPID in it).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 08:35:36 pm
I was setting up a 2nd node so I had to restart the daemon on my controller wallet. Now the daemon will only run for about a minute then stop.

2018-02-20 02:33:22  GetBlockSubsidy 2673.000000
2018-02-20 02:33:22 init message: Done loading
2018-02-20 02:33:33 P2P peers available. Skipped DNS seeding.
2018-02-20 02:33:33 dnsseed thread exit
2018-02-20 02:33:45 Misbehaving: 206.125.154.17:5719 (0 -> 14)

UPDATE

Not sure what's going on but started it a third time and it's running ok now.....
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 08:42:42 pm
I was setting up a 2nd node so I had to restart the daemon on my controller wallet. Now the daemon will only run for about a minute then stop.

2018-02-20 02:33:22  GetBlockSubsidy 2673.000000
2018-02-20 02:33:22 init message: Done loading
2018-02-20 02:33:33 P2P peers available. Skipped DNS seeding.
2018-02-20 02:33:33 dnsseed thread exit
2018-02-20 02:33:45 Misbehaving: 206.125.154.17:5719 (0 -> 14)

Can you please run it in valgrind if you have more than 2gb of ram?

sudo apt-get valgrind

valgrind ./biblepayd

?

That will give us the line of the error.
 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 08:44:42 pm
Can you please run it in valgrind if you have more than 2gb of ram?

sudo apt-get valgrind

valgrind ./biblepayd

?

That will give us the line of the error.

The vps only has 0.7gb of ram. I can try that later when I upgrade it but I'll just monitor it for now. Thank you.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 19, 2018, 08:48:15 pm
The vps only has 0.7gb of ram. I can try that later when I upgrade it but I'll just monitor it for now. Thank you.

Ok cool.  Ill run it that way also if I encounter a crash.

On your nonsyncing sanc you can check to see in coin control if you still have the 500K.  I spent mine today, and it didnt throw any errors and stopped syncing in mnsync also... Reenabling mine now to see if that was it.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 08:52:58 pm
Ok cool.  Ill run it that way also if I encounter a crash.

On your nonsyncing sanc you can check to see in coin control if you still have the 500K.  I spent mine today, and it didnt throw any errors and stopped syncing in mnsync also... Reenabling mine now to see if that was it.

I checked my wallet and both of the wallet accounts have at least 500k tBBP. Masternode outputs also still show 2 hashes. Both nodes are still at 1. How does the nodes sync anyways? Does it get the information from the memory pool? Where is the memory pool?

UPDATE:
Node #2 stopped again.

UPDATE#2:
You forgot to add "install" in the apt-get command if you want to update it.

UPDATE#3:
valgrind is using 99% of my cpu and getinfo returns
error code: -28
error message:
Loading block index...

I upgraded to 2GB ram but it's the same. I tried getinfo without valgrind and its fine.

UPDATE #4:
Valgrind gave me something when I left it running:
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 19, 2018, 08:55:23 pm
I see someone is trying to hack my CPID in testnet.  I see the users testnet bbp address is yRo7XJD3rWw88DuaHsu5VkXnMwtbn4mqv5.  I just sent you 125 bbp with a message Happy Hacking!  Its probably Swongle.

Thanks for testing that for us.  I see the network rejected the fraudulent transaction.

(The hacker was trying to insert a fraudulent burn in the chain with my CPID in it).

Thats awesome! Glad people are testing everything :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 19, 2018, 09:08:30 pm
Thats awesome! Glad people are testing everything :)

lol, so which one of us is going to hold Rosetta at gunpoint to test that? ;D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 19, 2018, 09:35:03 pm
Are your nodes synced? mnsync status?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 20, 2018, 12:56:47 am
I catch your drift, but I think security and integrity trumps usability in this case.  I believe we should do everything possible to keep the system working for tablets and phones, and also, keep it acceissble for people in the unbanked world where they cant afford stakes to use it (IE dont make the rich richer).

Im thinking of ways to make that happen, but so far all I have are two modifications:
1) The "controller" wallet can run on any of your boincing pcs (IE if you send the wallet to the boinc PC, it doesnt necessarily mean your home PC has to stay on), but yes, so far at least one biblepay node has to stay up at all times
2) We can make the coin_amount*age modifier relatively small, but definitely intact.  What this would do is going back to the botnet issue, require a mining org to have BBP at stake to receive research rewards.  However in sympathy to 3rd world users mining to pay for a loaf of bread, we should require a pretty low stake amount, say < 99,000 bbp or something.  (I mean any amount would work, but dont give Huge benefits to people with a lot of coin age, or then the rich get richer).  Im thinking CoinAmount*CoinAge*RAC = Reward, but the CoinAmount*CoinAge is limited and capped to something like 7 days of coin age @ 250,000 BBP. Etc.

Im open to suggestions, but driving our price up due to a breakthrough feature, and helping 100,000 orphans is much much more important.  If our price goes up, people will find a way to leave a controller wallet running and then mine on multiple tablets :).

So here would be my suggestion, which is very off the cuff after 10 hours at work and I've not fully thought this out but wanted to get something down as it was fresh.

Would it be possible to have the stake amount relative to the RAC?  What I'm thinking is this, big fish (which I might be considered) could be held to the "who much is given, much is required" standard.  So if someone with RAC of 5K might be required to have a balance of 50K BBP to receive the full benefit or their high RAC, whereas a new user or poor users isn't going to have that so they might receive their full benefit from 200 RAC at only 500 BBP?  So in short/long, cap the benefit both overall, but also in terms of relative to the RAC/BBP ratio.  Furthermore, would it be possible for mobile users to receive a lessor benefit from a not-always-connected phone, provided they updated within some time frame of a new WU?

Anyhow, I'll consider more details as I wake up tomorrow.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 20, 2018, 03:10:55 am
in other side: mining on phones is bad or with SIM cards= internet traffic with biblepay is very bad for most poor ppl  :-[ = almost 60GB monthly
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 20, 2018, 07:06:30 am
I checked my wallet and both of the wallet accounts have at least 500k tBBP. Masternode outputs also still show 2 hashes. Both nodes are still at 1. How does the nodes sync anyways? Does it get the information from the memory pool? Where is the memory pool?

UPDATE:
Node #2 stopped again.

UPDATE#2:
You forgot to add "install" in the apt-get command if you want to update it.

UPDATE#3:
valgrind is using 99% of my cpu and getinfo returns
error code: -28
error message:
Loading block index...

I upgraded to 2GB ram but it's the same. I tried getinfo without valgrind and its fine.

UPDATE #4:
Valgrind gave me something when I left it running:
Great, Im glad you were finally able to figure out how to get valgrind running.
Coincidentally last night my dev testnet died before going to sleep and I left it run in valgrind.
I have the exact same log as you, so thats good that we agree we crashed in the same exact place.
So this looks a little fishy, because this line has been in forever.  It points toward possible hacking (IE spamming us with some invalid blocks), but i cant say for sure.
Anyway, I did fix the issue to prevent a crash by rejecting the block and continuing. I checked in 1.0.9.3b if you want to go ahead upgrade now.

** I recommend everyone testing to upgrade to 1.0.9.3b to avoid the crash.   Ill compile a windows version today **


You were asking:
"I checked my wallet and both of the wallet accounts have at least 500k tBBP. Masternode outputs also still show 2 hashes. Both nodes are still at 1. How does the nodes sync anyways? Does it get the information from the memory pool? Where is the memory poo?"

I don't understand the question but it sounds like you are asking a couple different questions, but Im not sure in what context or why you are asking these things. Some are googlable, regarding bitcoin and the memory pool, but it sounds like you are wondering why the sanc wont sync in regards to its mnsync command, but also mentioning memory pool for "syncing".  So Im not sure what the question means, could you please elaborate?



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 20, 2018, 07:22:34 am
in other side: mining on phones is bad or with SIM cards= internet traffic with biblepay is very bad for most poor ppl  :-[ = almost 60GB monthly

No, Im seeing the biblepay wallet used 78 meg of bandwidth over 24 hours.

The rosetta mining device uses Zero of your biblepay bandwidth (as biblepay controller is on a different machine than a tablet or phone).  Rosetta uses its own bandwidth for new tasks and task checking.  I dont think the packets are that big. 
Someone needs to test boinc/rosetta with wireshark software. 
Be sure to realize the first 2-3 slots that get filled with Rosetta data are much larger, because its downloading the protein database and the program.  After a couple hours you should take a 24 hour baseline and then actually know the *real* consumption of the mining node.

If we add real time certification of tasks, I suppose it will increase bandwidth on the controller, but not by more than 10% or so.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 20, 2018, 07:54:27 am
Updated the node.

Don't worry about my questions from above, I'll just google it. Thanks.

UPDATE:
The node stopped again.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 20, 2018, 08:45:30 am
Updated the node.

Don't worry about my questions from above, I'll just google it. Thanks.

UPDATE:
The node stopped again.

Yeah, I valgrinded it and now it died a couple lines before the same place.  I checked in 1093c, please grab that one now, LOL!

So far I think 1093c got past it- Ive been running 30 minutes now.

Anyway I do see a sanc mnsync issue on my 2nd sanc also.  But let me research that a little further, as our chainparams might not be calling for all parts of sancs to start until block 5000, Or, it could be that we only have 5 sancs and 3 of them are only preenabled (IE not a supermajority).  Im thinking it is one of these two things, Ill take a look.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 20, 2018, 08:56:10 am
Yeah, I valgrinded it and now it died a couple lines before the same place.  I checked in 1093c, please grab that one now, LOL!

So far I think 1093c got past it- Ive been running 30 minutes now.

Anyway I do see a sanc mnsync issue on my 2nd sanc also.  But let me research that a little further, as our chainparams might not be calling for all parts of sancs to start until block 5000, Or, it could be that we only have 5 sancs and 3 of them are only preenabled (IE not a supermajority).  Im thinking it is one of these two things, Ill take a look.

Its not our chainparams; our masternodes are fully enabled at block 202 in testnet.
I think its the fact that none of the 5 pre-enabled masternodes have been on long enough; too many people have crashed and restarted over night.
Lets give it a good run and see if our masternodes start communicating over the next 8 hours or so, then we regroup and check mnsync status.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 20, 2018, 09:19:31 am
Its not our chainparams; our masternodes are fully enabled at block 202 in testnet.
I think its the fact that none of the 5 pre-enabled masternodes have been on long enough; too many people have crashed and restarted over night.
Lets give it a good run and see if our masternodes start communicating over the next 8 hours or so, then we regroup and check mnsync status.

Just to accelerate our Sancs sync in testnet, anyone who has 0 PS compatible masternodes showing in : Tools | Information: Total Number of Masternodes (PS Compatible 0/0), please rm blocks, rm chainstate and resync.  I didnt have to delete the *.dat files, I just resynced, and then all 5 of the masternodes showed up.  Once that happens, I think our other masternodes will start syncing mnpayments again, and then the 'mnsync status'will move to 999 for everyone quicker.


In my case, my dev machine had the correct MN list, my vultr machine didnt, I resynced it, and now both agree.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 20, 2018, 09:29:38 am
Just to accelerate our Sancs sync in testnet, anyone who has 0 PS compatible masternodes showing in : Tools | Information: Total Number of Masternodes (PS Compatible 0/0), please rm blocks, rm chainstate and resync.  I didnt have to delete the *.dat files, I just resynced, and then all 5 of the masternodes showed up.  Once that happens, I think our other masternodes will start syncing mnpayments again, and then the 'mnsync status'will move to 999 for everyone quicker.


In my case, my dev machine had the correct MN list, my vultr machine didnt, I resynced it, and now both agree.

My node is synced now! Hope it won't stop anymore.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 20, 2018, 12:35:47 pm
Could someone send me 500.000 tBBP so I can set up a new masternode?

yaxDh4ioa8bg3QWzDYeycFyuvt9yxi8xWJ
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 20, 2018, 01:41:49 pm
Could someone send me 500.000 tBBP so I can set up a new masternode?

yaxDh4ioa8bg3QWzDYeycFyuvt9yxi8xWJ

Sent.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 20, 2018, 02:39:17 pm
Alright, windows 1093 is out there, now lets try to increase our Sanc count to ensure all sancs sync to 999.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 20, 2018, 04:14:30 pm
Alright, windows 1093 is out there, now lets try to increase our Sanc count to ensure all sancs sync to 999.

Just fired up my sactuary again. Synced nicely up to 999 and is PRE-ENABLED now. Also installed the latest windows wallet.

One (minor) thing: the 'setgenerate 1' option makes the wallet hash at the old speed again (not 1%) on both the linux and windows wallets. I think it was also the case with the previous version.
So, to be clear: with the current wallet, when I do 'setgenerate 1 true', on my quadcore 4 thread system, I'm using about 25% of my CPU.

(And T-Mike: thanks for the tBBP!)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 20, 2018, 05:46:15 pm
Rob whatever you fixed in latest commit fixed issue I had on my one of my linux sanctuaries,
folders and .dat files deleted, I couldnt get it to reindex, it would be stuck at block 0 for a little bit and crash, works now!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 20, 2018, 09:00:10 pm
OK, 3 nodes up and running. I'll set up some more tomorrow.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 21, 2018, 05:23:09 am
Rob whatever you fixed in latest commit fixed issue I had on my one of my linux sanctuaries,
folders and .dat files deleted, I couldnt get it to reindex, it would be stuck at block 0 for a little bit and crash, works now!

Great!

Yes, we had at least 2 bugs, and Im a little happier when I see the reason for them instead of programming around the issue until we drop.

The first bug, the reason we couldnt sync from 0, was due to a 2 digit rounding error in the old contract.  I found out that the grand total magnitude with 25 researchers, out to the 2nd digit in scale was 1000.03, which created an attempted overpayment, and due to the grandfather rule we synced over that block but it "covered" up the problem.  Now the system shoots for a 998 magnitude, and uses 3 digit scale, so that appears to have solved the syncing issue permanently.

I have a lot of code coming today so we wont be in this lull long.  Ive been working on the integrated integrity feature.  I truly think if we can reconcile the rosetta work with utxo's, we will be the first coin to have trustable PODC.  PODC that exceeds the righteousness of the Pharisees and scribes, just kidding.  No PODC that exceeds the trust of POS, because POS is based on UTXO (unspent outputs).

So with greater integrity comes a greater workload for the controller wallet and the sancs, that means more propensity for clerical errors or should I say technical errors in the sancs.  For example what if a sanctuary fails to verify one task out of 100, due to a vultr network tcp error, I would hate to throw the entire contract off (meaning our SanctuaryQuorum would fail and no one would be paid).  And that would happen if one unverified task lowered a researchers task integrity level from 100 to 91.123 and other sancs felt a different way about various researchers.  The other one is UTXOWeight, although Im not worried about that as much, because it will always verify correctly, but it needs to established that the window of UTXOWeight must be exact, for example if one researcher sent 2 UTXO's in 8 hours of PODC updates, in 24 hours period, then the Sanc creating the contract must have an exact start-endtime snapped into the grid as well. 

To handle this, Im creating a UTXO Weight breaks chart.  This means researchers will receive a Percentage reward based on the UTXO Stake Amount inside the PODC update from a chart, with relatively large breaks.  Something like 1-50000 BBP is in the chart, (the chart ends at 50,000 bbp max to not give much advantage to whales), and we have a break every 10000.  This means only 6 allowable reward levels: 0, .2, .40, .60, 1.00 Etc.  This way the contracts will tend to "jive" across all sancs.  Im doing the same thing with the Task integrity system - the validated tasks as compared to total researcher tasks will snap to a grid, so that the user receives a percentage float result based on .20 breaks.  I think what happens in the end is everyone is assessed with 3 values per day that comprise ones magnitude:  UTXOWeight (0-100%), TaskWeight (0-100%) and RosettaRAC (Current RAC from Boinc).  We multiply your UTXOWeight*TaskWeight*RosettaRAC to arrive at your magnitude while preprocessing the file.  These levels will allow us to write an exportable excel report with trustable integrity per day with actual provable details per researcher.  (If for example Rosettas SQL DBA is being held up at gunpoint after one of our timestamps, it will disrupt the integrity of those affected researchers due to timestamp manipulation).

Finally, I am adding sporks for system enabling of the UTXOWeight, and TaskWeight as distinct features.  This allows us to shutdown those two features and revert back to plain vanilla PODC in case something goes haywire in prod.  The most common thing I can think of is not that UTXO "blows up", but that the Task Validation system malfunctions - possibly because the boinc servers are down while Rosetta is up.  Im thinking if something in the public interface changes, for example, if boinc shoots out emergency updates that break compatibility with biblepay, we can shut off TaskWeight with a spork, and still survive in our old plain vanilla PODC mode (daily RAC rewards) until that other piece is fixed again.  So we would have more granular survival levels:  Plain PODC, PODC + UTXO + TaskAudits, or POBH mining only - etc.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 21, 2018, 02:49:06 pm
...
Otherwise, require proof of every task, every task start time, and a UTXO.  So for the small fish in the block (usually < 100 RAC or so) we could let them in.    I wouldnt mind programming that in, especially for usability in 3rd world countries.
...
Rob, to the small fishes :)
My Nexus 4 testing is going really great. Just for imagination my RAC on that device is 280 ;) Of course it runs almost 24/7.
https://boincstats.com/en/stats/-1/host/detail/333426255/lastDays
Oh... to the data consuption... In those 6 days it spent approx. 1GB.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 21, 2018, 05:26:41 pm
Rob, to the small fishes :)
My Nexus 4 testing is going really great. Just for imagination my RAC on that device is 280 ;) Of course it runs almost 24/7.
https://boincstats.com/en/stats/-1/host/detail/333426255/lastDays
Oh... to the data consuption... In those 6 days it spent approx. 1GB.

Ok, thanks, let me take a look at what the sanctuary can find out about the host.  We should definitely consider allowing tablets and phones without any extra work from the controller. 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 21, 2018, 05:35:59 pm
Thanks. And small detail to the future. I think, that will be fair that Biblepay team country on Rosetta should be "International", not "Canada". And why is it Canada? :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 21, 2018, 06:07:37 pm
I didn't start the other nodes today because it looks like there will be an update soon.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 21, 2018, 08:02:27 pm
Thanks. And small detail to the future. I think, that will be fair that Biblepay team country on Rosetta should be "International", not "Canada". And why is it Canada? :)

Its a mistake, it should be Intl, let me see if I can fix it now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 21, 2018, 08:12:35 pm
I didn't start the other nodes today because it looks like there will be an update soon.

Good point.  Yeah, its very, very close.  Im testing it on my LAN now.  Im not sure if it will be ready tonight though...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 21, 2018, 09:11:06 pm
Good point.  Yeah, its very, very close.  Im testing it on my LAN now.  Im not sure if it will be ready tonight though...

No problem.

By the way, I don't think it's very loving to say "get lost". I understand your frustration though.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 06:44:07 am
No problem.

By the way, I don't think it's very loving to say "get lost". I understand your frustration though.

He said We were all here for Greed, and alluded that this project is about money and were not really Christians.  Your right, I should have replied with more Love.

If you look at the history, I have tried that, and God actually says to forgive your brother not 7 times but 77 times.
I do forgive him....

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 06:44:57 am
Its a mistake, it should be Intl, let me see if I can fix it now.

This had to be escalated to the top.  I entered a ticket for it - and they closed it.  I emailed David Anderson.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 22, 2018, 08:36:18 am
He said We were all here for Greed, and alluded that this project is about money and were not really Christians.  Your right, I should have replied with more Love.

If you look at the history, I have tried that, and God actually says to forgive your brother not 7 times but 77 times.
I do forgive him....

I understand your frustration Rob. Slovakia is quite the character, and I think he must have used up most of the '77 times' by now  ;D


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 10:45:13 am
I understand your frustration Rob. Slovakia is quite the character, and I think he must have used up most of the '77 times' by now  ;D

LOL, Hes getting there.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 10:47:13 am
1.0.9.4b - Mandatory Upgrade for Testnet

- Add PODC Integrity system to core wallet
- Require controller wallet to send task updates into the blockchain
- Require Sanctuaries to Verify Rosetta Tasks
- Base Magnitude on UTXOWeight, TaskWeight and RACWeight

* Windows is compiling now *
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 11:03:06 am
So, our PODC system is becoming pretty huge, and its obviously adding inrinsic value to Biblepay for the long haul.

We have a lot to test and a lot to explain.

First,  please see the changes I made to the wiki page on distributed computing:
http://wiki.biblepay.org/Distributed_Computing

Search for the "Biblepay UTXO Reward Chart".
Once you find that, please review the utxo reward chart and the Task Integrity reward chart and the Disaster Recovery Modes chart.

Hopefully those charts will explain the primary changes.

Let me go over the primary changes:

- Researchers are required to be on Team Biblepay for the researching credit to count.
(Support personnel can point the user to exec getboincinfo, look for TEAM: 15044, and if the researcher CPID is missing from the team they will see a warning).

- It is required that the controller wallet be running mostly 24/7, in order to be paid for research.
We now have a metric per cpid called "Task Integrity" (Its called TaskWeight in getboincinfo).  This is a percentage from 0-100% and is based on the integrity level the sanctuaries have assessed your CPID with.  If for example one CPID is working on 10 tasks, if 2 of those tasks are found to be tampered with- the task will not be counted as part of the integrity level.  If no task updates are transmitted from the controller wallet, No rewards are given to the researcher.  This means for now, you must run the controller wallet 24/7.  See the Task Integrity chart for a breakdown on the snap-to-grid reward percentages.

- You must run at least one thread in the controller wallet miner.  Setgeneratetrue = 1 or greater.  Otherwise biblepay will not transmit the PODCUpdates to the blockchain.

- The PODCUpdate transaction can be seen from the txlist.

- Inside the PODCUpdate, we send a coinstake "stake amount".  This ties the tasks that CPID is working on with a UTXO output, and also the CPID signature is required.  Depending on the level of stake, your magnitude is adjusted.  You receive a "UTXOWeight" value from 0-100%.  See the UTXO Weight chart to determine your place on the chart.  (Note, if the controller cannot sign with the CPID, no credit is rewarded for the UTXOWeight or the TaskWeight).

- Exec getboincinfo will also show the UTXOWeight and TaskWeight levels.  This will be useful in diagnosing issues to find why payments are not being received.

I know some people will view this as: Why have we made it so complicated to research?  However, the upside to these changes, proving each UTXO belongs to a researchers tasks at a given point in time is of far more benefit.  It will also provide higher rewards to those who maintain the  infrastructure properly.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 22, 2018, 11:52:06 am
jaapgvk+tmike+rob= the defamation of other people is a manifestation of selfishness  ;) we are here only for profit 99.99% all SVK miners=our electricity is expensive here
too bad,that the state didntt care about the orphans
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 22, 2018, 11:54:41 am
Awesome, so just to summarize:
We will have to have our controller wallet (the wallet with the CPID Burn link) be on 24/7 mining at 1 thread?
We will need 50,000 BBP in the controller wallet to receive max research rewards?


./biblepay-cli getblockhash 5260
1fbe3bcb4325233dd43aa6eefa46c22c966ad1e6e5420e022956cb33caf16d7f

./biblepay-cli mnsync status

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",

Im still masternode syncing, but not seeing attempts, weird, Ill report back later
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 12:30:32 pm
Awesome, so just to summarize:
We will have to have our controller wallet (the wallet with the CPID Burn link) be on 24/7 mining at 1 thread?
We will need 50,000 BBP in the controller wallet to receive max research rewards?


./biblepay-cli getblockhash 5260
1fbe3bcb4325233dd43aa6eefa46c22c966ad1e6e5420e022956cb33caf16d7f

./biblepay-cli mnsync status

  "AssetID": 1,
  "AssetName": "MASTERNODE_SYNC_SPORKS",

Im still masternode syncing, but not seeing attempts, weird, Ill report back later

Yes, your controller wallet with the associations would have to be the one to stay on so it can send the podc updates.  It sends one every 4-8 hours (spork TBD still), but only if task updates have changed.  Note for people with more than one CPID, it sends one PODC update PER cpid per frequency.

As far as the 50K requirement, thats generally correct, but the stakeminer tries to use .05% of the balance unless you set POLpercentage=50 in the config. 

As far as syncing, please try to rebuild the chain after deleting mn*.dat. 

One nice side benefit we will reap is the controller wallets will be on for more pobh security 24/7.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 22, 2018, 12:43:45 pm
Okay removing the chainstate and blocks folders and the .dat files and doing a reindex worked,
both testnet sanctuaries synced now, and Im running 1 miner thread on the one with the CPID burn

./biblepay-cli getblockhash 5291
e85566fcf7a1f2da10af68206543aa2270568c725903f56293ba1bf9d7190556
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 12:59:15 pm
Okay removing the chainstate and blocks folders and the .dat files and doing a reindex worked,
both testnet sanctuaries synced now, and Im running 1 miner thread on the one with the CPID burn

./biblepay-cli getblockhash 5291
e85566fcf7a1f2da10af68206543aa2270568c725903f56293ba1bf9d7190556

Great!  To jump start your node without waiting 4 hours type:
exec podcupdate

Wait 6 blocks (til the podcupdate tx is ticked) , then type exec getboincinfo and see if your TaskWeight=100% and your UTXOWeight=100%?

If so that means the researcher will receive the Full reward.


Btw, in heavenly mode, thats the mode we are in now, we are in DR Mode == 0 (Heavenly) currently, Magnitude = TaskWeight * UTXOWeight * RAC.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 22, 2018, 01:11:50 pm
Code: [Select]
./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422035,
  "NextSuperblockHeight": 5346,
  "NextSuperblockBudget": 1380386,
  "93138f032bdd027fa3246b48bb715a77_RAC": 7229.4,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
[b]  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 0,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 0,[/b]
  "Total_RAC": 7229.4,
  "Total Payments (One Day)": 725112,
  "Total Payments (One Week)": 15047816,
  "Total Budget (One Day)": 4141158,
  "Total Budget (One Week)": 48313510,
  "Superblock Count (One Week)": 49,
  "Superblock Hit Count (One Week)": 35,
  "Superblock List": "5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5247,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 311.4618664634385
}



./biblepay-cli exec podcupdate
{
  "Command": "podcupdate",
  "PODCUpdate": true
}



./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422035,
  "NextSuperblockHeight": 5346,
  "NextSuperblockBudget": 1380386,
  "93138f032bdd027fa3246b48bb715a77_RAC": 7229.4,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
[b]  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 0,[/b]
  "Total_RAC": 7229.4,
  "Total Payments (One Day)": 725112,
  "Total Payments (One Week)": 15047816,
  "Total Budget (One Day)": 4141158,
  "Total Budget (One Week)": 48313510,
  "Superblock Count (One Week)": 49,
  "Superblock Hit Count (One Week)": 35,
  "Superblock List": "5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5247,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 311.4618664634385
}

ok looks like TaskWeight went from 0 to 100 but UTXOWeight still at 0

Is there anything I have to do for the staking/UTXO part?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 01:24:05 pm





Code: [Select]

  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422035,
  "NextSuperblockHeight": 5346,
  "NextSuperblockBudget": 1380386,
  "93138f032bdd027fa3246b48bb715a77_RAC": 7229.4,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
[b]  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 0,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 0,[/b]
  "Total_RAC": 7229.4,
  "Total Payments (One Day)": 725112,
  "Total Payments (One Week)": 15047816,
  "Total Budget (One Day)": 4141158,
  "Total Budget (One Week)": 48313510,
  "Superblock Count (One Week)": 49,
  "Superblock Hit Count (One Week)": 35,
  "Superblock List": "5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5247,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 311.4618664634385

ok looks like TaskWeight went from 0 to 100 but UTXOWeight still at 0

Is there anything I have to do for the staking/UTXO part?


Hmm,

Maybe you didnt wait long enough, please try exec getboincinfo now, does it show 100 for utxoweight now?

Looking at the list:


13:21:20

Code: [Select]

exec datalist utxoweight


13:21:20

{
  "DataList": "UTXOWEIGHT",
  "04FBA56D89A5EB38B1B82F8A6240132C": "",
  "4FD1BF6C6900D92B226E16C6A6935661": "",
  "6785DED1F65063EF8F01F42DEB31CF1D": "",
  "71F1F1F46DEB2F25961C7D9AF06F2B31": "",
  "8735CFE64D964416DBA6015EB414CF7E": "",
  "93138F032BDD027FA3246B48BB715A77": "100",
  "95A79CD5829E8315B0B946709930DF18": "",
  "C9085154B7CC0CA2B5189672559DD6D8": "100",
  "CA895B47AACFFBDBF906201821AF2F9F": "100",
  "CC37D0EF74A621379974484F43D3B1C5": "",
  "D9B22FCCFAE5582D4EE7838883AAA3CF": "",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7": "",
  "E94C1704C75F731F8BFDE303F08408EE": "",
  "F80AB050AB53459EC937879A046D603E": ""
}

Looks like you are 100% now.

Let me run the commands to check our next pending block.

Oh btw, when you post long pastes, please surround them with the "[ code ]" and the "[ / code ]" so they look shorter - thanks man.


EDIT:

Ok, it looks like you are going to be fine, here is a secret, to find out what the next superblock is going to look like, run the exec testvote, and extract the contract row starting with your cpid like this:
93138f032bdd027fa3246b48bb715a77,597.312,1981221,15044,100,100,11999\n

Notice the last 4 fields: 15044 is your team, 100 is your utxo weight, and 100 is your taskweight, and 11999 is the team total verified task RAC.  This is what composes your magnitude.  So now I know your magnitude will be changing on this next block.  Let me see when that hits.

Your magnitude should change right after block 5346 is solved.  So you can run exec getboincinfo now, and you probably have your last magnitude based on the old DR mode.   Then check the magnitude and paste after 5346 is over. 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 22, 2018, 01:30:53 pm
Maybe you didnt wait long enough, please try exec getboincinfo now, does it show 100 for utxoweight now?

Shows 100 for UTXOWeight now!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 01:33:56 pm
Shows 100 for UTXOWeight now!

Its good to know you have 311 mag right now, as of the last post, thats because we were in dr mode 3 prior to the upgrade.

(The system finds your mag from the last solved superblock).

  But please, post it for us after block 5346- Im curious what you jump up to.
You should jump higher since only 3 of us have 100% integrity currently.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 01:35:46 pm
Shows 100 for UTXOWeight now!
Hey btw what block number was your PODC update in?  I noticed you were running a massive number of tasks, like hundreds.
I need to see what your CPID did to our block size?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 22, 2018, 01:43:09 pm
Hey btw what block number was your PODC update in?  I noticed you were running a massive number of tasks, like hundreds.
I need to see what your CPID did to our block size?

Hmm Im not sure, had to be from block 5291 or upwards, Is there a way to check?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 22, 2018, 02:06:01 pm
Its good to know you have 311 mag right now, as of the last post, thats because we were in dr mode 3 prior to the upgrade.

(The system finds your mag from the last solved superblock).

  But please, post it for us after block 5346- Im curious what you jump up to.
You should jump higher since only 3 of us have 100% integrity currently.

Code: [Select]
./biblepay-cli getinfo
{
  "version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 17470827.03959162,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 5347,
  "timeoffset": 0,
  "connections": 9,
  "proxy": "",
  "difficulty": 0.21511500044313,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422036,
  "NextSuperblockHeight": 5445,
  "NextSuperblockBudget": 1380386,
  "93138f032bdd027fa3246b48bb715a77_RAC": 7229.4,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 7229.4,
  "Total Payments (One Day)": 725112,
  "Total Payments (One Week)": 15047816,
  "Total Budget (One Day)": 5521544,
  "Total Budget (One Week)": 49693896,
  "Superblock Count (One Week)": 50,
  "Superblock Hit Count (One Week)": 36,
  "Superblock List": "5346,5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5346,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 302.8101479505652
}

Block 5347, looks like my Magnitude went down from 311 to 302
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 22, 2018, 02:06:37 pm
3 sanctuaries up.

Before block 5346:
Code: [Select]
"version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 9574526.06132864,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 5339,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.2604936799427617,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

Code: [Select]
"Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84",
  "CPIDS": "f80ab050ab53459ec937879a046d603e;71f1f1f46deb2f25961c7d9af06f2b31;cc37d0ef74a621379974484f43d3b1c5;95a79cd5829e8315b0b946709930df18;e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422035,
  "NextSuperblockHeight": 5346,
  "NextSuperblockBudget": 1380386,
  "f80ab050ab53459ec937879a046d603e_RAC": 430.07,
  "f80ab050ab53459ec937879a046d603e_TEAM": 15044,
  "f80ab050ab53459ec937879a046d603e_TaskWeight": 100,
  "f80ab050ab53459ec937879a046d603e_UTXOWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_RAC": 441.45,
  "71f1f1f46deb2f25961c7d9af06f2b31_TEAM": 15044,
  "71f1f1f46deb2f25961c7d9af06f2b31_TaskWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_UTXOWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_RAC": 446.56,
  "cc37d0ef74a621379974484f43d3b1c5_TEAM": 15044,
  "cc37d0ef74a621379974484f43d3b1c5_TaskWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_UTXOWeight": 100,
  "95a79cd5829e8315b0b946709930df18_RAC": 407.91,
  "95a79cd5829e8315b0b946709930df18_TEAM": 15044,
  "95a79cd5829e8315b0b946709930df18_TaskWeight": 100,
  "95a79cd5829e8315b0b946709930df18_UTXOWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 557.48,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 2283.47,
  "Total Payments (One Day)": 223900,
  "Total Payments (One Week)": 2028581,
  "Total Budget (One Day)": 4141158,
  "Total Budget (One Week)": 48313510,
  "Superblock Count (One Week)": 49,
  "Superblock Hit Count (One Week)": 35,
  "Superblock List": "5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5247,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 41.98786219423925

After Block 5346:
Code: [Select]
"version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 9601523.09132864,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 5350,
  "timeoffset": 0,
  "connections": 9,
  "proxy": "",
  "difficulty": 0.1106453170532401,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

Code: [Select]
"Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84",
  "CPIDS": "f80ab050ab53459ec937879a046d603e;71f1f1f46deb2f25961c7d9af06f2b31;cc37d0ef74a621379974484f43d3b1c5;9
5a79cd5829e8315b0b946709930df18;e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422036,
  "NextSuperblockHeight": 5445,
  "NextSuperblockBudget": 1380386,
  "f80ab050ab53459ec937879a046d603e_RAC": 430.07,
  "f80ab050ab53459ec937879a046d603e_TEAM": 15044,
  "f80ab050ab53459ec937879a046d603e_TaskWeight": 100,
  "f80ab050ab53459ec937879a046d603e_UTXOWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_RAC": 441.45,
  "71f1f1f46deb2f25961c7d9af06f2b31_TEAM": 15044,
  "71f1f1f46deb2f25961c7d9af06f2b31_TaskWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_UTXOWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_RAC": 446.56,
  "cc37d0ef74a621379974484f43d3b1c5_TEAM": 15044,
  "cc37d0ef74a621379974484f43d3b1c5_TaskWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_UTXOWeight": 100,
  "95a79cd5829e8315b0b946709930df18_RAC": 407.91,
  "95a79cd5829e8315b0b946709930df18_TEAM": 15044,
  "95a79cd5829e8315b0b946709930df18_TaskWeight": 100,
  "95a79cd5829e8315b0b946709930df18_UTXOWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 557.48,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 2283.47,
  "Total Payments (One Day)": 223900,
  "Total Payments (One Week)": 2028581,
  "Total Budget (One Day)": 5521544,
  "Total Budget (One Week)": 49693896,
  "Superblock Count (One Week)": 50,
  "Superblock Hit Count (One Week)": 36,
  "Superblock List": "5346,5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,
2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5346,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 40.82153268884372
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 02:50:30 pm
Code: [Select]
./biblepay-cli getinfo
{
  "version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 17470827.03959162,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 5347,
  "timeoffset": 0,
  "connections": 9,
  "proxy": "",
  "difficulty": 0.21511500044313,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422036,
  "NextSuperblockHeight": 5445,
  "NextSuperblockBudget": 1380386,
  "93138f032bdd027fa3246b48bb715a77_RAC": 7229.4,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 7229.4,
  "Total Payments (One Day)": 725112,
  "Total Payments (One Week)": 15047816,
  "Total Budget (One Day)": 5521544,
  "Total Budget (One Week)": 49693896,
  "Superblock Count (One Week)": 50,
  "Superblock Hit Count (One Week)": 36,
  "Superblock List": "5346,5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5346,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 302.8101479505652
}

Block 5347, looks like my Magnitude went down from 311 to 302

It looks like 9 researchers have joined since the last post, (exec datalist utxoweight) so that is most likely why it dropped - you can also type exec leaderboard, to see what levels were in the last block.

As far as searching for the podc transaction you can look in the tx list in -qt mode.  Or if you can find the right switches you can look for it in listtransactions.   

I dont need it currently so thats ok.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 02:53:04 pm
3 sanctuaries up.

Before block 5346:
Code: [Select]
"version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 9574526.06132864,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 5339,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.2604936799427617,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

Code: [Select]
"Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84",
  "CPIDS": "f80ab050ab53459ec937879a046d603e;71f1f1f46deb2f25961c7d9af06f2b31;cc37d0ef74a621379974484f43d3b1c5;95a79cd5829e8315b0b946709930df18;e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422035,
  "NextSuperblockHeight": 5346,
  "NextSuperblockBudget": 1380386,
  "f80ab050ab53459ec937879a046d603e_RAC": 430.07,
  "f80ab050ab53459ec937879a046d603e_TEAM": 15044,
  "f80ab050ab53459ec937879a046d603e_TaskWeight": 100,
  "f80ab050ab53459ec937879a046d603e_UTXOWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_RAC": 441.45,
  "71f1f1f46deb2f25961c7d9af06f2b31_TEAM": 15044,
  "71f1f1f46deb2f25961c7d9af06f2b31_TaskWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_UTXOWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_RAC": 446.56,
  "cc37d0ef74a621379974484f43d3b1c5_TEAM": 15044,
  "cc37d0ef74a621379974484f43d3b1c5_TaskWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_UTXOWeight": 100,
  "95a79cd5829e8315b0b946709930df18_RAC": 407.91,
  "95a79cd5829e8315b0b946709930df18_TEAM": 15044,
  "95a79cd5829e8315b0b946709930df18_TaskWeight": 100,
  "95a79cd5829e8315b0b946709930df18_UTXOWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 557.48,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 2283.47,
  "Total Payments (One Day)": 223900,
  "Total Payments (One Week)": 2028581,
  "Total Budget (One Day)": 4141158,
  "Total Budget (One Week)": 48313510,
  "Superblock Count (One Week)": 49,
  "Superblock Hit Count (One Week)": 35,
  "Superblock List": "5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5247,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 41.98786219423925

After Block 5346:
Code: [Select]
"version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 9601523.09132864,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 5350,
  "timeoffset": 0,
  "connections": 9,
  "proxy": "",
  "difficulty": 0.1106453170532401,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

Code: [Select]
"Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84",
  "CPIDS": "f80ab050ab53459ec937879a046d603e;71f1f1f46deb2f25961c7d9af06f2b31;cc37d0ef74a621379974484f43d3b1c5;9
5a79cd5829e8315b0b946709930df18;e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422036,
  "NextSuperblockHeight": 5445,
  "NextSuperblockBudget": 1380386,
  "f80ab050ab53459ec937879a046d603e_RAC": 430.07,
  "f80ab050ab53459ec937879a046d603e_TEAM": 15044,
  "f80ab050ab53459ec937879a046d603e_TaskWeight": 100,
  "f80ab050ab53459ec937879a046d603e_UTXOWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_RAC": 441.45,
  "71f1f1f46deb2f25961c7d9af06f2b31_TEAM": 15044,
  "71f1f1f46deb2f25961c7d9af06f2b31_TaskWeight": 100,
  "71f1f1f46deb2f25961c7d9af06f2b31_UTXOWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_RAC": 446.56,
  "cc37d0ef74a621379974484f43d3b1c5_TEAM": 15044,
  "cc37d0ef74a621379974484f43d3b1c5_TaskWeight": 100,
  "cc37d0ef74a621379974484f43d3b1c5_UTXOWeight": 100,
  "95a79cd5829e8315b0b946709930df18_RAC": 407.91,
  "95a79cd5829e8315b0b946709930df18_TEAM": 15044,
  "95a79cd5829e8315b0b946709930df18_TaskWeight": 100,
  "95a79cd5829e8315b0b946709930df18_UTXOWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 557.48,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 2283.47,
  "Total Payments (One Day)": 223900,
  "Total Payments (One Week)": 2028581,
  "Total Budget (One Day)": 5521544,
  "Total Budget (One Week)": 49693896,
  "Superblock Count (One Week)": 50,
  "Superblock Hit Count (One Week)": 36,
  "Superblock List": "5346,5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,
2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 5346,
  "Last Superblock Budget": 1380386,
  "Last Superblock Payment": 0,
  "Magnitude": 40.82153268884372

Great, well so far everything looks OK but I just remembered something important:
When we vote on the contract for 5346, that vote actually reflected the state the contract was in Before 5346, because the sancs download and process based on rules *prior* to the superblock.  We should see more accurate changes in utxo weight and taskweight in the *next* superblock, now that Mikes sancs will be voting along with mine using the current rulesets.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 02:55:44 pm
So assuming this system is reliable and for 30 days we see 100% taskweight and utxo weight for the average researcher, do you like the feature, IE will this raise the integrity of PODC up to the accepted levels and be a killer feature?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 22, 2018, 03:01:59 pm
Hi Rob, please I have UTXOWeight 75:
"6785ded1f65063ef8f01f42deb31cf1d_UTXOWeight": 75,

I have balance over 1M tBBP but have not sanctuary , only wallet.

It is a problem ?

Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 22, 2018, 03:07:22 pm
And have same question like jaapgvk.
****
One (minor) thing: the 'setgenerate 1' option makes the wallet hash at the old speed again (not 1%) on both the linux and windows wallets. I think it was also the case with the previous version.
So, to be clear: with the current wallet, when I do 'setgenerate 1 true', on my quadcore 4 thread system, I'm using about 25% of my CPU.
****
I am on linux and last two versions are back on 1 full thread (1.0.9.2 was 1% of all processor).

Thank and excuse my english. I beleve that you understand my question :).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 22, 2018, 03:08:20 pm
So assuming this system is reliable and for 30 days we see 100% taskweight and utxo weight for the average researcher, do you like the feature, IE will this raise the integrity of PODC up to the accepted levels and be a killer feature?

I think it is much improved, great job.

For the task weight, is it calculated from invalid tasks like the one's we can see on the Rosetta website? And the uxto is purely on the amount of BBP available in the wallet correct?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 22, 2018, 03:52:00 pm
Rob, when does it change??
  "04fba56d89a5eb38b1b82f8a6240132c_TaskWeight": 0,
  "04fba56d89a5eb38b1b82f8a6240132c_UTXOWeight": 0,
On starting new task, or on the end?
And second T-mike's question... how it is Task Integrity calculated?

oh.. EDIT :) when i will be "mine" only on rosetta without online master wallet I will be DR level 3?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 22, 2018, 04:12:18 pm
Rob, when does it change??
  "04fba56d89a5eb38b1b82f8a6240132c_TaskWeight": 0,
  "04fba56d89a5eb38b1b82f8a6240132c_UTXOWeight": 0,
On starting new task, or on the end?
And second T-mike's question... how it is Task Integrity calculated?

oh.. EDIT :) when i will be "mine" only on rosetta without online master wallet I will be DR level 3?

No, the levels are for disaster recovery, like when Rosetta goes down or if there is a problem with the validation modules.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 04:30:44 pm
Hi Rob, please I have UTXOWeight 75:
"6785ded1f65063ef8f01f42deb31cf1d_UTXOWeight": 75,

I have balance over 1M tBBP but have not sanctuary , only wallet.

It is a problem ?

Thanks.

The 75 for utxoweight means it only staked at level 4 on the chart. So it only allocated say, 40K bbp in your coinstake.
You can fix this in prod by adding: polpercentage=50 in your bbp config file, or just wait and see if things improve on the next PODCUpdate tx.

You'd have to go to your PODCUpdate tx and look at what it spent (double click it in biblepay-qt).  Maybe you have some funds locked.  It used .05% currently by default.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 04:36:09 pm
I think it is much improved, great job.

For the task weight, is it calculated from invalid tasks like the one's we can see on the Rosetta website? And the uxto is purely on the amount of BBP available in the wallet correct?
The UTXO weight is very similar to POS, where the wallet tries to spend 5% of your balance back to you in a coinstake, and that amount is used for the UTXOweight.  You can raise it with polpercentage=60 for example.

The task integrity is assessed by the sanctuary iterating through all your reported tasks, and comparing the timestamp information for each task with Rosettas XML report for its (live in real time) timestamp info.  With the goal of being to detect any WU tampering.  We do not dock you for an invalid task solved out of your TaskWeight, but in that case you dont get paid any RAC at all for that task, we actually only dock you if your purported timestamps disagree with Rosettas timestamps on a given WU, or if your WU is not reported to the Sanc and you solve it and ask for credit.  This is designed to allow us to assess if you are indeed working on the task(s) you say you are working on and they match.  The RAC reward comes separately after the task(s) are completed, validated and assigned credit, Then the final magnitude calc is : Integrity * RAC * UTXOWeight = Magnitude.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 04:39:18 pm
Rob, when does it change??
  "04fba56d89a5eb38b1b82f8a6240132c_TaskWeight": 0,
  "04fba56d89a5eb38b1b82f8a6240132c_UTXOWeight": 0,
On starting new task, or on the end?
And second T-mike's question... how it is Task Integrity calculated?

oh.. EDIT :) when i will be "mine" only on rosetta without online master wallet I will be DR level 3?

You can force it with exec podcupdate, or just wait 24 hours and lets see if everything works correctly.
If you are using 'setgenerate true=1' (or higher) it should be sending a podcupdate within 8 hours.

Ive got to head out, Ill be back in about 4 hours.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 22, 2018, 04:42:34 pm
You can force it with exec podcupdate, or just wait 24 hours and lets see if everything works correctly.
If you are using 'setgenerate true=1' (or higher) it should be sending a podcupdate within 8 hours.

Ive got to head out, Ill be back in about 4 hours.
Ok. thanks. And the wallet must be unlocked?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 04:47:11 pm
Windows 1.0.9.4b is out there, if anyone wants to test on windows.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: ischindl on February 22, 2018, 04:53:57 pm
The 75 for utxoweight means it only staked at level 4 on the chart. So it only allocated say, 40K bbp in your coinstake.
You can fix this in prod by adding: polpercentage=50 in your bbp config file, or just wait and see if things improve on the next PODCUpdate tx.

You'd have to go to your PODCUpdate tx and look at what it spent (double click it in biblepay-qt).  Maybe you have some funds locked.  It used .05% currently by default.

Thanks Rob, it is ok, now I understand.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 22, 2018, 05:29:06 pm
For some reason I'm not showing on the R@h leaderboard on the pool, but I show on the R@h website as being in the group.

Also, is there a way to see all the commands you can do with the exec in regards to the wallet?  I'd be happy to test them but need a masterlist
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 22, 2018, 06:41:27 pm
The UTXO weight is very similar to POS, where the wallet tries to spend 5% of your balance back to you in a coinstake, and that amount is used for the UTXOweight.  You can raise it with polpercentage=60 for example.

The task integrity is assessed by the sanctuary iterating through all your reported tasks, and comparing the timestamp information for each task with Rosettas XML report for its (live in real time) timestamp info.  With the goal of being to detect any WU tampering.  We do not dock you for an invalid task solved out of your TaskWeight, but in that case you dont get paid any RAC at all for that task, we actually only dock you if your purported timestamps disagree with Rosettas timestamps on a given WU, or if your WU is not reported to the Sanc and you solve it and ask for credit.  This is designed to allow us to assess if you are indeed working on the task(s) you say you are working on and they match.  The RAC reward comes separately after the task(s) are completed, validated and assigned credit, Then the final magnitude calc is : Integrity * RAC * UTXOWeight = Magnitude.

The XML report is the one you obtain the RAC from correct? Where does the task information come from?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 08:49:24 pm
The XML report is the one you obtain the RAC from correct? Where does the task information come from?
Here is an example of how the sanctuary verifies work units from the xml file:
https://boinc.bakerlab.org/rosetta/result_status.php?ids=976055122,975055123,975055124,975055125,975055126,975055127,975055128,975055129,975055129,975055129

The task info is sent from the controller wallet into the block chain as a PODC Transaction.

For RAC, we actually get that out of the daily rosetta userbase file (its 389 megs per day).  If you go to your Sanctuary SAN directory you can see the "üser" file there.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 22, 2018, 09:04:07 pm
Here is an example of how the sanctuary verifies work units from the xml file:
https://boinc.bakerlab.org/rosetta/result_status.php?ids=976055122,975055123,975055124,975055125,975055126,975055127,975055128,975055129,975055129,975055129

The task info is sent from the controller wallet into the block chain as a PODC Transaction.

For RAC, we actually get that out of the daily rosetta userbase file (its 389 megs per day).  If you go to your Sanctuary SAN directory you can see the "üser" file there.

Rob, sorry, I'm still having difficulty understanding. I see the xml file, can you show exactly what your comparing? (I know it's the timestamp but which one to which one?)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 09:13:53 pm
For some reason I'm not showing on the R@h leaderboard on the pool, but I show on the R@h website as being in the group.

Also, is there a way to see all the commands you can do with the exec in regards to the wallet?  I'd be happy to test them but need a masterlist

Alright, your in there now.  It looks like the pool couldnt handle one of the values, now its programmed in.

As far as the exec command, finding a list of them, no there is currently no documentation, other than the wiki page.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 09:19:30 pm
Rob, sorry, I'm still having difficulty understanding. I see the xml file, can you show exactly what your comparing? (I know it's the timestamp but which one to which one?)
For example, if your first machine is running 10 tasks, and lets say WU 98651 was started at unix time 15345321, then your controller wallet will ask what time did that task start, once it receives 15345321 it will send that into the chain as a PODC update (along with a list of every other task it is working and timestamps to save size).  (It queries the timestamps from the Rosetta task themselves, not from the XML file). Then the Sanctuary will compare the XML sent_time, to that timestamp to ensure they agree.  This way if someone on the Rosetta side were to mass validate tasks or alter timestamps, or insert random records in the table to try to get someone paid, those may fail (if we catch one of the circumstances) - because we would have already sent our timestamps into our chain before the alteration.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 22, 2018, 09:24:26 pm
Ok. thanks. And the wallet must be unlocked?

Yes, since we are not POS, I suppose we would need to program some things in to "unlock for staking only" etc, but for now, yes it has to be unlocked for PODC updates as not only is it sending you a coinstake with UTXO in it, but there is a transaction fee in that transaction for the Task Transmission.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 22, 2018, 09:30:09 pm
For example, if your first machine is running 10 tasks, and lets say WU 98651 was started at unix time 15345321, then your controller wallet will ask what time did that task start, once it receives 15345321 it will send that into the chain as a PODC update (along with a list of every other task it is working and timestamps to save size).  (It queries the timestamps from the Rosetta task themselves, not from the XML file). Then the Sanctuary will compare the XML sent_time, to that timestamp to ensure they agree.  This way if someone on the Rosetta side were to mass validate tasks or alter timestamps, or insert random records in the table to try to get someone paid, those would fail because we would have already sent our timestamps into our chain before the alteration.

Oh...I understand now. That's a great idea!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 23, 2018, 02:05:57 am
And have same question like jaapgvk.
****
One (minor) thing: the 'setgenerate 1' option makes the wallet hash at the old speed again (not 1%) on both the linux and windows wallets. I think it was also the case with the previous version.
So, to be clear: with the current wallet, when I do 'setgenerate 1 true', on my quadcore 4 thread system, I'm using about 25% of my CPU.
****
I am on linux and last two versions are back on 1 full thread (1.0.9.2 was 1% of all processor).

Thank and excuse my english. I beleve that you understand my question :).

Yeah, I'm using the latest wallet and BOINC on my windows pc now. But I can't mine and use BOINC at the same time, because the wallet will use too much of the cpu-cycles and BOINC stops processing.

I don't know how to tweak the settings so that I can use both.

That also brings me to an other question about poor people all over the world using their phone to mine BBP (which I think will be a great application for Biblepay). How would one go about this? Would one person have a wallet running somewhere 24/7, and other people (with phones and tablets) would be running BOINC, and the person with the wallet would divide the collected BBP? Just thinking out loud.

Because I always liked the idea of 'one-click-mining', especially in combination with mobile phones and tablets, because even though - for example - a lot of people in Afrika are poor, a lót of them have a phone (although I don't know how many have smartphones).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 03:27:22 am
Yes, since we are not POS, I suppose we would need to program some things in to "unlock for staking only" etc, but for now, yes it has to be unlocked for PODC updates as not only is it sending you a coinstake with UTXO in it, but there is a transaction fee in that transaction for the Task Transmission.
So, that was my problem. It is a must-have to have option "unlock for PoDC only".
I am afraid to have my wallet on 24/7 server and if it should be unlocked it is even worst :)
Now I ordered VPS for testnet, but I am worried to unlock my wallet with command line. Ok there is option to delete bash history, but :)
It is possible to implement function "unlock for PoDC only" to options, or even better will be unlocked for PoDC everytime?
EDIT: maybe option "unlock for PoDC" may unlock wallet for PoDC without need to write password and run setgenerate true 1 automatically.

Next question :) Do I understand it correctly, that for now is 24/7 control wallet must-have even for mobile phone?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 03:38:55 am
Yeah, I'm using the latest wallet and BOINC on my windows pc now. But I can't mine and use BOINC at the same time, because the wallet will use too much of the cpu-cycles and BOINC stops processing.

I don't know how to tweak the settings so that I can use both.

That also brings me to an other question about poor people all over the world using their phone to mine BBP (which I think will be a great application for Biblepay). How would one go about this? Would one person have a wallet running somewhere 24/7, and other people (with phones and tablets) would be running BOINC, and the person with the wallet would divide the collected BBP? Just thinking out loud.

Because I always liked the idea of 'one-click-mining', especially in combination with mobile phones and tablets, because even though - for example - a lot of people in Afrika are poor, a lót of them have a phone (although I don't know how many have smartphones).
Hi.
I was fighting with this too :)
I have ordered "weak" linux based VPS for 24/7 wallet but I wanted to run boinc there too.
So, my solution is: run biblepay with setgenerate true 1. Of course it consumes more than 90% of CPU :) so rosetta won't work. But than I install "cpulimit" (apt-get install cpulimit). It is very useful for this. Than you can usse it with command like this: "cpulimit -b -l 15 -m -p 1607" what means allow PID nr 1607 to spend max 15% of CPU. After this my BBP process consumes 15-20% of CPU and rosetta eats rest to 100 ;)

And shared wallet was of my thought too. What about creating some Rosetta/BBP pool? Rob will it be possible to change pool to handle this?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 07:22:25 am
Yeah, I'm using the latest wallet and BOINC on my windows pc now. But I can't mine and use BOINC at the same time, because the wallet will use too much of the cpu-cycles and BOINC stops processing.

I don't know how to tweak the settings so that I can use both.

That also brings me to an other question about poor people all over the world using their phone to mine BBP (which I think will be a great application for Biblepay). How would one go about this? Would one person have a wallet running somewhere 24/7, and other people (with phones and tablets) would be running BOINC, and the person with the wallet would divide the collected BBP? Just thinking out loud.

Because I always liked the idea of 'one-click-mining', especially in combination with mobile phones and tablets, because even though - for example - a lot of people in Afrika are poor, a lót of them have a phone (although I don't know how many have smartphones).

Are you using Windows or Linux? In Advanced View->Options->Usage Limits of BOINC Manager you can set the usage for BOINC. I think Rob can fix the wallet to mine less but it's ok for for now. You can also use Oribs's method to limit the cpu usage on linux.

You can also try this for windows: http://mion.faireal.net/BES/

I wouldn't worry about it too much though, Rob will most likely fix it in the next update.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 07:27:53 am
Hi.
I was fighting with this too :)
I have ordered "weak" linux based VPS for 24/7 wallet but I wanted to run boinc there too.
So, my solution is: run biblepay with setgenerate true 1. Of course it consumes more than 90% of CPU :) so rosetta won't work. But than I install "cpulimit" (apt-get install cpulimit). It is very useful for this. Than you can usse it with command like this: "cpulimit -b -l 15 -m -p 1607" what means allow PID nr 1607 to spend max 15% of CPU. After this my BBP process consumes 15-20% of CPU and rosetta eats rest to 100 ;)

And shared wallet was of my thought too. What about creating some Rosetta/BBP pool? Rob will it be possible to change pool to handle this?

In testnet we use what's call hot sanctuaries where the controller wallet is on the same machine as the Sanctuary. Once in production, you should really have you wallet on your home computer, never run your wallet on the VPS!

@Rob: I think we will need something like the gridcoin pool for mobile devices or have it in the code if it sees an arm processor to drop the UXTO validation. But then I would check to see if more than 10 arm processors are coming from the same IP to stop people from abusing the lowered requirements.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 08:24:18 am
Hi.
I was fighting with this too :)
I have ordered "weak" linux based VPS for 24/7 wallet but I wanted to run boinc there too.
So, my solution is: run biblepay with setgenerate true 1. Of course it consumes more than 90% of CPU :) so rosetta won't work. But than I install "cpulimit" (apt-get install cpulimit). It is very useful for this. Than you can usse it with command like this: "cpulimit -b -l 15 -m -p 1607" what means allow PID nr 1607 to spend max 15% of CPU. After this my BBP process consumes 15-20% of CPU and rosetta eats rest to 100 ;)

And shared wallet was of my thought too. What about creating some Rosetta/BBP pool? Rob will it be possible to change pool to handle this?

We dont need a pool, because the boinc infrastructure is already pooling the RAC for us. 

Id rather simplify the infrastructure than make it more complicated.

Regarding the Gridcoin pool that T-mike mentioned, they have a pool because they dont have enough blocks per day to pay the researchers.  We dont need a pool, because we airdrop the payment once per day.

Regarding mobile devices, we may be able to add a feature to not require PODC updates on tablets and smartphones - but thats still in the wish list - I have not looked at that yet.

Jaap, regarding one thread using too much power, I already made it sleep 200ms between iterations, it could be that you are running this on a low power machine, I suppose I can put in more granular control over this to see if this can be improved.  Right now on my windows dev machine, Im running rosetta 6 tasks : taking 50% of the cpu, the plain vanilla biblepay on 1 thread is taking 13% of the cpu, and its hashing at 270hps in testnet.  So of course we have to consider the fact that we *do* want it hashing on 1 thread so we have a baseline level of average security.  But nevertheless, Ill add a setting to see if we can control the sleep better, and, have it actually attempt to sleep more often - there is also something that I need to look at for the miner process as far as CPU priority - it might be set to high and not normal, meaning that on certain machines its not listening to your wishes, ill check into all that today.

I think what will end up with the regular pool, is I have no intention on taking it down - I still want to make it a place for "Biblepay Central", for Reports, for Orphan related letter writing and functions, but the heat-mining pool might be removed.  If we keep compatibility with the heat mining side, which I believe we have done so far, I may let it run and see what kind of interest we have and what the numbers look like, but most likely with everyone running on one thread, it wont be necessary to have a pool for heat mining and I may end up shutting that feature down.

At that point we would be fully Rosetta decentralized, with no pools. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 08:37:22 am
We dont need a pool, because the boinc infrastructure is already pooling the RAC for us. 

Id rather simplify the infrastructure than make it more complicated.

Regarding the Gridcoin pool that T-mike mentioned, they have a pool because they dont have enough blocks per day to pay the researchers.  We dont need a pool, because we airdrop the payment once per day.

Regarding mobile devices, we may be able to add a feature to not require PODC updates on tablets and smartphones - but thats still in the wish list - I have not looked at that yet.

Jaap, regarding one thread using too much power, I already made it sleep 200ms between iterations, it could be that you are running this on a low power machine, I suppose I can put in more granular control over this to see if this can be improved.  Right now on my windows dev machine, Im running rosetta 6 tasks : taking 50% of the cpu, the plain vanilla biblepay on 1 thread is taking 13% of the cpu, and its hashing at 270hps in testnet.  So of course we have to consider the fact that we *do* want it hashing on 1 thread so we have a baseline level of average security.  But nevertheless, Ill add a setting to see if we can control the sleep better, and, have it actually attempt to sleep more often - there is also something that I need to look at for the miner process as far as CPU priority - it might be set to high and not normal, meaning that on certain machines its not listening to your wishes, ill check into all that today.

I think what will end up with the regular pool, is I have no intention on taking it down - I still want to make it a place for "Biblepay Central", for Reports, for Orphan related letter writing and functions, but the heat-mining pool might be removed.  If we keep compatibility with the heat mining side, which I believe we have done so far, I may let it run and see what kind of interest we have and what the numbers look like, but most likely with everyone running on one thread, it wont be necessary to have a pool for heat mining and I may end up shutting that feature down.

At that point we would be fully Rosetta decentralized, with no pools.

I mainly mentioned the pool because it allows you to perform DC without having to stake, in our case it allows you to not need a controller wallet on 24/7. But if you can exclude the UXTO validation for phones and tablets that would work too.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 23, 2018, 08:48:01 am
We dont need a pool, because the boinc infrastructure is already pooling the RAC for us. 

Jaap, regarding one thread using too much power, I already made it sleep 200ms between iterations, it could be that you are running this on a low power machine, I suppose I can put in more granular control over this to see if this can be improved.  Right now on my windows dev machine, Im running rosetta 6 tasks : taking 50% of the cpu, the plain vanilla biblepay on 1 thread is taking 13% of the cpu, and its hashing at 270hps in testnet.  So of course we have to consider the fact that we *do* want it hashing on 1 thread so we have a baseline level of average security.  But nevertheless, Ill add a setting to see if we can control the sleep better, and, have it actually attempt to sleep more often - there is also something that I need to look at for the miner process as far as CPU priority - it might be set to high and not normal, meaning that on certain machines its not listening to your wishes, ill check into all that today.


Well, it's an AMD Phenom II machine. 4 cores and 4 threads. What I've done for now, is allocate 3 cores to BOINC and 1 core to the wallet (which is mining with 1 thread now (+-250hps), with low priority).
Now both can run at the same time.

It's interesting to read that your Rosetta tasks take up 50% of your cpu power. With my PC (if I don't allocate cores), it just goes up to 100%, and I don't know how to lower that (is there a way to configure the amount of tasks that you do?).

I fired up Rosetta on a second PC (also AMD 4-core, 4-thread), and there Rosetta also takes up 100% of the CPU power.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 09:23:28 am
Well, it's an AMD Phenom II machine. 4 cores and 4 threads. What I've done for now, is allocate 3 cores to BOINC and 1 core to the wallet (which is mining with 1 thread now (+-250hps), with low priority).
Now both can run at the same time.

It's interesting to read that your Rosetta tasks take up 50% of your cpu power. With my PC (if I don't allocate cores), it just goes up to 100%, and I don't know how to lower that (is there a way to configure the amount of tasks that you do?).

I fired up Rosetta on a second PC (also AMD 4-core, 4-thread), and there Rosetta also takes up 100% of the CPU power.

You can lower the number of tasks by limiting the amount of RAM used in the settings. Or you can just reduce the CPU time setting.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 09:34:20 am
Well, it's an AMD Phenom II machine. 4 cores and 4 threads. What I've done for now, is allocate 3 cores to BOINC and 1 core to the wallet (which is mining with 1 thread now (+-250hps), with low priority).
Now both can run at the same time.

It's interesting to read that your Rosetta tasks take up 50% of your cpu power. With my PC (if I don't allocate cores), it just goes up to 100%, and I don't know how to lower that (is there a way to configure the amount of tasks that you do?).

I fired up Rosetta on a second PC (also AMD 4-core, 4-thread), and there Rosetta also takes up 100% of the CPU power.

Oh ok thats good to know.  Just wanted to know we werent dealing with a one core VPS where the root issue could have been even the base biblepay wallet would be consuming more than 10% LOL, good to know.
Well in the case of my dev machine, I went into boincs GUI preferences and limited CPU use to no more than 50%, and I also have it shutting boinc off when "computer is in use" as this machine has 40 things going on.

So, yes, I will definitely be looking at this thread priority and tailorization today.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 23, 2018, 09:36:34 am
You can lower the number of tasks by limiting the amount of RAM used in the settings. Or you can just reduce the CPU time setting.

Oh, thx! I didn't understand the 'CPU time' option. It indeed does what I was looking for. I'm also going to look for the RAM limiting option.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 09:39:40 am
I mainly mentioned the pool because it allows you to perform DC without having to stake, in our case it allows you to not need a controller wallet on 24/7. But if you can exclude the UXTO validation for phones and tablets that would work too.

Yeah, no one realizes this but the feature to allow mass payments in biblepay for 32767 researchers in one airdrop per day is actually a *major* feature.  No one has that.  So Id rather leverage it than lose it.

But yes I hear you, but lets remember the UTXO feature itself, the staking requirement raises PODC up to at least the integrity level of POS coins, and I think that could be major when people start to figure it out.

I understand from the convenience perspective, it would be nice to make this a sleek black box and leave the controller off.  But lets also not forget the controller will also provide a base level of security for POBH block checking (POW heat mining) so thats a major benefit for us as a stable backbone globally.  If we were to be considered a true payment system, it would pay off for us in a healthy way, because we could tell our potential partners we have a backbone of 10,000 PCs always on - as full nodes for block processing.

But yes, I really want the unbanked and the small tiny 3rd world phone to be able to use biblepay!  So that will also be a priority today, I will check into that today along with the threading.

As far as abuse of the system, Im pretty sure what we will have to do is add a checkbox to the association page and mark the CPID as "phone/tablet" only.  And then the sanc will check that CPIDs machines before it pays the RAC, and if they lied about it they get 0 reward.  If they really only have devices that match the processor type (ARM or whatever) and none are PCs, the RAC is induced into the superblock.  It adds yet one more complexity to biblepay, but I think its a good complexity.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 09:40:57 am
Oh, thx! I didn't understand the 'CPU time' option. It indeed does what I was looking for. I'm also going to look for the RAM limiting option.

Limiting the RAM required estimation. Each task on average is probably 500MB, so if you usually have 4 tasks running and it's taking up 100% of your cpu and you want it to be 50%, then just set the RAM usage to 1GB or so. The setting is in percentage so you'll have to calculate that from the amount of RAM you have.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 09:53:15 am
Yeah, no one realizes this but the feature to allow mass payments in biblepay for 32767 researchers in one airdrop per day is actually a *major* feature.  No one has that.  So Id rather leverage it than lose it.

But yes I hear you, but lets remember the UTXO feature itself, the staking requirement raises PODC up to at least the integrity level of POS coins, and I think that could be major when people start to figure it out.

I understand from the convenience perspective, it would be nice to make this a sleek black box and leave the controller off.  But lets also not forget the controller will also provide a base level of security for POBH block checking (POW heat mining) so thats a major benefit for us as a stable backbone globally.  If we were to be considered a true payment system, it would pay off for us in a healthy way, because we could tell our potential partners we have a backbone of 10,000 PCs always on - as full nodes for block processing.

But yes, I really want the unbanked and the small tiny 3rd world phone to be able to use biblepay!  So that will also be a priority today, I will check into that today along with the threading.

As far as abuse of the system, Im pretty sure what we will have to do is add a checkbox to the association page and mark the CPID as "phone/tablet" only.  And then the sanc will check that CPIDs machines before it pays the RAC, and if they lied about it they get 0 reward.  If they really only have devices that match the processor type (ARM or whatever) and none are PCs, the RAC is induced into the superblock.  It adds yet one more complexity to biblepay, but I think its a good complexity.

Would it be more transparent if the Sanc just looks the CPID up to see if it's an arm processor?

By the way, I started on the research assignment and right now I'm trying to figure out how much you can make with your phone per day. I think we might have to have a certain percentage of the block reward to be allocated to cellphones for it to be profitably for them. (So they have enough to buy bread.)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 10:15:55 am
Would it be more transparent if the Sanc just looks the CPID up to see if it's an arm processor?

By the way, I started on the research assignment and right now I'm trying to figure out how much you can make with your phone per day. I think we might have to have a certain percentage of the block reward to be allocated to cellphones for it to be profitably for them. (So they have enough to buy bread.)

As far as efficient: Unfortunately no, as I can pretty much tell you roughly whats going to happen.. LOL, because I watched this train wreck in slow motion before LOL.  Basically when we go live, we'll have about 100 CPIDs kick in the first week, then 400 by the end of the month, then about 2000 or so within 6 months.  When we hit 2000, that means the Sanc has to iterate through a lot of data once per morning.  So it really needs a checkbox to see if the researcher is "implying" that they are tablet only.  This way it only has to check the machines if it has to.  I dont want the sanc to have to do one hour of work each morning and freeze up, if it can do 10 minutes of work.  The other thing is remember, some researchers will have 75 machines attached to a cpid. So it has to loop through a lot of devices to come to a binary 1:0 conclusion.

As far as allocating funds for tablets, I dont really want to - as it will be a fallacy to try to believe that arm or a certain processor type is worth "more" per cobbleston than the rest of the system (IE they will get arbitraged to a certain value) that value is usually power related.  I think what happens is the compensation ends up being $20 per month for the amount of energy required to run a PC for 30 days, and that equates to say 1000 RAC in rosetta (at a constant state).  If the phone can do 100 RAC, then thats $2 per month for the phone, no matter what we do.  So yes the phone has to be crunching constantly to buy one loaf of bread once per month, its a sad state of affairs but you know thats pretty good for something you didnt have to do hard labor for.  Otoh, there will come a time - God willing - where our forward value may be Massively higher than we are worth - where someone will pay 20* the current rate for one BBP.  If that day comes, the phone will temporarily make $40 per month and can buy food for the whole family.  It depends on if we can higher 7 devs, and go through the stratis phase as well, if we can pull that off this can be a reality for a long, long time.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 10:23:34 am
As far as efficient: Unfortunately no, as I can pretty much tell you roughly whats going to happen.. LOL, because I watched this train wreck in slow motion before LOL.  Basically when we go live, we'll have about 100 CPIDs kick in the first week, then 400 by the end of the month, then about 2000 or so within 6 months.  When we hit 2000, that means the Sanc has to iterate through a lot of data once per morning.  So it really needs a checkbox to see if the researcher is "implying" that they are tablet only.  This way it only has to check the machines if it has to.  I dont want the sanc to have to do one hour of work each morning and freeze up, if it can do 10 minutes of work.  The other thing is remember, some researchers will have 75 machines attached to a cpid. So it has to loop through a lot of devices to come to a binary 1:0 conclusion.

As far as allocating funds for tablets, I dont really want to - as it will be a fallacy to try to believe that arm or a certain processor type is worth "more" per cobbleston than the rest of the system (IE they will get arbitraged to a certain value) that value is usually power related.  I think what happens is the compensation ends up being $20 per month for the amount of energy required to run a PC for 30 days, and that equates to say 1000 RAC in rosetta (at a constant state).  If the phone can do 100 RAC, then thats $2 per month for the phone, no matter what we do.  So yes the phone has to be crunching constantly to buy one loaf of bread once per month, its a sad state of affairs but you know thats pretty good for something you didnt have to do hard labor for.  Otoh, there will come a time - God willing - where our forward value may be Massively higher than we are worth - where someone will pay 20* the current rate for one BBP.  If that day comes, the phone will temporarily make $40 per month and can buy food for the whole family.  It depends on if we can higher 7 devs, and go through the stratis phase as well, if we can pull that off this can be a reality for a long, long time.

I see, I think the checkbox solution would be better then. I'll keep researching.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 10:32:23 am
I see, I think the checkbox solution would be better then. I'll keep researching.

So I think it is possible to welcome and love the unbanked and cells and tablets, if you log in to the pool, and look at the rosetta leaderboard machine view, I see that I can determine Which CPIDs are 100% tablets or phones by querying the Processor field per CPID (IE If the processor contains "ÄRM" and all processors are ARM then this is an unbanked CPID).  . .   So that is good, EXCEPT, one processor on the list: Rastiks.

Rastiks I see your machine right above your other ARM has 1.9GB ram and a BLANK for the processor.  What machine is that?

So far that is my assumption, we can mark CPIDs who are associated in biblepay as "ARM" only if they only have ARM devices, and those CPIDs do not need to stake UTXOs and do not need to have TaskWeight audited  they just receive 1*RAC = Magnitude, automatically.  Which makes it nice and easy for them - they basically need a PC with a controller wallet Once to set it up, then they dont need to leave their controller wallet on either.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 10:39:36 am
So I think it is possible to welcome and love the unbanked and cells and tablets, if you log in to the pool, and look at the rosetta leaderboard machine view, I see that I can determine Which CPIDs are 100% tablets or phones by querying the Processor field per CPID (IE If the processor contains "ÄRM" and all processors are ARM then this is an unbanked CPID).  . .   So that is good, EXCEPT, one processor on the list: Rastiks.

Rastiks I see your machine right above your other ARM has 1.9GB ram and a BLANK for the processor.  What machine is that?

So far that is my assumption, we can mark CPIDs who are associated in biblepay as "ARM" only if they only have ARM devices, and those CPIDs do not need to stake UTXOs and do not need to have TaskWeight audited  they just receive 1*RAC = Magnitude, automatically.  Which makes it nice and easy for them - they basically need a PC with a controller wallet Once to set it up, then they dont need to leave their controller wallet on either.

Yes, I think you can white list the ARM devices. In the future we can add one more check to fail any ARM processors having more then a certain amount of RAC. Actually, maybe we can just have an average ARM RAC counter and if anyone exceeds that by 20% it fails. That way as technology improves the threshold is automatically raised.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 11:41:38 am
Yes, I think you can white list the ARM devices. In the future we can add one more check to fail any ARM processors having more then a certain amount of RAC. Actually, maybe we can just have an average ARM RAC counter and if anyone exceeds that by 20% it fails. That way as technology improves the threshold is automatically raised.

Yeah, I think this is potentially resolved now but let me go over the feature now.
I think we can have the Sanctuary pull the unbanked report in the morning before it processes the RAC from its user file.

Please click on the unbanked report in the pool - its under Reports | Rosetta Unbanked report.

This thing pulls the Non-Arm RAC vs the ARM Rac for CPIDs who have ARM Rac > 0.

So what I think we can do is filter this report in the mornings , while its processing its User file, to find CPIDs who have LESS than 15 NonArm Rac, and Arm RAC > 0 into a little list of Ünbanked CPIDs.  So in this case, Rastiks is the Only one who would qualify as of today.

Rastiks Rosetta ID is connected to a certain CPID, that CPIDs RAC would be pulled in with no questions - everyone else would not be included. 


Now Im going to work on the Sanctuary side to see if I can make that rule.  Still looking into the Miner threadings.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 12:09:24 pm
Would it be more transparent if the Sanc just looks the CPID up to see if it's an arm processor?

By the way, I started on the research assignment and right now I'm trying to figure out how much you can make with your phone per day. I think we might have to have a certain percentage of the block reward to be allocated to cellphones for it to be profitably for them. (So they have enough to buy bread.)
Hi Mike, I'm testing my phones/tablets too :)
Like I wrote earlier my Nexus 4 is doing very well: https://boincstats.com/en/stats/-1/host/detail/333426255/lastDays
It is interresting, that old Nexus 4 is doing better than my Galaxy S7.
I don't know why. N4 runs on 2 of 4 cores. S7 4 of 8 cores, but when I look at completed tasks Nexus 4 has avg task run time 14500 sec and CPU time 14500, but S7 has avg run time 14500, but only 7000 CPU time. And the reward is only 1/2 from N4 too. Now I'm testing S7 only on 2 cores, so we will see. Difference is, that N4 is "mining" 24/7 and S7 is my primary phone, so it runs boinc mainly on night. I've tested 3 others tablets/phones. One intel based tablet wasn't compatible with rosetta. One old LG phone was compatible ARM based, but all tasks was denied (don't know why). And one old ARM based tablet was running fine, but with very small rewards.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 12:12:22 pm
In testnet we use what's call hot sanctuaries where the controller wallet is on the same machine as the Sanctuary. Once in production, you should really have you wallet on your home computer, never run your wallet on the VPS!
I have only one notebook PC and it is not possible to run it 24/7 that's why i ordered VPS. And that's why I'm aware of running controller wallet. But that's only my situation and my problems :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 12:27:05 pm
Yeah, I think this is potentially resolved now but let me go over the feature now.
I think we can have the Sanctuary pull the unbanked report in the morning before it processes the RAC from its user file.

Please click on the unbanked report in the pool - its under Reports | Rosetta Unbanked report.

This thing pulls the Non-Arm RAC vs the ARM Rac for CPIDs who have ARM Rac > 0.

So what I think we can do is filter this report in the mornings , while its processing its User file, to find CPIDs who have LESS than 15 NonArm Rac, and Arm RAC > 0 into a little list of Ünbanked CPIDs.  So in this case, Rastiks is the Only one who would qualify as of today.

Rastiks Rosetta ID is connected to a certain CPID, that CPIDs RAC would be pulled in with no questions - everyone else would not be included. 
Rob and what about poeple like me, if I have hidden PC's? :)
I have no problem to unhide it, but it's option too and we must count with it.
To the ARM based phones. On Rosettas CPU models page you can see all ARM based CPUs: https://boinc.bakerlab.org/rosetta/cpu_list.php
But what is interesting and like you wrote before some CPUs are not visible.
E.g. my Galaxy S7 has blank CPU model too. And it is arm64 based Exynos 8890 soc with a Quad-Core 2.3 GHz + Quad-Core 1.6 GHz.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 12:54:36 pm
Rob and what about poeple like me, if I have hidden PC's? :)
I have no problem to unhide it, but it's option too and we must count with it.
To the ARM based phones. On Rosettas CPU models page you can see all ARM based CPUs: https://boinc.bakerlab.org/rosetta/cpu_list.php
But what is interesting and like you wrote before some CPUs are not visible.
E.g. my Galaxy S7 has blank CPU model too. And it is arm64 based Exynos 8890 soc with a Quad-Core 2.3 GHz + Quad-Core 1.6 GHz.

I forgot to mention that earlier- if you hide your PCs while you are a member of biblepay, two things go bad for that CPID:
1) The PODCUpdate fails, because it cant figure out what tasks are part of each hostid.  So no UTXOWeight = 0 reward
2) The Sanc will not be able to figure any ARM RAC, so the user would not be able to ever become an Unbanked CPID either

So with those together : Hiding PC's from Biblepay = No Research Reward


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 23, 2018, 01:00:32 pm
Yeah, I think this is potentially resolved now but let me go over the feature now.
I think we can have the Sanctuary pull the unbanked report in the morning before it processes the RAC from its user file.

Please click on the unbanked report in the pool - its under Reports | Rosetta Unbanked report.

This thing pulls the Non-Arm RAC vs the ARM Rac for CPIDs who have ARM Rac > 0.

So what I think we can do is filter this report in the mornings , while its processing its User file, to find CPIDs who have LESS than 15 NonArm Rac, and Arm RAC > 0 into a little list of Ünbanked CPIDs.  So in this case, Rastiks is the Only one who would qualify as of today.

Rastiks Rosetta ID is connected to a certain CPID, that CPIDs RAC would be pulled in with no questions - everyone else would not be included. 

Now Im going to work on the Sanctuary side to see if I can make that rule.  Still looking into the Miner threadings.

I just checked the pool for the 'unbanked report', and I think this is a great way to 'shortlist' the data for the sanctuaries in light of this feature.

Rob, I must say, in the beginning I was not sure about PODC, but the more I'm able to wrap my head around it, the more excited I get! Absolutely marvelous work thus far.

I've also been testing with my daily phone. It only uses one core, and only when it's connected to the charger at night. But still I'm getting pretty nice results (a RAC of around 75).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 01:14:10 pm
I forgot to mention that earlier- if you hide your PCs while you are a member of biblepay, two things go bad for that CPID:
1) The PODCUpdate fails, because it cant figure out what tasks are part of each hostid.  So no UTXOWeight = 0 reward
2) The Sanc will not be able to figure any ARM RAC, so the user would not be able to ever become an Unbanked CPID either

So with those together : Hiding PC's from Biblepay = No Research Reward
That's interesting because my TaskWeight and UTXOWeight are 100.
But i'm going to unhide it :)


Admin EDIT:  But, I forgot to tell you all the fact that I unhid it today!  So maybe it isnt Biblepay, maybe its ME.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:01:57 pm
That's interesting because my TaskWeight and UTXOWeight are 100.
But i'm going to unhide it :)

What is your CPID?  Can you please leave it hidden so I can see what the sancs can see in your account?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:04:43 pm
I just checked the pool for the 'unbanked report', and I think this is a great way to 'shortlist' the data for the sanctuaries in light of this feature.

Rob, I must say, in the beginning I was not sure about PODC, but the more I'm able to wrap my head around it, the more excited I get! Absolutely marvelous work thus far.

I've also been testing with my daily phone. It only uses one core, and only when it's connected to the charger at night. But still I'm getting pretty nice results (a RAC of around 75).

Thanks, yeah I think if we can have a few months of consecutive uptime (98% + reliability) we will have something here, God willing.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 02:06:58 pm
What is your CPID?  Can you please leave it hidden so I can see what the sancs can see in your account?
I'm sorry, but they're unhidened right now.
My CPID is 04fba56d89a5eb38b1b82f8a6240132c
Should I hide it again?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:08:58 pm
I'm sorry, but they're unhidened right now.
My CPID is 04fba56d89a5eb38b1b82f8a6240132c
Should I hide it again?

Yeah can you hide them now? Ill write some commands that force it to show me what we can see.

Let me know when hidden.

Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 02:11:58 pm
Yeah can you hide them now? Ill write some commands that force it to show me what we can see.

Let me know when hidden.

Thanks.
OK. Hidden.
But now I was thinking about that and I unhide it for few hours yesterday because my podc wasn't work (that with locked wallet) and this was for test if it helps.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:16:59 pm
OK. Hidden.
But now I was thinking about that and I unhide it for few hours yesterday because my podc wasn't work (that with locked wallet) and this was for test if it helps.
Thanks for telling the truth.

I stand by with what I said earlier:  Those two statements above will cause the researcher to end up with 0 utxo weight and 0 task weight.

In your case you will lose your UTXO weight and your Task weight within 24 hours of being hidden.

I just verified:  We can't see your tasks right now, and your podcupdate will fail when it comes around within 8 hours.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 02:22:28 pm
Thanks for telling the truth.

I stand by with what I said earlier:  Those two statements above will cause the researcher to end up with 0 utxo weight and 0 task weight.

In your case you will lose your UTXO weight and your Task weight within 24 hours of being hidden.

I just verified:  We can't see your tasks right now, and your podcupdate will fail when it comes around within 8 hours.
OK... so can I leave it hidden for now?
They're hidden now more than 8 hours. Except of theese few unhidden minutes.
My UTXOWeight drops now to 75.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 23, 2018, 02:23:07 pm
I had an issue with my wallet, it kept crashing, tried all the normal recovery steps and nothing worked.  Since it was a pure test wallet, I ended up downloading a fresh copy of the biblepay client and cleaned out all files in the biblepaycore window (including my wallet).  After installing, mining a block and waiting for it to mature, I tried exec associate email pass and it responded "INVALID_CREDENTIALS", adding force to the end of the command did not change it.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:23:48 pm
OK... so can I leave it hidden for now?
They're hidden now more than 8 hours. Except of theese few unhidden minutes.
My UTXOWeight drops now to 75.
Yes, could you please be our guinea pig?  Lets just leave it hidden til you reach 0 reward and let us know when that happens (how many hours it took) then unhide it and watch it go back up.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:24:53 pm
I had an issue with my wallet, it kept crashing, tried all the normal recovery steps and nothing worked.  Since it was a pure test wallet, I ended up downloading a fresh copy of the biblepay client and cleaned out all files in the biblepaycore window (including my wallet).  After installing, mining a block and waiting for it to mature, I tried exec associate email pass and it responded "INVALID_CREDENTIALS", adding force to the end of the command did not change it.
Invalid credentials means the credentials are not correct.  Try logging into the web portal first, then retry association. 
Btw, if you keep a copy of your wallet.dat, you will not need to reassociate.

EDIT: Force is only required if you receive the error: ALREADY IN CHAIN.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 02:25:33 pm
Yes, could you please be our guinea pig?  Lets just leave it hidden til you reach 0 reward and let us know when that happens (how many hours it took) then unhide it and watch it go back up.
OK. :D
So we can starts to count it from now ;)
If it is only in testnet it is no problem :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 23, 2018, 02:38:45 pm
Invalid credentials means the credentials are not correct.  Try logging into the web portal first, then retry association. 
Btw, if you keep a copy of your wallet.dat, you will not need to reassociate.

EDIT: Force is only required if you receive the error: ALREADY IN CHAIN.

So I wasn't sure where"retry association" was, so I quit Team Biblepay, then rejoined.  But the error continued.  I was able to restore a previous wallet.dat file and it is correctly associated, but am unclear why the process would have failed on a new wallet (which is an unlikely situation to be in but...)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 23, 2018, 02:42:32 pm
One suggestion for the wallet to improve readability.  Could there be different mining categories?  So a Bible Icon for PoBH, a Church Icon for Sanctuaries and perhaps the atom (?) icon for PoDC?  And perhaps allow for these each to be shown  collectively under mining but also broken down by subcategory?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:54:24 pm
So I wasn't sure where"retry association" was, so I quit Team Biblepay, then rejoined.  But the error continued.  I was able to restore a previous wallet.dat file and it is correctly associated, but am unclear why the process would have failed on a new wallet (which is an unlikely situation to be in but...)

You won't have to ever quit Team Biblepay, it won't change any association business logic.
"The error continued", you mean Invalid Credentials?  - Answered Earlier.
If you change wallets, you should receive an "ALREADY IN CHAIN" message, once you enter the correct credentials.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 02:56:57 pm
One suggestion for the wallet to improve readability.  Could there be different mining categories?  So a Bible Icon for PoBH, a Church Icon for Sanctuaries and perhaps the atom (?) icon for PoDC?  And perhaps allow for these each to be shown  collectively under mining but also broken down by subcategory?

Icon's would definitely be nice.  That would be a nice cosmetic addition to the wallet.

Maybe you can reach out to Togo and see what kind of help he needs in recruiting a co-developer so we can have a dedicated testnet branch with features like that merged in for testing?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on February 23, 2018, 03:07:07 pm
Rastiks I see your machine right above your other ARM has 1.9GB ram and a BLANK for the processor.  What machine is that?

That was actually one of my ARM single-board computers. Not an Android mobile or tablet. But since it is running Linux, although I was able to connect it to rosetta@home, I wasn't able to solve any task with it, since Rosetta does not support ARM on Linux (other boinc projects do). And I tried very hard :-)

In general, you cannot assume that any ARM processor is a mobile or tablet: there are very high-performance multicore ARM servers (e.g. https://cavium.com/product-thunderx-arm-processors.html), there is even a 99$ ARM notebook (https://www.pine64.org/?page_id=3707).

BUT, the fact that you cannot leverage Linux-based ARM machine in Rosetta protects us a bit.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 23, 2018, 03:08:52 pm
You won't have to ever quit Team Biblepay, it won't change any association business logic.
"The error continued", you mean Invalid Credentials?  - Answered Earlier.
If you change wallets, you should receive an "ALREADY IN CHAIN" message, once you enter the correct credentials.

Yes, I tried exec asssociate with and without force multiple times and it continued "INVALID_CREDENTIALS", both when manually typing and cut and paste from the original file I used as well as trying the form on the main wallet as well as debug.  I didn't understand what you meant by "retry association" on Rosetta@home site, didn't see a link that was similar to that which is why I tried Quit and Rejoin Team Biblepay.

The only solution was restoring an old wallet backup from my testnet backups I maintain, works fine.  So not sure if there is a bug out there or if doing what you intended with retry association would have been sufficient but thought you should know.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 03:10:07 pm
Update on the next version - 1094c:

So I did a lot of expirimentation with the threading today, and have come to the conlcusion Jaap had a point, the wallet was using too much power even with the new settings in distributedcomputing mode.

So what I have done is in Distributed Computing mode the miner behaves slightly differently (in the next release).  It respects the CPU's thread priority meaning that it can run slower, and we now allow you to tweak the setting.

There will be a new setting called minersleep (the default is 0 for Prod and 250ms for Testnet).  If you set a numeric value you override it.
Now Im seeing about 10% proc usage by default, and when I raise the value, it does allow the machine to sleep more (down to more like 4% or so).

1094c is now out there for linux if anyone wants to expiriment.  This is a pretty minor change, so if you want to wait for the next release its no big deal.

Im compiling Windows now so we will have this to play with later tonight.

PS I did get the unbanked report working for the sanctuary validation system in unit test mode, but its not going to be ready til sometime tomorrow.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 03:15:16 pm
That was actually one of my ARM single-board computers. Not an Android mobile or tablet. But since it is running Linux, although I was able to connect it to rosetta@home, I wasn't able to solve any task with it, since Rosetta does not support ARM on Linux (other boinc projects do). And I tried very hard :-)

In general, you cannot assume that any ARM processor is a mobile or tablet: there are very high-performance multicore ARM servers (e.g. https://cavium.com/product-thunderx-arm-processors.html), there is even a 99$ ARM notebook (https://www.pine64.org/?page_id=3707).

BUT, the fact that you cannot leverage Linux-based ARM machine in Rosetta protects us a bit.

Ok great, thanks!  Yeah, I added that ARM (with blank proc) to the list in a way that it wouldnt disqualify you as an unbanked individual.
Regarding someone with only arms, and running in high power mode with the benefit of no controller wallet, I think all they really gain is not having a controller wallet anyway, so big deal, as long as we get our 98% integrity rating for the rest of the farm, Im ok with that :).  But if you guys see any heinous advantage, please, raise it as an issue and we can then put a Magnitude limit on the ünbanked CPIDs.  Those ARM tablets still only receive the same compensation as the banked cpids, (except they arent staking any capital so they get a free 100% utxo weight).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 03:24:34 pm
Yes, I tried exec asssociate with and without force multiple times and it continued "INVALID_CREDENTIALS", both when manually typing and cut and paste from the original file I used as well as trying the form on the main wallet as well as debug.  I didn't understand what you meant by "retry association" on Rosetta@home site, didn't see a link that was similar to that which is why I tried Quit and Rejoin Team Biblepay.

The only solution was restoring an old wallet backup from my testnet backups I maintain, works fine.  So not sure if there is a bug out there or if doing what you intended with retry association would have been sufficient but thought you should know.

Oh your right, I just reproduced that with my cpid, something changed.

Let me debug that problem next...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 23, 2018, 04:02:37 pm
Yes, I tried exec asssociate with and without force multiple times and it continued "INVALID_CREDENTIALS", both when manually typing and cut and paste from the original file I used as well as trying the form on the main wallet as well as debug.  I didn't understand what you meant by "retry association" on Rosetta@home site, didn't see a link that was similar to that which is why I tried Quit and Rejoin Team Biblepay.

The only solution was restoring an old wallet backup from my testnet backups I maintain, works fine.  So not sure if there is a bug out there or if doing what you intended with retry association would have been sufficient but thought you should know.
No wonder I was so confused!  I made the assumption the code was still working the way it was when I tested it last week.
So anyway when I added the podcupdate feature, it broke a couple of the return codes (or circumstances) inside the 'éxec  associate' feature.  So those are now fixed, and now people will see "ALREADY_IN_CHAIN" or "INVALID_CREDENTIALS" during the proper circumstances, in the next version.

Im checking in 1.0.9.4d now for linux if anyone wants to test that tonight.   Starting windows build over.

Lets check this out tomorrow when we have a chance to ensure reassociation works now.

Thanks for pointing out this bug!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 23, 2018, 04:36:03 pm
Icon's would definitely be nice.  That would be a nice cosmetic addition to the wallet.

Maybe you can reach out to Togo and see what kind of help he needs in recruiting a co-developer so we can have a dedicated testnet branch with features like that merged in for testing?
When we are talking about visual. I don't know if it is only my problem, but I'm not able to reduce wallet window size below some px (It is approx 90% of my screen height) And in testnet I'm unable to reduce it below maybe 110% of screen size, so I'm unable to see status bar and I must maximize my window to see everything. I have Win10. It is only my problem or it is common? Is possible to solve it?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 08:50:07 pm
When we are talking about visual. I don't know if it is only my problem, but I'm not able to reduce wallet window size below some px (It is approx 90% of my screen height) And in testnet I'm unable to reduce it below maybe 110% of screen size, so I'm unable to see status bar and I must maximize my window to see everything. I have Win10. It is only my problem or it is common? Is possible to solve it?

What's your resolution set to? If it's below 1024x768 you might not see the whole window.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 23, 2018, 10:15:36 pm
If Taskweight and UXTOweight are zero, should my magnitude be zero? I forgot to turn PoBH on.
Code: [Select]
"version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 14328660.49245012,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 6700,
  "timeoffset": 0,
  "connections": 12,
  "proxy": "",
  "difficulty": 0.2833186345714879,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

"Command": "getboincinfo",
  "CPID": "4fd1bf6c6900d92b226e16c6a6935661",
  "Address": "yWQfYmBCAQrcn9RkjM9DJwWGfgjHdvpZwn",
  "CPIDS": "4fd1bf6c6900d92b226e16c6a6935661;",
  "CPID-Age (hours)": 422068,
  "NextSuperblockHeight": 6732,
  "NextSuperblockBudget": 1359680,
  "4fd1bf6c6900d92b226e16c6a6935661_RAC": 820.6,
  "4fd1bf6c6900d92b226e16c6a6935661_TEAM": 15044,
  "4fd1bf6c6900d92b226e16c6a6935661_TaskWeight": 0,
  "4fd1bf6c6900d92b226e16c6a6935661_UTXOWeight": 0,
  "Total_RAC": 820.6,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 546564,
  "Total Budget (One Day)": 13700330,
  "Total Budget (One Week)": 67535384,
  "Superblock Count (One Week)": 63,
  "Superblock Hit Count (One Week)": 49,
  "Superblock List": "6633,6534,6435,6336,6237,6138,6039,5940,5841,5742,5643,5544,5445,5346,5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 6633,
  "Last Superblock Budget": 1359680,
  "Last Superblock Payment": 0,
  "Magnitude": 8.09300203283067
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 24, 2018, 01:52:25 am
Update on the next version - 1094c:

So I did a lot of expirimentation with the threading today, and have come to the conlcusion Jaap had a point, the wallet was using too much power even with the new settings in distributedcomputing mode.

So what I have done is in Distributed Computing mode the miner behaves slightly differently (in the next release).  It respects the CPU's thread priority meaning that it can run slower, and we now allow you to tweak the setting.

There will be a new setting called minersleep (the default is 0 for Prod and 250ms for Testnet).  If you set a numeric value you override it.
Now Im seeing about 10% proc usage by default, and when I raise the value, it does allow the machine to sleep more (down to more like 4% or so).

1094c is now out there for linux if anyone wants to expiriment.  This is a pretty minor change, so if you want to wait for the next release its no big deal.

Im compiling Windows now so we will have this to play with later tonight.

PS I did get the unbanked report working for the sanctuary validation system in unit test mode, but its not going to be ready til sometime tomorrow.

Great! I must say beforehand: Both AMD rigs I was telling you about were using the windows wallet. Looking back, could it be possible that the windows wallet (pre 1094c) wasn't using the 250ms setting yet?

Because just now I tested the new wallet on my linux rig, and out of the box (250ms) the cpu usage is already much lower than before. When I set it to 0ms it's back up to it's old values again.

I now set it to 500ms, and I'm able to get BOINC running along nicely while also mining (it's a véry slow AMD E-450 laptop) . I think it's great to have a 'one-go-solution' to tweaking the settings so that BOINC and one-thread-mining can go hand in hand, because I can imagine that a lot of people will be using only one computer to generate BBP.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 03:04:31 am
What's your resolution set to? If it's below 1024x768 you might not see the whole window.
My resolution is FHD 1920*1080.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 07:13:59 am
If Taskweight and UXTOweight are zero, should my magnitude be zero? I forgot to turn PoBH on.
Code: [Select]
"version": 1000904,
  "protocolversion": 70715,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.4",
  "balance": 14328660.49245012,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 6700,
  "timeoffset": 0,
  "connections": 12,
  "proxy": "",
  "difficulty": 0.2833186345714879,
  "testnet": true,
  "keypoololdest": 1518115544,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

"Command": "getboincinfo",
  "CPID": "4fd1bf6c6900d92b226e16c6a6935661",
  "Address": "yWQfYmBCAQrcn9RkjM9DJwWGfgjHdvpZwn",
  "CPIDS": "4fd1bf6c6900d92b226e16c6a6935661;",
  "CPID-Age (hours)": 422068,
  "NextSuperblockHeight": 6732,
  "NextSuperblockBudget": 1359680,
  "4fd1bf6c6900d92b226e16c6a6935661_RAC": 820.6,
  "4fd1bf6c6900d92b226e16c6a6935661_TEAM": 15044,
  "4fd1bf6c6900d92b226e16c6a6935661_TaskWeight": 0,
  "4fd1bf6c6900d92b226e16c6a6935661_UTXOWeight": 0,
  "Total_RAC": 820.6,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 546564,
  "Total Budget (One Day)": 13700330,
  "Total Budget (One Week)": 67535384,
  "Superblock Count (One Week)": 63,
  "Superblock Hit Count (One Week)": 49,
  "Superblock List": "6633,6534,6435,6336,6237,6138,6039,5940,5841,5742,5643,5544,5445,5346,5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 6633,
  "Last Superblock Budget": 1359680,
  "Last Superblock Payment": 0,
  "Magnitude": 8.09300203283067

I know this is going to sound a little complicated.. and Im thinking of ways to simplify this but with advanced system comes some advanced business logic:

The getboinc info values are current as of right now, so this is what Your client feels your RAC and your UTXOWeight and your TaskWeight are right now.  However, it takes a while for those to propagate through into the Sancs memory.  Because the Sanc has to allow 6 confirms for utxo weight in order to trust it and memorize it (it memorizes each cpids utxo weight into memory with a global key, called CPID_UTXOWeight_ with a 24 hour deadline on the timestamp, where new stamps erase old stamps, so its a complicated thing to explain).  This way all sancs are memorizing the utxo weight and task weight at the same time - all their memories should be equal.  They actually vote on what *they* agree on.

Now the Magnitude in getboincinfo is actually your reverse engineered magnitude over 7 days period. 
Your Superblock magnitude however , seen in exec leaderboard, is actually your "realized" mag as of the last superblock.

So from a cosmetic point of view, Im working on homogenizing this to just give the average biblepay-qt user a few numbers to look at on the GUI.

For the techies though, this means:  Your getboinc info is current debug info, but what the sancs vote on (they are always voting on the Next contract) is slightly different, as their memories are lagging slightly.

To see what a sanc *will* be voting on, go to one of your sancs and type exec testvote.  That particular contract can be dissected to see what they see about the network.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 07:17:13 am
No wonder I was so confused!  I made the assumption the code was still working the way it was when I tested it last week.
So anyway when I added the podcupdate feature, it broke a couple of the return codes (or circumstances) inside the 'éxec  associate' feature.  So those are now fixed, and now people will see "ALREADY_IN_CHAIN" or "INVALID_CREDENTIALS" during the proper circumstances, in the next version.

Im checking in 1.0.9.4d now for linux if anyone wants to test that tonight.   Starting windows build over.

Lets check this out tomorrow when we have a chance to ensure reassociation works now.

Thanks for pointing out this bug!
1.0.9.4d for windows is now out there, if anyone was experiencing the Invalid Credentials bug or the miner-cpu-usage issue.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 07:21:10 am
I know this is going to sound a little complicated.. and Im thinking of ways to simplify this but with advanced system comes some advanced business logic:

The getboinc info values are current as of right now, so this is what Your client feels your RAC and your UTXOWeight and your TaskWeight are right now.  However, it takes a while for those to propagate through into the Sancs memory.  Because the Sanc has to allow 6 confirms for utxo weight in order to trust it and memorize it (it memorizes each cpids utxo weight into memory with a global key, called CPID_UTXOWeight_ with a 24 hour deadline on the timestamp, where new stamps erase old stamps, so its a complicated thing to explain).  This way all sancs are memorizing the utxo weight and task weight at the same time - all their memories should be equal.  They actually vote on what *they* agree on.

Now the Magnitude in getboincinfo is actually your reverse engineered magnitude over 7 days period. 
Your Superblock magnitude however , seen in exec leaderboard, is actually your "realized" mag as of the last superblock.

So from a cosmetic point of view, Im working on homogenizing this to just give the average biblepay-qt user a few numbers to look at on the GUI.

For the techies though, this means:  Your getboinc info is current debug info, but what the sancs vote on (they are always voting on the Next contract) is slightly different, as their memories are lagging slightly.

To see what a sanc *will* be voting on, go to one of your sancs and type exec testvote.  That particular contract can be dissected to see what they see about the network.


But to answer your question more specifically, since you left podcupdates off, which is good so we can see the effects of it, you were asking why is my magnitude still 8 in getboincinfo?  Its because getboincinfo takes the last 7 days of magnitude-payments and averages them to be your Last 7 Day mag.

However your exec leaderboard should show you dropped out of the leaderboard with 0 mag. 

Also your exec getboincinfo  Last superblock payment should be 0.  <- Thats a good test, please see if you missed out on a research payment in a block where others have received research payments?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 07:22:52 am

But to answer your question more specifically, since you left podcupdates off, which is good so we can see the effects of it, you were asking why is my magnitude still 8 in getboincinfo?  Its because getboincinfo takes the last 7 days of magnitude-payments and averages them to be your Last 7 Day mag.

However your exec leaderboard should show you dropped out of the leaderboard with 0 mag. 

Also your exec getboincinfo  Last superblock payment should be 0.  <- Thats a good test, please see if you missed out on a research payment in a block where others have received research payments?


I think Ill add 24 hour magnitude and 7 day magnitude in exec getboincinfo, to make this clear.

The UI shows the 7 day magnitude value, for smoothing.

Then the user will see trends more clearly.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 07:28:17 am
Great! I must say beforehand: Both AMD rigs I was telling you about were using the windows wallet. Looking back, could it be possible that the windows wallet (pre 1094c) wasn't using the 250ms setting yet?

Because just now I tested the new wallet on my linux rig, and out of the box (250ms) the cpu usage is already much lower than before. When I set it to 0ms it's back up to it's old values again.

I now set it to 500ms, and I'm able to get BOINC running along nicely while also mining (it's a véry slow AMD E-450 laptop) . I think it's great to have a 'one-go-solution' to tweaking the settings so that BOINC and one-thread-mining can go hand in hand, because I can imagine that a lot of people will be using only one computer to generate BBP.

Great on the improved results!

Yes, before it was definitely true both win & linux were not sleeping the full default value, primarily because the nonce break didnt allow the wallet to sleep when it was told to.  Now in 1094c+, the windows wallet looks for its &HFF nonce break (thats about 256 hashes) and does what it is programmed to.

Yes, I agree I think if we can make some intelligent decisions then using biblepay will be more like using an iPhone.  My old boss used to say Oh that was a developer decision (implying that it was a horrible decision).  I agree that there are a lot of brainless decision out there that creep in from crazy PR discussions.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 09:07:48 am
When we are talking about visual. I don't know if it is only my problem, but I'm not able to reduce wallet window size below some px (It is approx 90% of my screen height) And in testnet I'm unable to reduce it below maybe 110% of screen size, so I'm unable to see status bar and I must maximize my window to see everything. I have Win10. It is only my problem or it is common? Is possible to solve it?
I think, that I've found the cause of my problem. I'm using biblepay-taditional as interface theme. When i change interface theme it is no problem to change (decrease) window size. But it is impossible for me to decrease it in biblepay-taditional.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 09:17:58 am
Yes, could you please be our guinea pig?  Lets just leave it hidden til you reach 0 reward and let us know when that happens (how many hours it took) then unhide it and watch it go back up.
It is more almost 20 hours since I hid my PCs but nothing has changed till now. My taskweight and UTXO are the same. PoC payment was decreased (but it is caused my UTXO fell to 75 before). And my magnitude is still rising. You were writting that it should change after approx. 8 hours, but nothing happens till now. Is it OK?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 09:41:39 am
It is more almost 20 hours since I hid my PCs but nothing has changed till now. My taskweight and UTXO are the same. PoC payment was decreased (but it is caused my UTXO fell to 75 before). And my magnitude is still rising. You were writting that it should change after approx. 8 hours, but nothing happens till now. Is it OK?

Lets wait the full 24 hours to see your magnitude go to zero.
I see exec leaderboard still shows your 04fb* CPID to have a magnitude of 37.1, and my sanctuary shows you with a UTXO weight of 75 and taskweight of 100.  Id like to see those show as zero before you change your settings to unhide the machines.

In the mean time can you give us the blocknumber that your PODC update was sent out on?  You can see it in the transaction list.

EDIT:  The 8 hours is when the client tries to send more updates (thats called a PODC Update).  The 24 hours is when the network loses your records.  Lets try to make distinctions between those things.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 10:03:57 am
Lets wait the full 24 hours to see your magnitude go to zero.
I see exec leaderboard still shows your 04fb* CPID to have a magnitude of 37.1, and my sanctuary shows you with a UTXO weight of 75 and taskweight of 100.  Id like to see those show as zero before you change your settings to unhide the machines.

In the mean time can you give us the blocknumber that your PODC update was sent out on?  You can see it in the transaction list.

EDIT:  The 8 hours is when the client tries to send more updates (thats called a PODC Update).  The 24 hours is when the network loses your records.  Lets try to make distinctions between those things.
Rob, I'm sorry, but I'm not able to find that PODC update block number. I watched all of my superblock tx, but I didn't found there something like that. How can I find it? I'm sending you my tx export, if it helps.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 24, 2018, 10:53:22 am

But to answer your question more specifically, since you left podcupdates off, which is good so we can see the effects of it, you were asking why is my magnitude still 8 in getboincinfo?  Its because getboincinfo takes the last 7 days of magnitude-payments and averages them to be your Last 7 Day mag.

However your exec leaderboard should show you dropped out of the leaderboard with 0 mag. 

Also your exec getboincinfo  Last superblock payment should be 0.  <- Thats a good test, please see if you missed out on a research payment in a block where others have received research payments?

OK, my last superblock payment before I set setgenerate to true was zero. Everything is coming back up now.

Code: [Select]
"Command": "getboincinfo",
  "CPID": "4fd1bf6c6900d92b226e16c6a6935661",
  "Address": "yWQfYmBCAQrcn9RkjM9DJwWGfgjHdvpZwn",
  "CPIDS": "4fd1bf6c6900d92b226e16c6a6935661;",
  "CPID-Age (hours)": 422080,
  "NextSuperblockHeight": 7326,
  "NextSuperblockBudget": 1359680,
  "4fd1bf6c6900d92b226e16c6a6935661_RAC": 823.29,
  "4fd1bf6c6900d92b226e16c6a6935661_TEAM": 15044,
  "4fd1bf6c6900d92b226e16c6a6935661_TaskWeight": 100,
  "4fd1bf6c6900d92b226e16c6a6935661_UTXOWeight": 75,
  "Total_RAC": 823.29,
  "Total Payments (One Day)": 167155,
  "Total Payments (One Week)": 713719,
  "Total Budget (One Day)": 14956480,
  "Total Budget (One Week)": 75693464,
  "Superblock Count (One Week)": 69,
  "Superblock Hit Count (One Week)": 55,
  "Superblock List": "7227,7128,7029,6930,6831,6732,6633,6534,6435,6336,6237,6138,6039,5940,5841,5742,5643,5544,5445,5346,5247,4653,4554,4257,4059,3861,3762,3267,3069,2970,2871,2772,2673,2574,2475,2376,2277,2178,2079,1980,1881,1782,1683,1584,1485,1386,1287,1188,1089,990,891,792,693,594,495",
  "Last Superblock Height": 7227,
  "Last Superblock Budget": 1359680,
  "Last Superblock Payment": 33431,
  "Magnitude": 9.429070388428782
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 11:03:13 am
Rob, I'm sorry, but I'm not able to find that PODC update block number. I watched all of my superblock tx, but I didn't found there something like that. How can I find it? I'm sending you my tx export, if it helps.

In the -qt client its easy because its in the txlist.  In the headless you would have to find a way to run listtransactions with "*" and filter things sent to you.

Instead of doing all that lets leapfrog forward and just improve the tools we have in PODC because I think we will need them.

Im adding timestamps to some of the tools now to ensure the network datavalues are : A) Getting cleared so that we dont bloat the users memory over time, and B) are actually clearing after 24 hours for a PODC consensus.

So far I have added this timestamp:


11:00:35

exec datalist utxoweight


11:00:35

{
  "DataList": "UTXOWEIGHT",
  "04FBA56D89A5EB38B1B82F8A6240132C (02-23-2018 19:26:49)": "75",
  "4FD1BF6C6900D92B226E16C6A6935661 (02-24-2018 13:23:45)": "75",
  "6785DED1F65063EF8F01F42DEB31CF1D (02-24-2018 13:54:18)": "100",
  "71F1F1F46DEB2F25961C7D9AF06F2B31 (02-24-2018 00:15:48)": "100",
  "93138F032BDD027FA3246B48BB715A77 (02-24-2018 16:51:54)": "100",
  "95A79CD5829E8315B0B946709930DF18 (02-24-2018 15:21:23)": "100",
  "C9085154B7CC0CA2B5189672559DD6D8 (02-23-2018 19:41:35)": "100",
  "CA895B47AACFFBDBF906201821AF2F9F (02-23-2018 19:41:35)": "100",
  "CC37D0EF74A621379974484F43D3B1C5 (02-24-2018 14:52:32)": "100",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (02-24-2018 15:07:13)": "75",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (02-24-2018 13:35:32)": "100",
  "E94C1704C75F731F8BFDE303F08408EE (02-24-2018 14:20:35)": "100",
  "F80AB050AB53459EC937879A046D603E (02-24-2018 10:43:28)": "100"
}



But now I need to do some more work to check the values.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 11:26:03 am
In the -qt client its easy because its in the txlist. 
Maybe it is easy, but I haven't any tx like this imy tx list. There are only two types of tx: mined block and superblock reward, like you can see im my tx export.

In the headless you would have to find a way to run listtransactions with "*" and filter things sent to you.
I run it on my VPS and it gives me this error:
Code: [Select]
error: Error parsing JSON:all_projects_list.xml
Instead of doing all that lets leapfrog forward and just improve the tools we have in PODC because I think we will need them.

Im adding timestamps to some of the tools now to ensure the network datavalues are : A) Getting cleared so that we dont bloat the users memory over time, and B) are actually clearing after 24 hours for a PODC consensus.
OK, i'll be waiting. In less than 3 hours it will be more than 24 hours since "hiding", so we will see.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 11:51:52 am
Maybe it is easy, but I haven't any tx like this imy tx list. There are only two types of tx: mined block and superblock reward, like you can see im my tx export.
I run it on my VPS and it gives me this error:
Code: [Select]
error: Error parsing JSON:all_projects_list.xmlOK, i'll be waiting. In less than 3 hours it will be more than 24 hours since "hiding", so we will see.

No, listtransactions works:
listtransactions "*"
(No json error)

Also, in -qt mode, you must have the PODCUpdate, otherwise we wouldnt be seeing your UTXOWeight.  Maybe you didnt scroll far enough back.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 12:07:16 pm
Looking a little closer at these 3 entries:
"04FBA56D89A5EB38B1B82F8A6240132C (02-23-2018 19:26:49)": "75",
  "C9085154B7CC0CA2B5189672559DD6D8 (02-23-2018 19:41:35)": "100",
  "CA895B47AACFFBDBF906201821AF2F9F (02-23-2018 19:41:35)": "100

These 3 are going to expire in 1 hour 45 minutes.
Lets see if they drop off.  Im going to leave my node up and not do anything.
These 3 are Me and Orbis.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 12:19:03 pm
Also, in -qt mode, you must have the PODCUpdate, otherwise we wouldnt be seeing your UTXOWeight.  Maybe you didnt scroll far enough back.

Ouch... I found where was problem :)
I had a filter set up to view only "mined" tx. But i don't know why :) Sorry, my big fault.
Here is my PODC tx:
Code: [Select]
Transaction fee: -0.00177080 tBiblepay
Net amount: -0.00177080 tBiblepay

Height: 6337
Difficulty: 28.704485
Time: 02-23-2018 19:26:49
Subsidy: 590.7047

PODC_UPDATE:
Transaction ID: d292be23f1d21cd688f10878937321dfd4bb331a7276abc6a606edc6e4bd3ff3-000
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 01:38:00 pm
so.. after last superblock my TaskWeight and UTXOWeight "jumps" to 0.
Magnitude is still 23.96673132507092.
It is interresting that my magnitude in leaderboards is 37.12730901380473.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 02:30:15 pm
so.. after last superblock my TaskWeight and UTXOWeight "jumps" to 0.
Magnitude is still 23.96673132507092.
It is interresting that my magnitude in leaderboards is 37.12730901380473.

Yes, thats good, but there is a reason for everything.  Not sure how I could explain this to all the users, lol.

So the getboincinfo magnitude is a 7 day average, so thats one thing, then exec leaderboard is what the sancs voted on in the "last" superblock, so thats another thing.

Finally, looking at the state of affairs in my sanc right now, the sanc knows your cpid now has 0 weight, and its creating a new contract with 0 for weight, but heres the other thing we have to take into consideration:  There is an anti-ddos locking rule in, where the sanctuaryquorum tries to honor files that have been downloaded for Up to 24 hours, and only if they are chosen sancs.  That brings into play all the variables of : What is your sanctuary rank, and are you chosen, and is your file fresh.

So in a nutshell, the exec leaderboard still shows you with magnitude right now, because the last contract voted in still had you in.

If we sat around and waited though, the maximum amount of time, those files would expire and the sancs would be forced to vote on the fresh contract with 0 mag.

I could add summarize this situation that a researcher must wait up to 48 hours for the data to flow through the pipeline (and drop off) but Im thinking about simplifying this situation.





Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 02:38:25 pm
I got my zbox c1327 in today, and installed the OS (btw, I had to install windows 10, win 7 with slipstreamed drivers wouldnt allow booting, so dont waste your time) anyway, Boinc 64 bit didnt work, so I installed boinc32 and I just added Rosetta.  This device is really small, you would think by the pics it was the size of an xbox, but its more like the size of a power supply.  No fan inside, and it has integrated video, lan wifi, etc.  It seems pretty snappy, Im opening browser windows in about 2 seconds, etc.  (It pulls about 20 watts total).   So once I get the ryzen 8 core running next to it, Ill keep track of these two machines: wattage, RAC, run time, cost per watt, RAC per watt, and ill take a picture of it.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 24, 2018, 02:43:10 pm
So the getboincinfo magnitude is a 7 day average, so thats one thing, then exec leaderboard is what the sancs voted on in the "last" superblock, so thats another thing.
Now it is clear, thanks.

I could add summarize this situation that a researcher must wait up to 48 hours for the data to flow through the pipeline (and drop off) but Im thinking about simplifying this situation.
Ok. I will leave my PCs hidden for next 24 hours :) Let's see if it works correctly (I have no doubt that yes  ;) ).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 03:32:47 pm
Now it is clear, thanks.
Ok. I will leave my PCs hidden for next 24 hours :) Let's see if it works correctly (I have no doubt that yes  ;) ).

Yeah, Im leaving mine hidden too until I see a superblock pay me zero.  Lets see if ours are zero at the same time.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 03:34:09 pm
Here is a pic of the expirimental Rosetta rig Im working on (for RAC comparisons per watt), the Zotac is the little box that looks like a power supply on the top, the Ryzen is the barebones Thermaltake on the bottom:

(http://pool.biblepay.org/SAN/zotac.jpg)

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 24, 2018, 06:14:29 pm
Here is a pic of the expirimental Rosetta rig Im working on (for RAC comparisons per watt), the Zotac is the little box that looks like a power supply on the top, the Ryzen is the barebones Thermaltake on the bottom:

(http://pool.biblepay.org/SAN/zotac.jpg)

Nice! I had something similar once: a Gigabyte Brix with a Celeron n-someting. It was fast enough for browsing and Word, not much else. It was very low-power though (that's why I bought it).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 24, 2018, 08:39:48 pm
Looks like Orbis and I were not in the last superblock, so that part appears to be working.

Im still going to add more magnitude metrics, and a memory clearing function, so the sancs only ever have a couple days of stagnant RAM associated with CPID weights.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 25, 2018, 03:31:02 am
Looks like Orbis and I were not in the last superblock, so that part appears to be working.

Im still going to add more magnitude metrics, and a memory clearing function, so the sancs only ever have a couple days of stagnant RAM associated with CPID weights.
Yes, my last superblock payment was on block 7425.
And my magnitude is still decreasing.
Ok. I'm going to unhide my PCs :) It looks that it won't be worthy to play with that in prod ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 25, 2018, 08:16:03 am
Nice! I had something similar once: a Gigabyte Brix with a Celeron n-someting. It was fast enough for browsing and Word, not much else. It was very low-power though (that's why I bought it).

Yeah, I was thinking since the zotac is 1.1ghz and 4 core, it would run rosetta at half the speed of the power hungry PC, and maybe someone could stack 10 together and have a low power monster, but in reality so far what Im seeing is a 30 RAC (in one day) from the zotac and a 250 RAC (per day) in the ryzen.  So its not quite worth buying these.  But let me finish a full 10 day test before trusting any of these numbers or figures.  Ill make a wiki page with a table on it at the end.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 25, 2018, 08:17:38 am
Yes, my last superblock payment was on block 7425.
And my magnitude is still decreasing.
Ok. I'm going to unhide my PCs :) It looks that it won't be worthy to play with that in prod ;)

Great! 

So far it looks promising - we now have UTXO integrity inside PODC...  And people must do some actual work to maintain the infrastructure... and the Controller wallets are staying on for block security...  Not a bad environment...

No pool required...  I think other coins are going to be jealous.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 25, 2018, 03:40:44 pm
Rob: your Ryzen is what ryzen 1700? and did only 250RAC for 24hours? .. how much RAM is need for ROSETTA? any help with 1core=1task? thanks guys
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 25, 2018, 06:32:22 pm
Rob: your Ryzen is what ryzen 1700? and did only 250RAC for 24hours? .. how much RAM is need for ROSETTA? any help with 1core=1task? thanks guys

It is about 500MB per task but it can vary. I don't think there is an easy way to have one task per core at the moment. It does what it needs to achieve the cpu usage you specified.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 25, 2018, 06:36:24 pm
Rob: your Ryzen is what ryzen 1700? and did only 250RAC for 24hours? .. how much RAM is need for ROSETTA? any help with 1core=1task? thanks guys
Looks like its a ryzen 1700 8 core.  I didnt tweak it to use 100% of the proc til this morning, so I started a new baseline with both this morning.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 25, 2018, 08:11:25 pm
Anything we should be testing tomorrow Rob? When would you like me to set up the additional 7 sanctuaries? I have 3 activated at the moment.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 25, 2018, 11:08:15 pm
Anything we should be testing tomorrow Rob? When would you like me to set up the additional 7 sanctuaries? I have 3 activated at the moment.

I added the cache purge today and fixed the prayers, but I still need to add the two new metrics and the diagnostic feature.

In the mean time if you want to start bringing more sancs up that would be helpful, because Id like to test the sanctuary rank command to ensure out of 10 sancs, that the top 3 by rank are voting.  The sancs will need a place in the payment queue so it would be good to start adding them tonight if you can.

Ill get an update ready asap.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 26, 2018, 04:46:04 am
Yeah, I was thinking since the zotac is 1.1ghz and 4 core, it would run rosetta at half the speed of the power hungry PC, and maybe someone could stack 10 together and have a low power monster, but in reality so far what Im seeing is a 30 RAC (in one day) from the zotac and a 250 RAC (per day) in the ryzen.  So its not quite worth buying these.  But let me finish a full 10 day test before trusting any of these numbers or figures.  Ill make a wiki page with a table on it at the end.

Yeah, I can't really tell anything yet about which CPU is most efficient. But, for example my phone (snapdragon 800 2.2ghz) and my - very slow - laptop (AMD e-450, 2x 1.65ghz) are getting about the same RAC I think, while I only use 1 core on my phone, and it's only processing when it's charging and above 90% battery (about 8 hours per day or something) and my laptop is processing full time on two cores. But I probably need a longer timeline before I can really say anything conclusive.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 07:02:22 am
Yeah, I can't really tell anything yet about which CPU is most efficient. But, for example my phone (snapdragon 800 2.2ghz) and my - very slow - laptop (AMD e-450, 2x 1.65ghz) are getting about the same RAC I think, while I only use 1 core on my phone, and it's only processing when it's charging and above 90% battery (about 8 hours per day or something) and my laptop is processing full time on two cores. But I probably need a longer timeline before I can really say anything conclusive.
Thats interesting the phone can do so well.
Day 2 update: The zotac is up to 150 RAC and the Ryzen up to 550 rac.  Zotac wattage:  15 watts, Ryzen wattage: 250 watts.
Price: Zotac: $300, Ryzen $700

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 07:30:13 am
Thats interesting the phone can do so well.
Day 2 update: The zotac is up to 150 RAC and the Ryzen up to 550 rac.  Zotac wattage:  15 watts, Ryzen wattage: 250 watts.
Price: Zotac: $300, Ryzen $700

I don't really look at the RAC because it doesn't reach near the real value until a few weeks later. What I do is look at the completed tasks and average out the credits/hour and use this formula to calculate the number of credits per day: (credits/hour)*(#tasks running at any moment)*24hrs. The tasks typically run for either 4 or 8 hours so you can do credits/4hrs or 8hrs and modify the formula. Be sure the # of tasks are the ones actually running and does not include the ones being queued up.

You can see from my android device that I am getting roughly 50 credits per task every 4 hours and I am running 2 tasks at any given moment so my RAC should eventually be 100.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 08:00:38 am
I don't really look at the RAC because it doesn't reach near the real value until a few weeks later. What I do is look at the completed tasks and average out the credits/hour and use this formula to calculate the number of credits per day: (credits/hour)*(#tasks running at any moment)*24hrs. The tasks typically run for either 4 or 8 hours so you can do credits/4hrs or 8hrs and modify the formula. Be sure the # of tasks are the ones actually running and does not include the ones being queued up.

You can see from my android device that I am getting roughly 50 credits per task every 4 hours and I am running 2 tasks at any given moment so my RAC should eventually be 100.

But thats really what RAC is - it gives you an idea about the computing power you have, I realize my RAC wont reach its maximum potential til I have run the nodes for 14 days, but Im taking that into account though.  But anyway for now the small device is 150/550, so its putting out about 25% of what the ryzen is.  Now I dont have to do any complicated credit delta computations or anything.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 08:39:47 am
But thats really what RAC is - it gives you an idea about the computing power you have, I realize my RAC wont reach its maximum potential til I have run the nodes for 14 days, but Im taking that into account though.  But anyway for now the small device is 150/550, so its putting out about 25% of what the ryzen is.  Now I dont have to do any complicated credit delta computations or anything.

If you started both at the same time then it would probably be OK for a comparison. I have one computer that is generating 10,000 credits per day but the RAC is only at 2.5k after 3~4 days.

What is the floating point benchmark score for the Zotac?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 08:51:21 am
If you started both at the same time then it would probably be OK for a comparison. I have one computer that is generating 10,000 credits per day but the RAC is only at 2.5k after 3~4 days.

What is the floating point benchmark score for the Zotac?

I will look at that FPS later once we have a little more lull in the development cycle.

But focusing on RAC for comparison, I dont catch your gist - RAC is the most accurate comparison from box to box, researcher to researcher, because it takes validated tasks into consideration, time into consideration, and smooths out network-disk-random activity to yield one number.  Thats why we base our magnitude off of ones RAC, and since we only have one project, you couldnt get any better.

Looking at credit delta is more useful for the reporting that deals with day to day changes for tamper reports and auditing etc.

It doesnt matter when one started in the cycle.  Since the RAC has a half life of two weeks after two weeks the numbers are the correct comparison for the two hosts, regardless of when one started.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 09:03:10 am
I will look at that FPS later once we have a little more lull in the development cycle.

But focusing on RAC for comparison, I dont catch your gist - RAC is the most accurate comparison from box to box, researcher to researcher, because it takes validated tasks into consideration, time into consideration, and smooths out network-disk-random activity to yield one number.  Thats why we base our magnitude off of ones RAC, and since we only have one project, you couldnt get any better.

Looking at credit delta is more useful for the reporting that deals with day to day changes for tamper reports and auditing etc.

It doesnt matter when one started in the cycle.  Since the RAC has a half life of two weeks after two weeks the numbers are the correct comparison for the two hosts, regardless of when one started.

Rob, the RAC is accurate from box to box but in the beginning it needs to catch up to speed. If you have 2 identical computers and one was started a week ago and one just now. You cannot compare the RAC of the 2 to arrive at the conclusion that the one started a week ago is faster than the one you started just now. Now, if it was 2 months from now, then yes you can compare the RAC values of the 2 machines.

http://web.archive.org/web/20120418125739/http://www.boinc-wiki.info/Recent_Average_Credit (http://web.archive.org/web/20120418125739/http://www.boinc-wiki.info/Recent_Average_Credit)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 09:17:15 am
Rob, the RAC is accurate from box to box but in the beginning it needs to catch up to speed. If you have 2 identical computers and one was started a week ago and one just now. You cannot compare the RAC of the 2 to arrive at the conclusion that the one started a week ago is faster than the one you started just now. Now, if it was 2 months from now, then yes you can compare the RAC values of the 2 machines.

http://web.archive.org/web/20120418125739/http://www.boinc-wiki.info/Recent_Average_Credit (http://web.archive.org/web/20120418125739/http://www.boinc-wiki.info/Recent_Average_Credit)
Mike,
Do you really believe I dont know what RAC is, when I developed the magnitude formula? 

I said I started both at the same time, and you can compare two RAC's to each other if they have been running for 2 weeks, and yes, if they started at different times, you can compare two RACs together after 14 days - because that is the half life of the formula.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 10:09:21 am
Mike,
Do you really believe I dont know what RAC is, when I developed the magnitude formula? 

I said I started both at the same time, and you can compare two RAC's to each other if they have been running for 2 weeks, and yes, if they started at different times, you can compare two RACs together after 14 days - because that is the half life of the formula.

Rob, I think you know but it wasn't apparent from the conversation. Also, I could not find where you said you started both at the same time in the last 2 pages of this forum, and that was the main point. If I were to compared RAC numbers I would only compare after 4 weeks, at 2 weeks it's still only roughly 80% of what it should be. IF yo ustarted both at the same time then it wouldn't matter as much.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 10:54:35 am
Rob, I think you know but it wasn't apparent from the conversation. Also, I could not find where you said you started both at the same time in the last 2 pages of this forum, and that was the main point. If I were to compared RAC numbers I would only compare after 4 weeks, at 2 weeks it's still only roughly 80% of what it should be. IF yo ustarted both at the same time then it wouldn't matter as much.

Cool, but its not really a true statement that you need to wait four weeks, even if they are started at completely different times.

When working with exponents, each day both machines are running draws the comparison (of RAC over RAC) closer by 7.14% each - even if they were started at different times, and close to 100% equal in comparison if you wait 14 days, because even in the worst case scenario if Machine B was running for 30 days before machine A, and machine A for only 1 day in advance, by the 14th day, the RAC of machine B is 91% into its average reference reading while machine A is also 91% into its final slot.    By the 15th day this number is close to 99%.   

Thats why magnitude in exec leaderboard is going to reveal highly accurate comparisons of CPIDs without knowing anything about them - but the main difference with magnitude is we are looking at all the machines rolled up to one CPID, and how much total effort they put in (even if they have 90 machines working only 1 hour per day).


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 26, 2018, 12:26:02 pm
My understanding of RAC was it was a weekly half life, so days 0-7 = 100%, 8-14 = 50%, 15-21=25%, etc. etc.

So by my understanding after a week you can roughly estimate that a particular machine will do about double that over the long haul
1 week 50%
2 weeks 75%
3 weeks 87.5%
4 weeks 93.75%
... ...
99% at 7 weeks.

Is that a misunderstanding?

Additionally, I was thinking and wondering if there might be some benefit to the system to require a larger "stake" for higher RAC?  This could alleviate the phone / unbanked poor issue and also be more equitable for the larger RAC users (like it seems like I'm going to be one of).  So basically a graduated system where there were three or four tables for Biblepay UTXO Reward Chart  or maybe making it a percentile based affair?  Such as Stake amount required = 2*RAC for 100% (just spit balling)?  Looking at the leader board, I see a good number of users with RAC in the tens of thousands (and again, I may be one of them at some point), but I don't believe it to be equitable that a 1000 RAC user and a 10,000 RAC user both require the same 50K BBP stake for 100%.

Beyond that, it seems like PoDC is working very very well!  Are we still on target for a mid-to-end-of-March (barring any other significant issues) shift to PoDC?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 12:41:25 pm
My understanding of RAC was it was a weekly half life, so days 0-7 = 100%, 8-14 = 50%, 15-21=25%, etc. etc.

So by my understanding after a week you can roughly estimate that a particular machine will do about double that over the long haul
1 week 50%
2 weeks 75%
3 weeks 87.5%
4 weeks 93.75%
... ...
99% at 7 weeks.

Is that a misunderstanding?

Additionally, I was thinking and wondering if there might be some benefit to the system to require a larger "stake" for higher RAC?  This could alleviate the phone / unbanked poor issue and also be more equitable for the larger RAC users (like it seems like I'm going to be one of).  So basically a graduated system where there were three or four tables for Biblepay UTXO Reward Chart  or maybe making it a percentile based affair?  Such as Stake amount required = 2*RAC for 100% (just spit balling)?  Looking at the leader board, I see a good number of users with RAC in the tens of thousands (and again, I may be one of them at some point), but I don't believe it to be equitable that a 1000 RAC user and a 10,000 RAC user both require the same 50K BBP stake for 100%.

Beyond that, it seems like PoDC is working very very well!  Are we still on target for a mid-to-end-of-March (barring any other significant issues) shift to PoDC?

Yeah, its a misunderstanding of RAC, possibly due to not understand the nature of exponents or what half life of 30 days means.

On day 2 you would have 33% of your RAC in place, on day 8 : 66%, and on day 14 : 90%, roughly similar to what I said in the prior posts.
(By the time the half life hits, you have 90% of your Stabilized RAC in place)!  The Half life is 14 days!

Regarding the second idea, I dont think its beneficial to create arbitrary rules that promote people to split wallets and CPIDs (as thats all they would do, is split the cpid into two if they had to have higher balances).  In addition its important that we run this system for one year in the most simple form possible in order to support it and debug it, then vote on the most important changes after its live for a few quarters.




Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 12:42:46 pm
Biblepay 1.0.9.5 - Mandatory upgrade for Testnet

- Allow unbanked to be compensated without PODC Updates
- Added exec unbanked report, this shows a list of the unbanked (used by Sanctuaries)
- Fixed prayers diaplay in overview page  (they were invisible)
- Added UTXO weight and Task Weight to Distributed Computing Page GUI
- Added 7 day Magnitude and 1 day magnitude to exec getboincinfo
- Fixed DC Association process to throw the correct distinct errors for INVALID_CREDENTIALS or ALREADY_IN_CHAIN
- Added cache purging system (to prevent memory bloating in the future)

* Windows is compiling *
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 26, 2018, 01:52:48 pm
Yeah, its a misunderstanding of RAC, possibly due to not understand the nature of exponents or what half life of 30 days means.

On day 2 you would have 33% of your RAC in place, on day 8 : 66%, and on day 14 : 90%, roughly similar to what I said in the prior posts.
(By the time the half life hits, you have 90% of your Stabilized RAC in place)!  The Half life is 14 days!

Regarding the second idea, I dont think its beneficial to create arbitrary rules that promote people to split wallets and CPIDs (as thats all they would do, is split the cpid into two if they had to have higher balances).  In addition its important that we run this system for one year in the most simple form possible in order to support it and debug it, then vote on the most important changes after its live for a few quarters.

Is it our system that is going to work differently?  Because BOINC says https://boinc.berkeley.edu/wiki/Computation_credit  "Recent average credit: The average number of Cobblestones per day granted recently. This average decreases by a factor of two every week."  And the only other discussions I've seen on line about BOINC compute it the same way.  So it that document out of date, am I misunderstanding what it says or is our system utilizing a different factor?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 02:39:14 pm
Is it our system that is going to work differently?  Because BOINC says https://boinc.berkeley.edu/wiki/Computation_credit  "Recent average credit: The average number of Cobblestones per day granted recently. This average decreases by a factor of two every week."  And the only other discussions I've seen on line about BOINC compute it the same way.  So it that document out of date, am I misunderstanding what it says or is our system utilizing a different factor?

The RAC is calculated by BOINC I believe, is that correct Rob? I think we just need to clarify the formula that will be used.

RAC(new) = RAC(old)*d(t) + (1-d(t))*credit(new)
d(t) = e^(-ln(2)*t / 604800)

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 02:58:42 pm
Biblepay 1.0.9.5 - Mandatory upgrade for Testnet

- Allow unbanked to be compensated without PODC Updates
- Added exec unbanked report, this shows a list of the unbanked (used by Sanctuaries)
- Fixed prayers diaplay in overview page  (they were invisible)
- Added UTXO weight and Task Weight to Distributed Computing Page GUI
- Added 7 day Magnitude and 1 day magnitude to exec getboincinfo
- Fixed DC Association process to throw the correct distinct errors for INVALID_CREDENTIALS or ALREADY_IN_CHAIN
- Added cache purging system (to prevent memory bloating in the future)

* Windows is compiling *

Updating 3 nodes now and if there aren't any big issues I'll deploy the rest tomorrow.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 03:09:45 pm
Is it our system that is going to work differently?  Because BOINC says https://boinc.berkeley.edu/wiki/Computation_credit  "Recent average credit: The average number of Cobblestones per day granted recently. This average decreases by a factor of two every week."  And the only other discussions I've seen on line about BOINC compute it the same way.  So it that document out of date, am I misunderstanding what it says or is our system utilizing a different factor?

Your not evaluating the formula exponentially and the definition is correct.  A factor of two every week is the same as the RAC being fulfilled 90% within 2 weeks (its half life) and 99% in 4 weeks.  Ill put the formula in biblepay so you can type exec racformula and see the RAC per day.

Mike:  The formula you posted is correct- its done within the boinc network.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on February 26, 2018, 03:40:22 pm
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!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 04:49:06 pm
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.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 26, 2018, 04:54:29 pm
Alright :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 05:06:49 pm
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.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 05:10:48 pm
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! 


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 06:59:06 pm
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.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 08:46:54 pm
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.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 26, 2018, 08:56:17 pm
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




Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 26, 2018, 10:42:43 pm
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
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 26, 2018, 10:57:05 pm
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
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 27, 2018, 03:26:01 am
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]
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
 (https://boinc.bakerlab.org/rosetta/show_user.php?userid=1985966)

CPID: c852da1a620ad630b70c8ec1ccdee366

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

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: klondike on February 27, 2018, 06:48:10 am
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 ;D i must to upgrade my RAM on my xeons machines :(

thx for answers
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 27, 2018, 06:52:53 am
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).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 07:13:09 am
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.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 07:22:48 am
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.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 08:44:20 am
thx for fast answer ..woho :D

1. i didnt yet...ill go update now= tBBP is all
2. polpercentage setuped to 50 may be help it

thanks guys ...


Rob: whats problem when on rosetta i saw last 12hours    Error while computing  .. can be problem with less RAM? thx

These are not valid questions.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on February 27, 2018, 09:10:23 am
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.

Code: [Select]



16:06:15

masternode winners


16:06:15

{
  "10155": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:5",
  "10156": "yczua3NywynKiUUN3yzKryLJgJmgt466QV:5",
  "10157": "yczua3NywynKiUUN3yzKryLJgJmgt466QV:5",
  "10158": "yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:1, yW7P6b7572frx11TgeyBnNCjKaRCfYz6fi:4",
  "10159": "yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:1, yW7P6b7572frx11TgeyBnNCjKaRCfYz6fi:4",
  "10160": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb:4",
  "10161": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:3",
  "10162": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:3",
  "10163": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yLi5aMHH4ZwXT1jPzmSKNoZHT2hyjLey7p:3",
  "10164": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:5",
  "10165": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:4",
  "10166": "ySYCxw9dKishWtwAEWN3Md8xqUSLSufZ2D:4",
  "10167": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, ySYCxw9dKishWtwAEWN3Md8xqUSLSufZ2D:3",
  "10168": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, yh4nfiwoS94uqR7yMibib6UDe7kqxXRyCe:4",
  "10169": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, yh4nfiwoS94uqR7yMibib6UDe7kqxXRyCe:4",
  "10170": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, yZ7hJEWGw3hU76xdpWaBsuAkqmvpCXbwKQ:4",
  "10171": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:4",
  "10172": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:4",
  "10173": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:1, ygfopeKeCyL6NgtP1o1T63euiBteJp8vHg:4",
  "10174": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:1, ygfopeKeCyL6NgtP1o1T63euiBteJp8vHg:3",
  "10175": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:5",
  "10176": "Unknown",
  "10177": "Unknown",
  "10178": "Unknown",
  "10179": "Unknown",
  "10180": "Unknown",
  "10181": "Unknown",
  "10182": "Unknown",
  "10183": "Unknown",
  "10184": "Unknown"
}


16:06:19

exec testranks


16:06:20

{
  "Command": "testranks",
  "percentrank 10073 0": 1,
  "percentrank 10074 0": 1,
  "percentrank 10075 0": 1,
  "percentrank 10076 100": 3,
  "percentrank 10077 300": 6,
  "percentrank 10078 300": 6,
  "percentrank 10079 100": 3,
  "percentrank 10080 300": 6,
  "percentrank 10081 100": 2,
  "percentrank 10082 0": 1,
  "percentrank 10083 300": 6,
  "percentrank 10084 200": 5,
  "percentrank 10085 100": 2,
  "percentrank 10086 400": 8,
  "percentrank 10087 300": 6,
  "percentrank 10088 100": 3,
  "percentrank 10089 0": 1,
  "percentrank 10090 0": 1,
  "percentrank 10091 0": 1,
  "percentrank 10092 200": 4,
  "percentrank 10093 0": 1,
  "percentrank 10094 200": 4,
  "percentrank 10095 200": 5,
  "percentrank 10096 200": 4,
  "percentrank 10097 300": 7,
  "percentrank 10098 0": 1,
  "percentrank 10099 400": 8,
  "percentrank 10100 0": 1,
  "percentrank 10101 200": 5,
  "percentrank 10102 200": 5,
  "percentrank 10103 0": 1,
  "percentrank 10104 300": 7,
  "percentrank 10105 100": 3,
  "percentrank 10106 200": 5,
  "percentrank 10107 200": 4,
  "percentrank 10108 200": 5,
  "percentrank 10109 100": 2,
  "percentrank 10110 200": 4,
  "percentrank 10111 0": 1,
  "percentrank 10112 200": 5,
  "percentrank 10113 400": 8,
  "percentrank 10114 300": 6,
  "percentrank 10115 200": 5,
  "percentrank 10116 200": 4,
  "percentrank 10117 100": 2,
  "percentrank 10118 0": 1,
  "percentrank 10119 100": 3,
  "percentrank 10120 0": 1,
  "percentrank 10121 200": 5,
  "percentrank 10122 0": 1,
  "percentrank 10123 300": 6,
  "percentrank 10124 400": 8,
  "percentrank 10125 400": 8,
  "percentrank 10126 300": 7,
  "percentrank 10127 200": 5,
  "percentrank 10128 200": 4,
  "percentrank 10129 200": 5,
  "percentrank 10130 100": 3,
  "percentrank 10131 100": 2,
  "percentrank 10132 300": 6,
  "percentrank 10133 200": 4,
  "percentrank 10134 200": 5,
  "percentrank 10135 400": 8,
  "percentrank 10136 300": 6,
  "percentrank 10137 200": 5,
  "percentrank 10138 100": 3,
  "percentrank 10139 300": 7,
  "percentrank 10140 300": 6,
  "percentrank 10141 200": 5,
  "percentrank 10142 200": 5,
  "percentrank 10143 100": 2,
  "percentrank 10144 100": 3,
  "percentrank 10145 400": 8,
  "percentrank 10146 0": 1,
  "percentrank 10147 300": 6,
  "percentrank 10148 100": 3,
  "percentrank 10149 200": 4,
  "percentrank 10150 100": 3,
  "percentrank 10151 100": 2,
  "percentrank 10152 0": 1,
  "percentrank 10153 300": 6,
  "percentrank 10154 200": 4,
  "percentrank 10155 0": 1,
  "percentrank 10156 300": 6,
  "percentrank 10157 200": 4,
  "percentrank 10158 0": 1,
  "percentrank 10159 100": 3,
  "percentrank 10160 300": 7,
  "percentrank 10161 100": 2,
  "percentrank 10162 200": 5,
  "percentrank 10163 100": 3,
  "percentrank 10164 0": 1,
  "percentrank 10165 0": 1,
  "percentrank 10166 0": -1,
  "percentrank 10167 0": -1,
  "percentrank 10168 0": -1,
  "percentrank 10169 0": -1,
  "percentrank 10170 0": -1,
  "percentrank 10171 0": -1,
  "percentrank 10172 0": -1,
  "percentrank 10173 0": -1,
  "percentrank 10174 0": -1,
  "percentrank 10175 0": -1,
  "percentrank 10176 0": -1,
  "percentrank 10177 0": -1,
  "percentrank 10178 0": -1,
  "percentrank 10179 0": -1,
  "percentrank 10180 0": -1,
  "percentrank 10181 0": -1,
  "percentrank 10182 0": -1,
  "percentrank 10183 0": -1,
  "percentrank 10184 0": -1,
  "percentrank 10185 0": -1,
  "percentrank 10186 0": -1,
  "percentrank 10187 0": -1,
  "percentrank 10188 0": -1,
  "percentrank 10189 0": -1,
  "percentrank 10190 0": -1,
  "percentrank 10191 0": -1,
  "percentrank 10192 0": -1,
  "percentrank 10193 0": -1,
  "percentrank 10194 0": -1,
  "percentrank 10195 0": -1,
  "percentrank 10196 0": -1,
  "percentrank 10197 0": -1,
  "sanctuary_count": 2
}


16:07:19

masternode count enabled


16:07:19

2


16:07:27

masternodelist


16:07:27

{
  "8a90e15bbfaeac9ed6aebb654374900346fa9ea47e91418dcb2f8083f058c00e-1": "WATCHDOG_EXPIRED",
  "0d73d75aa399c497e9569232c6dfb8f7fd0f2f3c333f10b980839dba215c1d11-1": "NEW_START_REQUIRED",
  "57347df338d9bb8fa4e91852c910047df171f318ae70dfa263a11ef5726401c2-1": "NEW_START_REQUIRED",
  "bffc8466fb89bdd425ad884e0c31a677093260a80350c2e804cfeb79b836bb0a-0": "NEW_START_REQUIRED",
  "7fb209612bed04aa95e68091cfd0958396890aa7df748ce1b68502e23b9363ec-1": "NEW_START_REQUIRED",
  "da1bc33cdb64a4ef4cf6a9194fe4ca2350b2d53ee229cbf86c61b54777442223-1": "ENABLED",
  "5d0f236522fa2a9acf8f3b8523e67a34600f754aedf146b366361ab7dea41028-1": "WATCHDOG_EXPIRED",
  "73a43e8a400802c41fd3d5b04ebfd77b809c24cb8167bf12b6ea6f1b6261eb18-1": "ENABLED",
  "70c0e1dd08b3ea91a175452cf372f047b0b3b627527679209abe906b5eb06e96-1": "WATCHDOG_EXPIRED",
  "4f2d9e9097cc065a4600fa470a5950e58699f58a9464a12ef98e695e179e94df-1": "WATCHDOG_EXPIRED",
  "c7f3413b0bcfb871babde98ddef1f375572eadf567a3b2deccdd1bd454e69d56-1": "WATCHDOG_EXPIRED",
  "44b2fcb6d8092d1e837709e2fc181ef2ecf663737e1bbdb32f6cfb9279e87273-1": "WATCHDOG_EXPIRED"
}


My masternode says that there are only 2 masternodes enabled, but the payment que suggests otherwise. I am the 'yUU' adress btw.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 09:18:04 am
Rob A. from where i know that problem is in BOINC?   exists any BUG TUTORIAL with BBP-ROSETTA? no, so you can test alone with 3 guys here
bye

and dont think that you kill da BOTNET..... scripts is made for ROSETTA  ;D

BOTNET BBP yeah

Ill bet you $1000 of BBP that (after PODC Goes Live) : Either the Botnet is : A) Doing cancer research and is no longer a bot-net, or B) We are a secure happy family with lower difficulty.  Either of those is a win-win. 

My clarification is :  If difficulty is high in PODC, and we have 5,000 CPIDs for cancer research- That is No Longer a Botnet.  Why?  Because then we have our software updates on our side of the house still working, and those clear designated CPIDs are publically visible in our reports.  That makes them cancer researchers and Not a botnet.

If you are willing to take this challenge Ill send my BBP into escrow with one of the trusted members here like Togo or Jaap, and you can bet me publically.

Thats how much I believe in PODC.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 27, 2018, 09:21:43 am
10 Sanctuaries up!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 09:25:10 am
Code: [Select]



16:06:15

masternode winners


16:06:15

{
  "10155": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:5",
  "10156": "yczua3NywynKiUUN3yzKryLJgJmgt466QV:5",
  "10157": "yczua3NywynKiUUN3yzKryLJgJmgt466QV:5",
  "10158": "yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:1, yW7P6b7572frx11TgeyBnNCjKaRCfYz6fi:4",
  "10159": "yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:1, yW7P6b7572frx11TgeyBnNCjKaRCfYz6fi:4",
  "10160": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb:4",
  "10161": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:3",
  "10162": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yesrwrCZpBTrHXzt6o36WTAqtagvPpCp6F:3",
  "10163": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:1, yLi5aMHH4ZwXT1jPzmSKNoZHT2hyjLey7p:3",
  "10164": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:5",
  "10165": "yfhgGUHDYBaSyWYXd1X1gARTswyWKsyRX5:4",
  "10166": "ySYCxw9dKishWtwAEWN3Md8xqUSLSufZ2D:4",
  "10167": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, ySYCxw9dKishWtwAEWN3Md8xqUSLSufZ2D:3",
  "10168": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, yh4nfiwoS94uqR7yMibib6UDe7kqxXRyCe:4",
  "10169": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, yh4nfiwoS94uqR7yMibib6UDe7kqxXRyCe:4",
  "10170": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:1, yZ7hJEWGw3hU76xdpWaBsuAkqmvpCXbwKQ:4",
  "10171": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:4",
  "10172": "yd7si6yg2Tp4Pkp1dSYeisWFzJwmdwsjq3:4",
  "10173": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:1, ygfopeKeCyL6NgtP1o1T63euiBteJp8vHg:4",
  "10174": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:1, ygfopeKeCyL6NgtP1o1T63euiBteJp8vHg:3",
  "10175": "yUUGJxxFFxx3e9EWU7q2G649EvEs8bNvDC:5",
  "10176": "Unknown",
  "10177": "Unknown",
  "10178": "Unknown",
  "10179": "Unknown",
  "10180": "Unknown",
  "10181": "Unknown",
  "10182": "Unknown",
  "10183": "Unknown",
  "10184": "Unknown"
}


16:06:19

exec testranks


16:06:20

{
  "Command": "testranks",
  "percentrank 10073 0": 1,
  "percentrank 10074 0": 1,
  "percentrank 10075 0": 1,
  "percentrank 10076 100": 3,
  "percentrank 10077 300": 6,
  "percentrank 10078 300": 6,
  "percentrank 10079 100": 3,
  "percentrank 10080 300": 6,
  "percentrank 10081 100": 2,
  "percentrank 10082 0": 1,
  "percentrank 10083 300": 6,
  "percentrank 10084 200": 5,
  "percentrank 10085 100": 2,
  "percentrank 10086 400": 8,
  "percentrank 10087 300": 6,
  "percentrank 10088 100": 3,
  "percentrank 10089 0": 1,
  "percentrank 10090 0": 1,
  "percentrank 10091 0": 1,
  "percentrank 10092 200": 4,
  "percentrank 10093 0": 1,
  "percentrank 10094 200": 4,
  "percentrank 10095 200": 5,
  "percentrank 10096 200": 4,
  "percentrank 10097 300": 7,
  "percentrank 10098 0": 1,
  "percentrank 10099 400": 8,
  "percentrank 10100 0": 1,
  "percentrank 10101 200": 5,
  "percentrank 10102 200": 5,
  "percentrank 10103 0": 1,
  "percentrank 10104 300": 7,
  "percentrank 10105 100": 3,
  "percentrank 10106 200": 5,
  "percentrank 10107 200": 4,
  "percentrank 10108 200": 5,
  "percentrank 10109 100": 2,
  "percentrank 10110 200": 4,
  "percentrank 10111 0": 1,
  "percentrank 10112 200": 5,
  "percentrank 10113 400": 8,
  "percentrank 10114 300": 6,
  "percentrank 10115 200": 5,
  "percentrank 10116 200": 4,
  "percentrank 10117 100": 2,
  "percentrank 10118 0": 1,
  "percentrank 10119 100": 3,
  "percentrank 10120 0": 1,
  "percentrank 10121 200": 5,
  "percentrank 10122 0": 1,
  "percentrank 10123 300": 6,
  "percentrank 10124 400": 8,
  "percentrank 10125
  "percentrank 10176 0": -1,
  "percentrank 10177 0": -1,
  "percentrank 10178 0": -1,
  "percentrank 10179 0": -1,
  "percentrank 10180 0": -1,
  "percentrank 10181 0": -1,
  "percentrank 10182 0": -1,
  "percentrank 10183 0": -1,
  "percentrank 10184 0": -1,
  "percentrank 10185 0": -1,
  "percentrank 10186 0": -1,
  "percentrank 10187 0": -1,
  "percentrank 10188 0": -1,
  "percentrank 10189 0": -1,
  "percentrank 10190 0": -1,
  "percentrank 10191 0": -1,
  "percentrank 10192 0": -1,
  "percentrank 10193 0": -1,
  "percentrank 10194 0": -1,
  "percentrank 10195 0": -1,
  "percentrank 10196 0": -1,
  "percentrank 10197 0": -1,
  "sanctuary_count": 2
}


16:07:19

masternode count enabled


16:07:19

2


16:07:27

masternodelist


16:07:27

{
  "8a90e15bbfaeac9ed6aebb654374900346fa9ea47e91418dcb2f8083f058c00e-1": "WATCHDOG_EXPIRED",
  "0d73d75aa399c497e9569232c6dfb8f7fd0f2f3c333f10b980839dba215c1d11-1": "NEW_START_REQUIRED",
  "57347df338d9bb8fa4e91852c910047df171f318ae70dfa263a11ef5726401c2-1": "NEW_START_REQUIRED",
  "bffc8466fb89bdd425ad884e0c31a677093260a80350c2e804cfeb79b836bb0a-0": "NEW_START_REQUIRED",
  "7fb209612bed04aa95e68091cfd0958396890aa7df748ce1b68502e23b9363ec-1": "NEW_START_REQUIRED",
  "da1bc33cdb64a4ef4cf6a9194fe4ca2350b2d53ee229cbf86c61b54777442223-1": "ENABLED",
  "5d0f236522fa2a9acf8f3b8523e67a34600f754aedf146b366361ab7dea41028-1": "WATCHDOG_EXPIRED",
  "73a43e8a400802c41fd3d5b04ebfd77b809c24cb8167bf12b6ea6f1b6261eb18-1": "ENABLED",
  "70c0e1dd08b3ea91a175452cf372f047b0b3b627527679209abe906b5eb06e96-1": "WATCHDOG_EXPIRED",
  "4f2d9e9097cc065a4600fa470a5950e58699f58a9464a12ef98e695e179e94df-1": "WATCHDOG_EXPIRED",
  "c7f3413b0bcfb871babde98ddef1f375572eadf567a3b2deccdd1bd454e69d56-1": "WATCHDOG_EXPIRED",
  "44b2fcb6d8092d1e837709e2fc181ef2ecf663737e1bbdb32f6cfb9279e87273-1": "WATCHDOG_EXPIRED"
}


My masternode says that there are only 2 masternodes enabled, but the payment que suggests otherwise. I am the 'yUU' adress btw.

Thanks Jaap!  Yeah, the thing is the 'masternode list' command returns all the sancs in every state, and technically the ones in watchdog expired status that are UP, where biblepayd is responding , they are still voting for payments and end up being in the payment list and paid.  Thats because we dont have the spork enabld to Ban users for watchdog expired (watchman on the wall) violations, but we do POSE ban if the node goes down, so they are not getting free money.  SO yes we have something like 8 sancs up, the wallet thinks we have 2 (enabled sancs).

But anyway all this is OK because the Rank feature - when it exceeds the sanc count - does not fail, it just makes more sancs work than normal (IE more show 100% chance than normal), so look ing  at your report, your looks good, looks like mine...

I think that test will pass for prod.

In prod however we should have much more accuracy - about 10% voting, thats 15 sancs voting and processing files.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 09:39:40 am
500 CPID?   1CPID=1machine=1guy

botnet script = exists in botnet forum about rosetta how can we do script for 100 users=accounts on rosetta

100 accounts= 100CPIDs=totally easy make it and owner of botnet doesnt idiot, trust me

SVK guys 20 persons
1 person do 10 accounts with 10 CPIDs=10machines

200 CPIDS for 1 day.. wink

 ;)

and yes, you have true about botnet for rosetta= will be good deal for cancer researching


You act as if you have zero intelligence.  Its not beneficial to create more than one CPID, RAC takes 14 days to build up, magnitude is based on RAC per CPID, and it takes work to maintain each CPID. 

Slovakia, please stop posting here if you are not a NET VALUE to the community.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 09:42:03 am
Posted by T-Mike:

Klondike, if the "bots" are doing work on Rosseta, we do not consider it a bot anymore, it is doing good work. If you are here for profit, then it makes a different, if you are not, let all the botnets in the world start computing for Rosetta.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 27, 2018, 11:28:13 am
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?
So, you must have ARM based devices on unique CPID if you want to work like unbanked?
And what if my ARM based Galaxy S7 is without "CPU type": https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3351184
If I have PC what I just wanna run only sometimes (and it can run with controller wallet) it must be with different CPID?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 11:36:48 am
So, you must have ARM based devices on unique CPID if you want to work like unbanked?
And what if my ARM based Galaxy S7 is without "CPU type": https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3351184
If I have PC what I just wanna run only sometimes (and it can run with controller wallet) it must be with different CPID?

You just must not have any non-arm processors and non-blank processors on the same CPID, in order to not be disqualified.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 27, 2018, 12:02:06 pm
You just must not have any non-arm processors and non-blank processors on the same CPID, in order to not be disqualified.

Oh, if you have a non arm it can't be on the same account? I didn't know that. I created the account on my desktop even though I'm not using it for computing but since it's in the list my Android phone will not be excluded?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 27, 2018, 12:54:18 pm
You just must not have any non-arm processors and non-blank processors on the same CPID, in order to not be disqualified.
OK. Are these my findings good?:
1. If I want to have ARM based devices unbanked and PC's normal I must have at least two rosettas accounts.
2. It is no problem to join two rosetta acc to one BBP wallet with exec associate. (I didn't try it)
3. My ARM based Galaxy S7 can't be in unbanked acc because it has blank CPU type. (So it will be safer to try every phone outside unbanked acc to not disqualify myself)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on February 27, 2018, 12:59:42 pm
OK. Are these my findings good?:
1. If I want to have ARM based devices unbanked and PC's normal I must have at least two rosettas accounts.
2. It is no problem to join two rosetta acc to one BBP wallet with exec associate. (I didn't try it)
3. My ARM based Galaxy S7 can't be in unbanked acc because it has blank CPU type. (So it will be safer to try every phone outside unbanked acc to not disqualify myself)

If you have a sufficient BBP balance (50K+) there is no benefit to dividing accounts.  In fact, it would hurt you since you'd then have to run two separate wallets to account for the different rosetta accounts (as I understand it).  But the first part I'm confident of, no reason to run "unbanked" if you have 50K+ BBP.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 27, 2018, 01:04:20 pm
If you have a sufficient BBP balance (50K+) there is no benefit to dividing accounts.  In fact, it would hurt you since you'd then have to run two separate wallets to account for the different rosetta accounts (as I understand it).  But the first part I'm confident of, no reason to run "unbanked" if you have 50K+ BBP.
But other reason to be "unbanked" (even if you have 50k) is that you don't have  24/7 server for controller wallet ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 01:08:47 pm
But other reason to be "unbanked" (even if you have 50k) is that you don't have  24/7 server for controller wallet ;)

Thats the main benefit of course.  You dont have to have a BBP balance, and you dont have to run the controller wallet.

Meaning a tiny ARM cell phone in Ethiopia could potentially buy a loaf of bread!  Once we have coinomi!

However I warn you, if anyone finds a way to exploit the unbanked feature, we will most certainly and quickly reward .75 to the unbanked side, and that will take care of the exploit in a jiffy.  For now its 1 * utxo weight * 1 * task weight * RAC = Magnitude for the unbanked.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 27, 2018, 01:26:41 pm
Thats the main benefit of course.  You dont have to have a BBP balance, and you dont have to run the controller wallet.

Meaning a tiny ARM cell phone in Ethiopia could potentially buy a loaf of bread!  Once we have coinomi!

However I warn you, if anyone finds a way to exploit the unbanked feature, we will most certainly and quickly reward .75 to the unbanked side, and that will take care of the exploit in a jiffy.  For now its 1 * utxo weight * 1 * task weight * RAC = Magnitude for the unbanked.
Ok, but how do you join your rosetta acc to wallet in Coinomi (if it will be)? Is it enough to change your "web page" in rosettas acc? I see that there is my controller wallet written.
And I really hope, that no one will exploit it. It would be big disadvantage for "normal" users.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 27, 2018, 01:32:40 pm
Ok, but how do you join your rosetta acc to wallet in Coinomi (if it will be)? Is it enough to change your "web page" in rosettas acc? I see that there is my controller wallet written.
And I really hope, that no one will exploit it. It would be big disadvantage for "normal" users.
So far I dont know of a way - because BOINC stamps the processor type in the distributed network AFTER the machine asks for a certain architecture of work, so we will see if it holds up.  Its going to be pretty apparent because IM going to write reports showing magnitude by CPID, so we will know if any unbanked CPID ever gets past say a 100 magnitude etc.

Anyway, that is most certainly a good question on coinomi.  Right now you would have to be able to type 'éxec associate' in order to associate that thing at home on your laptop!  So I dont have an answer for you.  But what we can do is, if we move into the integration phase with coinomi, I can ask them if we can have a custom feature added!  Maybe we have to pay a couple grand for it.

I have another idea though.  I can make the pool offer free associations for boinc users.  So if coinomi cant do it, we can do it from the pool.  The pool can pass the info into the rpc command and broadcast it and destroy the credentials, so that works!  Problem solved either way...

The GUI of the pool can just display the result of the burn, and the pool can pay the 1bbp fee.

Actually I think to accomodate the unbanked, Ill work on that before March 15th.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 27, 2018, 01:48:16 pm
I have another idea though.  I can make the pool offer free associations for boinc users.  So if coinomi cant do it, we can do it from the pool.  The pool can pass the info into the rpc command and broadcast it and destroy the credentials, so that works!  Problem solved either way...

The GUI of the pool can just display the result of the burn, and the pool can pay the 1bbp fee.

Actually I think to accomodate the unbanked, Ill work on that before March 15th.
That would be great.
Many thing was done (thanks Rob) and it seems that everything is going well.
What else remains to do before March 15?

bottomline :)
Rob thanks for correcting the wallet window size. Now it's great.
And is somewhere a list of all exec commands? (someone asks about it here before)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 06:29:31 am
That would be great.
Many thing was done (thanks Rob) and it seems that everything is going well.
What else remains to do before March 15?

bottomline :)
Rob thanks for correcting the wallet window size. Now it's great.
And is somewhere a list of all exec commands? (someone asks about it here before)

There are a few things left to do, let me see if I can do a diff on what we have created and get back to you.
Today Im going to check the chain integrity - we need to ensure everything we are changing in prod will not affect syncing from zero, or reorganizing.

Regarding the exec commands, most of these are not really intended for the user to run, so I deliberately made them exec commands.  In the long term I envision commands that the user needs, such as exec getboincinfo, should be made into real RPC commands with help.  But nevertheless let me look at which exec commands are relevant.  Out of 20, I think we really should only document a few of these (as most are for diagnostic purposes).


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 07:35:52 am
Here is a list of the PODC related exec commands and definitions.

These will need to be added to the wiki.  I will be adding these to the wiki over the next 7 days.

My plan on the whitepaper is this:  We go live sometime in March with PODC, primarily to unplug the botnet and ensure our valuable emissions are going to researchers.  While that process is transitioning, I finish the whitepaper, send it to Luke who helps mark it up (this makes it look more professional), then I will send it in for peer review (this process could take a Year), so I look at this as something we do in the backgorund while we are live on PODC.

Remember, the people at the Journal know very little about blockchain programming - they are going to be asking Me questions about the interfaces, so I hope that clears up any confusion on why its being done in this order.

Exec RPC Commands related to PODC:

exec podcdifficulty
- PODC Difficulty is derived by how many concurrent researchers participated in the Last superblock * Their Respective Magnitudes.  This gives an idea how hard it will be to earn money on the PODC side in the next superblock.

exec podcupdate
- This forces a podc update.  Useful if you left your machine off by accident for a long period of time and your task weight or utxo weight dropped to zero.

exec associate
- This associates a CPID with a Biblepay public key.

exec leaderboard
- This shows the respective Research CPID participants and corresponding magnitudes as of the last superblock descending by magnitude.

exec getboincinfo
- This shows most of the important boinc/rosetta metrics, allowing a researcher to diagnose integration issues, and allows one to verify their current magnitude and magnitude trend.

exec unbanked
- This report shows a list of CPIDs who are unbanked.  Unbanked means CPIDs with 100% of the RAC originating from ARM devices, and none of the RAC originating from Non-Arm devices.  **Note this report is currently showing a list of Rosetta IDs not cpids, I will fix this report today to show one CPID per row**

exec sins
- This is a report on 40 sins that may send you to Hell if you are unrepentant.


I will go into more detail as I merge these into the wiki.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 09:40:44 am
Mini update on the Zotac vs the Ryzen:  Dont give up on the Zotac, its really starting to shine now, believe it or not.
Zotac RAC 460, Ryzen RAC 710!  That means zotac is doing 65% of the RAC of a ryzen, yet it costed less than half and its wattage is 1/10th that of the ryzen.  It may actually prove to be "the winner" in the end...   
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 28, 2018, 11:22:15 am
Mini update on the Zotac vs the Ryzen:  Dont give up on the Zotac, its really starting to shine now, believe it or not.
Zotac RAC 460, Ryzen RAC 710!  That means zotac is doing 65% of the RAC of a ryzen, yet it costed less than half and its wattage is 1/10th that of the ryzen.  It may actually prove to be "the winner" in the end...

Let's see if my estimate is accurate after 4 weeks:
My computer with an ATOM processor gets about half the CPU mark as the CPU you have in your computer and has the same number or cores. Your Ryzen 1700x estimation comes from comparing it to 2 different CPUs with known credits/day and by using the scores from cpubenchmark.net. The predictions are for full CPU usage without any interference.

Zotac: 1,800RAC max
1700x: 17,305RAC max
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 11:34:53 am
Let's see if my estimate is accurate after 4 weeks:
My computer with an ATOM processor gets about half the CPU mark as the CPU you have in your computer and has the same number or cores. Your Ryzen 1700x estimation comes from comparing it to 2 different CPUs with known credits/day by using the scores from cpubenchmark.net. The predictions are for full CPU usage without any interference.

Zotac: 1,800RAC max
1700x: 17,305RAC max

Ok cool, we will see.


Who wants to test exec associate?  To refresh everyones memory it used to allow you to know if INVALID_CREDENTIALS works, Or ALREADY_IN_CHAIN, or the ability to re-associate with a new wallet. Could someone please thoroughly test those at least those 3 things?

Btw, to know if re-association works:  run exec datalist dcc first, copy the CPIDs row information to notepad.  Note how a certain BBP public address is associated with the CPID at that time.  Then reassociate the CPID with a new public biblepay key (by replacing wallet.dat with a new wallet).  Then wait 6 confirms, then type exec datalist dcc again.  Verify that Only One Row exists for the cpid (as last most recent row wins in BBP) also verify the new Address is now associated with the CPID.  Then if you want maybe put it back to your old wallet if its a good cpid.

Youll need 10 BBP in the new wallet to perform reassociations.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 11:37:49 am
Unbanked report is now fixed for next version, we are getting there!

Any concerns by anyone, or anything anyone wants to ask, or double check, or any reservations to going live on March 20th?

Im thinking maybe we test another 7 days and ensure "quietness abounds" then we give CCEX and SouthXChange a 10 day upgrade notice.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 28, 2018, 12:04:52 pm
Mini update on the Zotac vs the Ryzen:  Dont give up on the Zotac, its really starting to shine now, believe it or not.
Zotac RAC 460, Ryzen RAC 710!  That means zotac is doing 65% of the RAC of a ryzen, yet it costed less than half and its wattage is 1/10th that of the ryzen.  It may actually prove to be "the winner" in the end...
Rob i think that something is wrong with your Ryzen.
Look at e.g. Togos or Klondikes comupters. They have more Ryzens 1700 and theirs Ryzens RAC is a lot higher than yours. And it is not caused by time... because they starts to "compute" with them only few days ago. And it looks that you have more powerful CPU (1700x).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 12:07:34 pm
Rob i think that something is wrong with your Ryzen.
Look at e.g. Togos or Klondikes comupters. They have more Ryzens 1700 and theirs Ryzens RAC is a lot higher than yours. And it is not caused by time... because they starts to "compute" with them only few days ago. And it looks that you have more powerful CPU (1700x).

You know that makes sense to me, because this thing is a monster, let me check it out and see if its going to sleep... I might have accidentally left it in auto-sleep mode.  Another possibility is its running windows 7, and I have a warning on the screen:  unsupported operating system (LOL).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 28, 2018, 12:38:30 pm
I've attached an Excel file to show percentage increase of RAC over the weeks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 28, 2018, 01:01:29 pm
Ok cool, we will see.


Who wants to test exec associate?  To refresh everyones memory it used to allow you to know if INVALID_CREDENTIALS works, Or ALREADY_IN_CHAIN, or the ability to re-associate with a new wallet. Could someone please thoroughly test those at least those 3 things?

Btw, to know if re-association works:  run exec datalist dcc first, copy the CPIDs row information to notepad.  Note how a certain BBP public address is associated with the CPID at that time.  Then reassociate the CPID with a new public biblepay key (by replacing wallet.dat with a new wallet).  Then wait 6 confirms, then type exec datalist dcc again.  Verify that Only One Row exists for the cpid (as last most recent row wins in BBP) also verify the new Address is now associated with the CPID.  Then if you want maybe put it back to your old wallet if its a good cpid.

Youll need 10 BBP in the new wallet to perform reassociations.
Ok. I've tested it.
First associate without force and it works: ALREADY ON CHAIN
Tan with force (at block 11320): Successfully advertised DC-Key. ....
after 6 blocks changed my address from yfvTaGZakXWsLqyTCSZRG3kqabY6WYhFym to yZYt9boPur9vMLC5CPrWuiwXQ2XzzpXMVJ
with exec podcupdate had UTXO and taskweight at 100 in a block :)
magnitude at 0.
checked with exec datalist dcc and looks OK.
BTW you can check your wallet easier in rosetass profile URL (it changed too) :)
Then jumped back to my old testnet wallet without problem. Thanks God it works without problem :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on February 28, 2018, 01:05:58 pm
On the Topic of Ryzen 7 1700 (3.0GHz),

apparently they can go up to 4.1GHz or so and I think thats what the Top Ryzen 7 1700 machines on Rosetta are using to get 10k RAC
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3194869
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3291011

I have both of my ryzens now overclocked to 3.8GHz

and for the i7 2600k I bumped it from 3.4GHz to 3.8GHz yesterday.

I have no experience overclocking so this has been interesting
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 01:42:58 pm
I've attached an Excel file to show percentage increase of RAC over the weeks.

This is a relatively impressive spreadsheet, in that I see that it uses the correct exponent function (2.71) that BOINC uses and the decay formula appears to be correct, but I see a few bugs in the sheet that causes it to lag over time:

- This does not take into consideration the compounding effect of RAC.  RAC is compounded at least once per day (roughly) when a host solves a WU.  For example, lets say machine A had zero rac, and worked for 24 hours to solve a 100 RAC workunit, once per day.  That means it would check in One Day after epoch, 86400 in since inception with 100 credits, and while those 100 are granted, its first decay point would be ONE day, its RAC IN would be the age of its PRIOR RAC (of 0).  On Day 2, its prior rac of 100 would be 2 days old and its new 100 credit would be 1 day old.  With a grand total of 189 rac on day 2.


So you must add a running total to this to show the prior days RAC total, and the new total so that they always are able to be decayed separately per the formula (Not 0 for one and the grand total for the IN).

- If the machine is crunching 100 new Credits per day, then the grand total in 4 weeks must be a RAC of 903 (not 100).  100 Credits per day means 100+100+100... = 500 RAC on week 1...  Not 50 rac on week 1.

So I think if you add a running total for Prior days End and New days begin it will match boinc. 
A 100 RAC input should yield a 920~ or so RAC at the end of the 31 day period...

Great job!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 01:45:03 pm
Ok. I've tested it.
First associate without force and it works: ALREADY ON CHAIN
Tan with force (at block 11320): Successfully advertised DC-Key. ....
after 6 blocks changed my address from yfvTaGZakXWsLqyTCSZRG3kqabY6WYhFym to yZYt9boPur9vMLC5CPrWuiwXQ2XzzpXMVJ
with exec podcupdate had UTXO and taskweight at 100 in a block :)
magnitude at 0.
checked with exec datalist dcc and looks OK.
BTW you can check your wallet easier in rosetass profile URL (it changed too) :)
Then jumped back to my old testnet wallet without problem. Thanks God it works without problem :)

Wow this is awesome, Thanks!!!!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob A. on February 28, 2018, 01:52:08 pm
On the Topic of Ryzen 7 1700 (3.0GHz),

apparently they can go up to 4.1GHz or so and I think thats what the Top Ryzen 7 1700 machines on Rosetta are using to get 10k RAC
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3194869
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3291011

I have both of my ryzens now overclocked to 3.8GHz

and for the i7 2600k I bumped it from 3.4GHz to 3.8GHz yesterday.

I have no experience overclocking so this has been interesting

Wow those are beasts!  So I should be looking for 10,000 RAC out of this baby.  Ok, Ill keep it running, not going to overclock it til we are in prod LOL.

I think it was the sleep setting in win7: the default was to sleep after 30 minutes.  Its making more RAC than the Zotac sleeping and I only disturbed it once per day to wake it up by accident, so much for green power...  Well at least the solar project might be fun in the future.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 28, 2018, 01:57:50 pm
Wow those are beasts!  So I should be looking for 10,000 RAC out of this baby.  Ok, Ill keep it running, not going to overclock it til we are in prod LOL.

I think it was the sleep setting in win7: the default was to sleep after 30 minutes.  Its making more RAC than the Zotac sleeping and I only disturbed it once per day to wake it up by accident, so much for green power...  Well at least the solar project might be fun in the future.

I'm actually surprised that it only gets 10K RAC, my cpu which has a lower benchmark score is getting 10K credits a day.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on February 28, 2018, 02:02:37 pm