God bless you all and I hope you all had an excellent Thanksgiving!
So I'm getting excited about BiblePay again, especially since we are a small community with immense growth potential.
The thing I'm excited about in our future, is how we can fulfill an on-demand use case and therefore be a useful service to the world (and to God's Kingdom).
Although I firmly believe the DAC idea (this is, the global donation address that automatically allocated funds to orphans even if our core members die, and allows our Sanctuaries to govern our charity relationships) is a good one alone, I am receiving more use cases (all credit to God) that I believe are not only possible, but probable for us.
Although BiblePay TV on Roku is also good, and I think we can keep that going in the background, I'm going to focus on some things next (in parallel to the DAC) for our next release.
Think of these features that fill two missions : battling internet censorship, and providing emergency communication during the Tribulation. (We could possibly name the release BiblePay Tribulation).
First we will start with an anonymous user record. We need to bring back anonymity to make everyone understand that we dont want to collect personal information. However we can still have an anonymous type user record for this feature - this is a UI page in the wallet that contains: CPK, NickName, Longitude, Latitude, RSA public key, optional external email address, and Optional testimony notes. The purpose of this record is for the great trib. (Note the reason for Long & Lat is to let the user synthesize their nearest street corner on a map, but not their exact address).
Imagine if the internet becomes so censored that DNS addresses are being blacklisted. Then imagine that bitcoin and biblepay ports are UP, but videos and general chat messages and social media are all monitored.
I imagine that direct DM (direct messaging) through the wallet would be valulable again: Again notice this distinction: Ability to send money from user-user, PM each user, or PM a chatroom, would all be valuable in the great trib if the wallet connection is up and parts of the internet are down. Say John Doe wants to find Robs Christian camp, or wants to send $10 to Jane Doe via BBP. This would become very valuable.
The other thing is Id like to do is integrate E-mail into BBP. Im thinking of both internal and external POP3 email. For one, people can pay BiblePay fees to send an e-mail On-chain, and/or addl fees to send e-mails through our network off-chain (for attachments). Im thinking of this use case: If John Doe wants to E-mail Jane Doe and they want to use the BIBLEPAY chain, this person can pay 100 bbp (or whatever per KB) to send an on-chain email. We also need to make encrypted email receipts with BBP cash attached. This cash can only be opened by the recipient. (Also, Im working on multisig transactions for e-mail. This allows you to seize back your BBP if it is never claimed. BBP will have commands to automatically send 1-of-2 multisig transactions in the next testnet release. We just need to add these to e-mails. The use case is also good for marketing: Those non-opened marketing emails can be re-claimed, and BBP recovered by the marketer).
We will also be rolling out RSA keys for each user, and these public keys will also be stored in the user record. This will allow Encrypted DMs and encrypted emails. Note that the data stored in the chain cannot be read by ANYONE except the recipient! Whats nice about encrypted DM, is we will be able to leap along with the signal protocol (with all of the features of signal-dm), and do more than they can do, simply because you will not need a keyexchange or a trusted third party.
Let me explain the advantage of BBP DM with RSA over Signal: If HTTPS is hacked (and some sources claim there is a prism that does that), you are trusting either discord, google, 3rd party eavesdroppers with the text up to the point of Signal encryption, then it is theretically safe until it reaches the end user. With Biblepays RSA encryption, your biblepaycore client will encrypt the traffic with RSA before it leaves your screen (before it hits the network or the chain), therefore your conversation or email will be unhackable (to the extent of the 2048 bit key etc). This will be a huge feature if we can actually market its use case properly. It will also be easier to use- you can just pick a biblepay nickname (those are stored in the user record page) and either send an e-mail or a DM (encrypted). Each of us will all have an RSA keypair associated with our user record.
Exciting times!
EDIT:
PS: I forgot to mention, I realize DWS is a great feature and is under demand and needs streamlined to make it available all the time. Im working on streamlining it for our next release to set a floor - fixing sensitivity and making it for all intents and purposes to be available at a minimum of .05-DWU -- so that people are not turned away. Also increasing the max burn amount from 1MM to 2MM with a higher daily cap to cover more funds per burn, etc.
4400 BBP
