BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[bible_pay]

*** BIBLEPAY IS ENTERING RUSSIA ***




We will be going live on Graviex on Christmas right after our new release!


The total integration cost is zero thanks to a donation from an anonymous donor.

[bible_pay]

From Compassion:

https://www.compassion.com/for-sponsors/stories/a-life-changed/meskerem-abebe.htm?referer=591993&j=485838&sfmc_sub=8526698&l=74_HTML&u=8180396&mid=10965948&jb=2&alias=%%linkname%%&utm_source=mc&utm_medium=email&utm_campaign=LifeChanged_Dec19_160681

[sunk818]

From Compassion: https://www.compassion.com/for-sponsors/stories/a-life-changed/meskerem-abebe.htm

If it is His will, may God bless BiblePay to survive long enough where orphans can become sacrificial leaders themselves.

Which criticism do you refer to from Inblue, I don't particularly know what you mean.

I do think DASH is watching us, I'll get back asap on that as time permits.

https://bitcointalk.org/index.php?topic=2388064.msg53286451#msg53286451

I'm referring to the "profit takers". Short term miners earn BBP and sell to offset their mining expenses. That is the same parallel with DASH miners. By adjusting the economics, the "profit takers" have less to sell on the exchange by diverting earnings from Proof of Work to Proof of Stake and Masternodes. DASH may completely eliminate Proof of Work after a lengthy and controversial community discussion. With InstantLock and Masternode quorums, much of the downside of Proof of Stake is mitigated by these technologies. The timing is also ripe as ETH is closer to switching to PoS as well.

Graviex

Are they the ones with the wonky 9th decimal? I've done some bad trades because of the 9th decimal. Just be careful when trading.

[sunk818]

For those interested in Prophetic Math and the number 7. This might help explain in more detail the Biblical connection of 7 and why Rob chose a block time of 7 minutes even though it doesn't divide evenly into a 24 hour period.

https://thebibleproject.simplecast.com/episodes/seventy-times-seven-prophetic-math-7th-day-rest-e10-7YtxtwnX

[bible_pay]

For those interested in Prophetic Math and the number 7. This might help explain in more detail the Biblical connection of 7 and why Rob chose a block time of 7 minutes even though it doesn't divide evenly into a 24 hour period.

https://thebibleproject.simplecast.com/episodes/seventy-times-seven-prophetic-math-7th-day-rest-e10-7YtxtwnX

Nice!  And in addition to the sabbatical cycle, the Shemitah and Jubilee cycle, the 7 day work week, I also believe in the '7000 year' Messianic Age theory; the theory that spans from Adam to the end of the Millenial reign of Christ (before we enter into a new period- eternity with Jesus).

In this theory, the age is broken into 4 dispensations:  2000 years for Noahanic (Adam to Noah), 2000 years from Abraham to Jesus (The Law, the time of Moses), and 2000 years for the Church Age (The age of grace), and finally the Messianic Kingdom (1000 years).

I believe that the Star of Bethlehem passed over Israel when Adam was born (in about 4000 BC), then again around 1500 BC (star software can show the exact date, but I believe Abraham was about 99 years old - approx the time God made the covenant), then again in 4 BC (2 years before Jesus was born, while the three wisemen were journeying), then again in 2016 (the end of the Obama presidency, roughly the end of the church age).  I believe it appears 'as a sign and wonder in the sky' approx. 2 years before something major takes place (IE 70 years from the reinstatement of Israel brings you to that date in our current Church Age).

So if you are like me, I look forward to the fulfillment of the 6000 years very soon (this is similar to saying, when will Daniels 70th week start)?
God has an accurate clock, and I believe this is another cycle.    If I'm wrong we still actually have a little room in between Daniels 69th and 70th week, and the length of a "strong" generation, so I'm not setting any date (to imply it has to be 2 years after the star passed over Israel last); I think the bible clearly tells us no mans knows the day or hour; and the "sign" is just that - a sign of the end of the church age.  We are to pay attention to the signs however, to be zealous for the Lord and know when we are in the "season" of his return.

[sunk818]

https://whitewalr.us/2019/2019-holiday-gift-305.html

Thanks to the generosity of the BiblePay community, we were able to collect 1.44M BBP and $100 USD.

That converted to 0.0424 BTC ($305 USD) and sent to the two charities for the children’s holiday party.

Thanks to everyone for their generous hearts and a desire to give anonymously without expecting anything back.

[bible_pay]

https://whitewalr.us/2019/2019-holiday-gift-305.html

