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

[spiccioli]

Troll less kthx.

Thanks to you for the most useless message of this thread.

spiccioli

[1714057582]

1714057582

[1714057582]

1714057582

[1714057582]

1714057582

[Frizz23]

Can I use p2pool to mine Bitcoins and with the --merged flag also mine Litecoins at the same time?

[twmz]

Can I use p2pool to mine Bitcoins and with the --merged flag also mine Litecoins at the same time?

Litecoins use a different miner and are a different pool.  You can do both bitcoins and litecoins at the same time, but you do that by running two copies of p2pool at the same time (one in bitcoins mode and the other in litecoins mode).  The litecoins p2pool instance will be running on different ports and you point your litecoin miners at it while your bitcoin miners point at the normal p2pool instance.

Start a litecoin instance like this:

./run_p2pool.py --net litecoin -a paymentaddress rpcusername rpcpassword

Then point your litecoin miners to http://localhost:9338

[Frizz23]

Can I use p2pool to mine Bitcoins and with the --merged flag also mine Litecoins at the same time?

Litecoins use a different miner and are a different pool.  You can do both bitcoins and litecoins at the same time, but you do that by running two copies of p2pool at the same time (one in bitcoins mode and the other in litecoins mode).  The litecoins p2pool instance will be running on different ports and you point your litecoin miners at it while your bitcoin miners point at the normal p2pool instance.

Start a litecoin instance like this:

./run_p2pool.py --net litecoin -a paymentaddress rpcusername rpcpassword

Then point your litecoin miners to http://localhost:9338

Thanks for clarification.

I was hoping it would be possible to do kinda merged mining (like it's possible with Bitcoind and Namecoin).

[kano]

Merged mining is only possible if both chains use the same hash function.
The CPU chains use different hash functions so thus cannot merge mine as such ...
... well they could, but you'd be using the same amount of extra resources as mining both chains separately so it's pointless.

[forrestv]

I have multiple interfaces on a host and I want run_p2pool.py to listen on 9.8.7.6:9332  How do I do this?

P2Pool should listen on port 9332 on all interfaces. Is this a problem..? You mentioned just needing to connect external miners, which many people already do.

[forrestv]

This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.

The first post has had a link to a full, guaranteed list of P2Pool-found blocks for a long time:

List of all blocks found: http://blockexplorer.com/address/1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4

[Ente]

Hmm..
We have seven rigs running, one of them doesnt seem to work.
No p2pool shares were generated. So I updated from 0.8.1 to the recent forrestv-p2pool-0.8.3-0-g3cfeee9.

Code:

2012-02-10 17:43:26.002000  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.5084 BTC
2012-02-10 17:43:26.017000  Local: 0H/s (10 min avg) Local dead on arrival: ??? Expected time to share: ???
2012-02-10 17:43:26.017000  P2Pool: 17426 shares in chain (17613 verified/34811 total) Peers: 11 (0 incoming)
2012-02-10 17:43:41.072000 Pool: 208GH/s Stale rate: 9.3% Average time between blocks: 0.33 days
2012-02-10 17:43:41.087000  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.5084 BTC
2012-02-10 17:43:41.118000  Local: 0H/s (10 min avg) Local dead on arrival: ??? Expected time to share: ???
2012-02-10 17:43:41.134000  P2Pool: 17426 shares in chain (17613 verified/34811 total) Peers: 11 (0 incoming)
2012-02-10 17:43:43.318000 New work for worker! Difficulty: 0.999985 Share difficulty: 449.278560 Total block value: 50.012000 BTC including 41 transactions
2012-02-10 17:43:44.160000 Pool: 210GH/s Stale rate: 9.3% Average time between blocks: 0.33 days
2012-02-10 17:43:44.176000  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.5084 BTC
2012-02-10 17:43:44.223000  Local: 0H/s (10 min avg) Local dead on arrival: ??? Expected time to share: ???
2012-02-10 17:43:44.254000  P2Pool: 17427 shares in chain (17521 verified/34719 total) Peers: 11 (0 incoming)

Still using GuiMiner, it throws:

2012-02-10 17:50:49: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:49, long poll: new block 000004f709b08c9c
2012-02-10 17:50:53: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:53, Unexpected error:
2012-02-10 17:51:03: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:03, Unexpected error:
2012-02-10 17:51:09: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:09, Unexpected error:
2012-02-10 17:51:10: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:10, long poll: new block 000004f709b08c9c
2012-02-10 17:51:16: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:16, long poll: new block 000004f709b08c9c
2012-02-10 17:51:18: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:18, long poll: new block 000004f709b08c9c

Any ideas?

Ente

[Proofer]

Code:

python run_p2pool.py --version
Install SciPy for more accurate confidence intervals!
053d7ca

I've been meaning to ask for a while... how are version numbers generated?  Do they encode any information of interest to a user?

[twmz]

I've been playing around with making a p2pool recent stats page.  It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:

http://btcstats.net/p2pool/

• Includes Recent pool hash rate and stale rate
• Recent blocks are shown on the chart as vertical lines so that you can "see" variance
• Recent blocks are also listed in a table with links to the details

[cheat_2_win]

I've been playing around with making a p2pool recent stats page.  It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:

http://btcstats.net/p2pool/

• Includes Recent pool hash rate and stale rate
• Recent blocks are shown on the chart as vertical lines so that you can "see" variance
• Recent blocks are also listed in a table with links to the details

Very nice.

[spiccioli]

This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.

The first post has had a link to a full, guaranteed list of P2Pool-found blocks for a long time:

List of all blocks found: http://blockexplorer.com/address/1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4

forrestv,

I'm sorry my sentence keeps coming up, I was answering a previous message from piuk with a link to blockchain.info which had a wrong block listed and just the day before p2pool log file was found by me to contain out-of-date (and as such "misleading" as in "misleading to a user" of p2pool) informations (they clearly are not misleading to their author or to someone who digs into the source code and understands its inner workings).

I also did not check that blockexplorer link because I thought that grepping p2pool log file was the surest way to know what was going on and in case of troubles (blocks being lost and share numbers swinging a lot were yesterday "problems" I was trying to go after) looking up an address to see if it got its payment is not a good idea IMHO since on a lost block every address should not receive any payment.

So I was trying to express the idea that there is not a "place" which lists blocks found and found but rejected by the network as it happens with other pools which often have such a "place".

Maybe my sentence sounds to english speaking peoples in way that is too harsh or just stronger than it was meant to be, my apologies if this is the case.

spiccioli

[Gabi]

Wow nice job




Aaaaaaand 220ghash/s! 

[spiccioli]

I've been playing around with making a p2pool recent stats page.  It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:

http://btcstats.net/p2pool/

• Includes Recent pool hash rate and stale rate
• Recent blocks are shown on the chart as vertical lines so that you can "see" variance
• Recent blocks are also listed in a table with links to the details

Very nice twmz,

do you know whether blocks found but later rejected by bitcoin network can be listed?

spiccioli

[ThiagoCMC]

I've been playing around with making a p2pool recent stats page.  It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:

http://btcstats.net/p2pool/

• Includes Recent pool hash rate and stale rate
• Recent blocks are shown on the chart as vertical lines so that you can "see" variance
• Recent blocks are also listed in a table with links to the details

Very nice twmz,

do you know whether blocks found but later rejected by bitcoin network can be listed?

spiccioli

You mean, "Invalid Blocks"?

[spiccioli]

I've been playing around with making a p2pool recent stats page.  It's not done yet, and the backend needs a lot of work, but it's done enough to give you an idea:

http://btcstats.net/p2pool/

• Includes Recent pool hash rate and stale rate
• Recent blocks are shown on the chart as vertical lines so that you can "see" variance
• Recent blocks are also listed in a table with links to the details

Very nice twmz,

do you know whether blocks found but later rejected by bitcoin network can be listed?

spiccioli

You mean, "Invalid Blocks"?

Yes, blocks found by pool but then rejected by bitcoin network.

spiccioli

[twmz]

do you know whether blocks found but later rejected by bitcoin network can be listed?

You mean, "Invalid Blocks"?

Yes, blocks found by pool but then rejected by bitcoin network.

No, my page doesn't include those.  There's not a convenient centralized place to get a list of those that I can pull from.

[forrestv]

I've been meaning to ask for a while... how are version numbers generated?  Do they encode any information of interest to a user?

They are git commit hashes. You can look at the source code for your version by going to https://github.com/forrestv/p2pool/tree/053d7ca or you can see changes I've committed since your version, by going to https://github.com/forrestv/p2pool/compare/053d7ca...master .

I'm sorry my sentence keeps coming up, I was answering a previous message from piuk with a link to blockchain.info which had a wrong block listed and just the day before p2pool log file was found by me to contain out-of-date (and as such "misleading" as in "misleading to a user" of p2pool) informations (they clearly are not misleading to their author or to someone who digs into the source code and understands its inner workings).

I also did not check that blockexplorer link because I thought that grepping p2pool log file was the surest way to know what was going on and in case of troubles (blocks being lost and share numbers swinging a lot were yesterday "problems" I was trying to go after) looking up an address to see if it got its payment is not a good idea IMHO since on a lost block every address should not receive any payment.

So I was trying to express the idea that there is not a "place" which lists blocks found and found but rejected by the network as it happens with other pools which often have such a "place".

Maybe my sentence sounds to english speaking peoples in way that is too harsh or just stronger than it was meant to be, my apologies if this is the case.

Ah, sorry, I guess I didn't understand then. The best way to see invalid blocks is to see if any of the blocks mentioned in your log aren't present on Block Explorer. Just looking at Block Explorer only tells you confirmed blocks, and only looking at your log can sometimes tell you old blocks and sometimes not tell you about new blocks, due to them being stale on P2Pool.

It wasn't too harsh!

[forrestv]

Still using GuiMiner, it throws:

2012-02-10 17:50:49: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:49, long poll: new block 000004f709b08c9c
2012-02-10 17:50:53: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:50:53, Unexpected error:
2012-02-10 17:51:03: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:03, Unexpected error:
2012-02-10 17:51:09: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:09, Unexpected error:
2012-02-10 17:51:10: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:10, long poll: new block 000004f709b08c9c
2012-02-10 17:51:16: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:16, long poll: new block 000004f709b08c9c
2012-02-10 17:51:18: Miner "p2pool": 127.0.0.1:9332 10/02/2012 17:51:18, long poll: new block 000004f709b08c9c

Any ideas?

Do all of the rigs have identical configurations? It looks like you're using poclbm as the backend.. Maybe try downloading the newest version of poclbm from https://github.com/m0mchil/poclbm/downloads and dropping it into GUIMiner's directory?

[Syke]

This fact that is not possibile to tell exactly what was found and when is a big problem, IMHO, which could stop miners from switching to p2pool.

+1

p2pool claims to be totally transparent. Users having full control (as in opposite to big mining pools).

Yet we don't even know for sure when / what was found.

Here's a great command to list found blocks:

Code:

bitcoind listtransactions