Author

Topic: Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB - page 206. (Read 1061449 times)

full member
Activity: 172
Merit: 100
The luck is NOT caused or effected by the attack, but I could certainly see the attacker using that as more fuel for the "leave Eligius" fire, unfortunately.

Bah, Eligius runs smooth and has great support. There is need for pool jumping. *gets a fire extinguisher and blows out the fire*
legendary
Activity: 1223
Merit: 1006
there timing to attack is right on during consecutive low luck days

Is it possible that the attacks are impacting 'luck'? Does the decreasing hash rate of the pool during these attacks have any impact luck? (or is it not really decreasing? just bad stats?) I'm new to mining so excuse me if these are dumb questions. I noticed the luck decreasing since the difficulty change, I understand that it takes longer to complete a block now but it looks like the luck calc takes that into consideration. Keep up the good work WK.

See my post above.

The luck is NOT caused or effected by the attack, but I could certainly see the attacker using that as more fuel for the "leave Eligius" fire, unfortunately.
nwp
newbie
Activity: 8
Merit: 0
there timing to attack is right on during consecutive low luck days

Is it possible that the attacks are impacting 'luck'? Does the decreasing hash rate of the pool during these attacks have any impact luck? (or is it not really decreasing? just bad stats?) I'm new to mining so excuse me if these are dumb questions. I noticed the luck decreasing since the difficulty change, I understand that it takes longer to complete a block now but it looks like the luck calc takes that into consideration. Keep up the good work WK.


EDIT: Looks like WK answered my question while I was typing it up Smiley
legendary
Activity: 1223
Merit: 1006
there timing to attack is right on during consecutive low luck days

Yeah, I was thinking that.

The luck is NOT caused or effected by the attack, but I could certainly see the attacker using that as more fuel for the "leave Eligius" fire, unfortunately.
sr. member
Activity: 406
Merit: 250
there timing to attack is right on during consecutive low luck days
sr. member
Activity: 462
Merit: 250

tl;dr  - There are are 3 likely suspects...



KNC, ghash or BTCGuild

I doubt it's Discus Fish since many of the people who would leave Eligius for calmer waters would not pick a Chinese centric pool


If it is not the above three, then it is something personal and/or jealously as the driving factor
hero member
Activity: 826
Merit: 1000
Well now I see normal 0,5% rejects... It was about 15 minutes where I was seeing about 6% of them... That is BFGminer data not pool...
legendary
Activity: 1223
Merit: 1006
If your miner is connected, and shares are being accepted.... just ignore the stats.

I'm actually about the just shut them down while they're being attacked so people don't get confused and think they aren't hashing properly.
hero member
Activity: 826
Merit: 1000
I'm seeing large amounts of shars on backup pool and also drop in pool hashing rate. There must be something wrong...

They're hitting some pool nodes as well as the web server.  Generally the pool nodes will reorganize themselves within a minute or so in response.
sorry for posting this but for some reason I didn't see new posts after hitting refresh. I can see them now... I also see a lot of rejects. About 6%...
legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
The ongoing DDoS had shifted gears and they're attacking database intense functions of the stats from thousands of IPs making it hard to filter.

Its causing *stats side* database replication lag, which is playing havoc with random hashrate calcs.

Pool side (ie: the important stuff like earnings) are not affected.

The attackers goal seems to be to stir up confusion.   Judging by these posts its unfortunately working. :-/



Thanks for the update. Do you have any idea how much assets you would need to get a better protection? If I or we all had a better idea, I'd go for a crowd-funding-round.

Not really the point. I honestly am pretty irritated that some person or group has decided that Eligius, a project I volunteer my free time and resources towards, is to be their target without even any reasons or explanations  given.

It's very discouraging and I'm at the end of my patience trying to deal with it.

So, I just ask that everyone please understand that I can't keep dedicating time and effort into combating this pointless attack when other items on the list are more important. I've spent many many hours hardening the pool side against this so that miner earnings arent effected.

To the attacker(s): I don't know what you want. Please let me know what I've possibly done to deserve a now approaching 3 week long attack and what can be done to rectify it. I have no real funds (nor does the pool) to pay any ransom demands so there is no point in that. In any case, I kindly ask that you stop this nonsense.

same thing on my stats page - most (but only 12/15) miners are showing about 20-30% slower speeds. My single bitfury unit looks unaffected along with 2 antminers. the other antminers all sit about 40GH less. hopefully this is just stats-side in which case I can deal with it for a while like with the fail-safe - but it would be nice if there was an objective way to check the pool hashrate (blocks solved on blockchain might show this, but would need 3+ hours of data to be remotely close to an actual average)

There is not much reason why a single person or very small group would go to these efforts against you for such a long period - the goal unless its personal against you just isnt clear in terms of benefit to him/her/them

A government entity makes no sense. They have very little to gain from destabilising a mining pool if it is not actually directly damaging the network hashrate. Thier attacks would be far more effective on trading or bitcoin news sites.

My guess is that some other pool is responsible. A pool attacking would work to shake loose eligius users to join other pools (presumably more stable, larger ones that charge larger fees - *cough*) - This theory serves a direct financial benefit to the attacker.

tl;dr  - There are are 3 likely suspects...
full member
Activity: 196
Merit: 100
The ongoing DDoS had shifted gears and they're attacking database intense functions of the stats from thousands of IPs making it hard to filter.

Its causing *stats side* database replication lag, which is playing havoc with random hashrate calcs.

Pool side (ie: the important stuff like earnings) are not affected.

The attackers goal seems to be to stir up confusion.   Judging by these posts its unfortunately working. :-/



Thanks for the update. Do you have any idea how much assets you would need to get a better protection? If I or we all had a better idea, I'd go for a crowd-funding-round.

Not really the point. I honestly am pretty irritated that some person or group has decided that Eligius, a project I volunteer my free time and resources towards, is to be their target without even any reasons or explanations  given.

It's very discouraging and I'm at the end of my patience trying to deal with it.

Maybe it's time to think about selling Eligius to someone who can make it an enterprise which isn't reliant on the altruism of a single individual.

Donating it to a non-profit organization would be another possible alternative.  In that case you'd probably be named as a board member.  I don't know about others, but I'd definitely feel better about donating to a non-profit organization than to...what exactly is Eligius anyway?  A partnership?  (For liability reasons I sure hope not!  But given that I don't see any "LLC" or "Inc." or "Ltd." in the name that's apparently what it is.)
legendary
Activity: 1484
Merit: 1007
spreadcoin.info
some strange spikes, as if my miners are hyperventilating or something:

http://eligius.st/~wizkid057/newstats/userstats.php/16bWt62xq5rmQuGscq7L7GuZfYmZkkvN5x
legendary
Activity: 1223
Merit: 1006
I'm seeing large amounts of shars on backup pool and also drop in pool hashing rate. There must be something wrong...

They're hitting some pool nodes as well as the web server.  Generally the pool nodes will reorganize themselves within a minute or so in response.
hero member
Activity: 826
Merit: 1000
I'm seeing large amounts of shars on backup pool and also drop in pool hashing rate. There must be something wrong...
legendary
Activity: 1223
Merit: 1006
The ongoing DDoS had shifted gears and they're attacking database intense functions of the stats from thousands of IPs making it hard to filter.

Its causing *stats side* database replication lag, which is playing havoc with random hashrate calcs.

Pool side (ie: the important stuff like earnings) are not affected.

The attackers goal seems to be to stir up confusion.   Judging by these posts its unfortunately working. :-/



Thanks for the update. Do you have any idea how much assets you would need to get a better protection? If I or we all had a better idea, I'd go for a crowd-funding-round.

Not really the point. I honestly am pretty irritated that some person or group has decided that Eligius, a project I volunteer my free time and resources towards, is to be their target without even any reasons or explanations  given.

It's very discouraging and I'm at the end of my patience trying to deal with it.

So, I just ask that everyone please understand that I can't keep dedicating time and effort into combating this pointless attack when other items on the list are more important. I've spent many many hours hardening the pool side against this so that miner earnings arent effected.

To the attacker(s): I don't know what you want. Please let me know what I've possibly done to deserve a now approaching 3 week long attack and what can be done to rectify it. I have no real funds (nor does the pool) to pay any ransom demands so there is no point in that. In any case, I kindly ask that you stop this nonsense.
legendary
Activity: 1223
Merit: 1006
My April 7 payout does not show as mined btc this time.
Why the change in reporting acquisition method?

Manual payout.  See my post from last night.
member
Activity: 70
Merit: 10
My April 7 payout does not show as mined btc this time.
Why the change in reporting acquisition method?
newbie
Activity: 56
Merit: 0
The ongoing DDoS had shifted gears and they're attacking database intense functions of the stats from thousands of IPs making it hard to filter.

Its causing *stats side* database replication lag, which is playing havoc with random hashrate calcs.

Pool side (ie: the important stuff like earnings) are not affected.

The attackers goal seems to be to stir up confusion.   Judging by these posts its unfortunately working. :-/



Thanks for the update. Do you have any idea how much assets you would need to get a better protection? If I or we all had a better idea, I'd go for a crowd-funding-round.
legendary
Activity: 1223
Merit: 1006
The ongoing DDoS had shifted gears and they're attacking database intense functions of the stats from thousands of IPs making it hard to filter.

Its causing *stats side* database replication lag, which is playing havoc with random hashrate calcs.

Pool side (ie: the important stuff like earnings) are not affected.

The attackers goal seems to be to stir up confusion.   Judging by these posts its unfortunately working. :-/

What I did on one of my sites running nginx and php was to use xcache to store the results of database calls for a period of time. I had wrapper functions for any database info I needed, and would cache the result for 30 seconds up to 15 minutes depending on what it was. This way even if someone did an endless spam of page reloads, it'd only affect the web server and the database server wouldn't even notice. Maybe something like that would help.

There is already pretty robust caching in place... however it doesn't help when the attack is specifically designed against the Eligius stats and each request is looking for new information.  These attackers are pretty determined.
sr. member
Activity: 434
Merit: 250
The ongoing DDoS had shifted gears and they're attacking database intense functions of the stats from thousands of IPs making it hard to filter.

Its causing *stats side* database replication lag, which is playing havoc with random hashrate calcs.

Pool side (ie: the important stuff like earnings) are not affected.

The attackers goal seems to be to stir up confusion.   Judging by these posts its unfortunately working. :-/

What I did on one of my sites running nginx and php was to use xcache to store the results of database calls for a period of time. I had wrapper functions for any database info I needed, and would cache the result for 30 seconds up to 15 minutes depending on what it was. This way even if someone did an endless spam of page reloads, it'd only affect the web server and the database server wouldn't even notice. Maybe something like that would help.
Jump to: