Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 48. (Read 243376 times)

Upgrade works fine. The expectation from the previous communication about 1.4.8.4 was that 1.4.5.3 should work until the mandatory cutover block height. This doesn't seem to the case. Its not a big deal because the cutover height will arrive shortly, but it'd be nice to help wallet users plan better.

Great news on WCG and Kairos. Let me know when Kairos is enabled. I'll be out of town, but will try to configure ASAP.

Merry Christmas to you and everyone else reading this post.

I didn't upgrade my sanctuaries yet, and it seems that they are on a lower blockheight than my upgraded wallets. Will upgrade now.

Can you please try upgrading next?  Ive already upgraded my sancs and home node, and the exchanges have upgraded, so at this point it would be counterproductive for me to downgrade just to see if they are on a fork.  We can ask others, if anyone else is running the old version if they are going on a fork?

Whats very possible is that once 51% of the sancs moved to the new version (70750), it probably became the defacto.  You can see if your 'exec health' disagrees on the old version with the new version, but I just recommend upgrading now.

Btw, I plan on enabling Kairos later today, so please watch so we can start sponsoring after that.  As I feel we will have a lot to do starting tomorrow to roll out WCG.  I plan on enabling WCG tomorrow.

Yeah, it seems like one of the exciting ones.  It sort of Trumps some of the things Ive been working on (trying to integrate with the best buy API).

Give me a little time to try to explain the IX to IX conversion.  I'm going to work on this next.

Also, I've got to share the idea about becoming a decentralized online church.

I've been away and still running 1484. I saw that my wallet had a lot of mined blocks and these warnings saying blocks have unexpected version, bad lexical cast, and block heights that do not match explorer.biblepay.org nor chainz. I'm about 15 blocks behind.

I had 20 blocks that were found on the wrong chain: http://sunpool.whitewalr.us/tbs

The difficulty has been under 100k recently as far I can tell.

Apparently, there's been a spike of orphans lately too.




2019-12-22 20:20:28 {PNB}: ACC  UpdateTip: new best=255568dadbe9913d94e18fa4378adc773d35643a4fbd7166877339cc02c04925 height=165102 version=0x20000000 log2_work=60.05644645 tx=1186215 date='2019-12-22 20:08:47' progress=0.999994 cache=0.0MiB(0txo) warning='4 of last 100 blocks have unexpected version'
2019-12-22 20:20:29 {PNB}: ACC  caught cdbl bad lexical cast 1 from with 0.000000UpdateTip: new best=ce781a158c37e79d86340d70923030bedda334b57ffa80c7b1d55e51549d02ed height=165103 version=0x20000000 log2_work=60.05644873 tx=1186217 date='2019-12-22 20:22:47' progress=0.999999 cache=0.0MiB(0txo) warning='3 of last 100 blocks have unexpected version'
2019-12-22 20:23:48 {PNB}: ACC  caught cdbl bad lexical cast 1 from with 0.000000Misbehaving: 45.76.120.35:40000 peer=17 (0 -> 1)
2019-12-22 20:19:12 ERROR: ConnectBlock(): ProcessSpecialTxsInBlock for block 81e8883fdb4c065ff6c6de64e169fa0730e8b15d3e3c7dc2988939cdbeab82bd failed with bad-qc-invalid-null (code 16)

** Solid Use-Case - Dash IX through BBP IX **

So, I stumbled across this site yesterday:  https://www.bitrefill.com/
They had high reviews from Dash, from people who were buying digital gift cards (these are sent directly to your e-mail box, and then you can buy whatever you want once you have that).

So, the idea here is the Dash, with its millions of $ of integration already completed, already has a massive amount of support in almost every area, buying gift cards, physical products, delivering physical products etc.  

In light of that, our most straightforward and useful feature would be a method to instantly send a DASH instantsend transaction to a recipient from the BBP wallet (using BBP funds via instantsend).

It would work like this.  Take bitrefill for example, they sell an amazon $20 gift card that is delivered in 1 minute to your email address.  You browse, and buy it and select "Dash" as the payment method.  A screen appears asking to send DASH to the DASH receive address.  At this point you have 15 mins to get into dash and send the funds.  Once you send the funds, the e-delivery occurs within 1 minute to your inbox.

So what we want to do, is provide an rpc command, something like "dashpay receiveaddress amount".  What we will do is send the amount in DASH to the DASH receive address, via instant send.   (The command will return a DASH transactionID.  Then you can track the transactionid (If necessary) via the Dash BX).    Theoretically, this would allow any BBP user to make an instant purchase and then we would be instantly as useful as dash.  Of crouse, we will need to put an initial limit on this for safety (IE $25 per transaction).  I believe this is theoretically possible, using instantsend, by requiring a lock on the transaction from a masternode.  (IE we can safely relay the funds out to the recipient, and not worry about a double spend, as long as our advanced checks pass - etc).

