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.


Messages - Rob A.

Pages: [1] 2 3 4 5 6 7 8 ... 69
1
Production Proposals / Re: Crypto Bridge Exchange Listing
« on: May 20, 2018, 12:50:01 pm »
There is currently just short of 1BTC in the New Exchange Fund (I have .45BTC on my ledger and .5+ BTC on c-cex. But I still have about 170k BBP to sell, so we'll have 1+BTC for sure this month.

I will definitely vote 'yes' for this proposal. In my opinion for a coin like us it's best to bet on big potential instead of paying big for already established exchanges (although getting on a big exchange would be awesome, it just isn't realistic at this point I guess).



All - thanks for finding CryptoBridge - and although this looks good, let us be transparent and remind everyone the status we have on any other live offers, so they can vote appropriately on this proposal.

As you all know it's not easy to be listed on an exchange.  Not only do we need to like them, they need to like us.  And the offer must not be a scam.  Even if an exchange has an offer that says "list coin here for 4 btc", just because you have 4 btc does not mean you are listed.  You also need to be vetted by them, and they have to agree to integrate.  Among other things.

So we have an outstanding offer on the table for CoinExchange.io, where our coin made it to the point that they offered to list us for 2BTC.  We asked them to hold on to the freshdesk ticket until we save up enough funding in the treasury for the listing.  We planned on voting for which exchange we apply Jaaps treasury funds to.  So please keep that in mind, and hopefully, we will go with coinexchange sometime in the future.

My personal opinion on this proposal is not only do they look solid, but the order in which we execute makes more sense to go with CryptoBridge first (as its solid and cheaper) and we almost have the funds ready.

In this case Ill vote for cryptobridge for the next exchange.

PS - so the moral of the story is next time we enter an exchange proposal lets list any live offers in the body also :).



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

3
I will be voting yes; the brethren are worthy of their wages.

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


5
Me too, I easily vote overwhelmingly Yes!  Its an awesome theme, the colors are consistent, the CSS is better, the icons are modern, etc, and you had to have programming skills to make the menu work on the left.

Now we have room to add buttons for an Exchange Link to our exchanges, for example.

We might even want to move the mixing buttons to the left menu eventually as they kind of hang out there.

Anywa, if you create a free account over at pool.biblepay.org and post your username I will up your balance so this proposal can be entered.


6
Awesome!

Just a heads up, currently if all proposals currently passing pass that comes out to 15,058,821 BBP
There is only 15,375,000 BBP in the budget, leaving 316,179 BBP leftover which is below the amount requested for this proposal.
So this proposal may knock out another proposal, or be pushed to next budget cycle.

Thanks Togo!

I deleted the old Compassion proposal and re-entered a new one for 4.6MM to rectify this issue.



7
Im glad we are making the site even better!  Great job!

We have a complex system, so I think we require a little more than the average site, with active Orphanage partners, PODC, Mining guides, Blogs, Governance, etc, but we'll get there.

