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

** Important Hash Check **

Before diving deep into the problem, first I would like everyone to check their hashes Asap,

getblockhash 129815
Verify the hash is:
85f39c01a397afcdb744e170d8decb0dd90f2e6473f0f31da8e1456105557aa9

If it is not, your node is on the light chain.
To fix this, no need to restart, please paste this into console:

reconsiderblock da101042c3cac70bd06d674a71e6b163f05a8e48cd308518ce94a89e60c9df0c

After that, your node will reorganize (it takes about 15 secs), then you can check the hash and you will see the diff is now > 5.5K and you are on the heavy chain.

I will explain this situation in detail, so we can permanently prevent this in the future.

The correct hash is actually the d3718* hash above for 129,800 and chainz is on a fork, due to an issue that I will explain in detail.

Fortunately the issue appears to be small (as CX, SX, the global Sanc report, and the foundation nodes are all on the d3718* "heavier" chain).

To work this out, I temporarily* disabled ABN, to build up the heavy chain back above a 10K diff, and let us work this off.

I will explain this situation in detail in the upcoming post(s).

Which block hash is correct?


Block #129800

explorer.biblepay.org:

d3718aba0f125d3ef6e52539dfbc488d0c50c936ceb43cf25ef151aae8759260

chainz.cryptoid.info:

600c462300ea6738708c0502e8ccf414791ead010eb828e8d7890aa54b6bfd09

Yes, and btw, if we have any cost cutting people out there, you can set it as low as .26 and it will still count the tithe.  Below .25 and the tithe is ignored (only due to preventing spam).

Oh so it only donates 5bbp per day by default?  That's easily manageable.   Thanks!

Thanks for all that info!
Yes, I can see you have plenty of ABN weight.  We are getting closer to resolving this now.

So it appears that the biblepay.conf file you changed is not the one being used.
The reason I say this is your getmininginfo shows genproclimit:1 but your file shows 4 (and 256).

You can actually first simulate genproclimit 20 by doing this:
setgenerate true 20

Then watch your CPU utilization.  If it rises higher than you have seen, then its obviously your config file.
(Plus you are not getting the benefit of minersleep=0 either, since that is not being read).


So if you confirm the above works, I recommend closing biblepay, and navigate to:
cd %appdata%\biblepayevolution
Take a look at the debug.log.  Was it just written to (timestamp is now)?

Then make a new biblepay.conf file, make sure its in the same directory as the debug.log you just checked, and make sure it does not have a double file extension (ie .conf.txt), and was created in notepad with CRLFs between each row.

Resave it and restart.

If you did the 'exec cpk nickname' and 'exec join pog', now you are in the POG campaign.  (Tithe=1 is no longer necessary).

The wallet will send a GSC transmission (this contains your stake-age) for the POG campaign once every 12 hours, but only if you are mining and your wallet is unlocked.

By default it sends a 2.50 tithe each time.  You can override this with this key:
https://wiki.biblepay.org/Getting_Started_with_Evolution
(Look for overriding POG).

Yes, the wallet would actually drain to 0 if a person left it mining, and each 2.50 tithe spent the bbp.
But you can do an 'exec roi' to see the effects of tithe amounts up front.

Also, if a person does not want to tithe they can set the override value to 0 (or do 'exec unjoin pog').

addnode=explorer.biblepay.org
gen = 1
genproclimit = 4
minersleep = 0
---------------------------
exec getabnweight 100000
{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 18824968.40258104,
  "total_required": 167652,
  "weight 100000.00": 2915882.193784723,
  "total_required 100000.00": 25997
}
------------------------------------
getmininginfo
{
  "blocks": 129763,
  "currentblocksize": 13741,
  "currentblocktx": 12,
  "difficulty": 3026.147186147186,
  "errors": "",
  "pooledtx": 11,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 454381.3860180424,
  "hashps": 756.1770107697015,
  "minerstarttime": "07-05-2019 08:08:16",
  "hashcounter": 13828944,
  "pooledtx": 11,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "abninfo": "",
  "gsc_errors": "",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 100000
}
--------------------------
my CPU is only 2% active....

Sorry if this has been discussed in the past, couldn't find any info on it in the Wiki.  I know the concept of PoG, that you give BBP to orphans and you can get rewarded for it, so it's an incentive to donate to the poor.  I also know the way to set it up is to add tithe=1 to the wallet config file, but other than that I'm not sure what else needs to be done.  How often does it donate BBP and how much does it donate?  I have no problem giving to the needy but is there any possibility of it completely draining my wallet if I'm not mining fast enough to make up for the donations?  Thanks!

This leaderboard reconciliation is an easy one; first on the amount owed as compared to the prominence matching it up - no that was actually fixed and you should not have a problem at all in that area.  If you look at the prominence %, say its .10 for someone, and knowing the daily superblock value (its usually about 950K) that would equal a 95,000 bbp reward.
But specifically TrumpFan as compared to you:  We have 2 campaigns in prod : Pog & healing.  Hes in Healing (Healing gets 5% of the GSC per day).  So click on "DETAILS VIEW", and scroll up to Trump Fan - and notice today he is the only one with a healing diary entry (Im slacking today as Im working in Develop lol).  So he has this 46.7K boost.  Then you can clearly see all the other prominence % lines up relative to each other.

