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

[Yzord]

Ah, at the end it is the same as using Slush's pool then? Is there a good thing which i should take in mind to switch over to a p2pool? Or is staying with Slush pool eventually the same?

[K1773R]

So simply running my own server is the best thing to do? And i have set a new p2pool which is located in my country and i receive a lot less rejects now. But they do not have many users, so i guess finding and finishing a block isn't top notch i guess

its p2pool, it dosnt matter at which p2pool instance you mine on (well there are some faulty ones out there intending to steal coins)...
the best way is to run p2pool locally

[Yzord]

Thanks you very much for all your answers...i like this forum

[mdude77]

Ah, at the end it is the same as using Slush's pool then? Is there a good thing which i should take in mind to switch over to a p2pool? Or is staying with Slush pool eventually the same?

Statistically, using p2pool will be the same as solo mining over time, minus whatever amount you choose to donate to the author (or whatever the node you are using is charging you).  The higher your hash rate, the lowest the variance, and the quicker that will statistically even out. 

Running a local node isn't that hard.  Try it, if after a few days it doesn't seem to be working out, there are a number of reliable public nodes out there.

Lastly, whatever you do, I recommend having backup pools in your mining configuration.  Just don't cross pool types, it isn't guaranteed to work.  That is, if your main is a p2pool node, all your backups should be p2pool nodes.

M

[twmz]

Uhm, sorry for the noobies question i give here, but i guess i need something sorted out about P2pool. First of all, i always used Slush's pool, so i used cgminer and the same string everyone is using and mined away. Yesterday i read about p2pool and went to the website p2pool.org and all i saw on the mainsite was

Mining for Bitcoins on P2Pool.org is quick and easy. Simply point your miner to the provided URL and use your Bitcoin address as the username and payments will be sent there automatically. Use settings below to start mining BTC!

Pool URL:   http://p2pool.org:9332
Username:   Bitcoin Address
Password:   Anything

Mining at p2pool.org is a bad idea (at least right now) because they are not on the latest version of p2pool software and as such are on a tiny fork of the p2pool network that only has a few GH/s.  You may as well be mining solo.

Run your own node or find a different public node to mine at.

It's unfortunate that such a high visibility public node is out of date.

[K1773R]

Uhm, sorry for the noobies question i give here, but i guess i need something sorted out about P2pool. First of all, i always used Slush's pool, so i used cgminer and the same string everyone is using and mined away. Yesterday i read about p2pool and went to the website p2pool.org and all i saw on the mainsite was

Mining for Bitcoins on P2Pool.org is quick and easy. Simply point your miner to the provided URL and use your Bitcoin address as the username and payments will be sent there automatically. Use settings below to start mining BTC!

Pool URL:   http://p2pool.org:9332
Username:   Bitcoin Address
Password:   Anything

Mining at p2pool.org is a bad idea (at least right now) because they are not on the latest version of p2pool software and as such are on a tiny fork of the p2pool network that only has a few GH/s.  You may as well be mining solo.

Run your own node or find a different public node to mine at.

It's unfortunate that such a high visibility public node is out of date.

mining @ p2pool.org is always a bad idea... run always a local node :S otherwise you kill yourself with latency->stales

[daemondazz]

Terracoin node at at http://cryptominer.org:9322/ has been updated with the latest GIT build of terracoind and p2pool patch from https://github.com/terracoin/p2pool/commit/14b0b75a6aba00304390b7d09fbf6563181732fd.

I've aimed about 1.6GH/s at the node, which appears to be about 70% of the p2pool network hash rate at the moment on the new fork.

[bitpop]

You can set your own difficulty by adding a / or + to your address. But I never understood it. Also if you use a local one, don't use an address as your username. Just u and p.

And when using public, don't choose a password, just use p.

[kano]

You can set your own difficulty by adding a / or + to your address. But I never understood it. Also if you use a local one, don't use an address as your username. Just u and p.

And when using public, don't choose a password, just use p.

