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
16
Active Discussions / Consolidation of Sanctuaries
« on: April 05, 2019, 08:33:46 pm »
Since BiblePay is moving to Evolution in June, we have the opportunity to potentially change the Sanctuary lockup requirements from 1,550,001 to another figure.

I think this would be a good time to discuss potentially changing this lockup requirement higher in order to :
- Give our investors more ROI per Sanc
- Decrease Hosting Costs
- Increase reliability per Sanc (because user may afford a higher quality host and have more time to monitor each sanc)

The obvious downside to this is a higher barrier of entry cost for the small investor.
But, with our recent downturn in price bringing a sanctuary investment to only $400, I think this is a feasible idea.

For me as an investor, I would personally lean towards consolidating so I can spend less on hosting fees.
Analyzing the effect of wasted hosting:

We currently have about 500 sancs.
Our sanc owners are spending a very high percentage of the revenue on hosting (If hosting is $10 per month, with $20 of revenue that is 50% spent on hosting).

I believe reducing the sanc count by half will not hurt biblepay (as 250 nodes are still more than enough to service our network), and, it could be argued that 250 high quality sancs are better than 500 low quality sancs (as with low quality instant sends could get lost).

Additionally over the next 5 years, even if we move to 125 sancs, our sanc count will again increase (due to more coins being emitted and a lockup ratio average of approx 50% coins become locked into sancs).

I propose that we enter 3 sanctuary proposals floating this idea with different size lockups:
1) 3 million lockup
2) 4.5 million lockup
3) 7 million lockup

If all 3 are voted down we keep 1.55 MM.




17
EVOLUTION



Currently testing Dash 0.14 features in BiblePay v1.4.5.1+



Testnet Download Links:

Windows v.1.4.5.2+:
https://biblepay.org/biblepayevo32develop.exe


Linux PC 32bits
Daemon: https://biblepay.org/biblepayd-evo-testnet-i686-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux PC 64bits
Daemon: https://biblepay.org/biblepayd-evo--testnet-x86_64-pc-linux-gnu.tar.gz
QT: https://biblepay.org/biblepay-qt-evo-testnet-i686-pc-linux-gnu.tar.gz

Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz
Linux ARM32 daemon: https://biblepay.org/biblepayd-evo-testnet-arm-linux-gnueabihf.tar.gz

MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg






Mac-OS QT version here:
https://www.biblepay.org/biblepaycore-testnet.dmg



The purpose of this thread is to test BiblePay-Evolution and our new GSCs.

BiblePay-Evolution is our next release (scheduled for June 2019).

It includes all of the features that Bitcoin and Dash added to Dash over the course of 2018.
Including Segwit, Security updates, Lightning network support, BIPS and DIPS, ChainLocks (51% attack prevention), Deterministic Masternodes, Non-financial transactions, the Depends Development Build environment, C++14 compatibility for devs, more reliable chain syncing, better chain reorganization code, more reliable Governance messages, more efficient messages, HD wallets, High definition display support, InstantSend improvements, and more.

In BIblePay, we have added ABN (Anti-BotNet) mining.  This is a feature that requires miners to include an ABN transaction in each of their blocks that spends coin-age according to the network coin-age requirement (see getmininginfo).

We have also added GSCs (Generic Smart Contracts) client and server side.  The GSC allows BiblePay to abstract payments away from a hard consensus to allow the business logic rules to be malleable and configured so that they do not break consensus rules.  This results in a more reliable prod environment.

Before testing, please read about our GSC's here:
https://wiki.biblepay.org/Generic_Smart_Contracts


To Download BiblePay-Evolution, look for v1.4.0.1+ for windows on this link (at first, we will stay with 32 bit builds until we get close to Prod):
https://biblepay.org/biblepaycore-1.4.0-win32-setup.exe

MIP is working on building linux and MAC builds.  If necessary I will be able to release a link for Ubuntu64 builds/linux also.

To self compile Evo:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Let us start by testing standard core functionality in testnet.

Launching the client:

Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepayevolution

Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepayevolution/testnet3 folder.

NOTE:  We are keeping BiblePay's blocks, wallet, and chainstate in its own dedicated folder until the end of the test cycle at which time we determine if it is safe to change our pointer back to legacy biblepay files (as Evolutions blocks support a new file format, compressed, and Evo's wallet format has also been upgraded), so it is safer for us to keep these separate for now. 

NOTE: This version will also work side-by-side our production nodes, it will sync blocks, send and receive coins, however it will not peer with legacy Sanctuaries (as their protocol is too old).  We will need to test creation and usage of Sancs in Prod in Evo, and upgrade all legacy Sancs with a mandatory.




Getting started with Evolution:
https://wiki.biblepay.org/Getting_Started_with_Evolution
GSC's:
https://wiki.biblepay.org/Generic_Smart_Contracts
Healing Campaign:
https://wiki.biblepay.org/BiblePay_Healing_Campaign
Street Healing:
https://wiki.biblepay.org/Street_Healing
Spiritual Warfare:
https://wiki.biblepay.org/Spiritual-Warfare-I

How to upgrade a legacy Sanc:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html


18
Archived Proposals / Compassion March 2019 Recurring Sponsorships
« on: March 22, 2019, 11:07:00 am »
Our recurring charge is approx $2090, or 8.931MM, capping at 7MM.


19
Archived Proposals / March 2019 Payroll
« on: March 22, 2019, 10:58:53 am »
I'm posting my commits from November 2018, because back when we started BiblePay, we didn't have a governance system until December 2017 (that is why these invoices are 4 months old) (not because our price dropped, or because we are trying to back-invoice), these have been consistently behind since the beginning.

Commits on Nov 21, 2018
Merge branch 'master' of https://github.com/biblepay/biblepay

@biblepay
biblepay committed on Nov 21, 2018
 
1.1.6.1 - Leisure Upgrade 

@biblepay
biblepay committed on Nov 21, 2018
 
Commits on Nov 19, 2018
PPA script and doc

 
1.1.6.0-Leisure 

@biblepay
biblepay committed on Nov 16, 2018
 
Merge branch 'master' of https://github.com/biblepay/biblepay

@biblepay
biblepay committed on Nov 16, 2018
 
1.1.5.9f-Leisure Upgrade 

@biblepay
biblepay committed on Nov 16, 2018
 
Merge pull request #45 from thesnat21/Add_Spork_Outputs 

