Distributed Computing Start Guide

From BiblePay Wiki
Revision as of 22:51, 6 February 2018 by Admin (talk | contribs)
Jump to: navigation, search

Welcome to Biblepay Distributed Computing - Getting Started

Each Biblepay Researcher participates in one or more Distributed Computing projects. Biblepay currently only supports Rosetta@Home, since this project helps cure cancer, and we are aligned with Healing in Jesus Name.

One researcher may wish to participate in a project on multiple machines. You may use windows, linux, or Android ARM devices.

A single researcher is identified by One CPID (Cross-Project-Identifier).

Therefore one CPID is pointed to All of your computing devices that compute to help cure cancer.

The Biblepay Controller Wallet will create One public key to be associated with your single Researcher CPID.

You do NOT need to run multiple copies of Biblepay. You only need one controller wallet, and many research machines.

Let us analyze a complicated researchers mining setup:

Jarid has purchased 50 windows PCs, and rents 50 linux virtual machines. Jarid's CPID is 12345.

Jarid's Biblepay address is BCD.

On each of the 50 PC's Jarid will install one copy of Rosetta (using BOINC - see below), and on each linux virtual machine, one copy of Rosetta (using BOINC).

Jarid will install Biblepay on his home Windows machine (this is the controller wallet) (of course, the controller wallet may be linux).

Jarid boots up Biblepay, and finds his BBP Receiving address is BCD.

Jarid will remote in to each of his distributed computers, launch BOINC, and click Tools | Add Project | Rosetta@Home | Next. From the prompts, enter the Rosetta account e-mail and password (If you do not have one, click Join and create an account. Note: If you desire privacy, you may enter your nickname in for your username and your anonymous info for your city and area, we take privacy seriously. No personal information is transmitted from Biblepay to BOINC or from BOINC to biblepay, except your CPID. Your IP is handled by the BOINC system, and not recorded by biblepay). Click Finished.

At this point the remote machine will start computing Rosetta tasks.

After you finish installing the cancer miner on every machine, come back to the controller wallet (biblepay).

On your single biblepay wallet, click Distributed Computing. Type in your Rosetta E-Mail and Password and click Associate.

Thats it. You are set.

To find out if your settings were successful:

From the RPC type: exec getboincinfo

Once per day, the distributed computing subsystem will automatically airdrop your payments to your wallet in the daily superblock.

Each CPIDs performance is measured in the form of RAC (RAC is the half life of your total rosetta credit).

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

So let us analyze Jarids RAC for Rosetta:

Let us assume Biblepay has 10 Researchers, each with One CPU running 24 hours per day - mining Cancer Research through Rosetta. Each researcher has accumulated 5,000 total credit points. Each researcher's RAC is now 1,000 (Recent-average-credit). This gives Biblepay a 10,000 total RAC for the superblock. Each researcher has contributed 10% toward the superblock.

This gives each researcher a magnitude of 1000. (Magnitude = Individual Researchers Share of RAC * 1000).

Another way to look at magnitude is your relativity to another researcher. If Joe has a magnitude of 700, and Jarid 350, Joe has done 2 Times the work as Jarid in the same period.

Payments

Proof-of-work (Heat-related) payments have been diverted to proof-of-distributed-computing. This means that Biblepay currently has approx. 1,212,000 BBP available per day in its distributed-computing budget.

The daily superblock will contain 1,212,000 in payments split according to the share of work done by the reasearchers. So, in our example with 10 equal researchers, each would receive 121,200 BBP per day.