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
61
Archived Proposals / BiblePay Proposal to be listed on CoinExchange.IO
« on: August 07, 2018, 09:45:08 pm »
CoinExchange.IO has given BiblePay a hard offer to list us on their exchange for 2 BTC!


This price is a 50% discount below the regular rate.

CoinExchange is ranked #130 on coinmarketcap with $730,000 volume per day:
https://coinmarketcap.com/exchanges/coinexchange/

We have filled out their listing form successfully:
https://wiki.biblepay.org/CoinExchange_Requirements

And it was approved by coinexchange.

However, the 'catch' is we applied for this listing last Christmas (of 2017), and it was approved in January, and now that 7 months have gone by, they would like to close the deal within 7 days, otherwise they will rescind the offer.  Unfortunately, the next offer will be 3 BTC if we delay.

Rob, Togo, Luke, Jaap and Chad have investigated the offers authenticity (Rob created a freshdesk ticket from inside coinexchange) and we have been e-mailing back and forth, so we have verified this offer is legitimate and not a scam.

Please vote for this proposal if you think this is a good move for Biblepay.

Time is of the essence, as we must reply to coinexchange within 6 days in order to close the deal.

We currently have 1.33 btc in the exchange fund (Jaap, our treasurer is holding this amount), and he believes we actually have 1.75 btc availalbe in total (since he has approx 1.5MM unsold biblepay coins this month that still need liquidated).

To finance the deal, Rob will loan the remaining .25 BTC temporarily for the integration to be started on time.  This proposal seeks 1 million BBP to close the gap between Jaaps current balance (1.75 BTC and the 2.00 BTC required), and another smaller proposal will be entered if we are short.

If we are over, Jaap will hold the remaining coins in the treasury for our next exchange project.


62
Each month we sponsor approximately 309 children at compassion.com.

Rob, the lead dev pays the expense and keeps a copy of the receipt. 

The expenses can be viewed by navigating to Accountability.biblepay.org | Expenses and viewing the PDF.

We have prepaid 1052 childrens premiums so far (starting Feb 2018)  into the future (out of a target of 1854 prepaid premiums),
  meaning we are prepaid with compassion at a level of over 56% - reducing the danger level for these kids.

All funds raised by this endeavor are spent at compassion.com, with any excess going to prepayments for the future (the prepaid amount is stored at compassion in the biblepay.org account).

To see the amounts we raised in the past by selling BBP for bitcoin see this page:
 See accountability.biblepay.org | Orphans | Orphan Fundraisers.  You can audit the total by finding the sum of all fundraisers.

I am committed to using 100% of the funds received in this months proposal entirely for our orphan premiums for compassion, and anything left over 100% to the future in the form of prepayments.

For this month, we are seeking $12,329, this covers the base compassion bill for 309 children for ONE MONTH plus approx 5% in prepayments.

I am requesting 9,000,000 BBP this month for Compassion (12329/.001428 = 8,633,753)  + rounding up for conservative exchange liquidity price slippage.

All orphanage coins are spent on orphan expenses at compassion.com.


63
Archived Proposals / Legal Formation of The BiblePay Foundation
« on: July 22, 2018, 04:04:43 pm »
So that BiblePay can fulfill its mission it is proposed that we enact The BiblePay Foundation.

The Foundation consists of boardmembers who represent BiblePay for functions requiring a TaxID number, including but not limited to:
Legal Decisions, Liquidating Crypto To Fiat, Vendor Relationships, Vendor Payments, Taxes, Professional Services, and more.

The plan for the proposal is here:
https://wiki.biblepay.org/BiblePay_DAO

When voting to enact this proposal please consider using the following format:

YES - I like the design of the DAO as is, or for the most part, I can live with its minor flaws (such as a boardmember you dont like etc).

NO - I either do not like the design (and feel it is not right for biblepay), or I do not like it in its current form and feel it contains a serious enough flaw to redesign this idea before proceeding.

ABSTAIN - I have no opinion on the matter but I have read the design.



64
Each month we sponsor approximately 339 orphans currently (309 from Compassion, (20 from Cameroon One and BLOOM) and 10 from Kairos Childrens Fund).

Rob, the lead dev pays the expense and keeps a copy of the receipt. 

The expenses can be viewed by navigating to Accountability.biblepay.org | Expenses and viewing the PDF.

We have prepaid 1019 childrens premiums so far (between Feb - July 2018) (out of a target of 1854 prepaid premiums),
  meaning we are preapid with compassion at a level of over 50% - which is well along the way in
 removing the danger level in the future for these kids.

All funds raised by this endeavor are spent at compassion.com, with any excess going to prepayments for the future (the prepaid amount is stored at compassion in the biblepay.org account).

To see the amounts we raised in the past by selling BBP for bitcoin see this page:
 See accountability.biblepay.org | Orphans | Orphan Fundraisers.  You can audit the total by finding the sum of all fundraisers.

I am committed to using 100% of the funds received in this months proposal entirely for our orphan premiums for compassion, and anything left over 100% to the future in the form of prepayments.

I am requesting 6,000,000 BBP this month for Compassion.

All orphanage coins are spent on orphan expenses at compassion.com and Rob will 'tip' in a little extra to ensure Gods money is put to use for Gods children.

65
Archived Proposals / June 2018 Payroll and IT Expenses
« on: July 21, 2018, 03:10:17 pm »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from March 1 2018 through March 31 2018:

Commits on Mar 31, 2018
1.1.1.6-Leisure 

@biblepay
biblepay committed on Mar 31
 
1.1.1.5b-Leisure 

@biblepay
biblepay committed on Mar 31
 
Commits on Mar 30, 2018
1.1.1.5-Leisure 

@biblepay
biblepay committed on Mar 30
 
Commits on Mar 29, 2018
1.1.1.4-Leisure 

@biblepay
biblepay committed on Mar 29
 
Commits on Mar 24, 2018
1.1.1.3-Leisure 

@biblepay
biblepay committed on Mar 24
 
Commits on Mar 20, 2018
1.1.1.2-Leisure 

@biblepay
biblepay committed on Mar 20
 
Commits on Mar 18, 2018
1.1.1.1f-Leisure 

@biblepay
biblepay committed on Mar 18
 
1.1.1.1e-Leisure 

@biblepay
biblepay committed on Mar 18
 
1.1.1.1d-Leisure 

@biblepay
biblepay committed on Mar 18
 
Commits on Mar 15, 2018
1.1.1.1c-Leisure Upgrade 

@biblepay
biblepay committed on Mar 15
 
Commits on Mar 12, 2018
1.1.1.1b-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 12


Commits on Mar 12, 2018
1.1.1.1-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 12
 
Commits on Mar 10, 2018
1.1.1.0-Leisure Upgrade 

@biblepay
biblepay committed on Mar 10
 
1.1.0.9b-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 10
 
1.0.9.9-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 10
 
Commits on Mar 9, 2018
1.1.0.8-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 9
 
Commits on Mar 8, 2018
1.1.0.7-Leisure Upgrade 

@biblepay
biblepay committed on Mar 8
 
1.1.0.6-Leisure Upgrade 

@biblepay
biblepay committed on Mar 8
 
Commits on Mar 7, 2018
1.1.0.5b-Leisure 

@biblepay
biblepay committed on Mar 7
 
1.1.0.5-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 7
 
1.1.0.4-Leisure Upgrade 

@biblepay
biblepay committed on Mar 7
 
1.1.0.3b-Leisure 

@biblepay
biblepay committed on Mar 7
 
1.1.0.3-Leisure Upgrade 

@biblepay
biblepay committed on Mar 7
 
1.0.2.3-Leisure Upgrade 

@biblepay
biblepay committed on Mar 7
 
Commits on Mar 6, 2018
1.1.0.2c-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 6
 
1.1.0.2b-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 6
 
Commits on Mar 5, 2018
1.1.0.2-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 5
 
1.1.0.1-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 5
 
1.0.9.9-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 5
 
Commits on Mar 4, 2018
1.0.9.8-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 4
 
1.0.9.7-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 4
 
Commits on Mar 3, 2018
1.0.9.6b-Leisure 

@biblepay
biblepay committed on Mar 3
 
1.0.9.6-Leisure 

@biblepay
biblepay committed on Mar 3
 
1.0.9.5f-Leisure 

@biblepay
biblepay committed on Mar 3
 
Commits on Mar 2, 2018
1.0.9.5e-Leisure Upgrade 

