Author

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

legendary
Activity: 1258
Merit: 1027
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... Wink
legendary
Activity: 2212
Merit: 1038
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.
member
Activity: 193
Merit: 10
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......
member
Activity: 193
Merit: 10
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.
full member
Activity: 238
Merit: 100
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?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
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.
member
Activity: 193
Merit: 10

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...
legendary
Activity: 2212
Merit: 1038

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.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/

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.
legendary
Activity: 2212
Merit: 1038
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.
member
Activity: 193
Merit: 10

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 ?
legendary
Activity: 2212
Merit: 1038
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?
legendary
Activity: 2212
Merit: 1038
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?

legendary
Activity: 1512
Merit: 1012
Else p2pool will die in some month.

P2Pool is here since 2011 ... little boy !
legendary
Activity: 2212
Merit: 1038
I've downloaded the p2pool binary and I've sandboxed that as the discussion on github suggests that python is being exploited to cause the memory leak in bitcoind.
member
Activity: 88
Merit: 10
Hi all.
What do think about very low global pool rate?
How we can pull up global hashrate? We need 3-5Ph in continues time. Else p2pool will die in some month.
Bye.
legendary
Activity: 1512
Merit: 1012
Anybody else noticing unusual activity, or is it just me?

not relevant ... for me.

legendary
Activity: 2212
Merit: 1038
My sandboxed bitcoind isn't working anymore it's started leaking memory or something again, I just had to restart it. Could Microsoft be working with Rand and Google to cause this? There must be teams of people working together to cause this, it can't be easy to get inside a sandboxed application.
legendary
Activity: 1258
Merit: 1027
The pool rate is a best estimate based on the number of valid shares and difficulty.

It is an estimate and will fluctuate, often wildly.

The 24 hour average rate may be a more stable metric.
legendary
Activity: 2212
Merit: 1038
Currently they've managed to push my GBT latency to 10s and appear to be targeting p2pool with some kind of impotent attack. Fortunately it's having little to no effect, at least on my node (currently at 116.8% efficiency). However, I can see the pool rate currently plummeting below 1PH.
Jump to: