Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Rob Andrews

Pages: 1 2 3 4 5 6 [7]
Each month we sponsor approximately 188 orphans currently.
Rob, the lead dev charges the expense on his credit card, and keeps a copy of the receipt. 
The expenses can be viewed by navigate to | Expenses and viewing the December PDF.

Since inception, Rob has spent $30,161.00 for BiblePay orphan premiums.  This can be audited by viewing the sum of all payments using the above link.

Rob has only raised $19,671 in orphan fundraisers however.  See | Orphans | Orphan Fundraisers.  You can audit the total by finding the sum of all fundraisers.

This leaves a deficit of $10,490 owed to Rob for previous activity.
This $10,490 includes our current actual December 2017 invoice for $7,068.00, spent on 12-20-2017.

Receipt here:


$19671 raised
$30161 spent
Out of the $30161, $7068 was for December 2017.

Therefore I am requesting 2894609 biblepay for December 2017 for reimbursement of these monthly premiums.

A new record will be logged as I sell the 2.8MM on the exchange, and anything over will be used to sponsor new orphan premiums (but based on 12 months for stability), so this proposal does not benefit Rob in any way shape or form.

I am committed to spending 100% of this proposals funded amount back into Charitable benefits for the orphans.

Archived Proposals / Unquestionably Horrible Proposal
« on: December 19, 2017, 06:31:57 am »
I have the dumbest idea ever, but would like to receive 1000 BBP for it.

Lets branch BiblePay into a version for non-believers and launch it on April Fools day 2018?


Budget Source: PR Budget

Amount: 1000 BBP

I think this move will be good for PR.

Archived Proposals / First Prod Test Proposal
« on: December 15, 2017, 01:43:35 pm »
This is a test proposal. 

Im asking 250 BBP for fixing an SQL query deadlock in the pool.

EDIT: Please charge this 250 BBP to IT.

General Support / Help with Mining Set Up
« on: December 02, 2017, 07:12:57 am »
If anyone is having trouble setting up the config file for pool mining, please create a topic or post a message here.

Two of the top 6 exchanges have agreed to list BiblePay for a total fee of 3.3BTC in order to help us achieve our goal of sponsoring more orphans.

Should we mint a block for this fee during our mandatory release at Christmas?

Or, should we wait until sanctuaries are up and running and consider making this a budget item in our future PR budget and vote on this like a normal item next year?

(The risk is-- maybe BTC will be more expensive by then, or the Exchange May withdraw the offer).

So, this is one opportunity that looks like we may want to jump on, but I leave this up to the community.


Around Christmastime, we will be going live with Sanctuaries.  At that time, the automatic 10% tithing block (for our Orphans) stops, BUT, with our superblocks and sanctuaries, we will continue to vote to fund the budget to pay for the orphans. 

The current breakdown for each Biblepay block is as follows: (With each block paying between 5000 and 20000 BBP, depending on network Difficulty and the deflation level):

5% is allocated from each block for IT expenses (such as payroll, web hosting fees, partner integration expenses etc).
10% is allocated from each block for Charity (this is where the budget will come from to pay for Compassion for example).

We currently do not have a budget for PR (public relations campaigns) or for P2P features (Features such as orphan letter writing, Pay To Preach, Pay to be a Priest, FAQ writers, Social Media functions, etc).

Since I personally do not wish to change the allocation breakdown now for integrity reasons, I will not make any adjustments at this point to the permanent breakdown. 

     However, with all of the recent good ideas that have been floating around, such as rewarding members for being Discipleship Leaders, or Pay for Priesting, or Pay for Orphan writing fees, etc, and with the positive impact of PR campaigns, I do not wish for us to miss the opportunity to vote  for the possible inclusion of PR budgets or P2P budgets permanently in our superblock reward ecosystem.

Hence the reason we are brought here for the poll.

The poll runs for 31 days (Ending 12-4-2017).

Please vote on potentially changing the superblock budget to include PR and/or P2P expenses on a regular basis.

 If the community decides to include a PR budget or a P2P budget, we will make the necessary adjustments in the Christmas Sanctuary mandatory release, and they will become a permanent part of BIblePay.

Thank you for participating!

Hello all fellow BiblePayers,

This is a proposal to fund orphan benefits for our 115 current active orphans.

The recurring fee is $38 per child, so we are requesting $4000 for the month of October 2017.

For testnet purposes, the estimated total BBP requested is 40,000.

Please vote on this proposal from your sanctuary.

Good Afternoon All,

It is time to Test sanctuaries in Testnet.

- Testing requires linux - because windows will not run watchman on the wall (thats the decentralized sanctuary database)
- Testing requires 500,000 TestNet BBP to be sent to the new testnet masternode (actually send more, so you have extra first) - this is not the final amount to run a sanctuary, its the testnet amount
- Testing requires an external open IP, IE you need to be able to run with the firewall port 40001 open
- Testing needs to have the latest version of BBP compiled from source

If anyone needs test BBP, let me know.

Here is a guide to explain how to start a masternode:
(*** NOTE!!!  The above guide says 1 million BBP is required.  Its actually 500,000 BBP in testnet!  Please dont try 1 million as it will not work ***)

** Note that this procedure documented above actually failed.  It failed when I took a look at the log in the actual masternode wallet, an error was generated saying something to the effect of invalid escrow sent to the masternode. 

To get around this, send the test biblepay to the masternode wallet, create the  private key on the masternode, set the masternodeprivatekey and masternode=1 in the config, and then we can resume testing.  If anyone can get this working in 'cold' mode (that means the mastnode has 0 funds in the wallet with remote activation working) that would be extremely valuable.  I will obviously help with this, as we cant go live until cold mode works, but I also need to move past and start testing the governance commands next.

My first test procedure is lets ensure we have 5+ masternodes running and see if we can all see each other and stay in sync.  We now have 1 minute blocks on testnet.

PS: To install watchman-on-the-wall, please see the "BuildBiblePay.txt" document in the root.  It has a section called Watchman. 

Note, I will modify the wiki entry to explain how to add watchman to the cron.

TestNet Discussion Archive / BLOCKCHAIN NEWS
« on: September 24, 2017, 10:52:40 am »
This is the testnet thread for :

- Testing Block Chain News (Add an article, View an article)
- Possibly: Viewing a Gui list of articles, Deleting an article, Editing an article
- Fixing Nanaminers double free or corruption mining error
- Baby steps for pre-testing of sanctuaries (primarily as since we will have many testnet nodes online this gives the dev a chance to verify governance proposal creation works, and create the web interface for proposal lists, and proposal voting)

To get started, please download or later from (or build

Launch in testnet mode like this:

cd c:\program files\biblepaycore
biblepay-qt -testnet

Read this wiki page on Block Chain News:

Start by creating a sample blockchain news article to get the feel of how this is done, and optionally publish one.

Note, that the first time you view an article, the images do not load quick enough and you may have to close the preview window and re-open it.  Solutions are welcome.

When you click Read Block Chain News, and enter the TXID, you should see this:

« on: September 02, 2017, 02:36:28 pm »
- Today we pay our recurring orphan commitment expenses
- We sponsor new orphans if we can afford it
- We create an audit record

TestNet Discussion Archive / [CLOSED] f7000 TestNet Testing Thread
« on: September 01, 2017, 07:56:36 am »
Welcome Bible Pay Users,

As you know we have had an exponential increase in interest and network hashing against Bible Pay since the launch, and now it is very hard to solo mine.  As a result, our Dev Team is writing a customized Bible Pay pool.

(The custom pool is necessary since we have a proprietary hash function that is resistant to ASIC and GPU mining.  In addition in the future the algorithm will be extended to raise the bar even higher, by requiring the full nodes to hash transaction lookups based on deterministic hash outputs, requiring the miners to be full nodes).

The purpose of this thread is to invite users to help test the pool from Test Net, to ensure it is ready for primetime.

We need to test things like: Hash Rate measurements, fair block payouts in the block distribution table, an accurate payment distribution at the time the block is solved, mining from many miners under one miner name to one pool, mining from multiple miners to one pool, the isolation of testnet from main net, the ability to withdraw BBP from the pool, the reliability of the pool, the reliability of the client miner, the fallback to solo mining if the pool is down, etc.  I will add more specific test cases and welcome any test cases.

Here is the location to download the latest wallet:
Note, in order to pool mine, you will need at least v1.0.1.8 of the wallet (both daemon and qt should work fine).

How to set up the configuration for pool mining:

On windows, navigate to %appdata%\biblepaycore.  On linux, navigate to ~/.biblepaycore.

Edit the biblepay.conf file, and place the following lines in the config:

pool= <- Note this URL is not live until approx Monday Aug 7th (Dev is deploying the pool tonight)
workerid=the_worker_id (explained below)

After upgrading biblepay and modifying the config, biblepay wallet will automatically revert to solo mining if it cannot connect to the pool, even if the pool goes down for maintenance while you are on vacation.

Next, you will need to configure the Web site side of the pool.

In your web browser navigate to the Pool URL (see pool= above), and click Register, and create a web account.
After that, go the Main menu, then Account, and add a Miner.
(The Notes textbox may be filled in with something personal, like Rooftop linux i686 etc.)
Save the miner record.
Take the name of the miner (IE the worker ID), and edit your config file, setting it where we have "workerid=" in the above example and restart biblepay.

Next, check your mining stats as you normally would (IE check getmininginfo), you may do this by clicking Tools | Information | Console, and then type "getmininginfo".

The pool exposes a few lines of text for debugging purposes, the PoolInfoLine1 is just populated with the current Pool URL if your node is pool mining, and the Pool Miner Guid is populated in Line2.  Note this is just technical info and you do not need to know this.  This is useful if the pool goes down and you want to know if you are pool mining or not.  We have a field called "pool mining: true/false" that sums up what the miner is doing.  If any thread is successfully pool mining, the value is true, otherwise its false.

Please hold off on mining against the main chain In pool mining mode until we fully test the client.  Mining on the main chain in the pool could result in lost BBP, as the pool will sign the block and have no idea who to pay currently (until we verify the distribution system works).  NOTE: To disable the pool settings once you are done testing on that node for the day (IE if you want to mine on the main chain outside of the pool) just put an x in front of the pool= entry in your config file and restart in prod mode.  (IE

To start your client in testnet mode do the following:

cd c:\program files (x86)\biblepaycore
biblepay-qt -testnet
The background should be green if in testnet.  Please do all of the testing in testnet.
Note on the above biblepay.conf configuration settings:
You will need to copy the biblepay.conf settings from the biblepay.conf file down to the \testnet3\biblepay.conf file (IE just let the coin start, it will create the file, close the wallet, open the config, copy the setting rows, paste them into the target file, restart the coin).

(I realize this is convoluted, but Biblepay/Bitcoin have the settings coalesced like this for a certain reason so its easier for us to go through the double settings now rather than change the coalesce rules.)

Note that this version of the miner updates the hashmeter more slowly to squeeze out as much performance as possible, so be patient when re-running getmininginfo, as it is delayed approximately 30 seconds before a change occurs.

Alright, good luck everyone, lets make this a great pool.

As of Aug 6th at 20:00 CST US time, the pool has not yet been deployed.  I will edit this message as soon as the website is ready for you all to create accounts.

BiblePay discussion / BiblePay - New Coin Launch - Official Thread
« on: June 05, 2017, 08:20:09 pm »


LAUNCH DATE:  JULY 23, 2017 at 17:00:00 CST



First coin with the KJV Bible compiled in the source, and utilizing the Bible in the hashing algorithm, while spreading the gospel throughout the IT community.  The blocks also hash to chained bible verses.





Backup Forum:




Exchange Go Live Date:  August 15th 2017






A secure blockchain benefiting those in distress - 10% of the emission goes to sponsoring Orphans, with provable contributions, expenses contributed to  - and future charities that are more than 75% efficient.  ** NOTE: THE COIN HAS RPC COMMANDS THAT PROVE 100% OF CONTRIBUTIONS ARE SPENT THE WAY INTENDED **

Proof of Work has been replaced with Proof Of Biblehash (POBh) - an algorithm that compensates full nodes participation,
  while preventing GPUs and ASIC by requiring full blockchain transaction referencing in the hashing function,
along with chained bible verses.  This means biblepay subsidizes full nodes that stay online.

Seven minute block targets minimize the blockchain file size, yet BiblePay does support Dash's instantsend for speedy transactions.
MasterNodes (called Sanctuaries) will come online after Christmas, allowing all expenses to be voted on and approved.

Expense receipts, to prove the sponshorship of new orphans, will be accessible from inside the wallet and we will even provide phone numbers for auditors to prove
 100% charity expenditures.  (From the rpc, type 'run contribution' to see the tithes into the foundation for a time period, and to see the outgoing sponsorship click the wallets 'Accountability' button to see
 a list of orphans, expenses, sponsorship dates, amounts, and the charity phone number, and txid).
For the first 6 months, 10% of each block will be allocated to the foundation, for sponsoring orphans at 100%.  Once per month, we will cash in anything over $40 available on an exchange, and sponsor orphans on our
volunteer time.

   After the sanctuaries go live, the 10% tithe will be diverted to an ongoing budget with DAO governance, voting, allowing the coin to function
as a dectralized autonomous charity; at that point the lead dev and volunteers will become a normal part of the community allowing the coin to run by itself.

To avoid wasting energy on meaningless SHA hashing, (or mining), biblepay introduces the BibleHash algorithm, that allows biblepay to
run on common commodity PCs, since the algorithm is resistant to porting to video cards and ASICs and is resistant to running in non-full node environments.

In addition to the low energy requirements and high efficiency of POB, the reward per block is set to be relative to the length of time the block took to solve,
(meaning that abusive hash attacks result in subsidy decreases).

The network will be high efficiency with low total energy consumption, and the charities sponsored must also be high efficiency (over 75%).
Next, we are deflationary, meaning that we start by issuing a larger amount of coins per block, and each year we tighten the supply by 10%.

The schedule is here: (205 blocks per day, 7 minute block targets):


The block reward breakdown is as follows:

After our sanctuaries go live, we allocate 10% of each block subsidy to our governance committe (a DAO), automatically, with 100% of that being
spent on charity. 
Over time, our sanctuaries will become a charity governance committee, to allow our community to take over the day to day operations of the charity: voting on where the money is spent, how much is spent.
This way, we will not be centralized.

We only partner with charities over 75% efficient, meaning over 75% reach the end-user.

NO PREMINE - the lead dev starts with zero, the orphan foundation fund starts with zero, the distribution is entirely fair.  NO ICO.  The distribution curve is evenly declining with no hidden bumps early.
The self-governance committee and masternode payments are deliberately delayed until Christmas, to allow people to prepare and save up the initial requirement.  Running a sanctuary is open to anyone.
The lead dev will sponsor the first 10 orphans out of his own pocket.


The wallet will have a reconciliation page built in at go live, to show all charitable income and expenses.

The expenses will be auditable - to prove the money actually was spent on orphans.

This will be accomplished through the use of : an RPC audit command that tallies the orphan income from the blockchain,
and secondly, an API connection to a database that stores the Compassion expenses (until sanctuaries go live), with auditable backing contact info for each expense.
We will also provide a web page with pictures of the sponsored orphans clicable from the wallet to show our investors what good we are doing.
And finally- we will maintain a copy of receipts in order to maintain 100% accountability.

Future Feature:
Pay to Preach, in wallet ineractive prayer rooms.



Novel distinct features of BiblePay:

Proof of Bible Hash algorithm (POBh), getblockinfo shows the chained bible verses required to solve the block,
sending money exposes a Tithe checkbox - allowing 10% to be gifted to the orphan foundation,
wallet has an in-wallet prayer system, allowing a user to send out a prayer request to the network or store prayers in the chain for the community to pray for from the overview page,
Transactions support in-chain messages, Instant Send, Voting, Decentralized Automated Charity Governance Committee, Repentance of Sins, Contributing to the orphan foundation checkbox, and reading the sin list and various staple prayers in wallet.

Pages: 1 2 3 4 5 6 [7]