@biblepay
biblepay committed on Mar 2
 
Commits on Mar 1, 2018
1.0.9.5d-Leisure 

@biblepay
biblepay committed on Mar 1
 
1.0.9.5c-Leisure 

@biblepay
biblepay committed on Mar 1



For a grand total programming time of
   (42.5 hrs per week * 4 weeks) = 170 hours @ 40.00 per hour = $6,800.00

Also, I would like to expense the following IT expenses for Biblepay:


For a Grand Total Proposal of :  $6,800.00
Equaling:

?6800.00/.002284 (CoinMarketCap 7-21-2018) = 2,977,232 BBP


Thank you for your consideration.

66
Archived Proposals / June 2018 IT Expense
« on: June 23, 2018, 04:20:09 pm »
The 1 year web hosting for www.biblepay.org + Togos exchange e-mail for 1 year just renewed, therefore I am requesting $263.76 for this expense:

http://pool.biblepay.org/SAN/expenses/June2018IT.pdf

?263.76/.002045=128977 bbp



67
Archived Proposals / Outbound Letter Writing Reward Refill
« on: June 20, 2018, 04:42:23 pm »
All,

We had pretty good success using the last 500K letter writing reward bounties, we wrote 107 outbound letters and paid a reward between 3400 bbp and 1350 bbp, but the money is being eaten up quickly (we spent 450K out of 500,000) so we have about 50K left.


Yes, we still need to implement the orphan adoption system, where a miner can adopt an orphan and have a closer relationship.  That is still coming, this is a stopgap in between.   The technical reason that has not been programmed yet is we have been hit with two high priority feature requests (Monthly expense totals for charities in the pool, and the ability to store tax records for bloom, compassion and cameroon one in the pool).  Once these are out of the way we will jump back to orphan adoption.


In the mean time lets vote for a refill so we can keep the writing going the old fashioned way  ;D.


68
Archived Proposals / May 2018 IT Expenses (Payroll)
« on: June 20, 2018, 01:22:06 pm »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from Feb 1 2018 through Feb 28 2018:



Commits on Feb 26, 2018
1.0.9.5b-Leisure Upgrade 

@biblepay
biblepay committed on Feb 26
 
1.0.9.5-Leisure 

@biblepay
biblepay committed on Feb 26
 
Commits on Feb 23, 2018
1.0.9.4d-Leisure Upgrade 

@biblepay
biblepay committed on Feb 23
 
1.0.9.4c-Leisure 

@biblepay
biblepay committed on Feb 23
 
Commits on Feb 22, 2018
1.0.9.4b-Leisure Upgrade 

@biblepay
biblepay committed on Feb 22
 
1.0.9.4-Leisure Upgrade 

@biblepay
biblepay committed on Feb 22
 
Commits on Feb 20, 2018
1.0.9.3d-Leisure Upgrade 

@biblepay
biblepay committed on Feb 20
 
1.0.9.3c-Leisure Upgrade 

@biblepay
biblepay committed on Feb 20
 
1.0.9.3c-Leisure 

@biblepay
biblepay committed on Feb 20
 
1.0.9.3b-Leisure 

@biblepay
biblepay committed on Feb 20
 
Commits on Feb 19, 2018
1.0.9.3-Leisure 

@biblepay
biblepay committed on Feb 19
 
Commits on Feb 17, 2018
Update biblepay_zh_CN.ts and biblepay_zh_TW.ts 

@jguan
jguan committed on Feb 17
 
1.0.9.2c-Leisure 

@biblepay
biblepay committed on Feb 17
 
1.0.9.2b-Leisure Upgrade 

@biblepay
biblepay committed on Feb 17
 
1.0.9.2-Leisure Upgrade 

@biblepay
biblepay committed on Feb 17
 
Commits on Feb 14, 2018
1.0.9.1b-Leisure 

@biblepay
biblepay committed on Feb 14
 
1.0.9.1-Leisure 

@biblepay
biblepay committed on Feb 14
 
Commits on Feb 13, 2018
1.0.9.0f-Leisure 

@biblepay
biblepay committed on Feb 13
 
1.0.9.0e-Leisure 

@biblepay
biblepay committed on Feb 13
 
1.0.9.0d-Leisure 

@biblepay
biblepay committed on Feb 13
 
1.0.9.0c-Leisure 

