Bible Pay

Archives => TestNet Discussion Archive => Topic started by: Rob Andrews on February 06, 2018, 04:00:36 PM

Title: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 [email protected] XXXXXXXXX
{
  "Command": "associate",
  "E-Mail": "[email protected]",
  "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 Andrews on February 06, 2018, 11:07:54 PM
./biblepay-cli exec associate [email protected] XXXXXXXXX
{
  "Command": "associate",
  "E-Mail": "[email protected]",
  "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 Andrews 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: 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: 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 Andrews 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: Rob Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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. [email protected].
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews 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. [email protected].

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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: Rob Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: Rob Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: Rob Andrews 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 Andrews 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: Rob Andrews 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 Andrews 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: Rob Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: Rob Andrews 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 Andrews 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: 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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: 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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 Andrews 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
Wow this is awesome, Thanks!!!!
Payout from last superblock without problem in old wallet with old magnitude... nice :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 28, 2018, 02:28:53 PM
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!

Let's clear up one thing first, when you say 100 RAC input, do you mean you are actually RECEIVING 100 credits per day? Because it doesn't make any sense if the RAC would be 920 if your only receiving 100 credits per day. Your RAC should be 100.

The RAC on T-COMPUSTICK is actually pretty close to what the excel is giving me. I receive about 1080 credits/day and I'm getting a RAC of 873 on the website and 899 on the excel file. The computer has been on for about 18 days.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 28, 2018, 02:32:28 PM
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

Revised quote:
Zotac: 1,800 RAC max
1700x: 15,464 RAC max

Updated because I was using a wrong RAC base number in my calculation for the 1700x.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on February 28, 2018, 04:19:40 PM
Let's clear up one thing first, when you say 100 RAC input, do you mean you are actually RECEIVING 100 credits per day? Because it doesn't make any sense if the RAC would be 920 if your only receiving 100 credits per day. Your RAC should be 100.

The RAC on T-COMPUSTICK is actually pretty close to what the excel is giving me. I receive about 1080 credits/day and I'm getting a RAC of 873 on the website and 899 on the excel file. The computer has been on for about 18 days.
Sorry, I meant if you are receiving 1000 per day, Yes you would have a RAC of 940 or so by the 4th week yes, Close to what the sheet says.

But without compounding and tracking each days old rac, your sheet shows that on the 14th day the user would only have accrued 75% of the RAC, when in reality it would be closer to 83% (due to compounding).  That would put the sheet on par with what I would expect to have as a researcher and on par with what the boinc formula is doing when you plug in each days old rac plus each days new rac into the function.

And thats why I made a comment a week ago about being able to compare two machines as long as they were both on for 14 days- for all intents and purposes the RAC has stabilized after that point and they can be compared.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on February 28, 2018, 04:58:34 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?

sorry, I was off for few days, but I associated my cpid weeks ago:

{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "yY6uBmPyks4VEBjZ18Kzw1LUNiTewAXSr3",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422182,

Will continue running boinc on phone+tablet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on February 28, 2018, 05:40:00 PM
sorry, I was off for few days, but I associated my cpid weeks ago:

{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "yY6uBmPyks4VEBjZ18Kzw1LUNiTewAXSr3",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422182,

Will continue running boinc on phone+tablet.


I dont see you in the chain; were up to 1.0.9.5 (had a couple mandatories that erased the chain) - Im looking in exec datalist dcc and dont see you - were on block 11533 please see if synced?
Blockhash for 11500: ccb74250c378c051ff560e40fcfe4bcb194f965b41eb595bb4a7af9c5192dd5e

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 28, 2018, 07:05:15 PM
Sorry, I meant if you are receiving 1000 per day, Yes you would have a RAC of 940 or so by the 4th week yes, Close to what the sheet says.

But without compounding and tracking each days old rac, your sheet shows that on the 14th day the user would only have accrued 75% of the RAC, when in reality it would be closer to 83% (due to compounding).  That would put the sheet on par with what I would expect to have as a researcher and on par with what the boinc formula is doing when you plug in each days old rac plus each days new rac into the function.

And thats why I made a comment a week ago about being able to compare two machines as long as they were both on for 14 days- for all intents and purposes the RAC has stabilized after that point and they can be compared.

I went through the code shown on the wiki and it doing exactly what the posted formula does. On my spreadsheet, I did not use the old RAC because it doesn't matter since the new credit per day is the same everyday, it would have mattered if the credits/per day was changing. I've updated the spreadsheet but it still shows 75% at 14 days. Are you saying the compounding is not in the formula?

Code: [Select]
void update_average(
    double work_start_time,         // when new work was started
                                    // (or zero if no new work)
    double work,                    // amount of new work
    double half_life,
    double& avg,                    // average work per day (in and out)
    double& avg_time                // when average was last computed
) {
    double now = dtime();

    if (avg_time) {
        // If an average R already exists, imagine that the new work was done
        // entirely between avg_time and now.
        // That gives a rate R'.
        // Replace R with a weighted average of R and R',
        // weighted so that we get the right half-life if R' == 0.
        //
        // But this blows up if avg_time == now; you get 0*(1/0)
        // So consider the limit as diff->0,
        // using the first-order Taylor expansion of
        // exp(x)=1+x+O(x^2).
        // So to the lowest order in diff:
        // weight = 1 - diff ln(2) / half_life
        // so one has
        // avg += (1-weight)*(work/diff_days)
        // avg += [diff*ln(2)/half_life] * (work*SECONDS_PER_DAY/diff)
        // notice that diff cancels out, leaving
        // avg += [ln(2)/half_life] * work*SECONDS_PER_DAY

        double diff, diff_days, weight;

        diff = now - avg_time;
        if (diff<0) diff=0;

        diff_days = diff/SECONDS_PER_DAY;
        weight = exp(-diff*M_LN2/half_life);

        avg *= weight;

        if ((1.0-weight) > 1.e-6) {
            avg += (1-weight)*(work/diff_days);
        } else {
            avg += M_LN2*work*SECONDS_PER_DAY/half_life;
        }
    } else if (work) {
        // If first time, average is just work/duration
        //
        double dd = (now - work_start_time)/SECONDS_PER_DAY;
        avg = work/dd;
    }
    avg_time = now;
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on February 28, 2018, 09:31:25 PM
I went through the code shown on the wiki and it doing exactly what the posted formula does. On my spreadsheet, I did not use the old RAC because it doesn't matter since the new credit per day is the same everyday, it would have mattered if the credits/per day was changing. I've updated the spreadsheet but it still shows 75% at 14 days. Are you saying the compounding is not in the formula?

Code: [Select]
void update_average(
    double work_start_time,         // when new work was started
                                    // (or zero if no new work)
    double work,                    // amount of new work
    double half_life,
    double& avg,                    // average work per day (in and out)
    double& avg_time                // when average was last computed
) {
    double now = dtime();

    if (avg_time) {
        // If an average R already exists, imagine that the new work was done
        // entirely between avg_time and now.
        // That gives a rate R'.
        // Replace R with a weighted average of R and R',
        // weighted so that we get the right half-life if R' == 0.
        //
        // But this blows up if avg_time == now; you get 0*(1/0)
        // So consider the limit as diff->0,
        // using the first-order Taylor expansion of
        // exp(x)=1+x+O(x^2).
        // So to the lowest order in diff:
        // weight = 1 - diff ln(2) / half_life
        // so one has
        // avg += (1-weight)*(work/diff_days)
        // avg += [diff*ln(2)/half_life] * (work*SECONDS_PER_DAY/diff)
        // notice that diff cancels out, leaving
        // avg += [ln(2)/half_life] * work*SECONDS_PER_DAY

        double diff, diff_days, weight;

        diff = now - avg_time;
        if (diff<0) diff=0;

        diff_days = diff/SECONDS_PER_DAY;
        weight = exp(-diff*M_LN2/half_life);

        avg *= weight;

        if ((1.0-weight) > 1.e-6) {
            avg += (1-weight)*(work/diff_days);
        } else {
            avg += M_LN2*work*SECONDS_PER_DAY/half_life;
        }
    } else if (work) {
        // If first time, average is just work/duration
        //
        double dd = (now - work_start_time)/SECONDS_PER_DAY;
        avg = work/dd;
    }
    avg_time = now;
}

It looks like this sheet is exactly accurate.

I believe I need to update my prior RAC assessment to say "The lions share of RAC is realized by day 20" (with 86%), and very little (13% happens) between day 21 and 40.

I just added the rac decay function with in and out to the next version of the client and it agrees with your latest spreadsheet.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on February 28, 2018, 10:08:55 PM
It looks like this sheet is exactly accurate.

I believe I need to update my prior RAC assessment to say "The lions share of RAC is realized by day 20" (with 86%), and very little (13% happens) between day 21 and 40.

I just added the rac decay function with in and out to the next version of the client and it agrees with your latest spreadsheet.

I'm glad we finally got it sorted out!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 06:27:11 AM
I'm glad we finally got it sorted out!
Me too.

And that means what 616West originally said was correct on his part, sorry about that 616.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 01, 2018, 07:30:45 AM
Me too.

And that means what 616West originally said was correct on his part, sorry about that 616.

Since a few days I was running my android phone on a separate CPID to test the 'unbanked' function, but forgot to join the Biblepay-team. Oops  :o

I joined now, so we'll see how it goes.

About the implementation in March Rob: I'm all for intensive testing to make sure that no bugs escape us. Do you think it would be beneficial to get more people testing?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 07:57:13 AM
Since a few days I was running my android phone on a separate CPID to test the 'unbanked' function, but forgot to join the Biblepay-team. Oops  :o

I joined now, so we'll see how it goes.

About the implementation in March Rob: I'm all for intensive testing to make sure that no bugs escape us. Do you think it would be beneficial to get more people testing?

Yes, the more the merrier.  Ill post something in the other forum now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 08:02:00 AM
I took a look at the logs on my two testnet nodes and dont see anything bad.  Other than a lot of unecessary logging, which I added switches for and removed (debugpodc=true).  And some Sanctuary mnpyaments logging was removed.

Can't find any other bugs... Lets hope we have some more volunteers help us asap.

Yes Jaap lets also not forget to verify your unbanked flag on my sanc later, let me know after you receive an unbanked payment.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 01, 2018, 08:26:01 AM
I took a look at the logs on my two testnet nodes and dont see anything bad.  Other than a lot of unecessary logging, which I added switches for and removed (debugpodc=true).  And some Sanctuary mnpyaments logging was removed.

Can't find any other bugs... Lets hope we have some more volunteers help us asap.

Yes Jaap lets also not forget to verify your unbanked flag on my sanc later, let me know after you receive an unbanked payment.

Great! Let's indeed hope we can get some more volunteers up here. I will let you know if I receive an unbanked payment :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 08:40:34 AM
Im compiling 1095c for windows now.

For existing testers: No need to upgrade, this next version just removes the logging and adds the exec racdecay function that matches T-Mikes spreadsheet.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 01:53:19 PM
Im compiling 1095c for windows now.

For existing testers: No need to upgrade, this next version just removes the logging and adds the exec racdecay function that matches T-Mikes spreadsheet.

Ok, windows 1095c is now out there  -   so now everyone can test the most recent version!


Lets Go PODC!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 01, 2018, 02:50:54 PM
Any concerns by anyone, or anything anyone wants to ask, or double check, or any reservations to going live on March 20th?
I was thinking about that and I remembered that we wrote about these thing later:
1. have PoDC only wallet unlock option
2. auto setgenerate true 1 on PoDC (maybe both can be cumulated in 1 command or settings option)
3. and those different icons for different tx
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 03:04:46 PM
I was thinking about that and I remembered that we wrote about these thing later:
1. have PoDC only wallet unlock option
2. auto setgenerate true 1 on PoDC (maybe both can be cumulated in 1 command or settings option)
3. and those different icons for different tx

I like #2 and #3, but on #1, I dont really like the way the POS coins implement that checkbox.
The problem with the implementation is it gives the user a false sense of security (when there is none).
If we add the option to unlock for staking only, then the user thinks their funds are secure (just because *they* cant spend them).
But in reality the whole point of making an encrypted wallet is to keep a hacker from stealing it.

So what you have in that case is someone moving 2 million biblepay to the controller , encrypting the wallet, clicking "unlock for staking only" and thinking they are secure.  Then when they get hacked, the hacker sends the whole 2 million out.

Otoh, when we just leave it the way it is, the user is forced to store the 2million in a cold wallet and leave only 50K on the controller.  OR manually take the risk and unlock the wallet.  This is far better , the way it is, imo.

I have not been able to think of a better solution to this.  It is possible to pull a hash from somewhere any make biblepay unlock the wallet, send the podc, and lock the wallet, but where is it going to pull the hash from if it does not open up a hole for a hacker to be able to see the file to find the hash?  Its not an easy issue to solve.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 01, 2018, 03:38:43 PM
OK. I understand.
I didn't know that it is only "false sense of security".
So why we have "Only for mixing via PrivateSend" option?
Is it diffent?
And is there option to unlock wallet via command walletpassphrase for "infinity" not only for written time?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 03:55:59 PM
OK. I understand.
I didn't know that it is only "false sense of security".
So why we have "Only for mixing via PrivateSend" option?
Is it diffent?
And is there option to unlock wallet via command walletpassphrase for "infinity" not only for written time?

Only for mixing is the same : Only a boolean in the code protects the funds from being stolen.

Option to unlock forever:  just the option of 9999999 currently.

So I still cant think of anything better than asking the user for the password on bootup, we could say "Enter your password for PODC Updates if you wish>" (if the wallet is encrypted), not unlock the wallet, store the password in an encrypted memory variable using Secure String (thats suppoedly a way to be unable to read the memory by a hacker), then in PODC update we unlock send and lock.     Semi secure..... possibly... 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 01, 2018, 04:29:10 PM
Only for mixing is the same : Only a boolean in the code protects the funds from being stolen.

Option to unlock forever:  just the option of 9999999 currently.

So I still cant think of anything better than asking the user for the password on bootup, we could say "Enter your password for PODC Updates if you wish>" (if the wallet is encrypted), not unlock the wallet, store the password in an encrypted memory variable using Secure String (thats suppoedly a way to be unable to read the memory by a hacker), then in PODC update we unlock send and lock.     Semi secure..... possibly...
Yes it would be good option but it can be annoying for some users. E.g. if you run your wallet on different PC.
I want to have it secure, because those 50k is all what I have now :D but it looks, that best solution is to leave it as it is.
And after unlock command just clear bash history. In windows wallets there is no that risk to "read" it so easy.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 01, 2018, 04:46:03 PM
Yes it would be good option but it can be annoying for some users. E.g. if you run your wallet on different PC.
I want to have it secure, because those 50k is all what I have now :D but it looks, that best solution is to leave it as it is.
And after unlock command just clear bash history. In windows wallets there is no that risk to "read" it so easy.

Well Im not too worried about annoying the user.  Its only when they reboot the wallet.  Once per session.
We can add a flag that turns off the feature (like disablepodcunlock=true in the config).

Anyway I went ahead and made the wallet prompt you for your password when you boot, if its locked, encrypted and running in PODC mode.

Im not done with the feature yet - I still need to store it in encrypted memory and make it actually perform the auto unlock when a PODC occurs.

On bash though, does bash record keys typed into a password box on the GUI?  This is a qt feature only so it should not go into bash history.

I havent even thought about headless.  On headless you can write a script.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Damian on March 01, 2018, 04:50:52 PM
Hi all,
    I've no idea on setting up a MN for testnet, but I can put my laptop in testnet as a miner if that helps??
 I've dloaded bionc and joined the BBP team, so wouldn't take much (dload new wallet). Let me know if I can be of any use?
   Damian
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 01, 2018, 05:54:51 PM
Just confirming, for PODC UTXO Reward Chart (Staking),
where you need 50,000 BBP in a wallet to receive 100% rewards from PODC
Chart here: http://wiki.biblepay.org/index.php?title=Distributed_Computing#Proof-of-Distributed-Computing

The coins have to be in an unlocked wallet? (specifically the wallet that has the CPID/Burn with 1 mining thread running)

Thats not toooo bad, just a little extra work to secure your coins,
could just use another PC or $5/month cloud machine and periodically send rewards to your main encrypted wallet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 01, 2018, 08:42:33 PM
Hi all,
    I've no idea on setting up a MS for testnet, but I can put my laptop in testnet as a miner if that helps??
 I've dloaded bionc and joined the BBP team, so wouldn't take much (dload new wallet). Let me know if I can be of any use?
   Damian

If you have BOINC set up, download the wallet and start mining by going into the debug tool and typing "setgenerate true 1". Once you have some test BBP, go to the Distributed Computing tab and associate your BOINC account with the Biblepay network.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Damian on March 02, 2018, 03:17:43 AM
Hi T-Mike,
  I've dloaded the latest wallet, and "setgenerate true 1", I'm not sure where the DC tab is?? is it in Bionc?
Also is the config I'm using suitable?

addnode=node.biblepay.org
gen=1
genproclimit=3
pool=https://pool.biblepay.org
workerid=bananaboyjoe

Thanks,
    Damian
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 02, 2018, 03:23:53 AM
I'm getting my first 'unbanked' transactions  8)

Code: [Select]
10:18:16

exec getboincinfo


10:18:19

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422217,
  "NextSuperblockHeight": 12969,
  "NextSuperblockBudget": 1339285,
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 57.44,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 15044,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 100,
  "Total_RAC": 57.44,
  "Total Payments (One Day)": 10465,
  "Total Payments (One Week)": 15780,
  "Total Budget (One Day)": 13474430,
  "Total Budget (One Week)": 85599588,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 64,
  "Superblock List": "12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514,8415,8217,8118,8019,7920,7821,7722,7623,7524,7425,7326,7227,7128,7029,6930,6831,6732,6633,6534,6435,6336,6237,6138,6039,5940,5841",
  "Last Superblock Height": 12870,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 2606,
  "Magnitude (One-Day)": 0.7766562296141655,
  "Magnitude (One-Week)": 0.184346681668608
}

Code: [Select]
Status: 278 confirmations
Date: 02-03-18 03:54
Source: Generated
Credit: 2647.47000000 tBiblepay
Net amount: +2647.47000000 tBiblepay

Height: 12672
Difficulty: 32.423041
Time: 03-02-2018 02:54:07
Subsidy: 5820.7679

:
Transaction ID: dfd8e518f41e3063882790ff25fd164298a988ca746a9ccc4c38c9fec283c673-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2647.47000000 tBiblepay

Transaction:
CTransaction(hash=dfd8e518f4, ver=1, vin.size=1, vout.size=13, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0280310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=21032833a45709cf01a2fd9db2c698)
    CTxOut(nValue=319900.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=46162.74000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28732.44000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=576463.14000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=87702.49000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=148849.65000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21582.93000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=24270.72000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23907.87000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=54696.47000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4367.65000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2647.47000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Code: [Select]
Status: 181 confirmations
Date: 02-03-18 06:09
Source: Generated
Credit: 2606.94000000 tBiblepay
Net amount: +2606.94000000 tBiblepay

Height: 12771
Difficulty: 36.267757
Time: 03-02-2018 05:09:05
Subsidy: 5820.7679

:
Transaction ID: 1d831b71fae895a8d7fa169ed3429179e937116675a8ccb2cfcae4163b2d6022-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=1d831b71fa, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02e3310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=210334fe421aa9256e0bba14d9941e)
    CTxOut(nValue=314647.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=45393.08000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28259.81000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=566983.49000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=86257.60000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=146405.45000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21997.77000000, scriptPubKey=76a9146ec0f5e17278e46595ed1fb3)
    CTxOut(nValue=21231.81000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=23879.07000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23516.25000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=53805.18000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4300.11000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2606.94000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Code: [Select]
Status: 82 confirmations
Date: 02-03-18 08:33
Source: Generated
Credit: 2606.94000000 tBiblepay (matures in 20 more blocks)
Net amount: 0.00000000 tBiblepay

Height: 12870
Difficulty: 36.267757
Time: 03-02-2018 07:33:43
Subsidy: 5819.8947

:
Transaction ID: 70d0bb8c35c02ca805654e27fe8193fe04dbce63e10f8186a01016ba438d11bb-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=70d0bb8c35, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0246320101)
    CTxOut(nValue=5819.89466250, scriptPubKey=2103272e1da0c3bb0196a37b6ebed0)
    CTxOut(nValue=314647.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=45393.08000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28259.81000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=566983.49000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=86257.60000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=146405.45000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21997.77000000, scriptPubKey=76a9146ec0f5e17278e46595ed1fb3)
    CTxOut(nValue=21231.81000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=23879.07000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23516.25000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=53805.18000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4300.11000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2606.94000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 02, 2018, 03:33:32 AM
Hi T-Mike,
  I've dloaded the latest wallet, and "setgenerate true 1", I'm not sure where the DC tab is?? is it in Bionc?
Also is the config I'm using suitable?

addnode=node.biblepay.org
gen=1
genproclimit=3
pool=https://pool.biblepay.org
workerid=bananaboyjoe

Thanks,
    Damian

Hi Damian, thanks for helping :)

I think you are using your wallet/client in 'production mode' right now. You need to be in testnet mode to be able to see the DC-tab right now. If you're in Windows, to start your client in testnet mode, enter the following in your command-prompt :

cd c:\program files (x86)\biblepaycore
biblepay-qt -testnet

You can also start in testnet-mode by adding a command in your biblepay-conf, but I don't know what it is precisely.

Once your wallet is started, you are able to see the 'distributed computing' tab, where you can enter your rosetta@home credentials. You can then open tools->debug console and type 'setgenerate true 1'. This will make sure you're mining on the testnet.

I hope I'm clear enough. If not, just ask :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Damian on March 02, 2018, 04:14:15 AM
Thanks Jaapgvk   
  I'll get on to it within the hour, if I've any problems I'll let you know,
    Damian
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 07:52:07 AM
Just confirming, for PODC UTXO Reward Chart (Staking),
where you need 50,000 BBP in a wallet to receive 100% rewards from PODC
Chart here: http://wiki.biblepay.org/index.php?title=Distributed_Computing#Proof-of-Distributed-Computing

The coins have to be in an unlocked wallet? (specifically the wallet that has the CPID/Burn with 1 mining thread running)

Thats not toooo bad, just a little extra work to secure your coins,
could just use another PC or $5/month cloud machine and periodically send rewards to your main encrypted wallet.

Yes, correct, the issue is in order to exercise ones UTXOWeight, the core must be able to "stake" up to 50K in a coinstake, at least once per day to associate its tasks with its UTXO coins.  So of course that means if the wallet is encrypted and locked, the core cant create a coinstake, and cant sign CPIDs either.

So let me cover the most Dangerous aspect of this so you can get a feel for the attack vectors:
Lets pretend you have 6.5 MILLION BBP, and 4 cold sanctuaries and you want to stake from the controller wallet on your home PC.
So you encrypted and locked the home wallet. 
Now you unlock the wallet with a passphrase for 9999 seconds so that PODC update can work.
The attack vectors are:

- Physical security - an intruder - a Wife, Husband, Sister, Brother, Or physical break in gains access to the machine and Sends coins out of the machine while the machine is unlocked
- Firewall security - a hacker breaches the firewall, compromises the password of the RPC port - and sends coins out with an RPC command
- Compromised Machine - Virus - A virus or botnet compromises the machine, and sends coins out of the running wallet - This type of attack could also copy the entire wallet.dat off the machine
- Fradulent Software Copy - A Very advanced virus, designed to mutate memory, is embedded on the machine altering the running state of the code - forcing the wallet to send out BBP
- Fraudulent Memory Reader - A Very advanced virus, copies the running memory of the machine and attempts to scan it for private keys in memory

As you can see with these attack vectors, a locked wallet would have prevented : Physical security, Firewall Security, Compromised Machine, Fraudulent Software and Fraudulent Memory Reader.   A locked for Staking wallet would prevent: physical security, firewall, compromised machine, but possibly would fail on the last two.

I ended up going with a feature that pops up when the user boots - asking for their wallet password (if they desire) and can be disabled with a config setting.  It stores the wallet password in a SecureString in memory (thats sort of like a non readable encrypted string that prevents reading the string from memory since it is not clear text), then when the wallet needs to Sign a CPID OR send a PODCUpdate, If that string is populated with a value, it unlocks the wallet, does the operation then locks the wallet again.

So this is as strong as I can make it with as much convenience as I can imagine, then for those who do not wish to break up the controller wallet into two pieces can still feel relatively at ease as long as they are running the binary.  In my case myself Ill probably use it, for my sanctuary set up on my home windows wallet, since I still need the ability to easily vote with the locked funds, maintain my start-stop of my sancs, its of higher security for me to keep that wallet available at home than on any rented VPS service. 

But yes if you sent the 50K out to a VPS, you would need your CPID rewards to go to that VPS, and then you could leave the wallet unencrypted/unlocked in the VPS.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 02, 2018, 08:01:04 AM
I have 5 CPIDs attached to my wallet, one of them is showing 0 for both weights.

"95a79cd5829e8315b0b946709930df18_RAC": 527.11,
"95a79cd5829e8315b0b946709930df18_TEAM": 15044,
"95a79cd5829e8315b0b946709930df18_TaskWeight": 0,
"95a79cd5829e8315b0b946709930df18_UTXOWeight": 0,
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 08:19:17 AM
I have 5 CPIDs attached to my wallet, one of them is showing 0 for both weights.

"95a79cd5829e8315b0b946709930df18_RAC": 527.11,
"95a79cd5829e8315b0b946709930df18_TEAM": 15044,
"95a79cd5829e8315b0b946709930df18_TaskWeight": 0,
"95a79cd5829e8315b0b946709930df18_UTXOWeight": 0,


I dont see how thats happening - can you please double check your synced?  After that run this first, log output then restart client and log output?

From my node I see your 95a utxoweight @ 13:59, wait thats just 30 minutes ago:
exec datalist utxoweight:

"95A79CD5829E8315B0B946709930DF18 (03-02-2018 13:59:34)": "100"


I think what happened is you ran the command when your utxo weight ran out, then it synced within 6 blocks after....

You can find out by looking for your last PODC Update Before 3-2-2018 @ 13:59 UTC, But it must contain the XML for the CPID: 95A.

Meaning you would have to look at the showblock blocknumber, then the coinbase transaction vout 0.


If its showing up now in exec datalist utxoweight, then I think we just had a 24 hour lag between PODC update for that One CPID.

EDIT:  I forcefully created a contract on my hot sanc to see your 95a status, and it did pick up 100% for both weights. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 08:26:00 AM
I'm getting my first 'unbanked' transactions  8)

Code: [Select]
10:18:16

exec getboincinfo


10:18:19

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422217,
  "Next
  "Total_RAC": 57.44,
  "Total Payments (One Day)": 10465,
  "Total Payments (One Week)": 15780,
  "Total Budget (One Day)": 13474430,
  "Total Budget (One Week)": 85599588,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 64,
  "Superblock List":
  "Magnitude (One-Day)": 0.7766562296141655,
  "Magnitude (One-Week)": 0.184346681668608
}

Code: [Select]
Status: 278 confirmations
Date: 02-03-18 03:54
Source: Generated
Credit: 2647.47000000 tBiblepay
Net amount: +2647.47000000 tBiblepay

Height: 12672
Difficulty: 32.423041
Time: 03-02-2018 02:54:07
Subsidy: 5820.7679

:
Transaction ID: dfd8e518f41e3063882790ff25fd164298a988ca746a9ccc4c38c9fec283c673-000




Debug information

Credit: 2647.47000000 tBiblepay

Transaction:
CTransaction(hash=dfd8e518f4, ver=1, vin.size=1, vout.size=13, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0280310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=21032833a45709cf01a2fd9db2c698)
    CTxOut(nValue=319900.42000000, sc
    CTxOut(nValue=21582.93000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=24270.72000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23907.87000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=54696.47000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4367.65000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2647.47000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Code: [Select]
Status: 181 confirmations
Date: 02-03-18 06:09
Source: Generated
Credit: 2606.94000000 tBiblepay
Net amount: +2606.94000000 tBiblepay

Height: 12771
Difficulty: 36.267757
Time: 03-02-2018 05:09:05
Subsidy: 5820.7679

:
Transaction ID: 1d831b71fae895a8d7fa169ed3429179e937116675a8ccb2cfcae4163b2d6022-000



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=1d831b71fa, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02e3310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=210334fe421aa9256e0bba14d9941e)
    CTxOut(nValue=314647.42000000, scriptP2)
    CTxOut(nValue=21997.77000000, scriptPubKey=76a9146ec0f5e17278e46595ed1fb3)
    CTxOut(nValue=21231.81000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=23879.07000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23516.25000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=53805.18000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4300.11000000, scriptPubKey=76

[code]Status: 82 confirmations
Date: 02-03-18 08:33
Source: Generated
Credit: 2606.94000000 tBiblepay (matures in 20 more blocks)
Net amount: 0.00000000 tBiblepay

Height: 12870
Difficulty: 36.267757
Time: 03-02-2018 07:33:43
Subsidy: 5819.8947

:
Transaction ID: 70d0bb8c35c02ca805654e27fe8193fe04dbce63e10f8186a01016ba438d11bb-000



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=70d0bb8c35, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0246320101)
    CTxOut(nValue=5819.89466250, scriptPubKey=2103272e1da0c3bb0196a37b6ebed0)
    CTxOut(nValue=31464

Inputs:



Thanks Jaap!  So far everything looks good... Checking more ....

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 02, 2018, 08:40:32 AM

I dont see how thats happening - can you please double check your synced?  After that run this first, log output then restart client and log output?

From my node I see your 95a utxoweight @ 13:59, wait thats just 30 minutes ago:
exec datalist utxoweight:

"95A79CD5829E8315B0B946709930DF18 (03-02-2018 13:59:34)": "100"


I think what happened is you ran the command when your utxo weight ran out, then it synced within 6 blocks after....

You can find out by looking for your last PODC Update Before 3-2-2018 @ 13:59 UTC, But it must contain the XML for the CPID: 95A.

Meaning you would have to look at the showblock blocknumber, then the coinbase transaction vout 0.


If its showing up now in exec datalist utxoweight, then I think we just had a 24 hour lag between PODC update for that One CPID.

EDIT:  I forcefully created a contract on my hot sanc to see your 95a status, and it did pick up 100% for both weights.

I ran getboincinfo and it's fine now. This CPID has been associated and running continuously for a few days now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 11:23:10 AM
I ran getboincinfo and it's fine now. This CPID has been associated and running continuously for a few days now.

Good, but just to clarify, once associated, the CPID wont lose association (for one year).  I think we will need to ask researchers to reassociate once per year, once they fall out of the chain.

But if you want to search your PODC Update transactions for the Last transmission you should see a 24.01 hour lag, to know why your weight dropped to zero for 6 blocks.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 11:32:40 AM
I'm getting my first 'unbanked' transactions  8)

Code: [Select]
10:18:16

exec getboincinfo


10:18:19

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422217,
  "NextSuperblockHeight": 12969,
  "NextSuperblockBudget": 1339285,
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 57.44,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 15044,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 100,
  "Total_RAC": 57.44,
  "Total Payments (One Day)": 10465,
  "Total Payments (One Week)": 15780,
  "Total Budget (One Day)": 13474430,
  "Total Budget (One Week)": 85599588,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 64,
  "Superblock List": "12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514,8415,8217,8118,8019,7920,7821,7722,7623,7524,7425,7326,7227,7128,7029,6930,6831,6732,6633,6534,6435,6336,6237,6138,6039,5940,5841",
  "Last Superblock Height": 12870,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 2606,
  "Magnitude (One-Day)": 0.7766562296141655,
  "Magnitude (One-Week)": 0.184346681668608
}

Code: [Select]
Status: 278 confirmations
Date: 02-03-18 03:54
Source: Generated
Credit: 2647.47000000 tBiblepay
Net amount: +2647.47000000 tBiblepay

Height: 12672
Difficulty: 32.423041
Time: 03-02-2018 02:54:07
Subsidy: 5820.7679

:
Transaction ID: dfd8e518f41e3063882790ff25fd164298a988ca746a9ccc4c38c9fec283c673-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2647.47000000 tBiblepay

Transaction:
CTransaction(hash=dfd8e518f4, ver=1, vin.size=1, vout.size=13, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0280310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=21032833a45709cf01a2fd9db2c698)
    CTxOut(nValue=319900.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=46162.74000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28732.44000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=576463.14000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=87702.49000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=148849.65000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21582.93000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=24270.72000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23907.87000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=54696.47000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4367.65000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2647.47000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Code: [Select]
Status: 181 confirmations
Date: 02-03-18 06:09
Source: Generated
Credit: 2606.94000000 tBiblepay
Net amount: +2606.94000000 tBiblepay

Height: 12771
Difficulty: 36.267757
Time: 03-02-2018 05:09:05
Subsidy: 5820.7679

:
Transaction ID: 1d831b71fae895a8d7fa169ed3429179e937116675a8ccb2cfcae4163b2d6022-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=1d831b71fa, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 02e3310101)
    CTxOut(nValue=5820.76786500, scriptPubKey=210334fe421aa9256e0bba14d9941e)
    CTxOut(nValue=314647.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=45393.08000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28259.81000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=566983.49000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=86257.60000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=146405.45000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21997.77000000, scriptPubKey=76a9146ec0f5e17278e46595ed1fb3)
    CTxOut(nValue=21231.81000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=23879.07000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23516.25000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=53805.18000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4300.11000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2606.94000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Code: [Select]
Status: 82 confirmations
Date: 02-03-18 08:33
Source: Generated
Credit: 2606.94000000 tBiblepay (matures in 20 more blocks)
Net amount: 0.00000000 tBiblepay

Height: 12870
Difficulty: 36.267757
Time: 03-02-2018 07:33:43
Subsidy: 5819.8947

:
Transaction ID: 70d0bb8c35c02ca805654e27fe8193fe04dbce63e10f8186a01016ba438d11bb-000

Generated coins must mature 102 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.



Debug information

Credit: 2606.94000000 tBiblepay

Transaction:
CTransaction(hash=70d0bb8c35, ver=1, vin.size=1, vout.size=14, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase 0246320101)
    CTxOut(nValue=5819.89466250, scriptPubKey=2103272e1da0c3bb0196a37b6ebed0)
    CTxOut(nValue=314647.42000000, scriptPubKey=76a914fd47980297aad2b9f0db4f1c)
    CTxOut(nValue=45393.08000000, scriptPubKey=76a914198bdbf43eebc1040e4b1752)
    CTxOut(nValue=28259.81000000, scriptPubKey=76a914fc40b74ca5caed7982895b2a)
    CTxOut(nValue=566983.49000000, scriptPubKey=76a9149eab0ec205faec29fe899807)
    CTxOut(nValue=86257.60000000, scriptPubKey=76a914d7098dd1f89cf8c9e36261b4)
    CTxOut(nValue=146405.45000000, scriptPubKey=76a914959c47d10a53bdbd3d2bb392)
    CTxOut(nValue=21997.77000000, scriptPubKey=76a9146ec0f5e17278e46595ed1fb3)
    CTxOut(nValue=21231.81000000, scriptPubKey=76a9146038548bdd9aae1ac290560b)
    CTxOut(nValue=23879.07000000, scriptPubKey=76a914df719a02dce5ba09dc474f1d)
    CTxOut(nValue=23516.25000000, scriptPubKey=76a91496ae325295b168d695d9d43d)
    CTxOut(nValue=53805.18000000, scriptPubKey=76a91430559e379e13083e6f156678)
    CTxOut(nValue=4300.11000000, scriptPubKey=76a914ed283debf89b31661f8604b5)
    CTxOut(nValue=2606.94000000, scriptPubKey=76a914a9e3493c08aa06c3c31746f6)

Inputs:

Jaap, after doing an exec dcc on my sanc (that forces a pretend morning quorum), and cd into the /SAN directory I can see your cpid is unbanked:
cat filtered | grep c852 -A10 -B10


Looking at the XML field for <unbanked>, it appears to be working correctly.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 02, 2018, 01:17:21 PM
Jaap, after doing an exec dcc on my sanc (that forces a pretend morning quorum), and cd into the /SAN directory I can see your cpid is unbanked:
cat filtered | grep c852 -A10 -B10


Looking at the XML field for <unbanked>, it appears to be working correctly.

Cool :) I saw the 'Associate Unbanked CPID' option in the pool. Awesome! Unfortunately I don't have a spare phone, so I can't test that function right now...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 01:21:00 PM
Cool :) I saw the 'Associate Unbanked CPID' option in the pool. Awesome! Unfortunately I don't have a spare phone, so I can't test that function right now...

Yeah, its not quite ready to test, it needs a windows upgrade also.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 02, 2018, 03:22:09 PM
Good, but just to clarify, once associated, the CPID wont lose association (for one year).  I think we will need to ask researchers to reassociate once per year, once they fall out of the chain.

But if you want to search your PODC Update transactions for the Last transmission you should see a 24.01 hour lag, to know why your weight dropped to zero for 6 blocks.

Could you explain how to look that up? Thank you.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 03:38:45 PM
Could you explain how to look that up? Thank you.
Best way is to have you launch in -qt mode, then go to the transactions list, and scan for PODC Update.  Double click it.
Grab the Block Hash to the clipboard.
Type 'getblock blockhash' or 'showblock blocknumber'.
Then Copy the coinbase transaction #0 (the first tx) to the clipboard) - just the txid.
Then type 'getrawtransaction TXID 1', and look in the <XML> near the bottom for a CPID signature. Find the TXID corresponding to the CPID that was missing its weight over 1 day.

Once you get that TXID, take a look at its mother block timestamp (the timestamp is called HR Time in showblock).




Oh btw guys:  I added Orbis's 3 suggestions last night:  Icon for PODC Update and PODC Payment, Automatic Unlock for encrypted wallets, and support for the unbanked command from the pool.  (I think there was one more thing, that was added also).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 04:02:26 PM
If anyone needs the latest windows, to test the PODC Payment and Update icons and the auto-unlock feature windows is now available for download.

PS I think we are close to being ready to go live on the 20th or so. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 02, 2018, 04:03:53 PM
I was thinking about that and I remembered that we wrote about these thing later:
1. have PoDC only wallet unlock option
2. auto setgenerate true 1 on PoDC (maybe both can be cumulated in 1 command or settings option)
3. and those different icons for different tx

Ok, these have been added and ready for testing.  Windows is ready for download.
The wallet defaults to automatic mining now (in PODC mode only) on one thread, with setgenerate=true automatically.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 03, 2018, 03:13:18 AM
Ok, these have been added and ready for testing.  Windows is ready for download.
The wallet defaults to automatic mining now (in PODC mode only) on one thread, with setgenerate=true automatically.

Icons and automatic-mining work as expected, but the automatic lock gives me a runtime error:

(https://preview.ibb.co/ijCka7/runtime_error_biblepay.png)

This is Windows btw.

I've tried a reindex, deleting the testnet3 folder, a complete reinstall with the backuped wallet.dat and with a new wallet.dat.
I've tried different passwords, but they all give me the same screen.

I don't even have to type in a password, If I start the wallet it gives me this error after about 10 seconds or so

I'm gonna try on a different PC now. If you need some debugging, I need some instructions on how to provide that :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 03, 2018, 03:47:18 AM
Icons and automatic-mining work as expected, but the automatic lock gives me a runtime error:

(https://preview.ibb.co/ijCka7/runtime_error_biblepay.png)

This is Windows btw.

I've tried a reindex, deleting the testnet3 folder, a complete reinstall with the backuped wallet.dat and with a new wallet.dat.
I've tried different passwords, but they all give me the same screen.

I don't even have to type in a password, If I start the wallet it gives me this error after about 10 seconds or so

I'm gonna try on a different PC now. If you need some debugging, I need some instructions on how to provide that :)

It's the same on an other Windows PC.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 03, 2018, 06:03:09 AM
I can't get new tasks from rosetta@home on my Android phone.  I tried seti@home and from them I do get tasks, so I think it's related to rosetta and not Boinc.

Does anyone else have the same problem? Maybe they don't always have tasks for Android phones?

About their server: I looked at this page: https://boinc.bakerlab.org/rosetta/server_status.php

I see now that it says that for 'Rosetta for Android' there are 0 'not sent tasks'. So that means that they are 'empty' at the moment regarding Android tasks I guess?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 03, 2018, 08:39:05 AM
It's the same on an other Windows PC.

For me, I get the password prompt in windows, and then it silently exits after I type in the password.
Are you saying on your machine you do not get the password prompt, just an immediate crash window?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 03, 2018, 09:33:04 AM
For me, I get the password prompt in windows, and then it silently exits after I type in the password.
Are you saying on your machine you do not get the password prompt, just an immediate crash window?

Oh yeah, sorry. I do get the password prompt, but from there on things get really unstable. If I just leave the wallet open with the prompt, nothing is happening, but as soon as I start entering my password, I get the error.

Actually, if I'm really fast, the wallet opens without problems (on one PC, on the other it just crashes no matter what I do (but I'm reinstalling the wallet in that PC also, to see if that makes a difference).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 03, 2018, 10:15:36 AM
Oh yeah, sorry. I do get the password prompt, but from there on things get really unstable. If I just leave the wallet open with the prompt, nothing is happening, but as soon as I start entering my password, I get the error.

Actually, if I'm really fast, the wallet opens without problems (on one PC, on the other it just crashes no matter what I do (but I'm reinstalling the wallet in that PC also, to see if that makes a difference).

Thanks a lot!  That helped... I tracked it down, that whole prompt needed to be moved to Inside the qt wallet, so it has a parent.  OK it will be fixed asap, Im testing it now...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 03, 2018, 12:24:25 PM
Since most of us are new users, our RAC is still building, we should be close to the top 10 in a few weeks via natural progression of RAC.
Yeah, and also I think we have 10,000 PC's out there, so we should easily reach #1 in Rosetta eventually but Im not sure where we will end up in the international list.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 03, 2018, 01:11:48 PM
I can't get new tasks from rosetta@home on my Android phone.  I tried seti@home and from them I do get tasks, so I think it's related to rosetta and not Boinc.

Does anyone else have the same problem? Maybe they don't always have tasks for Android phones?

About their server: I looked at this page: https://boinc.bakerlab.org/rosetta/server_status.php

I see now that it says that for 'Rosetta for Android' there are 0 'not sent tasks'. So that means that they are 'empty' at the moment regarding Android tasks I guess?

I was wondering what was wrong, my phone hasn't gotten a new task for 1 day or 2.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 03, 2018, 01:19:24 PM
1.0.9.5f for windows is out there if anyone wants to re-test the podc unlock.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 03, 2018, 01:52:44 PM
Ok, these have been added and ready for testing.  Windows is ready for download.
The wallet defaults to automatic mining now (in PODC mode only) on one thread, with setgenerate=true automatically.
Wau. Thanks Rob. I was tried it right now and all works fine. (Windows, 1.0.9.5f)
And that pool unbanked function is great. Nice work.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 03, 2018, 01:56:33 PM
I can't get new tasks from rosetta@home on my Android phone.  I tried seti@home and from them I do get tasks, so I think it's related to rosetta and not Boinc.

Does anyone else have the same problem? Maybe they don't always have tasks for Android phones?

About their server: I looked at this page: 

I see now that it says that for 'Rosetta for Android' there are 0 'not sent tasks'. So that means that they are 'empty' at the moment regarding Android tasks I guess?
Same for me. Didn't get tasks on android for 2 days. I reinstalled boinc on my phone but didn't helped. It looks that we just must wait. But that's bad for me, because my Nexus 4 was my best "computer" :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 03, 2018, 02:06:24 PM
Same for me. Didn't get tasks on android for 2 days. I reinstalled boinc on my phone but didn't helped. It looks that we just must wait. But that's bad for me, because my Nexus 4 was my best "computer" :D

Although I havent dealt with this in a couple years, I remember that the administrator of the boinc project has to run a script to release more work for each processor type.  I assume they have this automated for windows and linux, but the work might have run out for ARM only.

If you open up the boinc event log you might see an error messaged about scheduler returned no tasks.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 03, 2018, 11:20:31 PM
1.0.9.5f for windows is out there if anyone wants to re-test the podc unlock.

Where do I find this new version?  The new website only has up to 1.0.9.2b.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 12:53:00 AM
Where do I find this new version?  The new website only has up to 1.0.9.2b.
It look, that it is just bad "label". It is still not corrected, but after download it is the newest version.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 01:00:12 AM
Same for me. Didn't get tasks on android for 2 days. I reinstalled boinc on my phone but didn't helped. It looks that we just must wait. But that's bad for me, because my Nexus 4 was my best "computer" :D
I've received two tasks on one of my mobile phones since yesterday. It looks they're slowly releasing them.
Edit: I've found that these new tasks are 4 hours. Old tasks on this phone was 2 hours.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 04:35:20 AM
I've received two tasks on one of my mobile phones since yesterday. It looks they're slowly releasing them.
Edit: I've found that these new tasks are 4 hours. Old tasks on this phone was 2 hours.

Okay, interesting. Maybe they changed something on their end, and that's  we we didn't get new tasks for a while.

My phone is on the charger now, so soon I can see if I also get new tasks.
About that: I want to test the 'Associate Unbanked CPID' function on the pool. But of course we are on testnet now. I if switch the pool to testnet (Network>test), will I be able to associate a testnet BBP adres via the Unbanked funtion in the pool?

And my wallets no longer crash at the password prompt  ;D Running smoothly now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 06:23:19 AM
It look, that it is just bad "label". It is still not corrected, but after download it is the newest version.

Yes, waiting for Tom (zthomasz) to implement a dynamic label on the website, needs done as a high priority. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 06:27:11 AM
Okay, interesting. Maybe they changed something on their end, and that's  we we didn't get new tasks for a while.

My phone is on the charger now, so soon I can see if I also get new tasks.
About that: I want to test the 'Associate Unbanked CPID' function on the pool. But of course we are on testnet now. I if switch the pool to testnet (Network>test), will I be able to associate a testnet BBP adres via the Unbanked funtion in the pool?

And my wallets no longer crash at the password prompt  ;D Running smoothly now.

Sweet, so far so good.  On that unbanked feature, I need to release one RPC command in the win version to the wallet the pool uses (it has one more field in the associate result command), but, with the ninja release coming up, I need to merge all the latest changes required for prod into this next version.  Im working on that now.... so heres my game plan:

- Ensure the unbanked feature for the pool is in this next version
- Ready the wallet with a Prod block cutover
- Release this some time today for testing

If all goes well, we can possibly stay on this same version in prod, and sail through the block number.

Ill notify as soon as its ready...  But yes the pool unbanked feature cant be tested until this next windows version is ready.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:18:00 AM
While Im readying this next version will someone please test this:
 Slovakia said on the main thread he cant force a reassociation to a new wallet, he was typing the wrong command:
exec associate email pass force

The command should be:
exec associate email pass true

Anyway will someone please retry association wait 6 blocks then reassociate back using the latest version?

Thanks!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 09:37:15 AM
While Im readying this next version will someone please test this:
 Slovakia said on the main thread he cant force a reassociation to a new wallet, he was typing the wrong command:
exec associate email pass force

The command should be:
exec associate email pass true

Anyway will someone please retry association wait 6 blocks then reassociate back using the latest version?

Thanks!

Fired up a testwallet (1.0.9.6.) and tried it:

Code: [Select]
16:34:45

exec associate [email protected] password true


16:34:51

{
  "Command": "associate",
  "E-Mail": "[email protected]",
  "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!"
}

I will wait a few blocks and reassociate with the old wallet again. Or I can wait to see if I now receive payments with this wallet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: capulo on March 04, 2018, 09:39:44 AM
Rob  weve tried with SLOVAKIA and true helped.... we´re trying to understand how it working.... you wrote about command force few days ago for change adminwallet btw....

we was think that this command is for change wallet    exec associate email pass force

Quote
"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!"
}

thanks for your time  ;)

can i to ask about utxoweight and taskweight... this parameters will be visible after 24hours,right? when adminwallet was close more like 24 hours, podcupdate will be inapplicable?  me and slovakia tried exec podcupdate on mainwallet and we see FALSE

PODC looks amazing




Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:50:39 AM
Fired up a testwallet (1.0.9.6.) and tried it:

Code: [Select]
16:34:45

exec associate [email protected] password true


16:34:51

{
  "Command": "associate",
  "E-Mail": "[email protected]",
  "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!"
}

I will wait a few blocks and reassociate with the old wallet again. Or I can wait to see if I now receive payments with this wallet.


Thanks for helping out!  Its best to double check first, then associate back later.  After you waited 6 blocks after you ran the associate command, here is how we can tell if it worked.  This is a secret command not meant for normal users use, although thinking more about it, it would be nice to add a filter to this command so we can sometimes use this under normal circumstances.  But for now:

exec datalist dcc

Please take a look at the first column, ensure your CPID is only in the list once.  Then look at the 2nd column of the "value" side (thats the semicolon delimited string side), and ensure its associated with the new address.

Once you know that is true, thats what all the nodes know about that CPID.

Then you can reassociate back and wait another 6 blocks and retry the datalist command and ensure its only in there once and its back to your original address.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:56:25 AM
Rob  weve tried with SLOVAKIA and true helped.... we´re trying to understand how it working.... you wrote about command force few days ago for change adminwallet btw....

we was think that this command is for change wallet    exec associate email pass force

thanks for your time  ;)

can i to ask about utxoweight and taskweight... this parameters will be visible after 24hours,right? when adminwallet was close more like 24 hours, podcupdate will be inapplicable?  me and slovakia tried exec podcupdate on mainwallet and we see FALSE

PODC looks amazing

Thanks, well he basically said the commands didnt work in the main thread.  Im running out of patience with him, not only is he blaming the software and cant test properly but he cant explain the issue properly. 

Yes, most users never need the force part of the command.  The idea is to associate the rosetta email and password once to a biblepay address, until someday you receive the error "ALREADY_IN_CHAIN" - that happens when you try to reassociate to a new wallet but yet the CPID is already in use.  Thats when you need the force command, so it can forcefully overwrite the old CPID association in the chain (this protects the integrity of the original cpid in most cases from accidents).

So PODC has some dynamic natured programming in it, in that if we receive over 16,384 researchers it can actually adjust to the influx, and the timing of UTXO weight and Task weight can adjust dynamically, but for all intents and purposes for now, we are looking for a PODC update once every 24 hours - that will refresh one researchers given UTXO weight and Task weight for up to 24 more hours.  The Sanctuaries check the tasks integrity and determine the Task weight.  The UTXO weight is determined by the amount staked by the controller wallet.  Btw, also see the charts for task weight and utxo in the wiki page.  Im sure I have not answered your question yet, give me a minute.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 10:05:12 AM
Just wanted to give everyone a heads up, Im going to be forced to upgrade the mandatory sanctuary protocol version up to 70716.

Primarily because when we go live with the mandatory, we are going to need to force every Sanctuary to upgrade to 70716, otherwise they are not acting properly in the quorum.

This means I am also forced to increment the required Payment Protocol version to 70716, meaning Sancs wont be paid if they do not upgrade.

This will most likely break compatibility for all testnet sancs also, (as the code cannot discern between testnet & prod sanc versions, its just not possible at this time), meaning that for the short period of testing, we will need to upgrade some of our hot sancs to 70716 also.

So keep that in mind, and don't jump to the conclusion that we broke everything, we will need to verify we have a supermajority on 70716, verify everything works, then release the mandatory (sometime Wednesday).

It should be ready for testing within 1 hour...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: capulo on March 04, 2018, 10:06:59 AM
we askin you cos this:

our adminwallet running w/mistakes,bugs = we have 1testnet machine with SLOVAKIA....

and we checked today our adminwallet and from 1.3.2018 didnt receive PODC PAYMENT, we dont know whats wrong ... utxo+task was 0 on both

weve tried EXEC PODCUPDATE and received FALSE still ...


now,we change adminwallet to windows from linux.....


edit:// we can go to update our linux+windows masternode now
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 10:08:10 AM

Thanks for helping out!  Its best to double check first, then associate back later.  After you waited 6 blocks after you ran the associate command, here is how we can tell if it worked.  This is a secret command not meant for normal users use, although thinking more about it, it would be nice to add a filter to this command so we can sometimes use this under normal circumstances.  But for now:

exec datalist dcc

Please take a look at the first column, ensure your CPID is only in the list once.  Then look at the 2nd column of the "value" side (thats the semicolon delimited string side), and ensure its associated with the new address.

Once you know that is true, thats what all the nodes know about that CPID.

Then you can reassociate back and wait another 6 blocks and retry the datalist command and ensure its only in there once and its back to your original address.

Glad to be of assistance!

My CPID is listed only once and is associated with the new address :)

Code: [Select]
17:02:19

exec datalist dcc


17:02:19

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (02-28-2018 18:57:43)": "04fba56d89a5eb38b1b82f8a6240132c;yfvTaGZakXWsLqyTCSZRG3kqabY6WYhFym;yfvTaGZakXWsLqyTCSZRG3kqabY6WYhFym;1981529;H3TE1ocsh4C0LjTdPyiGi2REXCFYBDyMogAJAO4IBD2eLeT1xmxwdjyfJ8s+Fl3Tn7KqEffHcJLS/G9l4BEP/Q0=",
  "4B7D2D64C88B32927A21AD20A57868E4 (02-27-2018 04:53:55)": "4b7d2d64c88b32927a21ad20a57868e4;yhwRCipWmkGncgFMp9hK2v92pSEKnqHWj2;yhwRCipWmkGncgFMp9hK2v92pSEKnqHWj2;1985935;INgDBUp1XVgjxa5vkADf9cXP20NOQ7MNyMJRCqYlgr7KYcHwu0vdjsZjVWqpgYmgUn44Lq1jJaZnJA3p1TXfwMw=",
  "4FD1BF6C6900D92B226E16C6A6935661 (02-19-2018 22:01:42)": "4fd1bf6c6900d92b226e16c6a6935661;yWQfYmBCAQrcn9RkjM9DJwWGfgjHdvpZwn;yWQfYmBCAQrcn9RkjM9DJwWGfgjHdvpZwn;1981544;H2x6mg4cutmIdtLMbt0tA3QDJt2sFoAzJi50YzkGHd5mfJlDmgMNj7dQCGVJR3lKw6808qr8aMyOJdA69+Aqacg=",
  "6785DED1F65063EF8F01F42DEB31CF1D (02-20-2018 00:22:34)": "6785ded1f65063ef8f01f42deb31cf1d;yQj1rFpeMbaWJ9dNBGrYLoZ1YZdV5zQ9Qr;yQj1rFpeMbaWJ9dNBGrYLoZ1YZdV5zQ9Qr;1981965;IIKcfM2lOlykKDslRzCfZ94QR6R82VAC1rtvV8anwBW0exp3SxWD6x5NejDKuSwfekjv+J0sd7L75Hv+dlYy1AU=",
  "71F1F1F46DEB2F25961C7D9AF06F2B31 (02-19-2018 21:39:32)": "71f1f1f46deb2f25961c7d9af06f2b31;yWR4LS4qTQJnE9FiYGJPdfFDSWfv62gNNd;yWR4LS4qTQJnE9FiYGJPdfFDSWfv62gNNd;1981959;H7PHD0KXvbJpnnr8k/38jDJpRHMlOpFafuXuwMQuQNc2cwMqZdkSdhdNMfjB9ULE8fwJYoiZfAvAyk+HVwEg8H8=",
  "8735CFE64D964416DBA6015EB414CF7E (02-20-2018 02:48:50)": "8735cfe64d964416dba6015eb414cf7e;yXnQ21gKRh1t5vMr4jKbGHSSJkMeXc8R5o;yXnQ21gKRh1t5vMr4jKbGHSSJkMeXc8R5o;1981648;H3Hxm+K0Gx6KuKpXV5RuIUTf7BGNd/2EBdFGOIF6qt//CFwBvti8069t8GtIhvCX+kZA84QDEsenhJzgo53dz40=",
  "93138F032BDD027FA3246B48BB715A77 (02-19-2018 18:11:22)": "93138f032bdd027fa3246b48bb715a77;yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc;yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc;1981221;H9fC303lsYACiELVZejQeZA2m1RK+N9WVeH+mLDMIRI9AbgRVtF1pRz18fY8J6bxDgSf9cIx4Ub39sVwZX43dqY=",
  "95A79CD5829E8315B0B946709930DF18 (02-19-2018 21:45:46)": "95a79cd5829e8315b0b946709930df18;yggudABrHvV5vuKZnnsdWPfjcJ7vApijdF;yggudABrHvV5vuKZnnsdWPfjcJ7vApijdF;1981963;ICuPmhSRKXo5Uftd+KG+V8HfY8IktQCAfD2SaSizkjoZJzdn5B6pnAma6ie/BtwhShMgWs5I2bgWa1dST4MVF+E=",
  "C852DA1A620AD630B70C8EC1CCDEE366 (02-27-2018 08:46:06)": "c852da1a620ad630b70c8ec1ccdee366;ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv;ybojKjcfCMPpoD1S97NPdVUdbbcsk6k5Lv;1985966;IMfOvAS2bWCb6RqYQwbh6Jkur8zBres4HVkFMgZXPVCuBSgtwD7YrfQH2zbWBspnbrTzuQLxsf+5TqZ9H/dkE+s=",
  "C9085154B7CC0CA2B5189672559DD6D8 (03-01-2018 16:58:03)": "c9085154b7cc0ca2b5189672559dd6d8;yNeXHaws4KRpEfuaDT6sjQWvomFTfALZWU;yNeXHaws4KRpEfuaDT6sjQWvomFTfALZWU;1084150;IE1yZ8x8MM6QYOU9n76qEkdBfRWWzkvbvrBi1s+2d9GAcdk4JOOhSV3RHViVRanTrQhViavub6L9ycbAZlfCQQI=;1",
  "CA895B47AACFFBDBF906201821AF2F9F (02-19-2018 15:43:50)": "ca895b47aacffbdbf906201821af2f9f;yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb;yjQfaAE1yqYULCJMS6FmX98jBHtaY9sdMb;475629;H1C+xdEuI73ipUtnvqIcJz7V1ohM2e9KrhEl0TtcZvQjT+WI5lZ0IeiZvzKvv+6P7QUfKiAmx99rArTgrOyS8jA=",
  "CC37D0EF74A621379974484F43D3B1C5 (02-19-2018 21:47:10)": "cc37d0ef74a621379974484f43d3b1c5;ya4AtNH78Q2px2iQyewG6fvpctFzLZMnVR;ya4AtNH78Q2px2iQyewG6fvpctFzLZMnVR;1981964;H88UWU+ZPMh5aQr6k4d3QmJ+Cmr9Cr8HLRm6TPiGi1gDSvyHdFaulR/gAoktaPT6BCoHH3l75b0pXbH3nRz5Tmk=",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-04-2018 15:35:56)": "d9b22fccfae5582d4ee7838883aaa3cf;yhW1cbeQeNvVZaGJuqNkKCMzPkQGs4J6fg;yhW1cbeQeNvVZaGJuqNkKCMzPkQGs4J6fg;1981615;IOc9ei8QtgBjRXpc6UMyHc4Y2W7EFIvc3oghnSNkM8KxMdHJilis79qS0PliV9Pyhr9lcSdENaZaUzazs+3C4wU=;0",
  "DDE30F3EF57ED2DF69ECBC687DB75E46 (03-04-2018 15:24:18)": "dde30f3ef57ed2df69ecbc687db75e46;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;1982089;IG5f8Wv8SuXsay+7CNqRXrI0fyVbgBMKtA5fDOb3zS6iaXAkNLQhVDqNKgdv2238AV0AWHUYJFTPQQ6rCJ1X0IE=;0",
  "E6CE50042187D4B285568D86EF458F32 (02-24-2018 19:20:38)": "e6ce50042187d4b285568d86ef458f32;yjSv5YRA1tmBAYtkqpoZJELnKLhKpC1vGY;yjSv5YRA1tmBAYtkqpoZJELnKLhKpC1vGY;1985116;IIQRXbG0I6lryqqKHh/d6DQYCC5LechhP+yadz8OeNNYF1o44mIUQhWAQZ4WVB2o4VpKu3hxh7W/UBseeIyALPA=",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (02-20-2018 16:56:53)": "e7ae6abd6284b05f3fd5f7c780e60bc7;yanQXohgWcygJznMn8NGs3yrA77MFXTLAy;yanQXohgWcygJznMn8NGs3yrA77MFXTLAy;1981355;IAdgY+TLxFKwsnOWPEhp/gdLa+FiPQiug6lH56AYxxu/Ec7zkH4aFkO5ynsNbOSBVJHJNLZCTThvGNz36aT84oY=",
  "E94C1704C75F731F8BFDE303F08408EE (02-19-2018 20:01:17)": "e94c1704c75f731f8bfde303f08408ee;yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84;yjKEf6GvMkuiXLXibCCtj9wt4ZEBwQ5i84;1981209;H1tzerdJv8Ot1f2dQG23Jl30pG7LLhktLbOBCls64h91XqmmQq3lFex3jR7+E98KOa/wibJ/FCrOSkZhPEWr6bw=",
  "F80AB050AB53459EC937879A046D603E (02-19-2018 21:43:10)": "f80ab050ab53459ec937879a046d603e;yV6DCWkg9pmbLhCYwZM8jiEd9dNgvQGEZx;yV6DCWkg9pmbLhCYwZM8jiEd9dNgvQGEZx;1981962;H4qaxt5D8Mo2qb/NPbRXouMT+5hQBCdnuz0rzq56XBLmAUI1dZr/Ck70rgI5LIv8vK1u2EMiuzSUo7tLQjYc2PY="
}


(my CPID is d9b22fccfae5582d4ee7838883aaa3cf btw)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 10:08:42 AM
Rob  weve tried with SLOVAKIA and true helped.... we´re trying to understand how it working.... you wrote about command force few days ago for change adminwallet btw....

we was think that this command is for change wallet    exec associate email pass force

thanks for your time  ;)

can i to ask about utxoweight and taskweight... this parameters will be visible after 24hours,right? when adminwallet was close more like 24 hours, podcupdate will be inapplicable?  me and slovakia tried exec podcupdate on mainwallet and we see FALSE

PODC looks amazing

Yes, if the controller wallet was closed > 24 hours, podc updates have lagged and fell out of the visibility window, so the researchers utxo weight = 0 and task weight = 0, when you type 'exec getboincinfo' you should see that problem.

As far as 'exec podcupdate' that will force a PODC update forcefully, then you can see the results in 6 blocks.

If you receive 'false', that usually means the wallet is encrypted & locked, or has no funds in it.  PODC updates cost about .01 BBP (for miner tx fees).


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 10:10:13 AM
we askin you cos this:

our adminwallet running w/mistakes,bugs = we have 1testnet machine with SLOVAKIA....

and we checked today our adminwallet and from 1.3.2018 didnt receive PODC PAYMENT, we dont know whats wrong ... utxo+task was 0 on both

weve tried EXEC PODCUPDATE and received FALSE still ...


now,we change adminwallet to windows from linux.....


edit:// we can go to update our linux+windows masternode now


Please initialize PODC, set this up yourself, check it personally then post back.  These lines above are incomprehensible to me. 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: capulo on March 04, 2018, 10:10:44 AM
and here is problem what SLOVAKIA tried asking you

we have 8M tBBP in wallet and testnet wallet is unlock
on running adminwallet utxo+task droped to 0 and PODCUPDATE doesnt unresponsive : response : FALSE

exec podcupdate helps when is admin wallet close 24+ hours?


this is us
"DDE30F3EF57ED2DF69ECBC687DB75E46 (03-04-2018 15:24:18)": "dde30f3ef57ed2df69ecbc687db75e46;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;1982089;IG5f8Wv8SuXsay+7CNqRXrI0fyVbgBMKtA5fDOb3zS6iaXAkNLQhVDqNKgdv2238AV0AWHUYJFTPQQ6rCJ1X0IE=;0",


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 10:31:35 AM
and here is problem what SLOVAKIA tried asking you

we have 8M tBBP in wallet and testnet wallet is unlock
on running adminwallet utxo+task droped to 0 and PODCUPDATE doesnt unresponsive : response : FALSE

exec podcupdate helps when is admin wallet close 24+ hours?


this is us
"DDE30F3EF57ED2DF69ECBC687DB75E46 (03-04-2018 15:24:18)": "dde30f3ef57ed2df69ecbc687db75e46;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;yQBU33UXZoFURsK4yy751tiD4i311sZJDR;1982089;IG5f8Wv8SuXsay+7CNqRXrI0fyVbgBMKtA5fDOb3zS6iaXAkNLQhVDqNKgdv2238AV0AWHUYJFTPQQ6rCJ1X0IE=;0",


Can anyone help Capulo?

Capulo, Im going to delete the messages if they are not comprehensible.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 10:41:41 AM

Can anyone help Capulo?

Capulo, Im going to delete the messages if they are not comprehensible.

Sure... I'll give it a shot via private messages.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 10:43:38 AM

Biblepay 1.0.9.7
Mandatory Upgrade for Testnet


- 7 Minute Blocks, 16 minute late blocks
- Cutover to PODC at 33440
- Superblock icons + PODC Payment icons
- Checkpoint
- Sanctuary Mandatory upgrade to protocolversion 70716


Windows is compiling.

Ill be at church so I would appreciate it if anyone can help answer questions while Im gone.

So now, please- everyone testing in testnet, upgrade to latest in order to continue testing.  We need to ensure everything still works: new contracts generate, exec getboincinfo works correctly, basically an end-to-end test. 

Please upgrade your sancs in testnet also so we have a supermajority on 70716.

Ill release windows tonight.  If all goes well with very little changes, we can release this version to prod.  It transitions into PODC mode after block 33440.

Note, I added an error message to getmininginfo designed to show you if the wallet is unable to sign the CPID or process a UTXO (coinstake) - that happens if the wallet is locked or if the new password feature didnt work.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 12:04:17 PM
I'm in conversation with capulo at the moment, but I'd like to ask something about the following: there is an obvious difference between the Rosetta leaderboard (https://boinc.bakerlab.org/rosetta/team_members.php?teamid=15044&offset=0&sort_by=total_credit) and the pool leaderboard.
Slovakia, West and Togo are on the Rosetta leaderboard, but not on the pool leaderboard.

West and/or Togo, could either one of you confirm that your wallets have been offline for 24+ hours? Or do you have the same experience that capulo has?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: capulo on March 04, 2018, 12:34:43 PM
i tried it after 2hours   its really true that we must wait so long? 


Quote
19:30:19

exec podcupdate


19:30:19

{
  "Command": "podcupdate",
  "PODCUpdate": true
}


now ill be wait for raise UTXO+TASK WEIGHTS to 100 100

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 12:56:21 PM
I'm in conversation with capulo at the moment, but I'd like to ask something about the following: there is an obvious difference between the Rosetta leaderboard (https://boinc.bakerlab.org/rosetta/team_members.php?teamid=15044&offset=0&sort_by=total_credit) and the pool leaderboard.
Slovakia, West and Togo are on the Rosetta leaderboard, but not on the pool leaderboard.

West and/or Togo, could either one of you confirm that your wallets have been offline for 24+ hours? Or do you have the same experience that capulo has?

The pool leaderboard is just for team spirit, not used for payments, so as long as West and Togo are in the exec getboincinfo in the client and see their own magnitude, they are going to get paid.  Ill diagnose the missing accounts in the pool leaderboard either tonight or tomorrow- Im sure its either that they are hiding their machines or its a bug in the pool leaderboard.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 12:59:27 PM
i tried it after 2hours   its really true that we must wait so long? 



now ill be wait for raise UTXO+TASK WEIGHTS to 100 100

No - it happens immediately, not sure what you mean by 2 hours.

In client PODC updates *transmit* after approx 30 minutes on thread #0, podcupdate command happens immediately, results happen from the viewing side in 6 blocks, and then in the sancs after the contract is voted on.  Youll have to clarify what you are talking about - reading  writing what value and what you are referring to.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: capulo on March 04, 2018, 12:59:42 PM
ROB

im on wallet 196  and i tried setup SETGENERATE TRUE 8,12,16 in adminwallet and withouts response overloading on CPU ...


Rob can you check it where is problem?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 01:02:23 PM
ROB

im on wallet 196  and i tried setup SETGENERATE TRUE 8,12,16 in adminwallet and withouts response overloading on CPU ...


Rob can you check it where is problem?

PODC Does not use setgenerate true > 1.

Why are you doing that?

From my end, if you deliberately do that it does not overload the CPU (as PODC sleeps, whereas heat mining does not).  Please stop posting inaccurate info.  Is this Slovakia talking through Capulo?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: capulo on March 04, 2018, 01:13:01 PM
before worked: few days ago .. very weird then ...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 01:16:56 PM
The pool leaderboard is just for team spirit, not used for payments, so as long as West and Togo are in the exec getboincinfo in the client and see their own magnitude, they are going to get paid.  Ill diagnose the missing accounts in the pool leaderboard either tonight or tomorrow- Im sure its either that they are hiding their machines or its a bug in the pool leaderboard.

Well, when I enter 'exec leaderboard' I think it roughly reflects the data I see on the pool leaderboard?

Code: [Select]

{
  "Leaderboard Report": 1520190924,
  "Height": 13167,
  "Total Block": 1339277,
  "e7ae6abd6284b05f3fd5f7c780e60bc7": 419.5733935580661,
  "ca895b47aacffbdbf906201821af2f9f": 232.8383132627656,
  "d9b22fccfae5582d4ee7838883aaa3cf": 108.3420374699033,
  "04fba56d89a5eb38b1b82f8a6240132c": 63.83294819643024,
  "6785ded1f65063ef8f01f42deb31cf1d": 39.81252541623185,
  "c9085154b7cc0ca2b5189672559dd6d8": 33.59200498782548,
  "e94c1704c75f731f8bfde303f08408ee": 20.9097892302355,
  "95a79cd5829e8315b0b946709930df18": 17.66848816437161,
  "cc37d0ef74a621379974484f43d3b1c5": 17.40789980408907,
  "71f1f1f46deb2f25961c7d9af06f2b31": 16.28415916734059,
  "f80ab050ab53459ec937879a046d603e": 15.70250205370135,
  "e6ce50042187d4b285568d86ef458f32": 8.929444700913667,
  "4b7d2d64c88b32927a21ad20a57868e4": 3.180074001270282,
  "c852da1a620ad630b70c8ec1ccdee366": 1.926412520140251
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 01:18:59 PM

Biblepay 1.0.9.7
Mandatory Upgrade for Testnet


- 7 Minute Blocks, 16 minute late blocks
- Cutover to PODC at 33440
- Superblock icons + PODC Payment icons
- Checkpoint
- Sanctuary Mandatory upgrade to protocolversion 70716


Windows is compiling.

Ill be at church so I would appreciate it if anyone can help answer questions while Im gone.

So now, please- everyone testing in testnet, upgrade to latest in order to continue testing.  We need to ensure everything still works: new contracts generate, exec getboincinfo works correctly, basically an end-to-end test. 

Please upgrade your sancs in testnet also so we have a supermajority on 70716.

Ill release windows tonight.  If all goes well with very little changes, we can release this version to prod.  It transitions into PODC mode after block 33440.

Note, I added an error message to getmininginfo designed to show you if the wallet is unable to sign the CPID or process a UTXO (coinstake) - that happens if the wallet is locked or if the new password feature didnt work.

1.0.9.7 has been deployed for windows.

Note, the hot sanctuaries will say "unable to start" until we start getting the other peers connected on 1.0.9.7.
You can try deleting your peers.dat, and restarting the hot sanc after you upgrade.

Also, if some people could please upgrade their Prod instance and just verify everything works.  I realize this is going to be a little messy.

I will be gone for about 6 hours...



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 01:20:15 PM
Well, when I enter 'exec leaderboard' I think it roughly reflects the data I see on the pool leaderboard?

Code: [Select]

{
  "Leaderboard Report": 1520190924,
  "Height": 13167,
  "Total Block": 1339277,
  "e7ae6abd6284b05f3fd5f7c780e60bc7": 419.5733935580661,
  "ca895b47aacffbdbf906201821af2f9f": 232.8383132627656,
  "d9b22fccfae5582d4ee7838883aaa3cf": 108.3420374699033,
  "04fba56d89a5eb38b1b82f8a6240132c": 63.83294819643024,
  "6785ded1f65063ef8f01f42deb31cf1d": 39.81252541623185,
  "c9085154b7cc0ca2b5189672559dd6d8": 33.59200498782548,
  "e94c1704c75f731f8bfde303f08408ee": 20.9097892302355,
  "95a79cd5829e8315b0b946709930df18": 17.66848816437161,
  "cc37d0ef74a621379974484f43d3b1c5": 17.40789980408907,
  "71f1f1f46deb2f25961c7d9af06f2b31": 16.28415916734059,
  "f80ab050ab53459ec937879a046d603e": 15.70250205370135,
  "e6ce50042187d4b285568d86ef458f32": 8.929444700913667,
  "4b7d2d64c88b32927a21ad20a57868e4": 3.180074001270282,
  "c852da1a620ad630b70c8ec1ccdee366": 1.926412520140251
}

That is not accurate enough - we will need one specific person who claims to be missing paste their exec getboincinfo.  Pool is a completely different codebase than the client.  The client was created to work through disaster recovery modes, etc.

Lets not look at the pool for anything.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 01:27:46 PM
That is not accurate enough - we will need one specific person who claims to be missing paste their exec getboincinfo.  Pool is a completely different codebase than the client.  The client was created to work through disaster recovery modes, etc.

Lets not look at the pool for anything.

Alright :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 04, 2018, 02:33:16 PM
My testnet wallet with CPID burn transaction ran out of disk space, not sure when though,
Im too much of a linux newbie still to pinpoint the issue, but the disk space on AWS was only 8GB, Ive extended to 20GB now,
the debug.log was only 155MB in size

Upgraded both of my testnet sanctuaries to v1.0.9.7

In testnet3 folder, removed blocks and chainstate folders and relevant .dat files, reindexed
Since there was a protocol version increase, ran start-alias command for masternodes
Turned on 1 mining thread for wallet with CPID burn

Reference: 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: orbis on March 04, 2018, 02:38:01 PM
1.0.9.7 has been deployed for windows.

Note, the hot sanctuaries will say "unable to start" until we start getting the other peers connected on 1.0.9.7.
You can try deleting your peers.dat, and restarting the hot sanc after you upgrade.

Also, if some people could please upgrade their Prod instance and just verify everything works.  I realize this is going to be a little messy.

I will be gone for about 6 hours...
Hi,
Rob I'm thinking that something is wrong with it.
I am on 1097. Win and Linux.
In linux headless it is normal. Starts with setgenerate true 1 and you must just unlock it.
But in Win it didn't work for me.
On boot it asks for PWD and after inserting it does nothing.
Wallet is locked and not generating BBP. When I do it manually it works, but not automatically.
getinfo:
Quote
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 7332481.00093010,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15388,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 0.02513946871654256,
  "testnet": true,
  "keypoololdest": 1506015302,
  "keypoolsize": 1012,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
and getmininginfo
Quote
  "blocks": 15388,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 28.7044849880676,
  "difficulty_pow": 0.2513946871654256,
  "difficulty": 28.7044849880676,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 19290821.32796781,
  "hashps": 75.48933921421167,
  "minerstarttime": "03-04-2018 20:02:50",
  "hashcounter": 7428,
  "pooledtx": 0,
  "testnet": true,
  "chain": "test",
  "biblepay-generate": false,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 14,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false

And using genproclimit more than 1 is working for me. When I use e.g. setgenerate true 12 cpu is "heating" more.

In prod version is asking for PODC pwd on boot and PODC tab is there too.
So can we try associate in prod? is it live now?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 02:53:31 PM
My testnet wallet with CPID burn transaction ran out of disk space, not sure when though,
Im too much of a linux newbie still to pinpoint the issue, but the disk space on AWS was only 8GB, Ive extended to 20GB now,
the debug.log was only 155MB in size

Upgraded both of my testnet sanctuaries to v1.0.9.7

In testnet3 folder, removed blocks and chainstate folders and relevant .dat files, reindexed
Since there was a protocol version increase, ran start-alias command for masternodes
Turned on 1 mining thread for wallet with CPID burn

Reference: How to Update and Clean Wallets:
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

Cool, I also updated my testnet-sanctuary.

Also updated a prod wallet. At first sight it seem to function as expected, and the 'Distributed Computing' tab is showing.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 03:04:26 PM

In prod version is asking for PODC pwd on boot and PODC tab is there too.
So can we try associate in prod? is it live now?

I tried to associate a new 'unbanked' account on the pool, and it seems to be working  8)

(https://preview.ibb.co/duKtXn/unbanked.png)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 03:07:15 PM
1.0.9.7 is working on my windows machine without error, although I did have to "clean" it, meaning erase all the files in the Biblepay Core folder except the biblepay.conf and the wallet.dat (i erased all the others in both main and test3)
I've made "clean" install but it didn't helped. Still same. After bootup PoDC pwd is wallet still locked and not generate.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 03:08:01 PM
I'm still not getting any tasks on my Android.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 03:10:38 PM
I've made "clean" install but it didn't helped. Still same. After bootup PoDC pwd is wallet still locked and not generate.

I've tried a couple of things, and on windows the new wallet is functioning fine with both unlocked and locked wallets in testnet as well as prod. I didn't even do a clean install.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 03:14:19 PM
I've made "clean" install but it didn't helped. Still same. After bootup PoDC pwd is wallet still locked and not generate.

Are you absolutely sure you've entered the right password, because when I open my wallet and enter a wrong password purposely, the wallet does open, but gives me the same 'Failed to sign CPID signature' error.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 03:15:18 PM
I'm still not getting any tasks on my Android.

Me neither...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 03:17:41 PM
Me neither...

And it's funny that no one seems to be asking about it on the Rosetta forums.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 03:30:16 PM
https://boinc.bakerlab.org/rosetta/server_status.php

You can see there it appears they have run out of Android tasks

Application                    Unsent    In progress    Runtime of last 100 tasks in hours: average, min, max    Users in last 24 hours
Rosetta for Android    0           7508            6.54 (0.46 - 97.78)                                                                    793

Only about 3% use Rosetta for Android, and it pulls from a totally different set than the rest.  Windows, Linux, Mac, they all pull from either Rosetta or Rosetta Mini.

Thanks for the link.

https://boinc.bakerlab.org/rosetta/forum_forum.php?id=201

Lets see if anyone responds.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 03:36:10 PM
https://boinc.bakerlab.org/rosetta/server_status.php

You can see there it appears they have run out of Android tasks

Application                    Unsent    In progress    Runtime of last 100 tasks in hours: average, min, max    Users in last 24 hours
Rosetta for Android    0           7508            6.54 (0.46 - 97.78)                                                                    793

Only about 3% use Rosetta for Android, and it pulls from a totally different set than the rest.  Windows, Linux, Mac, they all pull from either Rosetta or Rosetta Mini.

Yeah, they do seem to send some out from time to time, because I've seen the 'unsent' amount sit at '2' when I watched yesterday.

Also. West, I didn't see you on the pool leaderboard today. Is that a bug on the side of the pool, or can you confirm that your testnet-wallet had been offline somewhere in the past couple of days (and didn't receive payment)?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 03:37:48 PM
My understanding is genproclimit of 1 is the minimum, you can use as much as you want to and will still be PoBh mining with that.  In fact, if you're NOT using BOINC at that computer, for the health of the network you should run it as high as possible in my opinion.

1.0.9.7 is working on my windows machine without error, although I did have to "clean" it, meaning erase all the files in the Biblepay Core folder except the biblepay.conf and the wallet.dat (i erased all the others in both main and test3)

Running it higher than 1 thread is just a waste of electricity, unless you want to waste electricity to try to solo mine blocks (at a 90% discounted reward rate).

We have DGW and distinct CPIDs for pobh security.

And yes, using more threads increases processor utilization, but not as much as pure POBH did (PODC has a sleep in each thread at each noncebreak limit).  But I dont believe it uses all the proc, thats probably another bad test on Slovakias part.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 03:47:52 PM
I hope they do, because Android tasks are pretty important for the real unbanked.  But I can also see if they have less than 3% of their users on it and I doubt there are too many people running more than a pair of Androids, but there are a bunch running multiple PCs.  Plus the PCs are doing much more work per machine on average, so I would be pretty confident in a guess that less than half a percent of the work is done by Android so it's likely not a high priority.

I was actually thinking the other day in the shower.....that there should be another way to make money than "mining". There's got to be a better way for the unbanked to participate in this new economy. Won't go into too much detail but I think you know what I mean.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 03:58:36 PM
9 testnet Sanctuaries running.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:00:25 PM
I did an upgrade this morning (actually a pair, one to the last .96 and one to the .97).  I just got a payment at 15;13 CST (about 20 minutes ago).

getmininginfo looks good, exec getboincinfo looks good, exec leaderboard shows me on it.

Ok great!  I just wanted to make sure, because your account being missing on the pool side I think has something to do with the pools SQL join - so the accounts that dropped out - in the core wallet over 1 day, that Jaap mentioned, I think were due to missing UTXO or task weight...

Ill fix the pool display & leaderboard tonight when I get home...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:03:18 PM
9 testnet Sanctuaries running.

I noticed my Hot sanc wouldnt start in 70716 (in testnet) until I cleared the data like West suggested, now my hot sanc is started and running 70716.

Thats good to know, because I really dont want to forcefully (cause Prod nodes to hang up on all prior version in prod unless we have to)...  so tomorrow, If we can start a few of our Prod  70716 sancs - and test them in prod to ensure they start in prod 70716 mode - then I think we can sail through Wednesday.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:06:27 PM
I tried to associate a new 'unbanked' account on the pool, and it seems to be working  8)

(https://preview.ibb.co/duKtXn/unbanked.png)

Wow, thats amazing, as I didnt even test it - I actually didnt know the pool was upgraded already , ok sweet.
Well, let me know if you receive a payment to that particular address?

Btw, in the latest version, the payments now say "Superblock" or "PODC - Research" depending on the source of the revenue.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 04:06:57 PM
Are you absolutely sure you've entered the right password, because when I open my wallet and enter a wrong password purposely, the wallet does open, but gives me the same 'Failed to sign CPID signature' error.
Yes I'm sure that i put there right pwd. After opening i can unlock it without problem. Ok. nevermind. maybe it is only some bug on my wallet or pc.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 04:07:29 PM
I noticed my Hot sanc wouldnt start in 70716 (in testnet) until I cleared the data like West suggested, now my hot sanc is started and running 70716.

Thats good to know, because I really dont want to forcefully (cause Prod nodes to hang up on all prior version in prod unless we have to)...  so tomorrow, If we can start a few of our Prod  70716 sancs - and test them in prod to ensure they start in prod 70716 mode - then I think we can sail through Wednesday.

I always clear the files before I upgrade. So I'm a little confused about updating in production. Should I update my Sanctuary now? If I only update my controller wallet will I still get the rewards? I'm cautious because the protocol version is different.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:08:02 PM
I've made "clean" install but it didn't helped. Still same. After bootup PoDC pwd is wallet still locked and not generate.
Yes like Jaap said, I think you might be entering a bad password on boot.  Please be sure you have the absolute latest version first, as we definitely had a bug in that password box up to yesterday!  So after you boot you can type 'walletpassphrase pass 9999' and see if you are typing the correct passphrase.  Then reboot, type it in, and you should not be receiving the getmininginfo errors.  I tested last night and Jaap tested, working for us now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 04:09:00 PM
Me neither...
I have received 4 task on 2 mobile phones today and 2 tasks yesterday...
It looks that I just have a luck :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:09:05 PM
Yes I'm sure that i put there right pwd. After opening i can unlock it without problem. Ok. nevermind. maybe it is only some bug on my wallet or pc.

We reserve 800 characters for the pass.  Does it contain spaces or control characters?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 04:09:44 PM
I was actually thinking the other day in the shower.....that there should be another way to make money than "mining". There's got to be a better way for the unbanked to participate in this new economy. Won't go into too much detail but I think you know what I mean.

Lol, I don't know what you mean, but I have been thinking about this too. I have an idea but need to thresh it out some more. Are you on slack/Discord?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:10:59 PM
I always clear the files before I upgrade. So I'm a little confused about updating in production. Should I update my Sanctuary now? If I only update my controller wallet will I still get the rewards? I'm cautious because the protocol version is different.

If you upgrade Prod now, your only issues is you will not be able to Vote yet (but dont worry about that as people will be upgrading and be in the same boat - and im upgrading the pool tonight for the sake of the proposal voting), and your heat miner runs a tad slower.  Heat mining seems to be a lost cause right now anyway.

After we have 51% of the sancs upgraded to 70716, voting works again.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 04:14:05 PM
Lol, I don't know what you mean, but I have been thinking about this too. I have an idea but need to thresh it out some more. Are you on slack/Discord?

I'm on discord. tmike. Has the new dev said anything? I haven't heard a peap from him.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:14:24 PM
I should be able to switch over my MN in the late morning on Monday.

Two questions.

When it says PoDC starts on block 33,440 does that mean that is the first paying block for the PoDC or that the PoDC block will be one day later?

Second, when saying one day, is that 24 hours or 202 blocks?

On block 33440, we start reserving PODC budget payments in each block, and 33441 starts the very low heat miner payment (600).
And 33441 starts the 7 minute block targets.  We have one PODC superblock every 202 blocks.  I will share the command for the PODC superblock budget asap also.
The first PODC superblock should be 33440 + 11 + 202 roughly - as long as the sancs are a supermajority on 70716 and can vote by then....
Also, everyone will need to associate their cpids in prod...btw.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 04:16:16 PM
If you upgrade Prod now, your only issues is you will not be able to Vote yet (but dont worry about that as people will be upgrading and be in the same boat - and im upgrading the pool tonight for the sake of the proposal voting), and your heat miner runs a tad slower.  Heat mining seems to be a lost cause right now anyway.

After we have 51% of the sancs upgraded to 70716, voting works again.

OK, I'll try to update both later tonight or tomorrow morning.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 04:18:50 PM

Also, everyone will need to associate their cpids in prod...btw.
Sorry if dumb question, can we do that now or do we wait for block 33440?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 04:19:57 PM
Wow, thats amazing, as I didnt even test it - I actually didnt know the pool was upgraded already , ok sweet.
Well, let me know if you receive a payment to that particular address?

Btw, in the latest version, the payments now say "Superblock" or "PODC - Research" depending on the source of the revenue.

Well, the pool says it's still on 1095 on the 'about' page, but the popup seems to suggest that it worked. I hope that my phone will be getting new tasks in the coming days, because I don't have any RAC on that account yet...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:21:22 PM
I'm on discord. tmike. Has the new dev said anything? I haven't heard a peap from him.

The core dev is now working on compiling the base, the mobile dev sent me some info about a mobile wallet but it looked very unusual, like a wallet that is not based on Crypto, maybe it is for amazon, Im trying to get more info.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:25:01 PM
Thanks for the quick reply,  I was guessing it would be that way but didn't want to spread a guess too far without confirming it from you.

So 33441 starts : PodC budget reservation to be paid every 202 blocks starting with 33653, 7 minute targets (woo-hoo) and reformatted heat PoBh mining.

What is the official name for the PoDC Superblock?  And have we seen what happens when the PoDC superblock falls on a MN Superblock?

I just called it a PODC Superblock so far as compared to a budget superblock.  For one the collission should not be possible (think of n+202+202+202... compared to 202*30 + 202*30 ... with different starting heights for each) , but the overarching answer is if they were to fall on the same block number, the highest voted triggerheight would win.  So only one would pay.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 04:27:38 PM
Sorry if dumb question, can we do that now or do we wait for block 33440?
Not dumb at all, especially when there are no instructions.  You can do it now in prod :).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 04:30:02 PM
Not dumb at all, especially when there are no instructions.  You can do it now in prod :).
Ok. I'll try to make it in prod version.

Btw. I don't know if i'm on good block in testnet. Please give me some actual block and blockhash.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 04:32:09 PM
Not dumb at all, especially when there are no instructions.  You can do it now in prod :).
Perfect! Thanks.
I see we are top 15 Rosetta team... we will likely be top 3 by the end of the month.

Great work everyone!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 04:46:23 PM
Ok. I'll try to make it in prod version.

Btw. I don't know if i'm on good block in testnet. Please give me some actual block and blockhash.

Code: [Select]
23:46:04

getblockhash 15508


23:46:04

ae40c3edf8874e7a6c78d1a9720d3460a7c9d98d88e28b92cdb02777a136aaca
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 05:08:41 PM
Ok. I'll try to make it in prod version.

Btw. I don't know if i'm on good block in testnet. Please give me some actual block and blockhash.
Result after trying to add PODC to prod version:
  "Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

after waiting 5 block same message.

EDIT: waiting little bit more :) and I was successful. I was too impatient.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 05:12:51 PM
Yes like Jaap said, I think you might be entering a bad password on boot.  Please be sure you have the absolute latest version first, as we definitely had a bug in that password box up to yesterday!  So after you boot you can type 'walletpassphrase pass 9999' and see if you are typing the correct passphrase.  Then reboot, type it in, and you should not be receiving the getmininginfo errors.  I tested last night and Jaap tested, working for us now.
I've changed password to simple "password"... but didn't helped. I don't know..
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 05:48:09 PM
Not dumb at all, especially when there are no instructions.  You can do it now in prod :).
Since I have already linked Rosetta to BBP in testnet, in Prod should i do

Code: [Select]
exec associate rosetta_email_address rosetta_password
OR

Code: [Select]
exec associate rosetta_email rosetta_pass force
I'm updating my wallet for prod now.
Will do my Sanctuary and controller wallet  later today.

Thanks!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 04, 2018, 05:53:52 PM
Since I have already linked Rosetta to BBP in testnet, in Prod should i do

Code: [Select]
exec associate rosetta_email_address rosetta_password
OR

Code: [Select]
exec associate rosetta_email rosetta_pass force
I'm updating my wallet for prod now.
Will do my Sanctuary and controller wallet  later today.

Thanks!

Small correction.
the right force command is:
Code: [Select]
exec associate rosetta_email rosetta_pass trueat the end you must write TRUE not force
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 04, 2018, 06:13:26 PM
My TaskWeight and UTXOWeight are 100
but I think its saying my Magnitude is 0?

Code: [Select]
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41951758.00458577,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15493,
  "timeoffset": 0,
  "connections": 16,
  "proxy": "",
  "difficulty": 0.1304545155954208,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422278,
  "NextSuperblockHeight": 15543,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 42468.79,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 42468.79,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4299843,
  "Total Budget (One Day)": 13392850,
  "Total Budget (One Week)": 79670455,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514,8415",
  "Last Superblock Height": 15444,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 53.97035827145709
}

./biblepay-cli getblockhash 15508
ae40c3edf8874e7a6c78d1a9720d3460a7c9d98d88e28b92cdb02777a136aaca

After Superblock at 15543:

ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41963981.79231373,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15551,
  "timeoffset": 0,
  "connections": 17,
  "proxy": "",
  "difficulty": 0.1200567171124102,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422279,
  "NextSuperblockHeight": 15642,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 43224.22,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 43224.22,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4016960,
  "Total Budget (One Day)": 14732135,
  "Total Budget (One Week)": 79650060,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15543,15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514",
  "Last Superblock Height": 15543,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 50.43260482164106
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 04, 2018, 06:18:28 PM
Thanks for the link.

https://boinc.bakerlab.org/rosetta/forum_forum.php?id=201

Lets see if anyone responds.

I also posted here:

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=6982&postid=88421#88421
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 07:10:31 PM
My TaskWeight and UTXOWeight are 100
but I think its saying my Magnitude is 0?

Code: [Select]
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41951758.00458577,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15493,
  "timeoffset": 0,
  "connections": 16,
  "proxy": "",
  "difficulty": 0.1304545155954208,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422278,
  "NextSuperblockHeight": 15543,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 42468.79,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 42468.79,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4299843,
  "Total Budget (One Day)": 13392850,
  "Total Budget (One Week)": 79670455,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514,8415",
  "Last Superblock Height": 15444,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 53.97035827145709
}

./biblepay-cli getblockhash 15508
ae40c3edf8874e7a6c78d1a9720d3460a7c9d98d88e28b92cdb02777a136aaca

After Superblock at 15543:

ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41963981.79231373,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15551,
  "timeoffset": 0,
  "connections": 17,
  "proxy": "",
  "difficulty": 0.1200567171124102,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422279,
  "NextSuperblockHeight": 15642,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 43224.22,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 43224.22,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4016960,
  "Total Budget (One Day)": 14732135,
  "Total Budget (One Week)": 79650060,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15543,15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514",
  "Last Superblock Height": 15543,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 50.43260482164106
}

Since your RAC, Team, and Weights are good: your good.  The client generally uses the 7 day magnitude figure.  The 1 day mag just means you were not in the last superblock, (see last superblock payment), and thats rare, but its because the testnet sancs cant vote on a contract until we get the protocol upgrade disseminated.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 07:11:34 PM
Since I have already linked Rosetta to BBP in testnet, in Prod should i do

Code: [Select]
exec associate rosetta_email_address rosetta_password
OR

Code: [Select]
exec associate rosetta_email rosetta_pass force
I'm updating my wallet for prod now.
Will do my Sanctuary and controller wallet  later today.

Thanks!

You can always do the former, without the force=true, unless you are moving an already associated CPID to a new wallet.

Besides, if that happens it will throw the error "ALREADY_IN_CHAIN", then you can do force=true.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 07:33:34 PM
You can always do the former, without the force=true, unless you are moving an already associated CPID to a new wallet.

Besides, if that happens it will throw the error "ALREADY_IN_CHAIN", then you can do force=true.

Thanks Rob and Orbis!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 07:43:51 PM
Hi all, can I please clarify what is needed in the config file.
What is the command to set my percentage of coins for stake?

So far my config file is:

Code: [Select]
addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network
gen=1
genproclimit=1

Thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 07:48:36 PM
Hi all, can I please clarify what is needed in the config file.
What is the command to set my percentage of coins for stake?

So far my config file is:

Code: [Select]
addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network
gen=1
genproclimit=1

Thanks :)


Please set :
polpercentage=50

For 50% of your coins to be staked once every ~12 hours.  The default in the wallet is 10% of the coins.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 07:55:16 PM

Please set :
polpercentage=50

For 50% of your coins to be staked once every ~12 hours.  The default in the wallet is 10% of the coins.

Awesome! thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 08:19:53 PM
Ok I set up a wallet running in qt mode in prod.
I have associated my cpid and it seemed happy.

getinfo gives me

Code: [Select]
"version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 9.05762053,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33038,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 3207.285566212733,
  "testnet": false,
  "keypoololdest": 1507790364,
  "keypoolsize": 1007,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

getmininginfo gives me
Code: [Select]
"blocks": 33038,
  "currentblocksize": 2034,
  "currentblocktx": 2,
  "difficulty_podc": 0,
  "difficulty_pow": 32072.85566212733,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 206993854304.6948,
  "hashps": 86.77371370534651,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 96544,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 169,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false


Are there other commands I should be checking to see weights etc?

EDIT: By the way, my wallet does not yet have a password on it. Is this OK? I assumed this means it is always unlocked for staking...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 08:28:57 PM
My TaskWeight and UTXOWeight are 100
but I think its saying my Magnitude is 0?

Code: [Select]
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41951758.00458577,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15493,
  "timeoffset": 0,
  "connections": 16,
  "proxy": "",
  "difficulty": 0.1304545155954208,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422278,
  "NextSuperblockHeight": 15543,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 42468.79,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 42468.79,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4299843,
  "Total Budget (One Day)": 13392850,
  "Total Budget (One Week)": 79670455,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514,8415",
  "Last Superblock Height": 15444,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 53.97035827145709
}

./biblepay-cli getblockhash 15508
ae40c3edf8874e7a6c78d1a9720d3460a7c9d98d88e28b92cdb02777a136aaca

After Superblock at 15543:

ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli getinfo
{
  "version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 41963981.79231373,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 15551,
  "timeoffset": 0,
  "connections": 17,
  "proxy": "",
  "difficulty": 0.1200567171124102,
  "testnet": true,
  "keypoololdest": 1507584559,
  "keypoolsize": 1001,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
ubuntu@ip-172-31-34-47:~/biblepay/src$ ./biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "93138f032bdd027fa3246b48bb715a77",
  "Address": "yjUmY8EmuSKf6EWJf4aajWovksV2TQbxWc",
  "CPIDS": "93138f032bdd027fa3246b48bb715a77;",
  "CPID-Age (hours)": 422279,
  "NextSuperblockHeight": 15642,
  "NextSuperblockBudget": 1339285,
  "93138f032bdd027fa3246b48bb715a77_RAC": 43224.22,
  "93138f032bdd027fa3246b48bb715a77_TEAM": 15044,
  "93138f032bdd027fa3246b48bb715a77_TaskWeight": 100,
  "93138f032bdd027fa3246b48bb715a77_UTXOWeight": 100,
  "Total_RAC": 43224.22,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 4016960,
  "Total Budget (One Day)": 14732135,
  "Total Budget (One Week)": 79650060,
  "Superblock Count (One Week)": 72,
  "Superblock Hit Count (One Week)": 60,
  "Superblock List": "15543,15444,15345,15246,15147,15048,14949,14850,14751,14652,14553,14454,14355,14256,14157,14058,13860,13761,13365,13167,13068,12969,12870,12771,12672,12573,12474,12375,12276,12177,12078,11979,11880,11781,11682,11583,11484,11385,11286,11187,11088,10989,10890,10791,10494,10395,10296,10197,10098,9999,9900,9801,9702,9603,9306,9207,8910,8811,8712,8514",
  "Last Superblock Height": 15543,
  "Last Superblock Budget": 1339285,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 50.43260482164106
}


Wait, I spoke too soon, Ive been analyzing your data ever since I replied, to see if any superblocks have actually been created in testnet over the last few hours while Ive been gone, and actually they have been being created without your 9313* CPID in them... So, yes something is awry with your account.

Let me debug this and get to the bottom of it.  If we need a code change, then thanks for discovering this for us, this is the beauty of having full coverage in testnet.

Don't worry, we will not go live without you, if this is flaw, lets hold the network back until you are in the contract.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 08:38:18 PM

Wait, I spoke too soon, Ive been analyzing your data ever since I replied, to see if any superblocks have actually been created in testnet over the last few hours while Ive been gone, and actually they have been being created without your 9313* CPID in them... So, yes something is awry with your account.

Let me debug this and get to the bottom of it.  If we need a code change, then thanks for discovering this for us, this is the beauty of having full coverage in testnet.

Don't worry, we will not go live without you, if this is flaw, lets hold the network back until you are in the contract.

So Togo, the reason you are missing is your CPID exploited a circumstance not caught in testing:  A circumstance where a researcher is part of team biblepay, then one who is not, then one immediately who follows - a particular flag was not being handled properly causing certain accounts to be skipped. 

Fixed.

We will need everyone + Sancs to upgrade to 1.0.9.8.

Windows is compiling.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 08:41:08 PM

Biblepay 1.0.9.8
Mandatory Upgrade for Testnet


- Handle Rosetta Teams properly - to avoid CPIDs from being skipped in the superblock

** Windows is compiling **
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 08:45:14 PM
Ok I set up a wallet running in qt mode in prod.
I have associated my cpid and it seemed happy.

getinfo gives me

Code: [Select]
"version": 1000907,
  "protocolversion": 70716,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.7",
  "balance": 9.05762053,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33038,
  "timeoffset": 0,
  "connections": 8,
  "proxy": "",
  "difficulty": 3207.285566212733,
  "testnet": false,
  "keypoololdest": 1507790364,
  "keypoolsize": 1007,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

getmininginfo gives me
Code: [Select]
"blocks": 33038,
  "currentblocksize": 2034,
  "currentblocktx": 2,
  "difficulty_podc": 0,
  "difficulty_pow": 32072.85566212733,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 206993854304.6948,
  "hashps": 86.77371370534651,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 96544,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 169,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false


Are there other commands I should be checking to see weights etc?

EDIT: By the way, my wallet does not yet have a password on it. Is this OK? I assumed this means it is always unlocked for staking...


So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 08:46:04 PM
Im going to analyze the pool.biblepay.org next for missing users, please, post here if we have any other critical issues that need fixed before the end of the night?


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 08:49:44 PM

So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....

Awesome, I will do once 6 blocks are gone.
I will not upgrade to new version just yet then
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 04, 2018, 08:51:52 PM
Glad I could help a little Rob! Wouldnt be possible without you though 8)

Updating to v1.0.9.8 now
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 09:07:48 PM

So this is a very, very good guinea pig test.  After 6 blocks could you please do an 'exec datalist dcc', this is a secret command, see if your CPID is in the list.  I believe the "FAILED TO SIGN CPID Error" is occuring, because you just associated yourself.  Once its in the list try a reboot then check getmininginfo again just to see that the error cleared?

Yes if you are not encrypted, your not locked (lock on the front bottom right GUI overview should be Open), so no it should not be a lock issue....

OK here we go "exec datalist dcc"

Code: [Select]
"DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 00:24:09)": "04fba56d89a5eb38b1b82f8a6240132c;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;1981529;H1MouWGO6yWBk/fQBKp0OTEGApw9FZY5Tnbf8BQz1LujYjQnY/PyPhpd+tjce2vpUhIYaQ/4cxrMF0lfYwg9wSU=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}

I'm sorry, to me it is gibberish.


"getmininginfo"

Code: [Select]
{
  "blocks": 33045,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 33728.72968180398,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 228922584200.2176,
  "hashps": 88.14359163965726,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 354736,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 614,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
}

That error has gone...


"exec getboincinfo"

Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422283,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_RAC": 24261.07,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 24261.07,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0

So it looks to be working fine!

Should I upgrade my prod wallet to 1098?

My UXTO weight is zero, but I have only a few BBP (I need to backup wallet first)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 09:09:53 PM
The staking percentage command is suppose to be in the controller wallet config file right?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 09:10:57 PM
The staking percentage command is suppose to be in the controller wallet config file right?
I have this as my config file for my PoDC wallet (not Sanctuary)

addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network
gen=1
genproclimit=1
polpercentage=50
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 09:27:28 PM
"hashps": 74.40307451385468,
  "minerstarttime": "03-05-2018 02:19:07",
  "hashcounter": 296188,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": false,

I think you said the wallet automatically starts with gen=1 right? So why is biblepay-generate: false
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 09:29:18 PM
How do I debug "PODCUpdate": false? I updated my windows wallet about an hour ago. getboincinfo and getmininginfo both show no errors and the CPID is associated. OR does it say false because my CPID is already in the system?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:36:53 PM
How do I debug "PODCUpdate": false? I updated my windows wallet about an hour ago. getboincinfo and getmininginfo both show no errors and the CPID is associated. OR does it say false because my CPID is already in the system?
It really should only say false if your wallet does not have enough funds to send 1 bbp out, or if its locked.
Could you please try a 'sendtoaddress YYYY 1" to yourself to see if that succeeds?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:38:31 PM
"hashps": 74.40307451385468,
  "minerstarttime": "03-05-2018 02:19:07",
  "hashcounter": 296188,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": false,

I think you said the wallet automatically starts with gen=1 right? So why is biblepay-generate: false

Right, it starts with 1 thread and generate=true now.  The "generate": = false, thats a bug!  I just fixed it , but it is low priority so it will be in next build.  But yes, it should be running with some HPS, usually about 50 HPS.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:44:47 PM
OK here we go "exec datalist dcc"

Code: [Select]
"DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 00:24:09)": "04fba56d89a5eb38b1b82f8a6240132c;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;BHUyNiVgRcW4ZudFmyyzJydL9t2QW8fdWD;1981529;H1MouWGO6yWBk/fQBKp0OTEGApw9FZY5Tnbf8BQz1LujYjQnY/PyPhpd+tjce2vpUhIYaQ/4cxrMF0lfYwg9wSU=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}

I'm sorry, to me it is gibberish.


"getmininginfo"

Code: [Select]
{
  "blocks": 33045,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 33728.72968180398,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 228922584200.2176,
  "hashps": 88.14359163965726,
  "minerstarttime": "03-05-2018 01:58:23",
  "hashcounter": 354736,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 614,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
}

That error has gone...


"exec getboincinfo"

Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422283,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_RAC": 24261.07,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 24261.07,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0

So it looks to be working fine!

Should I upgrade my prod wallet to 1098?

My UXTO weight is zero, but I have only a few BBP (I need to backup wallet first)

Great!  So it looks like you guys have debugged a lot of things in prod and I have not gotten around to feeling prod out yet - or associating a CPID.
Yes, I see you made it in the prod chain with exec datalist dcc, so that is very revealing for others, who have reported today they received that Unable to Sign CPID error.  So guys, if you just associated a CPID, and reboot before the 6th confirm, this is yet another way you could receive the "unable to sign cpid" other than not having enough to stake, or a locked wallet.

As far as upgrading no rush, as long as nothing goes wrong tomorrow, whenever you feel like it.  Im hoping we can form a sanctuary supermajority sometime Wednesday, (thats when the cutover block hits), and then lets not give word for the exchanges to upgrade until *after* we solve our first DC superblock in prod.  (Hopefully that will be Thursday evening).  (We can wait a couple extra days for good measure also).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:45:37 PM
** Rosetta Leaderboard Fixed in pool.biblepay.org **

It was an unrelated SQL issue, you should now all see yourselves and your machines, as long as you have not Hidden your machines.

I also made the pool refresh the leaderboard every hour.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 09:49:21 PM
The staking percentage command is suppose to be in the controller wallet config file right?

Yea, and just to clarify the UTXO staking wallet is always the one with the DC association.
You could have a controller for sanctuaries with 10 million in it, and a separate controller with 100K in it with your CPID associations and the unlocked wallet.  The important thing is to put the funds in the one with the association, because that wallet will then know how to loop through your CPIDs Tasks and send the PODCUpdate properly.

On a side note, if you associated 1 cpid on a laptop and then tried to use your home PC as your staking controller it wouldnt send PODC updates because it would not know your CPID list....


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 09:57:11 PM
It really should only say false if your wallet does not have enough funds to send 1 bbp out, or if its locked.
Could you please try a 'sendtoaddress YYYY 1" to yourself to see if that succeeds?

I used the GUI to send some to myself:
Transaction ID: edd8348af06de7463e3f95bf7381736581d4c03a932c3efee6f75b931bc3f974-000

So far haven't got a confirmation. But I did double check that my wallet is unlocked when I ran podcupdate.

UPDATE:
Looks like no confirmations after 13 min.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 10:05:48 PM
I used the GUI to send some to myself:
Transaction ID: edd8348af06de7463e3f95bf7381736581d4c03a932c3efee6f75b931bc3f974-000

So far haven't got a confirmation. But I did double check that my wallet is unlocked when I ran podcupdate.

UPDATE:
Looks like no confirmations after 13 min.

Looks like exec podcupdate has about 5 possible reasons to return false.   It should log the reason then return false.
So please try 'exec podcupdate' again, then immediately look at the log for the error.

Here is the most likely one:
   LogPrintf("\n PODCUpdate::Failed to Sign CPID Signature.  %s ",sError.c_str());
            

I believe that is happening when you dont have a CPID in the chain as of yet...


NOTE to all users:  You will never need to manually run exec podcupdate under normal circumstances; this is just to force it if your machine was off for long periods of time.


As far as the waiting for confirm:  Check the last block timestamp, its probably a lagging block.

** We just solved 33049; it probably confirmed

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 10:08:31 PM
Hi,

One of the Slovakian guys messaged me with an issue. i wonder if we can help. So I think this is the issue he is having:

Linux, commandline

1. He associated CPID to Wallet #1 (W1), he had receiving address RA1.
2. He wanted to change to wallet 2 (W2) with receiving address RA2. He typed
"exec associate mail pass true"
He received the message about welcome to cancer mining
3. The URL on this website https://boinc.bakerlab.org/rosetta/home.php
should be the wallet receiving address.
The URL matched RA2. Perfect!
4. He wasn't sure it had worked so he associated his CPID with wallet 2 again. This time there was a new address created and shown in the  https://boinc.bakerlab.org/rosetta/home.php site.
But he does not recognize the address. It is not RA1 or RA2. I checked, it is also not a mining address.
The question is, should this address on the boinc site be your receiving address of the wallet? Is there an error here?

5. He tried associating it again on another machine in QT mode. It worked fine and the address changed to his receiving address.


Seems that people may have issues if they associate CPID to the same wallet twice (by accident)

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 10:09:32 PM
Looks like exec podcupdate has about 5 possible reasons to return false.   It should log the reason then return false.
So please try 'exec podcupdate' again, then immediately look at the log for the error.

Here is the most likely one:
   LogPrintf("\n PODCUpdate::Failed to Sign CPID Signature.  %s ",sError.c_str());
            

I believe that is happening when you dont have a CPID in the chain as of yet...


NOTE to all users:  You will never need to manually run exec podcupdate under normal circumstances; this is just to force it if your machine was off for long periods of time.


As far as the waiting for confirm:  Check the last block timestamp, its probably a lagging block.

** We just solved 33049; it probably confirmed

The transaction I sent myself is getting confrimations now. The error I'm getting is:

2018-03-05 04:06:47
 PODCUpdate::Error: Insufficient funds.

But there is plenty of BBP in my wallet. Does it have to be under a certain wallet address? This is in production by the way.

UPDATE:
I think the issue might be the receiving address that is associated with my CPID doesn't have enough BBP in it. Trying again now.

UPDATE 2:
podcupdate returned true. I didn't know it was only using a certain receiving address. Thanks guys!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 10:12:23 PM
Hi,

One of the Slovakian guys messaged me with an issue. i wonder if we can help. So I think this is the issue he is having:

Linux, commandline

1. He associated CPID to Wallet #1 (W1), he had receiving address RA1.
2. He wanted to change to wallet 2 (W2) with receiving address RA2. He typed
"exec associate mail pass true"
He received the message about welcome to cancer mining
3. The URL on this website https://boinc.bakerlab.org/rosetta/home.php
should be the wallet receiving address.
The URL matched RA2. Perfect!
4. He wasn't sure it had worked so he associated his CPID with wallet 2 again. This time there was a new address created and shown in the  https://boinc.bakerlab.org/rosetta/home.php site.
But he does not recognize the address. It is not RA1 or RA2. I checked, it is also not a mining address.
The question is, should this address on the boinc site be your receiving address of the wallet? Is there an error here?

5. He tried associating it again on another machine in QT mode. It worked fine and the address changed to his receiving address.


Seems that people may have issues if they associate CPID to the same wallet twice (by accident)

I also associated my account to the same wallet twice because I forgot it takes a while before the CPID shows up in the GUI. Oh, I see waht address your talking about now. I wonder if that's why I'm having issues, I don't have enough BBP in that address.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 04, 2018, 10:26:19 PM
I also associated my account to the same wallet twice because I forgot it takes a while before the CPID shows up in the GUI. Oh, I see waht address your talking about now. I wonder if that's why I'm having issues, I don't have enough BBP in that address.

Hmm, I dont think it requires a specific sending address to send funds though - can you instead go into coin control and see how much is available that is not locked?  It could be that all is allocated to sanctuary locked funds?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 10:29:43 PM
Hmm, I dont think it requires a specific sending address to send funds though - can you instead go into coin control and see how much is available that is not locked?  It could be that all is allocated to sanctuary locked funds?

The receiving address that was on the Rosetta website did not have enough BBP in it. Once I put enough in, podcupdate shows true now. I actually had other receiving addresses on my account with BBP in them and none of them were locked except for the sanctuary wallet address.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 04, 2018, 10:41:52 PM
One comment, when I installed the windows wallet, the sanctuaries tab was hidden because of the PODC tab I think. I couldn't find it until I dragged the window larger. Someone new might have some trouble figuring that out. Now it just may be just me on my computer with the desktop configuration I have but I'm not sure.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 04, 2018, 11:30:07 PM
Ok I'm about to upgrade my wallet (in prod) to newest version.
Do I need to backup wallet.dat every time I upgrade wallet?

After I upgrade successfully I will transfer the stake to my wallet. Then is it true that my UXTO should be greater than 0?
Is it true that my taskweight will stay 0 until  the first superblock payout?

Thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 03:18:44 AM
Ok I'm about to upgrade my wallet (in prod) to newest version.
Do I need to backup wallet.dat every time I upgrade wallet?


I would always backup your wallet.dat, just in case :)
Don't know about your other questions...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 03:29:51 AM
I would always backup your wallet.dat, just in case :)
Don't know about your other questions...

thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 06:14:36 AM
thanks :)

You only need to backup your wallet once I believe, even if you added new addresses or had transactions after you backed it up.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 06:20:43 AM
You only need to backup your wallet once I believe, even if you added new addresses or had transactions after you backed it up.

That is not necessarily true. As far as I know, the wallet creates a new batch of keys after a certain number have been used (I think it's default number is 1000?), so if you do a lot of transactions, you have to redo your updates.

Also, if you have an unencrypted wallet.dat, and you encrypt it, you have to make a new backup, because the old wallet.dat becomes unusable as I understand it.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 07:06:57 AM
That is not necessarily true. As far as I know, the wallet creates a new batch of keys after a certain number have been used (I think it's default number is 1000?), so if you do a lot of transactions, you have to redo your updates.

Also, if you have an unencrypted wallet.dat, and you encrypt it, you have to make a new backup, because the old wallet.dat becomes unusable as I understand it.

I think Biblepay usese deterministic wallets so this does not apply. Rob, can you confirm this?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 07:19:48 AM
I think Biblepay usese deterministic wallets so this does not apply. Rob, can you confirm this?
On walletbackups, the dash subsystem does create a copy of wallet.dat once per boot and copies this file into \backups.  Something like mmddyyyy.dat. 
I recommend keeping a copy of a good wallet offsite - maybe on a CD and USB flash if possible in a safe.

Anyway regarding the necessity to make constant backups:  There is truth to both sides but let me explain this nuance.
It is true, that if you only have one plain vanilla address with all your BBP allocated to that address, no matter how big the physical wallet.dat file gets, you can always get back all your bbp, if you had a backup of that original small file somewhere.  The wallet will expand in size as you resync the chain and you will gain all your BBP back.

The specific issue that requires you to back your wallet more often is this:  If you *add* a receiving address to the wallet, it comes with 1000 keys, if you have been mining for a while, if the action of creating a new address (doing that creates a keypair - a private key and a public wallet address), if that resulted in creating a new keypair that was *not* in the original backup, *and* you send BBP from somewhere to that new address, now that part of your balance is *not* in the original wallet.  Now you need a new backup.

So you either have to cognizently re-send your BBP periodically to your *original* address, and then you are fine, *or* keep backing it up.

Btw, an easy way to understand this is if you loop through your addresses and balances, if you were to type:
dumpprivkey publicbbpaddress
For each address with a balance, you could print those keys out to a printer and have a way to gain access to the BBP if you ever lost the cold wallet backup...

Its also beneficial to consolidate your wallet as the core will run faster, but it also risks a loss of privacy.  The reason the devs made so many keys it to obfuscate your identity.  If you dont care about anonymity, by all means send it all back to one address.  If you do care about anonymity let it bloat and keep backing it up on a regular basis.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 07:33:18 AM
On walletbackups, the dash subsystem does create a copy of wallet.dat once per boot and copies this file into \backups.  Something like mmddyyyy.dat. 
I recommend keeping a copy of a good wallet offsite - maybe on a CD and USB flash if possible in a safe.

Anyway regarding the necessity to make constant backups:  There is truth to both sides but let me explain this nuance.
It is true, that if you only have one plain vanilla address with all your BBP allocated to that address, no matter how big the physical wallet.dat file gets, you can always get back all your bbp, if you had a backup of that original small file somewhere.  The wallet will expand in size as you resync the chain and you will gain all your BBP back.

The specific issue that requires you to back your wallet more often is this:  If you *add* a receiving address to the wallet, it comes with 1000 keys, if you have been mining for a while, if the action of creating a new address (doing that creates a keypair - a private key and a public wallet address), if that resulted in creating a new keypair that was *not* in the original backup, *and* you send BBP from somewhere to that new address, now that part of your balance is *not* in the original wallet.  Now you need a new backup.

So you either have to cognizently re-send your BBP periodically to your *original* address, and then you are fine, *or* keep backing it up.

Btw, an easy way to understand this is if you loop through your addresses and balances, if you were to type:
dumpprivkey publicbbpaddress
For each address with a balance, you could print those keys out to a printer and have a way to gain access to the BBP if you ever lost the cold wallet backup...

Its also beneficial to consolidate your wallet as the core will run faster, but it also risks a loss of privacy.  The reason the devs made so many keys it to obfuscate your identity.  If you dont care about anonymity, by all means send it all back to one address.  If you do care about anonymity let it bloat and keep backing it up on a regular basis.

Cool, thanks for the clarification.

https://bitcoin.org/en/secure-your-wallet says you don't need to do this anymore in the future. (When is the future?)
https://wiki.bitcoin.com/w/Securing_your_wallet says only 3 wallet types support BIP32 right now.
https://bitcointalk.org/index.php?topic=2484895.0 does say you need to backup. (Not sure about HD wallets.)
https://www.reddit.com/r/dashpay/comments/5wn16h/backups_of_dash_core_how_frequently/ does say you need to back up.

I think it just comes down to if BIP 0032 was implemented.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 08:02:18 AM
My UTXO is still zero after 9 hours, I think I remember you saying I need to wait 24 hours? I updated my production sanctuary and wallet and everything seems to be working fine. I'll let you know when I receive a Sanctuary payment.

Code: [Select]


exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422293,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 4746.2,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 0,
  "Total_RAC": 4746.2,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

exec datalist dcc

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 08:37:48)": "04fba56d89a5eb38b1b82f8a6240132c;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;1981529;INQ84/j9PlIAiksMlIWytRUWeT1Oy1IUearmIBEQwhSGPyv91yrspBm6SoYXiLQ3g5XTKXBNWBQcrs+GQfLbuzI=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "CA895B47AACFFBDBF906201821AF2F9F (03-05-2018 13:27:33)": "ca895b47aacffbdbf906201821af2f9f;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;475629;H1QQr77z7khrCeX3CJn6iUAQRqmqRZyIAl1CJdfeJx3oG9wfeJknjhmBvuokvJSUhqC+3+nzWhsr7T3MOkSoFqg=;0",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-05-2018 13:22:45)": "d9b22fccfae5582d4ee7838883aaa3cf;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;1981615;IO9jRoYdWOO9iSFJ+yBLrlIqAhzyxKAv16jrpLrB3sqfEBhHuO+Tu8UWNQISXmp1cUePVOKJm8TBvY8gN8DsVuY=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 05, 2018, 08:44:02 AM

Biblepay 1.0.9.8
Mandatory Upgrade for Testnet


- Handle Rosetta Teams properly - to avoid CPIDs from being skipped in the superblock

** Windows is compiling **

I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 08:58:37 AM
I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet

I'm updating my sanctuary as we speak...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 09:58:00 AM
I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet

Yeah I only updated one of my two so far, but I did jump in 15 mins ago to see how 1.0.9.8 is propagating on the sancs, to see if your CPID, the 9313 made it into any contracts yet, and so far I see since all these sancs are supermajority the old version you have not yet been included- But, I see the next contract : at block 16236, looks like it will have you in it.  I was waiting for this to happen before recommending anyone upgrade Prod sancs.

Ill go ahead and upgrade my other testnet sanc, and wait til we see you receive payment, then if no other bugs occur, we can try to upgrade some of our prod sancs.

Mike, UTXO weight shold not take long - should take 6 blocks - let me do some testing on that before I reply, it might be the conditions in Prod are different - are you referring to your UTXO weight in prod or test?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:00:41 AM
I think there are only 4 testnet sanctuaries enabled?
Mine are both on v1.0.9.8

How to Setup Testnet Sanctuary:
http://wiki.biblepay.org/Distributed_Computing_2#PART_F._.28OPTIONAL.29_Setup_Sanctuary_.28Masternode.29_in_Testnet

Nice avatar Togo, thats wild!


1.0.9.8 is out there now for windows...


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:04:16 AM
My UTXO is still zero after 9 hours, I think I remember you saying I need to wait 24 hours? I updated my production sanctuary and wallet and everything seems to be working fine. I'll let you know when I receive a Sanctuary payment.

Code: [Select]


exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422293,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 4746.2,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 0,
  "Total_RAC": 4746.2,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

exec datalist dcc

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 08:37:48)": "04fba56d89a5eb38b1b82f8a6240132c;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;1981529;INQ84/j9PlIAiksMlIWytRUWeT1Oy1IUearmIBEQwhSGPyv91yrspBm6SoYXiLQ3g5XTKXBNWBQcrs+GQfLbuzI=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "CA895B47AACFFBDBF906201821AF2F9F (03-05-2018 13:27:33)": "ca895b47aacffbdbf906201821af2f9f;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;475629;H1QQr77z7khrCeX3CJn6iUAQRqmqRZyIAl1CJdfeJx3oG9wfeJknjhmBvuokvJSUhqC+3+nzWhsr7T3MOkSoFqg=;0",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-05-2018 13:22:45)": "d9b22fccfae5582d4ee7838883aaa3cf;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;1981615;IO9jRoYdWOO9iSFJ+yBLrlIqAhzyxKAv16jrpLrB3sqfEBhHuO+Tu8UWNQISXmp1cUePVOKJm8TBvY8gN8DsVuY=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}

Mike-
In testnet your e94 CPID has a 100 weight as of a few hours ago: E94C1704C75F731F8BFDE303F08408EE (03-05-2018 12:31:08)": "100
(exec datalist utxoweight) alluding to the fact that since you have multiple cpids, you probably didnt leave the controller wallet on long enough to send 5 UTXO's out.  Each CPID requires a separate UTXO.  So it might have looped through 4 of your CPIDS and Failed to send the 5th until you manually triggered  it a few hours ago... 

This is a good reason in Prod we should have One cpid, of course for testing, I realize this is why we have multiple CPIDs.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 10:05:42 AM
Yeah I only updated one of my two so far, but I did jump in 15 mins ago to see how 1.0.9.8 is propagating on the sancs, to see if your CPID, the 9313 made it into any contracts yet, and so far I see since all these sancs are supermajority the old version you have not yet been included- But, I see the next contract : at block 16236, looks like it will have you in it.  I was waiting for this to happen before recommending anyone upgrade Prod sancs.

Ill go ahead and upgrade my other testnet sanc, and wait til we see you receive payment, then if no other bugs occur, we can try to upgrade some of our prod sancs.

Mike, UTXO weight shold not take long - should take 6 blocks - let me do some testing on that before I reply, it might be the conditions in Prod are different - are you referring to your UTXO weight in prod or test?

I think I'm having the same problems that Mike has (in prod): I can't use the 'podcupdate' command and don't get Task/UTXO weight after 6+ blocks.

Code: [Select]
16:11:48

exec podcupdate


16:12:28

{
  "Command": "podcupdate",
  "PODCUpdate": false
}

Code: [Select]

16:08:10

exec getboincinfo


16:08:12

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


The log says:

" PODCUpdate::Error: Insufficient funds. "

Which is weird, because I can make normal payments. I also send some funds to the Rosetta adress (BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD) and tried podcupdate, but it didn't help.

I must say that I was on a 1.0.9.7. wallet when I associated my CPID. Now I tried to associate my rosetta account on an different wallet with 1.0.9.8. and I'm going to wait for a minimum of six blocks to see I if I can get some UTXO/Task Weight there.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:17:27 AM
Heres another thing that sheds light on part of the problem in prod, giving the false perception that utxo weight is taking long long time to confirm:

In one of the prior versions of PODC between 1092-1095 or so, we expanded the size of the vout transaction message field for PODC tasks.  However most of Prod is running the old version (68% on 1.0.81 and 23% on 1087), heinously bad situation, so basically Prod will not propagate the long fields required for PODC updates.  Until we start getting some updates going.  So we are sort of DOA in prod until we take action.  Note, the short PODC updates will propagate that explains why some work.

In reality, a PODC update should propagate in 6 confirms.  Then everyone sees the UTXO weight as 100 on block #7.

As far as requiring the actual wallet address of the CPID to be filled with BBP, thats probably happening without me realizing that that particular "feature" was programmed in - its kind of important, as otherwise UTXOs will fail to send, Ill have to take a look at that in detail.  Maybe we should allow it to choose any coin available.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 10:22:15 AM

As far as requiring the actual wallet address of the CPID to be filled with BBP, thats probably happening without me realizing that that particular "feature" was programmed in - its kind of important, as otherwise UTXOs will fail to send, Ill have to take a look at that in detail.  Maybe we should allow it to choose any coin available.

Well actually, I sent BBP to the CPID wallet address because it seemed to work with Mike, but it made no difference in my case. It still returns the ' Insufficient funds' error.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:25:18 AM
I just remembered "why" its sending the UTXO stake amount from the CPID wallet address.
Its for security - we check the signature of the sender to ensure the senders address owns the CPID that sent the coinstake, and we check the CPID is related to the association tx, and we check the signature of the message is a valid sig for the cpid.  So this gives us the integrity of Address->UTXO->CPID->Tasks and the validation. 

We will need to add something to the instructions to send 60K or so over from yourself to the primary CPID BBP address on file.  As the CPID receives rewards it will be less of a problem.

Ill add the BBP address to getboincinfo, so we can see the addresses easier.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:28:38 AM
Well actually, I sent BBP to the CPID wallet address because it seemed to work with Mike, but it made no difference in my case. It still returns the ' Insufficient funds' error.

Try doing exec datalist dcc, picking your address to the clipboard for that particular CPID, then send some BBP to that address with
sendtoaddress address amount
Then doing the exec podcupdate again?

Im adding a feature now to show your address per cpid in exec getboincinfo, so this will be easier in prod.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:30:23 AM
My Zotac hard drive blew out 4 days into use!  So much for reliability...

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 10:32:55 AM
Same problem here.
Testing in prod.
CPID associated without problem. getinfo, getmininginfo, getboincinfo without problem.
but after podc update it gives false with debug "PODCUpdate::Unable to create PODC UTXO::Balance too low"
I've send funds to my CPID address more than 40 blocks ago.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:51:35 AM
Same problem here.
Testing in prod.
CPID associated without problem. getinfo, getmininginfo, getboincinfo without problem.
but after podc update it gives false with debug "PODCUpdate::Unable to create PODC UTXO::Balance too low"
I've send funds to my CPID address more than 40 blocks ago.

Oh Ok, I think we found a minor thing should not be a showstopper but will require another tweak in the final prod version-
Do me a favor, type 'exec stakebalance'.  Let me know what your Real unlocked balance is vs your stakebalance?

I believe the PODC update system is only looking for coins older than 24 hours.  We can remove that rule for Prod, as we are going by total balance, not by aged balance (as far as PODC UTXO's are concerned).  Yeah, that looks like the problem.  Fixing this now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 10:54:31 AM
Ok, Togo you made it!  Your in exec leaderboard in Test now.

So thats one huge thing out of the way.  All we have left now is:
- Large podc update handling (field size) in prod
- Sanc supermajority by version
- Non-Aged utxos

I think that sums it up.  Id like to form a game plan for prod before proceeding.
Im thinking with the botnet out there, judging by the fact that 68% are on a heinously old version, we may need to also add a mandatory upgrade flag for prod (IE we become the new network) in this next version.

But lets continue testing and ensure we squashed all the bugs before I create 1099.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 10:57:47 AM
Oh Ok, I think we found a minor thing should not be a showstopper but will require another tweak in the final prod version-
Do me a favor, type 'exec stakebalance'.  Let me know what your Real unlocked balance is vs your stakebalance?

I believe the PODC update system is only looking for coins older than 24 hours.  We can remove that rule for Prod, as we are going by total balance, not by aged balance (as far as PODC UTXO's are concerned).  Yeah, that looks like the problem.  Fixing this now.
it looks like possible problem:
Code: [Select]
{
  "Command": "stakebalance",
  "StakeBalance": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 11:18:56 AM
it looks like possible problem:
Code: [Select]
{
  "Command": "stakebalance",
  "StakeBalance": 0
}

Yeah, in UnitTest I just fixed it - its trying to use aged coins > 24 hours in coin_age only, fixed.


So that will be resolved in the next version.

Im thinking to kick the botnet off, we are going to need a flag set anyway to allow us to "be" the new prod network.

Any other issues we can think of for the next build?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 12:17:01 PM

Biblepay 1.0.9.9
Mandatory Upgrade


- Use standard unlocked wallet balance for PODC UTXO stakes
- Require mandatory protocol upgrade for sanctuaries to 70717
- Added BBP address to exec getboincinfo for each CPID

* Windows is now building *


This new version breaks compatibility in test & prod.  Lets all upgrade to 1099 in test, ensure its functioning and then in the evening Ill start recommending we upgrade in prod to ensure things are propagating.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 05, 2018, 12:28:11 PM
Super minor: Something Ive noticed after stopping Biblepay on Ubuntu, I get message written to the command line like this: "written 0.000000  written 960.000000  written 0.000000", the longer its been running the longer the message, I can only backspace a little of it, I just have to click enter and then type my next command in, hasnt caused any issues

Upgrading both of my testnet sanctuaries to v1.0.9.9
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 12:29:32 PM
Mike-
In testnet your e94 CPID has a 100 weight as of a few hours ago: E94C1704C75F731F8BFDE303F08408EE (03-05-2018 12:31:08)": "100
(exec datalist utxoweight) alluding to the fact that since you have multiple cpids, you probably didnt leave the controller wallet on long enough to send 5 UTXO's out.  Each CPID requires a separate UTXO.  So it might have looped through 4 of your CPIDS and Failed to send the 5th until you manually triggered  it a few hours ago... 

This is a good reason in Prod we should have One cpid, of course for testing, I realize this is why we have multiple CPIDs.

I was referring to my production controller wallet, I associated that CPID with my production wallet so I shoudn't be linked to the test wallet anymore. I checked the stake balance:

exec stakebalance

{
  "Command": "stakebalance",
  "StakeBalance": 85139
}

Code: [Select]
exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422298,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e94c1704c75f731f8bfde303f08408ee_RAC": 5117.84,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 0,
  "Total_RAC": 5117.84,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

exec podcupdate

{
  "Command": "podcupdate",
  "PODCUpdate": true
}

exec datalist dcc

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 08:37:48)": "04fba56d89a5eb38b1b82f8a6240132c;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;1981529;INQ84/j9PlIAiksMlIWytRUWeT1Oy1IUearmIBEQwhSGPyv91yrspBm6SoYXiLQ3g5XTKXBNWBQcrs+GQfLbuzI=;0",
  "1E7184E17377549D5A7D7A2EDFB51017 (03-05-2018 17:58:54)": "1e7184e17377549d5a7d7a2edfb51017;B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m;B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m;1982314;H1xGyUiI2Tpbw7TSUZ8wEymzPo4kbb2sHsy6Fn4WyqesOCMS1JxWqrdnqUo0wC4YwhC4lQEiOH7epkNycltZTfc=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "CA895B47AACFFBDBF906201821AF2F9F (03-05-2018 13:27:33)": "ca895b47aacffbdbf906201821af2f9f;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;475629;H1QQr77z7khrCeX3CJn6iUAQRqmqRZyIAl1CJdfeJx3oG9wfeJknjhmBvuokvJSUhqC+3+nzWhsr7T3MOkSoFqg=;0",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-05-2018 17:58:54)": "d9b22fccfae5582d4ee7838883aaa3cf;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;1981615;IO9jRoYdWOO9iSFJ+yBLrlIqAhzyxKAv16jrpLrB3sqfEBhHuO+Tu8UWNQISXmp1cUePVOKJm8TBvY8gN8DsVuY=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 05, 2018, 01:34:15 PM

Biblepay 1.0.9.9
Mandatory Upgrade


- Use standard unlocked wallet balance for PODC UTXO stakes
- Require mandatory protocol upgrade for sanctuaries to 70717
- Added BBP address to exec getboincinfo for each CPID

* Windows is now building *

This new version breaks compatibility in test & prod.  Lets all upgrade to 1099 in test, ensure its functioning and then in the evening Ill start recommending we upgrade in prod to ensure things are propagating.

Both of my testnet sanctuaries are upgraded and running
since protocol upgrade ran masternode start-alias commands again
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 01:50:06 PM
Rob... nice... 1099 workings great...
podcupdate is now true in prod ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 01:52:58 PM
Upgraded 9 sanctuaries to 1.0.9.9.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 01:59:47 PM
Super minor: Something Ive noticed after stopping Biblepay on Ubuntu, I get message written to the command line like this: "written 0.000000  written 960.000000  written 0.000000", the longer its been running the longer the message, I can only backspace a little of it, I just have to click enter and then type my next command in, hasnt caused any issues

Upgrading both of my testnet sanctuaries to v1.0.9.9
Oh OK, thanks, yes that was the debug log from when we started testing SSL.  OK, I removed it for the next version, thanks.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 02:00:54 PM
Rob... nice... 1099 workings great...
podcupdate is now true in prod ;)
Good to hear, all credit to Yeshua Hamashiach.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 02:24:46 PM
for sure...
please give me newest block nr and blockhash :)
test and prod
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 02:32:14 PM
for sure...
please give me newest block nr and blockhash :)
test and prod


Testnet:
getblockhash 16390

14:31:04

da5d2e13221e082e8946cb5efea75273f4cf76e0d9c671257bb6a5a4ed86b8a6

19~ connections.

Prod:  I havent attempted an upgrade yet :)


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 02:35:01 PM
I have 0 connection in prod...
clean install and now without connection
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 05, 2018, 02:38:27 PM
I have same blockhash as Rob and 13 connections on both of my nodes, hmmm

Oh in prod, my bad! I was talking about testnet
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 02:39:00 PM
Upgraded production to v1.0.9.9 but the daemon keeps crashing. Testnet is fine.

Code: [Select]
2018-03-05 20:32:17 Invalid or missing peers.dat; recreating
2018-03-05 20:32:17 ERROR: Read: Failed to open file /home/biblepay/.biblepaycore/banlist.dat
2018-03-05 20:32:17 Invalid or missing banlist.dat; recreating
2018-03-05 20:32:17 Loaded 0 addresses from peers.dat  0ms
2018-03-05 20:32:17  Starting Thread #0.000000 with Bible #0.000000      torcontrol thread start
2018-03-05 20:32:17 opencon thread start
2018-03-05 20:32:17 mnbcon thread start
2018-03-05 20:32:17 msghand thread start
2018-03-05 20:32:17 BibleMiner -- started thread 0.000000
2018-03-05 20:32:17 addcon thread start
2018-03-05 20:32:17 net thread start
2018-03-05 20:32:17 dnsseed thread start
2018-03-05 20:32:17 Loading addresses from DNS seeds (could take a while)
2018-03-05 20:32:17  ** Started 1.000000 BibleMiner threads. **
2018-03-05 20:32:17  Genesis Hash 3b4431310395638c0ed65b40ede4b110d8da70fcc0c2ed4a729fb8e4d78b4452
2018-03-05 20:32:17 init message: Done loading
2018-03-05 20:32:17 36 addresses found from DNS seeds
2018-03-05 20:32:17 dnsseed thread exit
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 02:42:04 PM
I have 0 connection in prod...
clean install and now without connection
I also have no connection in 1099 in prod.
No block source
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 02:43:19 PM
Windows 1.0.9.9 has been released, lets do some testing for a couple hours in prod also before I announce to the masses.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 02:43:55 PM
I also have no connection in 1099 in prod.
No block source

Its most likely due to node.biblepay.org (the main seed node being on the old version).

Ill go ahead and upgrade it right now, now that windows is out.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 02:47:03 PM
Its most likely due to node.biblepay.org (the main seed node being on the old version).

Ill go ahead and upgrade it right now, now that windows is out.
Thanks Rob.
BTW we are now top 10 Rosetta
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 02:48:45 PM
Its most likely due to node.biblepay.org (the main seed node being on the old version).

Ill go ahead and upgrade it right now, now that windows is out.
now I catched some node... we will see if the correct one :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 05, 2018, 02:53:37 PM
Windows 1.0.9.9 has been released, lets do some testing for a couple hours in prod also before I announce to the masses.

https://www.biblepay.org/#downloads

Ok got a Windows Wallet updated to 1.0.9.9 in Production,
I have 1 connection,
I didnt clean any folders or .dat files or reindex,

Should I move forward with updating Sanctuary?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 02:55:09 PM
now I catched some node... we will see if the correct one :D
so... i got synced to block 33152, but all my BBPs are gone.. my ballance is 0
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 02:55:15 PM
https://www.biblepay.org/#downloads

Ok got a Windows Wallet updated to 1.0.9.9 in Production,
I have 1 connection, I didnt clean any folders or .dat files,

Should I move forward with updating Sanctuary?

Mine kept crashing. Starting from scratch.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 02:58:39 PM
I updated two prod wallets. Both seem fine with 1 connection at the moment:

Code: [Select]
21:58:12

getblockhash 33152


21:58:12

0b6062f664d324c169c77439b85bd0b1a20077f3f1739d9deaa9713eca72c7d1
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 05, 2018, 03:00:40 PM
I have same blockhash as Jaapgvk

So we are hardforking the chain right now?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 03:02:35 PM
me too on win version
on linux I've made clean install and I'm on the same block 33152, but with 0 ballance... same wallet like on win...

Good question Togo.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 03:08:38 PM
Wait, the prod wallet that is on version 1.0.9.8. is two blocks ahead at the moment. So maybe our 1.0.9.9. blockchain has stalled?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 03:09:23 PM
OK. I upgraded in prod (on linux) to 1099. I am synched and all my BBP are there!
My wallet is unlocked and I have enough stake in there with a 50% stake percentage in config.

Just wanted to show you my outputs

"getinfo"
Code: [Select]
"version": 1000909,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.0.9.9",
  "balance": 110009.05571073,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33152,
  "timeoffset": 0,
  "connections": 1,
  "proxy": "",
  "difficulty": 1982.185198022292,
  "testnet": false,
  "keypoololdest": 1507790364,
  "keypoolsize": 1006,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""

"getmininginfo"
Code: [Select]
"blocks": 33152,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 19821.85198022292,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 126738296153.7337,
  "hashps": 17.58459997091422,
  "minerstarttime": "03-05-2018 20:27:46",
  "hashcounter": 41474,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
[b]  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; ",[/b]
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 73,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false

exec getboincinfo
Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422301,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 28509.17,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
[b]  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,[/b]
  "Total_RAC": 28509.17,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0


So I guess the failed to sign CPID will sort itself out in some number of blocks?

I am not sure if in prod I should have taskweight and uxto both =0 still?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 03:14:49 PM
So different chains..
1098:
Block #33152: 4dc6548b6f95b1df673ed01adb54d0f43fd5cac2143f1f04f2758c0773430ac0

1099:
Block #33152: 0b6062f664d324c169c77439b85bd0b1a20077f3f1739d9deaa9713eca72c7d1
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 03:18:26 PM


So I guess the failed to sign CPID will sort itself out in some number of blocks?

I am not sure if in prod I should have taskweight and uxto both =0 still?

OK my wallet just did a transaction, sent some tiny amount of BBP to itself.

Now the failed to sign cpid is fixed.
Now my taskweight =100
Now I wait for my uxto!

(edit: transaction was automatic, not by me)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 03:28:48 PM
OK my wallet just did a transaction, sent some tiny amount of BBP to itself.

Now the failed to sign cpid is fixed.
Now my taskweight =100
Now I wait for my uxto!

(edit: transaction was automatic, not by me)

Are you on the same chain as the 1.0.9.8. wallets? And if so, could we have your ip-adres so we can connect to your node?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 03:30:54 PM
Are you on the same chain as the 1.0.9.8. wallets? And if so, could we have your ip-adres so we can connect to your node?
How do I check which chain I am on? How can I find IP in BBP?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 03:33:51 PM
How do I check which chain I am on? How can I find IP in BBP?

You can do a 'getblockhash 33152'

If you get this hash, you're in the same wrecked boat as us:
0b6062f664d324c169c77439b85bd0b1a20077f3f1739d9deaa9713eca72c7d1

You can find your ip if you google 'what's my ip' for instance :) But maybe it's not needed if you're on the same chain as us...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 03:35:38 PM
You can do a 'getblockhash 33152'

If you get this hash, you're in the same wrecked boat as us:
0b6062f664d324c169c77439b85bd0b1a20077f3f1739d9deaa9713eca72c7d1

You can find your ip if you google 'what's my ip' for instance :) But maybe it's not needed if you're on the same chain as us...

getblockhash 33152
0b6062f664d324c169c77439b85bd0b1a20077f3f1739d9deaa9713eca72c7d1

Not sure I want to share IP right now :)

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 03:39:44 PM
so... i got synced to block 33152, but all my BBPs are gone.. my ballance is 0

Wait, Togo we are not hard forking yet due to the cutover rules - thats going in at block 33440, but I do believe our chains are forking due to network segmentation.
We have one chain (of the existing current prod users who didnt upgrade + the botnet) and then we have the new chain (us).

Orbis, you should not be losing BBP.  Did you get it back after you synced?  The only way to lose BBP is if you *mined* on a fork.  You should have the balance you had before the cutover.


Hey guys, I found a relatively minor bug in 1099, so I need to re-build windows with v 1101 (1100 is not possible, due to the zeroes) anyway, the bug only affects people with lots of sanctuary funds- it turns out, the PODC Update is "trying" to calculate its available amount using the unlocked calculation (I had fixed this in a prior version, but this morning when we moved to GetBalance due to the complaints - it reverted this.) So basically the workaround is if you are on 1099, you can set a low polpercentage, and the system will work temporarily, but tonight please focus on upgrading prod to 1101 when we all upgrade.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 03:40:59 PM
You can do a 'getblockhash 33152'

If you get this hash, you're in the same wrecked boat as us:
0b6062f664d324c169c77439b85bd0b1a20077f3f1739d9deaa9713eca72c7d1

You can find your ip if you google 'what's my ip' for instance :) But maybe it's not needed if you're on the same chain as us...

Why do you say wrecked?  The new chain is *the* chain - the 1089 chain is the one that is sinking with the titanic....


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 03:43:45 PM
THANK YOU ALL FOR TESTING PODC

WE ARE MAKING A DIFFERENCE IN THE WORLD, we are creating a Sanctuary Economy for the benefit of the Orphans!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 03:44:26 PM
THANK YOU ALL FOR TESTING PODC

WE ARE MAKING A DIFFERENCE IN THE WORLD, we are creating a Sanctuary Economy for the benefit of the Orphans!


What's going on, is it the end?  ;D ;D ;D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 03:45:18 PM
Orbis, you should not be losing BBP.  Did you get it back after you synced?  The only way to lose BBP is if you *mined* on a fork.  You should have the balance you had before the cutover.
I know and I hope so :)
On linux I've made clean install and after sync to block 33152 is my balance still 0.
On windows I didn't made clean install and my balance is fine... But I don't have a balls to make clean install on win to :D
I have 2 peers on win wallet.
Let us know when 1101 will be on win :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 03:47:34 PM
I just wanted to make one point.
We are currently top 10 Rosetta, we will soon be 2nd behind Gridcoin.

If, as we expect, some people will switch to us from Gridcoin (due to better potential returns) this is really good for the coin.
It means our personal PoDC reward goes down as we share the pie with more people, but it also means that there will be more people buying BBP on exchanges due to the uxto requirement. This is really good for BBP and we could see some consistent price growth soon (which is really needed for our budget, looks like all columns will be close to maxed out this month).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 03:50:29 PM
Why do you say wrecked?  The new chain is *the* chain - the 1089 chain is the one that is sinking with the titanic....

Oh, sorry  :o I just thought something went wrong because the networks split. I didn't know it was intentional.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 03:54:00 PM
Wait, Togo we are not hard forking yet due to the cutover rules - thats going in at block 33440, but I do believe our chains are forking due to network segmentation.
We have one chain (of the existing current prod users who didnt upgrade + the botnet) and then we have the new chain (us).

Orbis, you should not be losing BBP.  Did you get it back after you synced?  The only way to lose BBP is if you *mined* on a fork.  You should have the balance you had before the cutover.


Hey guys, I found a relatively minor bug in 1099, so I need to re-build windows with v 1101 (1100 is not possible, due to the zeroes) anyway, the bug only affects people with lots of sanctuary funds- it turns out, the PODC Update is "trying" to calculate its available amount using the unlocked calculation (I had fixed this in a prior version, but this morning when we moved to GetBalance due to the complaints - it reverted this.) So basically the workaround is if you are on 1099, you can set a low polpercentage, and the system will work temporarily, but tonight please focus on upgrading prod to 1101 when we all upgrade.

"but tonight please focus on upgrading prod to 1101 when we all upgrade."

I will upgrade my PoDC wallet now.

Should we be upgrading our prod sanctuaries and controller wallets now also, or just wait?

Thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 03:59:34 PM
Are we all still on block 33152?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 04:01:32 PM
So,
linux 1101, clean install, synced to block 33152 and my balance is still 0 :(

EDIT: restored wallet from backup, clean istall again and balance is back :) thanks God, because those are all of my BBP. I play all in :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 04:02:42 PM
Oh, sorry  :o I just thought something went wrong because the networks split. I didn't know it was intentional.
Lol, no problem, no I didnt expect it actually, because we had some rogue actors over the years who shuttled blocks back and forth protocol versions in the past, eliminating the smaller chain.  This behavior is actually normal, the two shouldnt be communicating.  Lets see where this goes.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 04:03:23 PM
So,
linux 1101, clean install, synced to block 33152 and my balance is still 0 :(
You must have changed wallets? Can you go back to your original wallet?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 04:03:39 PM
Are we all still on block 33152?

Yup. My speculation is that we have a 'bitcoin cash' situation here. When they forked, they still had to mine the original difficulty, but with way less hashpower, so it took them a long time before they hit their first block.

I don't know if that's the case here. Just speculating. If it's true, luckily we have a difficulty adjustment each block (right?).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 04:03:42 PM
So,
linux 1101, clean install, synced to block 33152 and my balance is still 0 :(

Did you restore your wallet file?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 04:13:16 PM
Weve got a wild situation forming here, take a look at the legacy chain difficulty :
running this from the *new* wallet:

exec podcdifficulty 33120

Diff is about 24000....  So that explains why we are having issues solving block 33153.
So what happens is the block becomes 90% easier after 30 minutes - meaning that a 24000 diff is like a 2400 diff!  Thats crazy high for us little fish in this new pond.  We are going to have to recommend setgenerate 10 - we need to try to brute force 33153 together....

I just enabled 1 miner.

EDIT:  Yes Jaap just read your comment, exactly, but we have evaded this situation because of our late block rule above.  But whats strange is this 24000 diff is Way higher than normal!  We pissed someone off right before the fork started.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 04:15:32 PM
You must have changed wallets? Can you go back to your original wallet?
restored wallet from backup, clean istall again and balance is back :) thanks God, because those are all of my BBP. I play all in :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 04:16:42 PM
restored wallet from backup, clean istall again and balance is back :) thanks God, because those are all of my BBP. I play all in :D
Good to hear!  Yes we should all keep an offsite backup of wallet.dat, just in case this happens.

Ive had many fried hard drives.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 04:20:24 PM
I think I'm going to use my Sanctuary wallet as my PODC wallet, that way I don't have to keep the controller on at home.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 04:20:31 PM
What's going on, is it the end?  ;D ;D ;D

No, but just in case this turns into a Prod drama, I wanted to thank everyone!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 04:24:16 PM
Weve got a wild situation forming here, take a look at the legacy chain difficulty :
running this from the *new* wallet:

exec podcdifficulty 33120

Diff is about 24000....  So that explains why we are having issues solving block 33153.
So what happens is the block becomes 90% easier after 30 minutes - meaning that a 24000 diff is like a 2400 diff!  Thats crazy high for us little fish in this new pond.  We are going to have to recommend setgenerate 10 - we need to try to brute force 33153 together....

I just enabled 1 miner.

EDIT:  Yes Jaap just read your comment, exactly, but we have evaded this situation because of our late block rule above.  But whats strange is this 24000 diff is Way higher than normal!  We pissed someone off right before the fork started.

I'm on block 33162 now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 04:26:14 PM
I'm on block 33162 now.
same here
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 04:27:31 PM
same here

Me too  ;D That was easier than expected, haha!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 04:35:16 PM
Me too  ;D That was easier than expected, haha!

Were not out of the woods yet, because DGW can take up to 4 blocks to recalibrate the diff.  Looks like the next block is 2400~ diff.
It will probably take the full hour to solve it + 1 + 2 etc.  I see part of the problem:  This exec podcdifficulty command's scale is *10, so our diff is really 2400, not 24000.  Whew. Good to know.

Ill fix this, plus the crash when you do a diff+1, plus the getmininginfo diff should be visible, but these are all cosmetic things they can wait until windows 1101 is released (should be within an hour).  Ill release 1101 then we can start upgrading some prod nodes, and then add these 3 cosmetic changes in.

So, it might take us up to 3 more hours to solve blocks at a normal rate.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 04:47:43 PM

Ill fix this, plus the crash when you do a diff+1


I just tried to set 'setgenerate 10' (to help mining blocks faster), but the wallet crashed immediately (1.0.9.9). I tried it twice with the same result.

(https://preview.ibb.co/n9XDYS/setgenerate.png)

Code: [Select]
2018-03-05 22:44:51  Starting Thread #0.000000 with Bible #0.000000      2018-03-05 22:44:51 BibleMiner -- started thread 0.000000
2018-03-05 22:44:51  Starting Thread #1.000000 with Bible #0.000000      2018-03-05 22:44:51 BibleMiner -- started thread 1.000000
2018-03-05 22:44:51  ** Started 2.000000 BibleMiner threads. **
2018-03-05 22:45:03  Starting Thread #0.000000 with Bible #0.000000      2018-03-05 22:45:03 BibleMiner -- started thread 0.000000
2018-03-05 22:45:03  Starting Thread #1.000000 with Bible #0.000000      BibleMiner -- started thread 1.000000
2018-03-05 22:45:03
BiblepayMiner -- terminated
2018-03-05 22:45:03  Starting Thread #2.000000 with Bible #0.000000      BibleMiner -- started thread 2.000000
2018-03-05 22:45:03 keypool added key 3020, size=1001
2018-03-05 22:45:03 init message: Loading wallet... (301.70 %)
2018-03-05 22:45:03  Starting Thread #3.000000 with Bible #0.000000      2018-03-05 22:45:03 BibleMiner -- started thread 3.000000
2018-03-05 22:45:03  Starting Thread #4.000000 with Bible #0.000000      BibleMiner -- started thread 4.000000
2018-03-05 22:45:03  Starting Thread #5.000000 with Bible #0.000000      BibleMiner -- started thread 5.000000
2018-03-05 22:45:04  Starting Thread #6.000000 with Bible #0.000000      BibleMiner -- started thread 6.000000
2018-03-05 22:45:04
BiblepayMiner -- terminated
2018-03-05 22:45:04  Starting Thread #7.000000 with Bible #0.000000      2018-03-05 22:45:04 BibleMiner -- started thread 7.000000
2018-03-05 22:45:04  Starting Thread #8.000000 with Bible #0.000000      2018-03-05 22:45:04 BibleMiner -- started thread 8.000000
2018-03-05 22:45:04  Starting Thread #9.000000 with Bible #0.000000      BibleMiner -- started thread 9.000000
2018-03-05 22:45:04  ** Started 10.000000 BibleMiner threads. **
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 05, 2018, 05:44:31 PM
Rob when will be WIN version available?
I want to go sleep :D I wake up in 5 hours :)
But I wanna try it ;)

EDIT: too late. Good night ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 06:22:43 PM
We found a block :)
33163 in prod now :)

Edit: Wow now we are moving! Block 33174
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 06:53:51 PM
I just tried to set 'setgenerate 10' (to help mining blocks faster), but the wallet crashed immediately (1.0.9.9). I tried it twice with the same result.


Code: [Select]
2018-03-05 22:44:51  Starting Thread #0.000000 with Bible #0.000000      2018-03-05 22:44:51 BibleMiner -- started thread 0.000000
2018-03-05 22:44:51  Starting Thread #1.000000 with Bible #0.000000      2018-03-05 22:44:51 BibleMiner -- started thread 1.000000
2018-03-05 22:44:51  ** Started 2.000000 BibleMiner threads. **
2018-03-05 22:45:03  Starting Thread #0.000000 with Bible #0.000000      2018-03-05 22:45:03 BibleMiner -- started thread 0.000000
2018-03-05 22:45:03  Starting Thread #1.000000 with Bible #0.000000      BibleMiner -- started thread 1.000000
2018-03-05 22:45:03
BiblepayMiner -- terminated
2018-03-05 22:45:03  Starting Thread #2.000000 with Bible #0.000000      BibleMiner -- started thread 2.000000
2018-03-05 22:45:03 keypool added key 3020, size=1001
2018-03-05 22:45:03 init message: Loading wallet... (301.70 %)
2018-03-05 22:45:03  Starting Thread #3.000000 with Bible #0.000000      2018-03-05 22:45:03 BibleMiner -- started thread 3.000000
2018-03-05 22:45:03  Starting Thread #4.000000 with Bible #0.000000      BibleMiner -- started thread 4.000000
2018-03-05 22:45:03  Starting Thread #5.000000 with Bible #0.000000      BibleMiner -- started thread 5.000000
2018-03-05 22:45:04  Starting Thread #6.000000 with Bible #0.000000      BibleMiner -- started thread 6.000000
2018-03-05 22:45:04
BiblepayMiner -- terminated
2018-03-05 22:45:04  Starting Thread #7.000000 with Bible #0.000000      2018-03-05 22:45:04 BibleMiner -- started thread 7.000000
2018-03-05 22:45:04  Starting Thread #8.000000 with Bible #0.000000      2018-03-05 22:45:04 BibleMiner -- started thread 8.000000
2018-03-05 22:45:04  Starting Thread #9.000000 with Bible #0.000000      BibleMiner -- started thread 9.000000
2018-03-05 22:45:04  ** Started 10.000000 BibleMiner threads. **

Hi Jaap,

I was able to reproduce this once.  It seems like if you let the wallet sit for a while on one thread, then go up to 5-10 threads it wont crash.  This might take me a few days to find the root cause (it might be that it cant sign the CPID also).  In the mean time lets either try waiting longer before raising it, or just running one thread.

Looks like some 1087 blocks are bleeding over to our chain, so we are basically a hybrid chain now.


1.1.0.1 is now out there for windows.




Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 06:55:15 PM
Had a possible error. In the console I typed

"getdifficulty"

And the wallet crashed.

Code: [Select]
[1]+  Segmentation fault      (core dumped) ./biblepay/src/qt/biblepay-qt

Great, yes I see the reason for this, fixing it now for 1102. 

This should only happen if the wallet is not synced yet or if you type 'exec podcdifficulty height' where height > bestblock_height.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 05, 2018, 06:59:18 PM
Had a possible error. In the console I typed

"getdifficulty"

And the wallet crashed.

Code: [Select]
[1]+  Segmentation fault      (core dumped) ./biblepay/src/qt/biblepay-qt

Tried it, and it's the same here.

It was a synced wallet btw.

Well, I'm off to bed. It's 2 A.M. here... Hope we can sort it all out in the end.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 07:03:14 PM
Is there a version we have to upgrade to tonight?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 07:15:04 PM
Is there a version we have to upgrade to tonight?
Let me check into this getdifficulty thing, if its not a showstopper and we get it fixed on the linux side, then maybe, as it sure would be nice to get a cross section of sancs upgraded then we can try the exec testvote in prod, hang on let me do some testing.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 07:22:31 PM
Let me check into this getdifficulty thing, if its not a showstopper and we get it fixed on the linux side, then maybe, as it sure would be nice to get a cross section of sancs upgraded then we can try the exec testvote in prod, hang on let me do some testing.

To get around getdifficulty, type either getmininginfo, or exec podcdifficulty height.

Fixing now - found it.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 07:36:18 PM
Hi Jaap,

I was able to reproduce this once.  It seems like if you let the wallet sit for a while on one thread, then go up to 5-10 threads it wont crash.  This might take me a few days to find the root cause (it might be that it cant sign the CPID also).  In the mean time lets either try waiting longer before raising it, or just running one thread.

Looks like some 1087 blocks are bleeding over to our chain, so we are basically a hybrid chain now.


1.1.0.1 is now out there for windows.

Ok, I believe this is fixed in 1102 and the getdifficulty is fixed.

Lets just wait a little longer to ensure prod has a quality product.

Let me start compiling 1102 and let us test on windows again, and we can release to prod tomorrow after we re-test.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 08:54:53 PM
1.1.0.2 for Linux is out there.

Windows is still compiling.

- Show correct error in getmininginfo
- Prevent crash during miner start
- Prevent crash during getdifficulty
- Prevent crash during exec podcdifficulty

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 09:17:47 PM
1.1.0.2 for Linux is out there.

Windows is still compiling.

- Show correct error in getmininginfo
- Prevent crash during miner start
- Prevent crash during getdifficulty
- Prevent crash during exec podcdifficulty

Tested on linux in prod.

No crashes! 


Nice one!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 05, 2018, 09:18:17 PM
1.1.0.2 for Linux is out there.

Windows is still compiling.

- Show correct error in getmininginfo
- Prevent crash during miner start
- Prevent crash during getdifficulty
- Prevent crash during exec podcdifficulty

Is it also protocol version 70717?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 05, 2018, 09:48:31 PM
Is it also protocol version 70717?

Yes, because its not really a mandatory, its technically a leisure.

This windows is still compiling, lets pick this up in the morning.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 05, 2018, 11:28:06 PM
Hi all,

I see in the pool that Proof-of-BibleHash block mining still gets full block rewards - when will we cut to the new 10% for proof-of-loyalty/proof-of-work?
Or I have misundestood this?

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 05, 2018, 11:47:39 PM
Hi all,

I see in the pool that Proof-of-BibleHash block mining still gets full block rewards - when will we cut to the new 10% for proof-of-loyalty/proof-of-work?
Or I have misundestood this?

Best regards,
Simon

Hi Simon, still a few days until we switch over to PoDC. Block 33620 I think

EDIT: Block where PoDC starts is 33,440.
(33,620 is first superblock payment block)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 01:46:26 AM
After waking up, I've looked up to my wallet (1101) give me that I have task 100 but UTXO 0.
So I've tried podcupdate and again it was false :( (insufficient balance)
Wallet unlocked and BBP on correct (same) addres associated with CPID.
Is it counting "age" of coins from 0 since "new" chain?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 06, 2018, 01:59:05 AM
After waking up, I've looked up to my wallet (1101) give me that I have task 100 but UTXO 0.
So I've tried podcupdate and again it was false :( (insufficient balance)
Wallet unlocked and BBP on correct (same) addres associated with CPID.
Is it counting "age" of coins from 0 since "new" chain?

Is your stakebalance still '0'? ('exec stakebalance')?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 06, 2018, 02:01:58 AM
Also, has anyone received any new Android tasks in Boinc? Not me...

Code: [Select]
rah_make_work_android bwsrv1 Actief
rah_assimilator_android (rosetta_android) bwsrv1 Actief
rah_validator_android (rosetta_android) bwsrv1 Actief

Their Android related servers seem online, but I don't know if they are generating new tasks...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 02:36:44 AM
I updated 1.1.0.1 in Windows (production), unlocked my wallet, and registered my Rosetta user, and I get this


Quote
getmininginfo

{
  "blocks": 33220,
  "currentblocksize": 2646,
  "currentblocktx": 2,
  "difficulty_podc": 0,
  "difficulty_pow": 14054.13127284258,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 10,
  "networkhashps": 136662306069.4784,
  "hashps": 0.2939447383891828,
  "minerstarttime": "03-06-2018 08:05:18",
  "hashcounter": 4,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Failed to sign CPID signature (unlock wallet)?; Failed to sign CPID signature (unlock wallet)?; Failed to sign CPID signature (unlock wallet)?; ",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 4,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
}

and


Quote
exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422312,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Chain seems to be ok and sync.

Is this correct?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 06, 2018, 02:49:23 AM
I updated 1.1.0.1 in Windows (production), unlocked my wallet, and registered my Rosetta user, and I get this


and


Chain seems to be ok and sync.

Is this correct?

When you registered your Rosetta account, was there a window welcoming you to the cancer research? And was there an outgoing transaction of (I think) about 1 BBP?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 06, 2018, 03:38:58 AM
I have been upgraded for 6 hours or so.

So far:

Code: [Select]
  "Command": "stakebalance",
  "StakeBalance": 0

(I have a decent balance in my wallet, same address as CPID)

exec getboincinfo:
Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422313,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 31221.99,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 31221.99,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0

So no taskweight or UTXO.

Maybe I just need to wait longer
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 06, 2018, 04:03:45 AM
Just an observation, not sure if relevant.
I have two receiving addresses in my PoDC wallet, A1, A2.

When I linked with Rosetta I only had one address, my CPID was linked with A1.
A1 contains my stake.

Somehow I managed by accident to create a new address, A2.

When I type

Code: [Select]
getaccountaddress ""
I get address A2 (the new default).

Rob, is this an issue or am I overthinking? Possibly the reason why my "stakebalance" is still 0?

Thanks
Luke
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 04:27:18 AM
When you registered your Rosetta account, was there a window welcoming you to the cancer research? And was there an outgoing transaction of (I think) about 1 BBP?

Yes to both questions.

EDIT: I see we are not mining blocks so this might be the cause, as long as the 1BBP transaction is not confirmed.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 06, 2018, 05:47:34 AM
This is what I'm getting

get boincinfo
Method not found (code -32601)

Still unconfirmed burn transaction of 1 bbp
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 06, 2018, 05:51:46 AM
This is what I'm getting

get boincinfo
Method not found (code -32601)

Still unconfirmed burn transaction of 1 bbp

The correct command is 'exec getboincinfo'.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 06:55:28 AM
Btw all, in PODC, you have to have a CPID in order to heat mine.  When the miner reports the error "unable to sign", our current network allows the mining to occur anyway - and accepts the mined block up to the cutover block (33440) and ignores the error.  After 33441, there must be a signed cpid in every block (or the block is rejected).

Except under this condition: If the block takes longer than 16 minutes to solve, we do allow any solution with a valid low hash (IE unsigned by a cpid).

So if you are receiving the Unable to sign error in the miner, that means after 33441, your miner would have a hard time actually "mining" since it has no CPID associated with it.

Btw, the next version has a much more precise error in it (1102b) - Im compiling it now.  It will show the reason it cant sign.

Orbis, if you are using linux please get the latest and see if that gives you a more precise reason you have utxo weight = 0.  Also, 'exec stakebalance' should actually show your true balance now, here is the new formula:  Unlocked Coins with over 5 confirmations.  Then it uses that * PolPercentage to create the Podcupdate.  So podcupdate will fail if it was done within 6 past recent blocks (unless you have a high balance).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 07:05:56 AM
I have been upgraded for 6 hours or so.

So far:

Code: [Select]
  "Command": "stakebalance",
  "StakeBalance": 0

(I have a decent balance in my wallet, same address as CPID)

exec getboincinfo:
Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422313,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 31221.99,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 31221.99,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0

So no taskweight or UTXO.

Maybe I just need to wait longer
Good morning Luke,
If you are on 1102b, what happens when you 'exec podcupdate', does it end in true?

I see your tasks in my sanc buffer, but I dont see your UTXO weight.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 07:31:15 AM
I still don't see my CPID. My prod client says we are in 33235. Am I in the right chain? Do I have to upgrade/clean files? Thank you
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 07:32:51 AM
I still don't see my CPID. My prod client says we are in 33235. Am I in the right chain? Do I have to upgrade/clean files? Thank you
Yes, im on 33235 also.
Whats your exec getboincinfo output?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 07:50:14 AM
Yes, im on 33235 also.
Whats your exec getboincinfo output?

The same I posted some hours before



Quote
exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422317,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

The funny thing is that the CPID-Age (hours) is correct, but CPID itself is blank. Also I saw the 1BBP charge but as we have been in current block since then, transaction (e6e5d60e2c4d85d1e6f7ccec7dbae61ccacda8f9947b2d6a8277de2260c07206-000) is not confirmed yet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 08:11:35 AM
podcupdate gave true last night but my CPI is still not associated. I moved the cpid from my controller wallet to the sanctuary. Updating to the latest version now.

By the way, make -j4 doesn't seem to be doing anything, it seems to still use only 1 core.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 08:41:40 AM
podcupdate gave true last night but my CPI is still not associated. I moved the cpid from my controller wallet to the sanctuary. Updating to the latest version now.

By the way, make -j4 doesn't seem to be doing anything, it seems to still use only 1 core.

I tried to compile once in a 16 vCPU with -j4 and -j8 and gcc crashed badly. -j2 worked fine though.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 06, 2018, 08:42:01 AM
Hi,

I am on 1.1.0.1 (Win) and production.
I think the problem that users above have is in not confirmed transactions - there have to be 6 blocks confirmed for CPID to show, but I think none is confirmed.
I think this beacause my pool withdraw (8 hours ago) is still unconfirmed.

Otherwise my CPID is fine, also getboincinfo - I have associated it yesterday evening.
I am on block 33235.

EDIT: Now that I upgraded to 1.1.0.2 The confiramtions started (with block 33236). I have 1 of 6 confirmations on pool withdraw now.

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 08:47:20 AM
The same I posted some hours before



The funny thing is that the CPID-Age (hours) is correct, but CPID itself is blank. Also I saw the 1BBP charge but as we have been in current block since then, transaction (e6e5d60e2c4d85d1e6f7ccec7dbae61ccacda8f9947b2d6a8277de2260c07206-000) is not confirmed yet.

In your case it looks like the problem is the CPID is still not associated.   The e6e tx is not being accepted by the current state of the network.

Try re-associating your cpid again, until the tx is confirmed.

Once we are live in prod with a supermajority, I anticipate this problem diminishing.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 09:08:48 AM
1.1.0.2b for windows has been released.

Alright, I suppose this marks the milestone where I believe the bugs we found in testnet have been resolved.

Im going to go ahead and attempt an upgrade of a few of my prod sancs now (with 1102b) and also try the association in prod with my CPID, to see if we squashed all known bugs.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 09:13:25 AM
Rob, why does running the commands below cause my daemon to stop after a few seconds. It refuses to run continuously.

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

This happened to me yesterday and I had to start from scratch and it's doing it again today.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 09:35:50 AM
Rob, why does running the commands below cause my daemon to stop after a few seconds. It refuses to run continuously.

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

This happened to me yesterday and I had to start from scratch and it's doing it again today.

Running those would cause multiple problems - the database state would be corrupted in memory.
You would need to run those after you stop the node.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 09:40:21 AM
Running those would cause multiple problems - the database state would be corrupted in memory.
You would need to run those after you stop the node.

Right, I did run them after I stopped the daemon. Maybe it didn't stop? I will check next time before I remove.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 10:01:46 AM
Alright guys, I think we are starting to be pressured into a mandatory upgrade.

Lict has raised a very valid point in prod - since I upgraded node.biblepay.org and the pool server, now the pool is enforcing the 1102 chain, which is causing questions.

So I suppose we need to hurry up and test 1102 and make a decision for release candidate.

I just checked my ca89 cpid association in prod and it was successful and I have utxo weight.

Luke, do you have utxo weight now?

Are we experiencing any other problems?

Im going to upgrade a few sancs now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 10:20:01 AM
Alright guys, I think we are starting to be pressured into a mandatory upgrade.

Lict has raised a very valid point in prod - since I upgraded node.biblepay.org and the pool server, now the pool is enforcing the 1102 chain, which is causing questions.

So I suppose we need to hurry up and test 1102 and make a decision for release candidate.

I just checked my ca89 cpid association in prod and it was successful and I have utxo weight.

Luke, do you have utxo weight now?

Are we experiencing any other problems?

Im going to upgrade a few sancs now.

I have 1.1.0.2 and the transactions I made a few hours ago show as "unconfirmed" (one of them is the 1BBP).

At this point I don't know which chain I am on. Is blockexplorer in the new one or the old one?

I already upgraded the MN without apparent issues though.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 10:26:19 AM
I have 1.1.0.2 and the transactions I made a few hours ago show as "unconfirmed" (one of them is the 1BBP).

At this point I don't know which chain I am on. Is blockexplorer in the new one or the old one?

I already upgraded the MN without apparent issues though.

I think Togo is the only block explorer left as I think Alex went on vacation, uh I dont know if Togo upgraded his bx.

In my 1102 node, Lict pointed out our chain just switched over in 1102 to the higher diff chain, and I just confirmed this - so here is what Im getting now:


10:24:18

getblockhash 33268


10:24:18

550699009b14fe33f79be164dbba0ac063e4423d7a0fa75f119738704c7388d1


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 10:27:21 AM
I have 1.1.0.2 and the transactions I made a few hours ago show as "unconfirmed" (one of them is the 1BBP).

At this point I don't know which chain I am on. Is blockexplorer in the new one or the old one?

I already upgraded the MN without apparent issues though.

On the unconfirmed, if you could double click it - if its an associate, please reassociate, if its a PODC update, just do a new one.

Those will probably stay unconfirmed forever - then later do a restart with -zapwallettxes

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 06, 2018, 10:32:00 AM
On the unconfirmed, if you could double click it - if its an associate, please reassociate, if its a PODC update, just do a new one.

Those will probably stay unconfirmed forever - then later do a restart with -zapwallettxes

Hi,

My unconfirmd transaction is withdraw from the pool:

Code: [Select]
Status: 0/unconfirmed
Date: 6.3.2018 06:17
From: unknown
To: B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m (own address)
Credit: 430.00000000 Biblepay
Net amount: +430.00000000 Biblepay


:
Transaction ID: 143ff5a08d229cffd2d881e9e9aee4bae20122a84fd8b1d0804306010028f0cf-000



Debug information

Credit: 430.00000000 Biblepay

Transaction:
CTransaction(hash=143ff5a08d, ver=1, vin.size=1, vout.size=2, nLockTime=33204)
    CTxIn(COutPoint(a0dadb18179ae1dd38345883c2712797929edb518493d021d1359c0a2db8c37f, 0), scriptSig=473044022019a008719811f0, nSequence=4294967294)
    CTxOut(nValue=430.00000000, scriptPubKey=76a9141dc8a8dbf8caca55dd871013)
    CTxOut(nValue=5543.49989254, scriptPubKey=76a9141b7d8578af86bb535bb70f36)

Inputs:
BNvQ5Txs1riZvuKA5W7prbtwx7PuSXXBwL Amount=5973.49993834 Biblepay IsMine=false IsWatchOnly=false


Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 06, 2018, 10:35:26 AM
I think Togo is the only block explorer left as I think Alex went on vacation, uh I dont know if Togo upgraded his bx.

Upgrading the Backup Explorer right now, should be ready soon
http://explorer.biblepay.org:3001/
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 11:01:38 AM
My PODC wallet is running in headless. Does the auto-unlock work like in the GUI? If not, what's the best way for UTXO?

getblockhash 33276
6c148975fdac517c89b9f1cf7447cd8ea32b5fce023ec46fc4e1729e700b5be2
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 11:20:10 AM
Hi,

My unconfirmd transaction is withdraw from the pool:

Code: [Select]
Status: 0/unconfirmed
Date: 6.3.2018 06:17
From: unknown
To: B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m (own address)
Credit: 430.00000000 Biblepay
Net amount: +430.00000000 Biblepay


:
Transaction ID: 143ff5a08d229cffd2d881e9e9aee4bae20122a84fd8b1d0804306010028f0cf-000



Debug information

Credit: 430.00000000 Biblepay

Transaction:
CTransaction(hash=143ff5a08d, ver=1, vin.size=1, vout.size=2, nLockTime=33204)
    CTxIn(COutPoint(a0dadb18179ae1dd38345883c2712797929edb518493d021d1359c0a2db8c37f, 0), scriptSig=473044022019a008719811f0, nSequence=4294967294)
    CTxOut(nValue=430.00000000, scriptPubKey=76a9141dc8a8dbf8caca55dd871013)
    CTxOut(nValue=5543.49989254, scriptPubKey=76a9141b7d8578af86bb535bb70f36)

Inputs:
BNvQ5Txs1riZvuKA5W7prbtwx7PuSXXBwL Amount=5973.49993834 Biblepay IsMine=false IsWatchOnly=false


Best regards,
Simon

This was paid in 1101, could you please resync, I see the tx on my sanctuary... Existing.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 11:21:24 AM
My PODC wallet is running in headless. Does the auto-unlock work like in the GUI? If not, what's the best way for UTXO?

getblockhash 33276
6c148975fdac517c89b9f1cf7447cd8ea32b5fce023ec46fc4e1729e700b5be2

I dont know yet, LOL no plan has been devised yet.  So ok lets think about that.
If we ask the user for a password when the headless boots, as long as that is not logged into the bash log it might be the way to go.

Does anyone know if passwords from user input go into the bash log?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 11:22:03 AM
On the unconfirmed, if you could double click it - if its an associate, please reassociate, if its a PODC update, just do a new one.

Those will probably stay unconfirmed forever - then later do a restart with -zapwallettxes

I did that, and the transactions dissappeared. But 5 minutes later they appeared again from nowhere and got a confirmation... interesting. No problem so far.

One of those was the 1BBP for CPID I sent 8 hours ago (42cad1f72d9b5578c6e67edd8fd2001d5312c930c5f5caa964e328b6b70dbbf1-000),

 I'll wait for 6 confirmations to see if CPID finally shows up.

EDIT: now I see the transactions as unconfirmed again... there must be a conflict somewhere
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 06, 2018, 11:25:44 AM
I've updated two sacs in prod some hours ago. One is on 1.1.0.1. and one is on 1.1.0.2.  Both have received payments according to the 'masternode winners' list. but I only got payment for one in my wallet.

Code: [Select]
  "33263": "B7aXGzeaSsmm2QPE2SzFpH52Xuzw3zhTfq:1, BGf3UZMRqhtvyHK6zusEjh63ssqaQ46EZh:1",

  "33267": "BPZ58mUyzL58sPt8MpLuZdSPmFmMNBeibJ:2, B7fSLq4euhkfzdQPh2KWb8bCUiuFQtJGiP:1",


I only received payment for the 'BPZ' one. That is probably related to the whole 'chain instability' thing, right?

I will check the updated chain-explorer later. Or could the payment have gone to the 'BGf' on instead of the 'B7a' one in block 33263?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 11:32:18 AM
That's weird, there was bbp in my podc wallet just 5 min ago that I sent an hour ago and now there is none. It was also getting confirmations and now it's back at zero.

5 minutes ago:
Code: [Select]

12:21:32

gettransaction ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5-000


12:21:32

{
  "amount": -2.00000000,
  "fee": -0.00006740,
  "confirmations": 1,
  "bcconfirmations": 1,
  "blockhash": "b51f188b002cd8a341c972b9b7196371ace1e2a1e414bfb0fdc905d92213a0ab",
  "blockindex": 53,
  "blocktime": 1520356616,
  "txid": "ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5",
  "walletconflicts": [
  ],
  "time": 1520355908,
  "timereceived": 1520355908,
  "bip125-replaceable": "no",
  "details": [
    {
      "account": "",
      "address": "BCY2vBWzUF5Sh5P5XKuFEEUjxjuNuNMnTo",
      "category": "send",
      "amount": -2.00000000,
      "label": "",
      "vout": 0,
      "fee": -0.00006740,
      "abandoned": false
    }
  ],
  "hex": "01000000015782a6bdadb25bfe9b4b51a0efb3456264a3758ebb0d5cef55f23f661d5981a4000000006b483045022100af348bc0154b4fdb7815f08a8c915ce24abb04ecac9607d9bad37d064108f33102202001b0a1c8a4c898d911373ab6596094077ee4d7712516e6f6df1f60c443efc10121033bada5903b17a23120779e463c40fed4978b22cd76dac2c7119f0f438dac8f5bfeffffff0200c2eb0b000000001976a91458b0d54c0f3efc0f4de46bf03f4e04b7f19be5ed88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3e02277407330000001976a914b0d165b3d2edf48887dfbe5d9a67fec1013334ae88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3efc810000"
}

Now:
Code: [Select]

12:33:26

gettransaction ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5-000


12:33:26

{
  "amount": -2.00000000,
  "fee": -0.00006740,
  "confirmations": 0,
  "bcconfirmations": 0,
  "trusted": true,
  "txid": "ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5",
  "walletconflicts": [
  ],
  "time": 1520355908,
  "timereceived": 1520355908,
  "bip125-replaceable": "no",
  "details": [
    {
      "account": "",
      "address": "BCY2vBWzUF5Sh5P5XKuFEEUjxjuNuNMnTo",
      "category": "send",
      "amount": -2.00000000,
      "label": "",
      "vout": 0,
      "fee": -0.00006740,
      "abandoned": false
    }
  ],
  "hex": "01000000015782a6bdadb25bfe9b4b51a0efb3456264a3758ebb0d5cef55f23f661d5981a4000000006b483045022100af348bc0154b4fdb7815f08a8c915ce24abb04ecac9607d9bad37d064108f33102202001b0a1c8a4c898d911373ab6596094077ee4d7712516e6f6df1f60c443efc10121033bada5903b17a23120779e463c40fed4978b22cd76dac2c7119f0f438dac8f5bfeffffff0200c2eb0b000000001976a91458b0d54c0f3efc0f4de46bf03f4e04b7f19be5ed88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3e02277407330000001976a914b0d165b3d2edf48887dfbe5d9a67fec1013334ae88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3efc810000"
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 11:34:43 AM
I've updated two sacs in prod some hours ago. One is on 1.1.0.1. and one is on 1.1.0.2.  Both have received payments according to the 'masternode winners' list. but I only got payment for one in my wallet.

Code: [Select]
  "33263": "B7aXGzeaSsmm2QPE2SzFpH52Xuzw3zhTfq:1, BGf3UZMRqhtvyHK6zusEjh63ssqaQ46EZh:1",

  "33267": "BPZ58mUyzL58sPt8MpLuZdSPmFmMNBeibJ:2, B7fSLq4euhkfzdQPh2KWb8bCUiuFQtJGiP:1",


I only received payment for the 'BPZ' one. That is probably related to the whole 'chain instability' thing, right?

I will check the updated chain-explorer later. Or could the payment have gone to the 'BGf' on instead of the 'B7a' one in block 33263?

Height 33267 has 8 votes for BPZ so that explains that.  Height 33263 has 8 votes for a different sanc: BK1 (in my chain at least) so he probably ganked that particular payment.  Yes, chain needs more stability, we probably reorganized back and forth - once we know our exec testvote works we can have more confidence in staying with this version and sailing through the mandatory block.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 11:36:07 AM
That's weird, there was bbp in my podc wallet just 5 min ago that I sent an hour ago and now there is none. It was also getting confirmations and now it's back at zero.

5 minutes ago:
Code: [Select]

12:21:32

gettransaction ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5-000


12:21:32

{
  "amount": -2.00000000,
  "fee": -0.00006740,
  "confirmations": 1,
  "bcconfirmations": 1,
  "blockhash": "b51f188b002cd8a341c972b9b7196371ace1e2a1e414bfb0fdc905d92213a0ab",
  "blockindex": 53,
  "blocktime": 1520356616,
  "txid": "ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5",
  "walletconflicts": [
  ],
  "time": 1520355908,
  "timereceived": 1520355908,
  "bip125-replaceable": "no",
  "details": [
    {
      "account": "",
      "address": "BCY2vBWzUF5Sh5P5XKuFEEUjxjuNuNMnTo",
      "category": "send",
      "amount": -2.00000000,
      "label": "",
      "vout": 0,
      "fee": -0.00006740,
      "abandoned": false
    }
  ],
  "hex": "01000000015782a6bdadb25bfe9b4b51a0efb3456264a3758ebb0d5cef55f23f661d5981a4000000006b483045022100af348bc0154b4fdb7815f08a8c915ce24abb04ecac9607d9bad37d064108f33102202001b0a1c8a4c898d911373ab6596094077ee4d7712516e6f6df1f60c443efc10121033bada5903b17a23120779e463c40fed4978b22cd76dac2c7119f0f438dac8f5bfeffffff0200c2eb0b000000001976a91458b0d54c0f3efc0f4de46bf03f4e04b7f19be5ed88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3e02277407330000001976a914b0d165b3d2edf48887dfbe5d9a67fec1013334ae88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3efc810000"
}

Now:
Code: [Select]

12:33:26

gettransaction ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5-000


12:33:26

{
  "amount": -2.00000000,
  "fee": -0.00006740,
  "confirmations": 0,
  "bcconfirmations": 0,
  "trusted": true,
  "txid": "ddbf8111d009b50640a88ca91ab7d3b7d6fdf241ae9c0005cc523672897ba7f5",
  "walletconflicts": [
  ],
  "time": 1520355908,
  "timereceived": 1520355908,
  "bip125-replaceable": "no",
  "details": [
    {
      "account": "",
      "address": "BCY2vBWzUF5Sh5P5XKuFEEUjxjuNuNMnTo",
      "category": "send",
      "amount": -2.00000000,
      "label": "",
      "vout": 0,
      "fee": -0.00006740,
      "abandoned": false
    }
  ],
  "hex": "01000000015782a6bdadb25bfe9b4b51a0efb3456264a3758ebb0d5cef55f23f661d5981a4000000006b483045022100af348bc0154b4fdb7815f08a8c915ce24abb04ecac9607d9bad37d064108f33102202001b0a1c8a4c898d911373ab6596094077ee4d7712516e6f6df1f60c443efc10121033bada5903b17a23120779e463c40fed4978b22cd76dac2c7119f0f438dac8f5bfeffffff0200c2eb0b000000001976a91458b0d54c0f3efc0f4de46bf03f4e04b7f19be5ed88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3e02277407330000001976a914b0d165b3d2edf48887dfbe5d9a67fec1013334ae88ac363c5041434b3e3c4d543e4d4553534147453c2f4d543e3c4d4b3e4f55545f54583c2f4d4b3e3c4d563e203c2f4d563e3c2f5041434b3efc810000"
}

I bet the transaction was reversed when the entire chain reorged.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 11:39:45 AM
Hi.
I've tried everything but my task and UTXO are still 0.
1102 on linux and on WIN...
once it works and stakebalance was right but PODCupdate give me just "" and I didn't found anything in debug about PODC :(
I've tried send 1BBp to other wallet and it was confirmed.. then just dissapeared and now are back in my old wallet (of course after rescan)
It looks really strange.
Rob do you think it will be without problem if the wallet will be unlocked? Make new wallet and then send there 50k BBP?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 11:47:38 AM
I dont know yet, LOL no plan has been devised yet.  So ok lets think about that.
If we ask the user for a password when the headless boots, as long as that is not logged into the bash log it might be the way to go.

Does anyone know if passwords from user input go into the bash log?

It is, I just checked. But if you delete the bash history afterwards it should be ok.

https://askubuntu.com/questions/297053/where-are-all-ubuntu-logs-terminal-history-stored

I don't see how it would be less secure though since I have to unlock it anyways manually and it will be in the bash history.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 11:52:24 AM
I bet the transaction was reversed when the entire chain reorged.

Does that mean I need to re-send it?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 06, 2018, 11:58:19 AM
Backup Block Explorer updated to v1.1.0.2c
http://explorer.biblepay.org:3001/
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 06, 2018, 12:01:58 PM
Backup Block Explorer updated to v1.1.0.2c
http://explorer.biblepay.org:3001/

I see three blocks numbered 33281 with their respective different hashes (?!)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 12:10:50 PM
I see three blocks numbered 33281 with their respective different hashes (?!)
yes there are more "double, triple" blocks... those are tx, not blocks...
But.. now I've created new clean wallet without pwd.
Trying send there some BBP, but the network refused it:
Code: [Select]
Status: 0/unconfirmed (InstantSend verification failed), broadcast through 16 nodes
Date: 06.03.2018 18:58
To: PODC BALzAYQ9hKU2CziuRxXWf4R3ceAbAkpBLP
Debit: -10.00000000 Biblepay
Transaction fee: -0.00100000 Biblepay
Net amount: -10.00100000 Biblepay

MESSAGE:
Transaction ID: 1990c18555577a7b72dab323fe5ed88cf803bcb4a06267e595b9882714bc73c4-000

EDIT: I've tried it many times, but with same result :( Everytime 0 out of 10 instantsend verification. Is Instantsend working? I've tried to send 50010BBP and same. I dont know what I'm doing wrong. I've increased tx fee too.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 12:58:55 PM
yes there are more "double, triple" blocks... those are tx, not blocks...
But.. now I've created new clean wallet without pwd.
Trying send there some BBP, but the network refused it:
Code: [Select]
Status: 0/unconfirmed (InstantSend verification failed), broadcast through 16 nodes
Date: 06.03.2018 18:58
To: PODC BALzAYQ9hKU2CziuRxXWf4R3ceAbAkpBLP
Debit: -10.00000000 Biblepay
Transaction fee: -0.00100000 Biblepay
Net amount: -10.00100000 Biblepay

MESSAGE:
Transaction ID: 1990c18555577a7b72dab323fe5ed88cf803bcb4a06267e595b9882714bc73c4-000
Please try sending it without instant send - I could see the sancs being in a sad state of affairs right now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 01:26:41 PM
Rob,
please can you give me some good node address?
Sending without instant send  but still not successful.

I have:
addnode=node.biblepay.org 
addnode=biblepay.inspect.network 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 01:34:32 PM
Rob,
please can you give me some good node address?
Sending without instant send  but still not successful.

I have:
addnode=node.biblepay.org 
addnode=biblepay.inspect.network

I haven't been able to transfer any funds either, 0 confirmations.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 01:46:20 PM
I haven't been able to transfer any funds either, 0 confirmations.
Srry, Havent even read all my emails yet this morning, this is crazy.

Let me give that a try in prod.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 01:52:27 PM
Looks like most of the problem is 87% of our network is still on 1.0.8.7 and down.
Thats heinously bad for PODC, since any tx larger than 1K is rejected (and a lot are bigger than that, when we have task count like Togo has).

So I think we are going to need to march forward and go with a mandatory and pray for the best, pray that we caught all the major bugs and that anything we find going forward is a leisure fix.

Ill get ready to announce a mandatory upgrade in prod.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 01:54:13 PM
Looks like most of the problem is 87% of our network is still on 1.0.8.7 and down.
Thats heinously bad for PODC, since any tx larger than 1K is rejected (and a lot are bigger than that, when we have task count like Togo has).

So I think we are going to need to march forward and go with a mandatory and pray for the best, pray that we caught all the major bugs and that anything we find going forward is a leisure fix.

Ill get ready to announce a mandatory upgrade in prod.

OK, so I'm assuming we just keep going on the current version or will there be a new version?

Right now my CPID is still attached to my old wallet even though I have already moved it.

Code: [Select]

14:55:18

exec getboincinfo


14:55:18

{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422323,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 10694.06,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 0,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 0,
  "Total_RAC": 10694.06,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

But on Rosetta it is showing my new wallet's address:
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1981209

Not sure if the network will automatically correct everything.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 01:59:54 PM
Looks like most of the problem is 87% of our network is still on 1.0.8.7 and down.
Thats heinously bad for PODC, since any tx larger than 1K is rejected (and a lot are bigger than that, when we have task count like Togo has).

So I think we are going to need to march forward and go with a mandatory and pray for the best, pray that we caught all the major bugs and that anything we find going forward is a leisure fix.

Ill get ready to announce a mandatory upgrade in prod.
I was trying to send 1BBP, 10BBP, but still without success.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 02:40:14 PM
I was trying to send 1BBP, 10BBP, but still without success.

I confirm, I cannot get my BBP to be inducted into a block either- it says confirmed by 8 peers but sits unconfirmed.

The good news is at block 33400, we require a signed CPID.  So otherwise I would offer to create a version with 1102+ blocks only, but its fruitless as for one, we have most of the network upgrading now, and 2) PODC basically does that during the hard fork.  I suppose we can let the botnet get the last 98 more blocks and with optimism, make it through 33400 and start confirming.

I obviously wish with upgrades over the next 2 hours we start confirming again.

I see there are 109 transactions in the memory pool - they are piling up.  The botnet miners are not accepting our transactions, but they have the supermajority hashpower.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 06, 2018, 02:44:37 PM
Hi Rob, all,

Sorry Rob I was asleep (we are in a funny time zone here at the bottom of the world!).

Firstly, this is an exciting day! Rob, you are doing a great job of what must be very busy, challenging, and potentially stressful. Thank you for your time and effort for what I think will be very very worthwhile.

Ok so this morning I checked and my TaskWeight =100 but my UTXO =0.
I have been in prod for with PoDC for the last two days over various versions and everntually taskweight always goes to 100, but I have never had UTXO anything other than 0, despite having plenty of funds in my address.

This morning I woke up, updated my PoDC wallet to the latest version, updated my sanctuary wallet (is now pre-enabled), and my controller wallet. So hopefully I am doing my share!

Ok, now that my PoDC wallet is updated, a few tests:

1.  exec getboincinfo

Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422324,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 34231.68,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 34231.68,
(I shortened the output here)

2. exec podcupdate

Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance too low."

3. exec stakebalance

Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 0



As noted above, my receiving address which is linked to my CPID is   "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",.
Just to prove it has funds:
http://explorer.biblepay.org:3001/address/BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq


So I am not sure what the problem is... I must admit to being a little nervous.

Some thoughts, Rob I would appreciate advice as you have time.

A) Perhaps I should re-associate my CPID? I associated it in prod around 3 or 4 wallet versions ago. But Have never had UTXO...
B) If I type getaccountaddress ""  I get

Code: [Select]
B9a1HK9QxmpFRvUffcN7FjXT3odPdFBBJa
Which is a different one from my CPID address. Is this an issue for my UTXO?

Thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 02:46:42 PM
I confirm, I cannot get my BBP to be inducted into a block either- it says confirmed by 8 peers but sits unconfirmed.

The good news is at block 33400, we require a signed CPID. 
Ok. So, if I have signed CPID, but task and UTXO are 0 it will be ok?

I see there are 109 transactions in the memory pool - they are piling up.  The botnet miners are not accepting our transactions, but they have the supermajority hashpower.
And what will be with those tx after block 33400? They would be accepted? Because I've tried to send something many times. I hope now, that those tx will be dissapeared :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 02:51:37 PM
Hi Rob, all,

Sorry Rob I was asleep (we are in a funny time zone here at the bottom of the world!).

Firstly, this is an exciting day! Rob, you are doing a great job of what must be very busy, challenging, and potentially stressful. Thank you for your time and effort for what I think will be very very worthwhile.

Ok so this morning I checked and my TaskWeight =100 but my UTXO =0.
I have been in prod for with PoDC for the last two days over various versions and everntually taskweight always goes to 100, but I have never had UTXO anything other than 0, despite having plenty of funds in my address.

This morning I woke up, updated my PoDC wallet to the latest version, updated my sanctuary wallet (is now pre-enabled), and my controller wallet. So hopefully I am doing my share!

Ok, now that my PoDC wallet is updated, a few tests:

1.  exec getboincinfo

Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422324,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 34231.68,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 34231.68,
(I shortened the output here)

2. exec podcupdate

Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance too low."

3. exec stakebalance

Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 0



As noted above, my receiving address which is linked to my CPID is   "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",.
Just to prove it has funds:
http://explorer.biblepay.org:3001/address/BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq


So I am not sure what the problem is... I must admit to being a little nervous.

Some thoughts, Rob I would appreciate advice as you have time.

A) Perhaps I should re-associate my CPID? I associated it in prod around 3 or 4 wallet versions ago. But Have never had UTXO...
B) If I type getaccountaddress ""  I get

Code: [Select]
B9a1HK9QxmpFRvUffcN7FjXT3odPdFBBJa
Which is a different one from my CPID address. Is this an issue for my UTXO?

Thanks :)

Thanks Luke, I appreciate it.

Jumping to the issue : exec podcupdate, with response: balance too low.
(Your right, the exec stakebalance is what podcupdate uses to make a utxo, so we need to get that > 0 first).
Could you please check the following, the stakebalance calculation is : Any unlocked coin with more than 5 confirmations.
Please go to coin control and loop through your Unlocked coin entries, there is a confirmations count on the right, see if you have any that are deeper than 5?  This will be interesting :)

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 02:52:14 PM
So I am not sure what the problem is... I must admit to being a little nervous.

Some thoughts, Rob I would appreciate advice as you have time.

A) Perhaps I should re-associate my CPID? I associated it in prod around 3 or 4 wallet versions ago. But Have never had UTXO...
B) If I type getaccountaddress ""  I get

Code: [Select]
B9a1HK9QxmpFRvUffcN7FjXT3odPdFBBJa
Which is a different one from my CPID address. Is this an issue for my UTXO?

Thanks :)
Hi, we are little bit stressed too :)
We have same problems like you. We're not able to send any tx, because the botnet with old wallets have supermajority and he didn't accept new wallet version.
So we've must wait till block 33400 and hoping in bright future :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 06, 2018, 03:01:38 PM
Thanks Luke, I appreciate it.

Jumping to the issue : exec podcupdate, with response: balance too low.
(Your right, the exec stakebalance is what podcupdate uses to make a utxo, so we need to get that > 0 first).
Could you please check the following, the stakebalance calculation is : Any unlocked coin with more than 5 confirmations.
Please go to coin control and loop through your Unlocked coin entries, there is a confirmations count on the right, see if you have any that are deeper than 5?  This will be interesting :)

Hi Rob,

I'm not sure how to do the coin control loop thing. But If I go to the transactions tab (Linux, qt mode) then I can see that my 110k transaction has >200 confirmations (image attached).

Since then the wallet has tried to send tiny payments to itself 3 times. All three of these have 0 confirmations. Again please see images attached.

Is that what you wanted to see? Otherwise could someone please help me to see how to do coin control and looping?

Thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 03:02:52 PM
Ok. So, if I have signed CPID, but task and UTXO are 0 it will be ok?
And what will be with those tx after block 33400? They would be accepted? Because I've tried to send something many times. I hope now, that those tx will be dissapeared :)
No problem on the double spend- the wallet will only spend your old UTXO once - because it originates in only one place - the source of the funds is in one block, one txid, one vout, and one position only.
So the *later* spend on the vout would stay conflicted and orphaned in your txlist until you reboot with -zapwallettxes

I was just thinking, we probably shot ourselves in the foot a little by forcing the mandatory version and not having a rule to reject blocks < 1100.  Its a little too late to talk about that, only 97 blocks to go now.

Anyway, I believe the problem is due to network segmentation, the botnets miners will not honor our transactions!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 03:11:52 PM
No problem on the double spend- the wallet will only spend your old UTXO once - because it originates in only one place - the source of the funds is in one block, one txid, one vout, and one position only.
So the *later* spend on the vout would stay conflicted and orphaned in your txlist until you reboot with -zapwallettxes

I was just thinking, we probably shot ourselves in the foot a little by forcing the mandatory version and not having a rule to reject blocks < 1100.  Its a little too late to talk about that, only 97 blocks to go now.

Anyway, I believe the problem is due to network segmentation, the botnets miners will not honor our transactions!

But I'm afraid of that after 33400 will my BBPs flows to other wallets and I won't be able to have UTXO 100 because of that :)
50 blocks later I was calm, but after 33400 won't be time to take my BBP back to be counted :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 03:17:00 PM
But I'm afraid of that after 33400 will my BBPs flows to other wallets and I won't be able to have UTXO 100 because of that :)
50 blocks later I was calm, but after 33400 won't be time to take my BBP back to be counted :)
Are you talking bout the .01 bbp tx fee, or the actual UTXO stake?

The UTXO stake is *to* you, so nothing to worry about, if its not included in a block, you can get it back, if it is included in a block you get it back.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 06, 2018, 03:27:09 PM
Hi Rob,

I'm not sure how to do the coin control loop thing. But If I go to the transactions tab (Linux, qt mode) then I can see that my 110k transaction has >200 confirmations (image attached).

Since then the wallet has tried to send tiny payments to itself 3 times. All three of these have 0 confirmations. Again please see images attached.

Is that what you wanted to see? Otherwise could someone please help me to see how to do coin control and looping?

Thanks :)

Ah ok, I went to the send tab and I think hat is the coin control.
Image attached.

Interestingly, in here the 100k received transaction is in small bits and all have 0 confirmations...
SO I just wait until after the switchover block?

Thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 03:32:23 PM
Is it possible to cancel a transaction since everything is unconfirmed?

Specifically this one:  ad03b3d4f0bcea7999ed6f20324dbb9f40528f03786493fafc3c79ef56cbe301-000
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 03:33:28 PM
Are you talking bout the .01 bbp tx fee, or the actual UTXO stake?

The UTXO stake is *to* you, so nothing to worry about, if its not included in a block, you can get it back, if it is included in a block you get it back.
I just talking about UTXO stake, because I was trying anything :)
One of that was that I created new wallet and tried to send there 50k to be my new PODC wallet. So it looks, that after 33400 all of my BBP just flow to "new" wallet and I wont be able to have UTXO 100 because my CPID associated wallet will be without BBP :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 03:34:21 PM
Is it possible to cancel a transaction since everything is unconfirmed?
Yes that is good question :) Or just delete mempool tx :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 03:41:24 PM
Yes that is good question :) Or just delete mempool tx :D

There is no way to delete a transaction once broadcasted.  All you can do is -zapwallettxes, reboot, and that will keep your client from rebroadcasting unconfirmed tx.

The reason why is we dont know how many nodes have it in the memory pool, and it could be included in a block at any time.


So on this issue guys, lets  just hope 1102 solves some blocks between now and t+94.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 03:51:20 PM
There is no way to delete a transaction once broadcasted.  All you can do is -zapwallettxes, reboot, and that will keep your client from rebroadcasting unconfirmed tx.
The reason why is we dont know how many nodes have it in the memory pool, and it could be included in a block at any time.
So on this issue guys, lets  just hope 1102 solves some blocks between now and t+94.
Ok.. so "clean" install is enough :)

I've made versionreport:
Code: [Select]
  "Version": "Popularity,Percent %",
  "1.0.8.1": "116; 56.58%",
  "1.0.8.6": "8; 3.90%",
  "1.0.8.7": "53; 25.85%",
  "1.0.8.9": "2; 0.98%",
  "1.0.9.1": "2; 0.98%",
  "1.0.9.5": "1; 0.49%",
  "1.0.9.7": "22; 10.73%",
  "1.0.9.8": "1; 0.49%"
But when I look at pool there is 1 tx with blockversion 1102, why it is not in report?

I wont be easier to make new update with "cutout" <1101?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 03:55:10 PM
Yes that is good question :) Or just delete mempool tx :D

zap transactions worked for me! --zapwallettxes=1

https://bitcoin.stackexchange.com/questions/45988/how-do-you-apply-zapwallettxes-on-windows

Open a command prompt to do it, the config file option didn't work for me. All the transactions I made yesterday and today are gone from my transactions list.

I actually lost a wallet with 60k because i forgot to backup it up and now the funds are showing in my sendto wallet again! Praise God!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 04:14:55 PM
Ok.. so "clean" install is enough :)

I've made versionreport:
Code: [Select]
  "Version": "Popularity,Percent %",
  "1.0.8.1": "116; 56.58%",
  "1.0.8.6": "8; 3.90%",
  "1.0.8.7": "53; 25.85%",
  "1.0.8.9": "2; 0.98%",
  "1.0.9.1": "2; 0.98%",
  "1.0.9.5": "1; 0.49%",
  "1.0.9.7": "22; 10.73%",
  "1.0.9.8": "1; 0.49%"
But when I look at pool there is 1 tx with blockversion 1102, why it is not in report?

I wont be easier to make new update with "cutout" <1101?

Looks like pool lost it but paid it anyway, look at showblock 33277, the botnet on 1081 snaked it back...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 06, 2018, 04:21:14 PM
Looks like pool lost it but paid it anyway, look at showblock 33277, the botnet on 1081 snaked it back...
same with 33183 and 33189. all "stolen"
Do you think that it is possible to win those rewards with >1101?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 06:25:20 PM
Rob, I just re-associated my Rosetta account back to my controller wallet since my headless Sanctuary's wallet is encrypted and won't auto unlock. The address from getboincinfo is different from the Rosetta website, which one should I trust?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 06:25:49 PM
same with 33183 and 33189. all "stolen"
Do you think that it is possible to win those rewards with >1101?
The issue is that the 1081 botnet has so much hashpower, their chain grows in chainweight within a few blocks of our 1101 block, and the chain reverts back to the chain with most work.

Everything changes on 33400, since they will not have a CPID, they will be forced to upgrade.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 06, 2018, 06:28:04 PM
Rob, I just re-associated my Rosetta account back to my controller wallet since my headless Sanctuary's wallet is encrypted and won't auto unlock. The address from getboincinfo is different from the Rosetta website, which one should I trust?
Re-associate wont work right now with these non-confirming tx.

Always trust the wallet, the info in the Rosetta account is just Step 1 of the process, Step 2 is that the rest of the network honors the burn in the chain Plus the burn must match the info in the Rosetta account.

I think we are in a holding pattern until 33400- personally im not even trying anything right now.

I am upgrading all my sancs though and all my machines.

Were really relying on this going without a hitch after 33400 :).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 06:30:48 PM
Re-associate wont work right now with these non-confirming tx.

Always trust the wallet, the info in the Rosetta account is just Step 1 of the process, Step 2 is that the rest of the network honors the burn in the chain Plus the burn must match the info in the Rosetta account.

I think we are in a holding pattern until 33400- personally im not even trying anything right now.

I am upgrading all my sancs though and all my machines.

Were really relying on this going without a hitch after 33400 :).

Alright, I'm just trying to figure out where to put the 50k so my UTXO will rise. I don't recognize the address shown on Rosetta.

UPDATE:
The address on my Rosetta homepage is different than my user profile(ID) page!

UPDATE 2:
The address from getboincinfo just changed also.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 06, 2018, 10:47:39 PM
Rob, while we are waiting. To get 100 UTXO, you need 50k BBP according to the wiki. What does the polpercentage affect then?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 04:16:46 AM
Ok so my MN in prod has been on latest version for 12 hours. I just got a payment. But looks like blockchain is divided because I see payment on Togo's block explorer but not Alex's. Also block numbers are different. Anyway main point is that we seem to be confirming transactions. I now have stakebalance!

Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 110000

In my config file I have

Code: [Select]
gen=1
genproclimit=1
polpercentage=50

so should be using over 50% of my 110k stake...

But!!!!

exec getboincinfo

Code: [Select]
  "8f273b30f8e0a298ed26e242762df701_RAC": 37944.24,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 37944.24,


My UTXO is only 25. Should be 100, correct?

We are moving in the right direction!
By the way, the 33400 block number is the one on the old version? Then we are only hours away!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 05:19:45 AM
My block explorer was supposed to switch to the new version right before block 33400 as this is what I understood was the cut off before a fork. It seems the chain forked waaaay before that block hence why you see different things znffal.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 07, 2018, 05:25:25 AM
I finally see my CPID after confirmations started working. However I want to separate the controller wallet for PoDC from the MN controller one, to another windows machine.

Can I run QT wallet on a new windows machine and re-associate to Rosetta, or do I have to "un-link" the current association first?
Thank you
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 05:42:25 AM
My block explorer was supposed to switch to the new version right before block 33400 as this is what I understood was the cut off before a fork. It seems the chain forked waaaay before that block hence why you see different things znffal.
Yes for sure. Been a busy week!
Looks like your explorer is down?

So the botnet will be kicked due to mandatory at block 33400.
But 33400 on our chain or the bot chain?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 07, 2018, 05:48:51 AM
Yes for sure. Been a busy week!
Looks like your explorer is down?

So the botnet will be kicked due to mandatory at block 33400.
But 33400 on our chain or the bot chain?

I would say that bot is already out of the "official" PoDC chain because we are getting our own confirmations (finally) and bot is 30 blocks ahead on its own chain. It can go on like that forever.

If bot tries to upgrade and hook to the "official" PoDC chain, he will mine by PoW until 33400 is reached (not likely as we are pretty close now).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 05:54:34 AM
I would say that bot is already out of the "official" PoDC chain because we are getting our own confirmations (finally) and bot is 30 blocks ahead on its own chain. It can go on like that forever.

If bot tries to upgrade and hook to the "official" PoDC chain, he will mine by PoW until 33400 is reached (not likely as we are pretty close now).

Oh cool. So it is unclear if Sanctuary rewards from the previous 8 hours from bot chain will persist, but rewards on new chain (in last few hours) should
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 05:57:24 AM
Yes for sure. Been a busy week!
Looks like your explorer is down?

So the botnet will be kicked due to mandatory at block 33400.
But 33400 on our chain or the bot chain?

It depends what you call botnet as it seems there has been different uses for that word around here. With the standard and used definition of what a botnet is,  it's impossible to know if the miners of this/these botnet(s) were upgraded or not and are therefore on the new chain (or not). They will eventually end up upgrading anyway.

There should only have been 1 chain until block 33400. Then those who didn't upgrade would have continued mining with PoBH and those who upgraded would have gone on a new chain with PoDC.

From what I understood, the new protocol (PoDC) was supposed to kick off on block 33400 and hence should have been the splitting point between those who upgraded and those who didn't upgrade (there is no such thing as the botnet chain/non-botnet chain, etc).

That did not happen and instead there was a split between those who upgraded and those who didn't upgrade waaaaay before block 33400 for other reasons  (haven't looked at the exact block but it happened at least 5 hours ago).

The block explorer is offline right now while I put it back on the chain used by people on version 1010002.

Edit:

To reply to Mike even though I'm sure Rob might not agree with that as we seem to have different definition of what a botnet is.

I'm going off this definition when I am talking about botnet:

"Cybercriminals use special Trojan viruses to breach the security of several users’ computers, take control of each computer and organise all of the infected machines into a network of ‘bots’ that the criminal can remotely manage."

The botnet(s) can/will mine with PoBH if it still make sense (financially) or is still the most profitable for them. They can mine using the same software you use to mine MIP. That's why you can't stop it as you can't separate your computer for example, from a computer that has been taken control of illegitimately and is being used to mine BBP.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 06:02:15 AM
It depends what you call botnet as it seems there has been different uses for that word around here. With the standard and used definition of what a botnet is,  it's impossible to know if the miners of this/these botnet(s) were upgraded or not and are therefore on the new chain (or not). They will eventually end up upgrading anyway.

There should only have been 1 chain until block 33400. Then those who didn't upgrade would have continued mining with PoBH and those who upgraded would have gone on a new chain with PoDC.

From what I understood, the new protocol (PoDC) was supposed to kick off on block 33400 and hence should have been the splitting point between those who upgraded and those who didn't upgrade (there is no such thing as the botnet chain/non-botnet chain, etc).

That did not happen and instead there was a split between those who upgraded and those who didn't upgrade waaaaay before block 33400 for other reasons  (haven't looked at the exact block but it happened at least 5 hours ago).

The block explorer is offline right now while I put it back on the chain used by people on version 1010002.

Right, I was using the Botnet chain as meaning the "other/old" chain. But PoBH chain would have made more sense.
Ok then so the 33400 block target number should be on the new/PoDC chain
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 06:06:06 AM
Right, I was using the Botnet chain as meaning the "other/old" chain. But PoBH chain would have made more sense.
Ok then so the 33400 block target number should be on the new/PoDC chain

33400 should be when the new protocol kicks off. But there is already been a fork between those who upgraded and those who didn't for other reasons. So if you upgraded, you are already on a new chain.

Edit:

Just to make to make it clear. It's not (or shouldn't be PoDC yet), it just forked for other reasons. Probably by forcing new clients to drop the connection from old clients. Both chains should still be exclusively PoBH right now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 06:10:54 AM
33400 should be when the new protocol kicks off. But there is already been a fork between those who upgraded and those who didn't for other reasons. So if you upgraded, you are already on a new chain.

Edit:

Just to make to make it clear. It's not (or shouldn't be PoDC yet), it just forked for other reasons. Probably by forcing new clients to drop the connection from old clients. Both chains should still be exclusively PoBH right now.

Awesome, thanks. That's clear and makes sense.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:51:03 AM
Guys, I set my alarm to watch all the fireworks but unfortunately I have to take my son somewhere, so Ill join the party as soon as possible.

I see the non-PODC chain (the botnet is at block 33401 with a difficulty of 5000! a very high diff) and the PODC chain is still at 33376 with a 97 diff, and Im hoping that with the confirms and wild differences forming in the two chains, none of the "botnet" blocks will bleed back over to our podc chain, lets hope all these confirms stick.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 07:20:04 AM
Looks like somebody was "smart" and connected to an upgraded node from the "other chain". Since it's the same protocol but is/was/has the longest chain, the upgraded nodes now took all these blocks in or may be stuck I guess depending on your situation.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 07:55:31 AM
I was talking to canopus and he is stuck on the old chain with the latest daemon. Just be aware of that.

Update:
Just found out my sanctuary crashed an hour ago:
Code: [Select]
2018-03-07 13:00:03 DSEG -- Sent 168 Masternode invs to peer 6366
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:32 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:32 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:32 ERROR: Block has no ancestor.

2018-03-07 13:00:32 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: block is marked invalid
2018-03-07 13:00:48 ERROR: invalid header received 14afaeadd3d5a967bf92b99d3b49df9d0dc02883cb2b5e15604a3dec04abcda4
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (23 -> 44)
2018-03-07 13:00:48 ERROR: invalid header received fc91647bc98f1427627243475c5b3cb8b17b72ed6ed1e6ad1635ec301877486d
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (44 -> 65)
2018-03-07 13:00:48 ERROR: invalid header received f301478b883c7bd4a4f486a53210f4816f38724c3bcfb0608bf8aa7f186df2a6
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (65 -> 86)
2018-03-07 13:00:48 ERROR: invalid header received 26b92a245a8d0897fd3595e6ac5308b020f3f0108d84fe9649cd0a57a26ddab8
2018-03-07 13:00:48 ERROR: AcceptBlockHeader: prev block not found
2018-03-07 13:00:48 Misbehaving: 109.230.40.66:58706 (86 -> 107) BAN THRESHOLD EXCEEDED
2018-03-07 13:00:48 ERROR: invalid header received 08dd452df7d78364f8778c302b6afc7b62cd5646560f39f63659a465a9f46567
2018-03-07 13:00:51 MASTERNODEPAYMENTSYNC -- Sent Masternode payment votes to peer 6316
2018-03-07 13:57:57
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 08:08:37 AM
I've got three different wallets open, and all three seem to be on different chains:

33355:
Code: [Select]
15:08:26

getblockhash 33355


15:08:26

752a784656582f0123dc396e5afc0fc8f20d2cfd958675165138137fdeadaef1

33357:
Code: [Select]
15:05:39

getblockhash 33357


15:05:39

3a230e3e705441c8c02fa412191ff3aa11380205cb41cfe10e677f470fe558fd


33410:
Code: [Select]
15:07:05

getblockhash 33410


15:07:05

8de885ac26fed11683af444c59d1ed5f159a774a36088f473e7695df42abf76f



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:10:05 AM
I've got three different wallets open, and all three are on different chains:

Did you check the block height for all 3?

I'm on height 33380.


09:11:43

getblockhash 33380


09:11:43

62e1c04282bb448cc3e51eab8e3a254e9b4ead3273878b1cb8c6d34cc4c921b8
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 08:13:36 AM
The active chain is always the longest chain.  Somebody was smart and saw the only thing preventing upgraded node from connecting to old nodes was to check the version number (which can be changed easily).

The "old chain" was the longest/chain with the most work so it became the active chains. Upgraded nodes are now on that chain or stuck depending on circumstances.

On top of that, I haven't been following PoDC much I guess PoBH seems to still be accepted by "upgraded" nodes so they're accepting these blocks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 08:16:15 AM
Did you check the block height for all 3?

I'm on height 33380.


09:11:43

getblockhash 33380


09:11:43

62e1c04282bb448cc3e51eab8e3a254e9b4ead3273878b1cb8c6d34cc4c921b8

The blocks stated are the blockheights, so it seems to are on an other chain too... Or certain chains just stall at certain points.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:20:46 AM
Looks like somebody was "smart" and connected to an upgraded node from the "other chain". Since it's the same protocol but is/was/has the longest chain, the upgraded nodes now took all these blocks in or may be stuck I guess depending on your situation.
Or more like "stupid", as anyone who created a fraudulent client to "help" the botnet in my opinion is a traitor, and practices dissent.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 08:22:57 AM
The active chain is always the longest chain.  Somebody was smart and saw the only thing preventing upgraded node from connecting to old nodes was to check the version number (which can be changed easily).

The "old chain" was the longest/chain with the most work so it became the active chains. Upgraded nodes are now on that chain or stuck depending on circumstances.

On top of that, I haven't been following PoDC much I guess PoBH seems to still be accepted by "upgraded" nodes so they're accepting these blocks.

I thought that the older wallets had different protocol versions. Or has that nothing to do with this?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:24:32 AM
Or more like "stupid", as anyone who created a fraudulent client to "help" the botnet in my opinion is a traitor, and practices dissent.

So should I be banning peers with height greater then 33400 or should i just let it play out? But it's crashing my masternode.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 08:24:46 AM
I thought that the older wallets had different protocol versions. Or has that nothing to do with this?

The protocol version is just a number. It can't really be enforced.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 08:29:26 AM
Or more like "stupid", as anyone who created a fraudulent client to "help" the botnet in my opinion is a traitor, and practices dissent.

We don't really agree on the definition of botnet so I don't really want to comment on that. However, I think it could have been expected since it can really be changed -edit: adding "easily"- and can't really be enforced. The "botnet" or someone is using a custom miner only caring about the protocol but ignoring the protocol number if you remember. 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:33:28 AM
I finally see my CPID after confirmations started working. However I want to separate the controller wallet for PoDC from the MN controller one, to another windows machine.

Can I run QT wallet on a new windows machine and re-associate to Rosetta, or do I have to "un-link" the current association first?
Thank you

I would recommend waiting til we have one chain, and maybe at least 25 blocks in after 33400 first, but anyway, you can reassociate your wallet to a new wallet by just running the 'exec associate' command, with "true" at the end (that means force).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:34:34 AM
zap transactions worked for me! --zapwallettxes=1

https://bitcoin.stackexchange.com/questions/45988/how-do-you-apply-zapwallettxes-on-windows

Open a command prompt to do it, the config file option didn't work for me. All the transactions I made yesterday and today are gone from my transactions list.

I actually lost a wallet with 60k because i forgot to backup it up and now the funds are showing in my sendto wallet again! Praise God!

You can also just go to dos prompt and type:

cd c:\program files\biblepaycore
biblepay-qt -zapwallettxes=1

Etc.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:36:32 AM
Rob, while we are waiting. To get 100 UTXO, you need 50k BBP according to the wiki. What does the polpercentage affect then?

The polpercentage affects how much of your 'exec stakebalance' the wallet is allowed to try to stake in a PODCUpdate tx.

If you have 100,000 available generally then you could set it at 50 for example to stake 50K per podcupdate.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:37:53 AM
Ok so my MN in prod has been on latest version for 12 hours. I just got a payment. But looks like blockchain is divided because I see payment on Togo's block explorer but not Alex's. Also block numbers are different. Anyway main point is that we seem to be confirming transactions. I now have stakebalance!

Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 110000

In my config file I have

so should be using over 50% of my 110k stake...

But!!!!

exec getboincinfo

My UTXO is only 25. Should be 100, correct?

We are moving in the right direction!
By the way, the 33400 block number is the one on the old version? Then we are only hours away!


It could be at the time, the exec stakebalance was low (due to the issue where we cant see that our chain depth is increasing (because our prior utxo confirmation height is so miniscule).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:39:43 AM
I would say that bot is already out of the "official" PoDC chain because we are getting our own confirmations (finally) and bot is 30 blocks ahead on its own chain. It can go on like that forever.

If bot tries to upgrade and hook to the "official" PoDC chain, he will mine by PoW until 33400 is reached (not likely as we are pretty close now).

I think the botnet was winning through 80% of the night, then we hosed them up for about 10 blocks around 5AM US time, now they appear to be hosing us up again.  (90% of my tx from last night were confirmed, but the PODC sent a few hours ago wont confirm).  I think we are going to be OK though in the long run!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:41:10 AM
You can also just go to dos prompt and type:

cd c:\program files\biblepaycore
biblepay-qt -zapwallettxes=1

Etc.

Thank, yup that's what I did.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:42:54 AM
The active chain is always the longest chain.  Somebody was smart and saw the only thing preventing upgraded node from connecting to old nodes was to check the version number (which can be changed easily).

The "old chain" was the longest/chain with the most work so it became the active chains. Upgraded nodes are now on that chain or stuck depending on circumstances.

On top of that, I haven't been following PoDC much I guess PoBH seems to still be accepted by "upgraded" nodes so they're accepting these blocks.

Not correct - the active chain is the chain with the most chain-work that has not violated any business logic rules.

Thats why the POBH chain (shorter) was the official chain for a while. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 08:46:29 AM
Not correct - the active chain is the chain with the most chain-work that has not violated any business logic rules.

Thats why the POBH chain (shorter) was the official chain for a while.

As you can see from you own quote of my post, I did say with the most work.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:50:02 AM
The protocol version is just a number. It can't really be enforced.

Yes, it can be enforced.  If I enabled my switch to reject blocks from prior versions, it would have been enforced.  We also could have enforced the block version in a hard fashion.

As far as the botnet definition goes, let me clarify it for you:
A botnet in Biblepay is a POW mining organization that is producing more than 51% of the hashpower on the network and refuses to upgrade the client in a timely manner.

Now there is no "confusion" about the terminology here.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:52:29 AM
As you can see from you own quote of my post, I did say with the most work.

Not correct - you said in two places on the prior page the active chain is always the Longest Chain.

"Looks like somebody was "smart" and connected to an upgraded node from the "other chain". Since it's the same protocol but is/was/has the longest chain, the upgraded nodes now took all these blocks in or may be stuck I guess depending on your situation."

I'm clarifying its Not the longest chain.  Its the chain with the most chain-work.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 08:56:16 AM
Yes, it can be enforced.  If I enabled my switch to reject blocks from prior versions, it would have been enforced.  We also could have enforced the block version in a hard fashion.

As far as the botnet definition goes, let me clarify it for you:
A botnet in Biblepay is a POW mining organization that is producing more than 51% of the hashpower on the network and refuses to upgrade the client in a timely manner.

Now there is no "confusion" about the terminology here.

1) You're the only with that definition of what a botnet is so I think there is confusion. Just google what a "botnet" is I guess..?

2) The version number cannot be enforced as it is not a change of protocol but just changing a number in the code. You can easily just change the Biblepay client version you're advertising to be anything...

If you have a line of code saying only accept block version > 3....I can just advertise my block version > 3 and it will be accepted if there is no other checks. The number alone can't be enforced...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 07, 2018, 08:57:01 AM
Hi all,

If I understand correctly - I can check on which chain I am with my Win miner with this:

Code: [Select]
15:55:10

getblockhash 33410


15:55:10

8de885ac26fed11683af444c59d1ed5f159a774a36088f473e7695df42abf76f

Is this the correct hash?
Thank you.

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 09:00:08 AM
Not correct - you said in two places on the prior page the active chain is always the Longest Chain.

"Looks like somebody was "smart" and connected to an upgraded node from the "other chain". Since it's the same protocol but is/was/has the longest chain, the upgraded nodes now took all these blocks in or may be stuck I guess depending on your situation."

I'm clarifying its Not the longest chain.  Its the chain with the most chain-work.

Did you look at your quote of my own post lol. I said after that the chain with the most work (the one you quoted if you need me to refresh your memory).

When I wrote that post (the one you quoted just now) the longest chain was the one with the most work...that's where all the hashing power is.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 09:11:46 AM
canopus - Today at 10:07 AM
HEALTH NODES
addnode "54.37.156.244" "add"
addnode "139.99.101.222" "add"
addnode "47.93.223.203" "add"
addnode "45.32.7.66" "add"
addnode "80.211.203.45" "add"
addnode "45.76.56.211" "add"
can you post it in testnetforum....for add

These nodes are on 33384 I believe, I didn't check them. Just reposting.

Question: If another chain wins, how do I switch over. How do I check which chain is winning?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 09:17:22 AM
canopus - Today at 10:07 AM
HEALTH NODES
addnode "54.37.156.244" "add"
addnode "139.99.101.222" "add"
addnode "47.93.223.203" "add"
addnode "45.32.7.66" "add"
addnode "80.211.203.45" "add"
addnode "45.76.56.211" "add"
can you post it in testnetforum....for add

These nodes are on 33384 I believe, I didn't check them. Just reposting.

Question: If another chain wins, how do I switch over. How do I check which chain is winning?

Can someone confirm it is the 'right thing' to use these nodes and be on that chain?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 09:26:33 AM
I'm going to sleep and wish everyone the best while you all figure out that situation.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 09:28:27 AM
I'm going to sleep and wish everyone the best while you all figure out that situation.

Should keep me awake throughout the day.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 09:54:03 AM
Should keep me awake throughout the day.

Haha! Me too. Been on the computer many hours in the past couple of days  :( ;D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 10:14:09 AM
1) You're the only with that definition of what a botnet is so I think there is confusion. Just google what a "botnet" is I guess..?

2) The version number cannot be enforced as it is not a change of protocol but just changing a number in the code. You can easily just change the Biblepay client version you're advertising to be anything...

If you have a line of code saying only accept block version > 3....I can just advertise my block version > 3 and it will be accepted if there is no other checks. The number alone can't be enforced...

There are a lot of things in certain niche businesses, such as Crypto, that differ from industry standard and run of the mill development.  This is called "domain knowledge".  If Im the leader of the group and hire 5 devs to work with me, and want to hold daily scrum meetings, and I tell you what a certain term means for our business, then its your responsibility to use it - so we can communicate in a more efficient way.  Its not your job to argue with the head of development about things, thats non productive and is a net negative - it also wastes everyones elses time, and is embarassing.

Next, I know its true that certain soft rules - such as a protocol version - when implemented in a way where another node will hang up and refuse to comunicate based on that version, is not a hard rule, and it can be circumvented by a hacker.  But apparently what you have a hard time grasping, is there are also hard rules in the client, that have been programmed by both Dash and Me in both of my communities, that do enforce soft rules.  For example, we have a piece of code in our biblepay version right now that adds up what percent of blocks were solved by prior versions in the last 100 in the chain, and it does take into account the protocol version.  I could have easily enabled that feature and allowed the chain to fork if *any* blocks were solved by a version below the greatest in the chain.  I didnt, because I felt at the time we would have a smoother transition to the cutover block by letting everyone play.  You need to understand every algorithm in the code before making misleading statements to our community.    I am still maintaining that anyone who deliberately compiles a fraudulent version and detracts from the prod experience is a dangerous and semi-untrustworthy individual, when we are all here trying to get past the block number without forks and as much integrity as possible.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 10:15:17 AM
Can someone confirm it is the 'right thing' to use these nodes and be on that chain?

Its useless.  Its more beneficial to rebuild your chain once we get past 33440.

The wallet picks its own addnodes and puts them in peers.dat, and only needs one addnode: the one compiled in.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 10:24:21 AM
Is everyone's magnitude at zero or is it just me? (Been at zero for 12 hours or so.)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 10:31:04 AM
Is everyone's magnitude at zero or is it just me? (Been at zero for 12 hours or so.)
Yeah, thats normal until we create the first superblock - then the system assigns everyone a magnitude for the first time.

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

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 07, 2018, 10:41:36 AM
My wallet says 33360, my 1BBP transaction now has confirmations, my utxo show 0 and my stakebalance shows 0, my CPID now shows up in exec getboincinfo. Is all this correct? I change polpercentage in the dat file to 100.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 11:01:06 AM
Yeah, thats normal until we create the first superblock - then the system assigns everyone a magnitude for the first time.

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

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

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

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

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

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 11:02:50 AM
My wallet says 33360, my 1BBP transaction now has confirmations, my utxo show 0 and my stakebalance shows 0, my CPID now shows up in exec getboincinfo. Is all this correct? I change polpercentage in the dat file to 100.
Can you paste your exec getboincinfo?  I can look up your CPID from my sanc.

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

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 11:05:25 AM
So things look semi-OK, I guess on a scale from 1-10, maybe a 5 for this go live.  Primarily low because none of our transactions are confirming.
So here is the first rock in the rocky start:
The exec testvote, this is used to "prime" our sancs for the first contract (no need to ever do this later once we are rolling), gave me an error- I cant paste it : Something to the effect of Unable to calculate magnitudes, project RAC below minimum.

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

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

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

Rob, I think we are on a different chain:

Code: [Select]
{
  "DataList": "UTXOWEIGHT",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-07-2018 14:44:31)": "100",
  "4004B7FEC94751F61FE9135977BAC553 (03-07-2018 13:38:25)": "100",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-07-2018 15:01:37)": "50",
  "6BCD1F25DC07679DB5AD812A012DF1A4 (03-07-2018 14:21:22)": "0",
  "84D803E4D82D3BDCDF8E2AB601E93E20 (03-07-2018 15:53:17)": "100",
  "8735CFE64D964416DBA6015EB414CF7E (03-07-2018 12:17:54)": "60",
  "8F273B30F8E0A298ED26E242762DF701 (03-07-2018 09:56:52)": "25",
  "940552F602F67A3CF57A452438F36EE9 (03-07-2018 05:44:28)": "25",
  "96892EC0FC8A2710FA84F26C9C84CD3E (03-07-2018 12:03:32)": "60",
  "968D0A04AA31FA9BBBFF2EB6A87B02F2 (03-07-2018 09:56:52)": "25",
  "A9420A038E44750C69CA4497FE08C2A9 (03-07-2018 15:01:37)": "60",
  "CA895B47AACFFBDBF906201821AF2F9F (03-07-2018 14:21:22)": "50",
  "D4E56169934BF307F145C75BCB2896A2 (03-07-2018 15:14:26)": "25",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-07-2018 08:33:51)": "100",
  "E6CE50042187D4B285568D86EF458F32 (03-07-2018 15:14:26)": "75",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (03-07-2018 16:26:29)": "100",
  "E94C1704C75F731F8BFDE303F08408EE (03-07-2018 13:01:08)": "75"
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 07, 2018, 11:09:36 AM
Hi,

Here is my boincinfo - does it look ok?

Code: [Select]
18:08:33

exec getboincinfo


18:08:35

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

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 11:23:25 AM
Hi,

Here is my boincinfo - does it look ok?

Code: [Select]
18:08:33

exec getboincinfo


18:08:35

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

Best regards,
Simon

In general, it seems about the same as mine:

Code: [Select]
18:18:36

exec getboincinfo


18:18:38

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

But I do show up in Mike's list with an UTXOWeight of 100.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 11:48:44 AM
Rob, I think we are on a different chain:

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

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

Probably unfruitful to look at the blockhash right now, lets check them after 33440, and see if we can match up then.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 07, 2018, 11:57:52 AM
Hey Rob, here's the exec getboincinfo you requested:


Code: [Select]
11:56:35

exec getboincinfo


11:56:36

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422345,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2711.63,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2711.63,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 11:59:05 AM
Yeah, were on a different chain, Im going to rebuild that particular sanc now.

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

Sanc:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

Wallet:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 07, 2018, 12:04:32 PM
Wallet:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

Hi,

My wallet hash is:

Code: [Select]
19:02:00
getblockhash 33401

19:02:00
5a273421d162aeeddde4883dcd49e9ec4e558d05673e4fc1b05ec3f222c3831e

Can I do anything about this right now?

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 07, 2018, 12:08:55 PM
How do I add information in the boxes with the scroll bars? So I don't take up lots of post space.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 12:10:45 PM
How do I add information in the boxes with the scroll bars? So I don't take up lots of post space.
Thanks, just surround it with
"[ code ]"

and

[ /code ]

Without the spaces in there.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 07, 2018, 12:23:26 PM
Thanks, just surround it with
"[ code ]"

and

[ /code ]

Without the spaces in there.

Thanks, worked! My info is above somewhere. I appreciate everything you're doing Rob.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 12:35:22 PM
Sanc:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

Wallet:
getblockhash 33401
a5fc139e2881da15080abe85e2caf500abf02ae145f1a257755bbd5613b5384f

I have same hash like you.
It looks good for me... 3 wallets on same chain (looks good because it is same as Mike and explorer :) )
My task and UTXO are 100 (after many hours, blood and sweat) :)
BUT... after getinfo I have in all of my wallets this message:
Code: [Select]
"errors": "Warning: We do not appear to fully agree with our peers! You may need to upgrade, or other nodes may need to upgrade."
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 07, 2018, 12:51:30 PM
Is there a way to view all the forked blockchains?
I tried running getchaintips command but it crashes my wallet LOL

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

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

Which chain are we waiting to reach 33440?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 12:57:23 PM
Is there a way to view all the forked blockchains?
I tried running getchaintips command but it crashes my wallet LOL

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

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

Which chain are we waiting to reach 33440?

I think we are waiting to see which one wins. The block has already passed, it was 33400.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 12:57:36 PM
Is there a way to view all the forked blockchains?
I tried running getchaintips command but it crashes my wallet LOL

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

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

Which chain are we waiting to reach 33440?

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

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

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 12:58:13 PM
Backup Explorer is on 33407


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

BTW: I see some node with 1103 with same block as I. Oh and 1099 wallet is there too. Is it possible?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 01:00:19 PM
I think we are waiting to see which one wins. The block has already passed, it was 33400.

I made a mistake on the block number - its 33440 actually , sorry :).  Thats 1 block from now.

Btw, the latest version that I checked in , 1103 - shows the CPID who solved the block after block 33440.  We will need this info to analyze blocks 33440+ to ensure the subsidy < 600 for the heat side, and that a cpid is solving it etc.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 01:03:09 PM
I made a mistake on the block number - its 33440 actually , sorry :).  Thats 1 block from now.

Btw, the latest version that I checked in , 1103 - shows the CPID who solved the block after block 33440.  We will need this info to analyze blocks 33440+ to ensure the subsidy < 600 for the heat side, and that a cpid is solving it etc.

I think most of us trying to get on PODC is on the lower height chain. The higher chain is the old one correct? It looks like that chain will win at the moment. I made a new wallet and it's also syncing to the higher chain.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 01:16:17 PM
I made a mistake on the block number - its 33440 actually , sorry :).  Thats 1 block from now.

Btw, the latest version that I checked in , 1103 - shows the CPID who solved the block after block 33440.  We will need this info to analyze blocks 33440+ to ensure the subsidy < 600 for the heat side, and that a cpid is solving it etc.
Ok, so if block 33441 is with reward 600 that will be correct chain?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 01:16:52 PM
I think most of us trying to get on PODC is on the lower height chain. The higher chain is the old one correct? It looks like that chain will win at the moment. I made a new wallet and it's also syncing to the higher chain.
Well I cant really say which one is correct as its dynamically the one with the most total work on it (sum of total chainwork, which is the bits in the prior block period lookback).

I just realized one  other hurdle we have hit, we only have 7 signed cpids in the higher chain, meaning that its going to be extremely unlikely those cpids solve any blocks, LOL, so we are going to sit here even longer and wait for the diff to fall while some of these tx get inducted and allow us to grow in cpid size.

The only bright light in this whole situation is kjv.cpp has a slight change in BL rules after 15 mins, meaning I believe that breaks compatibility with the botnet versions - in hindsight I should have done a hard break in there (IE changed the hash function for the cutover).

Lets just see what happens and not jump to change the whole program yet, lets see how stable we become.

If worse comes to worse, we can always add a breaking change in and force a mandatory - and add a checkpoint, but lets not jump to that unless absolutely necessary.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 01:19:12 PM
Ok, so if block 33441 is with reward 600 that will be correct chain?
Yes, this is one other great issue, the payment drops to 600 after the cutover block, so that also should break the botnet! 
So lets see if diff drops like this after 33440:

1500, 1500, 750,750,750, 325,325,325,325, 170,170,80,80,40,40 - by then I think we can take over with CPIDs.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 01:33:31 PM
Yes, this is one other great issue, the payment drops to 600 after the cutover block, so that also should break the botnet! 
So lets see if diff drops like this after 33440:

1500, 1500, 750,750,750, 325,325,325,325, 170,170,80,80,40,40 - by then I think we can take over with CPIDs.

Well, do you suggest I delete the chains and resync? I'm pretty sure I'll be on your chain then.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 07, 2018, 01:36:42 PM
Well, do you suggest I delete the chains and resync? I'm pretty sure I'll be on your chain then.

I'm doing that, because my CPID 1BBP transaction disappeared and I'm back without registration... let's hope it works this time
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 01:40:22 PM
I'm doing that, because my CPID 1BBP transaction disappeared and I'm back without registration... let's hope it works this time

My sanctuary was on the lower height but then it jumped to an even lower one for some reason so I'm re-syncing that one for now.

Update:
Done, looks like it is also on the higher blockchain now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 07, 2018, 01:44:51 PM
Hi guys

I'm trying to bring two machines on to the new PODC. Last night I tried the GUI to associate my Rosetta account with Biblepay. Waited and nothing showed up this morning. I ran it again earlier this morning and waited, still nothing. This is the current readout of getboincinfo from my debug. Am I right in understanding my CPID is NOT associated with my Biblepay wallet?

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422347,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

I just ran a command line associate a few blocks ago, and then I ran it again and it says.

"Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

I'm hoping this will work. But just wondering if anyone else had trouble with using the GUI to associate? Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 01:47:42 PM
Hi guys

I'm trying to bring two machines on to the new PODC. Last night I tried the GUI to associate my Rosetta account with Biblepay. Waited and nothing showed up this morning. I ran it again earlier this morning and waited, still nothing. This is the current readout of getboincinfo from my debug. Am I right in understanding my CPID is NOT associated with my Biblepay wallet?

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422347,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

I just ran a command line associate a few blocks ago, and then I ran it again and it says.

"Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

I'm hoping this will work. But just wondering if anyone else had trouble with using the GUI to associate? Thanks.

If you ran it again within 5 blocks it will say that. Can you post your getinfo?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 07, 2018, 01:54:03 PM
Hey Mike, thanks for the quick response.

{
  "version": 1010003,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.0.3",
  "balance": 43.58675910,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33441,
  "timeoffset": 2,
  "connections": 8,
  "proxy": "",
  "difficulty": 1561.54112909823,
  "testnet": false,
  "keypoololdest": 1515744128,
  "keypoolsize": 1001,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 02:00:42 PM
Hey Mike, thanks for the quick response.

{
  "version": 1010003,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.0.3",
  "balance": 43.58675910,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33441,
  "timeoffset": 2,
  "connections": 8,
  "proxy": "",
  "difficulty": 1561.54112909823,
  "testnet": false,
  "keypoololdest": 1515744128,
  "keypoolsize": 1001,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}

Wait 5 blocks, then close and restart your wallet. Run exec getboincinfo again and we'll go from there.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 02:08:15 PM
So block 33441 paid the sanctuary 11K, but looking at the BL for that, I think we are OK, because we enforce the payments after GoLive+1, so that explains why the lower subsidy didnt kick in til 33442.  Looking at 33442, miner got paid 450, sanc 4500, so far so good.

Now lets hope the diff does drop, and some cpids get inducted in the chain. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 02:16:45 PM
So block 33441 paid the sanctuary 11K, but looking at the BL for that, I think we are OK, because we enforce the payments after GoLive+1, so that explains why the lower subsidy didnt kick in til 33442.  Looking at 33442, miner got paid 450, sanc 4500, so far so good.

Now lets hope the diff does drop, and some cpids get inducted in the chain.
Ok. So I was on wrong chain...
Resynced and now my CPID is associated with my wallet with more than 50k.
task and UTXO are 0. Stakabalce is with my all BBPs, but podcupdate fail with "Insufficient funds."...
So I'm on the begining :( I'm confused and helpless
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 02:17:42 PM
Code: [Select]
21:14:04

getblockhash 33442


21:14:04

e4fd364c82e86d2ed808160f6fa0842598447722bafd76e6f5fbf463ec0993c7


21:14:19

getinfo


21:14:20

{
  "version": 1010002,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.0.2",
  "balance": 3168890.87611826,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33442,
  "timeoffset": -8,
  "connections": 8,
  "proxy": "",
  "difficulty": 989.3094001745554,
  "testnet": false,
  "keypoololdest": 1518075876,
  "keypoolsize": 1001,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}


21:14:31

exec getboincinfo


21:14:33

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


21:16:08

exec datalist dcc


21:16:08

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 08:37:48)": "04fba56d89a5eb38b1b82f8a6240132c;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;1981529;INQ84/j9PlIAiksMlIWytRUWeT1Oy1IUearmIBEQwhSGPyv91yrspBm6SoYXiLQ3g5XTKXBNWBQcrs+GQfLbuzI=;0",
  "1E7184E17377549D5A7D7A2EDFB51017 (03-05-2018 17:58:54)": "1e7184e17377549d5a7d7a2edfb51017;B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m;B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m;1982314;H1xGyUiI2Tpbw7TSUZ8wEymzPo4kbb2sHsy6Fn4WyqesOCMS1JxWqrdnqUo0wC4YwhC4lQEiOH7epkNycltZTfc=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "CA895B47AACFFBDBF906201821AF2F9F (03-05-2018 13:27:33)": "ca895b47aacffbdbf906201821af2f9f;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;475629;H1QQr77z7khrCeX3CJn6iUAQRqmqRZyIAl1CJdfeJx3oG9wfeJknjhmBvuokvJSUhqC+3+nzWhsr7T3MOkSoFqg=;0",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-05-2018 17:58:54)": "d9b22fccfae5582d4ee7838883aaa3cf;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;1981615;IO9jRoYdWOO9iSFJ+yBLrlIqAhzyxKAv16jrpLrB3sqfEBhHuO+Tu8UWNQISXmp1cUePVOKJm8TBvY8gN8DsVuY=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}


21:10:46

exec podcupdate


21:11:38

{
  "Command": "podcupdate",
  "PODCUpdate": false
}


I think I'm on the right chain. Tried a podcupdate after block 33440, but returned false (PODCUpdate::Error: Insufficient funds.). My CPID seems to be on the list, but my TaskWeight and UTXOWeight are still zero.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 02:21:05 PM
Code: [Select]
21:14:04

getblockhash 33442


21:14:04

e4fd364c82e86d2ed808160f6fa0842598447722bafd76e6f5fbf463ec0993c7


21:14:19

getinfo


21:14:20

{
  "version": 1010002,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.0.2",
  "balance": 3168890.87611826,
  "privatesend_balance": 0.00000000,
  "retirement_balance": 0,
  "blocks": 33442,
  "timeoffset": -8,
  "connections": 8,
  "proxy": "",
  "difficulty": 989.3094001745554,
  "testnet": false,
  "keypoololdest": 1518075876,
  "keypoolsize": 1001,
  "unlocked_until": 0,
  "paytxfee": 0.00000000,
  "relayfee": 0.00010000,
  "errors": ""
}


21:14:31

exec getboincinfo


21:14:33

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


21:16:08

exec datalist dcc


21:16:08

{
  "DataList": "DCC",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-05-2018 08:37:48)": "04fba56d89a5eb38b1b82f8a6240132c;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa;1981529;INQ84/j9PlIAiksMlIWytRUWeT1Oy1IUearmIBEQwhSGPyv91yrspBm6SoYXiLQ3g5XTKXBNWBQcrs+GQfLbuzI=;0",
  "1E7184E17377549D5A7D7A2EDFB51017 (03-05-2018 17:58:54)": "1e7184e17377549d5a7d7a2edfb51017;B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m;B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m;1982314;H1xGyUiI2Tpbw7TSUZ8wEymzPo4kbb2sHsy6Fn4WyqesOCMS1JxWqrdnqUo0wC4YwhC4lQEiOH7epkNycltZTfc=;0",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-04-2018 23:17:49)": "6785ded1f65063ef8f01f42deb31cf1d;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j;1981965;IHbjBdincaH8YS/XL7k6VR9n8dHysachVwo63vwZk732SkG4+Q4qx/qObz2VsYPdBL8RtBpxv5pv3/gmmqtGFPY=;0",
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
  "8F273B30F8E0A298ED26E242762DF701 (03-05-2018 02:22:28)": "8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0",
  "CA895B47AACFFBDBF906201821AF2F9F (03-05-2018 13:27:33)": "ca895b47aacffbdbf906201821af2f9f;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J;475629;H1QQr77z7khrCeX3CJn6iUAQRqmqRZyIAl1CJdfeJx3oG9wfeJknjhmBvuokvJSUhqC+3+nzWhsr7T3MOkSoFqg=;0",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-05-2018 17:58:54)": "d9b22fccfae5582d4ee7838883aaa3cf;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD;1981615;IO9jRoYdWOO9iSFJ+yBLrlIqAhzyxKAv16jrpLrB3sqfEBhHuO+Tu8UWNQISXmp1cUePVOKJm8TBvY8gN8DsVuY=;0",
  "E94C1704C75F731F8BFDE303F08408EE (03-05-2018 02:22:28)": "e94c1704c75f731f8bfde303f08408ee;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN;1981209;IG2r+VxRlr+3ceKJhbLnldsMVoZv/uoKgx4SukL9Z+bJdIjpjCMaoceE1Aog7hFOSGJd70eU6bgLJM56hCRwV1k=;0"
}


21:10:46

exec podcupdate


21:11:38

{
  "Command": "podcupdate",
  "PODCUpdate": false
}


I think I'm on the right chain. Tried a podcupdate after block 33440, but returned false (PODCUpdate::Error: Insufficient funds.). My CPID seems to be on the list, but my TaskWeight and UTXOWeight are still zero.

Did you try exec stakebalance? And make sure the funds are in BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD with more then 5 confirmations. I think your datalist is old, it needs to be updated.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 02:23:15 PM
I think I'm on the right chain. Tried a podcupdate after block 33440, but returned false (PODCUpdate::Error: Insufficient funds.). My CPID seems to be on the list, but my TaskWeight and UTXOWeight are still zero.
So, almost same as me. CPID registered and in DCC list, TaskWeight and UTXOWeight are zero, but with "Insufficient funds." PODCupdate result and stakebalnce with all my BBPs.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 02:24:48 PM
So, almost same as me. CPID registered and in DCC list, TaskWeight and UTXOWeight are zero, but with "Insufficient funds." PODCupdate result and stakebalnce with all my BBPs.

exec stakebalance is > 50k?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 02:33:49 PM
exec stakebalance is > 50k?
yes... it was... then podc update was successful and my taskheight jumped to 100, but then (because of PODC micro payment) was my balance "renewed" and now it is zero :( but I don't know why after podc update my UTXO didn't jumped to 100 too.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 02:37:36 PM
yes... it was... then podc update was successful and my taskheight jumped to 100, but then (because of PODC micro payment) was my balance "renewed" and now it is zero :( but I don't know why after podc update my UTXO didn't jumped to 100 too.

We'll figure this out together, even if I have to add another argument to podcupdate.
First though could you please restart with -zapwallettxes, and check your stakebalance and resend you podcupdate again?
Lets see if that fixes it- also it takes 6 confirms for the wallet to memorize the utxoweight.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 02:43:08 PM
I see 3 votes when I run testvote, we need 10 right?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 03:00:08 PM
Hi guys,
Woke up this morning excited to see how we go today!

Lot's of posts! Can I please ask the following for clairty's sake:

1. So it looks like things should change when we reach block 33440? I see Alex's explorer is past that but Togo's not yet. Do we know which one will change to PoDC?

2. I see there is a leisure upgrade available. What are the changes? Should I be updating to this for controller wallet, Sanctuary wallet, PoDC wallet?

3. Should I be doing -zapwallettxes  (now or later) for controller wallet, Sanctuary wallet, PoDC wallet?

4. Anything else I should be doing now?

Many thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 03:15:57 PM
Hi guys,
Woke up this morning excited to see how we go today!

Lot's of posts! Can I please ask the following for clairty's sake:

1. So it looks like things should change when we reach block 33440? I see Alex's explorer is past that but Togo's not yet. Do we know which one will change to PoDC? Nope, but if you resync the chain it should be at 33446. I'm betting on this one.

2. I see there is a leisure upgrade available. What are the changes? Should I be updating to this for controller wallet, Sanctuary wallet, PoDC wallet? It is a minor upgrade to show more info.

3. Should I be doing -zapwallettxes  (now or later) for controller wallet, Sanctuary wallet, PoDC wallet? After resyncing i would do it.

4. Anything else I should be doing now? check your getboincinfo to make sure its associated and if its in the dcc list.

Many thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 03:19:49 PM
We'll figure this out together, even if I have to add another argument to podcupdate.
First though could you please restart with -zapwallettxes, and check your stakebalance and resend you podcupdate again?
Lets see if that fixes it- also it takes 6 confirms for the wallet to memorize the utxoweight.
Ok.. it looks that my wallet starts to live "old life". After that unsuccessful PODC it made "old" tx's from paaaast. I don't understand why, because I've made zapwallettxes before... so.. anyway... my stake is now 0 and it looks, that I just need to wait :( how many 6 blocks for new stakebalance?
Rob what changes was made in 1103?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on March 07, 2018, 03:25:20 PM
Hi, what's  wrong in my case? > 50000 in my wallet, but with zero TaskWeight and zero UTXOWeight, StakeBalance is 0.

Code: [Select]
# biblepay-cli getblockchaininfo
{
  "chain": "main",
  "blocks": 33446,
  "headers": 33446,
  "bestblockhash": "2ec8d52a70e382beb1bd0c5181f68581534799042e86112db6896a0468a38809",

Code: [Select]
# biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 50001.99963080,

Code: [Select]
# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422349,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC",
  "fe553a955f0e21d46724858870014cbe_RAC": 3283.5,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 3283.5,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Code: [Select]
# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 03:29:00 PM
Hi, what's  wrong in my case? > 50000 in my wallet, but with zero TaskWeight and zero UTXOWeight, StakeBalance is 0.

Code: [Select]
# biblepay-cli getblockchaininfo
{
  "chain": "main",
  "blocks": 33446,
  "headers": 33446,
  "bestblockhash": "2ec8d52a70e382beb1bd0c5181f68581534799042e86112db6896a0468a38809",

Code: [Select]
# biblepay-cli getwalletinfo
{
  "walletversion": 61000,
  "balance": 50001.99963080,

Code: [Select]
# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422349,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC",
  "fe553a955f0e21d46724858870014cbe_RAC": 3283.5,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 3283.5,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Code: [Select]
# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 0
}

Did you check to see if the coins were in BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 03:31:50 PM


Thanks mike. Should I be zapping all 3 wallets or just PoDC one?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 03:33:48 PM
Thanks mike. Should I be zapping all 3 wallets or just PoDC one?

i zapped all of mine just to be sure.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 07, 2018, 03:34:49 PM
Wait 5 blocks, then close and restart your wallet. Run exec getboincinfo again and we'll go from there.

Done. Nothing 6 blocks later.


13:33:45

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422349,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


13:33:54

getblockcount


13:33:54

33447
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 03:35:41 PM
i zapped all of mine just to be sure.

Awesome, thanks. I just realised that I have some addnodes in my config. This was from my old PoBH wallet. But some of these nodes could be on different chains?

What addnode addresses should I have in my config?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 03:36:17 PM
Done. Nothing 6 blocks later.


13:33:45

{
  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422349,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


13:33:54

getblockcount


13:33:54

33447

OK, now try exec associate email pass.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 03:38:09 PM
Awesome, thanks. I just realised that I have some addnodes in my config. This was from my old PoBH wallet. But some of these nodes could be on different chains?

What addnode addresses should I have in my config?

My config:
rpcuser=aaa
rpcpassword=xxx
rpcport=9998
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
logtimestamps=1
maxconnections=256
addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=1
polpercentage=50
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 07, 2018, 03:40:27 PM
OK, now try exec associate email pass.

RPC Error
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 07, 2018, 03:42:02 PM
RPC Error

Ah... then when I run it again it says.

 "Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

So basically, the first command produced an error, but running exec a second time assumes that the first command was successful. What is an RPC error anyways?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 03:43:40 PM
Ah... then when I run it again it says.

 "Results": "A DCBTX was advertised less then 5 blocks ago. Please wait a full 5 blocks for your DCBTX to enter the chain."

So basically, the first command produced an error, but running exec a second time assumes that the first command was successful. What is an RPC error anyways?

go into biblepaycore and look at the debug file, what does it say when you associate?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 03:55:26 PM
We'll figure this out together, even if I have to add another argument to podcupdate.
First though could you please restart with -zapwallettxes, and check your stakebalance and resend you podcupdate again?
Lets see if that fixes it- also it takes 6 confirms for the wallet to memorize the utxoweight.

I had the same issue as Orbis, tried this, and now it's fine :)

Code: [Select]
22:52:43

exec getboincinfo


22:52:44

{
  "Command": "getboincinfo",
  "CPID": "d9b22fccfae5582d4ee7838883aaa3cf",
  "Address": "BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD",
  "CPIDS": "d9b22fccfae5582d4ee7838883aaa3cf;",
  "CPID-Age (hours)": 422349,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "d9b22fccfae5582d4ee7838883aaa3cf_ADDRESS": "BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD",
  "d9b22fccfae5582d4ee7838883aaa3cf_RAC": 10356.26,
  "d9b22fccfae5582d4ee7838883aaa3cf_TEAM": 15044,
  "d9b22fccfae5582d4ee7838883aaa3cf_TaskWeight": 100,
  "d9b22fccfae5582d4ee7838883aaa3cf_UTXOWeight": 100,
  "Total_RAC": 10356.26,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 07, 2018, 04:05:09 PM
go into biblepaycore and look at the debug file, what does it say when you associate?

Is this the right section of the debug? I ran a search for associate and this is what I came up with.
Also, perhaps I missed a step? I followed Togo's guide for Windows. I set up a Rosetta@Home account and I can login with that email/password to their website.
The CPID below doesn't seem to match the one on my Rosetta account.

2018-03-07 21:33:28 GUI: QObject::connect: No such slot DistributedComputingDialog::clicked() in qt/distributedcomputingdialog.cpp:57
2018-03-07 21:33:28 GUI: QObject::connect:  (sender name:   'btnAssociate')
2018-03-07 21:33:28 GUI: QObject::connect:  (receiver name: 'DistributedComputingDialog')
2018-03-07 21:33:28 . model set .
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:35:56 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=144.202.64.156:40000
2018-03-07 21:36:01 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=104.238.158.39:40000
2018-03-07 21:38:09 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.216.160:40000
2018-03-07 21:38:24 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.218.12:40000
2018-03-07 21:38:37 CGovernanceManager::ProcessVote -- Unknown parent object , MN outpoint = f0db4fbdb37c627d55c83fb4bba953b0b01b80a996f86010d02a65a42a8192bc-1, governance object hash = 14ec3b00c46a8f1090be5bc46100e5df547f5e9ed6c3cba8a75ca72b4a9ef572
2018-03-07 21:39:34 RPC error
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- creating birth, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- update empty, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::ProcessTxLockRequest -- accepted, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on March 07, 2018, 04:06:03 PM
Did you check to see if the coins were in BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC?

They were  not :) Moved to that address (https://biblepay-explorer.org/address/BPzKKaUa2yXDufhd1YchEZDHY7aSLrvmyC), but  stakebalance is still 0, "PODCUpdate": returns "Unable to create PODC UTXO::Balance too low."
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 04:06:30 PM
So I know some of you with 0 utxo weight are getting nervous, but have no fear, we have 24 hours before the first PODC superblock to work this out.

There is a rule in the wallet that says : If a PODC Update was sent within the last 24 hours and it appears to have valid tasks in it, dont resend a new one (even if the user executes exec podcupdate).

So in light of all these inability to control new update issues, I am putting in a feature now so you can type 'exec podcupdate force'.

This should allow those who are stuck to pull out of the rut.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 04:06:54 PM
Is this the right section of the debug? I ran a search for associate and this is what I came up with.
Also, perhaps I missed a step? I followed Togo's guide for Windows. I set up a Rosetta@Home account and I can login with that email/password to their website.
The CPID below doesn't seem to match the one on my Rosetta account.

2018-03-07 21:33:28 GUI: QObject::connect: No such slot DistributedComputingDialog::clicked() in qt/distributedcomputingdialog.cpp:57
2018-03-07 21:33:28 GUI: QObject::connect:  (sender name:   'btnAssociate')
2018-03-07 21:33:28 GUI: QObject::connect:  (receiver name: 'DistributedComputingDialog')
2018-03-07 21:33:28 . model set .
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:35:56 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=144.202.64.156:40000
2018-03-07 21:36:01 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=104.238.158.39:40000
2018-03-07 21:38:09 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.216.160:40000
2018-03-07 21:38:24 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.218.12:40000
2018-03-07 21:38:37 CGovernanceManager::ProcessVote -- Unknown parent object , MN outpoint = f0db4fbdb37c627d55c83fb4bba953b0b01b80a996f86010d02a65a42a8192bc-1, governance object hash = 14ec3b00c46a8f1090be5bc46100e5df547f5e9ed6c3cba8a75ca72b4a9ef572
2018-03-07 21:39:34 RPC error
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- creating birth, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- update empty, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::ProcessTxLockRequest -- accepted, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000

I'm not sure, is your wallet unlocked and more then 1 BBP?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 04:09:24 PM
Is this the right section of the debug? I ran a search for associate and this is what I came up with.
Also, perhaps I missed a step? I followed Togo's guide for Windows. I set up a Rosetta@Home account and I can login with that email/password to their website.
The CPID below doesn't seem to match the one on my Rosetta account.

2018-03-07 21:33:28 GUI: QObject::connect: No such slot DistributedComputingDialog::clicked() in qt/distributedcomputingdialog.cpp:57
2018-03-07 21:33:28 GUI: QObject::connect:  (sender name:   'btnAssociate')
2018-03-07 21:33:28 GUI: QObject::connect:  (receiver name: 'DistributedComputingDialog')
2018-03-07 21:33:28 . model set .
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:34:56  VerifyDistributedBurnTransaction::PASS for CPID A64253121D79782C27CFAA3429412A64
2018-03-07 21:35:56 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=144.202.64.156:40000
2018-03-07 21:36:01 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=104.238.158.39:40000
2018-03-07 21:38:09 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.216.160:40000
2018-03-07 21:38:24 CMasternodeBroadcast::Update -- Got UPDATED Masternode entry: addr=45.32.218.12:40000
2018-03-07 21:38:37 CGovernanceManager::ProcessVote -- Unknown parent object , MN outpoint = f0db4fbdb37c627d55c83fb4bba953b0b01b80a996f86010d02a65a42a8192bc-1, governance object hash = 14ec3b00c46a8f1090be5bc46100e5df547f5e9ed6c3cba8a75ca72b4a9ef572
2018-03-07 21:39:34 RPC error
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- creating birth, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::CreateTxLockCandidate -- update empty, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31 CInstantSend::ProcessTxLockRequest -- accepted, txid=cbc13a395ee8925a48cfa2781cb32734da42490945fcffe2b8c8f0b1a9d503f3
2018-03-07 21:40:31  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000


Hmm, I think your the first guy to experience this one , interesting.

Before I comment, could you please ensure wallet is unlocked, has a balance in 'exec stakebalance', and you are able to send money to yourself with this command:

sendtoaddress your_bbp_address 1

?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 04:12:22 PM
Hi guys,
Woke up this morning excited to see how we go today!

Lot's of posts! Can I please ask the following for clairty's sake:

1. So it looks like things should change when we reach block 33440? I see Alex's explorer is past that but Togo's not yet. Do we know which one will change to PoDC?

2. I see there is a leisure upgrade available. What are the changes? Should I be updating to this for controller wallet, Sanctuary wallet, PoDC wallet?

3. Should I be doing -zapwallettxes  (now or later) for controller wallet, Sanctuary wallet, PoDC wallet?

4. Anything else I should be doing now?

Many thanks

Welcome back Luke!

1. So it looks like things should change when we reach block 33440? I see Alex's explorer is past that but Togo's not yet. Do we know which one will change to PoDC?

->  Were still ensuring this PODC chain has integrity,  we should know within 25 more blocks or so that it appears solid.  Then we can ask Togo if hes on the same chain as us.


2. I see there is a leisure upgrade available. What are the changes? Should I be updating to this for controller wallet, Sanctuary wallet, PoDC wallet?
->  Actually this leisure is just a couple small items to show more info in exec podcupdate, dont worry about it now, because Im going to be adding another option now for exec podcupdate....  Sancs do not need to upgrade.


3. Should I be doing -zapwallettxes  (now or later) for controller wallet, Sanctuary wallet, PoDC wallet?
-> Only if you have orphaned transactions in your wallet.


4. Anything else I should be doing now?
-> Just check exec getboincinfo to ensure you have full weight on both.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 07, 2018, 04:14:29 PM
OK. Just tested the send to myself and it seems to work as a PrivateSend Collateral Payment.
I think my mistake was that my wallet was locked.
I didn't realize that when you put in your password upon opening the Biblepay Core, that it didn't unlock the wallet. I had to click through Settings to unlock and then punch in the password again.
I just tried running another associate, but I'll have to wait for 5 blocks until the last DXBTX clears.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Alex on March 07, 2018, 04:15:53 PM
There are a lot of things in certain niche businesses, such as Crypto, that differ from industry standard and run of the mill development.  This is called "domain knowledge".  If Im the leader of the group and hire 5 devs to work with me, and want to hold daily scrum meetings, and I tell you what a certain term means for our business, then its your responsibility to use it - so we can communicate in a more efficient way.  Its not your job to argue with the head of development about things, thats non productive and is a net negative - it also wastes everyones elses time, and is embarassing.

Next, I know its true that certain soft rules - such as a protocol version - when implemented in a way where another node will hang up and refuse to comunicate based on that version, is not a hard rule, and it can be circumvented by a hacker.  But apparently what you have a hard time grasping, is there are also hard rules in the client, that have been programmed by both Dash and Me in both of my communities, that do enforce soft rules.  For example, we have a piece of code in our biblepay version right now that adds up what percent of blocks were solved by prior versions in the last 100 in the chain, and it does take into account the protocol version.  I could have easily enabled that feature and allowed the chain to fork if *any* blocks were solved by a version below the greatest in the chain.  I didnt, because I felt at the time we would have a smoother transition to the cutover block by letting everyone play.  You need to understand every algorithm in the code before making misleading statements to our community.    I am still maintaining that anyone who deliberately compiles a fraudulent version and detracts from the prod experience is a dangerous and semi-untrustworthy individual, when we are all here trying to get past the block number without forks and as much integrity as possible.

1)  I'm not working for you. I'm the one who told about botnets and the potential issues that they were/are causing to cpu coins so I'm even the one who first brought up that term. The first example I brought was Vertcoin. If you go and use a term that has an agreed definition by everyone, especially in IT, CS, etc., and slap on it something that has a totally different meaning at your convenience, then no wonder there are communication issues. I think you're wrong on that point.

2) I don't think you seem to understand that the wold is not there to please you and be honest. I also don't think you understand what has been talked before with implementation of a specific protocol being different from the protocol itself. And no..making another implementation is not "fraudulent". There are tons of implementation of bitcoin, ethereum, doge.., etc and this is to be expected when a coin starts to gain some attention.

We are talking about a financial ledger. There is money involved in this. Of course people will try to "hack" it, find exploits, gain any advantage.
We are in the business of security, that's why there is big money involved in blockchain...not just "making it work" and hoping for the best. I do that with my hair in the morning, not financial systems.

I stand my ground on saying that a version number cannot be enforced the way you want and therefore you shouldn't rely on it as you're literally just checking for a number that anyone can advertise/change without changing anything else.

if I had a different miner implementation...I would just have to change that number to match to w/e it is that you're looking for. Same with protocol version, etc. Can be done in 5 seconds and you will never know about it unless it's a version number you're not expecting (Ex: If I was suddenly advertising that my blocks were mined with version 0.4 right now when obviously it doesn't look correct).

@everyone
My BX is on the chain with the most work for now (has the most hashpower). This is the chain you will sync to if you sync any new wallet right now as this is how it chooses the active chain unless you try to do some tricky things (ban peers with the higher chain, only connecting to peer with the lowest chain, putting checkpoints, etc.). I will adjust it if this changes. For now I guess it lets you look and monitor both chains.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 04:19:17 PM
Welcome back Luke!

1. So it looks like things should change when we reach block 33440? I see Alex's explorer is past that but Togo's not yet. Do we know which one will change to PoDC?

->  Were still ensuring this PODC chain has integrity,  we should know within 25 more blocks or so that it appears solid.  Then we can ask Togo if hes on the same chain as us.


2. I see there is a leisure upgrade available. What are the changes? Should I be updating to this for controller wallet, Sanctuary wallet, PoDC wallet?
->  Actually this leisure is just a couple small items to show more info in exec podcupdate, dont worry about it now, because Im going to be adding another option now for exec podcupdate....  Sancs do not need to upgrade.


3. Should I be doing -zapwallettxes  (now or later) for controller wallet, Sanctuary wallet, PoDC wallet?
-> Only if you have orphaned transactions in your wallet.


4. Anything else I should be doing now?
-> Just check exec getboincinfo to ensure you have full weight on both.

Awesome thanks Rob.

getblockhash 33445
Code: [Select]
201ce2c68c5d520873037429fa644ca1180569a059f052621030e7152f4c5fd3
So I seem to be on the correct chain

exec stakebalance
Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 110009

So I have plenty of stake

exec getboincinfo
Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422350,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq",
  "8f273b30f8e0a298ed26e242762df701_RAC": 40580.95,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 40580.95,


TaskWeight is good!
But still confused as to why UTXOWeight is not 100.

Thanks!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 07, 2018, 04:27:13 PM
I took down the backup block explorer temporarily to upgrade it to latest version 1.1.0.3
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 05:18:33 PM
I took down the backup block explorer temporarily to upgrade it to latest version 1.1.0.3
Wow you have 64 processor machines!?  Arent those $100 a day?

I think youll be #1 in the world!

Thanks for updating the BX.  Ive had half of my sancs crash today, and ironically what allowed me to bring them back is deleting peers.dat.  I have no idea why the peers.dat is 289 megs.    Unfortunately, the sanc on my large 8192 RAM node has not died yet; if it does ill run valgrind on it. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 05:29:59 PM
Hi Rob, since my UTXO is stuck at 25, should I try downloading the new version and  "exec podcupdate force"?
 :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 05:32:28 PM
Hi Rob, since my UTXO is stuck at 25, should I try downloading the new version and  "exec podcupdate force"?
 :D

Yes, please try 'exec stakebalance' first, then set polpercentage to the correct percent, then grab the latest version, then after it starts and wallet is unlocked, try :

exec podcupdate true

The true = force, then double click on the sent Tx, and see if its high enough to make UTXO =100 (50K).

Good luck.


Edit: windows is compiling but almost finished.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 05:36:51 PM
We'll figure this out together, even if I have to add another argument to podcupdate.
First though could you please restart with -zapwallettxes, and check your stakebalance and resend you podcupdate again?
Lets see if that fixes it- also it takes 6 confirms for the wallet to memorize the utxoweight.
This fix my problem. Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 05:39:45 PM
Yes, please try 'exec stakebalance' first, then set polpercentage to the correct percent, then grab the latest version, then after it starts and wallet is unlocked, try :

exec podcupdate true

The true = force, then double click on the sent Tx, and see if its high enough to make UTXO =100 (50K).

Good luck.


Edit: windows is compiling but almost finished.

Awesome
Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 110009

Config file
Code: [Select]
addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network 
gen=1
genproclimit=1
polpercentage=100

I'll update now.
Thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 07, 2018, 05:43:04 PM
Wow you have 64 processor machines!?  Arent those $100 a day?
I think youll be #1 in the world!

Its a risky strategy, Im using spot instances,
all of them got terminated unexpectedly last night too, LOL poof gone,

Most of the motivation was that Slovakia reached #1 in our leaderboard
and I couldnt stand for that, I had to beat him LOL
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 05:49:54 PM
This fix my problem. Thanks.

Great, but let me take this opportunity for a sanity check, is your CPID in my UTXO list now with correct weight?

Code: [Select]


17:49:12

exec datalist utxoweight


17:49:12

{
  "DataList": "UTXOWEIGHT",
  "04FBA56D89A5EB38B1B82F8A6240132C (03-07-2018 22:34:41)": "100",
  "1414175AC4EA3DFBB9FB7CAF13540319 (03-07-2018 22:51:04)": "25",
  "4004B7FEC94751F61FE9135977BAC553 (03-07-2018 22:34:41)": "75",
  "6785DED1F65063EF8F01F42DEB31CF1D (03-07-2018 21:47:25)": "75",
  "6BCD1F25DC07679DB5AD812A012DF1A4 (03-07-2018 20:37:28)": "0",
  "7C9264559FEF3C1C689EE9FC3FF42494 (03-07-2018 20:53:25)": "60",
  "84D803E4D82D3BDCDF8E2AB601E93E20 (03-07-2018 20:37:28)": "100",
  "8735CFE64D964416DBA6015EB414CF7E (03-07-2018 20:01:05)": "60",
  "8F273B30F8E0A298ED26E242762DF701 (03-07-2018 20:37:28)": "25",
  "93138F032BDD027FA3246B48BB715A77 (03-07-2018 22:51:04)": "100",
  "940552F602F67A3CF57A452438F36EE9 (03-07-2018 20:37:28)": "25",
  "962B0D76DFB35F07B73F81A67FFC28B1 (03-07-2018 23:06:25)": "0",
  "96892EC0FC8A2710FA84F26C9C84CD3E (03-07-2018 20:01:05)": "60",
  "982538340112287ED60723499ADFEB4B (03-07-2018 22:34:41)": "60",
  "A64253121D79782C27CFAA3429412A64 (03-07-2018 22:18:49)": "0",
  "A9420A038E44750C69CA4497FE08C2A9 (03-07-2018 20:01:05)": "60",
  "B1AFC0756AB888F55D90AB39396EA8B9 (03-07-2018 22:34:41)": "25",
  "CA895B47AACFFBDBF906201821AF2F9F (03-07-2018 20:37:28)": "50",
  "D4E56169934BF307F145C75BCB2896A2 (03-07-2018 20:01:05)": "25",
  "D9B22FCCFAE5582D4EE7838883AAA3CF (03-07-2018 20:37:28)": "100",
  "E1B188FAAD0052F0BE11B5DC0827AAA4 (03-07-2018 22:51:04)": "75",
  "E6CE50042187D4B285568D86EF458F32 (03-07-2018 20:01:05)": "75",
  "E7AE6ABD6284B05F3FD5F7C780E60BC7 (03-07-2018 20:37:28)": "100",
  "E94C1704C75F731F8BFDE303F08408EE (03-07-2018 20:37:28)": "60"
}



Thanks!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 05:55:16 PM
Its a risky strategy, Im using spot instances,
all of them got terminated unexpectedly last night too, LOL poof gone,

Most of the motivation was that Slovakia reached #1 in our leaderboard
and I couldnt stand for that, I had to beat him LOL
LOL, Country of Texas against Slovakia, my my, LOL.  Maybe you can pay a mechanical turk .50 cents an hour to keep those running.  JK.

Ill have to check those out.  It would be wild to rent one once a day if you had to analyze the global equities market - all historical black scholes - or something with very deep analysis and then let it get terminated.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 05:59:55 PM
When I run podcupdate, it says true but i don't see any transactions and nothing is being logged in the debug file. I did find this:

Code: [Select]
2018-03-07 23:35:50 CInstantSend::CreateTxLockCandidate -- new, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:50 CInstantSend::ProcessTxLockRequest -- accepted, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:50  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:50  CInstantSend::ProcessTxLockRequest successful
2018-03-07 23:35:50 TXLOCKREQUEST -- Transaction Lock Request accepted, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a, peer=5
2018-03-07 23:35:51 CInstantSend::CreateTxLockCandidate -- creating birth, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:51 CInstantSend::CreateTxLockCandidate -- update empty, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:51 CInstantSend::ProcessTxLockRequest -- accepted, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-07 23:35:51  CInstantSend::ProcessTxLockRequest successful
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-07 23:36:34  End To End CPID Verification Failed, Address does not match advertised public key for CPID 962b0d76dfb35f07b73f81a67ffc28b1, Advertised Addr B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw, Addr BCD2eNowB8Hw9WNFYACD3U3diGzP9tfniR UpdateTip: new best=01a9e26d99304c6f9fc8738323ab2a8d0f145496100adcef3baf44ab9a24f570  height=33455  log2_work=58.86502  tx=124107  date=2018-03-07 23:36:59 progress=1.000002  cache=0.1MiB(225tx)
2018-03-07 23:36:34 ProcessNewBlock : ACCEPTED

Do I need to re-associate?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 07, 2018, 06:00:59 PM
Great, but let me take this opportunity for a sanity check, is your CPID in my UTXO list now with correct weight?
Thanks!
Yes. I'm the first one :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:08:30 PM
When I run podcupdate, it says true but i don't see any transactions and nothing is being logged in the debug file. I did find this:

Code: [Select]
2018-03-07 23:35:50 CInstantSend::CreateTxLockCandidate -- new, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:50 CInstantSend::ProcessTxLockRequest -- accepted, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:50  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:50  CInstantSend::ProcessTxLockRequest successful
2018-03-07 23:35:50 TXLOCKREQUEST -- Transaction Lock Request accepted, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a, peer=5
2018-03-07 23:35:51 CInstantSend::CreateTxLockCandidate -- creating birth, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:51 CInstantSend::CreateTxLockCandidate -- update empty, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:51 CInstantSend::ProcessTxLockRequest -- accepted, txid=dd6eaee3390c57c2c94299bfe81dbb9a3bb2924719b18ca25b6c7d72136aac5a
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-07 23:35:51  CInstantSend::ProcessTxLockRequest successful
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-07 23:35:51  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-07 23:36:34  End To End CPID Verification Failed, Address does not match advertised public key for CPID 962b0d76dfb35f07b73f81a67ffc28b1, Advertised Addr B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw, Addr BCD2eNowB8Hw9WNFYACD3U3diGzP9tfniR UpdateTip: new best=01a9e26d99304c6f9fc8738323ab2a8d0f145496100adcef3baf44ab9a24f570  height=33455  log2_work=58.86502  tx=124107  date=2018-03-07 23:36:59 progress=1.000002  cache=0.1MiB(225tx)
2018-03-07 23:36:34 ProcessNewBlock : ACCEPTED

Do I need to re-associate?
Thats kind of wild, I think that error is someone is trying to forge the wrong cpid on block 33455, and it failed.

Anyway, I would just do the 'exec getboincinfo' and check that the address that shows up for the cpid, is one you own in your wallet- if it matches you dont have to reassociate.
But then I would grab the latest version and do the 'exec podcupdate true', that way the UTXO is forced in.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 06:09:46 PM
Ok so updated!
I am on linux qt, unlocked wallet

exec podcupdate true
Code: [Select]
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}

exec stakebalance
Code: [Select]
{
  "Command": "stakebalance",
  "StakeBalance": 110009
}


exec getboincinfo
Code: [Select]
"8f273b30f8e0a298ed26e242762df701_RAC": 41174.76,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 41174.76,


Hmmm, not sure what is going on. Should i try sending my coins from the wallet and then back in again?

Thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:20:44 PM
Ok so updated!
I am on linux qt, unlocked wallet

exec podcupdate true
Code: [Select]
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}

exec stakebalance
Code: [Select]
{
  "Command": "stakebalance",
  "StakeBalance": 110009
}


exec getboincinfo
Code: [Select]
"8f273b30f8e0a298ed26e242762df701_RAC": 41174.76,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 41174.76,


Hmmm, not sure what is going on. Should i try sending my coins from the wallet and then back in again?

Thanks


Hmm, how bout try polpercentage=90, just to see if the math of 100 is causing it to try to send more than the total including the tx fee?

EDIT: Also you can try 'sendtoaddress your_bbp_address 1' just to ensure it goes out successfully first.




Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 06:28:39 PM
Thats kind of wild, I think that error is someone is trying to forge the wrong cpid on block 33455, and it failed.

Anyway, I would just do the 'exec getboincinfo' and check that the address that shows up for the cpid, is one you own in your wallet- if it matches you dont have to reassociate.
But then I would grab the latest version and do the 'exec podcupdate true', that way the UTXO is forced in.

That doesn't appear to work either, I just downloaded the latest windows wallet also. There is nothing in debug after I ran the command, no new transactions either.

exec podcupdate true

{
  "Command": "podcupdate",
  "PODCUpdate": ""
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:31:43 PM
Ok, windows 1.1.0.4 is now deployed with the 'exec podcupdate true' (force) feature in.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:33:26 PM
That doesn't appear to work either, I just downloaded the latest windows wallet also. There is nothing in debug after I ran the command, no new transactions either.

exec podcupdate true

{
  "Command": "podcupdate",
  "PODCUpdate": ""
}

The empty string means no errors occurred.  Are you sure your txlist does not have a new tx?  You might have it sorted wrong.
Maybe try the zapwallettxes first, then do it, then sort txlist by Received descending, then look for it?

I just grabbed that win wallet and repaired mine ( I had a 50% weight and it just worked for me ).

If then all that doesnt work then lets see if you have a debug entry.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 06:39:16 PM

Hmm, how bout try polpercentage=90, just to see if the math of 100 is causing it to try to send more than the total including the tx fee?

EDIT: Also you can try 'sendtoaddress your_bbp_address 1' just to ensure it goes out successfully first.

Thanks Rob.

I did that (and sent in another 10 BBP to my CPID address from my main wallet). Ran again

exec podcupdate true
Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Rob is it possible that this is an issue: My default wallet address is different to my CPID associated one?
When I was trying to help someone figure out the command to find an address balance i think I accidentally created a new one. Now when I type

getaccountaddress ""

I get a different address (still in my wallet) but different to the one assigned to my CPID.
Stake is in CPID address though.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 06:42:13 PM
The empty string means no errors occurred.  Are you sure your txlist does not have a new tx?  You might have it sorted wrong.
Maybe try the zapwallettxes first, then do it, then sort txlist by Received descending, then look for it?

I just grabbed that win wallet and repaired mine ( I had a 50% weight and it just worked for me ).

If then all that doesnt work then lets see if you have a debug entry.

OK, it finally worked after I upgraded the wallet to 1.1.0.4 and did zapwallettxes=1, not sure which one fixed it. Thanks!

When will the magnitude start going up?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 07, 2018, 06:46:46 PM
Thanks Rob.

I did that (and sent in another 10 BBP to my CPID address from my main wallet). Ran again

exec podcupdate true
Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Rob is it possible that this is an issue: My default wallet address is different to my CPID associated one?
When I was trying to help someone figure out the command to find an address balance i think I accidentally created a new one. Now when I type

getaccountaddress ""

I get a different address (still in my wallet) but different to the one assigned to my CPID.
Stake is in CPID address though.

It's not a well informed suggestion from my part, but did you already try the 'zapwallet' command? It solved my problems at least (had the same problem Orbis had, with the 'insufficient funds' error).

Anyway, I'm going to get some sleep now guys. It's been an exhilarating couple of days, but let's try and not make this a regular thing, haha!

Rob: thank you for all your hard work and perseverance.  Let's make Biblepay something to reckon with!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:55:55 PM
It's not a well informed suggestion from my part, but did you already try the 'zapwallet' command? It solved my problems at least (had the same problem Orbis had, with the 'insufficient funds' error).

Anyway, I'm going to get some sleep now guys. It's been an exhilarating couple of days, but let's try and not make this a regular thing, haha!

Rob: thank you for all your hard work and perseverance.  Let's make Biblepay something to reckon with!

Thanks, and have a good nights sleep.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:57:20 PM
OK, it finally worked after I upgraded the wallet to 1.1.0.4 and did zapwallettxes=1, not sure which one fixed it. Thanks!

When will the magnitude start going up?

Once the first superblock hits:  block 33620. 

That reminds me we need to test the testvote again, one minute.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 06:58:53 PM
It's not a well informed suggestion from my part, but did you already try the 'zapwallet' command? It solved my problems at least (had the same problem Orbis had, with the 'insufficient funds' error).

Anyway, I'm going to get some sleep now guys. It's been an exhilarating couple of days, but let's try and not make this a regular thing, haha!

Rob: thank you for all your hard work and perseverance.  Let's make Biblepay something to reckon with!

Thanks! I just tried and upfortnately I still have UTXO weight 25 and exec podcupdate true giving

Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Should I reassociate my cpid again? Totally delete wallet and start again?

EDIT: Oh I see there is a new version. I will try updating to that first
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 06:59:20 PM
Great news, block 33460 & 33461 were both signed by CPIDS!

CPID 7c9264559fef3c1c689ee9fc3ff42494 was awarded for our first PODC - CPID heat payment: 555 BBP!  Congrats!


showblock 33460 to see the blocks CPID info.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 07:02:16 PM
Thanks! I just tried and upfortnately I still have UTXO weight 25 and exec podcupdate true giving

Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."

Should I reassociate my cpid again? Totally delete wallet and start again?

EDIT: Oh I see there is a new version. I will try updating to that first

Luke- I have to take a look at the code that actually spends the podcupdate.  In the mean time, you said you had two addresses one unlabled and one default I think, but to clarify, ensure the 'getboincinfo' receive addresses is one actually contained in your File | Receiving Addresses list?

If so you do not have to reassociate.  I would try instantsending your balance back to your default address, and then retry the exec podcupdate.

Ill check that "spend" code asap to see if this is going to be a nuisance.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 07:03:29 PM
Luke- I have to take a look at the code that actually spends the podcupdate.  In the mean time, you said you had two addresses one unlabled and one default I think, but to clarify, just ensure the actual wallet.dat has the receiveing address corresponding to your CPID?  Another words exec getboincinfo should show a row for the receive address.  Ensure that is one of that particular wallet.dat receiving address.

If so you do not have to reassociate.  I would try instantsending your balance back to your default address, and then retry the exec podcupdate.

Ill check that "spend" code asap to see if this is going to be a nuisance.

Thanks Rob. Just installing the new version then I will try those thing.
Thanks
Luke
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 07:09:22 PM
Luke- I have to take a look at the code that actually spends the podcupdate.  In the mean time, you said you had two addresses one unlabled and one default I think, but to clarify, ensure the 'getboincinfo' receive addresses is one actually contained in your File | Receiving Addresses list?

If so you do not have to reassociate.  I would try instantsending your balance back to your default address, and then retry the exec podcupdate.

Ill check that "spend" code asap to see if this is going to be a nuisance.
Wow it was a quick update.

exec getboincinfo
Code: [Select]
Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD...etc etc",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
etc etc


My receiving addresses are in the attachment. I assume this is correct?
I will send myself some coins now

Thanks :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 07:21:41 PM
Wow it was a quick update.

exec getboincinfo
Code: [Select]
Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "BLLmyTDgsCtD...etc etc",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
etc etc


My receiving addresses are in the attachment. I assume this is correct?
I will send myself some coins now

Thanks :)

Yeah, your receive address on file matches the boinc address, so that means you can sign for that CPID.

So it must be a matter of the wallet picking the wrong spending account, please try sending the money into the top address then resending the podcupdate, lets see if that works.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 07:24:29 PM
So we are going relatively good now, but I found an issue.  Im looking at the exec testvote output on my sanc, and on the bright side, its generally good and 3 people already voted for it (it needs 5 votes minimum in prod which Im sure it would get eventually), but anyway, the other good news is most of the cpids look like they will have the correct magnitude (we can see the upcoming magnitude by looking in the /SAN directory at the magnitude file), (this is created by our sanc btw), anyway there is a problem with Togo.

Togos magnitude = 0.  It looks like its because his tasks are showing as "tampered" with.  I will look into this issue now.  Oh we were on a roll! LOL.  We'll figure it out before tomorrow gets here.

This might mean a system wide update is required.  Let me debug...


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 07, 2018, 07:34:29 PM
Just updated to 1104. Can someone tell me if all is correct?

getmininginfo
Code: [Select]
19:29:01

getmininginfo


19:29:01

{
  "blocks": 33386,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 0,
  "difficulty_pow": 0.889502687442315,
  "difficulty": 0,
  "errors": "",
  "genproclimit": 1,
  "networkhashps": 73878209.24980666,
  "hashps": 57.82132996155136,
  "minerstarttime": "03-08-2018 01:26:25",
  "hashcounter": 8963,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "miningpulse": 24,
  "poolmining": true,
  "pool_url": "http://pool.biblepay.org",
  "poolmining_use_ssl": false
}

exec getboincinfo
Code: [Select]
19:33:40

exec getboincinfo


19:33:41

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422353,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2726.94,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2726.94,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: togoshigekata on March 07, 2018, 07:38:41 PM
Togos magnitude = 0.  It looks like its because his tasks are showing as "tampered" with.  I will look into this issue now.

Uh oh!
a few days ago
I overclocked one machine and caused cpu to become unstable, and got a computation error in BOINC, so I aborted that task,
That same machine was also not running for a few days and I had to abort some tasks that were past due

Only thing I can think of recently in the past day
is that I have "merged" some aws machines in BOINC website (because the old ones got terminated)
hope that is not causing issues

I basically just run 4 linux commands and never touch these machines again LOL

So far today I:
1. Sent coins for CPID Burn and Staking
2. Performed CPID Burn through GUI
3. Added polpercentage to config

Were there any commands I needed to run?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 07:43:31 PM
Uh oh!
a few days ago
I overclocked one machine and caused cpu to become unstable, and got a computation error in BOINC, so I aborted that task,
That same machine was also not running for a few days and I had to abort some tasks that were past due

Only thing I can think of recently in the past day
is that I have "merged" some aws machines in BOINC website (because the old ones got terminated)
hope that is not causing issues

I basically just run 4 linux commands and never touch these machines again LOL

So far today I:
1. Sent coins for CPID Burn and Staking
2. Performed CPID Burn through GUI
3. Added polpercentage to config

Were there any commands I needed to run?
Thats cool, the system needs to be resilient enough to handle that anyway.  Its supposed to look at the total picture, and if it finds 3 errors out of 100, keep you in the top bracket, etc, so there is something obviously wrong with it, I am writing a command to pull the data now, right now no commands exist.

I would have expected you to be at 95% or something even if there were errors, Ill get to the bottom of it.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 08:18:15 PM
Yeah, your receive address on file matches the boinc address, so that means you can sign for that CPID.

So it must be a matter of the wallet picking the wrong spending account, please try sending the money into the top address then resending the podcupdate, lets see if that works.

Hi Rob,

before I saw you posted this I had already sent a transaction to myself to my CPID address.

After 6 confirmations:

Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "true"

Great!

Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 109919

looking good

Code: [Select]
"8f273b30f8e0a298ed26e242762df701_RAC": 41662.59,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 41662.59,

Oh so close!
So UTXO is still 25. Should I just give it a bit of time, or should I try sending to the other address?

Thanks!
Luke
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:19:40 PM
Thats cool, the system needs to be resilient enough to handle that anyway.  Its supposed to look at the total picture, and if it finds 3 errors out of 100, keep you in the top bracket, etc, so there is something obviously wrong with it, I am writing a command to pull the data now, right now no commands exist.

I would have expected you to be at 95% or something even if there were errors, Ill get to the bottom of it.


The problem is the current sanctuary magnitude system can only handle up to 512 task verifications per CPID before it causes an internal calculation error.  I have fixed the problem by chunking it.   

This is going to require a mandatory for all sancs.

Im going to take advantage of this mandatory upgrade and insert a checkpoint, and also do a hard check on the client version in each block.

Ill announce the new version in 30 mins on the main thread.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:20:58 PM
Hi Rob,

before I saw you posted this I had already sent a transaction to myself to my CPID address.

After 6 confirmations:

Code: [Select]
"Command": "podcupdate",
  "PODCUpdate": "true"

Great!

Code: [Select]
"Command": "stakebalance",
  "StakeBalance": 109919

looking good

Code: [Select]
"8f273b30f8e0a298ed26e242762df701_RAC": 41662.59,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 100,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 25,
  "Total_RAC": 41662.59,

Oh so close!
So UTXO is still 25. Should I just give it a bit of time, or should I try sending to the other address?

Thanks!
Luke

Luke,
There is a secret command, this is only good for internal use not network use, try this:
'exec memorizeprayers', 'exec datalist utxoweight'.  The memorizeprayers forces the client to load any unconfirmed tx into memory (as if 6 went by), let me know if it goes up to 100 after that.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:30:19 PM

Biblepay 1.1.0.5
Mandatory Upgrade for Sanctuaries
Leisure Upgrade for Users


- Add checkpoint at 33460 to prevent forking and lock in PODC consensus system
- Add checkblock to verify all 33460+ PODC blocks were generated by v1.1.0.0+
- Fix Task Verification Error in Sanctuary Quorum affecting Magnitude Calculation for Large CPIDs

** Windows is still building, this is a notification for all linux nodes **
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 08:33:41 PM
Luke,
There is a secret command, this is only good for internal use not network use, try this:
'exec memorizeprayers', 'exec datalist utxoweight'.  The memorizeprayers forces the client to load any unconfirmed tx into memory (as if 6 went by), let me know if it goes up to 100 after that.

Hi Rob.
Unfortunately I am still on 25 for UTXO weight.
Is there a way to delete the other wallet receiving address?
 
Thanks

EDIT: just for clarity, I did the memorizeprayers command
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:34:07 PM
Rob, not sure if I am having the same problem but here it goes:

Code: [Select]
exec dcc
{
  "Command": "dcc",
  "Success": true,
  "Error": ""
}

exec datalist utxoweight
{
  "DataList": "UTXOWEIGHT",
  "E94C1704C75F731F8BFDE303F08408EE (03-08-2018 00:43:05)": "60",

}

exec datalist taskweight
{
  "DataList": "TASKWEIGHT",
  "E94C1704C75F731F8BFDE303F08408EE (03-08-2018 02:20:23)": "0",
}

But getboincinfo is still showing:

exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422354,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 42216.08,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 60,
  "Total_RAC": 42216.08,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

So I did:

exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 147918
}

exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": ""
}

Transaction details:
Status: 1/unconfirmed, broadcast through 6 nodes
Date: 3/7/2018 21:24
Source: PODC-Update
Total debit: -16 904.96785832 Biblepay
Total credit: 16 904.96785832 Biblepay
Transaction fee: -0.00517320 Biblepay
Net amount: -0.00517320 Biblepay

I have polpercentage=50

My task weight was 100% a few hours ago but now its 0 and my UTXO weight has been decreasing. The staking amount doesn't seem to be enough.

p.s. I just mined a block, reward 556 BBP.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:41:26 PM
Wow, #1.

https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=1914608
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:46:25 PM
Wow, #1.

https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=1914608
He could probably weld a bridge together or fly a 737 with that much power (in watts), wow.
I hope he doesnt find out about BBP too fast, unless he buys some Sancs from the open market.
I wonder what team he is on.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:47:30 PM
He could probably weld a bridge together or fly a 737 with that much power (in watts), wow.
I hope he doesnt find out about BBP too fast, unless he buys some Sancs from the open market.
I wonder what team he is on.

No team apparently. I wonder if it's owned by some school but I wonder why they don't advertise it.

Updated linux Sanctuary just now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:50:10 PM
Rob, not sure if I am having the same problem but here it goes:

Code: [Select]
exec dcc
{
  "Command": "dcc",
  "Success": true,
  "Error": ""
}

exec datalist utxoweight
{
  "DataList": "UTXOWEIGHT",
  "E94C1704C75F731F8BFDE303F08408EE (03-08-2018 00:43:05)": "60",

}

exec datalist taskweight
{
  "DataList": "TASKWEIGHT",
  "E94C1704C75F731F8BFDE303F08408EE (03-08-2018 02:20:23)": "0",
}

But getboincinfo is still showing:

exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422354,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 42216.08,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 60,
  "Total_RAC": 42216.08,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

So I did:

exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 147918
}

exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": ""
}

Transaction details:
Status: 1/unconfirmed, broadcast through 6 nodes
Date: 3/7/2018 21:24
Source: PODC-Update
Total debit: -16 904.96785832 Biblepay
Total credit: 16 904.96785832 Biblepay
Transaction fee: -0.00517320 Biblepay
Net amount: -0.00517320 Biblepay

I have polpercentage=50

My task weight was 100% a few hours ago but now its 0 and my UTXO weight has been decreasing. The staking amount doesn't seem to be enough.

p.s. I just mined a block, reward 556 BBP.

I think in this case its best to go into coin control, and wait til you have 6+ confirms available for the whole 100K of UTXO's,   then set polpercentage=90, and do it again, im guessing when you sent it the last time, at least one of your inputs didnt have 6 depth in the chain (you can see the depth in coin control).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:51:53 PM
No team apparently. I wonder if it's owned by some school but I wonder why they don't advertise it.

Updated linux Sanctuary just now.

If you want to test your Sancs health with Togos cpid his cpid is 9313, you can type 'exec dcc', and when its done go to bash, cd /SAN, then 
cat filtered | grep 9313 -A10 -B10 and take a look at Togo's <taskweight> and it should be up to 100.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:52:36 PM
I think in this case its best to go into coin control, and wait til you have 6+ confirms available for the whole 100K of UTXO's,   then set polpercentage=90, and do it again, im guessing when you sent it the last time, at least one of your inputs didnt have 6 depth in the chain (you can see the depth in coin control).

I'll do that. Why set a percentage anyways? What happens if I remove polpercentage?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:54:42 PM
Hi Rob.
Unfortunately I am still on 25 for UTXO weight.
Is there a way to delete the other wallet receiving address?
 
Thanks

EDIT: just for clarity, I did the memorizeprayers command

Can you please double click on the PODC Update transaction it sent and paste the txid? 

I dont think switching CPID (addresses) will help, it sounds as if yours needs -zapwallettxes first, then wait for 6 confirms, then send all at once?
This is strange  - I dont mind putting more diagnostic harnesses in exec podcupdate, but I think we will figure this out pretty easily.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 08:56:01 PM
I'll do that. Why set a percentage anyways? What happens if I remove polpercentage?
If you remove it uses 10%.  We have it in case you have a 30 Million balance or something, as some people may freak out if it sends out all your money every time it stakes :).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:56:56 PM
If you want to test your Sancs health with Togos cpid his cpid is 9313, you can type 'exec dcc', and when its done go to bash, cd /SAN, then 
cat filtered | grep 9313 -A10 -B10 and take a look at Togo's <taskweight> and it should be up to 100.

Code: [Select]
cat filtered | grep 9313 -A10 -B10
 <name>strayapple</name>
 <id>1981219</id>
<utxoweight>75</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

</user>
<user>

 <teamid>15044</teamid>
 <url>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs</url>
 <cpid>93138f032bdd027fa3246b48bb715a77</cpid>
 <expavg_time>1520462480.639447</expavg_time>
 <expavg_credit>80933.641932</expavg_credit>
 <total_credit>1254458.742816</total_credit>
 <create_time>1517967718</create_time>
 <country>United States</country>
 <name>togoshigekata</name>
 <id>1981221</id>
<utxoweight>100</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 08:57:34 PM
If you remove it uses 10%.  We have it in case you have a 30 Million balance or something, as some people may freak out if it sends out all your money every time it stakes :).

Oh I see, but why not just cap it at 50k?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 09:00:13 PM
Can you please double click on the PODC Update transaction it sent and paste the txid? 

I dont think switching CPID (addresses) will help, it sounds as if yours needs -zapwallettxes first, then wait for 6 confirms, then send all at once?
This is strange  - I dont mind putting more diagnostic harnesses in exec podcupdate, but I think we will figure this out pretty easily.
Hi Rob, my wallet is updating but I got it from here
https://biblepay-explorer.org/address/BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM

38675844148c7aac09169282d280acdd7aeca210b1630df9e29104cbac1e24a3

Many thanks!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 09:02:23 PM
Oh I see, but why not just cap it at 50k?
We could possibly do that, the engine is still 95% compatible with staking, thats where all the rules came from when I made it for POL, as it searches for Up to the % target- and keeps track of the age, but now we dont use age currently, so yes if we feel pretty confident we wont need age we could probably do that.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 09:05:12 PM
Hi Rob, my wallet is updating but I got it from here
https://biblepay-explorer.org/address/BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM

38675844148c7aac09169282d280acdd7aeca210b1630df9e29104cbac1e24a3

Many thanks!

Ok so wallet is updated and this is what I get:

Code: [Select]
Status: 436 confirmations
Date: 5/03/18 14:56
To: BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM
Debit: -1.00000000 Biblepay
Transaction fee: -0.00016180 Biblepay
Net amount: -1.00016180 Biblepay

Height: 33039
Difficulty: 0.000000
Time: 03-05-2018 02:22:28
Subsidy: 4910.5389

DCC: 8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0
Transaction ID: 7bc50d0e20c6d4aff221bb5cc6ef5450431faf3ac291d4294f124c5b9f8d0023-000



Debug information

Debit: -10.00000000 Biblepay
Credit: 8.99983820 Biblepay

Transaction:
CTransaction(hash=7bc50d0e20, ver=1, vin.size=1, vout.size=2, nLockTime=33038)
    CTxIn(COutPoint(c5546bac172f6f24018bdd8960d013b8772406db371b5ef9f015c0e9dada1578, 1), scriptSig=47304402200aa464a3be9a45, nSequence=4294967294)
    CTxOut(nValue=1.00000000, scriptPubKey=76a9144813c26f2846cfcde5d1cc62)
    CTxOut(nValue=8.99983820, scriptPubKey=76a914308deb678d8be06d32fdb952)

Inputs:

:)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 09:12:04 PM
Ok so wallet is updated and this is what I get:

Code: [Select]
Status: 436 confirmations
Date: 5/03/18 14:56
To: BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM
Debit: -1.00000000 Biblepay
Transaction fee: -0.00016180 Biblepay
Net amount: -1.00016180 Biblepay

Height: 33039
Difficulty: 0.000000
Time: 03-05-2018 02:22:28
Subsidy: 4910.5389

DCC: 8f273b30f8e0a298ed26e242762df701;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;BLLmyTDgsCtD2gC4dxpSXnFHnpVVewkEiq;1981270;IN1loec110Y97Y9OILSxtkY1e5o1C9V/xOlrmfqwyD1IS9LA8yczMyFAgRa5nN/KQt+JxU+icBIQpKyJT7UsNUA=;0
Transaction ID: 7bc50d0e20c6d4aff221bb5cc6ef5450431faf3ac291d4294f124c5b9f8d0023-000



Debug information

Debit: -10.00000000 Biblepay
Credit: 8.99983820 Biblepay

Transaction:
CTransaction(hash=7bc50d0e20, ver=1, vin.size=1, vout.size=2, nLockTime=33038)
    CTxIn(COutPoint(c5546bac172f6f24018bdd8960d013b8772406db371b5ef9f015c0e9dada1578, 1), scriptSig=47304402200aa464a3be9a45, nSequence=4294967294)
    CTxOut(nValue=1.00000000, scriptPubKey=76a9144813c26f2846cfcde5d1cc62)
    CTxOut(nValue=8.99983820, scriptPubKey=76a914308deb678d8be06d32fdb952)

Inputs:

:)
Looks good, I see that CPID, just wait 6 confirms then send a massive utxo with 'exec podcupdate true'.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 09:15:30 PM
I'll do that. Why set a percentage anyways? What happens if I remove polpercentage?

So I made polpercentage=90. Ran exec podcupdate true but it's still sending less. I zapped the wallet beforehand also.

Transaction details:
Status: 1/unconfirmed, broadcast through 6 nodes
Date: 3/7/2018 22:10
Source: PODC-Update
Total debit: -14 972.87490824 Biblepay
Total credit: 14 972.87490824 Biblepay
Transaction fee: -0.00511820 Biblepay
Net amount: -0.00511820 Biblepay

Update:
I just remembered something, could it be because each account can have multiple addresses? I noticed that if I run getaccountaddress "", it will give me a different address sometimes. The adress associated with Rosetta has an account name but that account appears to have multiple addresses attached to it?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 07, 2018, 09:16:15 PM
Looks good, I see that CPID, just wait 6 confirms then send a massive utxo with 'exec podcupdate true'.

Hi Rob,

I sent that last message before seeing your pre-modified one. I checked my CPID and tried reassociating but I got the error ALREADY_IN_CHAIN.

The tx details I sent was from a few days ago.

Thanks for your help, I know you must be so busy today!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 09:31:00 PM
So I made polpercentage=90. Ran exec podcupdate true but it's still sending less. I zapped the wallet beforehand also.

Transaction details:
Status: 1/unconfirmed, broadcast through 6 nodes
Date: 3/7/2018 22:10
Source: PODC-Update
Total debit: -14 972.87490824 Biblepay
Total credit: 14 972.87490824 Biblepay
Transaction fee: -0.00511820 Biblepay
Net amount: -0.00511820 Biblepay

Update:
I just remembered something, could it be because each account can have multiple addresses? I noticed that if I run getaccountaddress "", it will give me a different address sometimes. The adress associated with Rosetta has an account name but that account appears to have multiple addresses attached to it?

Ok, I went ahead and modified PODC Updates to use Amounts instead of percentages.


So if you want to grab the latest code, we no longer use "-polpercentage".  We now use "utxoamount".

The default is now 50K.

Please let us know if this works, and that I did not break everyone.

So you set your wallet like this:
utxoamount=40000

For example, but the default is 50K.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 09:31:37 PM
Ok, I went ahead and modified PODC Updates to use Amounts instead of percentages.


So if you want to grab the latest code, we no longer use "-polpercentage".  We now use "utxoamount".

The default is now 50K.

Please let us know if this works, and that I did not break everyone.

So you set your wallet like this:
utxoamount=40000

For example, but the default is 50K.

I'll try it now.

Good thing you replied in time, I was about to try moving my Rosetta account to my Sanc again but it's having problems.

{
  "Command": "associate",
  "E-Mail": "xxx",
  "Results": "Unable to sign CPID e94c1704c75f731f8bfde303f08408ee"
}

2018-03-08 03:35:32 UpdateTip: new best=6f2dc78f647d37b2fbbef510b9ee7006505758d7dcacbc91e371cdcaf2ba02b6  height=33479  log2_work=$
2018-03-08 03:35:32 CMasternode::UpdateLastPaidBlock -- searching for block with payment to 31eb5a4581d3bc39a247fb499c51e6fd166a05$
2018-03-08 03:35:32 ProcessNewBlock : ACCEPTED

I also saw more of these:
2018-03-08 03:27:36 ERROR: CheckIndexAgainstCheckpoint: forked chain older than last checkpoint (height 33352)
2018-03-08 03:27:36 ERROR: AcceptBlockHeader: CheckIndexAgainstCheckpoint():
2018-03-08 03:27:36 Misbehaving: 218.71.239.70:49724 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-08 03:27:36 ERROR: invalid header received 52780d04e45328df88f6881f96da3575333452e22958a0f28ced6af8badcbddf
2018-03-08 03:28:15 DSEG -- Sent 168 Masternode invs to peer 182
2018-03-08 03:29:04 MASTERNODEPAYMENTSYNC -- Sent Masternode payment votes to peer 182
2018-03-08 03:30:09 ERROR: CheckIndexAgainstCheckpoint: forked chain older than last checkpoint (height 33352)
2018-03-08 03:30:09 ERROR: AcceptBlockHeader: CheckIndexAgainstCheckpoint():
2018-03-08 03:30:09 Misbehaving: 218.71.239.68:50027 (0 -> 100) BAN THRESHOLD EXCEEDED
2018-03-08 03:30:09 ERROR: invalid header received 52780d04e45328df88f6881f96da3575333452e22958a0f28ced6af8badcbddf
2018-03-08 03:30:15 DSEG -- Sent 168 Masternode invs to peer 202
2018-03-08 03:31:02  End To End CPID Verification Failed, Address does not match advertised public key for CPID 962b0d76dfb35f07b7$
2018-03-08 03:31:02 AddToWallet 8e041157fd8f3d11867dacdd22e307bc1861a7b96691d2d013ec080b37a671e6  update
2018-03-08 03:31:02 ProcessNewBlock : ACCEPTED
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 09:32:20 PM
Hi Rob,

I sent that last message before seeing your pre-modified one. I checked my CPID and tried reassociating but I got the error ALREADY_IN_CHAIN.

The tx details I sent was from a few days ago.

Thanks for your help, I know you must be so busy today!

To reassociate a cpid, add "true" to the end of the command.

exec associate user pass true

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 09:34:34 PM
I'll try it now.
Ok, I should be around for another 40 mins, but just in case, if something goes wrong with this, try to do this:
sendtoaddress your_bbp_address allOfYourBBP

See if sending it all to your primary wallet recv address helps the podcupdate send properly, but only do if this new build does not work as intended :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 09:37:53 PM
Ok, I should be around for another 40 mins, but just in case, if something goes wrong with this, try to do this:
sendtoaddress your_bbp_address allOfYourBBP

See if sending it all to your primary wallet recv address helps the podcupdate send properly, but only do if this new build does not work as intended :)

Oh wait I can't, it's on my windows machine. My linux doesn't have a desktop environment. I was trying to move it to my linux but it won't reassociate with true. See above, there is over 50k BBP on that machine.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 07, 2018, 09:43:45 PM
Oh wait I can't, it's on my windows machine. My linux doesn't have a desktop environment. I was trying to move it to my linux but it won't reassociate with true. See above, there is over 50k BBP on that machine.

Yeah, I have the same issue.  Im pretty confident we didnt break anyone with that, I took a look at it again.
So Im building windows, but it probably wont be ready til 6 am as its been quite a long day for me :), Im going to crash in about 30 mins.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 09:45:15 PM
Yeah, I have the same issue.  Im pretty confident we didnt break anyone with that, I took a look at it again.
So Im building windows, but it probably wont be ready til 6 am as its been quite a long day for me :), Im going to crash in about 30 mins.

OK, I can help with building the windows build if you would like in the future. I'm going to try sending everything out of that address, and then sending it back in.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 09:50:26 PM
Guys, I got Android tasks just now. Looks like they made a batch of 10000 tasks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 07, 2018, 11:06:45 PM
Going to bed.

Tried transferring out and then back in, waited for 7 confirmations but it still only staked 15k BBP with polpercentage set to 90. The other problem is I can't re-associate to another wallet. Will tackle these tomorrow!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 08, 2018, 01:58:30 AM
Hi all,

This is now getting very wierd for me:
- I had my Rosseta account associated with my Biblepay address, but my TaskWeight,  UTXOWeight,  Magnitude was still zero. Stakebalance is fine.
- So I decided to re-associate it again with exec associate <my rosseta user> <my rosseta password> true

Then I have waited at least 6 confirmations.

Now if I look at my getboininfo I see my my rosseta CPID as before, but biblepay has been replaced with some unknown one! I must say that I newer had more than one biblepay address!
Where did this unknown address come from ????

Code: [Select]
08:57:10
exec getboincinfo

08:57:12
{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "BRB4qQ2dVSf6cowjXF27xLfvUcW75JiLTJ",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422359,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "BRB4qQ2dVSf6cowjXF27xLfvUcW75JiLTJ",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 9405.16,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 9405.16,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Edit: I have made re-asociation again and now I get another unknown address:

Code: [Select]
09:30:02
exec getboincinfo
09:30:04
{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422360,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 9347.85,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 9347.85,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 02:43:41 AM
Hi all,

This is now getting very wierd for me:
- I had my Rosseta account associated with my Biblepay address, but my TaskWeight,  UTXOWeight,  Magnitude was still zero. Stakebalance is fine.
- So I decided to re-associate it again with exec associate <my rosseta user> <my rosseta password> true

Then I have waited at least 6 confirmations.

Now if I look at my getboininfo I see my my rosseta CPID as before, but biblepay has been replaced with some unknown one! I must say that I newer had more than one biblepay address!
Where did this unknown address come from ????

Code: [Select]
08:57:10
exec getboincinfo

08:57:12
{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "BRB4qQ2dVSf6cowjXF27xLfvUcW75JiLTJ",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422359,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "BRB4qQ2dVSf6cowjXF27xLfvUcW75JiLTJ",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 9405.16,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 9405.16,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Edit: I have made re-asociation again and now I get another unknown address:

Code: [Select]
09:30:02
exec getboincinfo
09:30:04
{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422360,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 9347.85,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 9347.85,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


Best regards,
Simon

If you look at 'file>receiving addresses', they aren't there?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 02:45:45 AM
Hi all,

This is now getting very wierd for me:
- I had my Rosseta account associated with my Biblepay address, but my TaskWeight,  UTXOWeight,  Magnitude was still zero. Stakebalance is fine.
- So I decided to re-associate it again with exec associate <my rosseta user> <my rosseta password> true

Then I have waited at least 6 confirmations.

Now if I look at my getboininfo I see my my rosseta CPID as before, but biblepay has been replaced with some unknown one! I must say that I newer had more than one biblepay address!
Where did this unknown address come from ????

Code: [Select]
08:57:10
exec getboincinfo

08:57:12
{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "BRB4qQ2dVSf6cowjXF27xLfvUcW75JiLTJ",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422359,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "BRB4qQ2dVSf6cowjXF27xLfvUcW75JiLTJ",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 9405.16,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 9405.16,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Edit: I have made re-asociation again and now I get another unknown address:

Code: [Select]
09:30:02
exec getboincinfo
09:30:04
{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422360,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 9347.85,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 9347.85,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


Best regards,
Simon

Try sending a transaction of 1BBP go that address. You will find that it is in your wallet (a transaction to yourself), but doesn't show up in receiving addresses
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 08, 2018, 02:46:47 AM
If you look at 'file>receiving addresses', they aren't there?

No, they aren't there - they newer were as I only had 1 address: B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m
I think that if I do re-associate agan I will end up with another strange address.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 02:48:04 AM
Guys, I got Android tasks just now. Looks like they made a batch of 10000 tasks.

Yeah got Android tasks too! Phew 8)

Maybe it's an idea for the future to have some redundancy in the case of 'unbanked' accounts. Because I can imagine that if you use your phone for BBP income, and tasks stop coming for a some time, you are going to lose hope in Biblepay.

So maybe we could look at implementing a backup-project (aside from Rosetta) for unbanked account, so their RAC will not fall if Rosetta fails to send out Android tasks. I don't know about the technicalities of this, it' just a thought.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 08, 2018, 03:00:01 AM
Try sending a transaction of 1BBP go that address. You will find that it is in your wallet (a transaction to yourself), but doesn't show up in receiving addresses

That is true. I was only charged a fee and it says Payment to yourself.
What is the deal with this?
TaskWeight,  UTXOWeight,  Magnitude are still zero ... It's a bit of a mess for me :(
Thanks for help.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 03:10:41 AM
That is true. I was only charged a fee and it says Payment to yourself.
What is the deal with this?
TaskWeight,  UTXOWeight,  Magnitude are still zero ... It's a bit of a mess for me :(
Thanks for help.
Ok so if you trust that address, send the stake to that address **AFTER** your association payment is confirmed (6 blocks)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 08, 2018, 03:14:32 AM
Ok so if you trust that address, send the stake to that address **AFTER** your association payment is confirmed (6 blocks)
Honestly ... I don't trust it :)  Does everyone have different addresse there?
I didn't think I would have to sent stake manually - wasn't that suppose to be automatic?

Thank you for your help.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 03:16:35 AM
Honestly ... I don't trust it :)  Does everyone have different addresse there?
I didn't think I would have to sent stake manually - wasn't that suppose to be automatic?

Thank you for your help.
Your stake needs to be in the
"Address" from
exec getboincinfo
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 03:33:36 AM
I tried to associate a new 'unbanked' account on the pool, and it seems to be working  8)

(https://preview.ibb.co/duKtXn/unbanked.png)

About the 'associate unbanked CPID' function on the pool:

A few days ago, I successfully used this function to associate my android phone on a Rosetta test-account (CPID: 8791a036b545f35e9ebd9333922738ac).
I used the following BBP adress: BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj

Today I wondered if this burn survived yesterdays chaos, so I looked it up via 'exec datalist dcc' and it gave me the following:

Code: [Select]
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
There is a different Biblepay adress here: BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J

Looking at the transactions, it seems to be a pool-address: http://explorer.biblepay.org:3001/address/BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J

I guess this happened because the code on the pool-side wasn't ready yet (Rob was surprised my association was successful at the time, haha!).

Anyway, my question to Rob is: should I just make a new test-account, or could you re-associate it to the correct address for me? It's just for testing anyway, so it doesn't really matter to me in terms of BBP (that's for the pool as far as I'm concerned). Just wanted to let you know :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 03:34:38 AM
Your stake needs to be in the
"Address" from
exec getboincinfo

Really? I didn't think this was the case.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 03:36:13 AM

Biblepay 1.1.0.5
Mandatory Upgrade for Sanctuaries
Leisure Upgrade for Users


- Add checkpoint at 33460 to prevent forking and lock in PODC consensus system
- Add checkblock to verify all 33460+ PODC blocks were generated by v1.1.0.0+
- Fix Task Verification Error in Sanctuary Quorum affecting Magnitude Calculation for Large CPIDs

** Windows is still building, this is a notification for all linux nodes **

Quoting for visibility. Upgrading now :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 04:01:46 AM
Really? I didn't think this was the case.

Maybe I am wrong. It happens often!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on March 08, 2018, 04:13:50 AM
Your stake needs to be in the
"Address" from
exec getboincinfo

I have the same issue. Plenty of BBP to stake, but zero UTXOWeight. Sent the BBP to the address from exec getboincinfo, now waiting for 6 confirms to see what happens.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 04:40:17 AM
I have around 3 mining rewards so far (~555 each).
Has anyone received Sanctuary rewards yet?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 04:53:33 AM
I have around 3 mining rewards so far (~555 each).
Has anyone received Sanctuary rewards yet?

Yes, i have received both mining and sanctuary rewards :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 04:56:50 AM
Yes, i have received both mining and sanctuary rewards :)
Thanks, OK great, mine will be on the way then  :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on March 08, 2018, 05:18:25 AM
I have the same issue. Plenty of BBP to stake, but zero UTXOWeight. Sent the BBP to the address from exec getboincinfo, now waiting for 6 confirms to see what happens.

aargh. Still not working for me. I have > 50 000 BBP in the wallet address from exec getboincinfo. Stakabalance confirms that. But my UTXOWeight is still 0, and exec podcupdate says Insufficient funds.

This is the second node I'm trying to make this runing (started from scratch today, since it did not work for me yestarday).

Code: [Select]
# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422363,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "fe553a955f0e21d46724858870014cbe_RAC": 6007.06,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6007.06,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Quote
# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 50099
}

Quote
# biblepay-cli listaddressgroupings
[
  [
    [
      "BCAPPX5PosAcqc5Z4codkaTMLnmQJSwhMX",
      0.00076300
    ],
    [
      "BMskLQZcPd8EUA8c5iHCmCiAruPjVXtUe1",
      0.00000000,
      ""
    ],
    [
      "BSF8FbMtBKVJ3XiP7fAtrMSU7NfQGQDtmw",
      0.00000000
    ]
  ],
  [
    [
      "BMdWb8WHRbgo6x6AEErNi4cvUVuiKqXn1u",
      0.00000000
    ]
  ],
  [
    [
      "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
      50099.99900000,
      ""
    ]
  ]
]


Code: [Select]
# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 05:26:55 AM
aargh. Still not working for me. I have > 50 000 BBP in the wallet address from exec getboincinfo. Stakabalance confirms that. But my UTXOWeight is still 0, and exec podcupdate says Insufficient funds.

This is the second node I'm trying to make this runing (started from scratch today, since it did not work for me yestarday).

Code: [Select]
# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422363,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
  "fe553a955f0e21d46724858870014cbe_RAC": 6007.06,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6007.06,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}


Code: [Select]
# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}


You could try reassociating your CPID again
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on March 08, 2018, 05:40:48 AM
You could try reassociating your CPID again

Have just tried that. So far still zero UTXOWeight, but let's wait 6 blocks. But frankly, I do not believe in success.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 06:54:23 AM
Alright good news, even though it requires an upgrade for the users, good news, I debugged the exec podcupdate feature this morning and I did find a bug!  This explains why T-Mike cant send the exact right stake amount and Simons UTXO is 0 and Rastiks is probably the same issue.

So I now confirm you dont need to worry about the source address of the funds, we will still sign the UTXO packet with your CPID no matter which "bucket" it originates from in the wallet, so that will alleviate a huge portion of the hassle with sending a PODC Update (in the next version).  The other biggie I found was the math the wallet was using was slightly off due to rounding, its kind of hard to explain, but the lions share of the problem was, if you were trying to send say 49K of your 50,000 balance, and your tasks consumed say 3.5K bytes, the internal math (in decimal) rounded down to an amount that was not properly split among the vouts ending with too small of a UTXO expenditure, so I had to fix that so the PODC update leg count (internally) would always round up the specific UTXO for that amount per leg, its a little technical but that is now fixed (in the next version). 

This should be checked in ASAP, doing a little unit testing with this.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on March 08, 2018, 07:00:36 AM
You could try reassociating your CPID again

Well, I tried. Waited 6 blocks, and still the same. Stakebalance shows 50093, but exec podcupdate syas Insufficient funds. UTXOWeight & TaskWeight are zero. May there be something wrong with my CPID ? Maybe, because I have some ARM (tablet + phone) connected to it? I have run out of ideas.

Code: [Select]
# biblepay-cli exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "fe553a955f0e21d46724858870014cbe",
  "Address": "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
  "CPIDS": "fe553a955f0e21d46724858870014cbe;",
  "CPID-Age (hours)": 422364,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "fe553a955f0e21d46724858870014cbe_ADDRESS": "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
  "fe553a955f0e21d46724858870014cbe_RAC": 6331.92,
  "fe553a955f0e21d46724858870014cbe_TEAM": 15044,
  "fe553a955f0e21d46724858870014cbe_TaskWeight": 0,
  "fe553a955f0e21d46724858870014cbe_UTXOWeight": 0,
  "Total_RAC": 6331.92,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Code: [Select]
# biblepay-cli exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 50093
}

Code: [Select]
# biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Insufficient funds."
}

The wallet is quite fragmented after i did several attempts and moved the coins back and forth :D
Code: [Select]
# biblepay-cli listaddressgroupings
[
  [
    [
      "B7Wtksz1hbBWXRY6U9QhdxMn78h9oEcV5B",
      0.00000000
    ],
    [
      "B7vWrPFoLLawsrpC6hewcxJ6ZbjtPXupV8",
      0.00000000
    ],
    [
      "B8RLs7oTsXvM4QXLQrVVHYwipKqaJXmH4W",
      0.00000000
    ],
    [
      "BB3WzCSGdH6ZYAn5o1a7N4XXKTNcYZ8K6C",
      93.99990840
    ],
    [
      "BCAPPX5PosAcqc5Z4codkaTMLnmQJSwhMX",
      0.00076300
    ],
    [
      "BHRvGs45us9mGimkWimv8kwgYgfmDn2iqm",
      994.99995420
    ],
    [
      "BMskLQZcPd8EUA8c5iHCmCiAruPjVXtUe1",
      0.00000000,
      ""
    ],
    [
      "BQNfVQxb75ssRZ5aqas4Wt2rj6AcPxaZkX",
      48993.99879240
    ],
    [
      "BSF8FbMtBKVJ3XiP7fAtrMSU7NfQGQDtmw",
      0.00000000
    ],
    [
      "BSG8v2noPJzEsNxT7DhMzLbva4AAuSgkvb",
      0.00000000,
      ""
    ]
  ],
  [
    [
      "BMdWb8WHRbgo6x6AEErNi4cvUVuiKqXn1u",
      0.00000000
    ]
  ],
  [
    [
      "BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY",
      11.00000000,
      ""
    ]
  ]
]
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: rastiks on March 08, 2018, 07:01:46 AM
Alright good news, even though it requires an upgrade for the users, good news, I debugged the exec podcupdate feature this morning and I did find a bug!  This explains why T-Mike cant send the exact right stake amount and Simons UTXO is 0 and Rastiks is probably the same issue.

So I now confirm you dont need to worry about the source address of the funds, we will still sign the UTXO packet with your CPID no matter which "bucket" it originates from in the wallet, so that will alleviate a huge portion of the hassle with sending a PODC Update (in the next version).  The other biggie I found was the math the wallet was using was slightly off due to rounding, its kind of hard to explain, but the lions share of the problem was, if you were trying to send say 49K of your 50,000 balance, and your tasks consumed say 3.5K bytes, the internal math (in decimal) rounded down to an amount that was not properly split among the vouts ending with too small of a UTXO expenditure, so I had to fix that so the PODC update leg count (internally) would always round up the specific UTXO for that amount per leg, its a little technical but that is now fixed (in the next version). 

This should be checked in ASAP, doing a little unit testing with this.

Great! thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 07:04:35 AM
I have around 3 mining rewards so far (~555 each).
Has anyone received Sanctuary rewards yet?
I havent, but the pool is killing it now!  It received about 13 blocks this morning.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 07:10:26 AM
Biblepay
1.1.0.6 - Leisure Upgrade



- Make exec podcupdate much more robust (error messages, utxo leg rounding)

** Windows is compiling **

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 07:10:38 AM
Alright good news, even though it requires an upgrade for the users, good news, I debugged the exec podcupdate feature this morning and I did find a bug!  This explains why T-Mike cant send the exact right stake amount and Simons UTXO is 0 and Rastiks is probably the same issue.

So I now confirm you dont need to worry about the source address of the funds, we will still sign the UTXO packet with your CPID no matter which "bucket" it originates from in the wallet, so that will alleviate a huge portion of the hassle with sending a PODC Update (in the next version).  The other biggie I found was the math the wallet was using was slightly off due to rounding, its kind of hard to explain, but the lions share of the problem was, if you were trying to send say 49K of your 50,000 balance, and your tasks consumed say 3.5K bytes, the internal math (in decimal) rounded down to an amount that was not properly split among the vouts ending with too small of a UTXO expenditure, so I had to fix that so the PODC update leg count (internally) would always round up the specific UTXO for that amount per leg, its a little technical but that is now fixed (in the next version). 

This should be checked in ASAP, doing a little unit testing with this.

Rob, for some reason my UTXOweight is 100 this morning, I checked the last PODC update transaction that happened at around 4am and it was only 15k, not sure why it make my weight 100.

Code: [Select]
Status: 25 confirmations, broadcast through 7 nodes
Date: 3/8/2018 04:35
Source: PODC-Update
Total debit: -15 762.10882064 Biblepay
Total credit: 15 762.10882064 Biblepay
Transaction fee: -0.00500860 Biblepay
Net amount: -0.00500860 Biblepay

Height: 33524
Difficulty: 0.000000
Time: 03-08-2018 09:49:06
Subsidy: 555.4128

PODC_UPDATE:
Transaction ID: 272c95b9f40a5d3a7d18c2b925301f79dc334845abb80272d04c9258c8a94b8a-000

Updating now. Does this build use utxoamount=x instead?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 07:14:00 AM
No, they aren't there - they newer were as I only had 1 address: B7AZbMPwtCNejwiLktZteGKuSgdmUkzq4m
I think that if I do re-associate agan I will end up with another strange address.

When someone reassociates a CPID, we do ask the wallet to create a new dedicated receiving address, this is so the chain contains distinct addresses per CPID during magnitude reverse engineering.

The address should be in your receiving address.  I confirm that we do pull one from your own wallet.

Note, in the next version we dont require any funds to actually be in the CPIDs address, so dont worry about sending funds to it anymore.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 07:18:18 AM
Rob, for some reason my UTXOweight is 100 this morning, I checked the last PODC update transaction that happened at around 4am and it was only 15k, not sure why it make my weight 100.

Code: [Select]
Status: 25 confirmations, broadcast through 7 nodes
Date: 3/8/2018 04:35
Source: PODC-Update
Total debit: -15 762.10882064 Biblepay
Total credit: 15 762.10882064 Biblepay
Transaction fee: -0.00500860 Biblepay
Net amount: -0.00500860 Biblepay

Height: 33524
Difficulty: 0.000000
Time: 03-08-2018 09:49:06
Subsidy: 555.4128

PODC_UPDATE:
Transaction ID: 272c95b9f40a5d3a7d18c2b925301f79dc334845abb80272d04c9258c8a94b8a-000

Updating now. Does this build use utxoamount=x instead?

Yeah, I need to inform everyone on the main thread of the big change, we now use "utxoamount=X" across the board.  Ill do that when windows is done building and explain it in that message.

So on your tx, I do see your CPID e94* in my utxoweight list being 100, so that is great.

The reason its 100 is you sent : 106.3K in leg 1 of your UTXO transaction.

Dont worry about debugging it, the last versions squirrely math might have sent an unpredictable amount, the new version should be dead on every time and send change back to you.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 08, 2018, 07:21:22 AM
When someone reassociates a CPID, we do ask the wallet to create a new dedicated receiving address, this is so the chain contains distinct addresses per CPID during magnitude reverse engineering.

The address should be in your receiving address.  I confirm that we do pull one from your own wallet.

Note, in the next version we dont require any funds to actually be in the CPIDs address, so dont worry about sending funds to it anymore.


Hi Rob,

Thanks for hard work.
Would it be possible to reassign the address manually?

This is list of my addresses (printscreen):
https://drive.google.com/open?id=1YQinWqsheQWfCE_Z2RvRv_5fedGR8gif

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 07:26:08 AM
Yeah, I need to inform everyone on the main thread of the big change, we now use "utxoamount=X" across the board.  Ill do that when windows is done building and explain it in that message.

So on your tx, I do see your CPID e94* in my utxoweight list being 100, so that is great.

The reason its 100 is you sent : 106.3K in leg 1 of your UTXO transaction.

Dont worry about debugging it, the last versions squirrely math might have sent an unpredictable amount, the new version should be dead on every time and send change back to you.

Oh, I see it in the details, it was not showing in the debited amount at the top.

You remember I told you I tried to associate it to my Sanctuary wallet yesterday? Well the address on Rosetta has changed to that account even though it failed.

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

Code: [Select]
exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422364,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 58863.33,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 58863.33,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Update:
I just tried adding my Android Rosetta account to the linux Sanctuary wallet and I get the same error: "Results": "Unable to sign CPID 4b7d2d64c88b32927a21ad20a57868e4"

I see no errors in debug.log.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 07:52:39 AM
Oh, I see it in the details, it was not showing in the debited amount at the top.

You remember I told you I tried to associate it to my Sanctuary wallet yesterday? Well the address on Rosetta has changed to that account even though it failed.

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

Code: [Select]
exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "e94c1704c75f731f8bfde303f08408ee",
  "Address": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "CPIDS": "e94c1704c75f731f8bfde303f08408ee;",
  "CPID-Age (hours)": 422364,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e94c1704c75f731f8bfde303f08408ee_ADDRESS": "BTTa9qDMsX6zEQcYJPNu1KptscotKMbPfN",
  "e94c1704c75f731f8bfde303f08408ee_RAC": 58863.33,
  "e94c1704c75f731f8bfde303f08408ee_TEAM": 15044,
  "e94c1704c75f731f8bfde303f08408ee_TaskWeight": 100,
  "e94c1704c75f731f8bfde303f08408ee_UTXOWeight": 100,
  "Total_RAC": 58863.33,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Update:
I just tried adding my Android Rosetta account to the linux Sanctuary wallet and I get the same error: "Results": "Unable to sign CPID 4b7d2d64c88b32927a21ad20a57868e4"

I see no errors in debug.log.

Its really OK if the wallet makes it through phase 1 of association and fails (IE changes your boinc URL) as that is just part of the process, but as far as it failing due to cannot sign cpid:

That means the wallet is locked.  Try sending some bbp to yourself with 'sendtoaddress address 1' first, then run the exec associate command.  Then it should pass.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 07:53:35 AM
Hi Rob,

Thanks for hard work.
Would it be possible to reassign the address manually?

This is list of my addresses (printscreen):
https://drive.google.com/open?id=1YQinWqsheQWfCE_Z2RvRv_5fedGR8gif

Best regards,
Simon

Hi Simon, no its not possible.

Best thing to do is send some BBP to the exec getboincinfo address, and ensure you receive it.  Then youre all set.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 07:58:54 AM
Its really OK if the wallet makes it through phase 1 of association and fails (IE changes your boinc URL) as that is just part of the process, but as far as it failing due to cannot sign cpid:

That means the wallet is locked.  Try sending some bbp to yourself with 'sendtoaddress address 1' first, then run the exec associate command.  Then it should pass.

I apologize, I forgot to delete my old encrypted wallet, I was going to use an un-encrypted one for PODC. Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 08:04:47 AM
Hi Simon, no its not possible.

Best thing to do is send some BBP to the exec getboincinfo address, and ensure you receive it.  Then youre all set.

But,  I will  figure out why its not adding bbp addresses to the address book and naming them rosetta... Let me check....

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 08:30:31 AM
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 08:34:55 AM
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?

Is there a minimum version that is required? My sancs are on 1.1.0.5. now.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 08:36:31 AM
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?
If anyone wants to help us verify their sanc so we ensure Togos will get processed please run this on the sanc:

"If you want to test your Sancs health with Togos cpid his cpid is 9313, you can type 'exec dcc', and when its done go to bash, cd /SAN, then 
cat filtered | grep 9313 -A10 -B10 and take a look at Togo's <taskweight> and it should be up to 100."


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 08:37:39 AM
Is there a minimum version that is required? My sancs are on 1.1.0.5. now.
Yes exactly, it was put in 1105,  Thanks.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 08:39:42 AM
So I upgraded all my sancs to ensure Togo is going to come through, at least on my end of the deal :), hey Mike, can you try that thing I posted for Sanc testing to ensure your sanc will process Togos CPID?

Not sure what's going on:
./biblepay-cli exec dcc
error code: -1
error message:
bad lexical cast: source type value could not be interpreted as target

But actually I ran that a few pages back and posted it.

From yesterday:
Code: [Select]
cat filtered | grep 9313 -A10 -B10
 <name>strayapple</name>
 <id>1981219</id>
<utxoweight>75</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

</user>
<user>

 <teamid>15044</teamid>
 <url>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs</url>
 <cpid>93138f032bdd027fa3246b48bb715a77</cpid>
 <expavg_time>1520462480.639447</expavg_time>
 <expavg_credit>80933.641932</expavg_credit>
 <total_credit>1254458.742816</total_credit>
 <create_time>1517967718</create_time>
 <country>United States</country>
 <name>togoshigekata</name>
 <id>1981221</id>
<utxoweight>100</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

Update:
Now it's saying:
./biblepay-cli exec dcc
{
  "Command": "dcc",
  "Success": false,
  "Error": ""
}

Nothing in debug.log
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 08:42:35 AM
If anyone wants to help us verify their sanc so we ensure Togos will get processed please run this on the sanc:

"If you want to test your Sancs health with Togos cpid his cpid is 9313, you can type 'exec dcc', and when its done go to bash, cd /SAN, then 
cat filtered | grep 9313 -A10 -B10 and take a look at Togo's <taskweight> and it should be up to 100."

Yeah, I wanted to do this earlier, but I don't understand this step:
'go to bash, cd /SAN'

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 08:43:58 AM
Yeah, I wanted to do this earlier, but I don't understand this step:
'go to bash, cd /SAN'

go into the biblepaycore dir and run cd SAN.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 08:44:28 AM
Not sure what's going on:
./biblepay-cli exec dcc
error code: -1
error message:
bad lexical cast: source type value could not be interpreted as target

But actually I ran that a few pages back and posted it.

From yesterday:
Code: [Select]
cat filtered | grep 9313 -A10 -B10
 <name>strayapple</name>
 <id>1981219</id>
<utxoweight>75</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

</user>
<user>

 <teamid>15044</teamid>
 <url>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs</url>
 <cpid>93138f032bdd027fa3246b48bb715a77</cpid>
 <expavg_time>1520462480.639447</expavg_time>
 <expavg_credit>80933.641932</expavg_credit>
 <total_credit>1254458.742816</total_credit>
 <create_time>1517967718</create_time>
 <country>United States</country>
 <name>togoshigekata</name>
 <id>1981221</id>
<utxoweight>100</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

Update:
Now it's saying:
./biblepay-cli exec dcc
{
  "Command": "dcc",
  "Success": false,
  "Error": ""
}

Nothing in debug.log

I get the same error:

Code: [Select]
error code: -1
error message:
bad lexical cast: source type value could not be interpreted as target

Later tried it again, also the same error Mike got (I think):
Code: [Select]
{
  "Command": "dcc",
  "Success": false,
  "Error": ""
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 08:45:44 AM
go into the biblepaycore dir and run cd SAN.

Thx!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 08:50:36 AM
Not sure what's going on:
./biblepay-cli exec dcc
error code: -1
error message:
bad lexical cast: source type value could not be interpreted as target

But actually I ran that a few pages back and posted it.

From yesterday:
Code: [Select]
cat filtered | grep 9313 -A10 -B10
 <name>strayapple</name>
 <id>1981219</id>
<utxoweight>75</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

</user>
<user>

 <teamid>15044</teamid>
 <url>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs</url>
 <cpid>93138f032bdd027fa3246b48bb715a77</cpid>
 <expavg_time>1520462480.639447</expavg_time>
 <expavg_credit>80933.641932</expavg_credit>
 <total_credit>1254458.742816</total_credit>
 <create_time>1517967718</create_time>
 <country>United States</country>
 <name>togoshigekata</name>
 <id>1981221</id>
<utxoweight>100</utxoweight>
<taskweight>100</taskweight><unbanked>0</unbanked>

Update:
Now it's saying:
./biblepay-cli exec dcc
{
  "Command": "dcc",
  "Success": false,
  "Error": ""
}

Nothing in debug.log

Confirmed, I was able to reproduce this exact same issue on my sanc.

The problem turned out to be during my morning PODC test, my particular task weight had a bad scale, to fix this, let me attempt to retransmit my podcupdate now, and see if it fixes you.  I will Fix this particular issue from happening permanently also, but in a way where we will not need to upgrade now as we are running out of time. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 08, 2018, 09:07:13 AM
Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code: [Select]
09:03:44

exec getboincinfo


09:03:45

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422367,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2917.45,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2917.45,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 09:14:41 AM
Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code: [Select]
09:03:44

exec getboincinfo


09:03:45

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

Did you run exec podcupdate true and wait 6 blocks?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:17:13 AM
go into the biblepaycore dir and run cd SAN.
Ok, anyone who had the bad lexical cast error, I have added code to the sanc side to prevent any number longer than the Max c++ length from happening again, and thankfully I was able to re-send my bad podcupdate, and the network accepted it.

So please, try the test over - if you type exec dcc - if it returns with false, just reboot your node.  This is a one time thing to clear the sanc out of its bad memories.

I just reran the test, and I see Togo is up and running with a magnitude of 268, looks like I have 56, etc.. you can see the mag this way from a sanc:
cd SAN
cat magnitude | grep 9313

Etc.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:18:26 AM
Any idea why my UTXO is still at 75? I updated to 1.1.0.5 and changed polpercentage to utxoweight=50000.

Code: [Select]
09:03:44

exec getboincinfo


09:03:45

{
  "Command": "getboincinfo",
  "CPID": "e6ce50042187d4b285568d86ef458f32",
  "Address": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "CPIDS": "e6ce50042187d4b285568d86ef458f32;",
  "CPID-Age (hours)": 422367,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "e6ce50042187d4b285568d86ef458f32_ADDRESS": "BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk",
  "e6ce50042187d4b285568d86ef458f32_RAC": 2917.45,
  "e6ce50042187d4b285568d86ef458f32_TEAM": 15044,
  "e6ce50042187d4b285568d86ef458f32_TaskWeight": 100,
  "e6ce50042187d4b285568d86ef458f32_UTXOWeight": 75,
  "Total_RAC": 2917.45,
  "Total Payments (One Day)": 0,
  "Total Pa
  "Magnitude (One-Week)": 0
}

Could you please double click , copy, and paste the outgoing UTXO txid here?

Edit: I dont show a PODCUpdate coming from E6CE recently - last one was yesterday.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 08, 2018, 09:19:56 AM
Could you please double click , copy, and paste the outgoing UTXO txid here?

Code: [Select]
Status: 122 confirmations
Date: 3/5/2018 23:26
To: BB2BwSbDCqCqNsfc7FgWFJn4sRgnUt4tsM
Debit: -1.00000000 Biblepay
Transaction fee: -0.00019140 Biblepay
Net amount: -1.00019140 Biblepay


DCC: e6ce50042187d4b285568d86ef458f32;BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk;BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk;1985116;H4P4qzNTeEqMQtyNKSalu01omMRfGXBhHe+8Y/IaVoKfEUwY3ZoA9PlMkAkyT9DbQsabpPvUOF0635hdXBrvkR8=;0
Transaction ID: 21d81563d6e3ecccaab0215df0a1fd7a3fc6ef4826e9f867e7fdf8abc5f6e8f4-000



Debug information

Debit: -1.00000000 Biblepay
Debit: -1.00000000 Biblepay
Credit: 0.99980860 Biblepay

Transaction:
CTransaction(hash=21d81563d6, ver=1, vin.size=2, vout.size=2, nLockTime=33204)
    CTxIn(COutPoint(d05dc9749756f29cee88e2267dff2ac4725cc346911518b6d6b902bde2a8ee41, 1), scriptSig=473044022024c6a78088fb37, nSequence=4294967294)
    CTxIn(COutPoint(14f89fcf60f39d461d7924326fc2f8b1189b9153566c77cbc1a66f9b0bbeb3f2, 0), scriptSig=47304402205db2565a1609bd, nSequence=4294967294)
    CTxOut(nValue=0.99980860, scriptPubKey=76a914aeea512bcbc96c148376c04d)
    CTxOut(nValue=1.00000000, scriptPubKey=76a9144813c26f2846cfcde5d1cc62)

Inputs:
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 09:21:03 AM
./biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (1.00) less than target UTXO (50000.00)."
}

Looks like it is working, going to have to wait for a few confirmations then I will try again. It is still looking for the right address on "version": 1010006 even though I have enough in my wallet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 09:24:35 AM
Ok, anyone who had the bad lexical cast error, I have added code to the sanc side to prevent any number longer than the Max c++ length from happening again, and thankfully I was able to re-send my bad podcupdate, and the network accepted it.

So please, try the test over - if you type exec dcc - if it returns with false, just reboot your node.  This is a one time thing to clear the sanc out of its bad memories.

I just reran the test, and I see Togo is up and running with a magnitude of 268, looks like I have 56, etc.. you can see the mag this way from a sanc:
cd SAN
cat magnitude | grep 9313

Etc.

exec dcc works now, thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:27:01 AM
Biblepay
1.1.0.6 - Leisure Upgrade



- Make exec podcupdate much more robust (add error messages, fix utxo leg rounding)


** Note to All: please modify the Distributed Computing process in this way:
Retire the use of -polpercentage in your config files.
Use "utxoamount=50000" instead, where 50000 is the amount of UTXO you choose to stake in each podcupdate (this occurs approx. once per day).
Note - the default is now 50,000, so you do not need to set it if you desire 50,000 **

Anyone with 'exec getboincinfo' with less than 100 utxoweight, please 'exec podcupdate' to send a new UTXO using this new version.

** Windows is ready for download **


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:27:16 AM
exec dcc works now, thanks.

Do you show the same mag for Togo Mike?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:28:52 AM
./biblepay-cli exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (1.00) less than target UTXO (50000.00)."
}

Looks like it is working, going to have to wait for a few confirmations then I will try again. It is still looking for the right address on "version": 1010006 even though I have enough in my wallet.

As long as 'exec stakebalance' shows 1 then no bug found yet.

It should now spend from any bucket, not just the CPID address, so I think the problem is not enough confirms in your wallet tx as of yet.


See Coin Control to ensure.

EDIT: I sent myself an instantsend this morning, waited 1 confirm and it had 6, and I was able to do a podcupdate.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 09:29:12 AM
Do you show the same mag for Togo Mike?

cat magnitude | grep 9313
<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512

Not sure if there was an update but it's not the same.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:30:22 AM
cat magnitude | grep 9313
<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512

Thats a beautiful sight as I show 291.640 for Togo also!

Ok, lets try exec testvote, what is your primary contract filehash?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 09:37:15 AM
As long as 'exec stakebalance' shows 1 then no bug found yet.

It should now spend from any bucket, not just the CPID address, so I think the problem is not enough confirms in your wallet tx as of yet.


See Coin Control to ensure.

EDIT: I sent myself an instantsend this morning, waited 1 confirm and it had 6, and I was able to do a podcupdate.

So in address A i had 50k with 6 confirmations when I tried it and 5 confirmations on the Rosetta account address with 1 BBP.

Code: [Select]
./biblepay-cli listreceivedbyaddress
[
  {
    "address": "BGmjr2mQNvSJ1faHGAo8FxtnUd98HGRkWK",
    "account": "",
    "amount": 50005.00000000,
    "confirmations": 6,
    "bcconfirmations": 6,
    "label": "",
    "txids": [
      "2f3cc129a739591f18d3ed17da186e6e545d125bae963ef1bbd571fee501295f"
    ]
  },
  {
    "address": "BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW",
    "account": "",
    "amount": 1.00000000,
    "confirmations": 5,
    "bcconfirmations": 5,
    "label": "",
    "txids": [
      "0aa3218c417ab80e00a8d362ebfddf63eb3ea160e73445856c3d5ea59d1fa579"
    ]
  }
]

Right now I have a stakebalance of zero since I'm trying to transfer everything into the Rosetta address and it's still going. I think you can just leave it aside for now and see if other people have a problem.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 09:37:30 AM
Thats a beautiful sight as I show 291.640 for Togo also!

Ok, lets try exec testvote, what is your primary contract filehash?

I see the same too!  :D

Code: [Select]
root@jaapgvk2:~/.biblepaycore/SAN# cat magnitude | grep 9313
<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 09:39:12 AM
Thats a beautiful sight as I show 291.640 for Togo also!

Ok, lets try exec testvote, what is your primary contract filehash?

Code: [Select]
./biblepay-cli exec testvote
{
  "Command": "testvote",
  "fileage": 891,
  "filehash": "000000000000000000000000000000009e0baa65c110d216239a1e784e3c1409",
  "contract": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,55.169,475629,15044,100,100,277512\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,277512\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,110.051,1981209,15044,75,100,277512\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.675,1981219,15044,100,100,277512\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,146.543,1981270,15044,100,100,277512\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.769,1981344,15044,60,100,277512\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,96.552,1981355,15044,100,100,277512\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.264,1981529,15044,100,100,277512\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,277512\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,38.195,1981615,15044,100,100,277512\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.787,1981648,15044,75,100,277512\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,277512\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.438,1981794,15044,100,100,277512\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.282,1981965,15044,75,100,277512\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,136.642,1982089,15044,75,100,277512\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.491,1982123,15044,60,100,277512\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,277512\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,18.151,1982463,15044,100,100,277512\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,14.146,1983490,15044,60,100,277512\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.285,1983588,15044,50,100,277512\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.245,1984116,15044,60,100,277512\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.263,1985116,15044,75,100,277512\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.342,1985935,15044,75,100,277512\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,277512\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,4.227,1987391,15044,60,100,277512\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.357,1987401,15044,25,100,277512\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.165,1987419,15044,75,100,277512\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.842,1987421,15044,60,100,277512\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.118,1987451,15044,25,100,277512\n<ROW>\n",
"sanctuary_rank": 0,
  "pam_hash": "0000000000000000000000000000000038eb4f0145166a60c10431e52fceb201",
  "govobjhash": "80cbe900009455a05a41ffe8c0d0b0bbe92c15708325be92bb05e308f2cf17ca",
  "Addresses": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J|BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW|BSVMHp2GMF2jag6yoididitrwJPoZaP1JK|BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs|B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4|BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm|BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8|BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa|BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD|BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx|BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh|BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j|BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M|BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug|BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo|BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7|BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm|BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp|BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk|BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS|BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu|BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg|BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7|BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG|BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r",
  "Amounts": "146834.01|292896.19|47055.02|776194.87|390013.70|18018.24|256966.17|37952.75|101668.65|36701.85|38431.81|8729.66|363665.02|3965.61|48305.91|37659.98|6094.80|5988.34|19322.37|904.90|11258.07|958.13|8436.90|2235.65|319.38",
  "pam_hash2": "0000000000000000000000000000000038eb4f0145166a60c10431e52fceb201",
  "votes_for_my_contract": 1,
"contract1": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,55.169,475629,15044,100,100,277512\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,277512\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,110.051,1981209,15044,75,100,277512\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.675,1981219,15044,100,100,277512\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,146.543,1981270,15044,100,100,277512\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.769,1981344,15044,60,100,277512\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,96.552,1981355,15044,100,100,277512\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.264,1981529,15044,100,100,277512\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,277512\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,38.195,1981615,15044,100,100,277512\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.787,1981648,15044,75,100,277512\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,277512\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.438,1981794,15044,100,100,277512\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.282,1981965,15044,75,100,277512\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,136.642,1982089,15044,75,100,277512\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.491,1982123,15044,60,100,277512\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,277512\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,18.151,1982463,15044,100,100,277512\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,14.146,1983490,15044,60,100,277512\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.285,1983588,15044,50,100,277512\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.245,1984116,15044,60,100,277512\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.263,1985116,15044,75,100,277512\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.342,1985935,15044,75,100,277512\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,277512\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,4.227,1987391,15044,60,100,277512\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.357,1987401,15044,25,100,277512\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.165,1987419,15044,75,100,277512\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.842,1987421,15044,60,100,277512\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.118,1987451,15044,25,100,277512\n<ROW>\n",
  "RequiredVotes": 3,
  "last_superblock": 0,
  "next_superblock": 33620,
  "cpid_count": 30,
  "total_magnitude": 999.6599999999999,
  "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: jaapgvk on March 08, 2018, 09:40:15 AM

Ok, lets try exec testvote, what is your primary contract filehash?

I guess it's '000000000000000000000000000000009e0baa65c110d216239a1e784e3c1409'?

Code: [Select]
root@jaapgvk2:/home/ubuntu/biblepay/src# ./biblepay-cli exec testvote
{
  "Command": "testvote",
  "fileage": 375,
  "filehash": "000000000000000000000000000000009e0baa65c110d216239a1e784e3c1409",
  "contract": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,55.169,475629,15044,100,100,277512\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,277512\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,110.051,1981209,15044,75,100,277512\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.675,1981219,15044,100,100,277512\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,146.543,1981270,15044,100,100,277512\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.769,1981344,15044,60,100,277512\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,96.552,1981355,15044,100,100,277512\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.264,1981529,15044,100,100,277512\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,277512\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,38.195,1981615,15044,100,100,277512\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.787,1981648,15044,75,100,277512\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,277512\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.438,1981794,15044,100,100,277512\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.282,1981965,15044,75,100,277512\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,136.642,1982089,15044,75,100,277512\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.491,1982123,15044,60,100,277512\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,277512\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,18.151,1982463,15044,100,100,277512\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,14.146,1983490,15044,60,100,277512\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.285,1983588,15044,50,100,277512\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.245,1984116,15044,60,100,277512\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.263,1985116,15044,75,100,277512\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.342,1985935,15044,75,100,277512\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,277512\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,4.227,1987391,15044,60,100,277512\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.357,1987401,15044,25,100,277512\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.165,1987419,15044,75,100,277512\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.842,1987421,15044,60,100,277512\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.118,1987451,15044,25,100,277512\n<ROW>\n",
  "sanctuary_rank": 100,
  "pam_hash": "0000000000000000000000000000000038eb4f0145166a60c10431e52fceb201",
  "govobjhash": "80cbe900009455a05a41ffe8c0d0b0bbe92c15708325be92bb05e308f2cf17ca",
  "Addresses": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J|BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW|BSVMHp2GMF2jag6yoididitrwJPoZaP1JK|BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs|B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4|BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm|BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8|BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa|BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD|BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx|BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh|BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j|BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M|BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug|BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo|BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7|BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm|BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp|BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk|BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS|BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu|BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg|BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7|BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG|BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r",
  "Amounts": "146834.01|292896.19|47055.02|776194.87|390013.70|18018.24|256966.17|37952.75|101668.65|36701.85|38431.81|8729.66|363665.02|3965.61|48305.91|37659.98|6094.80|5988.34|19322.37|904.90|11258.07|958.13|8436.90|2235.65|319.38",
  "pam_hash2": "0000000000000000000000000000000038eb4f0145166a60c10431e52fceb201",
  "votes_for_my_contract": 2,
  "contract1": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,55.169,475629,15044,100,100,277512\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,277512\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,110.051,1981209,15044,75,100,277512\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.675,1981219,15044,100,100,277512\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,291.640,1981221,15044,100,100,277512\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,146.543,1981270,15044,100,100,277512\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.769,1981344,15044,60,100,277512\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,96.552,1981355,15044,100,100,277512\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.264,1981529,15044,100,100,277512\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,277512\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,38.195,1981615,15044,100,100,277512\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.787,1981648,15044,75,100,277512\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,277512\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.438,1981794,15044,100,100,277512\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.282,1981965,15044,75,100,277512\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,136.642,1982089,15044,75,100,277512\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.491,1982123,15044,60,100,277512\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,277512\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,18.151,1982463,15044,100,100,277512\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,14.146,1983490,15044,60,100,277512\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.285,1983588,15044,50,100,277512\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.245,1984116,15044,60,100,277512\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.263,1985116,15044,75,100,277512\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.342,1985935,15044,75,100,277512\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,277512\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,4.227,1987391,15044,60,100,277512\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.357,1987401,15044,25,100,277512\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.165,1987419,15044,75,100,277512\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.842,1987421,15044,60,100,277512\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.118,1987451,15044,25,100,277512\n<ROW>\n",
  "RequiredVotes": 3,
  "last_superblock": 0,
  "next_superblock": 33620,
  "cpid_count": 30,
  "total_magnitude": 999.6599999999999,
  "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: jaapgvk on March 08, 2018, 09:42:50 AM
Biblepay
1.1.0.6 - Leisure Upgrade



- Make exec podcupdate much more robust (add error messages, fix utxo leg rounding)


** Note to All: please modify the Distributed Computing process in this way:
Retire the use of -polpercentage in your config files.
Use "utxoamount=50000" instead, where 50000 is the amount of UTXO you choose to stake in each podcupdate (this occurs approx. once per day).
Note - the default is now 50,000, so you do not need to set it if you desire 50,000 **

Anyone with 'exec getboincinfo' with less than 100 utxoweight, please 'exec podcupdate' to send a new UTXO using this new version.

** Windows is ready for download **

I followed the directions.
I already had a 100 utxoweight, and still have after updating from 1.1.0.2. to 1.1.0.6., so I don't have to do a 'exec podcupdate' after upgrading to 1.1.0.6. right?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:50:20 AM
I followed the directions.
I already had a 100 utxoweight, and still have after updating from 1.1.0.2. to 1.1.0.6., so I don't have to do a 'exec podcupdate' after upgrading to 1.1.0.6. right?
Right!  If anyone has an existing utxoweight, its completely compatible.


Great test on the sanc, our filehash matches, sweet.

10-4 Mike, same filehash, thanks!

EDIT: I think we do have a little work to do in a couple hours though!
See how we only have 3 votes for the newest "1409" contract?  We need way more, as the old version has a certain number of votes on that same height.  We need to pass that old version in votes.  I have to do some research to find the correct gobject though, ill check.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 09:59:54 AM
Right!  If anyone has an existing utxoweight, its completely compatible.


Great test on the sanc, our filehash matches, sweet.

10-4 Mike, same filehash, thanks!

EDIT: I think we do have a little work to do in a couple hours though!
See how we only have 3 votes for the newest "1409" contract?  We need way more, as the old version has a certain number of votes on that same height.  We need to pass that old version in votes.  I have to do some research to find the correct gobject though, ill check.
Looks like were going to be OK, the old one only has 4 votes so far.  The new one has 3 votes.  So we just need to keep an eye on that and make sure the new one is the kingpin by noon today.  'gobject list all triggers' . 80cbe900009455a05a41ffe8c0d0b0bbe92c15708325be92bb05e308f2cf17ca
is the good one, all others need to go down.

 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 10:11:05 AM
Looks like were going to be OK, the old one only has 4 votes so far.  The new one has 3 votes.  So we just need to keep an eye on that and make sure the new one is the kingpin by noon today.  'gobject list all triggers' . 80cbe900009455a05a41ffe8c0d0b0bbe92c15708325be92bb05e308f2cf17ca
is the good one, all others need to go down.

So what's the problem? Not enough Sanctuaries? Not sure how the whole voting thing works.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 10:13:49 AM
So what's the problem? Not enough Sanctuaries? Not sure how the whole voting thing works.
Not enough in the "ENABLED" state, which causes their rank to be low, and then auto-vote during each passing block.

We need to get people to run 'exec testvote' manually right now, so we coerce this particular contract through.

Then we look at auto for tomorrow.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 10:17:04 AM
I'm checking on the transaction when I sent BBP to my Rosetta address and it doesn't seem to be syncing correctly. mnsync status shows 999.
Code: [Select]
./biblepay-cli listreceivedbyaddress
[
  {
    "address": "BGmjr2mQNvSJ1faHGAo8FxtnUd98HGRkWK",
    "account": "b",
    "amount": 50005.00000000,
    "confirmations": 16,
    "bcconfirmations": 16,
    "label": "b",
    "txids": [
      "2f3cc129a739591f18d3ed17da186e6e545d125bae963ef1bbd571fee501295f"
    ]
  },
  {
    "address": "BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW",
    "account": "a",
    "amount": 100003.99970000,
    "confirmations": 5,
    "bcconfirmations": 5,
    "label": "a",
    "txids": [
      "871f1da32e25fd5dbee5411144a896d38ec3cb3359742cb6e08a6a02f6a72077",
      "0aa3218c417ab80e00a8d362ebfddf63eb3ea160e73445856c3d5ea59d1fa579",
      "69ef21f13ec4b4ad127377c24cc7fe000bb7348b0fbe9ec97846cbcb52685dcc"
    ]
  }
]

http://explorer.biblepay.org:3001/address/BGmjr2mQNvSJ1faHGAo8FxtnUd98HGRkWK

The transaction is not showing on my Sanctuary wallet, I tried restarting the daemon and zapping the wallet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 10:17:36 AM
** PODC ALERT **

Anyone with a Sanctuary, please ensure it is running 1.1.0.5+, then go to the console and type:

exec dcc

Wait for true

Then type:

exec testvote

We need to prime the sanctuaries ability to vote on PODC superblocks. 
The next superblock is coming at block 33620 (5 hours), so I would appreciate if you could do this over the next 4 hours.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 10:18:30 AM
Not enough in the "ENABLED" state, which causes their rank to be low, and then auto-vote during each passing block.

We need to get people to run 'exec testvote' manually right now, so we coerce this particular contract through.

Then we look at auto for tomorrow.

The ranking, is that the ranking shown when I ran ./biblepay-cli exec testvote? "sanctuary_rank": 0
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 10:19:19 AM
I'm checking on the transaction when I sent BBP to my Rosetta address and it doesn't seem to be syncing correctly. mnsync status shows 999.
Code: [Select]
./biblepay-cli listreceivedbyaddress
[
  {
    "address": "BGmjr2mQNvSJ1faHGAo8FxtnUd98HGRkWK",
    "account": "b",
    "amount": 50005.00000000,
    "confirmations": 16,
    "bcconfirmations": 16,
    "label": "b",
    "txids": [
      "2f3cc129a739591f18d3ed17da186e6e545d125bae963ef1bbd571fee501295f"
    ]
  },
  {
    "address": "BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW",
    "account": "a",
    "amount": 100003.99970000,
    "confirmations": 5,
    "bcconfirmations": 5,
    "label": "a",
    "txids": [
      "871f1da32e25fd5dbee5411144a896d38ec3cb3359742cb6e08a6a02f6a72077",
      "0aa3218c417ab80e00a8d362ebfddf63eb3ea160e73445856c3d5ea59d1fa579",
      "69ef21f13ec4b4ad127377c24cc7fe000bb7348b0fbe9ec97846cbcb52685dcc"
    ]
  }
]

http://explorer.biblepay.org:3001/address/BGmjr2mQNvSJ1faHGAo8FxtnUd98HGRkWK

The transaction is not showing on my Sanctuary wallet, I tried restarting the daemon and zapping the wallet.

What is the txid?

You pasted a wallet address, and a list of 3 transactions you already received.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 10:20:48 AM
The ranking, is that the ranking shown when I ran ./biblepay-cli exec testvote? "sanctuary_rank": 0

The 0 is a percent from 0-100, and anything below 10 is chosen, so in your case a zero means you would be auto-voting as each block goes by (actually once, then you would no longer be voting once your vote is registered).

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 10:23:57 AM
What is the txid?

You pasted a wallet address, and a list of 3 transactions you already received.

Sorry, transaction ID#0aa3218c417ab80e00a8d362ebfddf63eb3ea160e73445856c3d5ea59d1fa579 is not showing in my wallet.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 10:24:58 AM
"PODCUpdate": "Processed (275) over 1 CPID(s) successfully."

What does the 275 refer to?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 10:31:06 AM
Sorry, transaction ID#0aa3218c417ab80e00a8d362ebfddf63eb3ea160e73445856c3d5ea59d1fa579 is not showing in my wallet.

I see it here, so the network knows about it, its a 50k tx.  I would restart the node with -rescan=1.  That should pull the tx into your wallet.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 10:32:46 AM
I thought it was 50,001 to get 100%.

Good catch!  I just changed the default to 50,001 in the core wallet for the next release.

Ill go and mention this on the main thread now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 10:34:36 AM
Good catch!  I just changed the default to 50,001 in the core wallet for the next release.

Ill go and mention this on the main thread now.

Ha, no wonder my UTXO is 75%!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 10:35:30 AM
"PODCUpdate": "Processed (275) over 1 CPID(s) successfully."

What does the 275 refer to?

That means it found 275 running tasks, and verified 275.  Those are transmitted in the PODC update.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 10:36:08 AM
That means it found 275 running tasks, and verified 275.  Those are transmitted in the PODC update.

Thanks!  ;D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 11:21:42 AM
Although when I hard coded the utxoweight=50001 in the biblepay.conf, my utxweight % dropped to 75.

exec stakebalance still shows a larger balance as well

We will need the utxo txid to look into the problem.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 11:23:42 AM
The ranking, is that the ranking shown when I ran ./biblepay-cli exec testvote? "sanctuary_rank": 0

So on the surface the sancs appear to be voting now, some are voting by themselves, and I was just thinking, we are probably better off waiting a couple more hours before rallying on this, as the contract is going to be very volatile especially on Day #1, due to : new cpids, changing UTXO weights, and changing task weights.

So I think we should rally 10 blocks before the superblock and ensure we have some good votes on the last contract.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 11:24:43 AM
We will need the utxo txid to look into the problem.

Rob, in linux setting UTXO amount to 50001 seems to work but in Windows GUI it only sends 50K even if I have it set to 50,001.

Status: 1/unconfirmed
Date: 3/8/2018 11:51
Source: PODC-Update
Total debit: -50 000.00000000 Biblepay
Total credit: 50 000.00000000 Biblepay
Transaction fee: -0.00024800 Biblepay
Net amount: -0.00024800 Biblepay

Height: 33577
Difficulty: 0.000000
Time: 03-08-2018 17:10:22
Subsidy: 548.9591

PODC_UPDATE:
Transaction ID: 54d3a57949390808a8a06d9437ba29f01e10939c21e86b97968c3b6d5d19fe92-000

Headless podcupdate: http://explorer.biblepay.org:3001/tx/3f7ee6921f2aec3870f810f63d10547ebd8e4b6424292bd54196c9fd74d82532
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 11:25:38 AM
** PODC ALERT **

Anyone with a Sanctuary, please ensure it is running 1.1.0.5+, then go to the console and type:

exec dcc

Wait for true

Then type:

exec testvote

We need to prime the sanctuaries ability to vote on PODC superblocks. 
The next superblock is coming at block 33620 (5 hours), so I would appreciate if you could do this over the next 4 hours.

I just this this with my other sanctuary (1.1.0.5.), and it returned a different filehash:

Code: [Select]
{
  "Command": "testvote",
  "fileage": 15,
  "filehash": "00000000000000000000000000000000f95e8a52876afe8e8a8f025f47b97d9d",
  "contract": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,54.339,475629,15044,100,100,281752\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,281752\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,144.526,1981209,15044,100,100,281752\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.409,1981219,15044,100,100,281752\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,287.252,1981221,15044,100,100,281752\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,144.338,1981270,15044,100,100,281752\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.667,1981344,15044,60,100,281752\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,71.325,1981355,15044,75,100,281752\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.049,1981529,15044,100,100,281752\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,281752\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,37.621,1981615,15044,100,100,281752\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.579,1981648,15044,75,100,281752\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,281752\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.220,1981794,15044,100,100,281752\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.232,1981965,15044,75,100,281752\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,134.586,1982089,15044,75,100,281752\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.469,1982123,15044,60,100,281752\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,281752\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,17.878,1982463,15044,100,100,281752\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,13.934,1983490,15044,60,100,281752\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.251,1983588,15044,50,100,281752\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.211,1984116,15044,60,100,281752\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.153,1985116,15044,75,100,281752\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.253,1985935,15044,75,100,281752\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,281752\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,6.939,1987391,15044,100,100,281752\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.351,1987401,15044,25,100,281752\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.118,1987419,15044,75,100,281752\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.829,1987421,15044,60,100,281752\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.117,1987451,15044,25,100,281752\n<ROW>\n",
  "sanctuary_rank": 0,
  "pam_hash": "00000000000000000000000000000000c44ca39dcbab98c0fe8d05b33a33af87",
  "govobjhash": "0000000000000000000000000000000000000000000000000000000000000000",
  "Addresses": "",
  "Amounts": "",
  "pam_hash2": "0000000000000000000000000000000000000000000000000000000000000000",
  "quorum_hex": "5b5b2274726967676572222c7b226576656e745f626c6f636b5f686569676874223a33333632302c227061796d656e745f616464726573736573223a22425377374a5a39723263464c674c4c377467366f444b445769634747477a5866344a7c42546a4a454e6d5772517564464845617145704667375a65434138484b3248774c577c4253564d487032474d46326a616736796f69646964697472774a506f5a6150314a4b7c425365617857546464516d4c6d5643475a4265315474436579644e79677033797a737c42366e3644796d70625a4b4435476f453645583475573852767267365165503952347c4250396463325868426168416d775263767461775364596d3748634745655777436d7c42536d666d3372514248416b63654a694e785556444865755643675162544a5278387c42514a65755739637a4e7037584a47464531317344787169666159734b53486d47617c425371634c63464c597433624b766f55615a357247555257373578676a4a64516f447c42526e4a6355653366437573455839513936317a70774e4a386a4d74524a6a344d787c424e657478735a666a794e665737334b7673683541594c48454e70454863523371687c4254395233454c4d38317233755338614d6e4b7a5071324d6d34396d44415678356a7c4245614a52506f4866517375366938737841744e4170696159673765586d4253314d7c424c5352617569575a316f5a53587635587573397a524a744e5139767534513875677c424d626a6261595279694176636f6b4a38695a797442743573463853524e646d666f7c424e53736e686b623462416d416f5945545442796f41364751437379347643354d377c42426b706856706445644a53767a47456547526b517234506b474d4b64426d42716d7c424b44657a4456417742387659766145576367784c707575597162536144716d56707c42485434324b6e56705170417a59676e564a75564571427a327070314a665447596b7c424c48646f483844394556705477315a39445957536b4c6d51654c594431676d51537c424e656a7055323273674d763351634779745674716565666761416d547a344a43757c424b616537514d363941545a596b68746b4465774c6d754a717439347a466a334c677c424c554277756a537838775a4862754567575a4d727153454e65634e566a79687a377c4252414665477868384e575a7243567a4b6f547971764e4c784447786f5a374a7a477c42506d4d535568395a6847707a4132614d574a516d66453439384e4c786f64433472222c227061796d656e745f616d6f756e7473223a223134343632342e39387c3338343636342e31327c34363333362e34327c3736343531302e39367c3338343135382e34347c31373735322e30397c3138393834332e35387c33373339332e38337c3130303132342e39397c33363134322e39347c33373834362e32397c383539362e35397c3335383230382e39387c333931322e33387c34373538372e33317c33373037342e34367c353938382e33347c353838312e38387c31393032392e36307c3636352e33377c31383437302e36397c3933312e35327c383330332e38337c323230392e30337c3331392e3338222c2270726f706f73616c5f686173686573223a2230303030303030303030303030303030303030303030303030303030303030306639356538613532383736616665386538613866303235663437623937643964222c2274797065223a327d5d5d",
  "quorum_gobject_trigger_hash": "2ba714d893359aef68418c68de9b586eb720d6dfe5bf95fce51f6e65fd20a138",
  "quorum_error": "",
  "votes_for_my_contract": 0,
  "contract1": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,54.339,475629,15044,100,100,281752\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,281752\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,144.526,1981209,15044,100,100,281752\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.409,1981219,15044,100,100,281752\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,287.252,1981221,15044,100,100,281752\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,144.338,1981270,15044,100,100,281752\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.667,1981344,15044,60,100,281752\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,71.325,1981355,15044,75,100,281752\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.049,1981529,15044,100,100,281752\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,281752\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,37.621,1981615,15044,100,100,281752\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.579,1981648,15044,75,100,281752\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,281752\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.220,1981794,15044,100,100,281752\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.232,1981965,15044,75,100,281752\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,134.586,1982089,15044,75,100,281752\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.469,1982123,15044,60,100,281752\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,281752\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,17.878,1982463,15044,100,100,281752\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,13.934,1983490,15044,60,100,281752\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.251,1983588,15044,50,100,281752\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.211,1984116,15044,60,100,281752\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.153,1985116,15044,75,100,281752\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.253,1985935,15044,75,100,281752\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,281752\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,6.939,1987391,15044,100,100,281752\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.351,1987401,15044,25,100,281752\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.118,1987419,15044,75,100,281752\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.829,1987421,15044,60,100,281752\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.117,1987451,15044,25,100,281752\n<ROW>\n",
  "RequiredVotes": 3,
  "last_superblock": 0,
  "next_superblock": 33620,
  "cpid_count": 30,
  "total_magnitude": 999.6600000000002,
  "next_superblock_triggered": true,
  "vote1": true,
  "vote1error": "",
  "serial": "",
  "verified_sigs": 0

Is this okay, or do I have to change anything?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 12:10:38 PM
Rob, in linux setting UTXO amount to 50001 seems to work but in Windows GUI it only sends 50K even if I have it set to 50,001.

Status: 1/unconfirmed
Date: 3/8/2018 11:51
Source: PODC-Update
Total debit: -50 000.00000000 Biblepay
Total credit: 50 000.00000000 Biblepay
Transaction fee: -0.00024800 Biblepay
Net amount: -0.00024800 Biblepay

Height: 33577
Difficulty: 0.000000
Time: 03-08-2018 17:10:22
Subsidy: 548.9591

PODC_UPDATE:
Transaction ID: 54d3a57949390808a8a06d9437ba29f01e10939c21e86b97968c3b6d5d19fe92-000

Headless podcupdate: http://explorer.biblepay.org:3001/tx/3f7ee6921f2aec3870f810f63d10547ebd8e4b6424292bd54196c9fd74d82532


No, I tried it from the windows latest (v1006) and it worked for me - please verify you have the right key and case setting:

utxoamount=50007


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 12:11:31 PM
I just this this with my other sanctuary (1.1.0.5.), and it returned a different filehash:

Code: [Select]
{
  "Command": "testvote",
  "fileage": 15,
  "filehash": "00000000000000000000000000000000f95e8a52876afe8e8a8f025f47b97d9d",
  "contract": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,54.339,475629,15044,100,100,281752\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,281752\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,144.526,1981209,15044,100,100,281752\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.409,1981219,15044,100,100,281752\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,287.252,1981221,15044,100,100,281752\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,144.338,1981270,15044,100,100,281752\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.667,1981344,15044,60,100,281752\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,71.325,1981355,15044,75,100,281752\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.049,1981529,15044,100,100,281752\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,281752\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,37.621,1981615,15044,100,100,281752\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.579,1981648,15044,75,100,281752\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,281752\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.220,1981794,15044,100,100,281752\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.232,1981965,15044,75,100,281752\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,134.586,1982089,15044,75,100,281752\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.469,1982123,15044,60,100,281752\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,281752\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,17.878,1982463,15044,100,100,281752\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,13.934,1983490,15044,60,100,281752\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.251,1983588,15044,50,100,281752\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.211,1984116,15044,60,100,281752\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.153,1985116,15044,75,100,281752\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.253,1985935,15044,75,100,281752\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,281752\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,6.939,1987391,15044,100,100,281752\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.351,1987401,15044,25,100,281752\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.118,1987419,15044,75,100,281752\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.829,1987421,15044,60,100,281752\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.117,1987451,15044,25,100,281752\n<ROW>\n",
  "sanctuary_rank": 0,
  "pam_hash": "00000000000000000000000000000000c44ca39dcbab98c0fe8d05b33a33af87",
  "govobjhash": "0000000000000000000000000000000000000000000000000000000000000000",
  "Addresses": "",
  "Amounts": "",
  "pam_hash2": "0000000000000000000000000000000000000000000000000000000000000000",
  "quorum_hex": "5b5b2274726967676572222c7b226576656e745f626c6f636b5f686569676874223a33333632302c227061796d656e745f616464726573736573223a22425377374a5a39723263464c674c4c377467366f444b445769634747477a5866344a7c42546a4a454e6d5772517564464845617145704667375a65434138484b3248774c577c4253564d487032474d46326a616736796f69646964697472774a506f5a6150314a4b7c425365617857546464516d4c6d5643475a4265315474436579644e79677033797a737c42366e3644796d70625a4b4435476f453645583475573852767267365165503952347c4250396463325868426168416d775263767461775364596d3748634745655777436d7c42536d666d3372514248416b63654a694e785556444865755643675162544a5278387c42514a65755739637a4e7037584a47464531317344787169666159734b53486d47617c425371634c63464c597433624b766f55615a357247555257373578676a4a64516f447c42526e4a6355653366437573455839513936317a70774e4a386a4d74524a6a344d787c424e657478735a666a794e665737334b7673683541594c48454e70454863523371687c4254395233454c4d38317233755338614d6e4b7a5071324d6d34396d44415678356a7c4245614a52506f4866517375366938737841744e4170696159673765586d4253314d7c424c5352617569575a316f5a53587635587573397a524a744e5139767534513875677c424d626a6261595279694176636f6b4a38695a797442743573463853524e646d666f7c424e53736e686b623462416d416f5945545442796f41364751437379347643354d377c42426b706856706445644a53767a47456547526b517234506b474d4b64426d42716d7c424b44657a4456417742387659766145576367784c707575597162536144716d56707c42485434324b6e56705170417a59676e564a75564571427a327070314a665447596b7c424c48646f483844394556705477315a39445957536b4c6d51654c594431676d51537c424e656a7055323273674d763351634779745674716565666761416d547a344a43757c424b616537514d363941545a596b68746b4465774c6d754a717439347a466a334c677c424c554277756a537838775a4862754567575a4d727153454e65634e566a79687a377c4252414665477868384e575a7243567a4b6f547971764e4c784447786f5a374a7a477c42506d4d535568395a6847707a4132614d574a516d66453439384e4c786f64433472222c227061796d656e745f616d6f756e7473223a223134343632342e39387c3338343636342e31327c34363333362e34327c3736343531302e39367c3338343135382e34347c31373735322e30397c3138393834332e35387c33373339332e38337c3130303132342e39397c33363134322e39347c33373834362e32397c383539362e35397c3335383230382e39387c333931322e33387c34373538372e33317c33373037342e34367c353938382e33347c353838312e38387c31393032392e36307c3636352e33377c31383437302e36397c3933312e35327c383330332e38337c323230392e30337c3331392e3338222c2270726f706f73616c5f686173686573223a2230303030303030303030303030303030303030303030303030303030303030306639356538613532383736616665386538613866303235663437623937643964222c2274797065223a327d5d5d",
  "quorum_gobject_trigger_hash": "2ba714d893359aef68418c68de9b586eb720d6dfe5bf95fce51f6e65fd20a138",
  "quorum_error": "",
  "votes_for_my_contract": 0,
  "contract1": "BSw7JZ9r2cFLgLL7tg6oDKDWicGGGzXf4J,ca895b47aacffbdbf906201821af2f9f,54.339,475629,15044,100,100,281752\n<ROW>BScSypUZVEEY4TMz1ehyyPcS5wrnMM7WPB,c9085154b7cc0ca2b5189672559dd6d8,0.000,1084150,15044,50,0,281752\n<ROW>BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,144.526,1981209,15044,100,100,281752\n<ROW>BSVMHp2GMF2jag6yoididitrwJPoZaP1JK,4004b7fec94751f61fe9135977bac553,17.409,1981219,15044,100,100,281752\n<ROW>BSeaxWTddQmLmVCGZBe1TtCeydNygp3yzs,93138f032bdd027fa3246b48bb715a77,287.252,1981221,15044,100,100,281752\n<ROW>B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4,8f273b30f8e0a298ed26e242762df701,144.338,1981270,15044,100,100,281752\n<ROW>BP9dc2XhBahAmwRcvtawSdYm7HcGEeWwCm,96892ec0fc8a2710fa84f26c9c84cd3e,6.667,1981344,15044,60,100,281752\n<ROW>BSmfm3rQBHAkceJiNxUVDHeuVCgQbTJRx8,e7ae6abd6284b05f3fd5f7c780e60bc7,71.325,1981355,15044,75,100,281752\n<ROW>BQJeuW9czNp7XJGFE11sDxqifaYsKSHmGa,04fba56d89a5eb38b1b82f8a6240132c,14.049,1981529,15044,100,100,281752\n<ROW>BSHPizQ1MV6gXGnZDGTk6Jp4hBZRkb4HKY,fe553a955f0e21d46724858870014cbe,0.000,1981585,15044,0,0,281752\n<ROW>BSqcLcFLYt3bKvoUaZ5rGURW75xgjJdQoD,d9b22fccfae5582d4ee7838883aaa3cf,37.621,1981615,15044,100,100,281752\n<ROW>BRnJcUe3fCusEX9Q961zpwNJ8jMtRJj4Mx,8735cfe64d964416dba6015eb414cf7e,13.579,1981648,15044,75,100,281752\n<ROW>B9hCrvkS6ZAt3KftgLyiSg33kygao9PZDw,962b0d76dfb35f07b73f81a67ffc28b1,0.000,1981678,15044,0,100,281752\n<ROW>BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh,7c9264559fef3c1c689ee9fc3ff42494,14.220,1981794,15044,100,100,281752\n<ROW>BT9R3ELM81r3uS8aMnKzPq2Mm49mDAVx5j,6785ded1f65063ef8f01f42deb31cf1d,3.232,1981965,15044,75,100,281752\n<ROW>BEaJRPoHfQsu6i8sxAtNApiaYg7eXmBS1M,dde30f3ef57ed2df69ecbc687db75e46,134.586,1982089,15044,75,100,281752\n<ROW>BLSRauiWZ1oZSXv5Xus9zRJtNQ9vu4Q8ug,e7c056024cd3b781edd5af37965c652c,1.469,1982123,15044,60,100,281752\n<ROW>BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx,1e7184e17377549d5a7d7a2edfb51017,0.000,1982314,15044,0,0,281752\n<ROW>BMbjbaYRyiAvcokJ8iZytBt5sF8SRNdmfo,84d803e4d82d3bdcdf8e2ab601e93e20,17.878,1982463,15044,100,100,281752\n<ROW>BNSsnhkb4bAmAoYETTByoA6GQCsy4vC5M7,265d57ea664dbb5005f2db7b73d343b9,13.934,1983490,15044,60,100,281752\n<ROW>BBkphVpdEdJSvzGEeGRkQr4PkGMKdBmBqm,9e7c5405d65d2603ef4143e9b7a0eb7d,2.251,1983588,15044,50,100,281752\n<ROW>BKDezDVAwB8vYvaEWcgxLpuuYqbSaDqmVp,a9420a038e44750c69ca4497fe08c2a9,2.211,1984116,15044,60,100,281752\n<ROW>BHT42KnVpQpAzYgnVJuVEqBz2pp1JfTGYk,e6ce50042187d4b285568d86ef458f32,7.153,1985116,15044,75,100,281752\n<ROW>BLHdoH8D9EVpTw1Z9DYWSkLmQeLYD1gmQS,4b7d2d64c88b32927a21ad20a57868e4,0.253,1985935,15044,75,100,281752\n<ROW>BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ,c852da1a620ad630b70c8ec1ccdee366,0.000,1985966,15044,0,0,281752\n<ROW>BNejpU22sgMv3QcGytVtqeefgaAmTz4JCu,8aee6972dd6958234c4d813978e2ee20,6.939,1987391,15044,100,100,281752\n<ROW>BKae7QM69ATZYkhtkDewLmuJqt94zFj3Lg,b1afc0756ab888f55d90ab39396ea8b9,0.351,1987401,15044,25,100,281752\n<ROW>BLUBwujSx8wZHbuEgWZMrqSENecNVjyhz7,1414175ac4ea3dfbb9fb7caf13540319,3.118,1987419,15044,75,100,281752\n<ROW>BRAFeGxh8NWZrCVzKoTyqvNLxDGxoZ7JzG,982538340112287ed60723499adfeb4b,0.829,1987421,15044,60,100,281752\n<ROW>BPmMSUh9ZhGpzA2aMWJQmfE498NLxodC4r,6bcd1f25dc07679db5ad812a012df1a4,0.117,1987451,15044,25,100,281752\n<ROW>\n",
  "RequiredVotes": 3,
  "last_superblock": 0,
  "next_superblock": 33620,
  "cpid_count": 30,
  "total_magnitude": 999.6600000000002,
  "next_superblock_triggered": true,
  "vote1": true,
  "vote1error": "",
  "serial": "",
  "verified_sigs": 0

Is this okay, or do I have to change anything?

I think we have to wait a couple more hours then look at the volatile contract.

Its probably changing right now as we have new researchers every few minutes.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 12:25:01 PM

No, I tried it from the windows latest (v1006) and it worked for me - please verify you have the right key and case setting:

utxoamount=50007

I just tried it again, still 50k.

Code: [Select]
Status: 1/unconfirmed, broadcast through 8 nodes
Date: 3/8/2018 13:14
Source: PODC-Update
Total debit: -50 000.00000000 Biblepay
Total credit: 50 000.00000000 Biblepay
Transaction fee: -0.00024820 Biblepay
Net amount: -0.00024820 Biblepay

Height: 33585
Difficulty: 0.000000
Time: 03-08-2018 18:19:47
Subsidy: 552.9925

PODC_UPDATE:
Transaction ID: 3ea40681590759a0650b01cae89cc479c011456a9190f11a353aaa38bbec8a1a-000



Debug information

Debit: -53 475.15474690 Biblepay
Credit: 3475.15449870 Biblepay
Credit: 50 000.00000000 Biblepay

Transaction:
CTransaction(hash=3ea4068159, ver=1, vin.size=1, vout.size=2, nLockTime=33583)
    CTxIn(COutPoint(64f6db86d3b6ddad02db67d26eab80c5862c48de135943262a0b44ccd56bd88f, 0), scriptSig=473044022028f7f0c2529fc9, nSequence=4294967294)
    CTxOut(nValue=3475.15449870, scriptPubKey=76a914a65e672d083ccaea7050796a)
    CTxOut(nValue=50000.00000000, scriptPubKey=76a914adb8b79afbfdde04837d1553)

Inputs:

getinfo
  "version": 1010006,
  "protocolversion": 70717,
  "walletversion": 61000,
  "wallet_fullversion": "1.1.0.6",

addnode=node.biblepay.org
addnode=biblepay.inspect.network
gen=1
genproclimit=1
utxoamount=50001

I'll try a few things.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 12:26:36 PM
I think we have to wait a couple more hours then look at the volatile contract.

Its probably changing right now as we have new researchers every few minutes.

Oh, yeah. I've studied the data and I understand how it works now :) Thx!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 01:09:20 PM
Not sure what's going on but my UTXO weight is 100 now even though the previous podcupdate was 50k.

I deleted the chain and started over, made another podcupdate with 50,007 but it's still only sending 50k. I wonder if it's reading biblepay.conf.

podcupdate lastest transaction: d2cb2454c78342181373632e0f623340921f264a0a9d44c464447820e14c78f1 (May not be searchable yet.)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 01:29:12 PM
Not sure what's going on but my UTXO weight is 100 now even though the previous podcupdate was 50k.

I deleted the chain and started over, made another podcupdate with 50,007 but it's still only sending 50k. I wonder if it's reading biblepay.conf.

podcupdate lastest transaction: d2cb2454c78342181373632e0f623340921f264a0a9d44c464447820e14c78f1 (May not be searchable yet.)
Sounds like you might have a persmission issue on windows.
Try adding 'genproclimit=5' in your biblepay.conf, then restart wallet and see if getmininginfo honors the setting.
Also, see if debug.log (in the same place as biblepay.conf) has the latest timestamp from running biblepay in it.
If it doesnt you arent using the right datadir.

EDIT:

Ok, it looks like that transaction is for 3475+50000=53475, that explains why you have 100.
Looking at exec datalist utxoweight, your 4b7* cpid does have 100! Your set.

Just see if you can figure out why your datadir is not aligning

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 08, 2018, 01:39:24 PM
Hi,

I am now on 1.1.0.6 and I tried this:

Code: [Select]
20:33:32
exec podcupdate true
20:33:37
{
  "Command": "podcupdate",
  "PODCUpdate": "Processed 0 tasks for CPID 1e7184e17377549d5a7d7a2edfb51017"
}


20:33:47
exec getboincinfo
20:33:48
{
  "Command": "getboincinfo",
  "CPID": "1e7184e17377549d5a7d7a2edfb51017",
  "Address": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "CPIDS": "1e7184e17377549d5a7d7a2edfb51017;",
  "CPID-Age (hours)": 422371,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 2660579,
  "1e7184e17377549d5a7d7a2edfb51017_ADDRESS": "BNGti4oyDRU4YEBrbqQcmgEVR9t5VNbTUx",
  "1e7184e17377549d5a7d7a2edfb51017_RAC": 10259.47,
  "1e7184e17377549d5a7d7a2edfb51017_TEAM": 15044,
  "1e7184e17377549d5a7d7a2edfb51017_TaskWeight": 0,
  "1e7184e17377549d5a7d7a2edfb51017_UTXOWeight": 0,
  "Total_RAC": 10259.47,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -1,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Any clues would be helpful. Thanks.
Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 02:30:58 PM
Sounds like you might have a persmission issue on windows.
Try adding 'genproclimit=5' in your biblepay.conf, then restart wallet and see if getmininginfo honors the setting.
Also, see if debug.log (in the same place as biblepay.conf) has the latest timestamp from running biblepay in it.
If it doesnt you arent using the right datadir.

EDIT:

Ok, it looks like that transaction is for 3475+50000=53475, that explains why you have 100.
Looking at exec datalist utxoweight, your 4b7* cpid does have 100! Your set.

Just see if you can figure out why your datadir is not aligning

OK, I deleted everything and reinstalled the wallet. Copy pasted the conf files back in. Works now. Thanks.

I didn't know what that 3475 BBP transaction was, was it supposed to send more then 50k?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 02:53:47 PM
OK, I deleted everything and reinstalled the wallet. Copy pasted the conf files back in. Works now. Thanks.

I didn't know what that 3475 BBP transaction was, was it supposed to send more then 50k?

Oh I think I see whats happening there; You had two coins, 50K & 3.475K, the wallet chose those for your 50K stake and sent you the change, so that explains how you got lucky and made it.

No, whatever you choose in utxoamount it will honor to the penny, I think the issue is if people have large unbroken "bills" they will get a little more stakeweight in there.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 02:56:07 PM
Turns out was a typo on my part, that then caused the tx to be the default 50K (not 50K+1).  I got the typo corrected and just made the line in biblepay.conf utxoamount=55555 so it would stand out pretty easily.

Great!  We're coming together now, awesome!

We are rocketing up fast....

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 03:16:19 PM
About the 'associate unbanked CPID' function on the pool:

A few days ago, I successfully used this function to associate my android phone on a Rosetta test-account (CPID: 8791a036b545f35e9ebd9333922738ac).
I used the following BBP adress: BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj

Today I wondered if this burn survived yesterdays chaos, so I looked it up via 'exec datalist dcc' and it gave me the following:

Code: [Select]
  "8791A036B545F35E9EBD9333922738AC (03-04-2018 20:56:07)": "8791a036b545f35e9ebd9333922738ac;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J;1986929;IH0X/f06jDB7DGrsuew6YOgCwq5DPEcPZjW1hvd11BmvbNlPVOo/O6/RNYi028zk6i2pef0hh4dSMw9j3rqpFYU=",
There is a different Biblepay adress here: BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J

Looking at the transactions, it seems to be a pool-address: http://explorer.biblepay.org:3001/address/BSfnH2uxp8zm8cCmdxVLji7paJz6zNPd7J

I guess this happened because the code on the pool-side wasn't ready yet (Rob was surprised my association was successful at the time, haha!).

Anyway, my question to Rob is: should I just make a new test-account, or could you re-associate it to the correct address for me? It's just for testing anyway, so it doesn't really matter to me in terms of BBP (that's for the pool as far as I'm concerned). Just wanted to let you know :)

Just quoting for visibility, but it's not a priority.

I just tried 'cat magnitude | grep 8791', but I can't find my CPID.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 03:26:51 PM
Just quoting for visibility, but it's not a priority.

I just tried 'cat magnitude | grep 8791', but I can't find my CPID.

Yes, I confirm I do not see you in my cat magnitude either, but I do see you here:
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1986929
And you are in the team, and I see you in 'exec datalist dcc' | filter by 8791, and I see your association (which I think was done from the pool?), so now the question is , why are you not unbanked, and also I see you here:
exec unbanked

So, let me debug the Sanc Quorum side and see why, as its still pretty important to get all changes in by this weekend so we dont have to change anything in prod after the exchanges go live :), Ill check it out.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 03:32:56 PM
Yes, I confirm I do not see you in my cat magnitude either, but I do see you here:
https://boinc.bakerlab.org/rosetta/show_user.php?userid=1986929
And you are in the team, and I see you in 'exec datalist dcc' | filter by 8791, and I see your association (which I think was done from the pool?), so now the question is , why are you not unbanked, and also I see you here:
exec unbanked

So, let me debug the Sanc Quorum side and see why, as its still pretty important to get all changes in by this weekend so we dont have to change anything in prod after the exchanges go live :), Ill check it out.

Yes, it was made from the pool. You were surprised that it worked at the time because it the pool wasn't upgraded yet (don't know which wallet the pool was on but it was at least pre 1.0.9.9. I think).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 03:45:30 PM
Yes, it was made from the pool. You were surprised that it worked at the time because it the pool wasn't upgraded yet (don't know which wallet the pool was on but it was at least pre 1.0.9.9. I think).
Hi Jaap,
I think that is the problem; looking at the burn record, its missing a field.  The pool was running old software when we created the "unbanked" protocol version.  So it signed the CPID the old way.  I just upgraded the pool server to 1106.

Will you please try to re-associate your unbanked CPID from the pool now?

Then after 5 confirms, lets look at this again and see if the exec dcc actually pulls the unbanked cpid in.

It will be interesting how many votes your contract gets vs. the prod contract.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 04:42:59 PM
Hi Jaap,
I think that is the problem; looking at the burn record, its missing a field.  The pool was running old software when we created the "unbanked" protocol version.  So it signed the CPID the old way.  I just upgraded the pool server to 1106.

Will you please try to re-associate your unbanked CPID from the pool now?

Then after 5 confirms, lets look at this again and see if the exec dcc actually pulls the unbanked cpid in.

It will be interesting how many votes your contract gets vs. the prod contract.

Hi Rob,

I just tried and it said:
"RPC Error"
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 04:52:20 PM
Hi Rob,

I just tried and it said:
"RPC Error"

Oh wow, OK, please ensure the screen says v1.2 and please try again?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 08, 2018, 04:56:51 PM
Oh wow, OK, please ensure the screen says v1.2 and please try again?

Forgot to refresh :o It said 1.2 now (but the confirmation screen still says 1.1).

It now said: "private key not available" (see screenshot).
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 05:52:56 PM
Congratulations and thank you all for a successful PODC Go-Live!


(I'll keep this thread open so we can finish the finer details...)

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 05:53:28 PM
Forgot to refresh :o It said 1.2 now (but the confirmation screen still says 1.1).

It now said: "private key not available" (see screenshot).


Hmm, OK Ill check further in a little bit.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 08, 2018, 06:45:43 PM
I change utxoweight to 50001 and utxo is still showing 75. Any ideas?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 06:54:53 PM
I change utxoweight to 50001 and utxo is still showing 75. Any ideas?
utxoamount=50001
then do exec podcupdate true
and wait a few blocks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 06:56:31 PM
Shouldn't the network hashrate be lower than 7.6 ghs/s? Is solo mining feasible now?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 08, 2018, 07:04:21 PM
utxoamount=50001
then do exec podcupdate true
and wait a few blocks

This is what I get when I try to exec podcupdate true. I have 50010.99 in my wallet.

Code: [Select]
19:01:52

exec podcupdate true


19:02:00

{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (10.00) less than target UTXO (50001.00)."
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 07:11:05 PM
This is what I get when I try to exec podcupdate true. I have 50010.99 in my wallet.

Code: [Select]
19:01:52

exec podcupdate true


19:02:00

{
  "Command": "podcupdate",
  "PODCUpdate": "Unable to create PODC UTXO::Balance (10.00) less than target UTXO (50001.00)."
}

The staking BBP needs to have 6 or more confirmations. try exec stakebalance and see if it's 50,001 or above or go into coin control and see if you have more than 50,001 BBP that have more than 6 confirmations.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 08, 2018, 07:14:27 PM
The staking BBP needs to have 6 or more confirmations. try exec stakebalance and see if it's 50,001 or above.

Staking showed over 50k so I ran exec podcupdate true. I will wait 6 confirmations and check utxo again.

Code: [Select]
19:12:32

exec podcupdate true


19:12:41

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (25) over 1 CPID(s) successfully."
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 07:41:30 PM
Staking showed over 50k so I ran exec podcupdate true. I will wait 6 confirmations and check utxo again.

Code: [Select]
19:12:32

exec podcupdate true


19:12:41

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (25) over 1 CPID(s) successfully."
}

Look at the podcupdate transaction, how much did it send to yourself?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 08, 2018, 07:45:30 PM
Look at the podcupdate transaction, how much did it send to yourself?

Thanks! Already showing UTXO 100.
Code: [Select]
Status: 2/unconfirmed
Date: 3/8/2018 19:12
Source: PODC-Update
Total debit: -50 001.00000000 Biblepay
Total credit: 50 001.00000000 Biblepay
Transaction fee: -0.00042040 Biblepay
Net amount: -0.00042040 Biblepay

Height: 33628
Difficulty: 90.597458
Time: 03-09-2018 01:19:59
Subsidy: 554.3015
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 07:57:05 PM
Thanks! Already showing UTXO 100.
Code: [Select]
Status: 2/unconfirmed
Date: 3/8/2018 19:12
Source: PODC-Update
Total debit: -50 001.00000000 Biblepay
Total credit: 50 001.00000000 Biblepay
Transaction fee: -0.00042040 Biblepay
Net amount: -0.00042040 Biblepay

Height: 33628
Difficulty: 90.597458
Time: 03-09-2018 01:19:59
Subsidy: 554.3015

Oh good that's correct. So just wait a little bit.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 08:20:30 PM

Hmm, OK Ill check further in a little bit.

So it was a combination of core parts of the code requiring very high security for each element of the signed cpid.  We basically had to allow the unbanked CPID to be included in the contract under very specific circumstances.

So this requires an upgrade for all sancs, but I think what we can do so as not to disrupt the whole network is check it in as a leisure, and as people upgrade eventually these unbanked pool cpids will be paid.  I just tested it and the change worked on my sanc.

Ill check it in later tonight - Im creating a search feature for DCC that allows us to search for data.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 08, 2018, 08:24:54 PM
Shouldn't the network hashrate be lower than 7.6 ghs/s? Is solo mining feasible now?

Im pool mining on one quad core server - its maxxed out on boinc @ 100% and I have 40 threads running on the pool, its actually making more money in the pool than ever (about 200 BBP in the last 8 hours) - not sure about solo yet.

Ill check into this networkhashps, its probably stuck using some bad data.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 08, 2018, 08:49:47 PM
Im pool mining on one quad core server - its maxxed out on boinc @ 100% and I have 40 threads running on the pool, its actually making more money in the pool than ever (about 200 BBP in the last 8 hours) - not sure about solo yet.

Ill check into this networkhashps, its probably stuck using some bad data.

OK good because it didn't seem right, there should only be a few people with active cpids. Speaking of which, if both weights are zero, will there still be any hashing on that wallet?

By the way, I was trying minersleep=0 and genproclimit=6 and it would crash after a while.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 08, 2018, 09:53:36 PM
Did the block times improve?
Do we need more hash power on PoBH?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 09, 2018, 02:02:24 AM
Rob,

If you can do some debugging for my case I would really appreciate it.
I am on version 1.1.0.6 Win64 and I still can't get it to work. UTXOWeight, TaskWeight and Magnitude are still zero. I am on Biblepay team as DaytripperSimon.

Code: [Select]
exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 104283
}

exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Processed 0 tasks for CPID 1e7184e17377549d5a7d7a2edfb51017"
}

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

Thanks.

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 02:43:49 AM
Rob,

If you can do some debugging for my case I would really appreciate it.
I am on version 1.1.0.6 Win64 and I still can't get it to work. UTXOWeight, TaskWeight and Magnitude are still zero. I am on Biblepay team as DaytripperSimon.

Code: [Select]
exec stakebalance
{
  "Command": "stakebalance",
  "StakeBalance": 104283
}

exec podcupdate true
{
  "Command": "podcupdate",
  "PODCUpdate": "Processed 0 tasks for CPID 1e7184e17377549d5a7d7a2edfb51017"
}

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

Thanks.

Best regards,
Simon

I see that your computers are hidden. I think it might be that.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 09, 2018, 03:15:25 AM
I see that your computers are hidden. I think it might be that.
I have re-enabled this option now. Will see if it changes anything. Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 03:16:09 AM
Oh, and a question about the amount of BBP per superblock: shouldn't it be about half of what it is? Or is it that high because the network difficulty is low now?

Superblockbudget / blocks = 2.660.579 / 205 = +-13.000 per block.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 09, 2018, 03:24:14 AM
Hi all,

Is there an issue. My TaskWeight and UTXOWeight are now zero.
I was paid in the first PoDC superblock.

I didn't touch anything because I was scared of this!

getboincinfo
Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422385,
  "NextSuperblockHeight": 33825,
  "NextSuperblockBudget": 2660579,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4",
  "8f273b30f8e0a298ed26e242762df701_RAC": 48536.06,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 48536.06,
  "Total Payments (One Day)": 367630,
  "Total Payments (One Week)": 367630,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 2660579,
  "Superblock Count (One Week)": 1,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "33620",
  "Last Superblock Height": 33620,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 367630,
  "Magnitude (One-Day)": 138.1766901114381,
  "Magnitude (One-Week)": 138.1766901114381


Anyone else have this problem?

podcupdate says insufficient funds...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 03:46:18 AM
Hi all,

Is there an issue. My TaskWeight and UTXOWeight are now zero.
I was paid in the first PoDC superblock.

I didn't touch anything because I was scared of this!

getboincinfo
Code: [Select]
"Command": "getboincinfo",
  "CPID": "8f273b30f8e0a298ed26e242762df701",
  "Address": "B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4",
  "CPIDS": "8f273b30f8e0a298ed26e242762df701;",
  "CPID-Age (hours)": 422385,
  "NextSuperblockHeight": 33825,
  "NextSuperblockBudget": 2660579,
  "8f273b30f8e0a298ed26e242762df701_ADDRESS": "B6n6DympbZKD5GoE6EX4uW8Rvrg6QeP9R4",
  "8f273b30f8e0a298ed26e242762df701_RAC": 48536.06,
  "8f273b30f8e0a298ed26e242762df701_TEAM": 15044,
  "8f273b30f8e0a298ed26e242762df701_TaskWeight": 0,
  "8f273b30f8e0a298ed26e242762df701_UTXOWeight": 0,
  "Total_RAC": 48536.06,
  "Total Payments (One Day)": 367630,
  "Total Payments (One Week)": 367630,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 2660579,
  "Superblock Count (One Week)": 1,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "33620",
  "Last Superblock Height": 33620,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 367630,
  "Magnitude (One-Day)": 138.1766901114381,
  "Magnitude (One-Week)": 138.1766901114381


Anyone else have this problem?

podcupdate says insufficient funds...

I'm still at 100/100 with my main account...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 09, 2018, 03:47:26 AM
I'm still at 100/100 with my main account...
Hmmm. I understand UTXO has been difficult sometimes. But I don't get my taskweight = 0
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 04:03:14 AM
Hmmm. I understand UTXO has been difficult sometimes. But I don't get my taskweight = 0

Well, I also have some test-accounts. One of them is this:

Code: [Select]
10:44:50

exec getboincinfo


10:44:52

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422385,
  "NextSuperblockHeight": 33825,
  "NextSuperblockBudget": 2660579,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 35.38,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 15044,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 0,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 0,
  "Total_RAC": 35.38,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 2660579,
  "Superblock Count (One Week)": 1,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "33620",
  "Last Superblock Height": 33620,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

It's my android-phone, which I had mining on this account a few days ago. It isn't computing now, but I have some RAC on it, so I decided to test if it would still get task/UTXO weights. Well. It doesn't, haha!


It's in the dcc datalist, and my sanctuary sees it, but it hasn't got any weight.

Code: [Select]

22:12:02

exec podcupdate


22:12:07

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed 0 tasks for CPID c852da1a620ad630b70c8ec1ccdee366"
}


09:37:53

exec stakebalance


09:37:53

{
  "Command": "stakebalance",
  "StakeBalance": 8
}


Maybe it has got to do with the fact that it's not solving tasks anymore?

I'm gonna fire up this account on my phone again, and see if it changes things.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 09, 2018, 04:06:37 AM
Ok I updated to latest wallet then
exec podcupdate true
Now I am 100 100 again.

How to know if I am in the next contract?

Thanks
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: SimonSays on March 09, 2018, 04:28:51 AM
I see that your computers are hidden. I think it might be that.

Thanks! That did it!
All I did was to disable Rosseta option to hide computers.
Maybe this should be clearly written somewhere in manuals.

Best regards,
Simon
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 04:44:43 AM
Thanks! That did it!
All I did was to disable Rosseta option to hide computers.
Maybe this should be clearly written somewhere in manuals.

Best regards,
Simon

Great! I'll update the wiki now for clarity :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 06:31:59 AM
Well, I also have some test-accounts. One of them is this:

Code: [Select]
10:44:50

exec getboincinfo


10:44:52

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422385,
  "NextSuperblockHeight": 33825,
  "NextSuperblockBudget": 2660579,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 35.38,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 15044,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 0,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 0,
  "Total_RAC": 35.38,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 2660579,
  "Superblock Count (One Week)": 1,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "33620",
  "Last Superblock Height": 33620,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

It's my android-phone, which I had mining on this account a few days ago. It isn't computing now, but I have some RAC on it, so I decided to test if it would still get task/UTXO weights. Well. It doesn't, haha!


It's in the dcc datalist, and my sanctuary sees it, but it hasn't got any weight.

Code: [Select]

22:12:02

exec podcupdate


22:12:07

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed 0 tasks for CPID c852da1a620ad630b70c8ec1ccdee366"
}


09:37:53

exec stakebalance


09:37:53

{
  "Command": "stakebalance",
  "StakeBalance": 8
}


Maybe it has got to do with the fact that it's not solving tasks anymore?

I'm gonna fire up this account on my phone again, and see if it changes things.

I started mining on this account again, and now my boincinfo is as expected:

Code: [Select]
13:29:54

exec getboincinfo


13:29:56

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422388,
  "NextSuperblockHeight": 33825,
  "NextSuperblockBudget": 2660579,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 35.38,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 15044,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 25,
  "Total_RAC": 35.38,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 2660579,
  "Superblock Count (One Week)": 1,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "33620",
  "Last Superblock Height": 33620,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 09, 2018, 07:21:37 AM
Ok I updated to latest wallet then
exec podcupdate true
Now I am 100 100 again.

How to know if I am in the next contract?

Thanks

exec testvote and find your CPID, not sure if it works on non Sanc.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 07:52:12 AM
OK good because it didn't seem right, there should only be a few people with active cpids. Speaking of which, if both weights are zero, will there still be any hashing on that wallet?

By the way, I was trying minersleep=0 and genproclimit=6 and it would crash after a while.

Hmm, I need help with that as I cant get it to crash, need someone to mine with valgrind on.
Well on the pool though, they can technically mine without a CPID, but the hashes only count it the block gets stale, looks like I need an additional rule in the pool to kick them off the pool if they mine without a CPID.

Lots of fun.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 07:54:52 AM
Did the block times improve?
Do we need more hash power on PoBH?

I just analyzed the last few hundred blocks, and no it didnt improve.  Im still seeing 30 hour completion time for 205 blocks (about 20% slow still).

Ive triple and quadruple checked the rule - there is no way the rule is not being used, so let octuple check some things, and if need be, our exchange mandatory can reflect yet another change at a future height to make this right, Ill get to the bottom of this.

I strongly believe our rule kicked in and lowered our diff by 17%, and our block times with CPIDs happened to lag by 17% offseting the change, which is kind of hilarious but I believe it to be the case.

Im committed to fixing the emission system in 10 days - to decrease the DC budget by 20% and at the same time speed the blocks up by 20%.....  My, lots of fun.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 07:59:27 AM
I started mining on this account again, and now my boincinfo is as expected:

Code: [Select]
13:29:54

exec getboincinfo


13:29:56

{
  "Command": "getboincinfo",
  "CPID": "c852da1a620ad630b70c8ec1ccdee366",
  "Address": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "CPIDS": "c852da1a620ad630b70c8ec1ccdee366;",
  "CPID-Age (hours)": 422388,
  "NextSuperblockHeight": 33825,
  "NextSuperblockBudget": 2660579,
  "c852da1a620ad630b70c8ec1ccdee366_ADDRESS": "BT4PgVhnWKfonixcNGCbngA5vXEpqWCAWZ",
  "c852da1a620ad630b70c8ec1ccdee366_RAC": 35.38,
  "c852da1a620ad630b70c8ec1ccdee366_TEAM": 15044,
  "c852da1a620ad630b70c8ec1ccdee366_TaskWeight": 100,
  "c852da1a620ad630b70c8ec1ccdee366_UTXOWeight": 25,
  "Total_RAC": 35.38,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 2660579,
  "Superblock Count (One Week)": 1,
  "Superblock Hit Count (One Week)": 1,
  "Superblock List": "33620",
  "Last Superblock Height": 33620,
  "Last Superblock Budget": 2660579,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}

Yes, that is the tamper rule.  If the researcher stops researching new tasks for more than 24hours, we interpret that as ' no tasks to check ' (similar to SQL tampering), and the researcher receives 0 task weight.  So they have to keep researching to be in the next superblock.

However the 7 day magnitude on the screen would still linger for a while. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 09, 2018, 08:03:19 AM
Hmm, I need help with that as I cant get it to crash, need someone to mine with valgrind on.
Well on the pool though, they can technically mine without a CPID, but the hashes only count it the block gets stale, looks like I need an additional rule in the pool to kick them off the pool if they mine without a CPID.

Lots of fun.

OK, because I think people think they are still mining even though the hash rate is really low. But I think your saying that they might not actually be mining at all.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 08:05:09 AM
Oh, and a question about the amount of BBP per superblock: shouldn't it be about half of what it is? Or is it that high because the network difficulty is low now?

Superblockbudget / blocks = 2.660.579 / 205 = +-13.000 per block.
Yes, West emailed me of this this morning, and whats happening is we have a total gross emission error in the DC payment superblock calculation due to cascading superblocks (IE one per month plus one per day), causing the DC budget to be 20% too high (gross).  So to fix it we need to lower the DC emission rate by 30% net (that puts the entire block budget down below its allowable emission level). 

Im planning on merging that calc change in at a height of T+7 inside the exchange mandatory.

So in summary, due to cascading superblocks, there is a total emission error, and at T+7, the superblock emission for DC superblocks will be reduced by 30%, making the Biblepay block distribution:
20% for Monthly Budget Superblocks
50% for Distributed Computing Superblocks
27% for Sanctuary Payments
3% for POW mining

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 09:40:09 AM
I just analyzed the last few hundred blocks, and no it didnt improve.  Im still seeing 30 hour completion time for 205 blocks (about 20% slow still).

Ive triple and quadruple checked the rule - there is no way the rule is not being used, so let octuple check some things, and if need be, our exchange mandatory can reflect yet another change at a future height to make this right, Ill get to the bottom of this.

I strongly believe our rule kicked in and lowered our diff by 17%, and our block times with CPIDs happened to lag by 17% offseting the change, which is kind of hilarious but I believe it to be the case.

Im committed to fixing the emission system in 10 days - to decrease the DC budget by 20% and at the same time speed the blocks up by 20%.....  My, lots of fun.

Does the release of a new mandatory also mean that the pool unbanked function will be  fixed at that point? Because that would be awesome!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 10:38:29 AM
Does the release of a new mandatory also mean that the pool unbanked function will be  fixed at that point? Because that would be awesome!

Yes, absolutely, Im trying to team all this up together now and make a list of what it fixes:

- unbanked pool side
- unbanked sanc side and user side
- 7 min blocks
- lower DC budget
- Lukes new 10000 UTXO per magnitude

Etc...

The good news is since it has to be a mandatory, it shores up everything as a team.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 09, 2018, 11:14:04 AM
Yes, absolutely, Im trying to team all this up together now and make a list of what it fixes:

- unbanked pool side
- unbanked sanc side and user side
- 7 min blocks
- lower DC budget
- Lukes new 10000 UTXO per magnitude

Etc...

The good news is since it has to be a mandatory, it shores up everything as a team.

Absolutely awesome Rob! :D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 09, 2018, 11:26:12 AM
Yes, absolutely, Im trying to team all this up together now and make a list of what it fixes:

- unbanked pool side
- unbanked sanc side and user side
- 7 min blocks
- lower DC budget
- Lukes new 10000 UTXO per magnitude

Etc...

The good news is since it has to be a mandatory, it shores up everything as a team.

That's great, I'll update when the Windows wallet is ready.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 12:24:03 PM
https://bitcointalk.org/index.php?topic=2388064.new#new

Please Vote:

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 09, 2018, 03:13:34 PM
Does my wallet that is associated with my CPID have to be running to be eligible for rewards? I noticed that mine is down and I won’t be home for several hours.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 09, 2018, 04:09:49 PM
Does my wallet that is associated with my CPID have to be running to be eligible for rewards? I noticed that mine is down and I won’t be home for several hours.

Yes, the wallet has to on at all times. If it can't send out podc updates your UTXOweight will go to zero.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 09, 2018, 05:18:32 PM
Rob,
why I have more than 6 payment to yourself tx/day?
Last PODC update was 24h ago, but I have those 6 with UTXOamounth. Is it PODC confirmation?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 06:38:10 PM
Rob,
why I have more than 6 payment to yourself tx/day?
Last PODC update was 24h ago, but I have those 6 with UTXOamounth. Is it PODC confirmation?

You can actually just click on them and see if its "PODC notification", or check the XML in the vout to see if it says "PODCUpdate", but anyway it normally only sends a couple in 24 hours, but if you have multiple CPIDs, it sends one for each CPID.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 09, 2018, 06:39:50 PM
Does my wallet that is associated with my CPID have to be running to be eligible for rewards? I noticed that mine is down and I won’t be home for several hours.

Although I dont recommend it if you absolutely have to shut down you can exec podcupdate true and send a fresh one then hope that you are in the chain for 24 hours, and pick it up the next day.

There is an option in the qt wallet to minimize to Tray, and install as service.  This is nice if you do not want to see whats going on- now that we are pretty green Im sure you can run biblepay on a windows machine as a service and not even notice its running.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 09, 2018, 08:13:42 PM
Rob, I hope this helps. The wallet crashes with any values over 1 it seems like.

https://transfer.sh/12zRuR/Debug.zip

Password: biblepay
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 10, 2018, 04:28:53 AM
You can actually just click on them and see if its "PODC notification", or check the XML in the vout to see if it says "PODCUpdate", but anyway it normally only sends a couple in 24 hours, but if you have multiple CPIDs, it sends one for each CPID.
Yes they are all PODC update. But I have only one CPID. OK, but is it enough to update PODC once per day, yes?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 10, 2018, 05:48:04 AM
Rob, I hope this helps. The wallet crashes with any values over 1 it seems like.

https://transfer.sh/12zRuR/Debug.zip

Password: biblepay

Hi Mike-

I did download it I did open it, but unfortunately no lin crash dump or windows crash dump can point us to the line number crashing biblepay- except valgrind, or QT running in debug mode with symbols on linux, and I still havent ran it in valgrind mode as its a squirrely deal I cant reproduce it yet- although Im confident I will soon, just need to try to mine on my large vps.

So when you say one, does this crash for you when mining with more than one thread, or what is it that crashes it?

Im mining with 40 threads on my windows box.



EDIT:   I think I found the crash issue in the miner; fixing now...



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 10, 2018, 09:17:15 AM
Hi Mike-

I did download it I did open it, but unfortunately no lin crash dump or windows crash dump can point us to the line number crashing biblepay- except valgrind, or QT running in debug mode with symbols on linux, and I still havent ran it in valgrind mode as its a squirrely deal I cant reproduce it yet- although Im confident I will soon, just need to try to mine on my large vps.

So when you say one, does this crash for you when mining with more than one thread, or what is it that crashes it?

Im mining with 40 threads on my windows box.



EDIT:   I think I found the crash issue in the miner; fixing now...

Oh, that's great! Yeah anything over 1 thread the gui will crash.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 10, 2018, 11:53:38 AM
Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 10, 2018, 11:59:46 AM
Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110

Updated both linux and windows just now.

Update:
Windows wallet still crashes basically on open with threads set to 6 and sleep at 0. Also tried changing the # of threads in the debug terminal and it also crashes immediately when I change it. With a lower thread number, it takes longer before it crashes but with 6 it crashes immediately.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: znffal on March 10, 2018, 01:05:12 PM
Hi Rob,

I just upgraded my PoDC wallet.
My UTXO weight is now 60,000 which I guess is to prepare for changes depending on poll outcome.
Just wanted to check with you that this was expected behaviour.

Thanks
Luke

EDIT: But I guess it doesn't matter what the value is as long as it is over 50,001 until the cut-off block?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 10, 2018, 01:21:04 PM
Hi Rob,

I just upgraded my PoDC wallet.
My UTXO weight is now 60,000 which I guess is to prepare for changes depending on poll outcome.
Just wanted to check with you that this was expected behaviour.

Thanks
Luke

EDIT: But I guess it doesn't matter what the value is as long as it is over 50,001 until the cut-off block?
My UTXO weight is 50556 :) so it looks like preparing but I don't know if 50556 is good or not.
Is it enough? Is it like UTXO 100 before? What would be there if my BBP amount would be less than 50556?
Thanks for clarification.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 10, 2018, 01:30:47 PM
My UTXO weight is 50556 :) so it looks like preparing but I don't know if 50556 is good or not.
Is it enough? Is it like UTXO 100 before? What would be there if my BBP amount would be less than 50556?
Thanks for clarification.

The new UTXO is not in effect yet, you just need 50,001 for 100% UTXO weight.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 10, 2018, 02:05:53 PM
The new UTXO is not in effect yet, you just need 50,001 for 100% UTXO weight.
I know, but I want to know what does the number mean :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 10, 2018, 02:47:01 PM
Updated both linux and windows just now.

Update:
Windows wallet still crashes basically on open with threads set to 6 and sleep at 0. Also tried changing the # of threads in the debug terminal and it also crashes immediately when I change it. With a lower thread number, it takes longer before it crashes but with 6 it crashes immediately.

Ok, thanks, I finally see the problem.  It was kind of a complicated issue, but Im pretty sure its going to fixed in the next version in two hours.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 10, 2018, 03:20:39 PM
Ok, thanks, I finally see the problem.  It was kind of a complicated issue, but Im pretty sure its going to fixed in the next version in two hours.

Sounds good Rob, I'll test it out. If you get a chance, I sent you some PMs, thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 10, 2018, 09:48:19 PM
Rob, I think we really need something for headless if the new UTXO proposal passes, leaving it un-encrypted is not a good idea.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 10, 2018, 09:55:41 PM
Rob, I think we really need something for headless if the new UTXO proposal passes, leaving it un-encrypted is not a good idea.
Ok 1.1.0.1 windows is out there now if you want to grab it.

I wont have any time left tonight to read the emails or PMs.

On "encrypted" are you referring to the UTXO message in the chain?  Sending Tx from user to another user is not encrypted, its signed.
The UTXO is also signed.  So it cant be hacked by falsifying a message in the chain.  PODC updates are Signed by your CPID.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 10, 2018, 09:59:56 PM
Ok 1.1.0.1 windows is out there now if you want to grab it.

I wont have any time left tonight to read the emails or PMs.

On "encrypted" are you referring to the UTXO message in the chain?  Sending Tx from user to another user is not encrypted, its signed.
The UTXO is also signed.  So it cant be hacked by falsifying a message in the chain.  PODC updates are Signed by your CPID.

Rob, no I mean the wallet has to be unlocked for podc updates. Right now it does not auto-unlock in headless.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 10, 2018, 10:09:12 PM
Rob, no I mean the wallet has to be unlocked for podc updates. Right now it does not auto-unlock in headless.
Oh good, sounds like something easier to deal with.  So, yeah biblepay-cli would log entries in the bash log because those are from bash.
Maybe if I send it like the FTP prompt, maybe it would not be logged.  I guess I can check into that in the morning.

In the mean time you want to try FTPing into a server with a password and see if bash does not log the pass as root?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 10, 2018, 10:28:22 PM
Oh good, sounds like something easier to deal with.  So, yeah biblepay-cli would log entries in the bash log because those are from bash.
Maybe if I send it like the FTP prompt, maybe it would not be logged.  I guess I can check into that in the morning.

In the mean time you want to try FTPing into a server with a password and see if bash does not log the pass as root?

The ftp password prompt is the like normal linux user login prompt so it does not log the password, it doesn't even display it when your typing it. But I mentioned in an earlier post that you are typing out your passphrase when you unlock your wallet normally anyways so i don't think it's a bigger security concern compared to before.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 11, 2018, 06:22:12 AM
The ftp password prompt is the like normal linux user login prompt so it does not log the password, it doesn't even display it when your typing it. But I mentioned in an earlier post that you are typing out your passphrase when you unlock your wallet normally anyways so i don't think it's a bigger security concern compared to before.
Hmmm, right, but they could RPC over SSL to the box and enter the pass without it going in the log, so Id rather not condone that behavior of typing it in if we can make it secure.  Let me take a look at how FTP allows the characters to be typed and see if I can make a headless test case.

So I see the miner appears to be a little more stable/faster with the last update- now we ask the miner to sign the threads cpids once and only re-sign if necessary (this keeps the lock from going off/on and prevents the crash).  Did 1110 prevent the crash for you in the miner?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 11, 2018, 09:25:15 AM
Jaap, I just upgraded the pool server to 1110 if you want to re-associate the completely unbanked cpid and verify we dont receive an error.

As far as rewards are concerned we need a 51% supermajority on the sancs in order to start voting the correct contract for the unbanked cpid (IE by Thursday we should see some payments).

Thanks!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 11, 2018, 09:54:20 AM
Hmmm, right, but they could RPC over SSL to the box and enter the pass without it going in the log, so Id rather not condone that behavior of typing it in if we can make it secure.  Let me take a look at how FTP allows the characters to be typed and see if I can make a headless test case.

So I see the miner appears to be a little more stable/faster with the last update- now we ask the miner to sign the threads cpids once and only re-sign if necessary (this keeps the lock from going off/on and prevents the crash).  Did 1110 prevent the crash for you in the miner?

Rob, appears to be better? I  opened with 6 threads and it seemed fine, switch to 8 in debug and it crashed. sleep=0.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 11, 2018, 10:49:43 AM
Jaap, I just upgraded the pool server to 1110 if you want to re-associate the completely unbanked cpid and verify we dont receive an error.

As far as rewards are concerned we need a 51% supermajority on the sancs in order to start voting the correct contract for the unbanked cpid (IE by Thursday we should see some payments).

Thanks!

I tried it, and as far as I know it worked!
"Successively advertised DC-key"

Don't have much time now, sorry. And I'm on my phone, so it's difficult to give data now. But I'll get back on this tonight :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 11, 2018, 11:38:47 AM
Ok. Upgraded to 1110.
My observations:
On my 1-core VPS is one thread using more than 50% of CPU. Version before it was about 15%.

And Rob, my bootup unlock in WIN GUI is still not working :(
I don't know what can be bad here.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 11, 2018, 12:22:28 PM
Ok. Upgraded to 1110.
My observations:
On my 1-core VPS is one thread using more than 50% of CPU. Version before it was about 15%.

And Rob, my bootup unlock in WIN GUI is still not working :(
I don't know what can be bad here.
Try setting the minersleep=500 for example, this is configurable by the user.  Ill see if I can change it back to 250ms for the next version but it doesnt seem to be a bug.

On the Win GUI, not sure what you mean by not working.

It should throw an error if you type in the wrong password.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 11, 2018, 12:32:22 PM
I tried it, and as far as I know it worked!
"Successively advertised DC-key"

Don't have much time now, sorry. And I'm on my phone, so it's difficult to give data now. But I'll get back on this tonight :)
Good , that is half the battle, just see tonight when you exercise the new search feature:
exec search dcc cpid

See if the row is there with the unbanked cpid and the correct unbanked receive address?

Then in a couple days once we receive our first contract with the new utxo levels (of 500 per SPM), you should receive a payment.
Actually now that I think about it if you will paste that search row result, Ill check my upgraded sanc to see if the cpid is in the "future" payment (sort of like Minority Report), for some reason Im getting confused between Minority Report and the Pre-cogs (the 3 humans that are gifted) and seeing a movie one time with a dolphin with wires attached, that made lots of decisions for the group... hmmm.... 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 11, 2018, 12:34:28 PM
Rob, appears to be better? I  opened with 6 threads and it seemed fine, switch to 8 in debug and it crashed. sleep=0.

How about 40 threads with sleep=1?   And btw what OS is this that keeps crashing?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 11, 2018, 12:57:29 PM
How about 40 threads with sleep=1?   And btw what OS is this that keeps crashing?

Works fine until you try to change the # of threads in debug. Tried lowering to 20 and it crashed. Windows 10 Pro.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 11, 2018, 01:21:46 PM
Is there anything unusual about the current contract? The mag seems to be half on 2 of my wallets. I divided my RAC with the team RAC and it doesn't seem to be right.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 11, 2018, 01:28:38 PM
Try setting the minersleep=500 for example, this is configurable by the user.  Ill see if I can change it back to 250ms for the next version but it doesnt seem to be a bug.

On the Win GUI, not sure what you mean by not working.

It should throw an error if you type in the wrong password.
minersleep=1000 works for me.

And with that unlock.
At starting GUI wallet it asks me for password. I give there good password (I changed it, copy/paste, ...) and the wallet is still locked when it starts.
There is no error, only locked wallet (the lock icon is locked "wallet is encypted and currently locked", in menu is option "unlock wallet", in getinfo is "unlocked_until": 0, ... ). 
I must unlock it from menu then it works.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 11, 2018, 01:36:03 PM
minersleep=1000 works for me.

And with that unlock.
At starting GUI wallet it asks me for password. I give there good password (I changed it, copy/paste, ...) and the wallet is still locked when it starts.
There is no error, only locked wallet (the lock icon is locked "wallet is encypted and currently locked", in menu is option "unlock wallet", in getinfo is "unlocked_until": 0, ... ). 
I must unlock it from menu then it works.

Are you saying it won't auto-unlock for PODC updates? Your wallet will be locked even after the prompt, it is only unlocked for the podc update.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 11, 2018, 01:44:35 PM
Are you saying it won't auto-unlock for PODC updates? Your wallet will be locked even after the prompt, it is only unlocked for the podc update.
Oh. And how I know that it is unlocked? There is no "sign" about that in wallet.
After start and getmininginfo it gives me Unable to sign CPID.
Ok. Maybe I'm impatient and it'll be enough to wait, but I was thinking that it just don't work for me and unlock it manually.
But definitelly it will be good to have there some message about it that it is unlocked for PODC only.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 11, 2018, 01:53:08 PM
Oh. And how I know that it is unlocked? There is no "sign" about that in wallet.
After start and getmininginfo it gives me Unable to sign CPID.
Ok. Maybe I'm impatient and it'll be enough to wait, but I was thinking that it just don't work for me and unlock it manually.
But definitelly it will be good to have there some message about it that it is unlocked for PODC only.

Yeah, it could be that we throw *one* of the unable to sign cpids in the miner when you first boot - try this, lock wallet, close wallet, open wallet - type
 the password, ensure we dont throw a password error after clicking OK on the password prompt, start the miner, if you see an error in there, do another 'setgenerate true 5' and just wait a couple minutes - ensure the error goes away and its mining.    The issue might be that we dont clear the error for about 4 mins or so into mining in the miner. 

Yes, we unlock it, sign the cpid, and lock it when the password is provided.  But we only do that if its encrypted and locked at the time cpid needs signed. 



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 11, 2018, 02:03:24 PM
Is there anything unusual about the current contract? The mag seems to be half on 2 of my wallets. I divided my RAC with the team RAC and it doesn't seem to be right.

Running this upcoming contract on my sanc - I ran one about 2 hours ago:
'                        public key, cpid,                          magnitude, rosettaid, team, utxoweight, taskweight, rac,   unbankedindicator, utxoamount, RAC,   InductedCredit,

'BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,109.608,1981209,     15044,50001,       100,       976594,0,                  60.00,    178404,  107042

exec search utxoweight e94
  "E94C1704C75F731F8BFDE303F08408EE (03-11-2018 18:54:10)": "832822"


Looks like it has you at a mag of 109.6, with RAC of 178404 but its only giving you 60% based on UTXO weight of 50,001 see above, that gives only 107K rac, hence the lower mag.
Looking at your timestamp on the podcupdate - it looks like you send 832,822 in at 18:54 UTC time today (thats very recent, after my sanc ran its contract)

So hopefully you will be Hit by the old contract sancs today!  I guess the lesson here is to send the podcupdate a little earlier with the 500SPM just in case, so that its "in" earlier for the newer sancs.

Sorry but I have a family birthday party Ive got to go to and also got to run a long errand so I will be gone for about 5 hours.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 11, 2018, 02:10:48 PM
Running this upcoming contract on my sanc - I ran one about 2 hours ago:
'                        public key, cpid,                          magnitude, rosettaid, team, utxoweight, taskweight, rac,   unbankedindicator, utxoamount, RAC,   InductedCredit,

'BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,109.608,1981209,     15044,50001,       100,       976594,0,                  60.00,    178404,  107042

exec search utxoweight e94
  "E94C1704C75F731F8BFDE303F08408EE (03-11-2018 18:54:10)": "832822"


Looks like it has you at a mag of 109.6, with RAC of 178404 but its only giving you 60% based on UTXO weight of 50,001 see above, that gives only 107K rac, hence the lower mag.
Looking at your timestamp on the podcupdate - it looks like you send 832,822 in at 18:54 UTC time today (thats very recent, after my sanc ran its contract)

So hopefully you will be Hit by the old contract sancs today!  I guess the lesson here is to send the podcupdate a little earlier with the 500SPM just in case, so that its "in" earlier for the newer sancs.

Sorry but I have a family birthday party Ive got to go to and also got to run a long errand so I will be gone for about 5 hours.

Thanks for looking into it, hope you have a good time.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 11, 2018, 02:54:38 PM
Yeah, it could be that we throw *one* of the unable to sign cpids in the miner when you first boot - try this, lock wallet, close wallet, open wallet - type
 the password, ensure we dont throw a password error after clicking OK on the password prompt, start the miner, if you see an error in there, do another 'setgenerate true 5' and just wait a couple minutes - ensure the error goes away and its mining.    The issue might be that we dont clear the error for about 4 mins or so into mining in the miner. 

Yes, we unlock it, sign the cpid, and lock it when the password is provided.  But we only do that if its encrypted and locked at the time cpid needs signed.
So, it is OK. It works and I was too impatient. But I still think that visual "alert" for this need improvement :) Maybe it will be enough to change the onhover text on lock to "Wallet is encypted and unlocked for PODC only". Thanks Mike and Rob for clarification.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 11, 2018, 06:55:27 PM
Rob, is there a way to see which contract currently has the most votes? Thanks.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 12, 2018, 12:17:10 AM
I think we have a bug- PODC stake has used my 1550001 BBP of my sanc for staking, even if it's supposed to be locked

See:
http://explorer.biblepay.org:3001/tx/0321cce7ad6a91a707c4512e32c1bd13d31754233e7cd0403b7dee7face0c4d8

Now my sanc is "missing" :-(

Edit: I think it's because I cloned the wallet into another PC. Anyway, the lock enforcement should work at the blockchain level I think.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 12, 2018, 06:54:48 AM
I think we have a bug- PODC stake has used my 1550001 BBP of my sanc for staking, even if it's supposed to be locked

See:
http://explorer.biblepay.org:3001/tx/0321cce7ad6a91a707c4512e32c1bd13d31754233e7cd0403b7dee7face0c4d8

Now my sanc is "missing" :-(

Edit: I think it's because I cloned the wallet into another PC. Anyway, the lock enforcement should work at the blockchain level I think.

No, its not a PODC bug, we iterate through your UTXOs and honor the locks.  I would check to ensure you have re-locked your hot funds during each start.

Do you have a masternode.conf file set up with the Sanc's hot txid in it?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 12, 2018, 06:59:11 AM
Rob, is there a way to see which contract currently has the most votes? Thanks.

The only way to do it right now is to go to the sanc, and type 'gobject list all triggers', copy that to notepad and find the one with the highest votes.
Then you can 'gobject get gobjectid' to see the info.

I decided since we were getting so many questions about the upcoming contract, Im going to write a feature that allows the Pool to pull in the current "upcoming" contract into a pool page for viewing by everyone.  Hopefully it will answers the lions share of the questions, like UTXO amounts and am I in it, although Im doing this in a way where its going to pull my First sanctuaries (sanc1) into the pool 4 times per day, so I cant guarantee "my" sanc will be "the" voted contract!  But at least it should be 95% accurate most days, since Im going to have the same data as everyone else.  Im thinking of storing this info in history also, so we can make a chart of Magnitude by CPID, and maybe allow Capulo to drill into Yesterdays contract to check his yesterdays rac, etc. 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 12, 2018, 07:49:58 AM
No, its not a PODC bug, we iterate through your UTXOs and honor the locks.  I would check to ensure you have re-locked your hot funds during each start.

Do you have a masternode.conf file set up with the Sanc's hot txid in it?

In one PC I do, but not in the other wallet with the sanc. controller address. So it's possible that for this wallet that UTXO was not locked.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 12, 2018, 12:32:22 PM
In one PC I do, but not in the other wallet with the sanc. controller address. So it's possible that for this wallet that UTXO was not locked.

In testnet, I noticed that when I ran a hot sanc, I had to manually lock the row every day, which is a big nuisance, but in Prod, while using my masternode.conf file, the bootup sequence of the wallet locks every txid in the list, so even with all my PODC updates, I never have spent my locked funds in prod.

I also attempted to make sure the wallet does not spend anything equaliing SANCTUARY_COLLATERAL, but when you said earlier it spent one, Im thinking maybe that amount is Off in the wallet and only half of the feature is working. LOL.  So Ill check on #2 later today in the mean time try to do the masternode.conf then reboot and look in coin control and if its locked you should be OK.


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 12, 2018, 12:59:07 PM
In one PC I do, but not in the other wallet with the sanc. controller address. So it's possible that for this wallet that UTXO was not locked.

Ok yes, you discovered a certain unintended bug.     Fixed in the next version - now the wallet will not spend sanctuary funds in PODC updates or Associations.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 12, 2018, 02:23:08 PM
Good , that is half the battle, just see tonight when you exercise the new search feature:
exec search dcc cpid

See if the row is there with the unbanked cpid and the correct unbanked receive address?

Then in a couple days once we receive our first contract with the new utxo levels (of 500 per SPM), you should receive a payment.
Actually now that I think about it if you will paste that search row result, Ill check my upgraded sanc to see if the cpid is in the "future" payment (sort of like Minority Report), for some reason Im getting confused between Minority Report and the Pre-cogs (the 3 humans that are gifted) and seeing a movie one time with a dolphin with wires attached, that made lots of decisions for the group... hmmm....

Code: [Select]
21:21:49

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:21:49

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

Looks good  8)

Don't know that dolphin movie btw, haha! If you ever remember the title, I'd like to know it  ;D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 12, 2018, 05:41:14 PM
Code: [Select]
21:21:49

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:21:49

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

Looks good  8)

Don't know that dolphin movie btw, haha! If you ever remember the title, I'd like to know it  ;D

Great, so now since we have the pool contract report, (Reports | Superblock View) we can just go into the pool and search for 8791.  So to find out if you have any magnitude, take a look RAC and Modified RAC.  RAC = 54, Modified RAC = 54.  This shows a mag of .044.  If the CPID was penalized for taskweight or utxoweight, the modified RAC would have been lower or 0, so everything appears to be working, all we have to do is wait for the supermajority to run the latest sanc code and the payments should start.

I havent encountered any new showstoppers so I think we can announce the mandatory tomorrow and possibly re-enable the exchanges.

Im adding one more rule tonight for the potential of stake-per-rac processing.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 12, 2018, 07:01:54 PM
Biblepay - 1.1.1.1b
Mandatory Upgrade before block 35110


- Headless PODC Password support:
  ./biblepay-cli -headlesspodcpassword  <enter>     ,  then Enter password on next line.  Step 2 (optional): exec podcpasswordlength
- Added icon in QT for PODC Association, and icon for PODC Update
- Prevent wallet from spending Sanctuary collateral during PODC Update
- Add support for Required Stake-Per-RAC pending poll outcome


** Windows is compiling **

This is a prerelease, checked in now, available for linux.  It turns out this will need to be mandatory for the whole network due to that new 'potential' stake-per-rac feature pending the poll outcome. 

In the mean time if anyone wants to test the headless password prompt, go for it.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 12, 2018, 07:22:27 PM
Biblepay - 1.1.1.1b
Mandatory Upgrade before block 35110


- Headless PODC Password support:
  ./biblepay-cli -headlesspodcpassword  <enter>     ,  then Enter password on next line.  Step 2 (optional): exec podcpasswordlength
- Added icon in QT for PODC Association, and icon for PODC Update
- Prevent wallet from spending Sanctuary collateral during PODC Update
- Add support for Required Stake-Per-RAC pending poll outcome


** Windows is compiling **

This is a prerelease, checked in now, available for linux.  It turns out this will need to be mandatory for the whole network due to that new 'potential' stake-per-rac feature pending the poll outcome. 

In the mean time if anyone wants to test the headless password prompt, go for it.
That's great! What is the exec podcpasswordlength for?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 13, 2018, 08:00:27 AM
That's great! What is the exec podcpasswordlength for?

You can use it from headless to check that the password was memorized.  Its just a sanity check.

Windows has been deployed if anyone wants to test it.

I think we are OK to release this afternoon, from what I can tell.

This latest version handles either poll outcome.

Id like to inform exchanges to upgrade late tonight, so please if anyone has any concerns please post, and please test anything remaining.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 13, 2018, 08:12:38 AM
You can use it from headless to check that the password was memorized.  Its just a sanity check.

Windows has been deployed if anyone wants to test it.

I think we are OK to release this afternoon, from what I can tell.

This latest version handles either poll outcome.

Id like to inform exchanges to upgrade late tonight, so please if anyone has any concerns please post, and please test anything remaining.

I'll upgrade both and let you know if I see any issues.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 13, 2018, 01:47:31 PM
Biblepay - 1.1.1.1b
Mandatory Upgrade before block 35110


- Headless PODC Password support:
  ./biblepay-cli -headlesspodcpassword  <enter>     ,  then Enter password on next line.  Step 2 (optional): exec podcpasswordlength
- Added icon in QT for PODC Association, and icon for PODC Update
- Prevent wallet from spending Sanctuary collateral during PODC Update
- Add support for Required Stake-Per-RAC pending poll outcome


** Windows is compiling **

This is a prerelease, checked in now, available for linux.  It turns out this will need to be mandatory for the whole network due to that new 'potential' stake-per-rac feature pending the poll outcome. 

In the mean time if anyone wants to test the headless password prompt, go for it.

Rob,
it doesn't work for me.
when I use ./biblepay-cli -headlesspodcpassword it gives me error:
Code: [Select]
Too few parametersI've tried to add someting there e.g. ./biblepay-cli -headlesspodcpassword  1  and it ask for pwd. Entered pwd and then:
Code: [Select]
error code: -32601
error message: Method not found
Memorized 13
I think, those errors belongs to that "1".
after exec podcpasswordlength it gives: Length: 13 and getmininginfo looks sometime fine, without CPID error, but sometimes with error.
So it seems, that it works for me (sometimes), but with additional parameters :)

EDIT: so, tried many times and it didn't worked for me. Still CPID errors in getmininginfo.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 13, 2018, 02:06:18 PM
Rob,
it doesn't work for me.
when I use ./biblepay-cli -headlesspodcpassword it gives me error:
Code: [Select]
Too few parametersI've tried to add someting there e.g. ./biblepay-cli -headlesspodcpassword  1  and it ask for pwd. Entered pwd and then:
Code: [Select]
error code: -32601
error message: Method not found
Memorized 13
I think, those errors belongs to that "1".
after exec podcpasswordlength it gives: Length: 13 and getmininginfo looks sometime fine, without CPID error, but sometimes with error.
So it seems, that it works for me (sometimes), but with additional parameters :)

EDIT: so, tried many times and it didn't worked for me. Still CPID errors in getmininginfo.

Hi Orbis,

Try starting biblepayd first, then after its started try this:

/biblepay-cli -headlesspodcpassword exec podcpasswordlength


Then type the password, press <enter>


Then mine, and it should work.

As far as the error in getmininginfo, just wait a little longer.


I remember testing this the night I wrote it, but forgot the parameter must include the full 4 words as above...  Ill modify the release notes when releasing tonight.  Let me know if it works for you now.



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 13, 2018, 02:36:23 PM
Hi Orbis,
Try starting biblepayd first, then after its started try this:
/biblepay-cli -headlesspodcpassword exec podcpasswordlength
Then type the password, press <enter>

Then mine, and it should work.
As far as the error in getmininginfo, just wait a little longer.

I remember testing this the night I wrote it, but forgot the parameter must include the full 4 words as above...  Ill modify the release notes when releasing tonight.  Let me know if it works for you now.
:)
Of course I started with biblepayd
Then /biblepay-cli -headlesspodcpassword exec podcpasswordlength
Then typed the password
Then get a shower and after that getmining still gives me CPID error :(
After stoping biblepay it gives me this error:
Code: [Select]
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument

EDIT: tested on 3 different PCs. same result everywhere. with walletpassphrase is unlock successful.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 13, 2018, 07:20:16 PM
:)
Of course I started with biblepayd
Then /biblepay-cli -headlesspodcpassword exec podcpasswordlength
Then typed the password
Then get a shower and after that getmining still gives me CPID error :(
After stoping biblepay it gives me this error:
Code: [Select]
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::lock_error> >'
what():  boost: mutex lock failed in pthread_mutex_lock: Invalid argument

EDIT: tested on 3 different PCs. same result everywhere. with walletpassphrase is unlock successful.

Its mining for me

bible1:~/biblepay/src$ ./biblepay-cli -headlesspodcpassword exec podcpasswordlength

I do receive the mutex error when I stop the node, but I can see after setting the password the cpid signing error is gone...

Are you sure its not mining for you?




Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 14, 2018, 06:14:51 AM
Today I did not receive a reward.  Looking at my tx history, no evidence of a PODC Update tx since 3.11.18 at 08:17 local time.  Was on 1.1.1.0, so upgraded to 1.1.1.1 (although was under the impression that was not required until Thursday).  Restarted wallet, ran exec podcupdate and got the PODC Update tx, but concerned why there was no tx in about 36 hours.

The only reason I can think of is if the wallet was locked or if you didn't have enough stake balance. I think you would need to go through the log file to find out.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 14, 2018, 06:44:40 AM
Today I did not receive a reward.  Looking at my tx history, no evidence of a PODC Update tx since 3.11.18 at 08:17 local time.  Was on 1.1.1.0, so upgraded to 1.1.1.1 (although was under the impression that was not required until Thursday).  Restarted wallet, ran exec podcupdate and got the PODC Update tx, but concerned why there was no tx in about 36 hours.


Hmmm, not sure if you are using QT/headless or win/lin for the controller but other than ensure that getmininginfo shows no errors after a few mins after boot (to ensure wallet is not locked or throwing a sign error), try checking the log for this:

UTXOUpdate Processed (258) over 1 CPID(s) successfully.
Look for any errors after that entry in the timespan that you were affected in, maybe the wallet threw an error?

Going forward I think the key is ensuring at least 1 thread is running with HPS > 0 and the poolinfo1: row is empty (that is where the errors are shown currently for unable to sign CPID).


Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 14, 2018, 11:27:12 AM
Wallet was on Windows 7.

Only odd part of the debug log was

Code: [Select]
13 13:56:24  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-13 13:56:24  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000

repeated close to 100 times, one different statement in that run was

2018-03-13 13:56:24  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-13 13:56:24  CInstantSend::ProcessTxLockRequest successful
2018-03-13 13:56:24  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000

Then had

2018-03-13 13:56:29  InstantSend : AllOutPointReady 1.000000, IsLockedInstantSendTransaction 1.000000, bool 1.000000
2018-03-13 13:57:32 UpdateTip: new best=76c342e700a149155566862dc4ecda777398cf95442ed8bbd0b5ac41be8629b7  height=34370  log2_work=58.86532  tx=130988  date=2018-03-13 13:57:00 progress=0.999998  cache=1.8MiB(2269tx)
2018-03-13 13:57:32 ProcessNewBlock : ACCEPTED
2018-03-13 13:57:49 CInstantSend::CreateTxLockCandidate -- new, txid=157a2f1520b375523a3ea5cabef282eeaed7993b412ce40b138c456ae481ff24
2018-03-13 13:57:49 CInstantSend::ProcessTxLockRequest -- accepted, txid=157a2f1520b375523a3ea5cabef282eeaed7993b412ce40b138c456ae481ff24
2018-03-13 13:57:49  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000
2018-03-13 13:57:49  CInstantSend::ProcessTxLockRequest successful
2018-03-13 13:57:49 TXLOCKREQUEST -- Transaction Lock Request accepted, txid=157a2f1520b375523a3ea5cabef282eeaed7993b412ce40b138c456ae481ff24, peer=816
2018-03-13 13:57:49 CInstantSend::CreateTxLockCandidate -- creating birth, txid=157a2f1520b375523a3ea5cabef282eeaed7993b412ce40b138c456ae481ff24
2018-03-13 13:57:49 CInstantSend::CreateTxLockCandidate -- update empty, txid=157a2f1520b375523a3ea5cabef282eeaed7993b412ce40b138c456ae481ff24
2018-03-13 13:57:49 CInstantSend::ProcessTxLockRequest -- accepted, txid=157a2f1520b375523a3ea5cabef282eeaed7993b412ce40b138c456ae481ff24
2018-03-13 13:57:49  InstantSend : AllOutPointReady 0.000000, IsLockedInstantSendTransaction 0.000000, bool 1.000000

Also for some reason after updating to 1.1.1.1 the whole thing crashed (overnight)

last lines before the crash were
2018-03-14 10:37:57 ProcessNewBlock : ACCEPTED
2018-03-14 10:43:39  VerifyDistributedBurnTransaction::PASS for CPID A895052039C2E80B20C388ACC8AC47E1
2018-03-14 10:43:43  VerifyDistributedBurnTransaction::PASS for CPID A895052039C2E80B20C388ACC8AC47E1
2018-03-14 16:29:41



Nope, nothing in the log related to a PODC update (didnt see the word PODC in there).

Please surround long snippet posts with the code tags.

Regarding the crash we will need to ask you or a volunteer to run it on linux in valgrind mode.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: orbis on March 14, 2018, 12:35:37 PM
Its mining for me

bible1:~/biblepay/src$ ./biblepay-cli -headlesspodcpassword exec podcpasswordlength

I do receive the mutex error when I stop the node, but I can see after setting the password the cpid signing error is gone...

Are you sure its not mining for you?

Tested today again and now it works :)
I don't know why it didn't worked before.
But now looks fine. Thanks for it.
I wonder whether it was tested by someone else.

Do you plan to make someting with those mutex error?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Ichthus220 on March 14, 2018, 06:23:41 PM
How do I associate my CPID with my other machines, So I can pool mine, without messing up the burn transaction on my PODC machine?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 14, 2018, 08:05:32 PM
How do I associate my CPID with my other machines, So I can pool mine, without messing up the burn transaction on my PODC machine?

You can't, the CPID can only be used with one wallet at a time. You can copy the wallet to the other machines and just have one do the podc updates.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 15, 2018, 12:56:43 AM
I also tried 1.1.1.1 and it said unable to sign CPID when I was mining on Purepool.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 15, 2018, 09:17:43 AM
Not sure why it would have failed to do the update.  Again, was on 1.1.1.0, Win 7 wallet.  Upgraded to 1.1.1.1, crashed once, no crash since.  No PoDC tx being the issue.  Not mad about missing out on the Superblock reward but can imagine how if I was spending hundreds on a VPN that would be different.  Me, I'm a supporter of the coin, understand things happen.  But want to know what logs will be required to better troubleshoot.
Thanks!
So far all I can think of is your controller wallet might have stopped mining, but I cant imagine why.
The first thread, thread zero, has to have a HPS > 0 for the PODC update to work.
As far as what it logs, it should always log "PODCUpdate" in the log - and then something after it.

I suppose this will all come out in the wash.  Ive been mining on my dev machine controller wallet for 4 days now and have gotten in every superblock and each PODC update, but I realize there are still some situations out there that are unaccounted for.

Please see the PODC Update section regarding frequency, on an unrelated note if anyone is interested in *when* the miner sends it:
https://wiki.biblepay.org/Distributed_Computing#PODC_Updates

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 15, 2018, 09:20:20 AM
How do I associate my CPID with my other machines, So I can pool mine, without messing up the burn transaction on my PODC machine?

All you can do is copy the wallet.dat out to the other mining machine, and mine from that machine.  It will sign those pool packets with your primary cpid then.

Some people have recommended starting a second CPID, but I do not recommend that, as we have a rule that you must be in the prior superblock with magnitude to receive payments, and therefore that second cpid would not be helping the network.  And in lieu of that Im going to work with Lich to stop that reward in the pool on both of our pools so we can reward the *real* CPIDs more BBP asap.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 15, 2018, 09:23:32 AM
Tested today again and now it works :)
I don't know why it didn't worked before.
But now looks fine. Thanks for it.
I wonder whether it was tested by someone else.

Do you plan to make someting with those mutex error?

Yes, let me take a look at the mutex.  I think all that is happening is its locking the mutex and then when leveldb gets flushed it is unlocked when the thread is aborted.

The main concern I have is to ensure the wallet is flushed during exit.  I have reports here that some coins on bittrex take 35 seconds to exit because they have so many keys.  Ours is definitely getting flushed, and thats my main concern so we dont corrupt users wallets and allow them to lose any funds.

Luckily we have wallet backups also.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 15, 2018, 09:25:38 AM
I also tried 1.1.1.1 and it said unable to sign CPID when I was mining on Purepool.
Please ensure your 'exec getboincinfo' shows a valid CPID, then also that your wallet is unlocked and HPS > 0.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: thanospetr on March 15, 2018, 09:42:46 AM
Hello, I started mining for rosetta two days ago and I am trying to get used to the new procedures. My RAC has increased but I haven't received any payments yet. I know it has to do with the values of TaskWeight and UTXOWeight that are both zero, but I can't quite get the idea.

After executing the getboincinfo command, I get the following:

Code: [Select]
  "Command": "getboincinfo",
  "CPID": "1334aacdfb49248a75904d89ace59213",
  "Address": "BL6Chaxu4qiPawuiqZJS2iEm4Vhn1NGrcr",
  "CPIDS": "1334aacdfb49248a75904d89ace59213;",
  "CPID-Age (hours)": 422535,
  "NextSuperblockHeight": 34850,
  "NextSuperblockBudget": 2660579,
  "1334aacdfb49248a75904d89ace59213_ADDRESS": "BL6Chaxu4qiPawuiqZJS2iEm4Vhn1NGrcr",
  "1334aacdfb49248a75904d89ace59213_RAC": 1919.08,
  "1334aacdfb49248a75904d89ace59213_TEAM": 15044,
  "1334aacdfb49248a75904d89ace59213_TaskWeight": 0,
  "1334aacdfb49248a75904d89ace59213_UTXOWeight": 0,
  "Total_RAC": 1919.08,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 15963474,

After executing the podcupdate true command I get always this:
Code: [Select]
  "Command": "podcupdate",
  "PODCUpdate": "Processed 0 tasks for CPID 1334aacdfb49248a75904d89ace59213"

The getmininginfo command notes that I have some hashps, my wallet contains available bbp and I don't know if it is frozen or not, as I saw this suggegstion in a previous answer.
How should I proceed? 
Thank you
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 15, 2018, 10:01:07 AM
Hello, I started mining for rosetta two days ago and I am trying to get used to the new procedures. My RAC has increased but I haven't received any payments yet. I know it has to do with the values of TaskWeight and UTXOWeight that are both zero, but I can't quite get the idea.

After executing the getboincinfo command, I get the following:

Code: [Select]
  "Command": "getboincinfo",
  "CPID": "1334aacdfb49248a75904d89ace59213",
  "Address": "BL6Chaxu4qiPawuiqZJS2iEm4Vhn1NGrcr",
  "CPIDS": "1334aacdfb49248a75904d89ace59213;",
  "CPID-Age (hours)": 422535,
  "NextSuperblockHeight": 34850,
  "NextSuperblockBudget": 2660579,
  "1334aacdfb49248a75904d89ace59213_ADDRESS": "BL6Chaxu4qiPawuiqZJS2iEm4Vhn1NGrcr",
  "1334aacdfb49248a75904d89ace59213_RAC": 1919.08,
  "1334aacdfb49248a75904d89ace59213_TEAM": 15044,
  "1334aacdfb49248a75904d89ace59213_TaskWeight": 0,
  "1334aacdfb49248a75904d89ace59213_UTXOWeight": 0,
  "Total_RAC": 1919.08,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 2660579,
  "Total Budget (One Week)": 15963474,

After executing the podcupdate true command I get always this:
Code: [Select]
  "Command": "podcupdate",
  "PODCUpdate": "Processed 0 tasks for CPID 1334aacdfb49248a75904d89ace59213"

The getmininginfo command notes that I have some hashps, my wallet contains available bbp and I don't know if it is frozen or not, as I saw this suggegstion in a previous answer.
How should I proceed? 
Thank you

What does 'exec stakebalance' say?

Please read this paragraph of the Distributed Computing wiki:
https://wiki.biblepay.org/Distributed_Computing#PODC_Updates

Quote
The PODC Updates are sent out as a transaction from the researcher to the researchers CPID public key address, with a coinstake spend amount equal to the configuration key 'utxoamount=YYYY' found in the biblepay.conf file. In this way, the researcher proves coinstake confirmation age > 6 at the time the task was announced. This UTXOAmount influences the users UTXOWeight and therefore the corresponding magnitude and reward level.

At the moment, you need to stake at least 500BBP per - expected - Magnitude.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: thanospetr on March 15, 2018, 10:08:46 AM
Hello, the exec stakebalance outputs:

Code: [Select]
  "Command": "stakebalance",
  "StakeBalance": 62556

I previously added this value to the .conf file -> utxoamount=3000 , to check if anything changes, with no luck.

What does 'exec stakebalance' say?

Please read this paragraph of the Distributed Computing wiki:
https://wiki.biblepay.org/Distributed_Computing#PODC_Updates

At the moment, you need to stake at least 500BBP per - expected - Magnitude.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 15, 2018, 10:44:19 AM
Hello, the exec stakebalance outputs:

Code: [Select]
  "Command": "stakebalance",
  "StakeBalance": 62556

I previously added this value to the .conf file -> utxoamount=3000 , to check if anything changes, with no luck.

Okay, that seems fine. If I look your CPID up in the pools 'superblock view', I can see you, but I can't see your username nor the machines you are using. Are your computers hidden by any chance?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: thanospetr on March 15, 2018, 10:51:21 AM
Yes, they were and after un-hidding them and issuing a podcupdate I got this:
Code: [Select]
  "Command": "podcupdate",
  "PODCUpdate": "Processed (129) over 1 CPID(s) successfully."

I suppose this is good :) My TaskWeight also  became 100 from 0, but UTXWeight is still 0.

What does the amount that I choose to stake represent? Is this amount lost or is it just symbolic?
If it isn't lost, then I suppose that I have to raise it to 50001+, right?

Thank you for your time!

Okay, that seems fine. If I look your CPID up in the pools 'superblock view', I can see you, but I can't see your username nor the machines you are using. Are your computers hidden by any chance?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 15, 2018, 11:05:50 AM
Yes, they were and after un-hidding them and issuing a podcupdate I got this:
Code: [Select]
  "Command": "podcupdate",
  "PODCUpdate": "Processed (129) over 1 CPID(s) successfully."

I suppose this is good :) My TaskWeight also  became 100 from 0, but UTXWeight is still 0.

What does the amount that I choose to stake represent? Is this amount lost or is it just symbolic?
If it isn't lost, then I suppose that I have to raise it to 50001+, right?

Thank you for your time!

So the utxoamount represents how much out of your wallet you will stake for Cancer research, and its not lost, it comes back to you right away.
They are voting in 20 BBP per RAC right now, so to be safe just estimate what your RAC will be by typing 'exec getboincinfo' take a look at your RAC and estimate your future RAC value, and multiply that * 20.  Then use that as your stake amount (or higher :).  Then you should see an increase in UTXOAmount after 6 blocks of confirms after the exec podcupdate was executed.

Good luck man.


EDIT: Btw for anyone who unhides the machines, boinc obfuscates all personal information like domain name, machine name, IP, etc, it re-names this info "computer1, computer2" etc, so we do not gain any personal info other than the OS type, proc count, speed, processor type, and memory.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 15, 2018, 01:47:58 PM
Please ensure your 'exec getboincinfo' shows a valid CPID, then also that your wallet is unlocked and HPS > 0.

Yes to the above. I've been receiving regular rewards. What i meant was I downloaded 1.1.1.1 to test after reading warmoth's note. As soon as I noticed something odd with the behaviour, I immediately downgraded to 1.1.0.9b and it was fine. Was just wondering if there's a problem with 1.1.1.1 and perhaps podc updates?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 15, 2018, 02:22:17 PM
Yes to the above. I've been receiving regular rewards. What i meant was I downloaded 1.1.1.1 to test after reading warmoth's note. As soon as I noticed something odd with the behaviour, I immediately downgraded to 1.1.0.9b and it was fine. Was just wondering if there's a problem with 1.1.1.1 and perhaps podc updates?

I've updated to 1.1.1.1. and my PODC updates work :)

@West: I hope your problem will be solved. If things stop working with me, I usually just start again from scratch.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 15, 2018, 02:25:34 PM
Yes to the above. I've been receiving regular rewards. What i meant was I downloaded 1.1.1.1 to test after reading warmoth's note. As soon as I noticed something odd with the behaviour, I immediately downgraded to 1.1.0.9b and it was fine. Was just wondering if there's a problem with 1.1.1.1 and perhaps podc updates?

No problems have been reported with 1111, and 1111 is a mandatory so downgrading to 1109 would fork your chain.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 15, 2018, 02:33:46 PM
Sent you a PM Rob, did not receive a Superblock payment again.

I sent a PM to West explaining I believe his PODC update crossed while the last superblock contract was generated with him in it - IE his elements were not picked up by 51% of the sancs until after the 1am contract.

The current pool contract has him in it. 

These Pool superblocks are usually what are going to be voted in guys.

Meaning that the primary goal is to work hard to ensure your UTXO weight, task weight, and magnitude are populated in the current pool Superblock   report.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 16, 2018, 06:53:33 AM
Just got my first unbanked payment from the pool!  :D

http://explorer.biblepay.org:3001/address/BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 16, 2018, 07:51:41 AM
Just got my first unbanked payment from the pool!  :D

http://explorer.biblepay.org:3001/address/BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj

Thats awesome!  I guess the mandatory upgrade has propagated through the supermajority of the sancs.  (I saw this morning 67% of the general network had upgraded to 1.1.1.1), a much quicker response time than we had when the bot-net dragged us down.  Now do you all see why I called it a bot-net and have a dark view of the prior ecosystem?  They installed our software on so many machines they were not even able to upgrade it , and that caused us to have a very dangerous ecosystem, in that we have no control over our own software rules.  And this has little to do with being "powerful" it has everything to do with being "cutting edge" and "nimble".  If we want quarterly releases with cool new features, so we can work our way up the coinmarketcap ladder, its essential to have a network that can upgrade during mandatories.  Now these mining orgs have to come out in the light and expose themselves.  They can upgrade the single controllers easily now. 

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 16, 2018, 07:53:51 AM
Thanks for all the insight.  I PM'ed because the debug log contained some things I thought would not be ideal to share.

Great, did you get the payment?

Wait I guess I can type 'exec leaderboard', :),   "e7ae6abd6284b05f3fd5f7c780e60bc7": 21.30465742430721,
Alright congratulations, your back in!

So with West as a guineapig, remember how dangerous it is to fall out of the superblock, it could take up to 48 hours to be in the next one again, due to the sanctuary voting process.

This is a double edged sword, as some benefit from it while others are penalized - its a blessing overall that it requires work to be paid (IE leaving the controller running 24-7).

This saves up more rewards for the persistent.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 16, 2018, 12:11:43 PM
Yeah payment came through today so that is good and there have been no futher interruptions in the PoDC Updates which was the root issue.

One question, in a case like this when I don't bring my RAC to the equation, does that effectively mean that everyone else gets a slightly higher reward since the overall Team RAC is effectively lower for that superblock?

Yes very good question.

So yes, the superblock always shoots for a (fraction less than) 1000 magnitude, and attempts to use up 99.9% of the daily superblock budget, for payments within the contract.

So if someone has UTXO Weight = 0 or TaskWeight = 0, it ends up being More for the rest of the gang. 



Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: thanospetr on March 17, 2018, 12:23:37 PM
Block 35055 hit, shows next superblock budget as 1197260 at 35260, those look about where I was anticipating the breakdown should be initially.

What is the official word on staking for the UTXO reward component, and will that require a MN update to implement ?

My getboincinfo returns this:
Code: [Select]
  "NextSuperblockHeight": 35260,
  "NextSuperblockBudget": 2660579,

Is it wrong?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on March 17, 2018, 12:41:01 PM
Are you on 1.1.1.1 version?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: thanospetr on March 17, 2018, 12:43:03 PM
Are you on 1.1.1.1 version?

Not yet, so that's the culprit.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 17, 2018, 01:03:15 PM
Is the reduction in the superblock because of the tithe block?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 17, 2018, 01:03:40 PM
Block 35055 hit, shows next superblock budget as 1197260 at 35260, those look about where I was anticipating the breakdown should be initially.

What is the official word on staking for the UTXO reward component, and will that require a MN update to implement ?
Yes I agree, me too, but too bad we didn't catch it in TEST.

Hopefully this answers your question:
https://bitcointalk.org/index.php?topic=2388064.msg32447969#msg32447969

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 17, 2018, 01:05:20 PM
Is the reduction in the superblock because of the tithe block?

No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: sdc on March 17, 2018, 01:17:33 PM
No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

Got it. Thanks Rob!
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on March 17, 2018, 01:53:32 PM
Yes I agree, me too, but too bad we didn't catch it in TEST.

Hopefully this answers your question:
https://bitcointalk.org/index.php?topic=2388064.msg32447969#msg32447969

I guess my better question is when, if ever, is it going to change from 500BBP/Mag and what will be the final determining factor in deciding how much.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 17, 2018, 02:07:56 PM
I guess my better question is when, if ever, is it going to change from 500BBP/Mag and what will be the final determining factor in deciding how much.

In 1111, we have the SPM or SPR (stake per mag or stake per rac) indicator Spork doubles (double is like a floating point number) compiled in. 

So when this poll outcome :
http://forum.biblepay.org/index.php?topic=127.0

is known, then I sign a spork and induce it in the chain that night, and right away the sancs start honoring the new business logic rule for the next superblock.

So as an example if this poll ends of April Fools Day, and it dictates 20 bbp per rac, as of that evening, the sancs will start being influenced to create and vote on the contract using that new business logic.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 17, 2018, 02:15:35 PM
No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

Will the time between blocks be about what it is right now. 32.5 hours?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 17, 2018, 06:17:35 PM
Will the time between blocks be about what it is right now. 32.5 hours?

Starting at block 35110, it should technically speed up to 205 blocks per day.  Lets hope we got it right this time.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: 616westwarmoth on March 17, 2018, 11:36:52 PM
In 1111, we have the SPM or SPR (stake per mag or stake per rac) indicator Spork doubles (double is like a floating point number) compiled in. 

So when this poll outcome :
http://forum.biblepay.org/index.php?topic=127.0

is known, then I sign a spork and induce it in the chain that night, and right away the sancs start honoring the new business logic rule for the next superblock.

So as an example if this poll ends of April Fools Day, and it dictates 20 bbp per rac, as of that evening, the sancs will start being influenced to create and vote on the contract using that new business logic.

Is there a reason this poll is running so long?  20 BBP/RAC has nearly 40% of the vote in a 19 selection race.  Could we reduce it to the top three options and run a shorter vote?  Or since 20 BBP/RAC has more than the 2nd and 3rd option combined, I would think it is the winner even though it's not my choice. 
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 18, 2018, 02:48:06 PM
It seems like I missed the last two payments from my pool unbanked account.

CPID: 8791a036b545f35e9ebd9333922738ac
BBP adress: 8791A036B545F35E9EBD9333922738AC

Code: [Select]
21:42:51

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:42:51

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

This phone is only calculating for Rosetta when it's on the charger (about 10-12 hours every day). But that shouldn't need to be a problem, right?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 19, 2018, 04:35:12 PM
It seems like I missed the last two payments from my pool unbanked account.

CPID: 8791a036b545f35e9ebd9333922738ac
BBP adress: 8791A036B545F35E9EBD9333922738AC

Code: [Select]
21:42:51

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:42:51

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

This phone is only calculating for Rosetta when it's on the charger (about 10-12 hours every day). But that shouldn't need to be a problem, right?

Rob, could you shine some light on this?

Code: [Select]
UTXO amount  0.0000 bbp
UTXO weight 0 (%)

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 20, 2018, 04:04:38 AM
I don't know what happened but I got dropped down from the next payment list. I see utxoamount=0 even if PoDC payments have been happening for the latest hours without apparent trouble. I even changed utxoamount=100001 in conf file just in case...

Code: [Select]
exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422649,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19239.3,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19239.3,
  "Total Payments (One Day)": 5543,
  "Total Payments (One Week)": 70287,
  "Total Budget (One Day)": 1197260,
  "Total Budget (One Week)": 13036836,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "35465,35260,35055,34850,34645,34440,34235",
  "Last Superblock Height": 35465,
  "Last Superblock Budget": 1197260,
  "Last Superblock Payment": 5543,
  "Magnitude (One-Day)": 4.629737901541854,
  "Magnitude (One-Week)": 5.391415524441666
}

Any ideas? Thank you
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 08:56:26 AM
It seems like I missed the last two payments from my pool unbanked account.

CPID: 8791a036b545f35e9ebd9333922738ac
BBP adress: 8791A036B545F35E9EBD9333922738AC

Code: [Select]
21:42:51

exec search dcc 8791a036b545f35e9ebd9333922738ac


21:42:51

{
  "DataList": "DCC",
  "8791A036B545F35E9EBD9333922738AC (03-11-2018 16:50:26)": "8791a036b545f35e9ebd9333922738ac;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj;1986929;;1"
}

This phone is only calculating for Rosetta when it's on the charger (about 10-12 hours every day). But that shouldn't need to be a problem, right?

Hi Jaap,

I finally got a chance to look at this- and the great news is it was just a network setting set improperly and it has been corrected, so now looking at the

cat filtered | grep 8791a -B7 -A11
I see that you do have the <unbanked> indicator showing as 1 on sancs now.  This will go into effect during the next contract, so please lets see if you start receiving payments now.  It might take 24 more hours for it to cascade. 

Note that in the pool, you can look for the unbanked flag on your superblock row, to see if it shows as "1".  At that point you can expect a payment.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 08:59:22 AM
I don't know what happened but I got dropped down from the next payment list. I see utxoamount=0 even if PoDC payments have been happening for the latest hours without apparent trouble. I even changed utxoamount=100001 in conf file just in case...

Code: [Select]
exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422649,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19239.3,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19239.3,
  "Total Payments (One Day)": 5543,
  "Total Payments (One Week)": 70287,
  "Total Budget (One Day)": 1197260,
  "Total Budget (One Week)": 13036836,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "35465,35260,35055,34850,34645,34440,34235",
  "Last Superblock Height": 35465,
  "Last Superblock Budget": 1197260,
  "Last Superblock Payment": 5543,
  "Magnitude (One-Day)": 4.629737901541854,
  "Magnitude (One-Week)": 5.391415524441666
}

Any ideas? Thank you

I dont see you sending any UTXO weight out on the network:
exec search utxoweight 9689

Although I do see your cpid is present... 
I would try 'exec podcupdate true'
Lets see what kind of error you receive. 

With no UTXO stake, the utxoweight will remain 0, resulting in no superblock payments and no daily magnitude.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 20, 2018, 09:42:01 AM
I dont see you sending any UTXO weight out on the network:
exec search utxoweight 9689

Although I do see your cpid is present... 
I would try 'exec podcupdate true'
Lets see what kind of error you receive. 

With no UTXO stake, the utxoweight will remain 0, resulting in no superblock payments and no daily magnitude.

I understand, but that's the issue because I've been sending Podc updates regularly... I post the PoDC update txids since yesterday

1b21f2b352383ca00cd3c51e494cd99d032c540ba3af3f8963bd36c9b49c9ac0
2c43abb2fb1ae9e9e2db25005fb784dd045ce5fe304632f653aa0d91d2c2adbf
19ffe0b8cff60ae1939a9bf90dbff7794c99fb057090ccd6c3e73b0ea0d2f608
ed77dc115de82127c2e939594ee64993b151e80ed007172b72e7bcf70fe6e4d0
bcc9ce63827c6c29d7afea01d8068511fc7d7ebb7db2740d7f14d7aa707a0a3d
6d351f1e193535d6aa8622390374e9bc3fd1108bdfdb239d661a7ef0adfdb253
2f55f35dbabcd0fed7175e039f677533342a0442adc1b789d0a88de4735b2236
99b7bada905b0fb2c81f97e49b2468e52df341a39f91b0d351b74dc5491a6a87
9b3e2af19849bbaf2fa9a9250004f7ab69eeb4e82bfb5173dbfad5f3d747030c
05ae2f2d9776175ab37758b2bee3c73c12d7fbf7cf5847beb0b27f07bd9fb2fc
af897c9d4eb63eb8e538392c63b556a8f654eae2b397d6b83058fa9a2042c4bf
c9938257ee11646f6eb0984aaaadd08e08c71048c5aff802db7c6a8617a5d066
ea695770ba3708dbaec396777c2b8940a693574b52444191c832a640557981ab

Some of them were forced

I tried to re-associate but nothing. I'll try podcupdate true and see..

Edit:
Code: [Select]
exec podcupdate true

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (128) over 1 CPID(s) successfully."
}


I will wait and see.

By the way I remember the only change is that yesterday afternoon I password locked the wallet. But when I reloaded I unlocked it for PoDC. I don't know if it may be the cause.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 09:51:31 AM
I understand, but that's the issue because I've been sending Podc updates regularly... I post the PoDC update txids since yesterday

1b21f2b352383ca00cd3c51e494cd99d032c540ba3af3f8963bd36c9b49c9ac0
2c43abb2fb1ae9e9e2db25005fb784dd045ce5fe304632f653aa0d91d2c2adbf
19ffe0b8cff60ae1939a9bf90dbff7794c99fb057090ccd6c3e73b0ea0d2f608
ed77dc115de82127c2e939594ee64993b151e80ed007172b72e7bcf70fe6e4d0
bcc9ce63827c6c29d7afea01d8068511fc7d7ebb7db2740d7f14d7aa707a0a3d
6d351f1e193535d6aa8622390374e9bc3fd1108bdfdb239d661a7ef0adfdb253
2f55f35dbabcd0fed7175e039f677533342a0442adc1b789d0a88de4735b2236
99b7bada905b0fb2c81f97e49b2468e52df341a39f91b0d351b74dc5491a6a87
9b3e2af19849bbaf2fa9a9250004f7ab69eeb4e82bfb5173dbfad5f3d747030c
05ae2f2d9776175ab37758b2bee3c73c12d7fbf7cf5847beb0b27f07bd9fb2fc
af897c9d4eb63eb8e538392c63b556a8f654eae2b397d6b83058fa9a2042c4bf
c9938257ee11646f6eb0984aaaadd08e08c71048c5aff802db7c6a8617a5d066
ea695770ba3708dbaec396777c2b8940a693574b52444191c832a640557981ab

Some of them were forced

I tried to re-associate but nothing. I'll try podcupdate true and see..

Edit:
Code: [Select]
exec podcupdate true

{
  "Command": "podcupdate",
  "PODCUpdate": "Processed (128) over 1 CPID(s) successfully."
}


I will wait and see.

By the way I remember the only change is that yesterday afternoon I password locked the wallet. But when I reloaded I unlocked it for PoDC. I don't know if it may be the cause.


Hmmm, it looks like these transactions were signed by a wallet not associated to the CPID - another words, to the foreign nodes these transactions look forged.

The first few on the list were signed by BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H, yet when I look in the chain, exec search dcc 96892, I see your CPID is associated with a different public wallet key.

The controller doing the podcupdate should be the one associated with the CPID.

(Otherwise nodes will disregard your podcupdates as if the signature is forged).

EDIT: Whats the TXID of the one you just did successfully, I can check it?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 20, 2018, 09:59:53 AM

Hmmm, it looks like these transactions were signed by a wallet not associated to the CPID - another words, to the foreign nodes these transactions look forged.

The first few on the list were signed by BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H, yet when I look in the chain, exec search dcc 96892, I see your CPID is associated with a different public wallet key.

The controller doing the podcupdate should be the one associated with the CPID.

(Otherwise nodes will disregard your podcupdates as if the signature is forged).

EDIT: Whats the TXID of the one you just did successfully, I can check it?

I don't really know which is the last one that worked, How can I know? to me all seem exactly the same.

And I have been using the same address for a week without a problem. In fact I got payments until yesterday ...

Edit: ok I will start again with a "new" wallet file and re-associate from scratch to avoid interferences with other addresses.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 10:57:14 AM
I don't really know which is the last one that worked, How can I know? to me all seem exactly the same.

And I have been using the same address for a week without a problem. In fact I got payments until yesterday ...

Edit: ok I will start again with a "new" wallet file and re-associate from scratch to avoid interferences with other addresses.

I meant last one sent by timestamp, not last one that worked (last one that worked for you is probably the one that is invalid for me).

Anyway, if you reassociate your CPID with force, and try to sign with a different wallet.dat, this type of forge will happen.

Nothing changes in the chain, so it must have changed on your end - otherwise I would have over 1,250 messages telling me the system is broken completely.  Unless we have a bug that is only transmitting half of the public key or half of the cpid in the chain, but these messages you pasted earlier are complete (as they end in an XML suffix with an end character + a suffix).  The data all comes from your wallet, so there is no way other peoples data is intermingled into your data either.

You should never have to start over, unless you accidentally reassociated with a second wallet.dat.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 20, 2018, 11:46:00 AM
I just created a clean wallet, imported the address to stake with, re-associated and made podcupdate true, waited for confirmations,

Code: [Select]

exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422657,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19534.21,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19534.21,
  "Total Payments (One Day)": 5543,
  "Total Payments (One Week)": 70287,
  "Total Budget (One Day)": 1197260,
  "Total Budget (One Week)": 13036836,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "35465,35260,35055,34850,34645,34440,34235",
  "Last Superblock Height": 35465,
  "Last Superblock Budget": 1197260,
  "Last Superblock Payment": 5543,
  "Magnitude (One-Day)": 4.629737901541854,
  "Magnitude (One-Week)": 5.391415524441666
}


 :(

The PoDC transactions:
172bd33f5ee7757d82464b071bc312cf4f570fa1d6d473c94bb42c84ab50ee5d
8a4df3cdc03ad31be3a4acf7d20edc2229cd0c96c1bed6756ec20c7add5c7bce

How can you check that it's valid or it is rejected?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 12:33:56 PM
I just created a clean wallet, imported the address to stake with, re-associated and made podcupdate true, waited for confirmations,

Code: [Select]

exec getboincinfo

{
  "Command": "getboincinfo",
  "CPID": "96892ec0fc8a2710fa84f26c9c84cd3e",
  "Address": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "CPIDS": "96892ec0fc8a2710fa84f26c9c84cd3e;",
  "CPID-Age (hours)": 422657,
  "NextSuperblockHeight": 35670,
  "NextSuperblockBudget": 1197260,
  "96892ec0fc8a2710fa84f26c9c84cd3e_ADDRESS": "BE2XrQurnfzbqAGgMX9F8dXEyReML2Zr6H",
  "96892ec0fc8a2710fa84f26c9c84cd3e_RAC": 19534.21,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TEAM": 15044,
  "96892ec0fc8a2710fa84f26c9c84cd3e_TaskWeight": 100,
  "96892ec0fc8a2710fa84f26c9c84cd3e_UTXOWeight": 0,
  "Total_RAC": 19534.21,
  "Total Payments (One Day)": 5543,
  "Total Payments (One Week)": 70287,
  "Total Budget (One Day)": 1197260,
  "Total Budget (One Week)": 13036836,
  "Superblock Count (One Week)": 7,
  "Superblock Hit Count (One Week)": 7,
  "Superblock List": "35465,35260,35055,34850,34645,34440,34235",
  "Last Superblock Height": 35465,
  "Last Superblock Budget": 1197260,
  "Last Superblock Payment": 5543,
  "Magnitude (One-Day)": 4.629737901541854,
  "Magnitude (One-Week)": 5.391415524441666
}


 :(

The PoDC transactions:
172bd33f5ee7757d82464b071bc312cf4f570fa1d6d473c94bb42c84ab50ee5d
8a4df3cdc03ad31be3a4acf7d20edc2229cd0c96c1bed6756ec20c7add5c7bce

How can you check that it's valid or it is rejected?

Yeah, there is something funny going on here.  I see your taskweight in the chain, I see your Tx, and I see your updated CPID, but its almost as if it is ignoring your UTXO weight only.  This time it does look valid (probably what caused you to change it to begin with was the fact that you had no utxo weight), I see the CPID matches the sig and the key, so now its an interesting problem.

Im going to have to add a command to the RPC to diagnose this one.

Hang on please, I have an appointment in an hour but Ill try to work on this now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 20, 2018, 12:38:21 PM
Sure, thank you
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 01:30:43 PM
Sure, thank you

Getting closer; what OS and BBP compile version are you currently running that is emitting this particular sig?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 20, 2018, 02:02:13 PM
Getting closer; what OS and BBP compile version are you currently running that is emitting this particular sig?

OS: Windows Server 2012 R2 Standard
BBP compile version: 1.1.1.1
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 02:33:45 PM
OS: Windows Server 2012 R2 Standard
BBP compile version: 1.1.1.1
Alright, I found the bug!  You definitely were not at fault, you exploited something very interesting.
So we have alot of sigs in the chain already, probably 4000 or so, and we have 12 that are bad.  Im guessing that maybe 6-12 are yours.
So whats happening is there is a piece of math in the code that tacks your CPID signature on the back of a PODC update.  Since we only allow up to 3000 characters of free ascii space per Coinstake recipient, we add on more recipients (from your own address book) for space and change (change as in money owed to you if you broke a large bill in the coinstake).
So there is a funny behavior that occurs if the PODC update is between 3000 and 3100 long, the ceiling function returns like 1.01 (which gets rounded to 2), but for some reason when that happens, the change recipient (you) gets duplicated and it mangles the CPID base64 portion of the sig.  This only happens for PODCs that are between 3000 and 3100.  If they are 3101 or lower than 3000 they are OK.
Yours is 3100.

So anyway I am patching this now, windows is going to take hours to compile and Ill be out meeting someone soon, but Ive unit tested it and I believe its going to solve the problem globally.

Ill check in the unix version in about 15 mins, so if that helps you send it out you can grab that soon... Otherwise Ill check in windows tonight before the end of the night.

Im glad you found this, thanks!

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 02:46:35 PM
Biblepay 1.1.1.2
Leisure Upgrade

- Resolve bug in corrupted outbound PODC Updates due to inbound change
duplicating a portion of the cpid signature


* * Windows is Compiling * *
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 20, 2018, 02:47:30 PM
Great! I will wait, anyway I'm out of tomorrow´s reward too so no hurry.

Thank you for the incredible efforts.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 20, 2018, 03:38:20 PM
Hi Jaap,

I finally got a chance to look at this- and the great news is it was just a network setting set improperly and it has been corrected, so now looking at the

cat filtered | grep 8791a -B7 -A11
I see that you do have the <unbanked> indicator showing as 1 on sancs now.  This will go into effect during the next contract, so please lets see if you start receiving payments now.  It might take 24 more hours for it to cascade. 

Note that in the pool, you can look for the unbanked flag on your superblock row, to see if it shows as "1".  At that point you can expect a payment.

Great! I'm going to keep a close watch. Also, awesome that the average blocktime finally is 7 minutes. I'm curious what kept the blocktime around 10 minutes all this time :)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 07:48:33 PM
Great! I will wait, anyway I'm out of tomorrow´s reward too so no hurry.

Thank you for the incredible efforts.
Ok, 1.1.1.2 is out there if you want to give it a try, let me know a txid and Ill look at the 'getrawtransaction txid 1'.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 20, 2018, 07:50:48 PM
Great! I'm going to keep a close watch. Also, awesome that the average blocktime finally is 7 minutes. I'm curious what kept the blocktime around 10 minutes all this time :)

It was the biblehash functions late block threshhold feature.  The feature considers a block late after 15 mins, then reduces difficulty to make it 90% easier to solve by anyone (including non cpids).  The average amount of late blocks added 20% to the daily duration of blocks, despite having 420 seconds set in DGW (which is our difficulty algorithm).  So to fix it we now undershoot it by 20% - that teamed up with some 15.01 minute blocks averages out to 7 mins now.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on March 21, 2018, 01:54:07 AM
Ok, 1.1.1.2 is out there if you want to give it a try, let me know a txid and Ill look at the 'getrawtransaction txid 1'.

It worked! The funny thing is that I didn't even have to exec podcupdate to see the utxoamount again.

Some samples

2hr before updating (still with 1.1.1.1):
3abf4bdd39b918de8354df6143ac53f5948d7a16ea1b454ea7ee82e6570923b7

After updating to 1.1.1.2
632d8ec195e01a3679d0928196da7739e2e3912592dab84afa353bd1880c9a4a

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: Rob Andrews on March 21, 2018, 07:50:13 AM
It worked! The funny thing is that I didn't even have to exec podcupdate to see the utxoamount again.

Some samples

2hr before updating (still with 1.1.1.1):
3abf4bdd39b918de8354df6143ac53f5948d7a16ea1b454ea7ee82e6570923b7

After updating to 1.1.1.2
632d8ec195e01a3679d0928196da7739e2e3912592dab84afa353bd1880c9a4a

Great!  Yes looking at getrawtransaction 632d8, it looks correct now.  Awesome.

Yes, doing the exec search utxoweight 9689, I can see your weight now.

Thats good we have this flowing out earlier in the cycle before we have a lot of researchers, as that malformed sig could be a crash risk, although I see the code handled the malformed sigs OK but would rather not see it iterating over hundreds of malformed sigs obviously.

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 21, 2018, 05:58:11 PM
It was the biblehash functions late block threshhold feature.  The feature considers a block late after 15 mins, then reduces difficulty to make it 90% easier to solve by anyone (including non cpids).  The average amount of late blocks added 20% to the daily duration of blocks, despite having 420 seconds set in DGW (which is our difficulty algorithm).  So to fix it we now undershoot it by 20% - that teamed up with some 15.01 minute blocks averages out to 7 mins now.

Thank you for the clear explanation :) I understand.

In other news: I got an unbanked pool-payment again!!  ;D
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 22, 2018, 08:27:08 PM
Rob, Don't know if you know but there seems to be a problem with the blockchain. We are stuck on 36079.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 23, 2018, 09:44:45 AM
Didn't get a payment again with my pool-unbanked-account  :'(

Code: [Select]
36285 3/23/2018 9:35:55 AM jaapgvk_unbanked_poolCPID 8791a036b545f35e9ebd9333922738ac 0.059 1986929 15044 0 0 5069682 1 0 299 299 1 4
I did get a payment today :) Just keeping you updated. Let's see how it rolls from here...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 25, 2018, 09:20:48 PM
I'm trying to change the number of threads on a linux machine but I'm getting this error:

biblepay-cli setgenerate true 4
terminate called after throwing an instance of 'std::runtime_error'
  what():  CWallet::GenerateNewKey(): AddKey failed

It crashes the daemon and I have to restart it.

Noticed setgenerate true will only go up to 3. Set to 4 threads and it will crash.

Debug.log
Code: [Select]
2018-03-26 03:25:18  ** Started 3.000000 BibleMiner threads. **
2018-03-26 03:25:20
BiblepayMiner -- terminated
2018-03-26 03:25:20
BiblepayMiner -- terminated
2018-03-26 03:25:21  Starting Thread #0.000000 with Bible #0.000000      2018-03-26 03:25:21 BibleMiner -- started thread 0.000000
2018-03-26 03:25:21  MinerSleep 0.000000
2018-03-26 03:25:21  Starting Thread #1.000000 with Bible #0.000000      2018-03-26 03:25:21 BibleMiner -- started thread 1.000000
2018-03-26 03:25:21  MinerSleep 0.000000
2018-03-26 03:25:21  Starting Thread #2.000000 with Bible #0.000000      BibleMiner -- started thread 2.000000
2018-03-26 03:25:21  MinerSleep 0.000000
2018-03-26 03:25:21  Starting Thread #3.000000 with Bible #0.000000      BibleMiner -- started thread 3.000000
2018-03-26 03:25:21  MinerSleep 0.000000
2018-03-26 03:25:21  ** Started 4.000000 BibleMiner threads. **
2018-03-26 03:25:22 keypool added key 1102, size=1000
2018-03-26 03:25:22 init message: Loading wallet... (110.09 %)
2018-03-26 03:25:33
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: madmurphy on March 26, 2018, 12:48:37 AM
Is anyone else getting the message in Boinic that there is no work to do ?
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 26, 2018, 02:32:50 AM
Is anyone else getting the message in Boinic that there is no work to do ?

Yeah, it seems like Rosetta@home has run out of work for the moment. You can check the server-status here:
https://boinc.bakerlab.org/rosetta/server_status.php

(It does say 'Tasks ready to send 18124'  on that page somewhere, but I don' t know what that means exactly.)

There is work trickling down, probably from workers who have passed the due-date. Can' t really find any news about this. Maybe they are adjusting the work. There was something similar going on with the Android tasks about two weeks ago.

Or maybe it' s because they can't handle the growth of Biblepay ;)
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 26, 2018, 02:34:35 AM
Didn't get a payment again with my pool-unbanked-account  :'(

Code: [Select]
36285 3/23/2018 9:35:55 AM jaapgvk_unbanked_poolCPID 8791a036b545f35e9ebd9333922738ac 0.059 1986929 15044 0 0 5069682 1 0 299 299 1 4
I did get a payment today :) Just keeping you updated. Let's see how it rolls from here...

Also got a payment today. And I also signed up another pool-unbanked-testaccount that also got payed.

Seems that not getting payed a few superblocks ago was just a one-off thing...
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 26, 2018, 09:34:36 PM
encryptwallet  seems to be missing from the cli help.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on March 30, 2018, 05:13:05 AM
I got an error last night on 1.1.1.4.

gzip: /home/biblepay/.biblepaycore/SAN/user2.gz: unknown method 50 -- not supported
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on March 31, 2018, 02:28:18 AM
I've got three exactly the same payments in BBP in a row on my unbanked testaccount:

http://explorer.biblepay.org:3001/address/BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj

CPID: 8791a036b545f35e9ebd9333922738ac

Coincidence or bug?

Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: jaapgvk on April 06, 2018, 08:38:50 AM
I've got three exactly the same payments in BBP in a row on my unbanked testaccount:

http://explorer.biblepay.org:3001/address/BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj

CPID: 8791a036b545f35e9ebd9333922738ac

Coincidence or bug?

Got another two exactly the same payouts in a row.
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: T-Mike on April 13, 2018, 04:05:12 PM
Getting these errors on my linux machine.

************************
EXCEPTION: NSt8ios_base7failureB5cxx11E       
String length limit exceeded: iostream error       
biblepay in ProcessMessages()       



************************
EXCEPTION: NSt8ios_base7failureB5cxx11E       
String length limit exceeded: iostream error       
biblepay in ProcessMessages()       



************************
EXCEPTION: NSt8ios_base7failureB5cxx11E       
String length limit exceeded: iostream error       
biblepay in ProcessMessages()       



************************
EXCEPTION: NSt8ios_base7failureB5cxx11E       
String length limit exceeded: iostream error       
biblepay in ProcessMessages()
Title: Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)
Post by: MIP on May 17, 2018, 05:50:29 AM
I just leave a quick note to say that my windows wallet has stopped to send automatic PoDC updates a few days ago. I tried to restart and all that but to no avail.
 
Currently I'm doing it manually every 12h to keep on staking. I don't know where to start checking but when I have a bit more time I´ll check the logs in case I see something evident.