[POLL] Why don't you mine in p2pool?

[baloo_kiev]

security issues..

don't forget DoS attacks

Which exactly security issues do you mean?

Well, being a decentralised network, technically based on merged-mined share chain, p2pool has DoS protection similar to that of Bitcoin client and is actually better DoS-protected than any single pool. Of course, any single public p2pool node is still vulnerable to different types of DoS attacks, but that is solved by simply setting backup pools in your mining software (if you mine on a public p2pool node).

[maqifrnswa]

security issues..

don't forget DoS attacks

isn't that a strength of a p2pool? Isn't it one of (if not the most) DoS resistant pools?

[notme]

No pool was trusted from launch just "by default". Maybe you should select yourself a low latency node here http://p2pool.hostv.pl/ and give it a try! Also, there are some nodes which have been here for quite long time like p2pool.org and others.

The main fear I have is a malicious node operator skimming shares. It would be very hard to detect because the node could just say the share was "stale", and take it for himself. This can be done with traditional pools too, but even the smallest pools are magnitudes larger than p2pool nodes.

I run a p2pool back mining pool so people with low hashpower can use p2pool with lower variance:
https://bitcointalk.org/index.php?topic=234841.0

Skimming shares is exactly what my software does.  Can you please tell me how to do it without having the mining software report this:

Accepted untracked stratum share

I will be very appreciative since that message tends to scare off new users who don't read the OP carefully.

[baloo_kiev]

Skimming shares is exactly what my software does.  Can you please tell me how to do it without having the mining software report this:

Accepted untracked stratum share

I will be very appreciative since that message tends to scare off new users who don't read the OP carefully.

I guess something is wrong with your code and how it handles stratum connections. Have you seen this? https://bitcointalk.org/index.php?topic=28402.msg2167883#msg2167883

[notme]

Skimming shares is exactly what my software does.  Can you please tell me how to do it without having the mining software report this:

Accepted untracked stratum share

I will be very appreciative since that message tends to scare off new users who don't read the OP carefully.

I guess something is wrong with your code and how it handles stratum connections. Have you seen this? https://bitcointalk.org/index.php?topic=28402.msg2167883#msg2167883

I was using sarcasm... my point is the statum protocol will make it quite obvious if someone rewrites the share's payout address as I am.

[Soros Shorts]

ASIC manufacturers seem to only consider p2pool as an afterthought. They seem to like coming up with optimized designs that achieve increased hashrates by delaying the reporting of shares by a few hundred milliseconds or even a few seconds.

[notme]

ASIC manufacturers seem to only consider p2pool as an afterthought. They seem to like coming up with optimized designs that achieve increased hashrates by delaying the reporting of shares by a few hundred milliseconds or even a few seconds.

P2Pool is changing their share time to 30 seconds from 10 seconds, which should help.  In addition, there are ways to tune you mining settings so that you can achieve greater than 100% efficiency as long as you have good internet connectivity.

[IYFTech]

Hey peeps,

Noob to Bitcointalk - but not to mining, been doing it a few years now.

I used to mine at p2pool back in the day, but left when stratum support was introduced as it turned into a money pit. It just went down hill rapido and nothing was done to the software to bring it up to date or in line with other pools. I noticed they are finally going to make some adjustments in that regard, but they should have done this many months ago. There's also a bit of an elitist attitude going on, which puts a lot of people off - as well as the crap payouts lately, but everyone there seems to be too busy drowning in nano-second latency/getblock graphs to have noticed......

[asyring]

p2pool crashes too often.
I need a stable pool.

I think without these python *** it could be more stable.

[baloo_kiev]

p2pool crashes too often.
I need a stable pool.

I think without these python *** it could be more stable.

There are plenty of nodes with uptime >1month. From my own experience, power losses occur more often than p2pool crashes. If your node crashes often, you might be doing something wrong. Also, no pool has 100% uptime guarantee, that's why mining software has backup pools option.

[asyring]

my pool has over 200 connections to my miner why?

It is also growing

I pull the lasted version from git.

I don't know the reason.
I use Debian testing as distribution. Is there a problem in the twisted library?

which distrib do you use?

[2weiX]

so
..what's the command line for p2pool in, say bfgminer, for a couple of Erupters?
..for a Little SC?
..for 60GH SC?

can i mergemine NMC with it?

[baloo_kiev]

my pool has over 200 connections to my miner why?

It is also growing

I pull the lasted version from git.

I don't know the reason.
I use Debian testing as distribution. Is there a problem in the twisted library?

which distrib do you use?

Seems like this issue was introduced in the latest version. It is being discussed now on last page of the official thread. I am running Ubuntu 12.04.

Code:

$ lsof -np 4993 | grep -c -e TCP -e UDP
27
$ lsof -np 4993 | grep -e TCP -e UDP | grep -c 127.0.0.1
3

so
..what's the command line for p2pool in, say bfgminer, for a couple of Erupters?
..for a Little SC?
..for 60GH SC?

can i mergemine NMC with it?

It depends whether you want to run your local node or mine on a public one. In first case, you will need enough computational power to run bitcoin and p2pool (that's about 2 CPU cores + 2GB RAM + 10 GB disk space minimum in total), so you obviously can't do it with Raspberry Pi.

If you want to run your own node, launch it with

Code:

python run_p2pool.py --net bitcoin --merged http://<NMC RPC user>:<NMC RPC password>@127.0.0.1:<NMC RPC port>/ -w <port for workers> <BTC RPC user> <BTC RPC password>

then point your miners to <port for workers> (both getwork and stratum are supported!)

If you want to mine on a public node, go to http://p2pool.hostv.pl/ (once page loads, reload it again with F5), choose node with least ping (and suitable fee), and point your workers to it specifying your payout address as login and any password.

Unfortunately, Erupter blades are currently not supported because of their shitty on-board software which results in about 50% stales on p2pool (details based on my research: https://bitcointalk.org/index.php?topic=18313.msg2622669#msg2622669). Erupter USBs, however, work perfectly.

P.S. NMC merged mining is supported if you run your own node. However, it is not pooled! This means you will mine BTC in pool but NMC are mined solo.

[2weiX]

If you want to mine on a public node, go to http://p2pool.hostv.pl/ (once page loads, reload it again with F5), choose node with least ping (and suitable fee), and point your workers to it specifying your payout address as login and any password.

yeah, that exact synax woultd be nice, for BFGminer.

[baloo_kiev]

If you want to mine on a public node, go to http://p2pool.hostv.pl/ (once page loads, reload it again with F5), choose node with least ping (and suitable fee), and point your workers to it specifying your payout address as login and any password.

yeah, that exact synax woultd be nice, for BFGminer.

What do you mean with "exact syntax"? Try

Code:

bfgminer -o stratum+tcp://78.27.191.182:8349 -u 1YourBTCaddress -p x

[baloo_kiev]

Great news!

P2Pool release 13.0  - HARDFORK, UPGRADE REQUIRED - commit hash: f3a0e8dfcd872716123771db7900cdcd963b91ce

Windows binary: http://u.forre.st/u/xqerwrpk/p2pool_win32_13.0.zip
Windows binary signature: http://u.forre.st/u/viejmrru/p2pool_win32_13.0.zip.sig
Source zipball: https://github.com/forrestv/p2pool/zipball/13.0
Source tarball: https://github.com/forrestv/p2pool/tarball/13.0

After 50% of each P2Pool's mining power has upgraded, warnings will be displayed to everyone who hasn't upgraded. Approximately 24 hours after 95% of the mining power has upgraded, the switch will happen.

Changes:
* Hardfork at 95% upgraded:
** Bitcoin share period increased from 10 to 30 seconds to cater to ASIC miners. Avalon/BFL/ASICMINER devices should start working well after this.
** Litecoin share period increased from 10 to 15 seconds
** Litecoin payouts spread over 3 block-lengths instead of 12, reducing dust payouts
** Transaction pre-forwarding greatly simplified, allowing future network traffic reductions
** Maximum share difficulty multiplier increased from 10x to 30x to give more freedom to below share difficulty adjustments
** OP_RETURN used in last txout to prevent UTXO database spam
** Stratum nonce length increased from 4 to 8 bytes, allowing for future Avalon support without having to use the "avalon" branch

* Automatically increase share difficulty to prevent payouts below "dust threshold", 0.001 BTC and 0.03 LTC
* Automatically increase share difficulty to prevent any single node from making more than 5% of shares, by default
* Worker username parameters (+PSEUDOSHARE_DIFF/SHARE_DIFF) not longer have to be in a specific order
* Support for submitblock RPC call in new Litecoin versions
* Fixed incompatibility with ASICMINER BE Blade
* Updated bootstrap address list