Yes, on our GSC rewards as compared to Sancs, I agree, we are talking about a 500% higher payout ratio for locked up BBP in the GSC land right now.  Thats very surprising to me, in that POG/Healing pays so much, I expected to see at least 2-3 new users per day in the leaderboard jumping in and evening this out.   We have had about 33 participants a day, and we are going sideways.  I make a bold call:  this wont last too long, as both POBH mining is very profitable right now ($50 per month per PC), GSC is 500% too profitable, etc.  So the only way out is that we pick up new users.  I predict that we will double our user base by Christmas, as long as this profitability continues.  But yes, people would not want to start a new sanc right now with the BBP, they would want to use it in POG until POG gets less profitable.

Please let us know if what we mentioned for Gilligan_M fixed your issue too, or if you are still mining slow.  If so please post the same info I asked for Gilligan to post.

Other than verifying you are synced with this same chain hash:
https://chainz.cryptoid.info/bbp/
(As that would make you go to 99% error ratios on the pool if you are out of sync)

Could you also post your 'exec getabnweight 100000' results?

The pool also requires you to have unspent ABN weight for each new block created.

Thanks.

PS I see you already have minersleep=0, so like JSheets said, double check the biblepay.conf is in the same directory as your last timestamp modified debug.log.  If that wasn't it we can work through the getabnweight, to see if your miner is stopping and starting.  You can restart your miner with 'setgenerate true 5' and quickly look at getmininginfo for errors.  (Or check your log for errors).

"Won't fail so frequently"
->  You can ask Capulo, he's been mining with 40 machines for a year straight against the pool, so it's definitely some technical issue that can be solved if we work through it.  (Not something that is systemically affecting the whole community).  Granted, ABN is new and we could be exploiting new unchartered areas.

I will need your pool handle to figure this out.  Could you either PM me or email me at [email protected] and Ill tell you whats happening to the hashpower etc.

Looks like you just needed a little more good old fashioned patience.

I'd appreciate if you could jump in and help others also, like those who are having trouble mining;  one thing you can do is ask them questions and analyze the problem(s) - this way we can grow as a community.

Thanks Tiras!

Rob, I'm still not exactly sure how the POG leaderboard works. For example I currently have "owed" coins 561.1 with a prominence of 0.6. This is the exakt same amount like someone called "trumpfan" has.
However, I have more than 20x the amount of "points" on the leaderboard than him. So how do these translate to the owed amount? Or is this just another hickup in the time frame of both columns?

Also, talking to a friend of mine who hasn't enough BBP for the new masternodes, it seems like just doing POG pays a lot better than the sancs. He made several hundered thousand BBP in one week. Of course this will slowly decrease with his lower coin age, but it's still orders of magnitude higher than sanc payments.

I just try different genproclimit since i cant maximized my CPU.. I also check the path... 

When I attempted to set my miner to genproclimit 60+ it gave constant warnings that 60 was the highest it could go.
I don't know if that's the case anymore since I've then figured out how to to set the appropriate threads (I use 7 for 7 threads, 8 puts my CPU at 100% and locks it up.) Intel core i7, 4790k, quad core w/ 8 threads.

Looks to me like the miner is using a different configuration. What is full path to this configuration file and what is the command you are running to start the miner

Hi, I have been mining / attempting to mine for a while now, but something is catching my attention now.

I have the required ABN weight, but I usually get "ghosted" by the pool. Such as, my miner continues to run and hash, but the pool no longer recognizes my miner / stops paying me / says my miner is missing. Where is my hashpower going?

When I am ghosted, I can restart my wallet / miner and it works fine for about 5-10 minutes, before being ghosted again. If I'm not ghosted, the miner/wallet randomly and abruptly close itself (dissapear from the tray / just turn off completely.)

https://imgur.com/a/mZ4Wu5D

Is it a wallet issue?

I'm not looking to troll or hinder the project, as I am interested in continuing to mine, but I need an application that won't fail so frequently.

wallet running on win 10 64bit

I have this in my wallet configuration

addnode=explorer.biblepay.org
genproclimit=256
gen=1
minersleep=0

but my cpu is only using 10-25% and genproclimit is still 1..  i tried several values.. like 4, 16..  restart pc after but no efffect. Whats wrong?

getinfomining...
blocks": 129551,
  "currentblocksize": 1502,
  "currentblocktx": 1,
  "difficulty": 2070.207305034551,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 383570.8021583835,
  "hashps": 756.1588006589133,
  "minerstarttime": "07-04-2019 00:23:29",
  "hashcounter": 35825303,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
  "abninfo": "",
  "gsc_errors": "",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 100000