@biblepay
biblepay committed on Feb 13
 
1.0.9.0b-Leisure Upgrade 

@biblepay
biblepay committed on Feb 13
 
1.0.9.0-Leisure for Prod 

@biblepay
biblepay committed on Feb 13
 
Commits on Feb 12, 2018
1.0.8.9d-Leisure 

@biblepay
biblepay committed on Feb 12
 
Commits on Feb 10, 2018
1.0.8.9c-Leisure Upgrade 

@biblepay
biblepay committed on Feb 10
 
Commits on Feb 9, 2018
1.0.8.9b-Leisure 

@biblepay
biblepay committed on Feb 9
 
1.0.8.9-Leisure 

@biblepay
biblepay committed on Feb 9

Commits on Feb 8, 2018
1.0.8.8q-Leisure 

@biblepay
biblepay committed on Feb 8
 
Commits on Feb 7, 2018
1.0.8.8p-Leisure 

@biblepay
biblepay committed on Feb 7
 
1.0.8.8o-Leisure 

@biblepay
biblepay committed on Feb 7
 
1.0.8.8n-Leisure 

@biblepay
biblepay committed on Feb 7
 
1.0.8.8m-Leisure 

@biblepay
biblepay committed on Feb 7
 
Commits on Feb 6, 2018
1.0.8.8l-Leisure 

@biblepay
biblepay committed on Feb 6
 
1.0.8.8k-Leisure 

@biblepay
biblepay committed on Feb 6
 
1.0.8.8j-Leisure 

@biblepay
biblepay committed on Feb 6
 
1.0.8.8i-Leisure 

@biblepay
biblepay committed on Feb 6
 
1.0.8.8h-Leisure 

@biblepay
biblepay committed on Feb 6
 
Commits on Feb 5, 2018
1.0.8.8g-Leisure 

@biblepay
biblepay committed on Feb 5
 
1.0.8.8f-Leisure 

@biblepay
biblepay committed on Feb 5
 
1.0.8.8e-Leisure 

@biblepay
biblepay committed on Feb 5
 
1.0.8.8d-Leisure 

@biblepay
biblepay committed on Feb 5
 
1.0.8.8c-Leisure 

@biblepay
biblepay committed on Feb 5
 
1.0.8.8b-Leisure 

@biblepay
biblepay committed on Feb 5
 
1.0.8.8-Leisure Upgrade 

@biblepay
biblepay committed on Feb 5




For a grand total programming time of
   (42.5 hrs per week * 4 weeks) = 170 hours @ 40.00 per hour = $6,800.00

Also, I would like to expense the following IT expenses for Biblepay:


For a Grand Total Proposal of :  $6,800.00
Equaling:

?6800.00/.002371 (CoinMarketCap 6-20-2018) = 2,867,988 BBP


Thank you for your consideration.

69
Each month we sponsor approximately 329 orphans currently (309 from Compassion, (20 from Cameroon One and BLOOM)).

Rob, the lead dev charges the expense on his credit card, and keeps a copy of the receipt. 

The expenses can be viewed by navigating to Accountability.biblepay.org | Expenses and viewing the PDF.

We have prepaid 879 childrens premiums so far (between Feb - May 2018) (out of a target of 1854 prepaid premiums),
  meaning we are preapid with compassion at a level of 47% - which is well along the way in
 removing the danger level in the future for these kids (IE we are now 3 months completely prepaid for all children). 
NOTE: This stat is as of June 19th, 2018 - while June has not been paid yet, so the prepaid % will rise within 10 days (after Rob pays the June invoice).


(We have a target of being prepaid 6 months in advance before we continue sponsoring new Compassion children).

All funds raised by this endeavor are spent at compassion.com, with any excess going to prepayments for the future (the prepaid amount is stored at compassion in the biblepay.org account).

To see the amounts we raised in the past by selling BBP for bitcoin see this page:
 See accountability.biblepay.org | Orphans | Orphan Fundraisers.  You can audit the total by finding the sum of all fundraisers.

I am committed to using 100% of the funds received in this months proposal entirely for our orphan premiums for compassion, and anything left over 100% to the future in the form of prepayments.

I am requesting 8,000,000 BBP this month for Compassion.