One concern I did have is the use of wordpress plugins.  Our host gave me a call and said we pegged the servers performance within 48 hours, so I upped the monthly service level to the "supreme" plan, but then the server ran out of memory.  We looked at the plugins briefly and the host seems to think some of these are chained together (IE one developer of one plugin doesn't know it affects the performance of another).  So maybe when we have some time, if we could try to eliminate all the plugins and go with native wordpress?  (Or move away from wordpress altogether).

Btw I know Im supposed to look at the test site and the roadmap, I will do that soon, the families taxes have interfered this week.


8
Production Proposals / March 2018 IT Expenses - Payroll
« on: April 16, 2018, 12:51:22 pm »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from Dec 1 2017 through Dec 31 2017:

Commits on Dec 31, 2017
1.0.7.3-Leisure 

@biblepay
biblepay committed on Dec 31
 
1.0.7.3-Leisure 

@biblepay
biblepay committed on Dec 31
 
Commits on Dec 30, 2017
1.0.7.2-Leisure Upgrade 

@biblepay
biblepay committed on Dec 30, 2017
 
Commits on Dec 20, 2017
1.0.7.1b-Mandatory Upgrade 

@biblepay
biblepay committed on Dec 20, 2017
 
1.0.7.1-Mandatory Upgrade 

@biblepay
biblepay committed on Dec 20, 2017
 
Commits on Dec 19, 2017
1.0.7.0-Leisure Upgrade 

@biblepay
biblepay committed on Dec 19, 2017
 
Commits on Dec 18, 2017
1.0.6.9-Mandatory Upgrade 

@biblepay
biblepay committed on Dec 18, 2017
 
Commits on Dec 17, 2017
1.0.6.8b-Mandatory Upgrade 

@biblepay
biblepay committed on Dec 17, 2017
Commits on Dec 17, 2017
1.0.6.8-Mandatory Upgrade 

@biblepay
biblepay committed on Dec 17, 2017
 
1.0.6.7c-Mandatory Upgrade 

@biblepay
biblepay committed on Dec 17, 2017
 
1.0.6.7b-MANDATORY UPGRADE 

@biblepay
biblepay committed on Dec 17, 2017
 
1.0.6.7-Mandatory Upgrade 

@biblepay
biblepay committed on Dec 17, 2017
 
Commits on Dec 16, 2017
1.0.6.6c-MANDATORY UPGRADE 

@biblepay
biblepay committed on Dec 16, 2017
 
1.0.6.6b-Leisure 

@biblepay
biblepay committed on Dec 16, 2017
 
1.0.6.6-MANDATORY UPGRADE 

@biblepay
biblepay committed on Dec 16, 2017
 
Commits on Dec 14, 2017
1.0.6.5 - Mandatory Upgrade 

@biblepay
biblepay committed on Dec 14, 2017
 
Commits on Dec 6, 2017
1.0.6.4-Testnet 

@biblepay
biblepay committed on Dec 6, 2017




For a grand total programming time of
   (47.5 hrs per week * 4 weeks) = 190 hours @ 40.00 per hour = $7,600.00

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

Zinc, Exchange ($164)  (Exchange is for MIP-Biblepay Mobile Wallet - "Mobile Support" inbox):

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


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

?7764/.003301 (CoinMarketCap 4-16-2018 @ 12:50PM CST) = 2,352,014 BBP


Thank you for your consideration.

9
Production Proposals / Re: February 2018 IT Expenses (Payroll)
« on: April 16, 2018, 12:00:59 pm »
Great work Rob!

Is the developer you recently introduced also still working on the project?
Hi Jaap! Thanks dude, so Bhavani did report that he got his dev environment running and can now change the Biblepay code.
I originally put him on the Orphan Letter Writing project and then pulled him off based on the idea where we 'sponsor an orphan'.

But now he is working on integrated proposals in the core wallet.
So we can see a grid of proposals and vote on them.


10
Each month we sponsor approximately 210 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 navigating to Accountability.biblepay.org | Expenses and viewing the January PDF.

We have prepaid 450 childrens premiums (in Feb+Mar 2018) meaning we are preapid with compassion by $17,100  which is a great start to removing the danger level in the future for these kids (IE we are now 2 months completely prepaid for all children).  We have a target of being prepaid for $47,880 before sponsoring new children so we are 36% completed in the prepay mission.

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 5,000,000 BBP this month since we have a BLOOM proposal in requesting 13 childrens VISAs and trips (of a lifetime).

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.


11
Production Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: April 14, 2018, 11:12:55 am »
Amazing job MIP!  Thanks for your perseverance.

Now the unbanked cancer miner will be able to mine on android, receive rewards on the mobile, and spend on the mobile.

Now we just need to see how to bring down the hurdles for a person to buy groceries with the BBP if they have no PC and no BTC trading account.


EDIT:  On that subject, eventually, we should port our 'exec associate user pass' rpc command to the mobile!  LOL, not until after the iPhone works, weve got enough going on.


12
Awesome job bro!

How did the crowd receive the blockchain evangelization?

LOL, this is a good definition of a technology evangelist, lol, we are Technology Evangelists.


13
Great job!  Im glad you got the API path to expose the UTXOs, and figured out a way to persist the UTXO value in the database!

Im sure Lich will be happy to resync his chain!

Awesome!


14
Production Proposals / Re: Proposal idea: airdrop
« on: April 14, 2018, 10:55:00 am »
This sounds like a perfect project for T-mike.  Since he started podcbbp.org.

We could:
Advertise Helping cure cancer through clock cycles, receive $1 of free BBP - click here
The click takes you to his web site
The user pastes a New CPID
We verify the CPID Age > 0 and less than 7 days and the CPID has rac > 1 and the Receive address has not been used
We pay from his faucet the airdrop reward
We save the e-mail for new user correspondence on his mailing list


15
Production Proposals / Letter Writing Bounties
« on: April 10, 2018, 09:29:37 am »
Currently, we have a deficit in letter writing primarily because of our transition to PODC (heat mining rewards are lower, so the letter writing budget dropped) so people are not participating in writing for financial rewards.  In addition with the launch of purepool, most heat miners have navigated away from pool.biblepay.org to take advantage of the lower fee mining and avoiding the penalty that exists on the main pool.

Some have floated the idea of rewarding letter writers out of the p2p budget, others have floating sponsor-a-child feature (where one person owns a child, and takes responsibility for all communications with that child).

This proposal seeks 500,000 BBP to be split into two buckets:
Bucket 1: (250,000 BBP):   Used to reward letter writers in pool.biblepay.org for writing letters at approximately 1000 bbp per letter out of this fund.

Bucket 2: (250,000 BBP):  This will be reserved in the sponsor-a-child account, while Rob creates the feature.  Rob will make it so children who are sponsored by a miner do not appear in the general write-to-a-child business logic flow.  Instead the user will navigate to an available children list for sponsorship, and sponsor the child.  They will receive funds from this bucket as they write letters.

We will remove the writing penalty at the same time this bridge system goes into effect.


Pages: [1] 2 3 4 5 6 7 8 ... 69