We finally have a real world use case for BiblePay coming in the very near future. It looks like the features will be in testnet within 30 days at this point.
Users will be able to host their files in multiple regions (IE with a selectable level of storage density from 1 through 4), for a selected duration (30 to 365 days) and we will support both small and large files. We can now store long videos that are over 100 megabytes, and our hosting is compatible with HTML5 video tags (so yes, you can write an entire web site using BBP assets). Side note: This storage is not a joke either: The system will be so resilient that we can back the data with real SLAs and guarantees of quality.
One other feature I am working on releasing first (so that it is part of this next release) is the encrypted option. We will allow the user to encrypt data before it leaves their machine - then they can not only host public assets, but also private assets. We will also offer an alternative to FTP for corporations who need EDIs. This solution already works with a high degree of compatibility to SFTP, therefore we will be able to offer an alternative to SFTP. For example, lets say IBM wants to transfer a morning file to Microsoft at 8AM, they can do it over the BiblePay IPFS encrypted solution and help support orphans at the same time (and cheaper than setting up an SFTP server for one particular integration, etc).
We also have a c# version of BIPFS coming out in September. This allows c# developers to send files through biblepay without using the c++ wallet.
Therefore, a user can either: Send a file through the c++ wallet and automatically pay the storage fee (and we do have a dry-run quote), and the file is sent through c++, or they may download our c# opensource solution, and add a charge key (this allows their BBP wallet to be debited when they send a file). Either way, the file will contain the same storage parameters and quality levels.
I am also working on one suggestion I received from Ely: that if we offered an easier to use Dynamic Whale Stake option, more people might burn whale stakes. In response to this, I'm adding a method to the biblepay-QT wallet to invest BBP for 90 days (without going to the command line) from the UI. The user will click "Dynamic Whale Stake" (and the default will be 90 day duration), they type the amount to burn, and click Send (this is similar to donating to the foundation).
On a different note I was thinking back about comparison of this project from the beginning til now, from God's perspective. I believe that this project is much more aligned with God's true purposes now than where we were in the beginning.
Finally, comparing BBP to Bitcoin: To mine bitcoin, you have to use an ASIC and you compete with a farm of mining monopolies who have more money and more machines in a smaller number of hands than you. With BBP, you use commodity PCs with RandomX, and each individual has their own stake. With BBP, our charity is raised in two revenue streams: XMR, and by contributing sanctuaries. Our charity expenses are no longer being spent right out of the coinbase (or from the governance budget). This will lower the impact of sales pressure. We have PODC (cancer mining), so half of our electricity is spent for good use, and the other half is merge-mined (meaning we dont have to spend the entire electricity cost from BBPs pocket). Our only deficiency is in Mobilizing our use case so we become a usable currency. This is the primary advantage bitcoin has over BiblePay.
