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

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


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

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


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


6
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 63 childrens premiums for one month (in February 2018) meaning we are preapid with compassion by $2,394 which is a great start.

In the spirit of prepaying for 6 months in advance before sponsoring new children with compassion, I intend on using the suprlus to not only pay the $7,106 recurring invoice due on March 21 2018, but to use the excess to prepay more orphanage premiums into the future.

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,500,000 BBP this month since we have a higher budget with a target sale of $19,600.


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.



7
Production Proposals / February 2018 IT Expenses (Payroll)
« on: March 16, 2018, 05:29:50 pm »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from Nov 1 2017 through Nov 30 2017:

Commits on Nov 29, 2017
1.0.6.3-Mandatory Upgrade - TESTNET 

@biblepay
biblepay committed on Nov 29, 2017
 
Commits on Nov 20, 2017
1.0.6.2-Leisure 

@biblepay
biblepay committed on Nov 20, 2017
 
Commits on Nov 17, 2017
1.0.6.1b-Leisure (Highly Recommended Upgrade) 

@biblepay
biblepay committed on Nov 17, 2017
 
1.0.6.1-TESTNET 

@biblepay
biblepay committed on Nov 17, 2017
 
Commits on Nov 16, 2017
1.0.6.0-Testnet-Leisure 

@biblepay
biblepay committed on Nov 16, 2017
 
Commits on Nov 15, 2017
1.0.5.9b-Leisure 

@biblepay
biblepay committed on Nov 15, 2017
 
1.0.5.9-Leisure-Testnet 

@biblepay
biblepay committed on Nov 15, 2017
 
Commits on Nov 13, 2017
1.0.5.8c-Testnet 

@biblepay
biblepay committed on Nov 13, 2017
 
1.0.5.8b-TestNet 

@biblepay
biblepay committed on Nov 13, 2017
 
Commits on Nov 12, 2017
1.0.5.8-Testnet-Leisure 

@biblepay
biblepay committed on Nov 12, 2017
 
1.0.5.7-Leisure 

@biblepay
biblepay committed on Nov 12, 2017
 
1.0.5.6b-TESTNET 

@biblepay
biblepay committed on Nov 12, 2017
 
Commits on Nov 11, 2017
1.0.5.6-TESTNET-Leisure Upgrade 

@biblepay
biblepay committed on Nov 11, 2017
 
Commits on Nov 9, 2017
1.0.5.4b (TESTNET) - Leisure Upgrade 

@biblepay
biblepay committed on Nov 9, 2017
 


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

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

Zinc, Exchange, SSL for wiki.biblepay.org, and resource upgrade for biblepay.org for Wordpress ($313.08):
Receipts:
http://pool.biblepay.org/SAN/expenses/ITExpensesBiblePayFeb2018.pdf


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

?6713/.002930 = 2,291,126 BBP


Thank you for your consideration.


8
All,

Our PODC Distributed Computing superblocks pay based on a researchers magnitude, which is assessed once per day by the Sanctuary Quorum.

The magnitude ranges between 0 and 1000 per CPID (that is per researcher).

The proposal is geared towards requiring Super Users to Stake More Biblepay in order to be compensated for research.

With the thought that a mining organization, a previous bot-net, who deploys 500 machines yet only stakes 50,000 BBP will be receiving massive rewards and diluting the earnings of the small users who are less fortunate to afford that kind of big mining equipment.

In the spirit of increasing competition, we propose to require approx. 2500 BBP per magnitude, meaning that if you are a researcher with 4 computers, let us assume your magnitude is 20, then you would be required to set your utxoamount=50,000 in order to receive full research compensation.   If you only stake 25,000 on a given day, in this case your reward compensation would be multiplied * .50.

For another example, let us take a power user with 255 machines, and a magnitude of 300.  Since this user virtually controls a third of biblepay's emission level, if the 2,500 BBP UTXO requirement were in place, that CPID would need to stake 750,000 BBP per day to maintain the full reward level.

Thank you for your participation.


9
The primary purpose of this proposal is for the approval for us as a community to use Proof-of-Distributed Computing as a major reward algorithm in biblepay, and as a tool to help bust the botnet.

Please read some of the background info on PODC here:
http://wiki.biblepay.org/Distributed_Computing


Block Security
===========

With Proof-of-distributed-computing enabled, I propose that we continue to use the existing consensus algorithm, PoBH (proof-of-bible-hash),  for block security.

