Distributed Computing Start Guide

From BiblePay Wiki
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 [email protected], 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 mining setup:

Jarid has purchased 50 windows PCs, and rents 50 linux virtual machines.

Jarid's CPID is 12345.

Jarid's Biblepay address is BCDE.

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 one home Windows machine (this is the controller wallet) (or, Linux may be used if desired).

Jarid boots up Biblepay wallet, and finds his BBP Receiving address is BCDE (by clicking File | Receiving Addresses).

Jarid will remote in to each of his distributed computers, launch BOINC, and click Tools | Add Project | [email protected] | Next. From the prompts, enter the Rosetta account e-mail and password (If you do not have one, click Join and create an account from any machine).

Note: If you desire privacy, you may enter your nickname in for your username and your anonymous info for your city and area, as 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. (Note: We will publish a guide with tips on how to set up CPU usage and optimization. We support everything from cancer-mining during periods of inactivity all the way to full-bore processing at 100%).

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

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

Thats it. You are set. You will now receive rewards each day for distributed-computing.

To find out if your settings were successful:

From the RPC type: exec getboincinfo

Summary of Relationship Between Computers, Researchers, Biblepay Wallets, CPIDs, BiblepayAddresses, and Rosetta Instances

The single home computer controller wallet is one instance of biblepay, and although it contains many public biblepay addresses, only one is used to attach your wallet to a CPID. So we have One controller wallet, with One public Key (your address), attached to One CPID.

One CPID is attached to One Researcher. One CPID may participate in many projects. Since Biblepay only supports one project, One CPID is pointed to One project (Rosetta).

Each CPID has one or many computers. So think of One CPID referring to many computing devices.

Relationship summarized: Jarid R. Researcher->One Biblepay Wallet->One Public BBP Receive Address->One Cpid->One Project (Rosetta)->MANY MINING INSTANCES

Credit Computation

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 (Recent-Average-Credit is the half life of your total rosetta credit, it decays constantly, but is useful in measuring an accurate representation of the work put into the project on a regular basis - see more on 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 as a team a 10,000 total Rosetta RAC for the next superblock. Each researcher has contributed 10% toward the superblock. Therefore, each researcher should be compensated 10% of the superblock value.

(Note, in this example, each Researcher has a magnitude of 1000). (Magnitude is computed by assessing the Individual Researchers Share of RAC * 1000).

Magnitude is also your relative strength to another researcher. If Joe has a magnitude of 700, and Jarid is computing at 350, Joe has done 2 Times the work as Jarid in the recent period.


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 researchers.

So, in our example with 10 equal researchers, each would receive 121,200 BBP per day.


To install BOINC on Windows:


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 ****
        • NOTE2: I have been running Rosetta natively (using the 9.56meg download of BOINC) and have never encountered a security problem *****