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

Ok, I accept that.
But I don't have as much luck as you (pool)
I hit 90% less blocks. It was after 1146 update (maybe it's coincidence). But I don't remember these 1132 miners before. I'm almost sure, that those miners (except BHVaitQvSJpWqzLJg9N2owCq1W893KQvYP) are new, not "not upgraded". Maybe it is their own version.
But yes, they must have enough coins to mine, so from this point of view it looks that's OK.

Its interesting that 26% havent upgraded from 1432 yet.
In pool.biblepay.org, we enforce the version must be > 1.4.4.4 btw, so the 26% who did not upgrade are definitely solo mining.

As far as how they are doing it, the mandatory upgrade with 1445 actually was mostly related to govobj propagation + cameroon 1 bus logic.  So, we did make it mandatory so that the sancs upgraded (and we know they did because the sanc protocol version is enforced).  

But getting very specific, 1.4.3.2 will actually still stay in sync and mine technically (because it wasnt a hardfork consensus breaker).  The main reason it was a mandatory was the older versions had a problem with gobject propagation - this basically means those 1432 nodes do not have a complete picture of the daily GSC contract; they are more apt to go out of sync if they miss a gobject; and worse they might not forward a gobject over to a friend node.  We probably should enforce it in the next leisure (by ddossing or banning versions earlier than 1440).  Most likely these miners are not full nodes anyway (meaning they arent sharing the data much) as miners are usually behind their own firewalls (they arent sancs), so the problem is relatively low risk.

But yes we could consider banning them in our next release so they upgrade.

Thanks for pointing this out.

From a mining perspective this should not be causing a problem though since they can't pool mine, they must be self funded abns.

But as far as hitting blocks, the pool is still hitting 33%.  I havent seen a big change recently. 
(So these 3 CPKs are solo mining 25% of the blocks I see.  I wonder how many machines are being used; I don't think we can tell.)

Hi Rob,
please can you take a look o PoBH mining?
Maybe two days ago my miners stoped hiiting a blocks.
Today I found, that it looks that there is "some problem"
I tlooks that there are miners with wallet version 1432, but mandatory was 1145....
When I took a look to last 500 bloks it looks that first 3 miners are 1432...

It is OK?
Thanks

They reached out to me last night, that they received the airdrop funds (1.35MM), and we decided to potentially go live on 9/17.

They still have to confirm this, the ticker pairs, the airdrop info, etc.  I will post go-live info as soon as I hear further confirmation back.

Hey Rob, great work!

Any updates on Tokok?
A user from our telegram and another from CPU Miners Club discord were both asking

CPU Miners Club
- Discord: https://discord.gg/cc4jCB6

So it looks like a couple problems did exist.

First of all we have had a lot of Sanctuary migration over to Apollon in the last two days.  The old sanctuary votes that existed on expired nodes have been floating around and being purged causing a lot of extra traffic (as the new nodes recreate new votes, etc).  So that is coming to a close now, I see most of that activity is finished.

The second problem is we had a network setting - for certain gobjects - set wrong - causing higher than normal governance traffic levels.  This has been corrected.

Note, if you want to re-test the governance sync time, please make sure the sync occurs in one shot (IE it doesnt say : Attempt #8 etc).  (If sync is failing thats a different problem - that means the node you are pulling from is ddossing your request).  The true sync time for mnsync step 4 should be that it asks for the gobjects and succeeds in receiving all in one shot and moves to the next mnsync level.  Theoretically we should be syncing gobjects in less than 3 minutes now.

Regarding the complaint about network traffic that NSummy posted I have been monitoring network traffic and after, and I see a very large decrease now.  With our old settings, I sent and received 1 gig of data in 2 days.  Today, I see that has decreased to about 200 meg (that sounds relatively normal).  So feel free to confirm and if it still seems high we need a volunteer to set up a baseline comparison with Bitcoin and Dash.  Ill keep monitoring my local node to see if we stay low.

It does seem rather long; let me check into this.

It might just be my system but has anyone else noticed within the last week or so MASTERNODE_SYNC_GOVERNANCE seems to be taking much longer. Here is a an example of that where it took 810 Seconds to sync.. Configuration file has not changed in months but this seems to be just acting a little slow.. Anyone else see this or have an idea how to speed up this process?

2019-09-05 15:34:17 CMasternodeSync::SwitchToNextAsset -- Starting MASTERNODE_SYNC_GOVERNANCE
2019-09-05 15:37:49 UpdateTip: new best=6bd356c3656f535beeb651dd6c5eea03b51210ce75c0e9bfd431e0b65e4028cf height=142967 version=0x20000000 log2_work=59.54057831 tx=1131662 date='2019-09-05 15:37:45' progress=1.000000 cache=0.0MiB(0txo)
2019-09-05 15:37:49 {PNB}: ACC  UpdateTip: new best=333dbc8d077e827e2a5931aef78fbd2e88c26bf60977f922bf63dc8cbe22ad70 height=142968 version=0x20000000 log2_work=59.54058279 tx=1131664 date='2019-09-05 15:41:29' progress=0.999999 cache=0.0MiB(0txo)
2019-09-05 15:42:58 {PNB}: ACC  CMasternodeSync::SwitchToNextAsset -- Completed MASTERNODE_SYNC_GOVERNANCE in 810s

Thank you Rob. You are right. It was a problem with the Age that I wrongly check.

I'm having the same problem.

This is a great achievement, let's hope this increases children sponsorships.

Right now in this cameroon-one startup phase, the excess coins are not emitted (so like you say, in effect they are burned).

could you please paste 'exec createabn 125000' if it is still happening?
This sometimes happens if you recently spent your coin-age and the confirms are < 5 (see coin control depth of each UTXO).

Hi BBP gurus,
What does it means the following errors in getmininginfo output:

I have more than 125000 BBP in my wallet with enough age.

Any idea what the message means?

so jw if half the POG rewards that now go to POOM are basically burned coins until we reach peak POOM? or if there are only a few peopling using POOM do the coins go back to POG?

Yes: see "Heat Mining" section here:

https://wiki.biblepay.org/Quick_Start

is this coin still only CPU mining ?

** APOLLON Turnkey Sanctuary Hosting **


I have tested Apollon successfully and they work great!

To have your sanctuary hosted for only 99 cents per month (including hosting fees), navigate to:
https://www.apollon.network/

Click '+'.  Choose BiblePay.  Choose "Apollon Hosted Node".

*** Cameroon-One Go-Live ***


We are proud to announce our partnership with Cameroon-One and POOM (Proof of Orphan Mining) and this program will go live on September 5th, 2019.

In POOM you may sponsor a personal child directly with Cameroon-One (and this is a tax deductible contribution), and this personal sponsorship will reward you "points" daily in our GSC campaign for Cameroon-One, currently at a rate of 100%!

This means that you will receive $1.33 back per day in BBP rewards for sponsoring one child (at a rate of $40.00 per month currently).

Steps to sponsor a child:


1.  First ensure you already have a CPK (Christian public key).  If you do not have a CPK, type 'exec cpk your_desired_nickname' first.

2.  Type 'exec join cameroon-one' to join the campaign.

3.  From the core BBP wallet, type 'sponsorchild'.  After reading the warning, that BBP will charge a 50,000 BBP fee (this goes to our orphan sponsorship fund), then type 'sponsorchild authorize'.  (The 50K fee is a deterrent to keep people from sponsoring children they do not intend to pay for).

4.  You will receive a 6 character child ID.  Follow the instructions on the screen to know how to pay the monthly sponsorship fee (PayPal, Check, GlobalGiving Credit Card, or in BBP).  If you want to pay in BBP, you can send the BBP to Cameroons wallet at: BHRiFZYUpHj2r3gxw7pHyvByTUk1dGb8vz then e-mail Todd at: [email protected] with the child ID.  In our next release we will add this payment option to the wallet.

5.  To see the status of your child, type :  'listchildren'.  Please be patient, it can take up to 7 days for Cameroon to find a child for you.  In the mean time you can send a payment and pre pay for as many months as you desire (just remember to include the BBP Child-ID# with your payment).  While Cameroon is looking for a child, the wallet will say "Not Provisioned".  Once they find you a child, the balance will change to 0.  Once your payment is accepted by Cameroon, your balance will become a credit balance.  You will also receive a personal Bio URL for your child (it will appear in the listchildren output).

We currently cap our Cameroon-One emissions at the number of children sponsored * 1.33 per day (in USD).  You may sponsor more than one child.

! IMPORTANT !  It is extremely important that you either leave your miner running on one thread each day, or alternatively, type 'sendgscc cameroon-one' once per day.  This is necessary so that you are counted as a daily POOM participant.  If you miss a day you will miss out on the $1.33 reward for that day only.


Footnotes:

a.  Our POG campaign rewards have been reduced to 47.5% to make way for POOM rewards.  POOM rewards are currently 47.5% of the daily GSC budget.  The remaining 5% is still unchanged for Healing.

MacOS and Linux binaries ready.