This is so our chains integrity can be maintained, and will not be completely trusted to any 3rd party.  We continue to use DGW (Dark Gravity Wave ) for our difficulty algorithm, this helps us stay less prone to 51% attacks (attacks formed by buying out a percent of biblepay on the market).
    The existing POBH-POW algorithm for chain security ensures that we have a structurally sound blockchain that syncs from zero consistently, and that it is easy for the core wallet to detect forks. 
( This is a major concern, and must be taken seriously).

(This is in contrast a common problem with proof-of-stake consensus systems- where hackers have an attack vector potential created by solving blocks on multiple chains, making it hard for the core wallet to recognize which chain has the most work). In POW based chains, it is easy for the core wallet to stay on track, as the chain with the most work is usually a magnitude more than other chains.

I recommend that we keep the existing POBH-POW-heat mining system for block security, and for chain sync consistency. However, we reduce the payments on the POW-Heat side by 90%, so that we starve off the botnet first of all, by raising the PODC rewards up by 90%.

Imo, no botnet is going to choose to Heat Mine for 90% less when they can choose Rosetta mining for 90% more.
(This is proven in practice in all casinos).

I propose that we promote POBH mining only on the controller wallets, since those wallets would perform sending/receiving of biblepay funds, starting/stopping sanctuaries, managing Rosetta CPIDs, CPID association, and also mining on one thread for our block security.

It has been raised as an issue that if we lower rewards on the heat side by 90%, most strong miners will go away thereby leaving our security more vulnerable to an entity with large dormant hashpower, meaning that they will attempt to come in with a quick hash attack, and take over the chain and issue a double spend.

To combat this, I propose that we limit the ability to solve blocks to only Researchers with Active CPIDs in the chain (associated cancer researchers), with existing Magnitude and coins earned in the last superblock, and limit CPIDs from solving only one block per 6 block period.  What this does is ensures that one researcher cannot enable massive hashpower and solve another block in the confirm period duration.  This would require distinct CPIDs to join in-lessening the chances of an attack.  Since the CPIDs must be actively crunching with RAC and magnitude and be in the prior superblock, a horizonal scaling attempt is not possible  (as it will take at least 2 days to ramp up a new CPIDs magnitude and be paid, while the attackers Old cpids will be diminishing in power).  In addition, DGW already adjusts to the current difficulty level, so a brute hashpower attack is very unlikely to win, with our low nonce rule, the attackers difficulty would rise by exponential amounts per solved block, and if any non-hacker CPID solves a block in between (which is highly likely due to the low nonce rule), the attack is not successful.

Security:

In this solution, we require Rosetta CPIDs to actually type in their credentials to become associated with Biblepay.  All other biblepay researchers check the burn transaction in the memory pool, to verify the CPID is actually owned by the owner.  So therefore it is not possible to be rewarded research rewards for any CPID not owned by the owner and verified with the burn transaction.  Once the burn is checked, the researchers signature is set in the chain, and we respect future signed CPID messages from this researcher.  Replay attacks are not possible.

The SanctuaryQuorum votes on the daily Magnitude file.  We have a system in place to ensure only the official CPID magnitudes will pass in the vote (as a net 10% have to vote on the correct hashed contract) in order for the contract to be recognized as valid for the daily superblock.

In addition, the research payments are constructed in a way that divides the magnitudes by the superblock available budget, so if a Rosetta error would occur, the payment error would be relative to that superblocks budget, and would not result in a chain block overpayment (IE we never pay more than the total budget per day) and we divide the rewards by the share of each researchers weight per day.

Unlimited Scalability:

The daily superblock reward system was chosen so that biblepay may scale to allow up to 32767 researchers to be paid concurrently per day.  Since there are currently 48,000 Rosetta servers actively crunching, this system could accomodate every Rosetta CPID as a potential biblepay user!  We also do not require the researcher to quit their team, but through our advanced security, they may come onboard as a loyal biblepay user.  This results in great PR for biblepay.


In summary, this is what I am proposing:

Proof-Of-Work rewards drop to approx 600 BBP per block (a reduction of 90%)
Proof-Of-Distributed-Computing rewards increase to approx 5500 BBP per block (an increase of 90%)
One superblock per day airdrops the researcher rewards, allowing up to 32767 research payments per day


Theory to bust the botnet:

Since POW rewards would decrease by 90%, the botnet would quit heat mining and start cancer mining
POW would require a signed CPID to solve a block
POW would require a CPID to be active and have prior payments to solve a block
Biblepay would have a feature, if no CPID is available in 31 minutes to solve a block, we would allow any heat miner to solve the block (so chain never gets frozen, in case of Rosetta being down etc)
These rules would lower the chances of an outside 51% attack to almost zero, when combined with DGW's protection

I recommend POL to be disabled for now (proof-of-loyalty) and that we instead research ways to include an element of POL in each Rosetta work unit to raise the trust and integrity level of Proof-of-distributed-computing to the highest level for the masses. 
^ If POL is trusted as a sole consensus algorithm, then PODC+POL may be a potential global leading candidate in the future.

PODC also will allow us to achieve a great future milestone:  Mining for the unbanked.  Since Rosetta cancer mining supports ARM tablets and ARM cell phones, it is possible for the unbanked through cancer research to earn enough to live on or at least buy groceries in third world countries.  This is more than we currently have, since POBH currently runs on PCs only.


The financial renumeration for this proposal is only 10 BBP, as our budget is mostly consumed.

Please vote for this if you believe this will not only allow us to be a humanitarian force - one facet of our community is doing what Jesus would do : help heal others, but also if you believe we will help remove the influence of the botnet and take our community back.




10
Please join us in testing Proof-of-Distributed-Computing, a new consensus algorithm for Biblepay.

This algorithm is designed to divert proof-of-work clock-cycles (heat mining) into cancer-mining-clock-cycles through Rosetta@Home, performing useful work.

Testnet release date :  February 6th, 2018  @   15:58:00.

Windows is still compiling.  Will update when ready.
Please compile Linux from source :  https://github.com/biblepay/biblepay
Version: 1.0.8.8k - Leisure

NOTE:

Testnet has changed severely.  Please :
rm blocks -r
rm chainstate -r
rm mnc*.dat
rm gov*.dat
rm banlist.dat

Restart client.


To get started with Proof of Distributed Computing:

See Background info on distributed-computing first:
http://wiki.biblepay.org/Distributed_Computing

See guide:

How to Get Started with Distributed-Computing:
http://wiki.biblepay.org/Distributed_Computing_Start_Guide


**NOTE:  So far, the guide shows how to run Rosetta on Windows (as your cancer miner), and your biblepay wallet on linux (compiled from github).

 I am still in the process of documenting how to install Rosetta on linux ** (Its easy, if you are daring, please check the windows instructions in the guide and give it a shot on linux using the apt-get boinc commands )



PS All credit for this project goes to Jesus.

11
Archived Proposals / Jan 2018 IT Expenses (Payroll)
« on: February 01, 2018, 08:01:44 pm »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from Oct 1 2017 through Oct 30 2017:

Commits on Oct 30, 2017
1.0.5.4-Leisure (TESTNET) 

@biblepay
biblepay committed on Oct 30, 2017
25e112a 
1.0.5.3 - Leisure Upgrade (TESTNET) 

@biblepay
biblepay committed on Oct 30, 2017
3d78c93 
Commits on Oct 29, 2017
1.0.5.2-Leisure (TESTNET) 

@biblepay
biblepay committed on Oct 29, 2017
afbcfe4 
Commits on Oct 28, 2017
1.0.5.1-Non-Mandatory 

@biblepay
biblepay committed on Oct 28, 2017
de1d1f4 
1.0.5.0 - Non Mandatory (TESTNET) 

@biblepay
biblepay committed on Oct 28, 2017
392d272 
Commits on Oct 27, 2017
1.0.4.9-Non-Mandatory (TESTNET) 

@biblepay
biblepay committed on Oct 27, 2017
14230b6 
Commits on Oct 6, 2017
1.0.4.8-Non-Mandatory 

@biblepay
biblepay committed on Oct 6, 2017
9a82919 
Commits on Oct 3, 2017
1.0.4.7b-Non-Mandatory 

@biblepay
biblepay committed on Oct 3, 2017
e77652e 
Commits on Oct 2, 2017
1.0.4.7-Non-Mandatory 

@biblepay
biblepay committed on Oct 2, 2017
98e8f9b 
Commits on Oct 1, 2017
1.0.4.6-Non-Mandatory 

@biblepay
biblepay committed on Oct 1, 2017
9a1575b 


For a grand total programming time of  90 hours @ 40.00 per hour = $3600.00

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

Zinc (Amazon integration) API charges =  $100.00
http://pool.biblepay.org/SAN/Expenses/ZincJan2018.pdf

Cloudflare charges = $20.00
http://pool.biblepay.org/SAN/Expenses/ZincJan2018.pdf

For a Grand Total Proposal of :  $3720.00
Equaling:

?3720/.003765 = 988047 BBP


Thank you for your consideration.




12
Archived Proposals / February 2018 Compassion.com Recurring Expenses
« on: February 01, 2018, 07:26:55 pm »
Each month we sponsor approximately 189 orphans currently.
Rob, the lead dev charges the expense on his credit card, and keeps a copy of the receipt. 
The expenses can be viewed by navigate to Accountability.biblepay.org | Expenses and viewing the December PDF.

We currently have a surplus of approx. $400 in Robs bank account that he will spend on the Orphan Prepaid Premiums this month (to start our initiative into Prepaying Premiums into the future, at least 6 months in the future to give these children some level of stability).

 See accountability.biblepay.org | Orphans | Orphan Fundraisers.  You can audit the total by finding the sum of all fundraisers.


 I am requesting 2894609 biblepay for the February 2018 montly premiums, and anything left over will be used for sponsoring orphan premiums into the future.  There will be a column updated in the Orphan Expenses to clearly show how much progress we made on prepaying after the third week of February (that is when the bill is due each month).


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

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.







13
Production Proposals / New Exchange Proposal - Add new Biblepay Exchange
« on: January 25, 2018, 06:46:01 pm »
Zthomasz, Tom, has spearheaded the initiative to get us listed on a new exchange, possibly Yobit, SouthXchange, or NEXT, or one of the top 50 bitcoin exchanges.

Yobit has a policy where they will list a new coin for .10BTC within 7 days - but we have since discovered they are NOT honoring this agreement.



Tom has started a campaign that accepts USD funds for a new exchange here:
New Exchange Fee Fund Link:

https://activara.net/yobit/


Please post here if you would like to donate in BBP, post the amount so we can keep track of how much we raised.


14
Archived Proposals / PROPOSAL : Proof-Of-Loyalty
« on: January 20, 2018, 11:43:01 am »
All, recently what appears to be either a harmless mining organization with a lot of nodes, or a botnet has taken over the majority of the hashpower of our network. 

In an attempt to stave off the botnet, I propose an extension to our hash algorithm called proof-of-loyalty.

It makes our PoBH algorithm a hybrid, as the blocks become easier to solve as you accrue more coin-age.

Please see this wiki page for the background information and most technical information:

http://wiki.biblepay.org/Proof_Of_Loyalty


This feature also helps us straighten the path to eventually mine on mobile devices, as this miner will eventually solo mine a block with enough coin-age without much hashing.



I personally believe rewarding investors and our loyal community members with more rewards and the propensity to solve a block by those in the light will prove to be a positive addition to biblepay, and will allow us (to have) more control during the software upgrade process.



Although this feature has taken more than 40 hours to code in the core client, I am asking for a flat 100,000 BBP reward for this to be voted and merged in to the core client.



15
All, it's time to test a new Biblepay   8)    Feature!

One that helps us make inroads into third world countries, helps us mine on mobile phones, and helps reward our loyal investors who Tithe!

And most importantly helps foil pesky BotNets.

Please see this wiki page for the background information and most technical information:

http://wiki.biblepay.org/Proof_Of_Loyalty


Note, that in the biblepay client, the default staking target percentage is set to .10.  (IE 10% of your coins).  If you would like to change it please modify the "polpercentage" key with a whole number between 00 and 100.


For linux:  Please build 1.0.8.3

or for Windows: Please download v1.0.8.3 from here: https://www.biblepay.org
before proceeding.

You may start your client in testnet by adding the "-testnet" suffix.

Let me know when synced and we will start testing.


NOTE:  The linux version currently has no way to notify you that it was a proof-of-loyalty block, I am working on that now.  The QT version does display it.


NOTE II:  This first version does not make any effort to unlock your wallet.  Staking requires an unlocked wallet.  We can discuss this in the thread.  For now, please unlock your wallet for thousands of minutes to test this version (if it is locked).


EDIT III:  If you need an addnode:  node.biblepay.org, we are on block number 514

** Please start with an empty chain in testnet, rules have changed in testnet since last tests **






Pages: [1] 2