All orphanage coins are spent on orphan expenses at compassion.com and Rob will 'tip' in a little extra to ensure Gods money is put to use for Gods children.

70
TestNet Discussion Archive / Very Good Test Proposal
« on: June 15, 2018, 09:59:51 am »
This proposal is groundbreaking.


71
Archived Proposals / Add Proposals UI to Biblepay
« on: June 14, 2018, 04:53:20 pm »
Add the ability to View a list of active proposals in a grid view from QT.
Add ability to right click a context sensitive menu and Vote on a proposal, chart a proposal, or view a proposal.
The Chart Proposal should show a pie chart with voting metrics.

This was programmed by Bhavani.

This commit took 65 hours @ $35.00 an hour = $2275 = 2275/.002472 =  920307.47 bbp



72
TestNet Discussion Archive / Very boring proposal
« on: June 10, 2018, 02:26:12 pm »
This proposal is quite boring to read.

The purpose of this proposal is to ensure pool.biblepay.org can interact with the test network.

We will need to verify that we can vote on this proposal in test, and this will also allow us to test Bhavani's changes.

IE:  Listing proposals, charting proposals and voting on proposals.


73
The goal is to test our next mandatory release for quality and stability.

Testnet Instructions:

Git pull origin master to the latest version (1.1.2.6+).
From ~/.biblepaycore
Create a file called biblepaytest.conf
Add the following lines:
testnet=1
server=1
masternodeprivkey=xxx
masternode=0

Launch testnet like this:
cd ~/biblepay/src/qt
./biblepay-qt -conf=biblepaytest.conf

This setup lets you run testnet side by side your prod node or masternode, and allows you to avoid problems finding a separate testnet configuration file.

To set up a hot testnet sanctuary:

Ask a forum member for 500,000 bbp.
Launch the wallet.
Type:  masternode genkey
Copy the key to the 'masternodeprivkey=xxxx' in the biblepaytest.conf file.
Send 500,000 bbp to one of your own receiving addresses.

Restart the wallet.


Testing objectives:

- Ensure monthly (weekly in testnet) superblock is capable of paying a dispursement, ensure getgovernanceinfo is correct
- Ensure daily PODC superblock is also capable of dispursing, ensure exec getboincinfo podc budget is correct
 (The above two tests verify the cascading superblock bug will be mitigated)
