Possible bug report.
The hashrate found at /local_stats seems to be incorrect when using a custom target.
My guess is that the hashrates are looking at the # of shares and assuming a default target thus under-report actual hashrate when using higher target (i.e. username/target option)
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 723. (Read 2591919 times)
April 08, 2012, 05:21:09 PM
April 08, 2012, 05:00:50 PM
I've updated v0.10.3,run it and shows errors:
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):
My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):
My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?
The problem is due to you using an encrypted wallet, which is locked. The easiest solution would be to run p2pool with the -a option, with a payment address.
April 08, 2012, 11:07:52 AM
how do you update your p2pool folder using git? I thought you could use the "pull" command but that gives an error...
What error? April 08, 2012, 10:57:51 AM
how do you update your p2pool folder using git? I thought you could use the "pull" command but that gives an error...
April 08, 2012, 10:38:46 AM
I've updated v0.10.3,run it and shows errors:
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):
My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):
My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?
Did you restart your computer when you updated? You might just have to wait long enough for bitcoin to synchronize the block chain.
April 08, 2012, 09:18:01 AM
I've updated v0.10.3,run it and shows errors:
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):
My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?
p2pool.util.jsonrpc.error:-12 error:keypool ran out,please call keypoolrefill first
error getting payout address from bitcoind:
traceback (most recent call last):
My bitcoin-qt is v0.6.0.6 and os is win7 x64
What is the matter?
April 07, 2012, 11:43:35 PM
I'd guess that the expected delay getting from miner to network is the (hash rate) weighted average of that for all pool miners.
Some would of course have sizeable delays from miner to bitcoind and most would probably have few connections to the network.
If that adds up to enough to increase the number of orphans? No idea.
Some would of course have sizeable delays from miner to bitcoind and most would probably have few connections to the network.
If that adds up to enough to increase the number of orphans? No idea.
April 07, 2012, 11:13:56 PM
Correct me if I'm wrong, but could the variance between what the pool should have produced, and what was actually produced be a result of lag between the blockchain and the sharechain? Or even lag between local P2Pool clients and bitcoind?
I haven't looked into the history too much, but does P2Pool have an abnormally high amount of orphaned blocks?
I haven't looked into the history too much, but does P2Pool have an abnormally high amount of orphaned blocks?
April 07, 2012, 03:00:08 PM
Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.
So then you lose... why did you bother posting? April 07, 2012, 01:01:58 PM
Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.
Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.
Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.
Hao? Last I checked, if you were right then... well... you're right.
-- Smoov
April 07, 2012, 12:25:11 PM
Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.
Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.
Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.
Hao? Last I checked, if you were right then... well... you're right.
April 07, 2012, 11:07:06 AM
Right but it's the internet where you always lose, so by posting, deathandtaxes automatically lost even if he is right.
Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.
Dear Panda Mouse if you aren't happy with reality send your whine to god. Meanwhile stop spreading FUD.
April 07, 2012, 11:02:33 AM
Dear DeathAndTaxes if you aren't happy with reality send your whine to god 
Uh, its not DnT whining here? He is setting the statistics facts straight? If anyone, Panda Mouse is whining, i.e. leaving p2pool because of scam or variance, depending on who you ask.
Ente
April 07, 2012, 10:31:58 AM
Dear DeathAndTaxes if you aren't happy with reality send your whine to god
Seriously, this fud is ridicolous, p2pool is open source, if you think p2pool is scamming you then check the code and find the scamming part.
Seriously, this fud is ridicolous, p2pool is open source, if you think p2pool is scamming you then check the code and find the scamming part.
April 07, 2012, 08:27:32 AM
Since p2pool started the expected # of blocks found would be 305.
How in the world do you calculate that? The hashing power of p2pool changes continually.
We have available the hour by hour hashrate statistics for p2pool since p2pool started. In fact, I have collected even more detailed hashrate stats (5 minute intervals) since mid February. Using the hashrate data along with the data on when bitcoin network difficulty changes occured, it's straightforward to calculate how many blocks were expected at various points in time in the past. And if you add them all up, you get 305. At least that is how p2pool.info does it.
April 07, 2012, 02:07:38 AM
Since p2pool started the expected # of blocks found would be 305.
How in the world do you calculate that? The hashing power of p2pool changes continually.
April 06, 2012, 03:42:07 PM
That's how my public node works, I never touch your earnings. Check it out below.
April 06, 2012, 03:33:23 PM
Is there a way for the users of my node to see how much BTC they have been and are about to be paid?
For "about to be paid", go to any up-to-date p2pool node and look at http://forre.st:9332/static/. They can find their address in the list of current payouts to see what they would get paid if a block was found immediately. That information is also on the Current Payouts tab of p2pool.info.
For "have been paid", they can look in their wallet? Or go to a site like blockchain.info and search for their address to see just the "Total Received" for that address?
I think he is asking for individual payouts for individual miners connecting to a single p2pool node, aka "public p2pool pool". Like when miners connect with an address as their username, they get a part of the payout for the whole p2pool node to their individual address.
Ente
For anyone running a "normal" public p2pool node, my answer remains the same. Individual miners who are using their address as their username will appear in the lists I suggested as individual entries. With unmodified public p2pool nodes, miners get paid for the shares that they find directly as if they were running their own node. The node as a whole does not have a single entry in the current payout lists. Every individual address that found a share has its own entry in that list.
Public p2pool nodes do not receive payments in bulk and redistribute them to their miners based on diff 1 shares or anything like that. The only node I know of that is doing that is p2pmining.com and he has developed his own infrastructure to do that and has his own web UI for seeing pending payments.
April 06, 2012, 01:54:42 PM
I note from the last line of the "usage" that (multiple) bitcoind RPC user/passwords may be OPTIONALLY included. When would one include them?
If bitcoind and p2pool are not on the same machine.
W/r "multiple"-- the usage syntax allows an indefinite number of BITCOIND_RPCUSERPASS items:
[BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]
I've no idea why.
April 06, 2012, 01:39:53 PM
Is there a way for the users of my node to see how much BTC they have been and are about to be paid?
For "about to be paid", go to any up-to-date p2pool node and look at http://forre.st:9332/static/. They can find their address in the list of current payouts to see what they would get paid if a block was found immediately. That information is also on the Current Payouts tab of p2pool.info.
For "have been paid", they can look in their wallet? Or go to a site like blockchain.info and search for their address to see just the "Total Received" for that address?
I think he is asking for individual payouts for individual miners connecting to a single p2pool node, aka "public p2pool pool". Like when miners connect with an address as their username, they get a part of the payout for the whole p2pool node to their individual address.
Ente
Jump to: