Thanks, then maybe the community should ultimately decide this.
I think we made a good decision in giving the unbanked the ability to mine in PODC 2.0 up to 250 rac, before posting collateral.  This also allows a newbie to build up some rewards, while only spending 1 bbp to get started (for the association fee).

However, I haven't heard back from Gridcoin, with any particular quid-pro-quo reward for BBP.  James mentioned that Gridcoin will be allowing any team to earn rewards. 
What would BBP get in return for whitelisting Gridcoin? 

I feel that we should put this up to a community vote soon.

I'll put in 1.1 million!

If anyone is wondering how to become a Christian healer, or wondering if all these diary entries about healing people are true:
I can assure they are all 100% true.  You can search for 'Tom Loud miracle healing' videos on youtube; he is basically the second (internet) person I learned this from (after meeting Torbens group and going out with them at his kickstart), and Tom's style seems to work for me the best.

Tom Loud is *exactly* the way I approach people, pray for people, and I see the exact same results as him.

He has a logical and methodical approach, and that seems to be compatible with my personality.  Other people might like Todd White, if you are a Marine, or Torben Sondergaard if you have that European approach, etc.

We grew someone's leg out last week.

Dash has a feature that we inherited called a dirty block index.
This means that once your node makes a call on a block, that it is invalid, the only way you can get past that block is to update the dirty block index flag back to null.

So the alternative is to find the good hash that you rejected, and type 'reconsiderblock rejected_block_hash'.
But this can easily lead into other problems, like what if you forked because you were already missing governance data?  (Which sounds like that is the case).

Thats the reason we type -erasechain=1, to solve more than one issue at a time.
Once we have the quick sync option that will be another option.  You can always *try* typing exec reassesschains, but I tend to try to lean toward the sure solution.

If there are any features from the Top 50 coins that anyone thinks biblepay should have, let us know.

Maybe we can merge them in also.

I was looking at proof-of-wifi last night (in the internet-of-things coin) and it was pretty cool; I thought yeah we should look into creating our own wimax network for the great tribulation; but that idea is almost as hard as launching a biblepay satellite for private communication, so we have to scratch it.  However the IOT mesh is actually pretty cool; eventually we can have a biblepay node running inside an IOT device etc.

Yeah, that was Chris, but now that we have PODC and DSQL I think we have found most of our identity, but, I think we still need a community prayer room, Pay to preach, maybe a proof-of-preaching feature, unbanked cancer mining and tithing, and the video voting room etc.

This is a good way to become friends with their whole community without looking like we are poaching users.  If we offered say for example 5,000 keys of potential rewards in a batch, then we could post something in their forum etc.

I don't know which Dash person you are referring to was this Chris A. when I spoke to him for an hour about UI enhancements and Evo (this was right before evo came out), or someone else?

Looks like its just you and two sancs (looking at the pool.biblepay.com health report), I see two sancs are stuck at that height, but the other 139 are healthy and have the exact vote levels.

I would reload the chain with -erasechain=1.

The height you are at means you rejected the last superblock (158690).

Question from the community:

Is there anything we missed in the .14 branch (this is our next mandatory upgrade)?

So far, this is what I'm working on shoring up before the end of this year (preferably, for a Christmas 2019 release):

- ChainLocks to be fully tested
- Any winning proposals that won between mandatories gets merged in (IE : the sanctuary raise, the GSC contract percentages for the future, any mandatory anti-fork rules, any future deflation changes, etc)
- PODC 2.0
- Dynamic Whale Staking
- InstantSend lock fix
- PrivateSend mixing fix
- External wallets requiring no unlocking for stakes
- Kairos support
- Apollon support
- Dash .14 prod fixes Up to the current date

Did I miss anything?  Please, if you feel something is missing in Biblepay that should be in the next version, post immediately.

The most probable outcome is we will focus on a Christmas mandatory upgrade and release all of this at once.

The biggest disruption this will require is everyone will need to be on deterministic sanctuaries by Christmas.  I am working with Apollon now to find out if they will support us during the cutover (or not).  If we do not have support from Apollon and Satoshi, we will recommend users who are about to be left behind use the new non-standard port feature to start a sanc.  But in the mean time I will do my best to set us up with a seamless path.

One other point we need to cover very soon:
I will be looking for a couple *prod* volunteers to run the new version against prod before the cutover.  The goal is to verify anti-fork behavior and ensure QOS.  We don't want any surprises leading up to the cutover block.  The version is not yet ready.

If you want to help test PODC 2.0:
https://forum.biblepay.org/index.php?topic=465.msg6650#msg6650

Regarding the question about 'exec theymos', yes that particular command (for accountability has been removed) in the new branch, and also business objects have been removed (in favor of DSQL).

DSQL can do everything the business objects did, and more, and also with an HTML 5 UI to show the data (in contrast to rpc lists).  (In the mean time our partners can still access http://accountability.biblepay.org for the expense data. 

Regarding accountability itself, let me comment on all that in detail when we roll out the .14 branch.  In general, I plan on coming up with a migration plan to copy anything in pool.biblepay accountability over to DSQL, so we have a better decentralized report of our history.  But, in a parallel endeavor I would also like the wallet to be able to report its history from the RPC. 

We've had : Tithe blocks, governance to vendors, foundation tithes, donations, and now POOM. 

Its of course desirable to have decentralized orphan sponsorships where accountability can all come from an rpc report, but that requires standardizing our sponsorships.  At this stage of the game POOM looks promising in that its decentralized by miner.  It remains to be seen if that stands the test of time, or if we also have a new 'address based' orphan, or, if we ever have 'sanctuary sponsored orphans' etc.

LOL, I never heard Closed on Sunday, its kind of hilarious he screams "Chic filA" at the end.
I like it.  Id rather the young be indoctrinated with hints of Jesus in their music than being gangster filled.

On a side note if anyone remembers my little comparison in the 'Immince of Jesus' wiki:  https://wiki.biblepay.org/Imminence_of_Jesus, Isaiah 17 is one step closer to being fulfilled today:
https://www.timesofisrael.com/syria-reports-air-defenses-intercept-hostile-targets-over-damascus/


Sure you can tweet out to them, but I haven't received any reply from the e-mail and I also left a message.

Ok, the BiblePay CPID Faucet has been deployed to 'pool.biblepay.org'.  We are getting ready for PODC 2.0 early.

Thanks Togo - this helps a lot.

OP Post Updated.

EDIT:  So far, I added the three pools (search for Nomp and Suns pool and LeoPool), and I changed the whitepaper parentheses warning to being updated.

Important message for BiblePay worldwide:

https://forum.biblepay.org/index.php?topic=465.msg6650#msg6650

I'll switch it back over to CPIDs, since PODC 2.0 is coming.

Can you please build up 100 rac on WCG, and give us a shout when you are ready and you can test it.

We have retired pool.biblepay.org mining for now, in favor of nomp.

Please navigate to:

http://nomp.biblepay.org to get started.

Note:  We have other pools also - please see the list over the last few pages here.  TODO:  We need to add these to our OP post.

Please discuss and vote on this also:

https://forum.biblepay.org/index.php?topic=468.msg6502#msg6502

I'll be entering this proposal today, primarily to ready our testnet branch for anything that is thrown at us towards the end of 2019.

Another way to put it, I want to start to bulletproof the .14 branch, in case we have a mandatory updgrade towards the end of this year (in contrast to a PODC 2.0 upgrade).

This could be a possibility, with the changes that are coming in related to the deterministic branch, Kairos, PODC 2.0, DWS, and Apollon, etc.

I love this advice; because God is so big he can fix this temporary rut.  I look at our condition as a temporary phase of character building for all of us.

Abba Father, please pull us out of the rut, because we have pure intentions to help orphans.

I reached out to the Chic-fil-a foundation to try to reach the VP of charity.

https://www.chick-fil-afoundation.org/faq

Since we have the same Christian values, I wanted to make them aware that we are a feel-good investment for people seeking cryptocurrency exposure.
They also like to help orphans.

I offered to have a conference call with them, and discuss white branding a Biblepay wallet into a Chic-fil-a wallet.
Also offering integration for door-dash so we can have people buy fast food with BBP and have it delivered.

I think it is just up to SX to allow sub-satoshi markets.  They could theoretically add a digit after the satoshi and make it 9 digits.
(Although it probably goes against the grain and is non-standard).