Topic: [ANN][DGC][WDC][CRC][CSC][P2Pool] xPool.net - page 4. (Read 22464 times)
Looks like you finally got some shares and are on the payout list
Well that's disappointing. Last week I made about 0.50 LTC per day for several days. I guess it's time to move on to a different pool.
I do not think that first number in cgminer reflects that it is an actual accepted share. Checking the documentation for cgminer it says:
With ~200 Kh/s it may take a while to have an accepted share on an LTC p2pool. This will only get worse when the LTC p2pool switches to a minimum payout threashold (very soon). They did this to minimize the quantity of "dust" payments but it also increases the variance of payouts for smaller miners. They say it should even out over time but I would recommend a PPS LTC pool for anyone under 300 Kh/s.
Quote
The 2 diff values are the actual difficulty target that share reached
followed by the difficulty target the pool is currently asking for.
followed by the difficulty target the pool is currently asking for.
With ~200 Kh/s it may take a while to have an accepted share on an LTC p2pool. This will only get worse when the LTC p2pool switches to a minimum payout threashold (very soon). They did this to minimize the quantity of "dust" payments but it also increases the variance of payouts for smaller miners. They say it should even out over time but I would recommend a PPS LTC pool for anyone under 300 Kh/s.
If the minimum difficulty for a share is 1, then if I find a share reported by cgminer as difficulty 1*65536 (64k) I should have earned a share, correct? If so, why aren't I showing on the payout list for the p2pool node I'm using? Is it averaged across multile blocks?
Q: Why does my miner say it has found a lot of shares but p2pool say I have only found a few?!A: The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly
Thank you for the response, but I have read the FAQ. I know that my "accepted" shares do not reflect my payout. My question is: if the share difficulty as reported on the LTC pool stats page is 1.0, then if I have an accepted share over 64k, I should have earned a share, correct? For example, in the last 24 hours, I've had these 3 shares accepted:
Code:
101 [2013-08-14 00:54:44] Accepted a6bc7db5 Diff 101K/75 GPU 0 pool 0
112 [2013-08-14 05:12:06] Accepted 95b8993c Diff 112K/75 GPU 0 pool 0
352 [2013-08-13 21:49:33] Accepted 2faa66d2 Diff 352K/75 GPU 0 pool 0
If the minimum difficulty for a share is 1, then if I find a share reported by cgminer as difficulty 1*65536 (64k) I should have earned a share, correct? If so, why aren't I showing on the payout list for the p2pool node I'm using? Is it averaged across multile blocks?
Q: Why does my miner say it has found a lot of shares but p2pool say I have only found a few?!
A: The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly
If the minimum difficulty for a share is 1, then if I find a share reported by cgminer as difficulty 1*65536 (64k) I should have earned a share, correct? If so, why aren't I showing on the payout list for the p2pool node I'm using? Is it averaged across multile blocks?
Dead Hash Rate is the amount of shares you are submitting that were stale or DOA. You will want that to be as low as possible. Your rate looks ok. Things that affect your dead hash rate are latency to the pool and miner settings or problems. Some have commented that lowering their intensity reduced their Stale/DOA rate.
Displaying that statistic is common for p2pools as it helps you determine if you are mining efficiently. I don't think I have seen it on other types of pools.
Edit:
DEAD ON ARRIVAL - Dead shares were too old by the time they arrived at the pool. Very high dead rates can indicate miner misconfiguration.
Q: "Do the 'orphan' and 'dead' shares in P2Pool's status display hurt me?"
A: They shouldn't - It's normal for some fraction of everyone's shares to end up orphaned or dead. Because payouts are calculated by counting how many shares you have relative to others, everyone with normal configurations is equally "hurt" by this. However, if you have a large proportion of stales, your payout will be hurt.
More can be read at: https://en.bitcoin.it/wiki/P2Pool
Please take note that a lot of what is mentioned is specific to the larger Bitcoin p2pool but the same concepts apply to altcoins...just at a much smaller scale.
Displaying that statistic is common for p2pools as it helps you determine if you are mining efficiently. I don't think I have seen it on other types of pools.
Edit:
DEAD ON ARRIVAL - Dead shares were too old by the time they arrived at the pool. Very high dead rates can indicate miner misconfiguration.
Q: "Do the 'orphan' and 'dead' shares in P2Pool's status display hurt me?"
A: They shouldn't - It's normal for some fraction of everyone's shares to end up orphaned or dead. Because payouts are calculated by counting how many shares you have relative to others, everyone with normal configurations is equally "hurt" by this. However, if you have a large proportion of stales, your payout will be hurt.
More can be read at: https://en.bitcoin.it/wiki/P2Pool
Please take note that a lot of what is mentioned is specific to the larger Bitcoin p2pool but the same concepts apply to altcoins...just at a much smaller scale.
What is this Dead hash rate?
Miner Hash Rate Dead Hash Rate
1.32MH/s 132kH/s
Miner Hash Rate Dead Hash Rate
1.32MH/s 132kH/s
Oh, thank you. No worries, its just a testing rig for many alt coins 
thought there was something broken in the pool, cos usually I end up getting something. Didn't realize that my hashrate was so low compared to the pools hashrate.
thought there was something broken in the pool, cos usually I end up getting something. Didn't realize that my hashrate was so low compared to the pools hashrate.
Hi minerapia,
You were not able to get any shares with your hash rate of around 40 Kh/s. For anything under 100 Kh/s you run the chance of not getting any shares and subsequently a payout. I have sent you 10 CSC for your effort.
You were not able to get any shares with your hash rate of around 40 Kh/s. For anything under 100 Kh/s you run the chance of not getting any shares and subsequently a payout. I have sent you 10 CSC for your effort.
I've mined around 3hrs (not includint around 0,5hr pause i had) at the CSC pool but still I dont receive anything, my address dont even show in payouts.
CZyJxHNBwt3BkH4ciQQdTvXVaLmULSzJkC
CZyJxHNBwt3BkH4ciQQdTvXVaLmULSzJkC
Added Casinocoin.
Added to the Original Post:
Note: Do NOT use an online or exchange wallet address! They will have no way of knowing that the mined coins belong to you. ONLY use an address from your own wallet.
Note: Do NOT use an online or exchange wallet address! They will have no way of knowing that the mined coins belong to you. ONLY use an address from your own wallet.
Thanks AbiTxGroup. Any and all feedback is appreciated!
Nothing gets past you AbiTxGroup!
Tweaked the PPLNS one last time...you should not see it cut out again.
To many years working on servers, reading log files, and reports from users. I know that any info about the workings of my servers could either be useful or not. I post what I see about servers that I use to be helpful, but if it's not, then I will stop. What I post is not intended as criticism but just for info. Nothing more. Tweaked the PPLNS one last time...you should not see it cut out again.
Nothing gets past you AbiTxGroup!
Tweaked the PPLNS one last time...you should not see it cut out again.
Tweaked the PPLNS one last time...you should not see it cut out again.
AbiTxGroup,
As you have seen we have reduced the PPLNS window from 24 hours to 3 hours for Digitalcoin, Worldcoin, and Craftcoin.
It was a highly requested change so I hope it is liked by everyone!
That does explain the ramp up happening so quickly. I like it.As you have seen we have reduced the PPLNS window from 24 hours to 3 hours for Digitalcoin, Worldcoin, and Craftcoin.
It was a highly requested change so I hope it is liked by everyone!
I know that you posted about updating the server, so I wanted to post what I see while being on it. Right around 02:05am CST, the server cut out again. Not sure if this is caused from the new server files or if something else is going on but its info that you can use to investigate what is happening.
AbiTxGroup,
As you have seen we have reduced the PPLNS window from 24 hours to 3 hours for Digitalcoin, Worldcoin, and Craftcoin.
It was a highly requested change so I hope it is liked by everyone!
As you have seen we have reduced the PPLNS window from 24 hours to 3 hours for Digitalcoin, Worldcoin, and Craftcoin.
It was a highly requested change so I hope it is liked by everyone!
Whats with the server payout resets?
Once today and once yesterday the server was reset and all of the PPLNS time was reset if you were still not on the server.
EDIT NOTE 1231am CST:
OK. It looks like the build up for the PPLNS payout after the server restart is quick to build up. Never seen that before or at least noticed that before.
Once today and once yesterday the server was reset and all of the PPLNS time was reset if you were still not on the server.
EDIT NOTE 1231am CST:
OK. It looks like the build up for the PPLNS payout after the server restart is quick to build up. Never seen that before or at least noticed that before.
All pools have been updated to P2Pool release 13.1.
Jump to: