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

[eternalenvoy]

So now someone knows what is the correct number block currently? 

[bible_pay]

The older Ubuntu PPA compiles the new release right now. After that is finished, Purepool will be updated (again...)

what about other releases? i was trying some i think 17.04 ubuntu and there was only 1.1.3.8 or so ...

WHYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY.
WHY should anyone go to this forum thread and WASTING its precious time, energy and resources, going through this non-sense fucked up bullshit...

WHYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY?
WHY YOU should go to this forum and WASTE your precious time, energy and resources, going through this non-sense fucked up bullshit...?

 

If it is something that you are not interested in then GO AWAYYYYY

We're doing it for the orphans and extending God's Kingdom into the crypto world - I don't think I ever said it directly, but it was clearer when we first launched:

At the time BTC was using a lot of energy to mine, Dash had governance.

If we can be a solid crypto based on Dash-governance and even tap 1% of the market share and provide a good service, we could sponsor 65,000 orphans per month (and still be deflationary).  The possibilities are endless here.  

Sure we are going through a rough time now, but I do see out of all the code we checked in over the last year, a good percentage of it is still going to be useful in Evolution on the Sanc side, so its not true that we aren't contributing to the crypto community.  I'm confident everyone will see this perspective when we write the Wiki page for our smart contract in 2 weeks.  Its simply not true that we're throwing away everything we've accomplished through 2018.  We will talk about it in detail.

We're not dying, we are just going through birth pains!

[bible_pay]

So now someone knows what is the correct number block currently? 

It looks like this chain is the most:
"height": 107158,
    "hash": "5b75ec85f8288341a3f3837d20a7e824b8c9e22ac1fc049432020acf4bbc3312",

But let me see if my sancs have all gone to agreement yet.

[bible_pay]

So here is something that goes against what the naysayers are saying: 
Out of all those masternode coins on GIN, according to my conversation with TTS, we would be the first Evolution based coin to upgrade after Dash according to our testnet schedule (IE Evo is only 6 days away from being tested in testnet at biblepay).  If we are so "worthless" then why are we first?  (Hmmm... ) Maybe its because we are actually competent, yes we don't look good when we are stuck in a ditch, but as Christians we should help each other out of the ditch.

And I just want everyone to know that got banned, I will forgive you and not hold a grudge, if you repent for your past behavior and send me an e-mail or a PM with a true repentant heart.  Then I would have mercy and remove you from the ban list. 

[pagalo]

@bible_pay

Why the CPU load is about 10% with the same settings that a few days ago was 75%???

I have  i5 7400 Windows 10

gen=1
genproclimit=3
minersleep=0

[bible_pay]

@bible_pay

Why the CPU load is about 10% with the same settings that a few days ago was 75%???

I have  i5 7400 Windows 10

gen=1
genproclimit=3
minersleep=0

Before I answer, A) Are you solo or pool mining, B) does it go to 100% when you do the genproclimit 20?

[pagalo]

@bible_pay

Why the CPU load is about 10% with the same settings that a few days ago was 75%???

I have  i5 7400 Windows 10

gen=1
genproclimit=3
minersleep=0

Before I answer, A) Are you solo or pool mining, B) does it go to 100% when you do the genproclimit 20?

I do solo mining.
I tried genproclimit=15 but still nothing.
I'll try 20.

[pagalo]

@bible_pay

Why the CPU load is about 10% with the same settings that a few days ago was 75%???

I have  i5 7400 Windows 10

gen=1
genproclimit=3
minersleep=0

Before I answer, A) Are you solo or pool mining, B) does it go to 100% when you do the genproclimit 20?

I do solo mining.
I tried genproclimit=15 but still nothing.
I'll try 20.

I tried 20. Still under 10%

THis is my conf.

addnode=explorer.biblepay.org

gen=1
genproclimit=20
poolport=80
workerid=
pool=https://pool.biblepay.org

minersleep=0

tithe=10
nickname=pagalo
tithing=10

[bible_pay]

So regarding POW *pool* mining, I did find a problem where the pool was showing "0" difficulty (after the upgrade) : FIXED.

Lict, please check PurePool also to make sure your POW difficulty is being inducted properly for each share.  

It looks like things are now returning to normal:  50 sancs just went to enabled and my personal sancs are in a quorum on the high diff chain.

Great work everyone!

Pagalo, let me look at solo mining.

Current chain seems to be swarming on:
"height": 107164,
    "hash": "7ad0be50377b2bbc104175a453915080d80a92a0dda354819bdade465e934c50",
    "difficulty": 2480.294495941811,

[bible_pay]

@bible_pay

