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

[notbatman]

I've been running the p2pool v15.0 windows binary (sandboxed) for a bit now but I've noticed that every incoming connection is from a v14 client:

2016-01-10 18:38:20.709000 Incoming connection to peer 195.208.39.210:4647 established. p2pool version: 1400 '14.0
2016-01-10 18:38:49.754000 Incoming connection to peer 80.169.241.69:38395 established. p2pool version: 1400 '14.0-23-g6514fd8-dirty'
2016-01-10 18:39:50.613000 Incoming connection to peer 71.8.220.126:39040 established. p2pool version: 1400 '14.0'
2016-01-10 18:41:11.713000 Incoming connection to peer 208.111.52.2:59707 established. p2pool version: 1400 '14.0-9-g4e5afe9'
2016-01-10 18:42:01.361000 Incoming connection to peer 89.22.129.82:50956 established. p2pool version: 1400 '14.0-9-g4e5afe9'
2016-01-10 18:44:14.349000 Incoming connection to peer 212.18.229.18:37078 established. p2pool version: 1400 '14.0-23-g6514fd8'

2016-01-10 18:52:31.344000 P2Pool: 17354 shares in chain (9147 verified/17359 total) Peers: 6 (0 incoming)


Am I the only user running p2pool v15 what's going on here?

[notbatman]

Now some kind of surge/EMP just shut down both my bitcoind/p2pool node and my Ethereum GPU rig that are on separate circuits I might add. Lights that are on the same circuits didn't even flicker, 'the hell man?

[nicklello]

I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?

[notbatman]

Else p2pool will die in some month.

P2Pool is here since 2011 ... little boy !

I get extremely bad vibes looking at that picture, she's definitely attractive but I don't think she's a nice person to be around. There's a lot of talk about satanic/psychopathic people in Hollywood.

To stay on-topic I agree, p2pool isn't going away any time soon.

[-ck]

I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?

Nothing quite like a conspiracy theory... they come up every time luck doesn't look so good. Nope, it's just that p2pool's hashrate is insignificant.

[notbatman]

I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?

The luck of one pool has absolutely no effect on the luck of other pools. Rapidly rising difficulty is to blame here.

[nicklello]

I'm wondering if someone has just started a new (large) mining op.... several pools (ie: not just p2pool) have sudden bad luck; slush for example has gone from 3-5 hours per round to over 15 hours for the current round.

Last new block on p2pool was about 4 days ago ?

Nothing quite like a conspiracy theory... they come up every time luck doesn't look so good. Nope, it's just that p2pool's hashrate is insignificant.

It's not meant to be a conspiracy theory... just trying to figure why all of the pools I'm involved in are suddenly getting such bad luck/long rounds...

[-ck]

It's not meant to be a conspiracy theory... just trying to figure why all of the pools I'm involved in are suddenly getting such bad luck/long rounds...

Same thing - bad luck. Look around and you'll see not all pools are having bad luck. Overall luck is "average" across all the pools. Some are having a streak of good luck.

[idonothave]

hypotethical question
if kano used his pool to mine with p2pool as a node, would it be more efficient mining fot his pool or not?

[nicklello]

It's not meant to be a conspiracy theory... just trying to figure why all of the pools I'm involved in are suddenly getting such bad luck/long rounds...

Same thing - bad luck. Look around and you'll see not all pools are having bad luck. Overall luck is "average" across all the pools. Some are having a streak of good luck.

I guess I've just selected a bad set of pools to look at then.

[nicklello]

hypotethical question
if kano used his pool to mine with p2pool as a node, would it be more efficient mining fot his pool or not?

Interesting idea... however I suspect Kano wouldn't want to risk the stability of his pool software (I'm assuming you mean altering/extending ckpool so shares are distributed with/like p2pool).

I'd prefer to ask: What would need to be different within bitcoin to make solo mining feasible again ?

I suspect Smaller (not Larger) blocks would be the solution as it would give the 'small' guy (< 1Th/s) a better chance of an income......

[notbatman]

OK, you want conspiracy theory?

I'm going to venture a guess that it's these hundreds of v14 p2pool clients that keep connecting to my node that are responsible for the python exploit that's causing the bitcoind memory leak. I'm also going to guess that sandboxing the compiled version of p2pool mitigated the problem and they hit me with an EMP targeted at the resonance frequency of the inductors in my PSUs shutting down both my mining computers as show of force that they can shut me down any time they want.

[windpath]

OK, you want conspiracy theory?

I'm going to venture a guess that it's these hundreds of v14 p2pool clients that keep connecting to my node that are responsible for the python exploit that's causing the bitcoind memory leak. I'm also going to guess that sandboxing the compiled version of p2pool mitigated the problem and they hit me with an EMP targeted at the resonance frequency of the inductors in my PSUs shutting down both my mining computers as show of force that they can shut me down any time they want.

Just wrap them in tinfoil, then you'll be protected...

[AndreyNag]

Else p2pool will die in some month.

P2Pool is here since 2011 ... little boy !

Tell me "Big boy" why P2pool is here since 2011, but now falls in a deep hole. And when the falls end and pool rise up?
Today global power is from 0.7 to 1Ph and 123 hours of waiting - do You think this is normal and nothing to worry about?
If you really think that you have leed balls.

[Meuh6879]

P2Pool is a support (backup) for all pools of bitcoin around the world ... usually farm start, on P2Pool, different grid to measure the performance, and then switch to local stratum server.

P2Pool never die at the end, because, it's the last wall of mining process (DDoS proof).

The power of P2Pool, you earn the SAME AMOUNT of bitcoins when you are on a big pool or on the P2Pool ... after 3 months. 

I mine on P2Pool since 2 years.

[Cassey]

Hi all.  Thought I'd check out p2pool for my local 16.5TH of mining.

Happy to say it all went smoothly for doing straight bitcoin mining.  Saw a few python exceptions during startup, but once it got initialized, it appears to be working fine.

I'm not having as much luck with merged mining bitcoin and namecoin.

Syntactically all appears fine, and initialization proceeds as above.  However I see:



Reoccurring frequently in the console output.  All my miners are also showing a Diff of 1, which is a change.

Any thoughts?

Edit:  Also seem to be stuck at 8 connections, even though I'm starting up with " --max-conns=256" and my bitcoind has 19 connections.

Pool stats at:  http://ngspoe.carpenter-farms.us:9332/static/

Update:  Found my stupid mistake, was specifying namecoins coin port instead of the rpcport on the --merged line.  The Diff of 1 also cleared itself up after a few minutes.

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

[windpath]

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...

[Cassey]

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...

Thanks.  Somehow I missed that port reference from the guide I was using to install.  I had 9332 open, but not 9333.  It is now opened and dnatted to my p2pool VM.  Not sure it matters but I'll restart the p2pool just to be safe.  I'll drop max connections some while its down.

[idonothave]

Still concerned about the number of connections being low.  Any thoughts on how to encourage more of them?

Welcome!

Be sure port 9333 is open for inbound connections, if it already is be patient... The inbound peers will come

As an aside, 256 is an insanely high number of peers, not much benefit from that many peers... We limit our node to 35, 25 inbound and 10 out...

Thanks.  Somehow I missed that port reference from the guide I was using to install.  I had 9332 open, but not 9333.  It is now opened and dnatted to my p2pool VM.  Not sure it matters but I'll restart the p2pool just to be safe.  I'll drop max connections some while its down.

you do not need to bind with every existing node. I run my node satisfied with 3 out 1 in connections and relaynode by Matt. I use github bitcoind with no conf change with <0.2s gbt latency (0.165s daily average just now, monthly average 0.188s) and github p2pool 15.0-11 keeping both in last version.

[idonothave]

if anybody interested to mine in central Europe, Czech republic, there is a node http://185.73.103.2:9332/
fee 0.9%, author donation 0.1%
johndoe stats @ http://185.73.103.2:9332/static/jd/

plans

to add spare hw to backup it using load balancing tools
to backup it via another independent internet connection
to build website @ sexy domain name