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

[afeno]

Light (or anybody who knows), I have three questions regarding purepool.

1) Why I am not getting any payout on my account since two days:
https://pool.purepool.org/main/miner/BGeQ6eFaKZW6sBJbP98f6s4bsDV5BDHJov/

2) Can you please explain how this works:

Code:

Ratio:  Amount of your shares required until a block was found in average.

Do you mean: Average of shares required by the pool to find X blocks? What is the X (or timeframe)? Or is this "my" ratio?

Code:

Ratio/Percent	245.1610 %
Your ratio compared to the average of the pool. 100% = on the level of the pool. Values over 150% will increase your work difficulty. Lower values are better.

Why does it matter my ratio? If I found a block it will be distributed to the pool so I don't understand why to increase my difficulty. Increasing my difficulty will not help the pool. Right? How can I see "my" work difficulty?
My % is always over 150%. I don't understand why... Is this measure something similar to "Lucky"? If my lucky is good then it is better for the pool. Right?

3) I have 5 PCs that generate the same HPS than 1 PC. However, the 1 PC is giving me half of the Shares than the 5 PCs. Is it more efficient to have more low-CPUs PCs than 1 more powerful PC?

I know that you explained the point 2 some pages ago in this post but is still unclear for me.

BTW, what happened with the official pool? It is almost empty. I tried to mine on that one yesterday with my 3 workers but the workers and shares are disappearing.

And last but not least, one recommendation. Guys, after the last 20 BBP per RAC rule, you should make POW simpler to avoid people running away. The 10 Miners limit on the official pool and the 150% rule on purepool are just creating confusion and giving the impression that you don't want newcomers to join or invest (through POW mining) on BBP. Not everybody can buy a high amount of BBP through exchanges.

[1715028507]

1715028507

[1715028507]

1715028507

[aikida3k]

All things considered, the price of Biblepay is doing pretty well.  The exchanges aren't doing much volume but price is holding up well.  It's good the price is doing as well as it is during the crypto market turbulence.  I'm glad we have the incentive to stake per RAC.  If the price goes up in a rally by a good bit, the issue of what to stake is a good problem to have. 

[afeno]

Just to confirm, is it normal to get this error in poolinfo1,2 when the wallet is started doing solo mining?

Version 1.1.1.9

"poolinfo1": "Unable to sign CPID; Unable to sign CPID;
"poolinfo2": "Failed to sign CPID Signature (Address does not refer to key);


The error message disappears after some minutes (sometime several minutes...) but just to be sure if everything is fine.

Code:

getmininginfo
{
  "blocks": 39035,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 1010.599897722452,
  "difficulty_pow": 10051.92660872537,
  "difficulty": 1010.599897722452,
  "errors": "",
  "genproclimit": 24,
  "networkhashps": 1054849.209638178,
  "hashps": 121.905344207592,
  "minerstarttime": "04-06-2018 22:48:48",
  "hashcounter": 70581,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; ",
  "poolinfo2": "Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); ",
  "poolinfo3": "",
  "podc_tried": 0,
  "podc_sent": 0,
  "podc_sent_amount": 0,
  "podc_average_amount_sent": 0,
  "miningpulse": 1663,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
}

Code:

 exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "6f10570756afd25e02ca7d0ca6bf1a44",
  "Address": "BSbfoMQj5fGE2Jnmre4hjbeAKMMifuPueW",
  "CPIDS": "6f10570756afd25e02ca7d0ca6bf1a44;",
  "CPID-Age (hours)": 423071,
  "NextSuperblockHeight": 39155,
  "NextSuperblockBudget": 1179301,
  "6f10570756afd25e02ca7d0ca6bf1a44_ADDRESS": "BSbfoMQj5fGE2Jnmre4hjbeAKMMifuPueW",
  "6f10570756afd25e02ca7d0ca6bf1a44_RAC": 1524.29,
  "6f10570756afd25e02ca7d0ca6bf1a44_TEAM": 15044,
  "6f10570756afd25e02ca7d0ca6bf1a44_WCGRAC": 0,
  "6f10570756afd25e02ca7d0ca6bf1a44_TaskWeight": 100,
  "6f10570756afd25e02ca7d0ca6bf1a44_UTXOWeight": 8623,
  "Total_RAC": 1524.29,
  "Total Payments (One Day)": 118,
  "Total Payments (One Week)": 1025,
  "Total Budget (One Day)": 1179301,
  "Total Budget (One Week)": 8255107,
  "Superblock Count (One Week)": 8,
  "Superblock Hit Count (One Week)": 8,
  "Superblock List": "38950,38745,38540,38335,38130,37925,37720,37515",
  "Last Superblock Height": 38950,
  "Last Superblock Budget": 1179301,
  "Last Superblock Payment": 118,
  "Magnitude (One-Day)": 0.1000592723994977,
  "Magnitude (One-Week)": 0.1241655619969553
}

How can I ensure that solo mining is working fine?

Thank you!

[zthomasz]

https://wiki.biblepay.org/Create_Sanctuary_2

zthomas/jaapgvk can we to add this tutorials on main web? thanks

To back this up, I've created two sanctuaries in the last month, both using this guide. It's clear, it's simple to follow, and it works. I would highly recommend it.

I added the Create Sanctuary link to the website "Guides" section at https://www.biblepay.org/#guides

fyi .. Jaap & Togo & OrphanDefender (April/Bloom) are working hard behind the scenes planning and designing a new website. It will have more features, additional pages and content.

Let us know if you have any more suggestions.

[bible_pay]

Light (or anybody who knows), I have three questions regarding purepool.

1) Why I am not getting any payout on my account since two days:
https://pool.purepool.org/main/miner/BGeQ6eFaKZW6sBJbP98f6s4bsDV5BDHJov/

2) Can you please explain how this works:

Code:

Ratio:  Amount of your shares required until a block was found in average.

Do you mean: Average of shares required by the pool to find X blocks? What is the X (or timeframe)? Or is this "my" ratio?

Code:

Ratio/Percent	245.1610 %
Your ratio compared to the average of the pool. 100% = on the level of the pool. Values over 150% will increase your work difficulty. Lower values are better.

Why does it matter my ratio? If I found a block it will be distributed to the pool so I don't understand why to increase my difficulty. Increasing my difficulty will not help the pool. Right? How can I see "my" work difficulty?
My % is always over 150%. I don't understand why... Is this measure something similar to "Lucky"? If my lucky is good then it is better for the pool. Right?

3) I have 5 PCs that generate the same HPS than 1 PC. However, the 1 PC is giving me half of the Shares than the 5 PCs. Is it more efficient to have more low-CPUs PCs than 1 more powerful PC?

I know that you explained the point 2 some pages ago in this post but is still unclear for me.

BTW, what happened with the official pool? It is almost empty. I tried to mine on that one yesterday with my 3 workers but the workers and shares are disappearing.

And last but not least, one recommendation. Guys, after the last 20 BBP per RAC rule, you should make POW simpler to avoid people running away. The 10 Miners limit on the official pool and the 150% rule on purepool are just creating confusion and giving the impression that you don't want newcomers to join or invest (through POW mining) on BBP. Not everybody can buy a high amount of BBP through exchanges.

Hi Afeno,

Regarding the last point:  Yes, Light and I added some code to the core wallet yesterday and collaborated, this basically:
- Requires a heat miner to have magnitude and be in a prior superblock (A miner must have magnitude > 0 and payments > 1 in prior superblock to contribute to the pool shares) - This is because of the core wallet rule for solo miners
- Requires heat miner to not have solved recent blocks in the pool - A miner must Not have solved a block within the last 4 blocks with his signed CPID (this is because of the core wallet rule for solo miners)
- If the blocks becomes > 15 mins old, we do allow any POW shares to be submitted in the pool

Once this is deployed to the pools, then I can open the floodgates up (at least on pool.biblepay.org) and remove the 10 cpu max restriction.

Should be ready within a day or two.

[bible_pay]

Just to confirm, is it normal to get this error in poolinfo1,2 when the wallet is started doing solo mining?

Version 1.1.1.9

"poolinfo1": "Unable to sign CPID; Unable to sign CPID;
"poolinfo2": "Failed to sign CPID Signature (Address does not refer to key);


The error message disappears after some minutes (sometime several minutes...) but just to be sure if everything is fine.

Code:

