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
1
Production Proposals / August payroll (Apr) 2019
« on: August 17, 2019, 10:23:39 am »
ommits on Apr 29, 2019
1.4.2.3-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 29
 
Commits on Apr 28, 2019
1.4.2.2b-Leisure Upgrade for TestNet 

@biblepay
biblepay committed on Apr 28
 
1.4.2.2-Mandatory upgrade for TestNet 

@biblepay
biblepay committed on Apr 28
 
Commits on Apr 26, 2019
1.4.2.1b-Mandatory upgrade for TestNet 

@biblepay
biblepay committed on Apr 26
 
1.4.2.1-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 26
 
Commits on Apr 25, 2019
Merge branch 'master' into develop 

MIP
MIP committed on Apr 25
 
Commits on Apr 23, 2019
1.4.2.0-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 23
 
Merge branch 'master' into develop 

MIP
MIP committed on Apr 23


Commits on Apr 22, 2019
1.4.1.9-Leisure upgrade for TestNet 

@biblepay
biblepay committed on Apr 22
 
Commits on Apr 21, 2019
Merge branch 'master' into develop 

MIP
MIP committed on Apr 21
 
Commits on Apr 20, 2019
1.4.1.8-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 20
 
Commits on Apr 18, 2019
Merge branch 'master' into develop 

MIP
MIP committed on Apr 18
 
Commits on Apr 17, 2019
1.4.1.7 - Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 17
 
Commits on Apr 12, 2019
1.4.1.6-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 12
 
Commits on Apr 10, 2019
1.4.1.5b-Leisure Upgrade 

@biblepay
biblepay committed on Apr 10
 
1.4.1.5-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 10
 
Commits on Apr 9, 2019
1.4.1.4-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 9
 
Commits on Apr 5, 2019
1.4.1.3-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 5
 
Merge branch 'master' into develop 

MIP
MIP committed on Apr 5
 
Commits on Apr 4, 2019
1.4.1.2b-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Apr 4
 
1.4.1.2-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 4
 
1.4.1.1-Mandatory Upgrade for TestNet 

@biblepay
biblepay committed on Apr 4
 
Commits on Apr 3, 2019
1.4.1.0-Leisure Upgrade for TestNet 

@biblepay
biblepay committed on Apr 3
 
1.4.0.9d-TestNet Leisure Upgrade 

@biblepay
biblepay committed on Apr 3
 
Commits on Apr 2, 2019
1.4.0.9c-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Apr 2
 
1.4.0.9b-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Apr 2
 
1.4.0.9-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Apr 2
 
Merge branch 'master' into develop 

MIP
MIP committed on Apr 2
 
Commits on Apr 1, 2019
1.4.0.8-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Apr 1


This was approx 120 hours - capping @ 1.5 MM this month due to budget constraints.


2
Production Proposals / Exchange Listing on Tokok.com
« on: August 17, 2019, 10:08:04 am »
We have an offer to be listed from Paul at Tokok.com for 2btc.

Tokok does 442 MM per day - see CoinGecko:
https://www.coingecko.com/en/exchanges/tokok
CMC:
https://coinmarketcap.com/exchanges/tokok/

If listed, Rob would provide the initial funding by loaning BBP the 2btc.
BBP would remunerate Rob in 12 payments of .16 btc each.

This is a competing proposal to provide entrance into the Asian market.
Impho, I recommend the sancs to vote on either one or the other (but not both) as I don't think we can afford both proposals.

Please evaluate Tokok, as we want the most honest and liquid exchange in Asia for BBP.


Payments:

Payment 1 - .16 btc - 2,430,939


** Help:  If anyone has anything negative to report about TOKOK, please report it now **

3
Production Proposals / FUBT Exchange
« on: August 15, 2019, 06:15:22 pm »
** Deal to List BiblePay with FUBT Exchange - Hong Kong **



I've been in contact with Mr. Yue and Nick Lee from FUBT for one year about potentially listing BiblePay.

A year ago the price quote was too high (IE over 5 bitcoins).

Over the last few months, Mr. Yue had quoted me 3 BTC to list, and I told him we would continue to evaluate their platform as our next exchange and continue to save up funds for our next exchange.

Over the last week, I started talking to Nick.  Nick explained that out of the 3 BTC fee, FUBT will spend a certain amount of money on promoting a new coin (IE they reach out to 50 media companies, and blast a summary of the coin, and promote it for a certain number of days in Asia).  Nick estimates the PR to be worth around $5000~ (or up to 1btc depending on its reception level).

Recently, our coin has been reviewed by FUBT's coin quality assessment group and they consider us to be an "A" grade coin (similar to SouthXChanges ranking system).  They again approached us and re-quoted us a listing for 6btc.  I explained it is out of the ballpark.

Recently, Nick explained to me he can only guarantee the 3 btc fee for a short period of time and we may lose our discount status if we don't try to make an offer soon.

I agreed to take a look at FUBT this month and attempt to create a deal that may possibly work with BiblePay.

FUBT does approx $500 mil per day total volume according to coinmarketcap and coingecko, (not the gecko normalized volume).  From looking at a comparison between Tokok, FUBT, Bittrex and SouthXChange, FUBT appears to be about 50* bigger than southxchange.  Nick explained to me they have 2 million registered traders at FUBT. 

https://www.coingecko.com/en/exchanges/fubt
https://coinmarketcap.com/exchanges/fubt/

Estimating the size of this investment, 3btc ($35,000), I estimate that we would see a potential increase of $5 - $10,000 per day in trading volume (based on similar coins to BiblePay) and this would potentially lead to a market cap increase in BiblePay, *potentially* paying off the investment within a short duration.  (Nick tends to think we would be received well in Asia and coins like us trade more than $20K per day, but this is speculative.)

I feel this move into Asia is something BiblePay currently needs, as we trade almost exclusively in the US.  I think the 2 mil additional accounts complement our needs to a high degree.

In light of this, if the sanctuaries agree, I am offering to help this listing along with the following offer:

If this proposal is voted in and the Security Check passes (this is an internal freshdesk ticket with FUBT senior management to verify the exchange proposal is signed and agreed upon by BiblePay and FUBT):
Rob sends FUBT 3 btc from his personal account (lending BBP 3 btc)
Rob enters a 12 part proposal to recoup .25btc per month until the 3 btc is paid back

FUBT Provides:

- Listing BTC/BBP trading Pair
- 1BTC worth of promotion (Media blitz with 50 media outlets, 1-2* depending on market appreciation)
- At least 4 mandatory upgrades per year with no fees (I verified this with Nick)
- The go live would be towards the end of September 2019 and media blitz around mid September

** If anyone has anything negative to report about FUBT please report it now **



Proposal Payment dispursement breakdown:

Payment 1 of 12:
BTC @ 10567 : .25BTC * 10567 / .000724 = 3,647,790 BBP

(Note, as each month occurs I will update the remaining payments until we hit 3 btc)



4
Production Proposals / Compassion - July 2019
« on: July 26, 2019, 09:37:07 pm »
We sponsor 55 compassion children @$2090.00 per month.
Seeking 1 mil.


5
Production Proposals / Cameroon One Installment 4 2019
« on: July 26, 2019, 09:16:17 pm »
We have 11 children with cameroon one, we have donated approx $2393 in 2019, and our annual due is $4026.00.

Requesting 2 million.


6
Production Proposals / July payroll (March) 2019
« on: July 26, 2019, 09:05:51 pm »
Commits on Mar 31, 2019
1.4.0.7d-TestNet mandatory upgrade 

@biblepay
biblepay committed on Mar 31
 
1.4.0.7c-Testnet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 31
 
1.4.0.7b-Testnet mandatory upgrade 

@biblepay
biblepay committed on Mar 31
 
1.4.0.7-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 31
 
Commits on Mar 30, 2019
Merge branch 'master' into develop 
 
1.4.0.6b-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 30
 
1.4.0.6-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 30
 
Commits on Mar 29, 2019
1.4.0.5 - TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 29
 
Commits on Mar 28, 2019
1.4.0.4-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 28
 
Commits on Mar 27, 2019
1.4.0.3-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 27
 
Merge branch 'master' into develop 

Commits on Mar 26, 2019
1.4.0.2-TestNet Mandatory Upgrade 

@biblepay
biblepay committed on Mar 26
 
Commits on Mar 25, 2019
1.4.0.1d-Testnet RC 

@biblepay
biblepay committed on Mar 25


Commits on Mar 24, 2019
1.4.0.1c-TestNet RC 

@biblepay
biblepay committed on Mar 24
 
1.4.0.1b-Testnet RC 

@biblepay
biblepay committed on Mar 24
 
1.4.0.1-Testnet Release Candidate 

@biblepay
biblepay committed on Mar 24
 
Commits on Mar 22, 2019
1.2.0.1o-Genesis 

