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

Pages: [1] 2 3 4
1
BiblePay - New Coin Launch / Implementing ?
« on: September 14, 2018, 10:47:21 am »
 

.

2
Production Proposals / August 2018 IT and Payroll
« on: September 11, 2018, 11:17:40 am »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from
April 1 2018 through April 30th 2018:
(Note that in July I expensed March commits, and I didn't enter any payroll in August due to our low price).
Commits on Apr 24, 2018
1.1.2.4b-Leisure 

@biblepay
biblepay committed on Apr 24
 
1.1.2.4-Leisure 

@biblepay
biblepay committed on Apr 24
 
Commits on Apr 23, 2018
1.1.2.3-Leisure 

@biblepay
biblepay committed on Apr 23
 
Commits on Apr 20, 2018
1.1.2.3-Leisure 

@biblepay
biblepay committed on Apr 20
 
 
Commits on Apr 18, 2018
1.1.2.2 - Mandatory for Users, Leisure for Exchanges 

@biblepay
biblepay committed on Apr 18
 
Commits on Apr 16, 2018
Create CODE_OF_CONDUCT.md

@biblepay
biblepay committed on Apr 16
 
Commits on Apr 15, 2018
1.1.2.1-Leisure 

@biblepay
biblepay committed on Apr 15
 
Commits on Apr 14, 2018
1.1.2.0b-Leisure 

@biblepay
biblepay committed on Apr 14
 
1.1.2.0-Leisure 

@biblepay
biblepay committed on Apr 14
 
Commits on Apr 12, 2018
1.1.1.9l-Leisure 

@biblepay
biblepay committed on Apr 12
 
1.1.1.9k-Leisure 

@biblepay
biblepay committed on Apr 12
 
1.1.1.9j-Leisure 

@biblepay
biblepay committed on Apr 12
 
1.1.1.9i-Leisure 

@biblepay
biblepay committed on Apr 12
 
Commits on Apr 11, 2018
1.1.1.9h-Leisure 

@biblepay
biblepay committed on Apr 11
 
1.1.1.9g-Leisure 

@biblepay
biblepay committed on Apr 11
 
1.1.1.9f-Leisure 

@biblepay
biblepay committed on Apr 11

ommits on Apr 10, 2018
1.1.1.9e-Leisure 

@biblepay
biblepay committed on Apr 10
 
1.1.1.9d-Leisure 

@biblepay
biblepay committed on Apr 10
 
1.1.1.9c-Leisure 

@biblepay
biblepay committed on Apr 10
 
Revert "1.1.1.9b-Leisure" 

@biblepay
biblepay committed on Apr 10
 
1.1.1.9c-Leisure 

@biblepay
biblepay committed on Apr 10
 
Merge pull request #8 from svirusxxx/master 

@biblepay
biblepay committed on Apr 10
 
Merge pull request #6 from mymosh/gcc-7.2.0 

@biblepay
biblepay committed on Apr 10
 
Merge pull request #1 from nelfwarrior/patch-1 

@biblepay
biblepay committed on Apr 10
 
1.1.1.9b-Leisure 

@biblepay
biblepay committed on Apr 10
 
@biblepay
biblepay committed on Apr 10
 
Commits on Apr 5, 2018
1.1.1.9-Leisure 

@biblepay
biblepay committed on Apr 5
 
Commits on Apr 3, 2018
1.1.1.8c-Leisure 

@biblepay
biblepay committed on Apr 3
 
Commits on Apr 2, 2018
1.1.1.8b-Leisure Upgrade 

@biblepay
biblepay committed on Apr 2
 
Commits on Apr 1, 2018
1.1.1.8-Mandatory for Sancs, Leisure for Network 

@biblepay
biblepay committed on Apr 1
 
1.1.1.7-Mandatory for Sancs, Leisure for Users 

@biblepay
biblepay committed on Apr 1

For a grand total programming time of
   (40 hrs per week * 4 weeks) = 160 hours @ 40.00 per hour = $6400

Also, I would like to expense the following IT expenses for Biblepay:
Exchange e-mail inbox (1 year: for one director) $71

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

?6471.00/.000474 (CoinMarketCap 7-21-2018) = 13.6 million biblepay
Since I don't want to exceed 50% of the IT budget, I'll cap this proposal at 3.5 million and gift the rest to biblepay.


Thank you for your consideration.

3
If the poll passes to remove the team requirement, what percentage of reward should we give to non-biblepay BOINC crunchers who fully associate their biblepay wallet with their CPID and post a valid UTXO stake for their RAC?


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


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 requesting  7,000,000 bbp (which is 25% of what we need.).

Due to our low price we will need to terminate approximately half of the sponsorships later this month.
They will be covered by Compassions continued-sponsor-insurance program.




5
All,

  We have 329 orphans sitting at risk currently with a questionable future.  I not only want to avoid attrition, I want to see growth! 

So heres an idea.  I really think we need to consider removing all the roadblocks inside Biblepay (IE Opening the Floodgates) for cancer mining.  We can consider doing this by:  Removing the Boinc team requirement (being the first cryptocurrency to not require a team for boinc), and making it easier to heat-mine.  (IE doing away with the last 4 block rule).  (We can leave in the signed by CPID rule as a lateral move preserving heat-mining security).

I feel with this change, we can test the theory that more miners = more adoption = higher price = more monthly orphan sponsorships.

Also, as Noxpost suggested, I dont see why we cant write our own boincstats report (as we will still have records of our Biblepay participating CPIDs, RAC, TotalRAC etc).  So we really only lose the "BiblePay BOINC Team" statistics in boincstats, but instead we have our own stats page.  Maybe that internal stats website is something T-Mike would like to take on for us?

So, as you can see I'm pretty zealous for success here, and want us to make a comeback.  Therefore I believe its in our best interests to vote on this change.

Proposed Changes:

- Remove Boinc Team Requirement for users participating in BiblePay PODC (this compensates users for Rosetta or World Community Grid on ANY team)
- Refactor Heat Mining Block acceptor to help minimize the possibility of forks
- Still require signed cpid per block, and CPID must not be within 3 solved blocks
- Remove the rule requiring CPID to be in the last superblock
- Work with a team member to help create our own stats report for a website and/or the pool
- Leave in UTXO requirement for Boinc Miners

Desired Outcome:

- A new boinc user who is crunching for XYZ discovers they can be compensated for Rosetta cancer mining through Biblepay.
 The new user loads our wallet, syncs, and associates their XYZ cpid with our wallet. 
(The new user still must have a required balance shown in exec totalrac to PODC mine).

- The user is able to heat mine with the signed cpid immediately, as long as the CPID has RAC > 100.

This removes most of the strange pool errors in pool.biblepay.org and purepool.


One notion is that in general, I assume BOINC users to have enough disposable income to afford expensive computers for volunteer computing, therefore I come to the conclusion they may become biblepay investors through this process.

And, to counter the theory that we are "giving away free money", consider the fact that the ones who do not become investors will sell off the coins cheap on the market and make us more rare.  So imo, this is an economic decision worth considering.

If the idea is a success, all credit to Jesus.







6
Welcome to the BiblePay Testnet thread for IPFS!

To install the latest version for testnet:
Please upgrade to v1.1.4.7+



  • Test attaching a document to a new QT Send Transaction
  • Test double clicking the transaction list and viewing the attached IPFS file hash
  • Test Opening the IPFS document link
  • Test the fee charged for BiblePay storage
  • Assess exact root cause of IPFS instability; when ipfs.io goes down, check to see if reliability is 100% when using our gateway (IE files are still always retrievable and instability is always gateway instability), we need to determine the quality level of IPFS itself

How to install IPFS on a Sanctuary (Ubuntu 64 instructions):
https://raw.githubusercontent.com/biblepay/biblepay/master/InstallingIPFS_Ubuntu64.md

How to launch biblepay-qt in testnet:
./biblepay-qt -testnet -listen=0 -masternode=0

(The listen and masternode flags are only required if you want to run Testnet side-by-side your Prod sanctuary)

Synced Verification Info:

getblockhash 53930
45aa03a87251d06b867e4fbb5e24d87970e18176d1739e609366156423a847fb


To help us isolate and assess any instability I started a gateway server (similar to ipfs.io except http:// and running on 8080):
http://ipfs.biblepay.org:8080/ipfs/QmPVMkWe7976YH22quBotbrDMV9tP4qCz9P5tndveKdeGs/hi.txt
We may want to change the biblepay links to go through this gateway to remove instability.



7
Create DAHF Algorithm for BiblePay / LOCKED - concept related to dahf
« on: August 19, 2018, 08:23:41 pm »
This thread is dedicated to the initial discussion for DAHF; Decentralized Autonomous Hedge Fund.

For a primer on the concept please read this first:
https://wiki.biblepay.org/Concept_DAHF

Some of the concepts we want to cover in this thread (resulting in a proof-of-concept program suite for testnet, and a regulatory review process) are:

A suite of programs:


Block Sync:  This program is designed to standardize financial blocks from the year 2000 on a daily basis up to the current day, with one financial block per day.  Financial blocks are synced by the sanctuaries up to the current day.  A hash algorithm is used (SHA256) to ensure each block's integrity.

Hedge Fund Options Analyzer/Sanctuary (AL):  The Hedge fund options analyzer standardizes raw market data into financial blocks and hashes the blocks.  This program does the majority of the work pertaining to the analysis of various strategies up front: such as Calendar Spread, Bear/bull Verticals, Iron-condors, Boxes, etc.

Portfolio Manager Virtual Machine (VM):  This program allows a portfolio manager to register strategies, thereby creating a virtual portfolio with certain rulesets using our very own hedge fund programming language (similar to a smart contract builder).  Some of the rules include:  The ability to go long or short a security based on richness (IE the Cost divided by the Maximum Gain), theoretical Bjerk Phi future stress test analys(es), Weighting of the contract quantity, trading on signals based on the Vix, option volatility, volume, etc.  This program gives the PM (the Portfolio Manager) a report, containing ROI per cost center, bank balance over time, and detailed trade activity.  This program runs in sanctuaries, and has the capability to emit trade signals based on short-term activity (despite the fact that most portfolios are long term - IE 2 year portfolios).

Black Boxes:  One of the goals for DAHF is to write Black Boxes, these are algorithmic option trading programs that seek to profit using specific strategies and quant (financial specialist) business logic based on a running simulation over time using actual financial data.  We are seeking one major black box per strategy.  Some of these strategies are core concepts, or quant secrets that large trading institutions (like Renaissance Technologies) use.  We are not seeking to reveal Renaissance' internal secrets, instead we are trying to recreate a similar black box that maintains similar performance.  For example, Renaissance has created a reference portfolio of long positions, in which they sub out to a bank who creates barrier options that replicates the portfolio.  In this way they can buy the barrier option and sell the reference portfolio.  They profit from the premium on each security that is short.  This is an example of a synthetic-reference arb.  We seek to create a black box for stat arb designed
 for each concept (per homogenized trading era per strategy) for Biblepay.


Initial Path for General User Investments:

We are discussing several paths of success with DAHF.  Some of these paths explore various methods of investing/liquidating investments into the fund. 

The first method, this method is preferred pending legal analysis: a normal user will buy shares of BBPHF by sending an amount to a BiblePay burn address (dedicated to the hedge fund).  This transaction will contain the users Hedge Fund ID (obtained with an RPC command prior to sending). 

BiblePay core will be modified to provide hedge fund redemptions at the current DAHF NAV rate.  The redemption is done with an RPC command. 
BiblePay core will guarantee the redemption by adding a block-exercise feature.  This feature pays the user and sends a bill to the Hedge Fund.  If the hedge fund is insolvent, the user still is paid the withdrawal, but the hedge fund relationship is terminated and is forced to close down. 

Note regarding the risk to biblepay:  Most of the risk will be removed from BiblePay itself due to multiple factors:  A) We will not be allowed to operate unless we raise a signifigant amount of capital with the prime broker, therefore the fund will most likely have enough money to pay biblepay core during a collapse.  B) During a collapse, even in the worst case scenario, the redemption value per user would be lower (due to a collapsing asset mark to market value), meaning the final payout from biblepaycore would not result in a catastrophic loss for biblepaycore.  We will provide examples of these collapse scenarios.


Mining:


One novel use of the Hedge Fund Quant Algorithm we are developing will be the ability to provide another avenue for Mining!  This is exciting in the sense that we may be able to offer another use case for your CPU, as an alternative to heat mining (and in addition to PODC mining).  However, this will most likely be a mining option for windows machines with large hard drives.  This is primarily because the hedge fund suite will run in .NET, and require large hard disks. 

But what is exciting is we may theoretically be able to dedicate 1 block per hour to DAHF.  I'm monitoring the amount of trading activity DAHF produces, and theoretically with an active biblepay portfolio, we would trade approx. one asset per hour in prod.  The trading would occur in batches, so that the VM may catch up in times of backlogs.  For example, if nothing happened for 3 hours, and then all of a sudden a user solved a financial block in the third hour, this block may contain 5 transactions.  Theoretically the transactions would include opening/closing information in the biblepay blockchain, of actual OPRA codes, quantities and values affecting our hedge fund.


Benefit to Orphans


This concept was kicked around by Luke, Togo, Rob, Chad and Jaap, and we are leaning towards giving a gross 10% (of profits only) - from the hedge fund to the orphans, as a separate transaction - distinct from the core wallet - from the hedge fund only - annually at the point of time when the annual statement is being created (to avoid any short term mistakes).  The idea is that this hedge fund would always bless orphans first, then non-greedy investors would profit after.  I feel the high potential ROI could overcome the burden and that God will bless our project if we keep the children in mind first.



8
Production 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.


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


10
Production 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.



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

12
Production 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.

13
Production 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



14
Production 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.


15
Production 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.

Pages: [1] 2 3 4