Yes, its OK, this is because in Prod, we send most of your change back to the CPK.  This is to allow the GSC system to auto-stake them continuing the cycle.

If you want them out of the CPK, just select them in coin control by checking that address then send them to one of your other owned addresses and the coins will then be out of your CPK.

Hi Buddy-

Well first of all the Christian-Public-Key address in Prod does nothing special, it doesn't hold any special amount (although the one in TestNet does).

So to jump right to the explanation, each of your keys has a different balance.
I think the easiest way to see this is for you to go to : Settings | Check Enable Coin Control features.
Then go to Send Money | Coin Control.

Take a look at the balances per public key.  Those equal each of the explorers balances per public key.
When you add them up they equal your grand total.

This is primarily for Dashs anonymity feature(s).

I can't really fathom where Iquidis is garnering 4,553; maybe something to do with peers.dat, but looking at Iquidis, which appears to be much closer, I believe iquidis is counting the distinct public node IP connections (IE full nodes with open firewall ports accepting inbound connections).

This is a little speculative, but my best guess on this is to multiply the 176 by 2 or 3 or so and round it off to about 500 nodes.
This is because private nodes who did not expose the firewall port can't be seen by iquidis and our bitcoin codebase does not attempt to track IPs (we just save peer info in peers.dat but thats not being reported on).

Thats a nice chart!

On the new 15 sponsorships, no, I havent sponsored Cameroon-ones 11 needed children yet.
So they are still open.  I just promised them I would if no one did by December.
Those 15 are children that I was sponsoring through Global Giving when they had the match going (GG was giving Cameroon double the revenue but I was paying for 15).  I decided when that ended to move them to POOM to save the children.

On #2, I believe we can address that.  Since we really want to move toward being a decentralized DAC, one more step in the right direction would be to make an RPC report that picks up all charity expenses and all POOM expenses from the chain.  If POOM becomes our future, then the core wallet would not need to rely on DSQL to add 'expenses' to the total.  We really need to look at all of our income and expense processes and make sure biblepay lives on regardless of one of our vendors, or any of our devs leaving.  Another words, ensure the foundation wallet has no bearing on the long term existence of our crypto.

On #3, Andy from Kairos got back to me yesterday and he is on board.  He is buying the domain, getting the web site set up and will be contacting us back with integration resources - he also has an IT person that will be getting involved. 

I haven't made any more changes since I checked them in the first time but more importantly, I don't think you have control over that.
The work restart occurs when nomp accepts a share for that difficulty level, then it asks bbp core for a new block merkleroot, then it updates the miners work.

So the update is just a naturally occuring factor as people solve the shares.
You are probably observing the nomp pool having more frequent restarts because the average share is being solved faster.

But either scenario should still be the same efficiency level as far as solving blocks.

Just covering the unanswered part:
You can still solo mine in the core wallet, but its about 20% less efficient than the external miner.
And pool.biblepay.org redirects core wallet pool miners over to solo mode now.

Thanks, yes, I agree that Coinsbit really looks great, and knowing a lot more about this process now, I like the Gecko 'reputation' score (of  8 ) for them.  It also shows like Togo mentioned in their support - they care about the customers on discord, and dont seem shady.

Of course Togo tried to start an account and couldnt get through, the laws of the US are probably so severe that an exchange cannot take that risk.

So guys keep trying to find one with an actual offer.   And or a way for a US trader to withdraw.

The reason BBP is listed on the page is we almost executed the deal, but stopped it before funding.

This first part is for our veterans, not meant for the new user:
Although the pool will still be up for a year or more while we figure out accountability migration to dsql, the reason I don't want to leave 'mining' on in the pool is since 99% of the miners left, it cant solve enough blocks to warrant supporting it, and more importantly, the payments are too low to cover people who hop, so I disabled mining against pool.biblepay.org to send everyone toward nomp.

So please ask him if he can go with nomp, or solo mine.

One other note:  I am working with MIP on an idea where we can bring the core wallet back up to the same speed as the external miner (and eliminate any chance of ever having a GPU) but this idea is still in its infancy and would be about 9 months out if we work out the details.