Commits on Nov 14, 2018
Better detection for BOINC client and error messages per OS

 
disable boost::process ShellCommand temporarily for non MacOS until w 

 
Commits on Nov 11, 2018
boinccmd call for MacOS (https://forum.biblepay.org/index.php?topic=2 

 
Commits on Nov 2, 2018



I'm requesting 80 hrs * 40 = 3200 = 13.2MM bbp, capping @ 3.5 MM


20
Archived Proposals / The Future of PODC - Proof of Distributed Computing
« on: February 28, 2019, 11:52:58 am »
DECIDING THE FUTURE OF PODC - PROOF OF DISTRIBUTED COMPUTING

Feb 28th, 2019


My what a ride its been in 2018.  (If we only knew everything that we know now, before the beginning of 2018, we would all be a little further ahead in life) - but for me - drawing closer to Jesus is the greatest achievement, and should never be traded for anything.

Going into 2018, I thought I was already experienced, but 2018 redefined that 'assumption' in many ways.  We had lots of things happen in our forums.  We had the huge HODL rise and crash.  I think while we were at our peak of 329 monthly orphans, we also took a lot of credit for this rise as if we - as a community - succeeded at something.  Another words, we should have been monitoring for our own pride and improving - but we let ourselves fall with the HODL fall.  Be very wary of taking credit for achievements -- I believe we were primarily influenced from external forces.  The cryptocurrency market was clearly influenced by Bitcoin and Dashes rise (and fall).

I personally had strong opinions of long held beliefs in certain areas only to be tested, and I've changed my opinion about certain things.  We had our sessions with our focus group (our internal advisors) and our external advisors (an SEC attorney, Manna, outwest advisors, DAHF, etc) and learned that we should be a utility, with a known revenue stream.  That going with DAHF would have pulled us in an anti-God direction.  And that we should add infrastructure to invite a Christian base to use the gospel features.

I'm only saying all of this because I want people to realize that many factors influence the decision of a good algorithm for BiblePay.  It's not that we are being hot and cold, it's that this is a complicated environment, and I personally want to make a long lasting decision that satisfies all of the facets to the highest degree.




We are trying to decide if we should retire PODC or keep it as an algorithm within Biblepay-core. 
The impetus for removing it is that a lot of us feel that our user-base has stagnated because PODC is too hard to understand and set up.
Thefore, it prevents us from sending the wallet to a brand new user - and allowing them to figure out on their own how to set up mining, receive rewards and tell their friends about BBP (free advertising and growth).

The problem with keeping both algorithms is it requires constant maintenace from the developers to focus on more than one.  The other problem is splitting rewards by 96% and 4% does not give POG the chance to grow.  So, the question is, should we completely retire PODC, and give the budget over to POG, so that POG can potentially grow our userbase automatically?

It could also be potentially floated to split the algorithms 50-50, allowing them to compete.  However, the issue with this is then our IT department still must support PODC and all of its related dependencies and infrastructure.  And, does a 50% PODC environment help biblepay more than a 100% POG environment?

That is what we will be discussing here.


Let me name off some of the facets in a mining algorithm:
IT Development Hours
IT Maintenance Hours
Coolness factor
Risk of a constantly supply of work units
User attrition/augmentation levels, Practicality, User Acceptance, Ease of Use, Community Growth/Price appreciation/Total orphan benefit
Algorithm Extensibility/Fragility
Hard emission reconciliation/Oracles, Whale Approval
Total infrastructure size and maintenance (3rd party credit sites, credit network, debug tool sites, pools)
Greed-Arms Race-Rat Race Levels
Jesus' (Christian Growth) levels/Christian Attraction/Christian Future
Blockchain Security


To start to compare the PODC algorithm to POG, let me first attempt to name some of the pros and cons of PODC:
NOTE!  The following views are *my opinion* as founder; if you disagree please have a civil conversation below, and vote appropriately.


Pros with PODC:

IT/Development: The Creation of PODC is already coded
Coolness:  The Rosetta cancer mining program is 'cool' and gives us a good image as in doing positive work for humanity, the highly technical users are drawn to 'try' podc as a challenge
Extensibility: The algorithm is modular (in that it works outside of biblepay and uses a sanctuary consensus),  and extensible (in that business logic changes can be made at the sanc level without requiring a mandatory)
Price Support: PODC has the 20bbp-per-rac rule meaning it "may or may not" cause price appreciation (I vote neutral on this as we can't tell at this point if this is good or bad for our price, since we appear to be stagnating).

Cons with PODC:

User Acceptance: The algorithm requires a dictionary of terminology to understand, so it appears to be complicated to learn by newbies, it appears to be complicated to be activated and maintained (without knowing the inner workings under the hood to understand how to keep it purring)
Dev Maintenance:  Development hours for Enhancing podc are still not complete, the algorithm certainly needs improved in the area of ease of use, the maintenance hours involved in maintaining PODC from an IT standpoint are relatively high
Fragility:  Fragility is high,  the risk of the contract breaking or changing is high, and the  BOINC/Rosetta/WCG interface risk is high
Work-unit-risk: The risk of work-units running out is medium to high
User attrition levels:  User levels appear to be low and stagnating (based on our sideways to shrinking podc diff level and user count), podc appears to attract richer users with many horizontal computers (in contrast to average users with a low pc count)-and this appears to stagnate growth as the rich users take a high percentage of rewards away from the small users.  The small user base appears to have stagnated our price into a range of 7 satoshi (due to the average miner being reluctant to sell below the electricity cost of PODC).  (I feel BBP has a much bigger potential in many other ways). 
Infrastructure Size and maintenance: The total infrastructure size is High (due to needing 3rd party tools for debugging and for credit reporting), and third party sites like pools and web support sites need maintained.
Greed-Rat-Race-Arms Race Level:  The Greed/Rat-Race level appears to be very high (as each user wants to achieve higher RAC than others) and this appears to create an environment in BBP where higher results are more important than talking about the gospel (Ive posted many snippets to links about Jesus in the middle of our forum, and actually was screamed at by people saying I was spamming, but yet I dont recall anyone starting a real conversation - other than a couple people who just disagreed about the Jews a year ago).
  The people we are attracting to the community for cancer research seem to be more scientific and less Theological (this is entirely an assumption and I dont mean to offend anyone - I actually want the atheists to come, but they dont appear to be coming to learn about Jesus from PODC), and I realize this is a hard requirement, so I simplify this down to : how can we attract a LOT of new users that turn to Christians that stick around.
Blockchain Security:  We have less hashpower being directed at POBH and more to PODC (because financially PODC pays 96% of the reward) so this results in less total network security with more machine power being used for RAC. 
Oracle/Whale Approval:   Whales may be reluctant to jump in as a BiblePay investor if emissions are not fully reconcilable in a hard way on-chain (when the whale takes into account the entire subject for coinbase-reconciliation).


Pros with POG:


IT/Creation: POG is coded,  99% of the POG maintenance (est) is already completed
IT/Maintenance:  POG is low maintenance
Work-Unit-Risk: POG does not have a work-unit limit
User attrition/growth:  POG has the capacity to attract *more users per consumed electricity KWH than PODC* because it is 80% greener than PODC and in addition it rewards users for holding distinct coins (meaning that a reconciled POG user daily reward points to One head, not many machines) therefore I conclude POG equals more HEADCOUNT than PODC, This theoretically means BiblePay expands its participation level, this results in community growth/help with tasks/price appreciation/more orphans, POG is very easy to setup - it is almost turnkey.
Fragility:  The algorithm is not fragile
Reconciliation/Trust/WhaleApproval: The payment emissions are hard and reconcilable, there is no oracle / trust issue, there is no tampering issue, POG would theoretically be whale approved.
Infrastructure: POG reduces total infrastructure down to an in-wallet novel pool and removes the need for 3rd party credit sites, pools, and debug tools.
Greed-arms-race-rat-race:  The rat-race and greed level appears to be very low (as people will be Giving to the foundation to receive a reward and hashing on single machines per head) and only out of personal generosity running multiple hashing machines.   
Christian Growth:  The total headcount appears to be aligned with increasing the attraction of Christian community members
Blockchain Security:  Security is increased due to having an increasing reward (1 mil per day towards pog) means a 10* userbase size increase, meaning a 10* POW security increase.  POG scales well to thousands of users.


Cons with POG:


Coolness factor: POG is much more "simple" than PODC (IE we aren't solving humanity's most complex problems) so we lose the "cool" factor of cancer-mining.
Extensibility:  POG can't allow us (currently) to change its rules without a mandatory (extensibility). 




21
Archived Proposals / Cameroon One - Installment 2
« on: February 23, 2019, 05:58:03 pm »
We only rose $492.55 last month due to our low price, so we are asking for 2 mil more for Todd at Cameroon One.

Note: Todds colleague Hillary will handle the liquidation, thanks Hillary!




22
Archived Proposals / Compassion Feb 2019 recurring orphan sponsorships
« on: February 20, 2019, 12:27:59 pm »
To maintain our 102 orphan sponsorships:
?3876/.000242
 16,016,528.9256198

Capping at 6 mil.


23
Archived Proposals / Feb Payroll
« on: February 20, 2019, 12:22:09 pm »
Commits on Oct 26, 2018
Merge pull request #48 from thesnat21/Update_Default_Theme 

@biblepay
biblepay committed on Oct 26, 2018
 
Commits on Oct 17, 2018
1.1.5.9c-No-Op 

@biblepay
biblepay committed on Oct 17, 2018
 
Commits on Oct 16, 2018
1.1.5.9b-No-Op 

@biblepay
biblepay committed on Oct 16, 2018
 
Commits on Oct 7, 2018
1.1.5.9-Leisure Upgrade 

@biblepay
biblepay committed on Oct 7, 2018
 
Commits on Oct 6, 2018
1.1.5.8-Leisure Upgrade 

@biblepay
biblepay committed on Oct 6, 2018
 
Commits on Oct 3, 2018
1.1.5.7d-No-Op 

@biblepay
biblepay committed on Oct 3, 2018
 
Commits on Oct 2, 2018
1.1.5.7c-No-op 

@biblepay
biblepay committed on Oct 2, 2018
 
Commits on Oct 1, 2018
1.1.5.7b-Leisure Upgrade 

@biblepay
biblepay committed on Oct 1, 2018
 
1.1.5.7-Mandatory Upgrade (at block 77000) 

@biblepay
biblepay committed on Oct 1, 2018


Commits on Oct 30, 2018
1.1.5.9e-Leisure Upgrade 

@biblepay
biblepay committed on Oct 30, 2018
 
1.1.5.9d - Leisure 

@biblepay
biblepay committed on Oct 30, 2018
 
Commits on Oct 26, 2018
Merge pull request #47 from thesnat21/Add_exec_helper 

@biblepay
biblepay committed on Oct 26, 2018
 


_____________________________________________________________________________________________________________________________________

120 hours for the month of October:
?4800/.000208
 23,076,923 bbp

Capping at 3.5 Million




24
Archived Proposals / Re-Enable Team BiblePay Requirement in PODC
« on: January 19, 2019, 04:25:52 pm »
I recommend that we hold an emergency vote that Proposes that Team BiblePay be REQUIRED to participate in PODC  rewards (in contrast to having no team requirement).

The reason for this is TheSnat has discovered that 5 Gridcoin users are sharing UTXOs by sending them back and forth to each other more than once per day.

Although we have a feature to Stop this behavior, the spork is not fully enabled in prod because it would require a mandatory upgrade (to ensure all of the remaining sancs honor this setting).

In the mean time I feel it is highly unfair to leave this activity unchecked at the expense of our core team.  (The activity is penalizing small users rewards at the expense of the bad actors).  (We estimate the ill-achieved UTXOs to be rewarding 20% of the PODC budget per day.)

Therefore I recommend that we vote in the Team Requirement to be REQUIRED again within 48 hours.

Secondly, we have been very patient, and the original idea behind Not requiring the team was that BiblePay would grow in popularity by reaching the mass of boinc users.  IMHO, it clearly has not had that effect.  What we have observed is a few very large users (I am told Turkish) have been hogging the top rewards, and we have seen stagnation.  This is actually driving away our smaller users.

Thirdly, our PODC difficulty level has not increased since we removed the team requirement, it has decreased.

In light of this I recommend the sanctuaries consider these factors to vote the way you feel would be best for the community at large.

Vote YES for us to REQUIRE TEAM BIBLEPAY to participate in PODC.

Vote NO for us to leave PODC as is and Not require a particular team.



25
Archived Proposals / Release POG Mining to Prod
« on: January 19, 2019, 04:10:00 pm »
This proposal authorizes the BiblePay Dev Team to release a mandatory upgrade that includes a change to our primary mining algorithm:

We will switch our primary heat mining algorithm to POG (Proof-of-Giving), which includes our existing POBH (proof of bible hash) heat mining algorithm, but changes the payout mechanism to use an in-wallet pool.

This means that 80% of the Heat Mined Rewards (POW) will go into the POG pool (in contrast to being given to the POW miner who mined the block).
20% of the Heat Mined Rewards (POW) will be given to the Reaper (the one who mined the block).

BiblePay POBH has an inherent 51% attack prevention mechanism called nonce-limiting that helps prevent a 51% attack.  We also have DGW (Dark Gravity Wave).

On a related side-note, in the future, we plan on implementing the 51% attack eliminator (being released in Evolution) which is technically viable since we have Sanctuaries, therefore we embrace the idea.

This proposal does not eliminate the PODC (proof-of-distributed-computing) budget - we will enter a separate proposal for that.

Specifics:
In approximately 30 days our mandatory release will enable us to go live with POG.  This proposal authorizes POG daily pool payments to go live with the characteristics outlined above.


26
Archived Proposals / Compassion Jan 2019 Recurring Orphanage Sponsorships
« on: January 19, 2019, 01:14:35 pm »
We currently sponsor 102 children at Compassion with a recurring charge of $3,876 per month.  (Approx 9.4MM BBP monthly).

I am requesting 4 million this month (to allow our other due Charity proposals to fit).

27
Archived Proposals / Cameroon One 2019 Quarter 1
« on: January 19, 2019, 12:51:34 pm »
It's time to renew our relationship with Cameroon One for the year 2019!

We currently sponsor 10 orphans through Cameroon One:
CAMEROON-BHE-CHRISTABLE   Bhe Christable   https://pool.biblepay.org/SAN/Mission/Cameroon/BheChristable.png
CAMEROON-BIH-ENCARNASIO   Bih Encarnasio   https://pool.biblepay.org/SAN/Mission/Cameroon/BihEncarnasio.jpg
CAMEROON-CHE-BRIAN   Che Brian   https://pool.biblepay.org/SAN/Mission/Cameroon/CheBrian.png
CAMEROON-CHE-SAMUEL   Che Samuel   https://pool.biblepay.org/SAN/Mission/Cameroon/CheSamuel.jpg
CAMEROON-FRU-NJI   Fru Nji   https://pool.biblepay.org/SAN/Mission/Cameroon/FruNji.jpg
CAMEROON-FUHNI-RANDY   Fuhni Randy   https://pool.biblepay.org/SAN/Mission/Cameroon/FuhniRandy.jpg
CAMEROON-MAMBO-LORA   Mambo Lora   https://pool.biblepay.org/SAN/Mission/Cameroon/MamboLora.png
CAMEROON-NDE-HARISON   Nde Harison   https://pool.biblepay.org/SAN/Mission/Cameroon/NdeHarison.png
CAMEROON-NGUM-CAROL   Ngum Carol   https://pool.biblepay.org/SAN/Mission/Cameroon/NgumCarol.png
CAMEROON-SWERI-MARYLEIN   Sweri Marylein   https://pool.biblepay.org/SAN/Mission/Cameroon/SweriMarylein.png


Our budget ran out on the last day of 2018.

I've had initial talks with Todd from Cameroon, and I must say I am extremely excited about continuing our relationship and expanding it.

I mentioned to Todd that we had a little bit of unhappiness with his competitor (our primary orphan partnership) - the organization's lack of motivation in certain areas.  Without being negative, we have met resistance when we asked if we could start an ad campaign and use the partner's logo and boilerplate message next to our primary campaign logo, also met resistance when seeking IT relationships for the creation of Orphan Mining, met resistance when asked if we could have more than one auditing report, and met resistance when asking if we could have assistance in Biblepay liquidation (to fiat).  This led me to ask Todd if Cameroon would be more flexible, and to my great pleasure, Todd has gone the extra mile for us, and promised to extend our relationship by accommodating us in many more ways (for example, working with us on IT projects, and liquidating BiblePay!).

In light of this I believe the least we can do is extend our current relationship through 2019 and not impact our Cameroon in any way.  We may even consider expanding our relationship with Cameroon, if our budget permits, at the expense of our other orphanages who do not feel like working with us.

Therefore, I am requesting that we pay Cameroon in 4 quarterly installments.  We must raise $4,000 per year, equaling $1000 per installment.

For installment one, I am requesting $1000 or 2,439,024 BBP at current rates.

Thank you!

EDIT: ! NOTE !   We are going to send the winning proposal funds directly to Todd for liquidation!  I am excited about this, as Todd as stepped up and agreed to help us decentralize BiblePay.




28
Archived Proposals / Jan 2019 IT Expenses and Payroll
« on: January 19, 2019, 12:33:54 pm »
I worked approx 120 hours in October for BiblePay on Core maintenance, Core new development, core support, and Pool support (as related to Orphan support and SQL administration).

$120 * $40hr = $4800 = 11.7MM BBP;  Capping at 3 Mil to allow other parts of the IT budget to be paid.




Commits on Oct 30, 2018
1.1.5.9e-Leisure Upgrade 

@biblepay
biblepay committed on Oct 30, 2018
 
1.1.5.9d - Leisure 

@biblepay
biblepay committed on Oct 30, 2018
 

@biblepay
biblepay committed on Oct 26, 2018
 

@biblepay
biblepay committed on Oct 26, 2018
 
@biblepay
biblepay committed on Oct 17, 2018
 

@biblepay
biblepay committed on Oct 16, 2018

Commits on Oct 14, 2018
Updating default theme in loadStyleSheet function

@biblepay
biblepay committed on Oct 7, 2018
 
Commits on Oct 6, 2018
1.1.5.8-Leisure Upgrade 

@biblepay
biblepay committed on Oct 6, 2018
 
Commits on Oct 3, 2018
1.1.5.7d-No-Op 

@biblepay
biblepay committed on Oct 3, 2018
 
Commits on Oct 2, 2018
1.1.5.7c-No-op 

@biblepay
biblepay committed on Oct 2, 2018
 
Commits on Oct 1, 2018
1.1.5.7b-Leisure Upgrade 

@biblepay
biblepay committed on Oct 1, 2018
 
1.1.5.7-Mandatory Upgrade (at block 77000) 

@biblepay
biblepay committed on Oct 1, 2018



29
Archived Proposals / Pool letter writing refill
« on: December 25, 2018, 11:21:56 am »
Im requesting 250K for letter writing rewards.

The pool has paid out more in rewards and faucet starts than received by proposals (the rest was funded by me).


30
Archived Proposals / Dec Payroll
« on: December 12, 2018, 11:09:08 am »
I am requesting some compensation for September 2018 development hours:

Commits on Sep 30, 2018
1.1.5.6c-Leisure Upgrade 

@biblepay
biblepay committed on Sep 30
 
Commits on Sep 27, 2018
1.1.5.6b-Leisure Upgrade 

@biblepay
biblepay committed on Sep 27
 
Commits on Sep 26, 2018
1.1.5.6-Leisure Upgrade (Mandatory for Sancs) 

@biblepay
biblepay committed on Sep 26
 
Commits on Sep 24, 2018
1.1.5.5d-Leisure 

@biblepay
biblepay committed on Sep 24
 
Commits on Sep 22, 2018
1.1.5.5c-Leisure Upgrade 

@biblepay
biblepay committed on Sep 22
 
1.1.5.5b-Leisure Upgrade 

@biblepay
biblepay committed on Sep 22
 
1.1.5.5-Leisure Upgrade (Mandatory for TestNet) 

@biblepay
biblepay committed on Sep 22
 
Commits on Sep 18, 2018
1.1.5.4b-Leisure 

@biblepay
biblepay committed on Sep 18
 
1.1.5.4-Leisure (Mandatory for TestNet) 

@biblepay
biblepay committed on Sep 18
 
Commits on Sep 17, 2018
1.1.5.3b-Leisure 

@biblepay
biblepay committed on Sep 17
 
Commits on Sep 16, 2018
1.1.5.3-Leisure (Mandatory for TestNet) 

@biblepay
biblepay committed on Sep 16
 
Commits on Sep 15, 2018
1.1.5.2b-Leisure 

@biblepay
biblepay committed on Sep 15
 
Merge pull request #43 from sunk818/patch-2 

@biblepay
biblepay committed on Sep 15
 
1.1.5.2-Leisure Upgrade 

@biblepay
biblepay committed on Sep 15
 
1.1.5.1-Leisure Upgrade (Mandatory for TestNet) 

@biblepay
biblepay committed on Sep 15
 
Commits on Sep 14, 2018
1.1.5.0d-Leisure Upgrade 

@biblepay
biblepay committed on Sep 14
 
1.1.5.0.c-Leisure Upgrade 

@biblepay
biblepay committed on Sep 14


Commits on Sep 13, 2018
1.1.5.0b-Leisure Upgrade 

@biblepay
biblepay committed on Sep 13
 
1.1.5.0-Leisure (Mandatory for TestNet) 

@biblepay
biblepay committed on Sep 13
 
Commits on Sep 7, 2018
1.1.4.9-Leisure Upgrade (Mandatory for Testnet) 

@biblepay
biblepay committed on Sep 7
 
Commits on Sep 2, 2018
1.1.4.8b-Leisure 

@biblepay
biblepay committed on Sep 2
 
1.1.4.8-Leisure Upgrade (Mandatory for TestNet) 

@biblepay
biblepay committed on Sep 2






I worked on BiblePay approx. 120 hours in September (primarily on creating a Business Object, an RSA keypair, and the ability to send and receive objects from IPFS).

This equals $4800 or 13MM bbp.

Capping at 2 MIL in case we have other dev proposals this month.


Pages: 1 [2] 3 4 5 6 7