Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 177. (Read 2591920 times)

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?

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.

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 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.

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.

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.

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

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

is it out yet ? looking fwd to some improvements !

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

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

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

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

the man is watching.

waiting for the release (hoping there will be improvements) & ready to upgrade.

thx forrestv & rest of the gang.

Absolutely!

Hopefully this will be the start of a new era of communication with p2pool users on this forum 

Forrestv - will there be any other improvements/fixes/additions to the new p2pool release?

Thanks, & welcome back 

The Prodigal Son has returned!

Thanks for the update, and I echo windpath's sentiments: glad to see you around.  I'll be sure to update my nodes as soon as you have completed your work.

Thank you Forrest, good to see you around!

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.

i don't even know or have any idea how are you a hero member at all ?

1st PLEASE read the posts regarding merged mining about 2 pages back.

2nd i think you are a little lost with regards of discussion

3rd yes i am very well aware that i am on a bitcoin thread -> pool -> p2pool that can MERGE mine other crypto coin aka altcoins

so what are you trying to say ? i think you are LOST somewhere.

do you run your own node ? do you merge mine ? do you have any idea at all ? do you read before you post ?

yes the graph you posted that occasionally spikes 1ph or more is from me directing the "extra" hashpower to help p2pool to hit some blocks & i hope you managed to gain some btc from mining at p2pool.