twmz and Death&Taxes,
thanks for the explanation!
spiccioli.
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 724. (Read 2591919 times)
April 06, 2012, 11:57:10 AM
April 06, 2012, 11:48:49 AM
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.
April 06, 2012, 11:47:04 AM
You don't need to specify $BITCOIN_USER or $BITCOIN_PASS if the user running p2pool has it in their bitcoin.conf
You do if you want p2pool to be able to connect to your Bitcoin instance.This is the command I use to start p2pool.
Code:
python ./run_p2pool.py -a 1HZY2Bks6HjTXFxXSj8ivhWCnkosypiUxR --p2pool-port 8335 -w 8336 --merged http://namecoindrpcuser:[email protected]:9332/ --disable-upnp -f 0.5
See any bitcoind username/password there?
Code:
usage: run_p2pool.py [-h] [--version] [--net {bitcoin,litecoin}] [--testnet]
[--debug] [-a ADDRESS] [--datadir DATADIR]
[--logfile LOGFILE] [--merged MERGED_URLS]
[--give-author DONATION_PERCENTAGE] [--irc-announce]
[--p2pool-port PORT] [-n ADDR[:PORT]] [--disable-upnp]
[--max-conns CONNS] [-w PORT or ADDR:PORT]
[-f FEE_PERCENTAGE] [--bitcoind-address BITCOIND_ADDRESS]
[--bitcoind-rpc-port BITCOIND_RPC_PORT]
[--bitcoind-p2p-port BITCOIND_P2P_PORT]
[BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]
I note from the last line of the "usage" that (multiple) bitcoind RPC user/passwords may be OPTIONALLY included. When would one include them?
April 06, 2012, 11:37:26 AM
Has someone namecoin payouts, last time?
My last namecoin block was 25 March, 14:25. I would expect to see another in about a week. April 06, 2012, 07:28:01 AM
So, in the end, is Panda Mouse right or wrong?
spiccioli
spiccioli
No and his math isn't even close to reality. Given he hasn't answered any questions on what he calculated for standard deviation or shown any work I don't know how he "calculated" that. He also seems to think that mining is a normal distribution which it isn't.
Since p2pool started the expected # of blocks found would be 305.
95% of the time after 305 expected blocks we should have found at least 267 and no more than 344. As you can see that is a pretty large variance, +/- ~40 blocks.
The 95% confidence interval is 305 blocks +/- 40. To convert that to luck you could say the pool should be within 88% to 112% of expected return 95% of the time. We are at 91% cumulative lifetime luck but still in the range expected.
Just to show how wrong the numbers provided were for us to have a 95% confidence interval of <2 luck% (~99% to ~101% luck) would require an expected # of blocks to be ~50,000 blocks.
April 06, 2012, 07:18:48 AM
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?
April 06, 2012, 07:16:37 AM
So, in the end, is Panda Mouse right or wrong?
spiccioli
spiccioli
Bitcoin mining is a Poisson Process. Using the data from the last 90 days, we found 261 blocks and were expected to have found 287. The probability of finding at most 261 blocks when 287 were expected is approximately 6.4% or 1 in 16 (see the Poisson probability calculator). Those odds are not impossibly small. "Bad luck" still seems plausible.
April 06, 2012, 07:09:51 AM
My testing with GUI Miner was using the poclbm miner.
-- Smoov
-- Smoov
April 06, 2012, 07:02:43 AM
Is there a way for the users of my node to see how much BTC they have been and are about to be paid?
Also, does anyone know if Guiminer works with P2Pool or not?
Also, does anyone know if Guiminer works with P2Pool or not?
Can confirm as well that Guiminer works. Here Guiminer is running with cgminer (poclbm before). I have values for "accepted" and "stales", both "accumulated" and "(hast hour)". Runs stable too, here, over weeks and over reboots too.
As for payout per user: I believe the users have to use the "vip password", then their miner(s) are displayed in the statistics. This was true for the old rrd stats, where all miners are summed up in one graph. I did not test if the "vip password" is still needed for the new, javascript one-graph-per-miner stats. And, this is the hashing power only, not the payout per miner.
Have a look here:
https://en.bitcoin.it/wiki/P2Pool#Web_interface
Maybe one of those shows info per user?
Ente
April 06, 2012, 03:31:02 AM
Has someone namecoin payouts, last time?
after major system upgrade
I am worried, because last my found block about mid of March
after major system upgrade
I am worried, because last my found block about mid of March
April 06, 2012, 03:11:39 AM
Also, does anyone know if Guiminer works with P2Pool or not?
GUI Miner works fine, although I have to keep resetting the port it is supposed to connect to. For some reason, it ignores the 9332 port that is saved in the settings, and changes it to 8332 every time I load it back up.Also, the accepted shares count in the summary tab will always show 0 outside of the perenthesis, like 0(47), but it still works.
Use the v2012-02-19 version.
-- Smoov
April 06, 2012, 02:50:01 AM
Well you said TIME that confused me. Your right the length vs expected can be used but that is because it is already adjusted for what matters (hashes observed vs hashes expected).
Not sure where you are getting 400 observations. p2pool has only found 275 blocks?
Lastly the length of block isn't a normal distribution. It is an exponential one.
Still even using incorrect 400 observation, incorrect assumption of a normal distribution I have no idea how you determined confidence interval is ~99% to ~101% over 400 blocks. I even tried to make mistakes and math just doesn't add up.
Not sure where you are getting 400 observations. p2pool has only found 275 blocks?
Lastly the length of block isn't a normal distribution. It is an exponential one.
Still even using incorrect 400 observation, incorrect assumption of a normal distribution I have no idea how you determined confidence interval is ~99% to ~101% over 400 blocks. I even tried to make mistakes and math just doesn't add up.
1. You're right, there was 275 probe (blocks), now with probability > 50% averages time should be between 99.14 and 100.86.
2. The average time to solve block is a normal distribution.
3. Thank you for putting these blocks.
Panda Mouse
April 06, 2012, 02:24:15 AM
So, in the end, is Panda Mouse right or wrong?
spiccioli
spiccioli
April 06, 2012, 02:14:39 AM
Holy crap @ the day we're having. 
Shh...Don't scare the luck away.
Someone did scare the luck away
287,7% and 300,0% for today's block
123.3% and 149.9% for previous blocks
April 05, 2012, 11:39:57 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?
Also, does anyone know if Guiminer works with P2Pool or not?
Also, does anyone know if Guiminer works with P2Pool or not?
April 05, 2012, 08:38:32 PM
BTW in last 7 days there was 2 orphaned blocks.
Why they are invisible, they should becrossed out.
Why they are invisible, they should be
They weren't produced by the main fork of p2pool.
There actually were 2 orphaned blocks made by the main fork of p2pool that were missing (because my node bitcoin node never heard about them). I added them to p2pool.info manually. These were in addition to the other orphaned blocks from the old p2pool fork.
April 05, 2012, 05:24:11 PM
Did anybody else's graphs at /static/graphs clear recently?
I did a git pull and restarted p2pool, now graphs are just empty. Been running for over a day now, still all the graphs are empty, and it looks like its not even registering the miners, because the section under Miners is empty. The old ones (rrdtool) still work fine, and the info at /static looks fine as well, but all the graphs are blank.
I'm getting the same thing after doing a pull last night.I did a git pull and restarted p2pool, now graphs are just empty. Been running for over a day now, still all the graphs are empty, and it looks like its not even registering the miners, because the section under Miners is empty. The old ones (rrdtool) still work fine, and the info at /static looks fine as well, but all the graphs are blank.
Yes, there was a bug. It effected me as well. He fixed it this morning. Do another git pull and restart p2pool. The latest pull will fix the issue.
April 05, 2012, 03:57:04 PM
Did anybody else's graphs at /static/graphs clear recently?
I did a git pull and restarted p2pool, now graphs are just empty. Been running for over a day now, still all the graphs are empty, and it looks like its not even registering the miners, because the section under Miners is empty. The old ones (rrdtool) still work fine, and the info at /static looks fine as well, but all the graphs are blank.
I'm getting the same thing after doing a pull last night. I did a git pull and restarted p2pool, now graphs are just empty. Been running for over a day now, still all the graphs are empty, and it looks like its not even registering the miners, because the section under Miners is empty. The old ones (rrdtool) still work fine, and the info at /static looks fine as well, but all the graphs are blank.
April 05, 2012, 03:56:00 PM
That was a bug; if you pull again (as of a couple of hours ago) it will work again. No data was lost, just the graph displaying was broken.
April 05, 2012, 03:40:35 PM
I haven't done a gitpull but using latest released version my graphs didn't clear.
Jump to: