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 8
1
Production Proposals / Foundation Pool Payment Method
« on: April 05, 2020, 01:01:40 PM »
Currently, foundation.biblepay.org pool keeps track of hashpower per address per block.

This means that if we havent solved a block in lets say 50 blocks, and we have 10 participants in the 50th block, (and lets say that 100 participants who are no longer hashing have dropped off 5 blocks ago), this means that the pool will only split the block reward by the TEN participants that contributed hashpower IN that last block.

But, the con to this is if we go a long period without solving a block, some miners might get frustrated when they see 0 payments for certain periods because they are not the lucky ones In the block being solved.

Should we instead consider paying all the participants who contributed from the last solved block up to the current solved block?

In that case, the entire 100+10 who contributed between blocks would all earn a percentage of the solved block.





2
Would it be useful for us to create the ability for a user with not enough collateral (to host an entire sanctuary (4.5MM)) - to instead, be able to invest in a fractional share of a sanctuary on foundation.biblepay.org?

The fractional share would pay dividends back to the hodler's based on the fraction invested.

The foundation would do this for a tiny fee (IE, probably barely more than the price of hosting).
The pro would be we could attract more outside investors into biblepay.

I believe BBP would also be able to maintain the sanctuaries, so this is  not only a turnkey hosting service but also a fractional share service.

I think if we do this we will add higher security to foundation.biblepay (2FA) and cold wallets, then I will feel better about hosting this, that is if we decide to schedule this in.

According to MNO an investor makes 45% for HODLING:
https://masternodes.online/currencies/BBP/

So if we can make this as easy - turnkey - as possible, this would be an avenue for HODLERS , or non techni grandmas, who want cryptocurrency exposure to invest where Dynamic Whale Staking failed to have the full resources available for them.



4
BiblePay discussion / RandomX Giveaway for New RandomX Miners
« on: March 23, 2020, 02:27:03 PM »
***** New RandomX Welcome Gift to onboard new RandomX Miners *****



To claim the faucet reward:

Create an account here at our forum (forum.biblepay.org).
Change your profile picture to either an avatar or your picture.
Download and sync biblepay (v1.5.0.7e+).
Click Tools | Information | Console
From the RPC console type : faucetcode
Paste the faucet code in a post here in this thread, along with your country.
(Optionally read more about biblepay and salvation at foundation.biblepay.org.)

Then, we will send you a reward of approximately 13000 bbp (at our discretion) if we deem you to be new and unique.

NOTE: You do not have to paste your reward address; the faucet code contains enough info for us to send your reward to you.

Thank you for using biblepay.




5
Pre-Proposal Discussion / Vote on your favorite future currency name:
« on: March 05, 2020, 10:00:20 PM »
Biblepay is currently designing a future feature - the ability to offer corporate whitebranding.