@biblepay
biblepay committed on Mar 22
 
Commits on Mar 20, 2019
1.2.0.1n-Genesis 

@biblepay
biblepay committed on Mar 20
 
1.2.0.1m-Genesis 

@biblepay
biblepay committed on Mar 20
 
Commits on Mar 18, 2019
1.2.0.1l-Genesis 

@biblepay
biblepay committed on Mar 18
 
Commits on Mar 16, 2019
1.2.0.1k - Genesis 

@biblepay
biblepay committed on Mar 16
 
Commits on Mar 12, 2019
1.2.0.1j-Genesis 

@biblepay
biblepay committed on Mar 12
 
Commits on Mar 10, 2019
1.2.0.1i-Genesis 

@biblepay
biblepay committed on Mar 10
 
Commits on Mar 6, 2019
1.2.0.1-Genesis 

@biblepay
biblepay committed on Mar 6
 
Commits on Mar 5, 2019
1.2.0.1g-Genesis 

@biblepay
biblepay committed on Mar 5
 
1.2.0.1f-Genesis 

@biblepay
biblepay committed on Mar 5
 
1.2.0.1e-Genesis 

@biblepay
biblepay committed on Mar 5
 
Commits on Mar 4, 2019
1.2.0.1d-Genesis 

@biblepay
biblepay committed on Mar 4
 
1.2.0.1c-Genesis 

@biblepay
biblepay committed on Mar 4
 1   
1.2.0.1b-Genesis 

@biblepay
biblepay committed on Mar 4
 
1.2.0.1-Genesis 

@biblepay
biblepay committed on Mar 4


120 hours = $4800 - capping at 3 mil.


7
Pre-Proposal Discussion / Foundation Donation Empowerment Feature
« on: June 30, 2019, 08:19:37 pm »
So that BiblePay can maximize the good that it does globally and help as many orphans as possible, I am proposing that we add a feature that will allow a foundation donor to designate which partner charity a foundation donation gets spent on, if they feel they want it spent on one of our partner charities other than Compassion.com.   (By default all foundation revenue gets liquidated and sent to compassion.com).

(One example of how we will sponsor more orphans than our monthly budget + monthly donations currently allows for, is we have a donor that is willing to pay for a certain number of Kenyan orphans at HFOC, but BiblePay currently has too small of a budget to handle the new Kenyan orphans.  So in this case, the donor will send a donation to the foundation once per month, and BiblePay will forward the BBP funds from the donation to HFOC, allowing the relationship to continue.  This will give BBP more of a global monthly sponsorship count also, helping us become more of a globally recognized charity - important when we make new partners and also for due diligence with integrations and exchanges).

This feature will work with both POG donations or standard donations.

Note that the donation amount must be greater than $100 USD (or approx 250,000 BBP) to use the feature (as clerical work is required to store the transaction and liquidate the transaction).

The user must direct the funds to go to a currently integrated Charity such as:  Compassion, Kairos Childrens Fund, Cameroon One, BLOOM, Side by Side Ugandan Women,  HFOC (as these charities accept BiblePay currently).

When the user designates a specific charity, BiblePay will store a record (for 10 years) of the revenue and expense.   This will allow us to produce accountability reports and also report a greater net giving total as a community.

To use the feature, first send a donation to the foundation using either our standard send money checkbox (or a POG donation) of > 250,000 BiblePay (or $100, whichever is less).  Copy the TXID to the clipboard.  From the Pool, navigate to Account | Donation Director.  From this page, paste the TXID of the transaction and select the designated Target charity from the dropdown list.  Click Submit.

Note: The donation director record must be received before 3 days before the current month superblock is paid, otherwise the record will be designated for the following month.

To see the donation director records, click : Reports | Donation Director Records.



 

8
The ABN feature reduces the liklihood of bot-net mining activity against BiblePay.

Rob wants to ensure Security is maintained and our difficulty level never falls below 5000.

Should we re-enable ABN in small steps, starting with a 1,000 BBP requirement?

Then, if difficulty remains > 5000, we can increase our ABN requirement in steps weekly maintaining diff around 10K or more.


9
Archived Proposals / Compassion June 2019 Recurring Sponsorships
« on: June 24, 2019, 09:13:39 pm »
We currently sponsor 55 children through compassion with a recurring fee of $2090.

Request 4.1MM for June.

10
Archived Proposals / June Payroll
« on: June 24, 2019, 06:47:28 pm »
 
@biblepay
Commits on Mar 26, 2019
1.2.0.1b-Leisure Upgrade 

@biblepay
biblepay committed on Mar 26
 
Commits on Mar 14, 2019
1.2.0.1-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 14
 
1.1.9.9g-Leisure Upgrade 

@biblepay
biblepay committed on Mar 14
 
1.1.9.9f-Leisure Upgrade 

@biblepay
biblepay committed on Mar 14
 
Commits on Mar 13, 2019
1.1.9.9e-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 13
 
1.1.9.9d-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 13
 
1.1.9.9c-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 13
 
1.1.9.9b-Mandatory Upgrade 

@biblepay
biblepay committed on Mar 13
 
1.1.9.9-TestNet Only RC 

@biblepay
biblepay committed on Mar 13
 
Commits on Mar 2, 2019
1.1.9.8-Leisure Upgrade 

@biblepay
biblepay committed on Mar 2
 3   
1.1.9.7 - Leisure Upgrade 

@biblepay
biblepay committed on Mar 2

Spent 20 hours researching the port to Dash-Evolution and discussing with MIP, and some additional time on conference calls.

Spent 160 hours working on biblepay.
160hrs * 40.00 = $6400 = 9.95M; capping @ 3.00 MM

IT Expenses:
Domain renewal for biblepay.org http://pool.biblepay.org/san/expenses/biblepayorg.png
$62 = 93,312bbp

Hosting for one year (biblepay.org):    http://pool.biblepay.org/san/expenses/hosting2019.png
$95 = 164,644 bbp

11
Archived Proposals / Kairos Childrens Fund PR Event
« on: June 13, 2019, 11:31:48 am »
Pastor Andrew from Kairos Childrens fund is asking if we would like to have a banner at his 3 day national conference in the Philipines:

These are the packages that we are offering. Check out our website at vismin.winnegor.org
$100 : We will have 2 banners outside the hotel during the 3 day event. One more banner inside.
          The logo and tagline will be at the bottom, small, but readable from the back of the room or across the road

$50 : We will distribute small brochure about your company or product along with the packet that we give them at the beginning of the event.

$50 : We will also post a logo under 'sponsored by' on the website, with a link to the Biblepay website.

$50 : We will have your company or product mentioned at the beginning of the 1st session every day. (as a great cryptocurrency for christians.)
         + $25 : Your business / product will be announced as a major sponsor of the event

* If time permits, I will discuss biblepay with interesting people and pastors.

* We are thinking of
 - http://www.facebook.com/wimdgte
 - http://www.winnegor.org


=-=-=-=-=-=-=-=-=-=-=-=-=-


The event is being held Oct 22 through Oct 25th.

Pastor Andrew will design the pamphlet and the banner for us.


Total charge $250.00 or 625,000 bbp.



12
Pre-Proposal Discussion / POOM Concept (Proof-of-Orphan-Mining)
« on: June 12, 2019, 04:57:48 pm »
June 12th, 2019

Concept:  Proof-of-Orphan-Mining (POOM)


 ** CLARIFICATION ON WHAT WE ARE VOTING ON, SANCTUARIES:
     The "Divert_50_percent_of_GSC_Budget_to_POOM" poll:

We are voting on creating an additional BiblePay GSC campaign called POOM.  This 50% poll means the budget would be capped at 450K per day.
(This would lower the POG/healing budget by 450k per day).

Each participant would receive rewards in POOM if:
- They have a credit balance with Cameroon for that Child Hex ID

Each daily reward would be capped at the exact amount of the expense.

The budget will not exceed the max 450K under any circumstances (rewards would be divided equally if we are overflowing with children).

(Please vote on the poll that you like the most - we have 3 sizes in ).


**

