[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[mdude77]

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

[1715092160]

1715092160

[1715092160]

1715092160

[1715092160]

1715092160

[1715092160]

1715092160

[1715092160]

1715092160

[1715092160]

1715092160

[yslyung]

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

i'm talking abt the conf cmds not bmt (settings) that keeps on raising their prices $ suckerz yes it's sp's game now !

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.

[mdude77]

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

i'm talking abt the conf cmds not bmt (settings) that keeps on raising their prices $ suckerz yes it's sp's game now !

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.

I'm not talking about the / command.  I'm talking about the - command to raise the psuedo share difficulty going to the miner.

/ never made sense to me.

M

[Chupacabras]

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

I wanted to get Spondoolie, I was not 100% Sure since everyone talks about Antminers I went with it. I will be buy one to test it out.
Have anyone taking a look at this? https://bitgrade.net/shop/ Just ran it to it. But Im really skeptical about it.

[mdude77]

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

I wanted to get Spondoolie, I was not 100% Sure since everyone talks about Antminers I went with it. I will be buy one to test it out.
Have anyone taking a look at this? https://bitgrade.net/shop/ Just ran it to it. But Im really skeptical about it.

Looks like a scam site to me.

I suggest buying directly from Bitmain.  If you ask around, someone might have a coupon they can give/sell you as well to help the cause.

M

[yslyung]

i
d suggest to buy directly from the manufacturers. highly trusted resellers or members that have proven tack record but i would always get it direct.

[jonnybravo0311]

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.

Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

Setting "/" does affect your payout IF you set it to a value higher than the current p2pool share difficulty.  Setting it to 1000 makes no difference.  Setting it to 1000000000 would certainly make a difference.  This parameter tells p2pool, "I don't care what you think the share difficulty to get on the chain should be.  You will use the difficulty I provide and weight any shares I submit accordingly."  Unless you have a miner that could potentially be submitting shares faster than every 30 seconds, there is really no reason to use this parameter.

[mdude77]

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.

Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

In an ideal world this would be true.  But with flaky bitmain hardware, setting the pseudo share difficulty will decrease your rejects, which will/may affect your payout.

M

[jonnybravo0311]

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.

Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

In an ideal world this would be true.  But with flaky bitmain hardware, setting the pseudo share difficulty will decrease your rejects, which will/may affect your payout.

M

You're correct, and I should have pointed out that caveat.  Also, for some reason with Bitmain's web UI, if you use a power of 2 for your pseudo difficulty, best share value will always be 0.  However, if you use any other value it works just fine.  Bitmain definitely has some peculiar issues with their hardware, firmware and software.

[mdude77]

the current share diff CANNOT be changed by using pseudo share diff (max is 999.98) (it only changes the share diff to the miner not the diff set by  p2pool)

p2pool share diff can be lowered by using the "/"

do correct me if i'm wrong.

Setting "+" has no effect on your payouts at all.  It simply makes the graphs prettier or spikier depending on the value you set.  The smaller the value, the more data points p2pool considers for your miner, the smoother the graph.

In an ideal world this would be true.  But with flaky bitmain hardware, setting the pseudo share difficulty will decrease your rejects, which will/may affect your payout.

M

You're correct, and I should have pointed out that caveat.  Also, for some reason with Bitmain's web UI, if you use a power of 2 for your pseudo difficulty, best share value will always be 0.  However, if you use any other value it works just fine.  Bitmain definitely has some peculiar issues with their hardware, firmware and software.

Bitmain has peculiar issues everywhere!!

M

[Chupacabras]

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

Thank you all for fast responds and help. Now im seen some improvement from 0.03 to 0.05 almost 0.06. Now im running @ 5.5 Ths Is that about the right pay?

[windpath]

tbh, if you're not sure what does those commands do, best is to leave it at defaults. ain't broken don't fix it as the old saying goes but no harm trying.

Edit: And there is really no need to set diff for your miners. P2Pool does an ok (not excellent) vardiff job.

I disagree with that statement.  Bitmain hardware, which a lot of people use, do not like two things:

1 - frequent work restarts.  p2pool averages a restart every 30 seconds.  setting the queue to 1 significantly helps the issue, but when you compare the results with spondoolie hardware, Bitmain sucks
2 - frequent share difficulty changes.  that's the same as #1 when the difficulty increases, causing "low difficulty" work to be submitted and subsequently rejected

You can fix #2 easily enough by setting a fixed pseudo share difficulty.

M

Thank you all for fast responds and help. Now im seen some improvement from 0.03 to 0.05 almost 0.06. Now im running @ 5.5 Ths Is that about the right pay?

That sounds about right. Keep in mind your expected payout can and will fluctuate based on your share submission luck/variance.

You can always find your miner in the active miners tab and see how your luck is holding:

http://minefast.coincadence.com/p2pool-stats.php

If your hashrate reported here is higher than actual you are currently lucky

If your hashrate is lower than actual you are currently unlucky.

[jonnybravo0311]

Thank you all for fast responds and help. Now im seen some improvement from 0.03 to 0.05 almost 0.06. Now im running @ 5.5 Ths Is that about the right pay?

The actual payout depends on the weight of the share when it was found.  It's easy to calculate how many shares you should expect to find, but remember, the share difficulty is constantly changing.  That means the share weights are constantly changing and the expected time to find a share is also constantly changing.

Let's assume a share difficulty of 10000000.  With your 5.5TH/s, you would expect to find a share every 2.17 hours or so, or about 11 shares a day.

[jcumins]

Ok all you smart miners,.


I am running Bitmain S1,S2 and S3 and soon to be S5 miners. I have set the Queue setting to Queue=0  in all the miners i am able to set.   My node averages 105% efficiency and average number of shares is approximately 20 shares in 24 hours.  I have 8.7TH  hash power

It seems I am running very consistent,  and I was wondering is it better to set queue=0 or queue=1. There seems to be some difference of opinion.

So please chime on with facts if possible.

Thanks

[idonothave]

Ok all you smart miners,.


I am running Bitmain S1,S2 and S3 and soon to be S5 miners. I have set the Queue setting to Queue=0  in all the miners i am able to set.   My node averages 105% efficiency and average number of shares is approximately 20 shares in 24 hours.  I have 8.7TH  hash power

It seems I am running very consistent,  and I was wondering is it better to set queue=0 or queue=1. There seems to be some difference of opinion.

So please chime on with facts if possible.

Thanks

read this: https://bitcointalk.org/index.php?topic=671189.msg8045025#msg8045025

[mdude77]

Ok all you smart miners,.


I am running Bitmain S1,S2 and S3 and soon to be S5 miners. I have set the Queue setting to Queue=0  in all the miners i am able to set.   My node averages 105% efficiency and average number of shares is approximately 20 shares in 24 hours.  I have 8.7TH  hash power

It seems I am running very consistent,  and I was wondering is it better to set queue=0 or queue=1. There seems to be some difference of opinion.

So please chime on with facts if possible.

Thanks

The facts appear to be that there is no difference.

M

[bhanu545]

The facts appear to be that there is no difference.

M

Hey mate,

I have a weird case with my 3 antminer s4's. I am in p2pool since a month and was receiving decent payouts than any other pool. I used custom cgminer built by ckolivas and made changes to que size=1. Here comes the big difference.

Before the p2pool took 4days+ to find a block, my 6TH gave me like 0.1btc, 0.2btc etc for 4days. after that recently when there was no block found in 4th day my payout became BLANK. nothing displays, it was like that for 12hours and i changed the pool completely to come back when a block is found.

Finally after a block is found in p2pool i pointed my miner back again to same old p2pool node but with different btc address as worker name. Ran it for 1.5hours and still no earnings. I got mad and changed to btcguild. Its been 24hours i ran my miners on node for 1.5hours yesterday. no sign of earnings at all.

Is it something with the custom cgminer which is the problem here? or is it something with my node? or pool?

I am really confused and dont want to leave p2pool because i know this is the best but weird things r worrying me.

Thanks

[mdude77]

The facts appear to be that there is no difference.

M

Hey mate,

I have a weird case with my 3 antminer s4's. I am in p2pool since a month and was receiving decent payouts than any other pool. I used custom cgminer built by ckolivas and made changes to que size=1. Here comes the big difference.

Before the p2pool took 4days+ to find a block, my 6TH gave me like 0.1btc, 0.2btc etc for 4days. after that recently when there was no block found in 4th day my payout became BLANK. nothing displays, it was like that for 12hours and i changed the pool completely to come back when a block is found.

Finally after a block is found in p2pool i pointed my miner back again to same old p2pool node but with different btc address as worker name. Ran it for 1.5hours and still no earnings. I got mad and changed to btcguild. Its been 24hours i ran my miners on node for 1.5hours yesterday. no sign of earnings at all.

Is it something with the custom cgminer which is the problem here? or is it something with my node? or pool?

I am really confused and dont want to leave p2pool because i know this is the best but weird things r worrying me.

Thanks

Sounds to me like your payout address wasn't set right as your username?

M

[bhanu545]

The facts appear to be that there is no difference.

M

Hey mate,

I have a weird case with my 3 antminer s4's. I am in p2pool since a month and was receiving decent payouts than any other pool. I used custom cgminer built by ckolivas and made changes to que size=1. Here comes the big difference.

Before the p2pool took 4days+ to find a block, my 6TH gave me like 0.1btc, 0.2btc etc for 4days. after that recently when there was no block found in 4th day my payout became BLANK. nothing displays, it was like that for 12hours and i changed the pool completely to come back when a block is found.

Finally after a block is found in p2pool i pointed my miner back again to same old p2pool node but with different btc address as worker name. Ran it for 1.5hours and still no earnings. I got mad and changed to btcguild. Its been 24hours i ran my miners on node for 1.5hours yesterday. no sign of earnings at all.

Is it something with the custom cgminer which is the problem here? or is it something with my node? or pool?

I am really confused and dont want to leave p2pool because i know this is the best but weird things r worrying me.

Thanks

Sounds to me like your payout address wasn't set right as your username?

M

For example, If you consider my previous worker in p2pool node. It earned too much for 5 days and earnings became blank later on. Dont know why.

The new btc address is correct and still no earnings after mining for 1.5hour. It also showed graphs of hashrate. I waited more than 24hours but still no sign of earnings.

I doubt the node owner did some changes or pool itself has problems giving out earnings.

Whats your opinion on this?

[mdude77]

The facts appear to be that there is no difference.

M

Hey mate,

I have a weird case with my 3 antminer s4's. I am in p2pool since a month and was receiving decent payouts than any other pool. I used custom cgminer built by ckolivas and made changes to que size=1. Here comes the big difference.

Before the p2pool took 4days+ to find a block, my 6TH gave me like 0.1btc, 0.2btc etc for 4days. after that recently when there was no block found in 4th day my payout became BLANK. nothing displays, it was like that for 12hours and i changed the pool completely to come back when a block is found.

Finally after a block is found in p2pool i pointed my miner back again to same old p2pool node but with different btc address as worker name. Ran it for 1.5hours and still no earnings. I got mad and changed to btcguild. Its been 24hours i ran my miners on node for 1.5hours yesterday. no sign of earnings at all.

Is it something with the custom cgminer which is the problem here? or is it something with my node? or pool?

I am really confused and dont want to leave p2pool because i know this is the best but weird things r worrying me.

Thanks

Sounds to me like your payout address wasn't set right as your username?

M

For example, If you consider my previous worker in p2pool node. It earned too much for 5 days and earnings became blank later on. Dont know why.

The new btc address is correct and still no earnings after mining for 1.5hour. It also showed graphs of hashrate. I waited more than 24hours but still no sign of earnings.

I doubt the node owner did some changes or pool itself has problems giving out earnings.

Whats your opinion on this?

Can you post a screenshot of your pool settings from your S4?

M