- Ensure wallet boots without memorizing prayers on the primary thread, but yet in the background thread (this is the speedy bootup feature)
- Ensure active proposal list view is available (Bhavani)
- Ensure active proposal list vote works (Bhavani)
- Ensure active proposal list pie chart works (Bhavani)
- Test new PODC mature consensus feature (Rob will explain)
   (  // Mature means we stake a point in history (one timestamp per day) as Yesterdays point, and mature means it is older than that historical point.
      // This should theoretically allow the sancs to come to a more perfect consensus each day for PODC elements: DCCs (Distinct CPIDs), UTXOWeights (UTXO Stake Amounts), TaskWeights (Task confirmations), and Unbanked Indicators.)

      

- Test exec podcvotingreport (Rob)
- Check Slovakian User Interface Language (Orbis) to ensure the ?'s have dissapeared
- After F13000 Cutover Height, Block speed has been increased by 4.5% (aiming for 205 blocks per day)

Thank you for your continued support that ultimately helps orphans globally.




74
Archived Proposals / April 2018 IT Expenses (Payroll)
« on: May 20, 2018, 12:39:13 pm »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from Jan 1 2018 through Jan 31 2018:

Commits on Jan 24, 2018
1.0.8.7-Leisure 

@biblepay
biblepay committed on Jan 24
 
1.0.8.6-No Upgrade Required 

@biblepay
biblepay committed on Jan 24
 
Commits on Jan 23, 2018
1.0.8.5b-Leisure for Mainnet, Mandatory for Sanctuaries 

@biblepay
biblepay committed on Jan 23
 
1.0.8.5-Leisure 

@biblepay
biblepay committed on Jan 23
 
1.0.8.4c-Leisure Testnet Only 

@biblepay
biblepay committed on Jan 23
 
1.0.8.4-Leisure 

@biblepay
biblepay committed on Jan 23
 
Commits on Jan 22, 2018
1.0.8.4-Leisure 

@biblepay
biblepay committed on Jan 22
 
Commits on Jan 19, 2018
1.0.8.3c-Leisure Upgrade 

@biblepay
biblepay committed on Jan 19
 
1.0.8.3b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 19
 
1.0.8.3-Leisure Upgrade 

@biblepay
biblepay committed on Jan 19
 
Commits on Jan 17, 2018
1.0.8.2-Leisure Upgrade 

@biblepay
biblepay committed on Jan 17
 
Commits on Jan 15, 2018
1.0.8.1b-Mandatory Upgrade 

@biblepay
biblepay committed on Jan 15
 
1.0.8.1-Mandatory Upgrade 

@biblepay
biblepay committed on Jan 15
 
Commits on Jan 14, 2018
1.0.8.0b-Leisure 

@biblepay
biblepay committed on Jan 14
 
1.0.8.0-Mandatory 

@biblepay
biblepay committed on Jan 14
 
Commits on Jan 13, 2018
1.0.7.9-Mandatory 

@biblepay
biblepay committed on Jan 13
 
1.0.7.8-Mandatory 

@biblepay
biblepay committed on Jan 13
 
Commits on Jan 12, 2018
1.0.7.7.c-Mandatory Upgrade 

@biblepay
biblepay committed on Jan 12
 
1.0.7.7b-Mandatory Upgrade 

@biblepay
biblepay committed on Jan 12
 
1.0.7.7-Mandatory Upgrade 

@biblepay
biblepay committed on Jan 12
 
Commits on Jan 4, 2018
1.0.7.6-Leisure 

@biblepay
biblepay committed on Jan 4
 
Commits on Jan 1, 2018
1.0.7.5-Leisure 

@biblepay
biblepay committed on Jan 1
 
1.0.7.4-Leisure 

@biblepay
biblepay committed on Jan 1
 
1.0.7.4-Leisure 

@biblepay
biblepay committed on Jan 1
 
1.0.7.3-Leisure 

@biblepay
biblepay committed on Jan 1




For a grand total programming time of
   (42.5 hrs per week * 4 weeks) = 170 hours @ 40.00 per hour = $6,800.00

Also, I would like to expense the following IT expenses for Biblepay:

Zinc, SSL certificates ($269.99)  - Note that the SSL charge is a little high because I was coerced into buying the $169.99 SSL (for one year) - certificate
 - primarily because the host for forum.biblepay.org would not support any other 3rd party SSL certs, and that particular day all the users were receiving a strange HTTPS error so being under pressure I renewed the SSL-5.  Next year before the hosting plan expires I will investigate potentially migrating the forum database to a new linux plan where we can buy our own SSL certs.

Receipts:
http://pool.biblepay.org/SAN/expenses/ITApr2018.pdf


For a Grand Total Proposal of :  $7,069.99
Equaling:

?7069.99/.0039 (CoinMarketCap 5-20-2018) = 1,812,817 BBP


Thank you for your consideration.

75
Each month we sponsor approximately 329 orphans currently (309 from Compassion, (20 from Cameroon One and BLOOM)).

Rob, the lead dev charges the expense on his credit card, and keeps a copy of the receipt. 

The expenses can be viewed by navigating to Accountability.biblepay.org | Expenses and viewing the PDF.

We have prepaid 879 childrens premiums so far (between Feb - May 2018) (out of a target of 1854 prepaid premiums),
  meaning we are preapid with compassion at a level of 47% - which is well along the way in
 removing the danger level in the future for these kids (IE we are now 3 months completely prepaid for all children). 

(We have a target of being prepaid 6 months in advance before we continue sponsoring new Compassion children).

All funds raised by this endeavor are spent at compassion.com, with any excess going to prepayments for the future (the prepaid amount is stored at compassion in the biblepay.org account).

To see the amounts we raised in the past by selling BBP for bitcoin see this page:
 See accountability.biblepay.org | Orphans | Orphan Fundraisers.  You can audit the total by finding the sum of all fundraisers.

I am committed to using 100% of the funds received in this months proposal entirely for our orphan premiums for compassion, and anything left over 100% to the future in the form of prepayments.

I am requesting 7,000,000 BBP this month for Compassion.

All orphanage coins are spent on orphan expenses at compassion.com and Rob will 'tip' in a little extra to ensure Gods money is put to use for Gods children.


Pages: 1 2 3 4 [5] 6 7