Thanks to the generosity of the BiblePay community, we were able to collect 1.44M BBP and $100 USD.

That converted to 0.0424 BTC ($305 USD) and sent to the two charities for the children’s holiday party.

Thanks to everyone for their generous hearts and a desire to give anonymously without expecting anything back.

Thats awesome!

Thank you for organizing this!

I'm sure they will have brighter eyes this Christmas.


On a side note, Todd clarified that no one has sponsored the core 11 yet; so I plan on sponsoring all 11 myself tomorrow; unless someone wants to commit to some today.  We can talk about Kairos right around Christmas.

[bible_pay]

I'm currently going through the c# pool.biblepay.org code to find anything we have in it that is still mission critical.  (Now that the pool no longer mines, nomp takes care of the mining).

My goal is to port this extra code to DSQL so it can be served in a decentralized way.

So far I have already found a lot of work for my todo list.  Decentralizing orphan letter writing (although, with POOM coming up, technically all the letters are the responsibility of the miners now, so Im placing this low on the list).  Decentralizing the Expense-Add and Revenue-Add pages (IE Im going to make it so a biblepay keyset can have permissions to add records, this means we can designate multiple users to add expense or revenue records).  (On a side note, DSQL will support almost any new data-add reqs in the future as this will be very generic and flexible - not hardcoded to be 'expense add'.  We will have a customizable UI per object type, so we can add more pages in the future, and allow our 'ambassadors' to make this a robust community project for administration purposes.

- Two reports for Cameroon and Kairos for POOM API integration
- An API call that gets the current BBP price and the BTC price (we will do this in DSQL also)
- BBP RPC call support for DSQL
- Linux MSSQL support and Docker support (this will need a video of its own)
- Decentralized orphan list
- Treasure Trove Video search
- SEO urls for BMS UI
- PODC UI
- Decentralized Web home page
- Partner Page (We partner with...)
- All things stored in the pool.biblepay.org SAN need converted to DSQL links (oh no.... this is huge).  We have a lot in there.

When this is finished, I plan on retiring pool.biblepay.org in favor of DSQL.

[sunk818]

On a side note, Todd clarified that no one has sponsored the core 11 yet; so I plan on sponsoring all 11 myself tomorrow; unless someone wants to commit to some today.  We can talk about Kairos right around Christmas.

I can sponsor core 5 of 11. Let me know how.

[bible_pay]

** Compassion.com Update/POOM Update **

So we currently have 80 children with compassion that we pay $38 per month for, and we have a credit balance.
To be fully transparent as we always have been, I want to give an update on our history with compassion and where we are going in the future.

Our first sponsored child was in August 2017 with compassion.  We peaked with 329 sponsored children in August 2018.  After the HODL crash we decreased down to 80 where we currently are.

We have a credit balance of ~$3200 that will allow our compassion children to continue until January 20, 2020.  I plan on giving Compassion a 20 day notice, after the holidays are over of our intent to temporarily cease sponsoring children in the compassion account.  This is not entirely for financial reasons however, it is primarily because we released POOM, and Cameroon-One graciously agreed to have IT conference calls, and integration meetings, and was flexible to implement a Proof-of-orphan-sponsorship mechanism that proves a miner is sponsoring a child.  (To clarify this:  With Cameroon-One, Kairos and POOM, a unique ID (generated by BBP) exists for every orphan.  This points to the orphans BIO URL - and it also points to a history of payment debits and credits for the child by the miner.  Meaning a person can provably ascertain this child is sponsored, and, anyone can check the hex-id code of the child with the charity and know the child is with biblepay.  Additionally, our API can query a child balance directly from the charities server by ChildID.  Otoh, with Compassion, they would not agree to providing any indicator on an account containing a hex-code that would point to the child being sponsored by BBP.  Therefore we placed an emphasis on integrating with POOM because it gives us exciting opportunities for transparency, decentralization, and for scalability.  With POOM, our sponsorships will scale up without destroying our price (because miner rewards are used to compensate the miners, in contrast to governance charity funds).

I agree that we still have work to do, in decentralizing further.  We will still explore even more autonomous options in the future, such as providing automatic keypairs per orphan id with auto-scaling, and further decentralizing our chairities to make them automatically pick up children without human interaction.  I agree that we should not have a single point of failure or a single person blocking this endeavor in the future.  

I want to stress, Compassion.com is still a valuable partner that we may want to work with in the future.  We need to tell them with love we enjoyed their cooperation and partnership up to this point, and that our decision to suspend the children was driven by our POOM endeavor.  If they will be open to future calls in providing a public orphan-id for biblepay to query, then we will open communication again with them.  What I would ultimately like to see is us take control of our expenses, our price rising above 100 satoshi, and having a true DAC (decentralized autonomous charity) to auto fund Cameroon, Kairos and Compassion, and see us with over 32000 orphans per month.

On a side note, compassion does have insurance for the children we are about to cancel.  A child sponsored with compassion is automatically covered on a policy of continuation until they receive a new sponsor.

[bible_pay]

On a side note, Todd clarified that no one has sponsored the core 11 yet; so I plan on sponsoring all 11 myself tomorrow; unless someone wants to commit to some today.  We can talk about Kairos right around Christmas.

I can sponsor core 5 of 11. Let me know how.

Awesome!  Thanks!

So primarily all we have to do is once we go through the normal two steps (step 1:  Sponsorchild authorize, and Step 2: Paycameroon for each of the new 5 children), when you email Todd with the RPC list of the 5 payments, you can tell him that you will take 5 of the core children that cancel this year.

Here is a list of our 11 children, you can pick the 5 you want (so just mention their 5 names) and Ill tell Todd Ill take whichever children remain tomorrow:

Clodeth Ajemsibom   https://i.ibb.co/wYwJcXQ/e345cff0-1135-4255-86ac-cdb486240320.jpg
Bhe Christable   https://pool.biblepay.org/SAN/Mission/Cameroon/BheChristable.png
Bih Encarnasio   https://pool.biblepay.org/SAN/Mission/Cameroon/BihEncarnasio.jpg
Che Brian   https://pool.biblepay.org/SAN/Mission/Cameroon/CheBrian.png
Che Samuel   https://pool.biblepay.org/SAN/Mission/Cameroon/CheSamuel.jpg
Fru Nji   https://pool.biblepay.org/SAN/Mission/Cameroon/FruNji.jpg
Fuhni Randy   https://pool.biblepay.org/SAN/Mission/Cameroon/FuhniRandy.jpg
Mambo Lora   https://pool.biblepay.org/SAN/Mission/Cameroon/MamboLora.png
Nde Harison   https://pool.biblepay.org/SAN/Mission/Cameroon/NdeHarison.png
Ngum Carol   https://pool.biblepay.org/SAN/Mission/Cameroon/NgumCarol.png
Sweri Marylein   https://pool.biblepay.org/SAN/Mission/Cameroon/SweriMarylein.png

Optionally if you don't care which 5 you can just say any 5 and we will work it out later.

Thanks!

[bible_pay]

Speaking of moving docs from the pool server to DSQL, I ran across this guide:

https://pool.biblepay.org/media/Biblepay-General%20Information.pptx

Its a very nice guide.  It says last modified by Sun.  Sun did you create this one? 

Is anyone (or Sun) interested in modifying it to reflect WCG in place of Rosetta?  And freshening the reqs for PODC 2.0?

Feel free to fix it and the Ill place it back where it is - and of course move it when our new page is ready.

Thanks....

[sunk818]

Speaking of moving docs from the pool server to DSQL, I ran across this guide:

https://pool.biblepay.org/media/Biblepay-General%20Information.pptx

Its a very nice guide.  It says last modified by Sun.  Sun did you create this one?  

Is anyone (or Sun) interested in modifying it to reflect WCG in place of Rosetta?  And freshening the reqs for PODC 2.0?

Feel free to fix it and the Ill place it back where it is - and of course move it when our new page is ready.

Thanks....

I did not create it but I vaguely recall making some edits when I first learned about BiblePay and I gave it to you and/or Jaap.

Regarding sponsorships, I'll make arrangements with Todd to sponsor the first five on the list:

Clodeth Ajemsibom   https://i.ibb.co/wYwJcXQ/e345cff0-1135-4255-86ac-cdb486240320.jpg
Bhe Christable   https://pool.biblepay.org/SAN/Mission/Cameroon/BheChristable.png
Bih Encarnasio   https://pool.biblepay.org/SAN/Mission/Cameroon/BihEncarnasio.jpg
Che Brian   https://pool.biblepay.org/SAN/Mission/Cameroon/CheBrian.png
Che Samuel   https://pool.biblepay.org/SAN/Mission/Cameroon/CheSamuel.jpg

[prologas]

GrepBlock.com

+

Biblepay (BBP)

https://grepblock.com/?page=coin&coin=BBP

[togoshigekata]

Richard Heart was almost in tears about Bitcoin not doing well 2 years ago in an interview with Ivan on Tech
(Richard was a Bitcoin Maximalist and was an early BTC miner getting 50 BTC a block),
he makes some good points in the interview [sorry about the cursing and gestures]:
https://www.youtube.com/watch?v=w8_1JFE_9dI&t=4100
I only recommend watching for maybe 15-20 minutes from the point I linked

[bible_pay]

Do Jews need Jesus?

https://www.youtube.com/watch?v=5CWAjcZLQSo

[bible_pay]

Richard Heart was almost in tears about Bitcoin not doing well 2 years ago in an interview with Ivan on Tech
(Richard was a Bitcoin Maximalist and was an early BTC miner getting 50 BTC a block),
he makes some good points in the interview [sorry about the cursing and gestures]:
https://www.youtube.com/watch?v=w8_1JFE_9dI&t=4100
I only recommend watching for maybe 15-20 minutes from the point I linked

That guy is raw and off the 'chain'.  I wish we could convince him to receive the Holy Spirit so he didn't swear.
But anyway he appears to be very intelligent and his point of view is very unique.  I give his opinion a lot of credibility.

I personally believe in Elliot Wave macrocycles.  I feel that up til now, everyone has been very loyal bitcoin (they give the devs complete credit and loyalty since they were the first successful crypto - and thats honorable and good  and surprising in an industry that has so many catastrophic problems) and the altcoins, got really trashed after that 2018 pump n dump.  I think the altcoins got blindly bought buy every institution out there because they were too dumb to pick the good ones so they bought everything at the same time, hoping to hold the holy grail.  Then after the crash the institutions were burnt so bad, they are looking at alt coins like hazardous waste (one reason we are so low right now ourselves).

But with waves, everything goes in cycles, meaning we will eventually see BTC crash (or halve) and no loyalty to the grandfather, and Altcoins be rewarded - but this time probably certain altcoins (as the burned institutions are going to do some homework).  That will be our chance to shine.  Also, if BTC goes down again it gives people a chance to reload on the failed altcoins.  This brings up the bigger question though, will the industry strengthen when the real coins with real use cases do get rewarded?

I think Richard is right about the facebook/amazon case.  They will make a coin and ruthlessly cut out bitcoin and steal the technology.  And it will put a gaping hole in the market value of bitcoin unfortunately.  Ive never told anyone to buy and hold a coin that is over $10k as I feel its risky.  BBP might be cheap but it has the potential to go places due to the leverage.

[sunk818]

Does BBP have a max time between blocks? I recall PoDC 1.0 had a 45 min (?) limit? I've been noticing some very long wait times between blocks since we got off anti-bot net (ABN). Blocks per day fluctuates more now. Does difficulty allowed to mine the block drop after a certain time? Does the pool handle this too, or this is only solo mining?

[bible_pay]

Looks like trading is already up at Graviex:
https://graviex.net/markets/bbpbtc

One nice thing they did for us is list us in all three markets:  USDC/BBP, ETH/BBP and BTC/BBP

Togo is working on a press release. 

[bible_pay]

Does BBP have a max time between blocks? I recall PoDC 1.0 had a 45 min (?) limit? I've been noticing some very long wait times between blocks since we got off anti-bot net (ABN). Blocks per day fluctuates more now. Does difficulty allowed to mine the block drop after a certain time? Does the pool handle this too, or this is only solo mining?

We still have a late block threshhold of one hour.  (I'm really, really glad we put that in, because that is what gave Rapture a disconcerting time when the chain froze).  What happens is after 60 minutes, the block becomes 80% easier to mine. 

It works on both pools and solo. 

I realize we have had the variation; we are doing a couple things to rectify this over the long term.  For one the next version has the 'masterclock' command that will allow us to see how far off our clock has drifted since inception.  The other thing is Ive been discussing a Part A & B miner with MIP, but I havent had much time to post the spec.  I believe this idea offers some pretty good pros, and whats really nice about it is it works with chainlocks and is fork proof.  This part would be a game changer, so I think we should discuss this further once I release the spec (as it makes the time drift a moot point).  I'm not inferring btw that BiblePay is going to replace POBH with a new algorithm.  Im just inferring that we will release a spec that shows how we can perform useful work on the main chain without forks by extending POBH.  Its also pool compatible so we can keep nomp in place, and its exchange compatible.  The part that I'm still working on is a dotnet proof of concept for "Part B".  I need to test this end to end before I can release the spec.