Why the CPU load is about 10% with the same settings that a few days ago was 75%???

I have  i5 7400 Windows 10

gen=1
genproclimit=3
minersleep=0

Before I answer, A) Are you solo or pool mining, B) does it go to 100% when you do the genproclimit 20?

I do solo mining.
I tried genproclimit=15 but still nothing.
I'll try 20.

I tried 20. Still under 10%

THis is my conf.

addnode=explorer.biblepay.org

gen=1
genproclimit=20
poolport=80
workerid=
pool=https://pool.biblepay.org

minersleep=0

tithe=10
nickname=pagalo
tithing=10

Before I look into the minersleep subprocedure could you please do me a favor: 
Please comment out "pool" by putting an x in front of it , and an x in front of workerid.  Then restart and try again and let me know if its still 10%.

Its possible the code is re-trying the pool once per outer loop.

[pagalo]

Yes that's the block and hash

[bible_pay]

I just asked GIN to upgrade sancs:
https://github.com/biblepay/biblepay/releases/tag/1.2.0.1

Lets wait a couple days and verify everything before we consider re-enabling the exchanges.

[pagalo]

I changed conf to this

addnode=explorer.biblepay.org

gen=1
genproclimit=20

minersleep=0

tithe=10
nickname=pagalo
tithing=10

CPU load still about 10%. It varies from 5.5% to 13%

[bible_pay]

I changed conf to this

addnode=explorer.biblepay.org

gen=1
genproclimit=20

minersleep=0

tithe=10
nickname=pagalo
tithing=10

CPU load still about 10%. It varies from 5.5% to 13%

Ok, on a side note, Im at 50% load on my windows box with genproclimit=20 (as a test), but let me look at the minersleep code, hang on.

[thesnat21]

So now someone knows what is the correct number block currently? 

It looks like this chain is the most:
"height": 107158,
    "hash": "5b75ec85f8288341a3f3837d20a7e824b8c9e22ac1fc049432020acf4bbc3312",

But let me see if my sancs have all gone to agreement yet.

All my clients are on this chain now .

Throwing some extra miners on it as well.

[bible_pay]

I changed conf to this

addnode=explorer.biblepay.org

gen=1
genproclimit=20

minersleep=0

tithe=10
nickname=pagalo
tithing=10

CPU load still about 10%. It varies from 5.5% to 13%

While Im testing this please try:
minersleep=-1

And genproclimit=30

Lets see if it goes above 50%.   Im trying genproclimit=40 and seeing 93% cpu use in win7.

One other thing you can try is running the 32bit version (as a test) on your machine and see if it rises.

Let me test some minersleep settings on my box.

[bible_pay]

I changed conf to this

addnode=explorer.biblepay.org

gen=1
genproclimit=20

minersleep=0

tithe=10
nickname=pagalo
tithing=10

CPU load still about 10%. It varies from 5.5% to 13%

While Im testing this please try:
minersleep=-1

And genproclimit=30

Lets see if it goes above 50%.   Im trying genproclimit=40 and seeing 93% cpu use in win7.

One other thing you can try is running the 32bit version (as a test) on your machine and see if it rises.

Let me test some minersleep settings on my box.

With minersleep=-1,  the tithe parameters removed, and genproclimit=10 Im seeing 100% cpu use on windows7.

Please try that.

[capulo]

So now someone knows what is the correct number block currently? 

It looks like this chain is the most:
"height": 107158,
    "hash": "5b75ec85f8288341a3f3837d20a7e824b8c9e22ac1fc049432020acf4bbc3312",

But let me see if my sancs have all gone to agreement yet.

All my clients are on this chain now .

Throwing some extra miners on it as well.

wow all my 7 wallets are on this chain also...
going to add remaining PCs... seems good now

[bible_pay]

So now someone knows what is the correct number block currently? 

It looks like this chain is the most:
"height": 107158,
    "hash": "5b75ec85f8288341a3f3837d20a7e824b8c9e22ac1fc049432020acf4bbc3312",

But let me see if my sancs have all gone to agreement yet.

All my clients are on this chain now .

Throwing some extra miners on it as well.

wow all my 7 wallets are on this chain also...
going to add remaining PCs... seems good now

Yeah it was the chicken & egg problem.  You cant have Sancs agreeing on the payment height without a POW consensus, and we couldnt have a POW consensus without Sancs telling us the exact list of sanc-public-addresses and amounts to pay (so we went in loops).  Then we disabled the payment checking rule and made it into a future spork rule - and now the nodes at the highest height are not rejecting blocks, and now the sancs are coming back online.

[bible_pay]

Its very clear when you look at the code that was checked in on 1.2.0.1 and it fixed the problem.