e.g. if you set the mining username to be username/+64 then cgminer will mine at 64 difficulty to p2pool
Of course it makes no difference to the number of share-chain shares you find, but it does mean you are sending ~1/64th of the number of shares to the p2pool (that's what I used for the ~week of p2pool mining I did)
I've no idea what happens if you use e.g. username/+100000 ...

[K1773R]

You can set your own difficulty by adding a / or + to your address. But I never understood it. Also if you use a local one, don't use an address as your username. Just u and p.

And when using public, don't choose a password, just use p.

e.g. if you set the mining username to be username/+64 then cgminer will mine at 64 difficulty to p2pool
Of course it makes no difference to the number of share-chain shares you find, but it does mean you are sending ~1/64th of the number of shares to the p2pool (that's what I used for the ~week of p2pool mining I did)
I've no idea what happens if you use e.g. username/+100000 ...

if you set +<int> higher than the current share diff, p2pool will adjust it to the current share diff. so if you put some millions there, you will only submit blocks.

[HellDiverUK]

Setting up your own node is easy, even an idiot like me was able to do it.  Running it on a Celeron 847 machine.

http://847Pool.no-ip.biz:31337

Had a stale share yesterday, but plenty of good ones since.  Making far more than I was on BTCGuild.

[gyverlb]

You can set your own difficulty by adding a / or + to your address. But I never understood it. Also if you use a local one, don't use an address as your username. Just u and p.

And when using public, don't choose a password, just use p.

On a local p2pool node uou can use any username you want. If you have several miners, use a different one for each of them to keep track of how they behave.

However, when configuring the p2pool node you should always use an address of a secure wallet with the "-a" parameter. If you don't p2pool uses an address genereated by the bitcoind it connects to and you shouldn't do that: the address is on a wallet exposed to the Internet: any security breach and your wallet is gone.

There are two difficulties you can setup and usually you don't need to.

The first one is the share difficulty used to compute your rewards, the minimum is enforced by the p2pool network and can't be set (you can see it in logs and on the p2pool web interface). The only reason to raise it is if you have a sizeable portion of the p2pool hashrate and would like to leave room for smaller miners in the sharechain (its size is bounded), this shouldn't be needed in latest p2pool: IIRC the rate of share submission is automatically adjusted now.
If for any reason you should want to change it, you can simply append the difficulty after a "/". If your username is "foo" and wanted difficulty is 20000, just use "foo/20000".

The second one is the miner's target difficulty, used to compute the estimated hashrate in p2pool. It's adjusted automatically so that the rate of shares submitted is ~1 every second which both gives accurate hashrate estimations and low load on p2pool. If you want to change it, you use "+" instead of "/": "foo+64". You can combine the two: "foo/20000+64".

TL;DR: don't use difficulty parameters in the username, you most probably don't need them.

[kano]

You can set your own difficulty by adding a / or + to your address. But I never understood it. Also if you use a local one, don't use an address as your username. Just u and p.

And when using public, don't choose a password, just use p.

On a local p2pool node uou can use any username you want. If you have several miners, use a different one for each of them to keep track of how they behave.

However, when configuring the p2pool node you should always use an address of a secure wallet with the "-a" parameter. If you don't p2pool uses an address genereated by the bitcoind it connects to and you shouldn't do that: the address is on a wallet exposed to the Internet: any security breach and your wallet is gone.

There are two difficulties you can setup and usually you don't need to.

The first one is the share difficulty used to compute your rewards, the minimum is enforced by the p2pool network and can't be set (you can see it in logs and on the p2pool web interface). The only reason to raise it is if you have a sizeable portion of the p2pool hashrate and would like to leave room for smaller miners in the sharechain (its size is bounded), this shouldn't be needed in latest p2pool: IIRC the rate of share submission is automatically adjusted now.
If for any reason you should want to change it, you can simply append the difficulty after a "/". If your username is "foo" and wanted difficulty is 20000, just use "foo/20000".

The second one is the miner's target difficulty, used to compute the estimated hashrate in p2pool. It's adjusted automatically so that the rate of shares submitted is ~1 every second which both gives accurate hashrate estimations and low load on p2pool. If you want to change it, you use "+" instead of "/": "foo+64". You can combine the two: "foo/20000+64".

TL;DR: don't use difficulty parameters in the username, you most probably don't need them.

As I said: username/+64 then cgminer will mine at 64 difficulty to p2pool

However, since the mining difficulty you use makes no difference to the number of share chain shares you get, as long at it is less than the share chain difficulty, it really doesn't matter.
What does matter, is how much work you get cgminer, p2pool and the network to do.
For 72GH/s I was using +64 ... I like powers of 2
My setting was to get a share every few seconds and thus not have a screen full of crap scrolling by, 64 gave me a share every ~4s and also ensures that the difficulty wasn't swapping and changing.

Aside: with normal pool mining I use 256 diff (and have even since I was above 2GH/s many many months ago)

[HellDiverUK]

I just tried running my p2pool node on my "main" server, which is a FX8320.  8-core 3.5GHz.  12GB RAM.  SSD driver.  Getwork latency is 2 seconds compared to 0.3-0.5 on my Celeron machine.  Good effort, AMD.  

[lenny_]

I just tried running my p2pool node on my "main" server, which is a FX8320.  8-core 3.5GHz.  12GB RAM.  SSD driver.  Getwork latency is 2 seconds compared to 0.3-0.5 on my Celeron machine.  Good effort, AMD.  

Problem is on your side. Fix your system/software.
I have 0.2s on slower AMD APU machine (Linux AMD64).

[HellDiverUK]

Yeah, I think there's something odd going on with Server 2012.  It's hovering about 0.7s at the moment.  Ran much better on Windows 7 on the Celeron 847. 

I think I'm going to abandon the idea of running the pool node on this machine.

[HellDiverUK]

And I'm back to the Celeron machine.  I set CPU Affinity to bitcoin-qt to one CPU core and p2pool.exe to the other, and I'm getting sub-0.2s latency.  Job jobbed.

[MINX]

There is definitely something strange with Terracoin, I continue having troubles with TRC and P2pool but today the Terracoin wallet is unable to synchronize with the network from about 5 hours ago and it's stuck in block 175050.  

[evilpete]

TRC was flooded with hashpower, I think they 51%'ed it as well to orphan other miners blocks.  The difficulty was jacked up through through the roof, then then left.

https://bitcointalk.org/index.php?topic=261986.0

This is the downside of short interval difficulty adjustment.  The two week one on bitcoin may be annoying but the short ones are open to far more abuse.

[kano]

TRC was flooded with hashpower, I think they 51%'ed it as well to orphan other miners blocks.  The difficulty was jacked up through through the roof, then then left.

https://bitcointalk.org/index.php?topic=261986.0

This is the downside of short interval difficulty adjustment.  The two week one on bitcoin may be annoying but the short ones are open to far more abuse.

No, it is the result of having a pump and dump scam coin with little network support ...