In the process of doing this we are also considering offering a DUAL BRAND (One channel for users that are not necessarily Christians, for a Global reach).  This other brand would be our parent company (For example, we could be known as DAC.ngo, our name being DIGITAL AUTONOMOUS CURRENCY.  This brand would still tithe 10% to orphan-charity (with the exact parameters of BiblePay and would share BiblePay's codebase and exchanges).  But we would have two tickers:  DAC & BBP pointing to the same underlying order book.  We would also have dual block explorers, dual forums, and dual branded randomx pools.

Or, you may vote for one new brand only (retiring biblepay).  This will give us an idea of the general feel as to what name feels the best, and if users generally like the idea of a dual brand.

In addition to the potential dual brand, we plan on using the new DAC identity to launch our charity-agent feature.  For example, if we become known as DAC, our DAC foundation website will host the charity agent partner pages and deals by magnitude descending, while biblepay acts as a website for gospel media and preaching and salvation, etc.  Basically the DAC arm would be more aligned with those talking about crypto while the BiblePay brand would have more gospel features and media that might turn away some types of traffic (for example hell videos, etc).  However, we could work together to make subtle inroads into the DAC side to try to save those users.

So hence one of the reasons for the dual coexisting brand.  I am also consulting with SX to seek approval for dual-exchange tickers.



6
Active Discussions / The BiblePay Foundation Web Site - BETA TESTING
« on: February 29, 2020, 12:11:58 PM »
Short Term Goals:

Expense and Revenue (Accounting reports)
Orphan collage of active orphans sponsored with clickable bios
Gospel Links / Media (Videos)
Theological articles
Prayer Blog (List of prayers that need prayed)/ Add a prayer / Prayer comments
User Account with email  - and optionally basic permissions (this is so we can notify users of a mandatory upgrade, Or, assign a user a permission-required function in the future, such as allowing a user who is responsible for adding Expenses to add an expense), but note most pages will be viewable anonymously.  User account register, edit, log in, log out.
Add blurb about mandatory upgrades to landing page/ make an actual lading page.
Site should be viewable on the mobile devices; it should also allow navigation, menus, and data entry to be possible.  Wide content and long content should not break the site.




Mid Term Goals:
Christian Dashboard:  This is a list of people you want to save.
Each person will have a status, a goal, a last step.
We will provide materials to help you achieve your goal(s) (Theological articles, illustrations, childrens cartoons, videos, etc).
We should allow each Contact to be guided through a salvation plan (IE a 10 step plan to salvation, etc).
The CRM type dashboard will summarize your ministry state, providing you a tool to become a ministry.


Long Term Goals:
Guest Pastors and Historical sermons, and pay to preach
BiblePay Charity Navigator.
This summarizes charity opportunities by magnitude descending (for our user base).  It allows outside donations to pass through to charities.
The actual design will need to be detailed in a PDF.







URL:

https://foundation.biblepay.org


NOTE: This site is still in beta, so please do not post it on our social media pages until we complete the first Prod release.


So far most of the items in "short term" have been completed - except the Christian Dashboard has not been started yet.





Test Cases for Short Term Goals (Phase 1):


- Test logging in and loggout out.  When you are logged in, you should see your e-mail address on the top right.
Note: Email addresses are not revealed to other users (they can only see your nickname).

- Test adding a prayer and viewing the prayer blog.
- Test Adding a prayer comment (IE, I'm praying for this, I feel the heartache for your family etc).  Test viewing the comments.

- Test adding an avatar to your user, and viewing the image on the blog.

- Test viewing the gospel videos, the theological articles, and the illustrations.

- Provide more landing page images, for example to replace the Lion (as ours needs replaced without the watermark etc).

- Give us any ideas to make it better.  Ideas for Christian processes are also welcome, as we want to appeal to those seeking the gospel etc.



7
Active Discussions / BIBLEPAY - RANDOMX INTEGRATION
« on: February 07, 2020, 10:28:39 AM »
RandomX Integration


Welcome to the Biblepay-RandomX Integration Testing thread.

In this thread we will be testing:
Dash 0.14.0.5 changes (these occurred between Nov 2019 and Jan 2020).  These include: https://github.com/biblepay/biblepay-evolution/commit/34851a046392e169fcfa90a0bbcd7a01e1096090 which are ddos and chainlocks enhancements.
Test BiblePay Core RandomX hashes, RandomX solo mining, RX multithread solo mining.
Test xmrig->bbpcore mining against bbpcore using RX.
Test xmrig dual-hash mining.
Test bbp->nomp pool mining.
Stress test biblepay; verify RAM utilization and reliability in running for days.
Test BBP against sancs; regression test sanctuary abilities.
Verify how many BBP memory footprints can fit on a VM.




Starting Version:    1.5.0.2+


(Please ensure your version is greater than this, otherwise your testnet branch will not sync.  We are at block  ____28050_____________ as of February 9th, 2020).
BlockHash 28189:
c6fd*****


Testnet Download Links:


Ready:
     Windows 64-bit:      https://biblepay.org/biblepayevo64develop.exe
     Linux PC 64bits Daemon:     https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz
     Linux 64 bits QT:       https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz
     MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg

     Linux 64 bits II (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip

Not ready:
(Unknown state, probably wont run due to memory constraints in the future)
       Linux ARM64 daemon: https://biblepay.org/biblepayd-evo-testnet-aarch64-linux-gnu.tar.gz


To self compile:
https://github.com/biblepay/biblepay-evolution/blob/develop/BuildBiblePay.txt
** Note above:  The instructions have changed, see the changes for randomx.  **

The ETA for MainNet for RandomX  is   April 30th, 2020.




CONFIGURING FOR TESTNET:


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: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
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

__________________________________________________________________________________________________________________________________________________________________________________________


POOLS for TESTNET (RandomX):

http://rxtest.biblepay.org


Instructions to pool mine:

Launch xmrig.exe or xmrig with these args:

xmrig-bbp-win64.exe -o rxtest.biblepay.org:3008 -u your_biblepay_testnet_address -p your_monero_prod_address --threads nproc_count

Where your bbp receive address for testnet receives Biblepay rewards, and your monero prod address receives prod rewards.


___________________________________________________________________________________________________________________________________________________________________________________________
XMRIG - The dual-hash miner for Biblepay + XMR:

To download Xmrig - binaries are here:

linux-64-bit :  https://github.com/biblepay/xmrig/raw/master/binaries/xmrig-bbp-linux64
windows-64-bit:  https://github.com/biblepay/xmrig/raw/master/binaries/bbprig.zip
(Extract the zip file to a folder on your machine, such as c:\mining\).  Run the miner from a batch file in that subdirectory (this allows the miner to use the dependencies).

To build your own xmrig:
https://github.com/biblepay/xmrig

How to mine:
xmrig-bbp-win64.exe -o rxtest.biblepay.org:3008 -u your_biblepay_testnet_address -p your_monero_prod_address --threads nproc_count
Where your bbp receive address for testnet receives Biblepay rewards, and your monero prod address receives prod rewards.

___________________________________________________________________________________________________________________________________________________________________________________________

How to get a monero production wallet, without running the full monero client (How to get an XMR address to mine to):
Since it is not allowed to mine to SX, we need to go with the next best option.
I'm sure other SPV wallets exist, but I'm currently using this one:

https://mymonero.com/

Just install it, then create a wallet.  Then use that address for your mining reward address.
NOTE:  The XMR side of the pool has a complicated payment strategy that we will explain asap.    For now know that XMR is held until the balance gets to 1xmr, but we will explain how to lower the threshhold etc.

The BiblePay payment side works the same as usual:  After the mined block matures in the pool, all the BBP is dispersed automatically.
____________________________________________________________________________________________________________________________________________________________________________________________


What is so special about XMR+BBP dual-hash mining?  What entices me as an XMR miner to mine BiblePay+XMR?


  • You get double the hashrate.  If you mined at 5,000 HPS with XMR, you will mine at 10,000 HPS with BBP+XMR.  This translates into a potential profit of almost double (minus the 10% we give to orphan-charity).
  • If you generate 1 XMR per month with XMR mining alone, you stand to generate .90 XMR + 80,000 BBP for the same amount of work (the amount of BBP is speculative, based on current rates).

How does this work, why am I earning double what I earn in XMR alone?

The way it works is when you mine XMR alone, the solution can only go to one pool because you are solving a blockheader based on the current height and time and nonce for Monero.
However, BiblePay, with RX integrated can also be solved *at the same time*.  How?  Every randomx hash is checked against our current height and difficulty, giving you one chance to win a biblepay block for every XMR hash.


Why is biblepay interested in integrating wtih XMR?

We are interested because we want more miners, because miners give us more PR.  And we want to help more orphans.  Theoretically, the more XMR miners that dual-hash-mine, the more of our 10% tithe goes to orphan-charity.  That is a win-win for us, XMR, and the orphans!

How are the payments allocated for the work I spend mining?

For every 100,000 hashes, 90,000 go toward your personal account and 10,000 toward our orphan-charity XMR address (IE we tithe 10% to orphan charity, dispersed in XMR liquidations to our charity partners).  Out of the 90,000 that go toward your personal account, every single hash has an equal chance at winning a BBP block.  On the biblepay side, we pay out 100% of the earnings to your personal BBP address (we keep no overhead, unless a pool charges a small bit of overhead, TBD).   On the orphan-charity side that we spend from our collected revenue for our foundation, our liquidated XMR is guaranteed to go 100% to our voted charity (with no overhead kept by us).  We only partner with charities who are 75%+ efficient, such as compassion.com, Cameroon-one, Kairos, etc (therefore the maximum passes through to the children in need.  You can also see our orphan collage at https://accountability.biblepay.org).

__________________________________________________________________________________________________________________________________________________________________________________________________

Hashrate comparison chart, supplied by earlzmoade, showing a 200% increase in hashrates between xmrig plain vanilla and xmrig dual mode:

https://wiki.biblepay.org/RandomX_Hashing_Speed_Comparison










8
Pre-Proposal Discussion / BiblePay Future Hash Algorithm for CPUs
« on: January 26, 2020, 10:09:36 AM »
Option 1 - POBH 3.0:  This means we would rewrite POBH (which has the 31,000 verses of the bible) in a way that would run slower in a GPU (than on a CPU) and be very unlikely to work on an ASIC in the future.  This appears to be possible by using .netcore's polymorphism, branching, and large initial required data streams.  In a nutshell it would take more work to move the inital calculated stream to a GPU than to perform the operation on the CPU.  The CPU is also the only way to execute the dotnetcore commands.

Option 2 - Math Prize:  Embed one of the worlds greatest math problems in the next algorithm, to give BBP a chance of winning the $1 mil prize, for example.  One example is the Reimann Zeta hypothesis, when calculating Zeta on the critical strip above 10 to the 30th power, these zeroes become extremely hard to calculate and elusive (the highest found is 10 to the 30th).  https://www.claymath.org/millennium-problems/riemann-hypothesis

Option 3 - Useful Work:  This option is similar to #1, in that our hash function would be in dotnetcore, but the difference is we would update the code occasionally using auto-upgrades.  And the code would perform some type of useful work; similar to what is done in boinc projects.  We would find a useful algorithm and use it until it needs upgraded (such as CFD, for instance that Togo recommended). 

Option 4 - RandomX and dual revenue streams for the miner:  The idea here is that we switch to the randomx hashing algorithm, for core wallet, pool and miner.  We add the ability to allow the miner to mine any randomX coin (we do this by querying the block-key which changes every 2048 blocks in all randomX coins, and making our hash algorithm solve for an *equation* rather than the diff level. )  This way, our miner can perform useful work that generates revenue, by mining XMR or another randomx coin, for instance.  However the difference is, every hash that is calculated in the randomX virtual machine would have a chance at solving the current BBP block also.  This would provide a dual revenue stream for the miner.  Theoretically, we would be a more enticing project for every randomx miner, simply because of the dual revenue.  This algorithm appears to not only be possible, but 95% efficient, meaning that each hash counts for both the primary randomx target (ONE only), plus BBP.  The theoretical algorithm we would use is :  X11(PrevBlockHash + CurrentRandomXHash) < DiffLevel(CurBBPBlock).  Note this is novel and unique in that our diff and block spacing can be in parallel to RandomX.  It also means the miner can mine any randomx pool or coin, and not need the Monero wallet for example (they will need the SPV wallet for the coin they mine).   


9
Production Proposals / Jan 2020 POBH and Integrity update
« on: January 19, 2020, 09:04:03 AM »
This proposal seeks authorization to make the changes necessary to release an emergency update to fix POBH.  As it was recently reported that Marcino ported POBH into a GPU.

This proposal seeks to change and clarify the following items:

- We will add a nonce limit for POBH hashing to limit the hasher to 256 hashes per second per miner.  This can be enforced, because the block start time is known in a hard way, and the last block time is known in a hard way.  Additionally, we enforce that the only field the miner can change is the nonce and start timestamp, and any other field that is changed results in a new block being created (and this requires many calculations for chainlocks, llmq, transaction lists, and recalculation of the merkleroot). 
    *** NOTE :  We will not limit CPU mining to 256 HPS, however.  When the miner is faster, the miner will create more blocks per minute.   Automatically.  ***
- It is a given that recalculating the merkle root requires more work than calculating more POBH hashes.
- Therefore the conclusion is that this interim release will remove the GPU risk from our POBH algorithm.
- We will still work on the next generation miner after this release, therefore this is a temporary stopgap for POBH to keep it running in a quality fashion.
- We seek to    shore up our emission deflation rate to match the target emission as of Dec 2020 (http://wiki.biblepay.org/Emission_Schedule).  This means we will for the time being increase our deflation rate to .0216 aiming to match the year end emission target.  We will monitor the situation afterwards and if necessary put it back to .0167 when the target is met (in a future mandatory).  In summary we are increasing our deflation rate to ensure we emit the exact proper amount of coins in total from inception until Dec 2020. 
- We seek to fix DWS.  This requires two changes:  At the mandatory cutover height, installing new rules that increase the sensitivity of the DWU reward.  This first change ensures that as burns take place, the wallet decreases the DWU quicker (saving more of the kitty for the next user).  Additionally we seek to reduce the maximum DWU to 35% of the original design (making more available to each individual user).  To accomplish this we must also adjust the DWS emissions to match the target emission schedule (4mm per month deflating starting in 2020).  The good news is DWS phase 1 had too low of an emission set-up so this is not really an issue - it means correcting the parameter to the intended value.
We will monitor DWS emissions - and ensure globally, DWS does not materially change the total emission schedule picture.  The goal is to flush out DWS phase 1 payments, allow Phase 2 to be established and ensure all factors are correct at the end of this year - and if necessary adjust the final DWS emissions level in the Sept-Dec 2020 mandatory to match our global emission schedule and DWS schedule as outlined in the prior point.
- Update the investors on the total orphan portfolio along with what is available at compassion.  Since we technically still have compassion funds, we are still above 100 orphans per month; but we need to be clearer.
- Clarify our stance on what the DAC and Biblepay charity agent proposal is, and that it is not expected to effect our charity emission level.  Clarify that our charity emission level target is still, and is expected to be 10% per month.  Clarify the complete idea - to explain that we do not veer from launch params and
 how we seek to continually work in integrity.




 
      

10
Pre-Proposal Discussion / BiblePay as a Global Charity Agent
« on: January 14, 2020, 05:52:10 PM »
This is an idea for a real world use-case for BiblePay.  Continuing the discussion on 'dimensions of a crypto' we have established that (https://wiki.biblepay.org/Dimensions) (if given 3 dimensions: Mining,  Innovation, real-world-use-cases), we score high on Mining (PODC), high on Innovation (Dashpay etc), and low on real-world use cases.

This idea involves either being a charity broker, or a charity agent.  Similar to the way a transistor works, we would 'enable' a charitable transaction - also by providing a reward back to the donor.  This would be the reason a donor would choose BBP over going directly to the charity.

Why would BBP be favorable?  We could constantly aggregate charities providing the 'best deal' in a web resource constantly updated.  For instance, lets say Korean orphans are in desperate need, and the orphanage offers a 30% discount.  Or, if we have matching funds available.  And, with corporate matches, and partnerships we may create a partnership discount.  Also we have platform fees charged by the big leagues (9%) plus transaction fees (3%), and all of this adds up to a huge amount of overhead.  The big leagues pay serious money to vet charities.  We can leverage this by downloading charity research for vetted orgs, and keep this in the folder for the org, and only partner with vetted orgs.  This will also save BBP all of the expenses (in vetting) - if we require pre-vetted orgs vetted by third parties with recent reports.

Looking at Charity, this is a huge untapped market in global finance.  We are obviously not tapped in any way, as the American charity donations are $390 billion annually, and global cause is over a trillion $.    Therefore this is a real world endeavor, so lets set our sights higher.

Let us create use cases for this feature.

In the current scenario (POOM), we match a miner with a charity.  Currently, we spend 10% of our blockchain emissions on charity.  But, we don't attempt to negotiate any discount with our charities, we spend the retail amount ($40 per child).  And this is technically not what I'm suggesting (I do not want to slim down the profit), I simply want to create a competitive market.  What we can do is ask each new charity partner as they are vetted, to offer us a  5-10% networking fee to be approved for the account - this would end up resulting in pooled rewards for the donor  (see below) - let us call this "Discount appeal A".

Next, there are many, many examples in the corporate world of companies that match employee donations.  Sometimes 2, 3, 4 or 5* the match is available.  We need to reach out for a pilot company, and design a flow that would allow an employee to sponsor a child, and facilitate the match. 

Next, there are real world examples - constant examples of 'matched funds' available at companies such as globalgiving.  I myself have sponsored over 10 kids last year with a match (that helped 20 kids), and, once through CARE, utilized the match of a NYC donor to double my CARE contribution.  We need to locate and partner with the match.  We can use the Match funds to offer a discount on the 'available charity for donation list' page - and this will be very enticing when a user is deciding to give through us (to see a 50% match, or 50% discount on the list).

Next, there is a platform fee of roughly 8%-9% charged by companies like GlobalGiving (and also a 3% network processing fee), for every donation!  This is huge.  (https://www.globalgiving.org/aboutus/fee/) .  This means $1000 given through globalgiving actually is reduced by 12% ($120) for a net receipt to the charity of 880$!  This point is one of the biggest points here.  This means, we can appeal directly to a vetted charity, receive a network-fee discount in our negotiation of new partnership (from point A above) - to broker the transaction.

This 5-10% total discount would entice the user to give through us (instead of going through globalgiving).  Because when we list each row, we will list the BBP reward available.  Then, we give the donor a refund in BBP, at the applicable % negotiated (creating a competetitive environment for new givers).
This gives the user 3 reasons to choose us :  Donating to causes with matches, donating with programs with discounts, bbp-reward back.

Real World Example:

We partner with Cameroon-One, Compassion, and Korean-Children Institute.  Cameroon-One negotiates a 5% discount with us, Compassion 5%, and Korean 10%.  This means right off the bat, Cameroon-One drops to $38 per child (because they are looking for partnershps and quantity), while if you go directly through cameroon, you pay $40. 

Next, we locate a charitable match partner (IE the same one globalgiving uses in NY).  They usually offer a match to the 501c3 for proof of a donation.  Then we apply this to our advertising page:

Cameroon-one     $38        With Match $19.00     
Compassion           $36         With Match $18.00

Note that what would happen is an inbound donor would choose an amount of the donation, say $380, and pick Cameroon-One.
We would automatically apply the match, and donate $760 to cameroon-one.  However, cameroon-one would pay a network fee of 5% (or $38) and this would go back to the donor in the form of BBP (not fiat).  Additionally, we could also pay a percentage of our charity budget for this transaction as an additional reward (of between 1-10% see chart based on price), however this additional reward would be capped at no more than 1% per donation of our total budget (IE if we have $2000 available, only a max of $20 could be paid in this additional bonus).  So lets say the BBP price is still on the chart level where 2% is being paid for rewards, then $15.60 additional in BBP would be added.   So this donor would receive $15.60+$39=$54.60 reward in the form of BBP (our coin would not keep the profit).  A random sanctuary would facilitate the transaction (IE document it and enter it in and execute it).  This would also be tax deductible, as the payments would go directly from the donor to the charity, and BBP would extract proof-of-transaction, and save the data so we can give real world credit for this on our web site etc.


Proposed Price breaks table :
BBP Price                   Charitable Expense Amount (And Governance emission amount)
.01+                             10% to charity (100% from superblock)
.005                              7% to charity (70% of superblock)
.001                             5% to charity (50% of superblock)
.0005                           2.5% charity (25% of superblock)
.0001                           1% to charity (10% of our superblock is emitted)

This table can be refined later, but it shows that we start to limit our payroll, IT expenses, superblock payments, and charity payments down to the governed table emission level while our price is low.  So only 2.5% goes to charity while our price is .0005.  However, we give the full 10% after our price exceeds .01.

So, as a bridge for POOM if we did this, we would sign up partners well in advance, negotiate deals, test in testnet, then we would want to convert POOM back over to donor->charity individual transactions; IE children would be removed from POOM, but left in the hands of the current sponsors for individual transitioning.  The hope would be during the go live we would have at least one match available to make this transition easier (as then the price would be lower to continue those children).

Note that I feel that if we did all this we would also need a 'legacy' page for classic type orphan charity, like we had in the beginning.  For example suppose we have half of our budget available.  We could by default, allow a user to sponsor an ongoing child for N months with no hassle.  So we would have both transaction lists of agent assisted transactions and lists of sponsored orphans sourced from our overflow funds.

Im thinking we would break out the fiat / crypto into two distinct services and offer both.
Fiat transactions would work like stated above.

But we should have a "donate" process for Crypto also.
We could pilot that with our orgs that already accept crypto (as it would get very tricky to make a crypto gateway available and force a sanctuary to liquidate funds, or lose their santuary if they did not perform).

Let me show an example:

Lets assume out of 10 charities, 5 will accept BBP+BTC.  We mark these 5 as crypto enabled.
We would want the transaction to be sent from the donor directly to the charity in crypto.
Then the charity would as usual send the network fee later back to us to disperse to our user.

What I'm wondering is, will this be used by the world if we make a brand new dedicated web site for this?

I'm a little more optimistic about this than some of our previous ideas.

Additionally, this entire idea seems to completely remove sell pressure from us as a coin.
All donor payments go directly to our charities in gross dollars, they receive a fat discount back for doing it.

The donations are tax deductible because they send To 501c3 enable charities.

One interesting thing that might happen in the case of a rich donor who has $1 billion to spend, lets say Trump decides to give $1 million to Cameroon-One.
This would cause Cameroon-One to send $50,000 in BBP back to Trump.  This is interesting because they would need to buy the bbp to send it.  Our governance emission would be $20 for this tx. 



Edit:  Another element I want to add, is ensuring our emission schedule completely matches our
target schedule here:
https://wiki.biblepay.org/Emission_Schedule
So what this means is I propose we tweak our internal deflation rate target to exactly match the Dec 2020
 target emission amount.  This is not a lot, or a major change to the deflation % level, but we have emitted about 100 million extra coins as of the current date and I feel we should shore this up for our Q3 2020 mandatory - we would end up increasing the deflation from 20.04% to something like 21% for example (after running the calculation).


And finally on an unrelated note, I will need to add a different thread for this subject:  Slightly modifying the POBH internal miner.  Things are pretty good right now.  But I believe God wants it perfect (the issue I have with this is "fair weights and balances").  I dont like how we ended up with a 75% mining speed for the solo miners in the core wallet and an increase in speed in the external miner.  So, I will open a separate thread to discuss this.  I mention it because it could be hampering our heavenly backing.  So that makes it important...

And finally one more point I forgot to mention: Globalgiving.  According to their financials they are bringing in $400 million per year of donations (and charging 8% fees on those, to handle those).  What we would do is analyze the top 100 charities, create folders and vet them, and then go to make deals with them, for discounts (this is the amount in BBP the reward will be for).  Then we expose them on a new web site ranked by the deal.  Then we make Donate buttons for our donors.  Then we add the sanc facilitation process.  And the refund process.  And the matching donor partnership and deal and flow.  And in the end the hopes would be browsers from the real world would flow over to us because they stand to gain a rebate of 6% if they give through BBP, and they get to accumulate BBP (crypto exposure).




11
Production Proposals / 1 MILLION BIBLEPAY PODC GIVEAWAY
« on: January 01, 2020, 08:16:10 PM »
** 1 Million BiblePay PODC Giveaway **


Terms and conditions:

- You must be an existing PODC researcher, in the biblepay leaderboard as of January 31st, 2020
- You must be contributing to research in World Community Grid
- You must have more than 100 RAC (recent average credit)

Mechanics of picking the winner:
- At block height 173307 we will take the first 4 hex-characters of the blockhash,  equaling 1-65535 (A).  Let B = 65535 / (count of superblock researchers in the prior superblock).  Let C = A / B.  C equals the (ordinal of) the winner (by counting from left to right through the last GSC contract prior to 173307, which was block 173245).


Technical considerations on choosing the winner:

Run this in vb6:

Code: [Select]

Private Sub PODCWinner()
'bbp podc winner
Height = 173307
sblockhash = "ec57a81e053ce1e61b299d4c0168c56d7c0214f817af30b35ddf8ad675209a0f"
C = CLng("&HEC57")
'last gsc transaction before 173307:
'getrawtransaction 0841a3066395229b7c0b2aae6b06f35c57a0df6ddc602ed5919a2c155f783ede 1
SuperBlockCount = 56 'researcher count minus pow miner tx minus sanctuary tx
B = 65535 / SuperBlockCount
A = CInt(C / B)
VOUT = A + 1 'First vout *after* pow and sanctuary - (Note, if we land on a CPID with < 100 RAC, we will move to the next payable ordinal - even if we need to reset the counter from the beginning).
'(This is to discourage people from making fake cpids to get votes)
'Winner = #52 (1 before Rob) : BQWhLA82SxL8PW5LGnwKj8qeog3k3JETBZ (who had a 661.69 reward at height 173245)
End Sub



12
Archived Proposals / Nov 2019 payroll
« on: December 20, 2019, 07:02:46 PM »
Program PODC 2.0.
Program Kairos integration.
Fix bugs in new development in testnet branch.

Commits on Dec 8, 2019
BiblePay

@biblepay
biblepay committed 12 days ago
 
Commits on Nov 30, 2019
BiblePay

@biblepay
biblepay committed 20 days ago
 
Commits on Nov 27, 2019
1.4.8.2 - BiblePay

@biblepay
biblepay committed 23 days ago
 
Commits on Nov 24, 2019
BiblePay - TestNet

@biblepay
biblepay committed 26 days ago


Commits on Nov 23, 2019
BiblePay

@biblepay
biblepay committed 27 days ago
 
Commits on Nov 21, 2019
1.4.7.8c-Mandatory Upgrade for TestNet

@biblepay
biblepay committed 29 days ago
 
1.4.7.8b-Mandatory Upgrade for Entire TestNet

@biblepay
biblepay committed 29 days ago
 
BiblePay

@biblepay
biblepay committed 29 days ago
 
[v0.14.0.x] Update release notes with change log (dashpay#3213)

 
Merge pull request dashpay#3202 from codablock/pr_v14_backports
 
Commits on Nov 20, 2019
1.4.7.7 - Mandatory Upgrade for TestNet

@biblepay
biblepay committed on Nov 20
 
BiblePay - TestNet

@biblepay
biblepay committed on Nov 20
 


Capping @ 3mil due to our low price.


13
Archived Proposals / Kairos Childrens Fund Recurring charges Nov 2019
« on: November 30, 2019, 07:49:50 PM »
11B   Helena NARCISO   1 - EL   $20
14B   Princess CABUGNASAN   4 - EL   $20
12B   Tajana Veroso   5 - EL   $20
13B  Pepe Gabriel   12 - SHS   $25
16B   Earl Darren Chiu   5 - EL   $20
Rowena Paladar   11 - SHS   $25
12B   Dante Balansag   10 - HS   $23
10B   Jovelyn Cadusale   11 - SHS   $25
17B   Kate Rebutazo   10 - HS   $25
      $203


Andy is requesting 1,201,283 bbp to pay 9 of our children up (out of 21) to the end of 2019.

Our total portfolio contains these children at $20-$25 per month:

Eda Mae Omotong
Shane Marie Francisco
Wendy Domik
Rhyejiam Cielo Alqiza
Brent Aaron Cresencio
John Gabriel
Jill Jangin
Ruth Alos
Jacious Amil
Kate Rebutazo
Genevieve Umba
John Rendal
HELENA-NARCISO
DANTE-BALANSAG
PEPE-GABRIEL
PRINCESS-CABUGNASAN
ROWENA-PALADAR
KENT-SUAN
ANGEL-OZOA
JOVILYN-CABUSALE
MARKKIS-UMBA


Requesting 1.201MM from the foundation to pay Andy during the non-POOM to POOM bridge era.


14
Production Proposals / PODC TEAM REQUIREMENTS
« on: November 22, 2019, 11:51:35 AM »
I believe this poll is relatively self explanatory  :o , but please ask any questions if I missed something.

Thank you for voting!


15
Archived Proposals / Payroll Nov 2019
« on: November 19, 2019, 10:18:52 AM »

MainNet commits:

Commits on Nov 1, 2019
1.4.5.2-Leisure Upgrade

@biblepay
biblepay committed 18 days ago
 
Commits on Oct 30, 2019
1.4.5.1c-Leisure Upgrade

@biblepay
biblepay committed 20 days ago
 
Commits on Oct 24, 2019
1.4.5.1b-Leisure Upgrade

@biblepay
biblepay committed 26 days ago
 
Commits on Oct 23, 2019
1.4.5.1-Leisure Upgrade

@biblepay
biblepay committed 27 days ago
 
Commits on Oct 21, 2019
1.4.5.0d-Leisure Upgrade

@biblepay
biblepay committed 29 days ago
 
1.4.5.0c-Leisure Upgrade

@biblepay
biblepay committed 29 days ago
 
Commits on Oct 14, 2019
Merge pull request #22 from sunk818/patch-1

@biblepay
biblepay committed on Oct 14
 
Merge pull request #23 from sunk818/patch-2

@biblepay
biblepay committed on Oct 14
 
Commits on Oct 11, 2019
1.4.5.0b - Leisure Upgrade

@biblepay
biblepay committed on Oct 11
 
1.4.5.0-Leisure Upgrade

@biblepay
biblepay committed on Oct 11

Also I worked on NOMP for 60 hours this month.



Capping @ 3 mil due to budget constraints.


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