Ill look into this feature next.  This sounds like it would theoretically plug most of the hole in BBP's dimension doc.  We can consider Dash our big brother.  

Ok, Childrens inbound letters have been migrated to:

https://web.biblepay.org

Orphans | Orphan Inbound Letters

As usual, you can also search by typing a phrase in the upper right search box.

Looking at the Mandatory upgrade post, the cutover height is not until 166075.

I mentioned the other day that we would be adding the orphan list and orphan collage to dsql (the post is missing on bitcointalk).

We have added the orphan list and orphan collage to DSQL.
We also added SEO to DSQL.

Therefore google can now spider DSQL.

Once we see this in the google cache, then we can test to see if our traffic increases.

** The integrity of Biblepay has always been in good standing **


We have receive 2,742 pages of inbound letters, written by our sponsored children to BIBLEPAY.

Obviously, anyone who has ever accused us of sponsoring false children is a false accuser.

In the spirit of providing transparency I will migrate all these letters over to BMS next so we can quickly leaf through them.  And of course, I don't want us to lose these precious letters that took time for each child to write.

Another way to 'provably' complete the equation that we sponsored a child for N duration is to tie the inbound letter to the hex-id code and randomly check for a childs inbound letter in the future.

Yeah, diff is still 177,000.

I don't see any signs of it.

** BIBLEPAY DIMENSIONS **

This is one area I feel we will need to spearhead a new project to dedicate ourselves to finding the 'solid use case' for BiblePay, to achieve a 100% score on the first dimension:

https://wiki.biblepay.org/Dimensions


I'm now in the process of creating a new Use cases document and an online Todo list.  The Todo list simply shows items dynamically that IT is working on - things that are happening that didn't fit the github list.  

The Use Cases list will attempt to show all of the potential paths, but of course some will be blocked due to impossible challenges, resource availability, and partner failures.  But I am confident that we will zero in on some excellent ones that will not only be possible but will be become a reality for BiblePay.  

Thanks, I also noticed those matrices were valuable in conveying complicated gospel topics, especially where they are debatable.
I made one recently for the Rapture, which I haven't posted yet:

https://wiki.biblepay.org/Rapture_Study

Notice how much clarity you can add when you balance the viewpoint either way. 


I will circle back and edit the Nutritional Guide asap with our new features, but first I promised to release information on:  BiblePay dimensions, todo list, use-cases and short-term goals (BestBuy and Direct Mail and greeting cards, direct mail letters from the rpc, etc).

Nice!  This explains a lot to the user.

Andy sent these pics and videos over (of the Christmas Party):

https://pool.biblepay.org/SAN/Mission/Kairos/Kairos1/20191218_151157.mp4
https://pool.biblepay.org/SAN/Mission/Kairos/Kairos1/20191218_152409.jpg
https://pool.biblepay.org/SAN/Mission/Kairos/Kairos1/20191218_153433.jpg

She has us on the projector at the conference!?  Thats very cool.

I'm glad to see what we're doing is not in vain.

God has a master plan....

Thanks, yeah, we need to write a tool to do this because the votes would take years.

A user in discord asked what makes BiblePay unique,
I did my best to try to answer him, and that led me to wanting to write an article about it

This is my draft for the questions, What is BiblePay? and What makes BiblePay unique?
https://pastebin.com/LM2DgK6H

Any and all feedback welcome!

=

The goal is for someone just sort of browsing us, without having to dig in too much, figure our our selling points

Rob your Nutritional Information wiki is a fantastic resource for this, it really does already answer the uniqueness question, in amazing detail!

https://wiki.biblepay.org/Nutrition_Information

I found a tweet where we got mentioned by a PhD Computer Scientist at an ACM conference in London
https://twitter.com/Maryammjd/status/1193931668136103937

SSR'19: The 5th Conference on Security Standardisation Research
https://dl.acm.org/citation.cfm?id=3353551

I made my last few changes and published the article
https://medium.com/biblepay-news/biblepay-q4-updates-2019-october-november-december-ef80085d4b27

Please let me know any edits that need to be made if you find any, and any feedback

(I think Im missing the DSQL Web / Christian Treasure Trove work, how do I word it?)

UPDATE: Sending wordpress website newsletter now!

UPDATE 2: Forgot to change the subject line, 48 of the 555 recipients got the wrong subject, paused it, fixed and continuing sending