This concept has been discussed in various forms in the past, but I believe the reason we had no traction was the variants contained unreasonable expectations.  (Our first variation, [email protected] with orphanstats.com, required BiblePay to know personal information for each user (it required trust, contained collusion risk, and tracked personal info; and the poll indicated it was intrusive).    The second variation, asking compassion.com's IT department to create a custom API for decentralized queries, was proposed to Jimmy, CEO of Compassion - and to ciqueue - and all attempts were met with a very high resistance level ranging from not willing to hear the proposal nor have meetings nor nor creating a custom solution for us at this time).

So in light of this, this new concept places a different spin on the idea, and bends both parties a little more, revisiting the idea.  The base idea, imho, has such great potential, it would be a disgrace to ignore and drop the idea in its entirety rather than take another fresh look at re-engineering it to meet in the middle.

Some positive things have also changed in the interim; we now have GSC contracts, which facilitate a much more flexible server side environment for validating the orphan balance consensus in a decentralized way without forks.  This also provides a mechanism to reward home sponsors.

In this adjusted concept, we promote sponsorship of children at home (rather than through our governance superblock).  We do not eliminate our governance superblock; we offer POOM in addition to everything else we already have.  This has the added benefit of allowing the home miner to sponsor a home orphan and write directly to the orphan (1:1 relationship is fostered).  (Alternatively in the future, we may also allow the home user to Choose whether they want to write to the child or if they want our BiblePay-Web to write to the child- more info on this soon). 

Rob has contacted our second largest orphanage, Cameroon One, who is potentially interested in integrating with us.

In this new scenario, we simplify the API requirements, so that we integrate with a simple solution in baby step 1 (in contrast to birthing the complicated baby first, something our vendors do not want to do).  In this way we get a green light to became a partner with our valuable vendor, rather than shut down.

The first part of the concept is here:
http://wiki.biblepay.org/POOM

Part of the desire to create this pre-proposal discussion now is driven by our initial conference call.  I have a soft commitment from Todd, Director of Cameroon, and Shaun, Founder of Cameroon, and Raj (IT/Cameroon), that Cameroon will be on board with BiblePay to go forward with this design, proof of concept, testing and implementation.  (I also had a conference call discussing the IT solution, and we have a potential green light to do this).

Therefore, this proposal seeks to authorize BiblePay IT (devs) to work on this proof-of-concept, for three months, test it with Cameroon, and if it works, seeks to deploy this to production, and reward either 30%, 50%, or 70% (depending on specific sanctuary proposal entered this month) of our daily rewards out of the GSC budget, towards the sponsorship of Cameroon One children in lieu of POOM rewards, strictly for children who are sponsored through this program by miners who sponsor personal children at home through this system.  (The reason I am seeking approval of the entire program now, is it is a considerably large effort for both companies, and I want to see that we have pre-approval for this to move to production and pay production POOM rewards before we program the lions share of this).

Note, in the security section, we intend to create two rules that make this relationship much more than an oracle:

Rule 1:
When a miner wishes to sponsor a new child, they will enter a command in the wallet (IE 'sponsorchild').  When the sponsorchild command executes, they will receive a Child ID (a Cameroon One Child ID).  This will be a distinct global ID that will prevent Cameroon One from giving this child to any other donor!  Therefore, we will enforce a rule where an existing Cameroon One home donor cannot come to biblepay with an existing orphan, they must initiate the orphan through BiblePay.  During this step, Cameroon will create a childhood BIO URL for the miner, and, a tracking code in their accounting system (allowing BiblePay sanctuaries to track this childs balance as charges, and payments are made to this childs record).  We will have daily visibility of each childs balance per miner.

Rule 2:
A public method will be set-up to allow random checks for any orphan sponsored by a miner by a third party auditor (IE a normal end user can check the balance of a child and call Cameroon and check the integrity of the childs status, to ensure the child is with BiblePay).  (This is similar to what we have with Compassion), so that it will be 100% provable that sponsored children through POOM are really sponsored to BiblePay. 


Payment Mechanics:

So that we can scale to the maximum,  I propose that the payment owed to the miner is converted to a daily amount, and awarded as POG points to the miner and paid from the POG GSC budget.  This is primarily so this POOM budget is friendly to our existing POG budget (in that people sponsoring children do not abruptly take over their own program budget but instead part of the POG budget).

Example:

John Doe, Miner 001, CPK 001, Sponsors Abraham, Cameroon One Orphan #ABC, for $40.00 per month.
Since this costs John Doe $1.33 per day, (and our wallet knows the current BiblePay Price thanks to QT), this is auto-converted to 4430 bbp per day (via the GSC contract), and this BBP is diverted from the Total daily POG budget (by converting to points) and added to John Doe's GSC CPK for the day.  (This reduces the available reward for the rest of the GSC participants).
(We can discuss a separate project for POOM, which GSC certainly supports, but imho it would be better to divert POG -> POOM, more on this tomorrow).

If total orphan payments exceed GSC rewards, they then start to be split equally among all participants.

Electric:

As everyone can see, this concept has a huge potential, because it has the effect of diverting normal mining rewards over to orphan sponsorships.

Unlimited BBP Potential:

One other effect that is less obvious, and I intend to create a model for this and paste my hypothesis, is that I believe if we open up the potential sponsorship of outside orphans (as proposed here, through cameroon one) with home users (miners), via USD payment, with the tax deduction (this was confirmed with Cameroon, that the payment is tax deductible) - received by the end-user, as the BBP is remunerated back, this cycle should technically have a very positive impact on our market cap and price.  This is because our mining rewards would change into pass-through rewards (IE reimbursements) for a certain percent of our emissions.  Yes, some pass through reimbursements would be liquidated immediately to cover the costs of the orphan, but I believe a certain percent would be held by miners (IE in a sense a tax-deductible buy-and-hold of BBP).

What makes this POOM concept an attractive configuration?

Currently I view BiblePays emissions flow as:
POBH - Security - 25%
Sanc rewards - 25%
GSC (Primarily Staking/Giving) - 35%
Governance Budget - 15%

As you can see, this is a very good configuration already, but with POOM, we can potentially divert some of the Staking revenue over to fully productive orphan reward payments.  And, if the test pilot works, once we have chain locks in place, we could also potentially move some of our security budget into POOM (Optional, depending on various factors).


Decentralization:

And one of the very obvious advantages in this idea is it decentralizes biblepay, allowing us to scale (as each home miner sponsors their own personal orphan using their own funds).













13
Archived Proposals / May compassion recurring sponsorships 2019
« on: May 20, 2019, 01:06:40 pm »
We currently sponsor 55 @ $2090 per month.

Requesting 3.22MM.


14
Archived Proposals / May payroll (Jan)
« on: May 17, 2019, 01:38:14 pm »
1.1.8.5-Mandatory Upgrade 

@biblepay
biblepay committed on Jan 27
 5   
Commits on Jan 23, 2019
1.1.8.4b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 23
 
1.1.8.4-Leisure Upgrade 

@biblepay
biblepay committed on Jan 23
 
Commits on Jan 21, 2019
1.1.8.3b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 21
 
1.1.8.3-Leisure Upgrade 

@biblepay
biblepay committed on Jan 21
 
Commits on Jan 14, 2019
1.1.8.2-Leisure Upgrade 

@biblepay
biblepay committed on Jan 14
 
1.1.8.1c-Leisure Upgrade 

@biblepay
biblepay committed on Jan 14
 
Commits on Jan 13, 2019
1.1.8.1b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 13
 
1.1.8.1-Leisure Upgrade 

@biblepay
biblepay committed on Jan 13
 
Commits on Jan 12, 2019
1.1.8.0b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 12
 
1.1.8.0-Leisure Upgrade 

@biblepay
biblepay committed on Jan 12
 
Commits on Jan 7, 2019
1.1.7.9b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 7
 
Commits on Jan 6, 2019
1.1.7.9-Leisure Upgrade 

@biblepay
biblepay committed on Jan 6
 
Commits on Jan 4, 2019
1.1.7.8q-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8p-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8o-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8n-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4

1.1.7.8m-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8l-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8k-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8j-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
1.1.7.8i-Leisure Upgrade 

@biblepay
biblepay committed on Jan 4
 
Commits on Jan 3, 2019
1.1.7.8h-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8g-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8f-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8e-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8d-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8c-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8b - Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
1.1.7.8-Leisure Upgrade 

@biblepay
biblepay committed on Jan 3
 
Commits on Jan 2, 2019
1.1.7.7c-Leisure Upgrade 

@biblepay
biblepay committed on Jan 2
 
1.1.7.7b-Leisure Upgrade 

@biblepay
biblepay committed on Jan 2
 
Merge branch 'master' of https://github.com/biblepay/biblepay

@biblepay
biblepay committed on Jan 2
 
1.1.7.7 - Leisure Upgrade 

@biblepay
biblepay committed on Jan 2
 
Merge pull request #63 from biblepay/develop 

@biblepay
biblepay committed on Jan 2
 
Merge branch 'master' into develop

@biblepay
biblepay committed on Jan 2
 
Commits on Jan 1, 2019
Added further error handling to Win ShellCommand in case boinccmd fails




=-=-=-=-=-=-


140 hours
Capping at 3,000,000


15
Archived Proposals / CAMEROON ONE May 2019
« on: May 17, 2019, 01:31:25 pm »
We have 11 children with cameroon one, we have donated $893 in 2019, and our annual due is $4026.00.

Requesting 5 million to shore up the deficit.


Pages: [1] 2 3 4 5 6 7