Upgraded to v1.1.5.2, Masternode Enabled, ipfs daemon running
=
I tested adding a Contact:
Contacts >> Contact Add
Filled in info, Clicked Save Record, A Popup came up, but not sure what it says
In my transactions I saw that a transaction happened with the Funding Address, -1.0001 BBP
Typing command "exec bolist contact", I see my contact object in the list!
I tested 'exec bosearch contact email [email protected]', works!
I searched for [email protected] as well, also worked
I ran 'exec emailbbp [email protected] 5' and 5 BBP was sent!
References:
https://forum.biblepay.org/index.php?topic=244.msg4313#msg4313
https://forum.biblepay.org/index.php?topic=244.msg4316#msg4316
Great progress! Thats an interesting pop-up. Can you try again and see if its expandable - or if it reproduces the same behavior twice?
Yes, I see you in the list, I received your BBP and sent you back something like 10.2 bbp this morning, thanks.
BTW guys, these contacts are stored in IPFS, not in the chain. Its interesting.. Kind of wild that we are creating a front end business system here.
And Jaap, I got your bbp also, great! I sent 10.15 or so back. (Via e-mail address).
So I was thinking, I fear starting with a disruptive mandatory where we *require* the sancs to all run IPFS so quickly (with all these other features at the same time). Im thinking we phase the IPFS requirement in slowly, maybe we create another type of business object, and make it optional to run IPFS (so that we have 10 or so nodes running in prod). Then we vote on potentially requiring IPFS after the next mandatory is out, and possibly requiring it if that vote passes. But I do want to pull off some high-end features during this next release: Contact add/edit, Gospel links, IPFS attachments, Fork Fix, etc.
I am considering that we make a really extensible feature for the next mandatory release: a user configurable business object. I believe we will start with Gospel Links, and make add/edit/view/list pages, and enter in all the gospel links we have in the pool. Id like to make it so we can store the actual Christian Video content in IPFS (so if the internet is down, and Christians are in a camp together they can pull the videos off of the local IPFS laptop). In baby step 1, we can upload the links as-is. In baby step 2, we can make a YouTube -> IPFS converter. (So for our Great Trib feature, User A who runs a cloud VMS would not stream to the Christian camp, but User B who runs IPFS on a laptop would have the video content in the event the net was down).
In other respects, I found a bug in 1.1.5.2 in QT. The great news is: QT was *starting* to work today. The Sancs decided on the price, decided we were in phase 1, emitted a contract, the core wallets found it, honored it-but the bug prevented the block from being mined. So we will all need to upgrade to 1.1.5.3 next- it should be out shortly. Note that I believe the chain will roll back 100 blocks or so, as it finds some bad testnet blocks mined at the higher non-qt adjusted subsidy. This will be normal, the chain should recover, and we should revert to qt phase 1.