getmininginfo
{
  "blocks": 39035,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty_podc": 1010.599897722452,
  "difficulty_pow": 10051.92660872537,
  "difficulty": 1010.599897722452,
  "errors": "",
  "genproclimit": 24,
  "networkhashps": 1054849.209638178,
  "hashps": 121.905344207592,
  "minerstarttime": "04-06-2018 22:48:48",
  "hashcounter": 70581,
  "pooledtx": 0,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; Unable to sign CPID; ",
  "poolinfo2": "Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); Failed to sign CPID Signature (Address does not refer to key); ",
  "poolinfo3": "",
  "podc_tried": 0,
  "podc_sent": 0,
  "podc_sent_amount": 0,
  "podc_average_amount_sent": 0,
  "miningpulse": 1663,
  "poolmining": false,
  "pool_url": "",
  "poolmining_use_ssl": false
}

Code:

 exec getboincinfo
{
  "Command": "getboincinfo",
  "CPID": "6f10570756afd25e02ca7d0ca6bf1a44",
  "Address": "BSbfoMQj5fGE2Jnmre4hjbeAKMMifuPueW",
  "CPIDS": "6f10570756afd25e02ca7d0ca6bf1a44;",
  "CPID-Age (hours)": 423071,
  "NextSuperblockHeight": 39155,
  "NextSuperblockBudget": 1179301,
  "6f10570756afd25e02ca7d0ca6bf1a44_ADDRESS": "BSbfoMQj5fGE2Jnmre4hjbeAKMMifuPueW",
  "6f10570756afd25e02ca7d0ca6bf1a44_RAC": 1524.29,
  "6f10570756afd25e02ca7d0ca6bf1a44_TEAM": 15044,
  "6f10570756afd25e02ca7d0ca6bf1a44_WCGRAC": 0,
  "6f10570756afd25e02ca7d0ca6bf1a44_TaskWeight": 100,
  "6f10570756afd25e02ca7d0ca6bf1a44_UTXOWeight": 8623,
  "Total_RAC": 1524.29,
  "Total Payments (One Day)": 118,
  "Total Payments (One Week)": 1025,
  "Total Budget (One Day)": 1179301,
  "Total Budget (One Week)": 8255107,
  "Superblock Count (One Week)": 8,
  "Superblock Hit Count (One Week)": 8,
  "Superblock List": "38950,38745,38540,38335,38130,37925,37720,37515",
  "Last Superblock Height": 38950,
  "Last Superblock Budget": 1179301,
  "Last Superblock Payment": 118,
  "Magnitude (One-Day)": 0.1000592723994977,
  "Magnitude (One-Week)": 0.1241655619969553
}

How can I ensure that solo mining is working fine?

Thank you!

Once the poolinfo1 & 2 errors dissapear (and you are confident your wallet is either unlocked, or you have the password entered correctly on boot), and the HPS is > 1, then you are solo mining, but remember to solo mine, you must have magnitude > 0 (you do) .

Looks good otherwise.

[bible_pay]

All things considered, the price of Biblepay is doing pretty well.  The exchanges aren't doing much volume but price is holding up well.  It's good the price is doing as well as it is during the crypto market turbulence.  I'm glad we have the incentive to stake per RAC.  If the price goes up in a rally by a good bit, the issue of what to stake is a good problem to have. 

Agreed, great job and great idea!

[bible_pay]

have a good day, team and project

God Bless You in Jesus Name.

https://wiki.biblepay.org/Jesus_Concise_Commandments

[bible_pay]

I have been running rosetta for weeks, but did not know i needed to keep biblepay open to get payouts. I downloaded 1.1.1.9, it is synced. my wallet conf. is as follows:

 addnode=dnsseed.biblepay-explorer.org

genproclimit=2

poolport=80

workerid=cjm_258

pool=http://pool.biblepay.org

gen=1

minersleep=

15:27:58

{
  "Command": "getboincinfo",
  "CPID": "b93d3a9d8d4dec7d72ab0189d793e1d0",
  "Address": "BRwp2t1LxDBj2skKQzzZ352yPmtD4Vmb6c",
  "CPIDS": "b93d3a9d8d4dec7d72ab0189d793e1d0;",
  "CPID-Age (hours)": 423068,
  "NextSuperblockHeight": 38335,
  "NextSuperblockBudget": 1179301,
  "b93d3a9d8d4dec7d72ab0189d793e1d0_ADDRESS": "BRwp2t1LxDBj2skKQzzZ352yPmtD4Vmb6c",
  "b93d3a9d8d4dec7d72ab0189d793e1d0_RAC": 1181.95,
  "b93d3a9d8d4dec7d72ab0189d793e1d0_TEAM": 15044,
  "b93d3a9d8d4de
  "Last Superblock Height": 38130,
  "Last Superblock Budget": 1179301,
  "Last Superblock Payment": 0,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0
}
what am i missing??

Try typing in the debug console

Code:

exec podcupdate true

See what it tells you

Take a look at the pool superblock view report.  your cpid is showing at 20% UTXO now.  You probably ran the command too fast in the wallet - it takes 6 confirms.

[afeno]

Once this is deployed to the pools, then I can open the floodgates up (at least on pool.biblepay.org) and remove the 10 cpu max restriction.

Should be ready within a day or two.

Thank you Rob. Please let us know when this is implemented so we can test it.
What is important for me is to ensure that the workers are not disappearing from the pool and losing all the shares without knowing why.

[bible_pay]

THE GREAT TRIBULATION:

https://wiki.biblepay.org/The_Great_Tribulation

[znffal]

Hi Rob!

I added a feature request
https://github.com/biblepay/biblepay/issues/16

Thanks!

[bible_pay]

THE RICH MAN:

https://wiki.biblepay.org/THE_RICH_MAN

[tmike]

Mining/PoDC chatbox enabled on bbppodc.org website!

[SEO_Account]

Mining/PoDC chatbox enabled on bbppodc.org website!

High Risk Website Blocked
bbppodc.org
Access to this page is blocked as the threat Mal/HTMLGen-A has been found on this website.

[slovakia]

SEO_Account what AV?

[seeksilence1]

Is there a way to control cpu usage?

[znffal]

Is there a way to control cpu usage?

For Rosetta/Boinc, or BBP wallet?

[Lichtsucher]

1) Why I am not getting any payout on my account since two days:
https://pool.purepool.org/main/miner/BGeQ6eFaKZW6sBJbP98f6s4bsDV5BDHJov/

I will have a look at this. Anybody else have this problem?

2) Can you please explain how this works:

Code:

Ratio:  Amount of your shares required until a block was found in average.

Do you mean: Average of shares required by the pool to find X blocks? What is the X (or timeframe)? Or is this "my" ratio?

It is a value to show the quality of your miners/shares compared to others.

Why does it matter my ratio? If I found a block it will be distributed to the pool so I don't understand why to increase my difficulty. Increasing my difficulty will not help the pool. Right? How can I see "my" work difficulty?
My % is always over 150%. I don't understand why... Is this measure something similar to "Lucky"? If my lucky is good then it is better for the pool. Right?

I'm not completely sure if it look or some question of configuration. What I can say: There are some miners whos solutions create blocks with much less shares then the average, and others need a LOT more shares for the same work.
This system is designed to even out the difference, to make it fair for everybody.
Or in other words: Without that system, I would have to kick out everybody with a bad ratio. This way, they can stay and still get a fair share.
But I can not answer the "why is the ratio different". It might be luck, or something else "nobody" understood yet.

By the way, you can not see your difficulty. I just changed the inner working of this, away from HashTarget Difficulty to the validation of the solutions send by the client. This is still in testing, we will see if it works good.

3) I have 5 PCs that generate the same HPS than 1 PC. However, the 1 PC is giving me half of the Shares than the 5 PCs. Is it more efficient to have more low-CPUs PCs than 1 more powerful PC?

You should check your configuration, maybe genproclimit is wrong? On all of my systems, the amount of shares is exactly what I would expect from the calculation power

And last but not least, one recommendation. Guys, after the last 20 BBP per RAC rule, you should make POW simpler to avoid people running away. The 10 Miners limit on the official pool and the 150% rule on purepool are just creating confusion and giving the impression that you don't want newcomers to join or invest (through POW mining) on BBP. Not everybody can buy a high amount of BBP through exchanges.

The 150% rule is not there to confuse people, but it is required for a healthy pool. I had disabled it in silent in the last 3 days, but immediately people saw that and tried to get an advantage. This is a normal problem for pools, as often people will try to fake things and the pool needs to "answer" that. I added the ratio on the statistics for transparency.

By the way, you can always see the inner workings of the Purepool in the Github repository (https://github.com/Lichtsucher/purepool). There is nothing hidden

[afeno]

There are some miners whos solutions create blocks with much less shares then the average, and others need a LOT more shares for the same work.
....
But I can not answer the "why is the ratio different". It might be luck, or something else "nobody" understood yet.

Thank you Light. Please let us know if you discover anything regarding the two sentences above.