Topic: [POLL] Why don't you mine in p2pool? (Read 3274 times)

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

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

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

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.

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?

$ 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?

python run_p2pool.py --net bitcoin --merged http://:@127.0.0.1:/ -w   

p2pool crashes too often.
I need a stable pool.

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

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.

I guess something is wrong with your code and how it handles stratum connections. Have you seen this? https://bitcointalksearch.org/topic/m.2167883

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

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

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.

Accepted untracked stratum share

security issues..

don't forget DoS attacks

security issues..

don't forget DoS attacks

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.

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.

Mine one day, 5 blocks found.... It's called variance.

Where is the "I do mine on p2pool" option?

Other: the need to run a node. It eats up bandwidth and cpu power. Plus you need high bandwidth and good connectivity to get low stales/DOA. Sure, you can use a p2pool node, but they're not as "trusted" as most pools.

My hashrate is low so I would have many insignificant transactions.