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

[K1773R]

Hello everyone,

BIP66 implements a Bitcoin softfork which will take effect sometime between the next few days and the next few weeks. Miners that have not upgraded to Bitcoin Core >=0.10.0 will generate invalid blocks after that point.

Bitcoin softforks are handled within P2Pool by a corresponding fork which forces P2Pool users to upgrade to a newer version of P2Pool. In this case, the new version of P2Pool will require Bitcoin Core >=0.10.0 to start. This is facilitated by first getting 50% of the P2Pool hashrate to upgrade by external means (this forum and the mailing list below), upon which the "A MAJORITY OF SHARES CONTAIN A VOTE FOR AN UNSUPPORTED SHARE IMPLEMENTATION! An upgrade is likely necessary. Check http://p2pool.forre.st/ for more information." warning is displayed to the rest of the users, which hopefully quickly upgrade. Upon 95% of the hashrate having converted, the fork happens, and users that haven't upgraded are split off to mine in their own mini-P2Pool. I regret not taking action earlier; I hadn't been aware of the softfork until an email on the bitcoin-dev mailing list today.

So, a new P2Pool version will be released within the next day or two, once testing has finished. Users will be urged to upgrade here and on the p2pool-notifications mailing list (which I'd urge you to subscribe to now if you haven't). Without this P2Pool softfork, we will continue mining with an unknown number of users generating invalid blocks, which clearly isn't desirable.

When forking can you also fix the tx size? currently new txs included in blocks can only be 50kb max!

[1714282996]

1714282996

[1714282996]

1714282996

[1714282996]

1714282996

[1714282996]

1714282996

[1714282996]

1714282996

[chalkboard17]

Forrest, perhaps you as a main developer could help with the problems I recently described on s5
I need to run a ssh command everytime after i reboot + hashrate from time to time drops to 650gh/s (only one board works)  it then restarts working after some time (seconds or many minutes sometimes) but my overall longterm hashrate goes from 1380 to 1345.
This doesnt happen on any other pool
This happens on any p2pool, my node or others

Thanks

[TierNolan]

Upon 95% of the hashrate having converted, the fork happens, and users that haven't upgraded are split off to mine in their own mini-P2Pool. I regret not taking action earlier; I hadn't been aware of the softfork until an email on the bitcoin-dev mailing list today.

Does this vote p2pool in favor of the fork, or would it just vote depending on which version of bitcoind the miner uses?

[forrestv]

Does this vote p2pool in favor of the fork, or would it just vote depending on which version of bitcoind the miner uses?

That's up to the bitcoind the block-finding miner uses. The P2Pool fork is just to force everyone to use an updated bitcoind.

[yslyung]

Does this vote p2pool in favor of the fork, or would it just vote depending on which version of bitcoind the miner uses?

That's up to the bitcoind the block-finding miner uses. The P2Pool fork is just to force everyone to use an updated bitcoind.

is it out yet ? looking fwd to some improvements !

[jcumins]

Is any one having issues with S-5 on P2P locking up and becoming non responsive.  I have numerous ones that seem to be doing this.  I am running CG ver 4.8  can any one running S-5 charm in and give me some of your thoughts. I am running the April 2015 firmware.

Thanks

[Meuh6879]

you use a local node (of P2Pool) ... or a remote node (not you that launch and keep running the P2Pool node) ?

[p3yot33at3r]

I am running the April 2015 firmware.

All my S5's are running the original firmware, kano's cgminer fix & a queue setting of 1 - all run fine with p2pool. I always avoid bitmain firmware upgrades as they seem to create more problems than they fix  It's the old saying: "If it ain't broke......"

Is anyone using the Avalon 4.1's with p2pool? I'm interested in how they perform........

Tak.

[TheAnalogKid]

Is any one having issues with S-5 on P2P locking up and becoming non responsive.  I have numerous ones that seem to be doing this.  I am running CG ver 4.8  can any one running S-5 charm in and give me some of your thoughts. I am running the April 2015 firmware.

Thanks

Bitmain hardware will lock up no matter the pool, it's just how they are.  They all of a sudden will "go out to lunch" and need a hard power cycle to kick them back into gear.

I had a large number of S5's deployed, I'd cycle a handful of them each week, and not always the same ones.  I just deployed 3x S4+ boxes last week.  Friday 2 of them went out, Sunday evening the other went out.  Power cycled today, back hashing, but just waiting for the next time.  Brand new.

[jcumins]

I was told by Bitmain support non of the Bitmain S Series are designed to work with P2P due the the work reset process of P2P.  My s-3 work perfectly, my s-4 has had no issues but these darn s-5 all get stupid from time to time to the point i had to replace the pdu in my cab in the data center to remote resetable PDU and a great expense and a trip to the data center.

I might try and go back to the old firmware and a cgminer upgrade to see if that helps.

I like running my own node and I like the thought of P2P, but haveing to reboot hardware every day is getting old.

[valkir]

Still dont understand why do people refuse to mine on p2pool?

Any good explanation for that ?

Bitcoin is suppoce to be decentralised and p2pool is right ?

[chalkboard17]

Still dont understand why do people refuse to mine on p2pool?

Any good explanation for that ?

Bitcoin is suppoce to be decentralised and p2pool is right ?

I tried. Hard. Couldn't afford investing more time into it and am being forced into mining on centralized pool, disrupting bitcoin's decentralization purpose and probably having my hashrate stolen once in awhile or used for other purposes I didn't agree.

[valkir]

Not sure to understand. You try to mine on p2pool ?? What didnt work ? I mean it should be easy connect to a node and mine?

[chalkboard17]

Not sure to understand. You try to mine on p2pool ?? What didnt work ? I mean it should be easy connect to a node and mine?

Trust me, other people and I who faced issues tried that. I get slightly lower hashrate on p2pool and also one hashing board stops once in awhile, decreasing further hashrate. Have a look at my previous posts.

[Geremia]

When only 3 of my 4 S5 chains were working, I was mining on P2Pool with very low variance in the hashrate. Now that I have all 4 chains running, I get high hashrate variability, and sometimes a miner just stops hashing as chalkboard17 says here. Bitcoind GetBlockTemplate Latency seems to be the bottleneck. I currently have a mean latency of 1.37 sec., but sometimes the latency is at most 3 sec.! My hashrate on both S5s is about 0.1 Th/s slower than optimal (1.1 Th/s).

I'm using cgminer 4.9.0 (http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer) with "--queue 0". Perhaps "-queue" should be a tad > 0? Would that help with the GetBlockTemplate Latency issues?

Update: I just tried "--queue 1" (which is cgminer's default; the default on S5s is something over 8000, which is WAAY too big to be useful with P2Pool), and it does not seem to be helping.

[p3yot33at3r]

I was told by Bitmain support non of the Bitmain S Series are designed to work with P2P due the the work reset process of P2P.

Did they now? Can you yell me who told you this at bitmain? I'm afraid bitmain & their "support" staff are pretty clueless when it comes to p2pool, as their attempted clone of it clearly shows. I wouldn't take any notice of him/them.

Getting a slightly lower hash rate is normal with p2pool, it's always been like this I believe. If your units are locking up, try lowering the OC settings - you're probably working them too hard.

[Meuh6879]

Still dont understand why do people refuse to mine on p2pool?

Any good explanation for that ?

Bitcoin is suppoce to be decentralised and p2pool is right ?

I tried. Hard.

me too ... but if no person can maintenance the P2Pool when Bitcoin Core upgrade ... Bitcoin Core v0.9.5 and early crash with a P2Pool.

I need to kill and relaunch P2Pool node + Bitcon Core + Miner every hour for ... hash.



Bitcoin Core work flawless with SOLO MINING (No P2Pool but with miner software).
Bitcoin Core close when P2Pool node is already working ... thaht why i must kill P2Pool before i relaunch Bitcoin Core v0.10.x

---

I have try to mine on remote P2Pool ... but it don't decrease difficulty (like it stay at 500 when i must have a 12-8 on my little miner).

[p3yot33at3r]

P2pool works fine with Bitcoind/qt. Can you provide more info?

ie: What OS/distro?

Do you have all the required dependences?

Have you built from source or using pre-compiled binaries?

What hardware are you using?

etc......

Tak.

[yslyung]

i have no crash last 5 days at least using bitcoin core qt v0.10.2 running on widows via python

i am sure there's something wrong with the crash setup.

you can visit my node to have a look.

[valkir]

When only 3 of my 4 S5 chains were working, I was mining on P2Pool with very low variance in the hashrate. Now that I have all 4 chains running, I get high hashrate variability, and sometimes a miner just stops hashing as chalkboard17 says here. Bitcoind GetBlockTemplate Latency seems to be the bottleneck. I currently have a mean latency of 1.37 sec., but sometimes the latency is at most 3 sec.! My hashrate on both S5s is about 0.1 Th/s slower than optimal (1.1 Th/s).

I'm using cgminer 4.9.0 (http://ck.kolivas.org/apps/cgminer/antminer/s5/4.9.0-150105/cgminer) with "--queue 0". Perhaps "-queue" should be a tad > 0? Would that help with the GetBlockTemplate Latency issues?

Update: I just tried "--queue 1" (which is cgminer's default; the default on S5s is something over 8000, which is WAAY too big to be useful with P2Pool), and it does not seem to be helping.

I saw somewhere (didnt find the thread) that S5 have problem with P2Pool but that S3 and S4 have no problem.
Maybe its a firmware problem.  

Why do conman doest work on P2Pool?