Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 550. (Read 2591920 times)
Yeah, it seems to me that the last week has been very unlucky - sort of corresponds to ASCIminer bringing more power online, but I don't know if that's just coincidental or not.
Returning with an answer to yesterday's issue: my p2pool is again showing payout if a block were found now at 0 btc and I have 6 peers out 3 in. Why does it say i'd get 0?
I believe you earn shares in quantum increments. Until you earn a share, it will be at zero.
your node is unlucky at the moment. When you hash, you're basically guessing a number. Sometimes you'll guess the right number (and solve a share - kind of like solving a block), and sometimes you'll guess a wrong number. As difficulty goes up, it's harder and harder to guess the right number. When you guess the right number, you get credit for a share which then means you get paid every time p2pool finds a block over the next day (currently for p2pool, but this can change).
Your node has been unlucky at guessing numbers lately, so you haven't gotten a share and won't get paid until you do. Sometimes you'll get luck and guess two in a row, in which case you'll get paid 2x more than if you found just one share.
regarding static address: p2pool generates one the first time you run it, and as long as there is a "p2pool" address in your wallet it will mine to that one. It wo't create a new one with new address unless you wipe your wallet.
Returning with an answer to yesterday's issue: my p2pool is again showing payout if a block were found now at 0 btc and I have 6 peers out 3 in. Why does it say i'd get 0?
I believe you earn shares in quantum increments. Until you earn a share, it will be at zero.
your node is unlucky at the moment. When you hash, you're basically guessing a number. Sometimes you'll guess the right number (and solve a share - kind of like solving a block), and sometimes you'll guess a wrong number. As difficulty goes up, it's harder and harder to guess the right number. When you guess the right number, you get credit for a share which then means you get paid every time p2pool finds a block over the next day (currently for p2pool, but this can change).
Your node has been unlucky at guessing numbers lately, so you haven't gotten a share and won't get paid until you do. Sometimes you'll get luck and guess two in a row, in which case you'll get paid 2x more than if you found just one share.
regarding static address: p2pool generates one the first time you run it, and as long as there is a "p2pool" address in your wallet it will mine to that one. It wo't create a new one with new address unless you wipe your wallet.
Hashrate varies between 110 and 280 Mh/s with an average of 190 over a month of nonstop mining. I'm using bitcoin-qt's address to send the payment and not the -a flag.
I highly recommend specifying a static address. If you don't, p2pool will pick different addresses when you restart the Bitcoin client and your share count will start over with the new address.
Hashrate varies between 110 and 280 Mh/s with an average of 190 over a month of nonstop mining. I'm using bitcoin-qt's address to send the payment and not the -a flag.
I highly recommend specifying a static address. If you don't, p2pool will pick different addresses when you restart the Bitcoin client and your share count will start over with the new address. Returning with an answer to yesterday's issue: my p2pool is again showing payout if a block were found now at 0 btc and I have 6 peers out 3 in. Why does it say i'd get 0?
I believe you earn shares in quantum increments. Until you earn a share, it will be at zero.
Returning with an answer to yesterday's issue: my p2pool is again showing payout if a block were found now at 0 btc and I have 6 peers out 3 in. Why does it say i'd get 0?
I believe you earn shares in quantum increments. Until you earn a share, it will be at zero.
Returning with an answer to yesterday's issue: my p2pool is again showing payout if a block were found now at 0 btc and I have 6 peers out 3 in. Why does it say i'd get 0?
I believe you earn shares in quantum increments. Until you earn a share, it will be at zero.
Returning with an answer to yesterday's issue: my p2pool is again showing payout if a block were found now at 0 btc and I have 6 peers out 3 in. Why does it say i'd get 0?
I believe you earn shares in quantum increments. Until you earn a share, it will be at zero.
Returning with an answer to yesterday's issue: my p2pool is again showing payout if a block were found now at 0 btc and I have 6 peers out 3 in. Why does it say i'd get 0?
Yep. It was that pesky QOS again. No idea why it would be causing issues, doesn't make much sense. P2Pool should still be getting bandwidth.
I've been mining pretty well I thought but I didn't get a payout on the last block.
https://blockchain.info/block/000000000000006fdeafb19ca3c74baa5f31f1f36f98b79fb914229d1dc7fe9e
Also, the "Blocks found in last day" is showing a very old block
time number hash/explorer link share
Thu May 02 2013 12:20:58 GMT-0500 (Central Daylight Time) 234219 000000000000003ca0bd661df02a9bba63fe0324b11c6c648a45d8b6b47adafb →
Anyone know what's going on here?
https://blockchain.info/block/000000000000006fdeafb19ca3c74baa5f31f1f36f98b79fb914229d1dc7fe9e
Also, the "Blocks found in last day" is showing a very old block
time number hash/explorer link share
Thu May 02 2013 12:20:58 GMT-0500 (Central Daylight Time) 234219 000000000000003ca0bd661df02a9bba63fe0324b11c6c648a45d8b6b47adafb →
Anyone know what's going on here?
Your node connected to any peers?
From the graph, it looks so. However, I had turned QOS back on which may have been causing me issues before. Turned it back off now and we'll see how it goes. Then I need to try making p2pool high priority and see if it starts working then.
I've been mining pretty well I thought but I didn't get a payout on the last block.
https://blockchain.info/block/000000000000006fdeafb19ca3c74baa5f31f1f36f98b79fb914229d1dc7fe9e
Also, the "Blocks found in last day" is showing a very old block
time number hash/explorer link share
Thu May 02 2013 12:20:58 GMT-0500 (Central Daylight Time) 234219 000000000000003ca0bd661df02a9bba63fe0324b11c6c648a45d8b6b47adafb →
Anyone know what's going on here?
https://blockchain.info/block/000000000000006fdeafb19ca3c74baa5f31f1f36f98b79fb914229d1dc7fe9e
Also, the "Blocks found in last day" is showing a very old block
time number hash/explorer link share
Thu May 02 2013 12:20:58 GMT-0500 (Central Daylight Time) 234219 000000000000003ca0bd661df02a9bba63fe0324b11c6c648a45d8b6b47adafb →
Anyone know what's going on here?
Your node connected to any peers?
I've been mining pretty well I thought but I didn't get a payout on the last block.
https://blockchain.info/block/000000000000006fdeafb19ca3c74baa5f31f1f36f98b79fb914229d1dc7fe9e
Also, the "Blocks found in last day" is showing a very old block
time number hash/explorer link share
Thu May 02 2013 12:20:58 GMT-0500 (Central Daylight Time) 234219 000000000000003ca0bd661df02a9bba63fe0324b11c6c648a45d8b6b47adafb →
Anyone know what's going on here?
https://blockchain.info/block/000000000000006fdeafb19ca3c74baa5f31f1f36f98b79fb914229d1dc7fe9e
Also, the "Blocks found in last day" is showing a very old block
time number hash/explorer link share
Thu May 02 2013 12:20:58 GMT-0500 (Central Daylight Time) 234219 000000000000003ca0bd661df02a9bba63fe0324b11c6c648a45d8b6b47adafb →
Anyone know what's going on here?
I'd like to point out some basic difficulty-related considerations here, which I believe were not mentioned in this thread. Please correct me if I am wrong!
Here's how I suggest to determine desired share difficulty. Variance of miner's income depends both on his own share generation variance and the p2pool's block generation variance. Even if you have high hashrate and generate shares every minute or so, you still get payouts only from blocks found by p2pool. One familiar with statistics/probability theory may see that payout variance ((rms deviation) / (estimated value)) after mining for T hours is proportional to
At the time of this post, p2pool is running at ~800 GH/s with Bitcoin difficulty ~10M and share difficulty ~1500. At this rate, expected time to block is ~16 hours.
At default share difficulty, estimated time to share for a miner with 1 GH/s is ~1.8 hours, which gives him overall variance coefficient ~sqrt( 16 + 1.8 ). If the miner manually sets his share difficulty to 5000, it will become ~sqrt(16 + 6), which is only ~11% higher.
Similarly, for a miner with 10 GH/s time to share is 0.18 hours, so variance at default difficulty is ~sqrt(16 + 0.18). So he can set his difficulty to 35,000, which gives variance of ~sqrt(16 + 4.2), which is again only 12% higher than default.
Only when a miner's time to share is comparable to (say, 3-5 times smaller than) the p2pool's time to block, increase of share difficulty will have considerable impact on his variance.
Tl;dr: I suggest that reasonable share difficulty for a miner is such, that estimated time to share is a couple of times lower than the p2pool's time to block. Setting it lower will harm small miners (increase their variance) without any serious decrease of the miner's own variance. Setting it higher will increase the miner's own variance.
Here's how I suggest to determine desired share difficulty. Variance of miner's income depends both on his own share generation variance and the p2pool's block generation variance. Even if you have high hashrate and generate shares every minute or so, you still get payouts only from blocks found by p2pool. One familiar with statistics/probability theory may see that payout variance ((rms deviation) / (estimated value)) after mining for T hours is proportional to
Code:
variance ~ sqrt(((miner's estimated time to share) + (p2pool's estimated time to block)) / T)
At default share difficulty, estimated time to share for a miner with 1 GH/s is ~1.8 hours, which gives him overall variance coefficient ~sqrt( 16 + 1.8 ). If the miner manually sets his share difficulty to 5000, it will become ~sqrt(16 + 6), which is only ~11% higher.
Similarly, for a miner with 10 GH/s time to share is 0.18 hours, so variance at default difficulty is ~sqrt(16 + 0.18). So he can set his difficulty to 35,000, which gives variance of ~sqrt(16 + 4.2), which is again only 12% higher than default.
Only when a miner's time to share is comparable to (say, 3-5 times smaller than) the p2pool's time to block, increase of share difficulty will have considerable impact on his variance.
Tl;dr: I suggest that reasonable share difficulty for a miner is such, that estimated time to share is a couple of times lower than the p2pool's time to block. Setting it lower will harm small miners (increase their variance) without any serious decrease of the miner's own variance. Setting it higher will increase the miner's own variance.
Code:
def get_local_stats():
...
lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...
So... I would guess that it's a 10 sec resolution?
No, one hour (3600 seconds).
Yeah, that'll be pulling out the last 360 samples - at 10 seconds each for an hour in total.
Perfect! Thanks!
Just to follow up on this, I've posted my nagios plugin on github: https://github.com/daemondazz/nagios-plugins
I get ---ERROR---
I use port 9554, yours may be different.
M
I'm trying to set up P2Pool for an altcoin, but it is hanging at:
What would cause this? I can see the node on the daemon.
Code:
Testing bitcoind P2P connection to '127.0.0.1:19323'
What would cause this? I can see the node on the daemon.
Code:
{
"addr" : "127.0.0.1:51311",
"services" : "00000000",
"lastsend" : 0,
"lastrecv" : 1367878607,
"conntime" : 1367878607,
"version" : 0,
"subver" : "",
"inbound" : true,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
Setting the magic numbers in p2pool/bitcoin/networks.py incorrectly.
I'm trying to set up P2Pool for an altcoin, but it is hanging at:
What would cause this? I can see the node on the daemon.
Code:
Testing bitcoind P2P connection to '127.0.0.1:19323'
What would cause this? I can see the node on the daemon.
Code:
{
"addr" : "127.0.0.1:51311",
"services" : "00000000",
"lastsend" : 0,
"lastrecv" : 1367878607,
"conntime" : 1367878607,
"version" : 0,
"subver" : "",
"inbound" : true,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
For the first time in a month of mining on p2pool, the page is saying "Payout if a block were found now: 0 BTC". This is in spite of the hashrate being shown normal and DOAs/orphans next to nonexistent. And about an hour ago it was showing a non-zero payment. I restarted the entire btc, p2pool, bfgminer ensemble but it's still showing 0. Why does this happen?
Do you have any peer connections?
Do you have a pretty low hash rate? If you don't get a share every 24 hours, your payout will drop to zero at times.
Wow, I didn't know that existed. That makes something I'm trying to do a lot easier.
Yep, useful. What time period are those stats over? In particular I mean the miner_hash_rates and miner_dead_hash_rates. I need them over a reasonably short period for alarming to be able to react if a miner goes away.
Code:
def get_local_stats():
...
lookbehind = min(node.tracker.get_height(node.best_share_var.value), 3600//node.net.SHARE_PERIOD)
...
So... I would guess that it's a 10 sec resolution?
No, one hour (3600 seconds).
Jump to: