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

[spiccioli]

So, in the end, is Panda Mouse right or wrong?

spiccioli

[Panda Mouse]

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.

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

[Smoovious]

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

[Ed]

Has someone namecoin payouts, last time?
after major system upgrade
I am worried, because last my found block about mid of March

[Ente]

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?

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

[Smoovious]

My testing with GUI Miner was using the poclbm miner.

-- Smoov

[twmz]

So, in the end, is Panda Mouse right or wrong?

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.

[twmz]

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?

[DeathAndTaxes]

So, in the end, is Panda Mouse right or wrong?

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. 

[thirdlight]

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.

[Proofer]

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.

No. You don't.

This is the command I use to start p2pool.

Code:

python ./run_p2pool.py -a 1HZY2Bks6HjTXFxXSj8ivhWCnkosypiUxR --p2pool-port 8335 -w 8336 --merged http://namecoindrpcuser:pass@127.0.0.1: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?

[DeathAndTaxes]

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.

[spiccioli]

twmz and Death&Taxes,

thanks for the explanation!

spiccioli.

[Ente]

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

[Proofer]

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.

[twmz]

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.

[bitpop]

That's how my public node works, I never touch your earnings. Check it out below.

[Syke]

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.

[twmz]

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.

[Gabi]

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.