So for now I recommend nomp.

Yeah, I think eventually one of these top 20 exchanges will help us.  Togo has reached out to the top 100 exchanges, and so far, we have only found 3 that are interested.  Coinsbit is EU only and Crex is EU only.  So we havent been able to justify their fee yet - although we told them we are open to negotiate a lower fee for not have ability to trade in the US.

We do have interest from Graviex and Stex.  Graviex looks like they might step up and help us- so we are going to discuss this month.  Stex is being pretty nice, but the owner doesnt want to list a btc pair for us (only eth).  Im still going to reach out to him again and see if we might have a middle ground.

Other than that, weve tapped the whole 100 and got nothing but insane offers; I think binance wants 100 btc, etc.

Thanks, the dynamic whale staking might be nice in that we maintain our entire infrastructure and make an easier to use version of 'whale staking' that doesnt require the wallet to be on.  Something that a Christian 401k might say: dump the excess 5k in bbp for a year and see what happens, if their staking generates 100% more coins for us, etc.

Ill make a proposal page out of it and get more feedback.  So far, I havent heard any resistance from the Holy Spirit, except - that we must strictly classify this feature as STAKING.  It cannot be confused with any non-staking feature, like for instance a coin offering interest on a balance, or a CD or anything like that.  It would be Coins earned on coins burnt for a duration of time, and classified as Dynamic Whale Staking.  Although let me clarify, the reward would be for any size stake (1000 bbp, or 1,000,000 bbp).  I will try to clarify that in the proposal.

Also:  I will be sure to include a plan to not veer from our total emission model.  This I think can be done by integrating a whale staking model in where the coin-emission deflation has a sharper curve at the end (like a black hole). So the end result is the same, but with staking for N years embedded in.

Very nice, on LeoPool, sweet.

Sun if this is your France domain, please PM or email me if you want a DNS record - for example - sun.biblepay.org, etc.

OK nomp is back up. 

I just got in, Ill check.

So I am brainstorming a little, trying to come up with some ideas that help address our two biggest problems:  1) Needing a boost in price - and this boils down to making biblepay attractive for Whales to invest in, and 2) needing a boost in new users - IE one new user per day.

Here is what I have so far - not sure about these yet, as I have a new mantra as a child of God:  Pray about them.  Ask Jesus if these are "approved" or not.

For now, the first idea - making BBP an attractive investment for whales:  Dynamic Whale Staking?
What if we created a new staking option, that was more simple than ever (does not require sancs, and does not require daily GSC stakes) but instead focuses on opening the relationship between buys on the open market and rewards - something to the effect of : Biblepay orphanage stakes, with a dynamic ROI determined by a supply-demand rule based on "burn demand".
Basically, we would have a wallet algorithm that determines the extra-BBP paid to the staker (this depends on the duration of the BBP hold period) and also on the other variable (the burn demand).

Something like this:  User buys N bbp on exchange A.  User enters a proof-of-stake command (this burns the bbp and gives them a staking TXID, and a maturity date).
Time passes.  At the end of the maturity period, the wallet refunds the bearer their original stake + Reward (which conditions are stored on the original transaction record) and this is done automatically by our coinbase.  Another words, the daily superblock would also pay that days stake rewards at the same time.  Of course, we would quadruple check our burn algorithm code in testnet - to verify the 'burn' condition (IE the original funds really were burned - meaning this idea only emits the net reward to the bearer). We would set up a dedicated burn address (similar to our foundation for orphans, but for burns).

This would theoretically cause outsiders to gain interest in BBP to seek the excess return.
The burn demand equation would be something to the extent of N addl BBP for your burned BBP, decreasing by the amount of outstanding 'live burns in the chain'.
So another words, if 500 burns already exist, the return for new burns would be almost zero, but if none exist, the return would be very large.
We would make it so the quote is reliable until its consumed (so people are not misled), but once consumed everyone else would see a lower quote etc (it would be dynamic and real time per block).

Idea 2: PR embedded in the core - through some algorithm:

The other idea is reviving our old BOINC faucet to reward 5000 bbp to new CPIDs, who have > 250 rac and have not collected BBP in the past.  
Or - embedding some type of PR campaign in the core - something that rewards new users similar to referrals.
But of course this is almost impossible to design.  The BOINC faucet is still our best bet.

Half of the sancs in TestNet are pose banned.  Please look into reviving them - see the revive command:
https://forum.biblepay.org/index.php?topic=465.msg6445#msg6445

Updated the OP.  Ack on the BBP home page.

** Cryptopia.NZ bankruptcy **

If anyone is affected by the Cryptopia bankruptcy I found this:
https://www.grantthornton.co.nz/globalassets/1.-member-firms/new-zealand/pdfs/cryptopia/4.-affidavit-of-dir.pdf

It basically shows that Cryptopia had 1,000,000 distinct active trading accounts who had a positive cryptocurrency balance at the time the funds were stolen.
And Cryptopia owes these account holders $217,000,000.  The top 101 whales are owed 1608 BTC.

It also shows Cryptopia had active a/p owed out to vendors totaling $12,000,000 ($1.5 million to their web hosting company) that is also not paid (since the entire companys assets were seized).

I havent found out yet how much assets the police were able to recover for the class action suit - but if I find it I will edit this post.

Could u please post there and I will explain, thanks!

I just read this;  thank you Sun for taking the time to interview Capulo.

And I think it was a very good article, it definitely gives insight into how a community member comes to mine BBP.  

And of course its good to know who Capulo is!  Thank's Capulo for taking the time to unveil yourself.

I did see that Capulo is not a believer yet!  This is good, because Capulo, I want to convince you of the reality of Jesus, this should be part of my job here.

You know this Thursday I have a baptism, I'm baptising someone I prayed for.
Is it strange to hear, this woman was cured of cancer by Jesus the night that I prayed for her in Walmart?  And, that she is an Orphan?  (How was she cured... she was diagnosed with cancer, went to the doctor, looked depressed in real life when I saw her, then I prayed for her, she went home, that night Jesus appeared at midnight and shot a white light at the cancer, she went back to the doctor, and the cancer was missing).

Yes, it is very strange.  Also, I never gave her my card.  I was walking through walmart the other day and she found me and what she said was very touching.

Heres another one:  I prayed for a woman in the front of the store - and she dropped her crutches the next day.  Its not US, its that Jesus is using us.  (She was hit by a lightning bolt at church, also - I met up with her again at a restaurant to hear the story).

Its hard to jump straight to aliens, but I personally believe aliens are fallen angels or demons.

So anyway, what we need to do is pray for you, that Jesus reveals himself to you.  Just do this for me, pray to God: God if you are real, please reveal yourself to me.
God is waiting for you to make a move first.  Then he makes a move.   And so on.  Maybe thats why you found BiblePay!

Anyway, God bless everyone here.

On a side note:  I read and agree we need to be more user friendly for new users - thanks.

I'm primarily referring to non-copyrighted self uploaded material like rapture videos.
But if we ever got to the point where these were getting viewed, we could make arrangements with "channels" who OK the scanning first, or find a way to read the metadata for its copyright info - its probably already encoded in a youtube format that has a certain code if its public domain data.

I assert most of the data Im talking about scanning has more of a right on our computers than on youtubes servers.

(They make ad revenue off of the ads and make billions of profit, where we dont make any revenue and spend money to maintain and host it).

Anyway, this idea is not yet about scanning videos - its about writing something similar to BOINCs operation - but as a hashing function - BOINC is a framework that allows tasks to run.  I'm working on designing a way for tasks to run in Part B that is insulated from fork risk.

Could you first please check your time & timezone, ensure it is correct within a minute or so?  Thats a common problem.

Next you could add a couple peers:

addnode add 216.116.134.119 onetry
addnode add 192.3.249.34 onetry

If that fails, just restart with:
./biblepay-qt -erasechain=1

Could be a bad cache of gobjects, possibly.