Status as of Friday, June 30, 2017

mrgoldy
Archived posts: 55
Joined: Jun 02, 2017

Re: Status as of Friday, June 30, 2017

by mrgoldy · · Post #6868

copy of discussion from the slack chat:
we would be fine until the attacker changed the flood type
then it would take time for javapipe to find where the attack is taking place.
flood type changes, javapipe finds new solution, is that new solution then permanent and that flood type could never happen again?

If the answer is that as javapipe grows/defends, that they become more reliable with less down time. I would say stay with javapipe
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Status as of Friday, June 30, 2017

by Steve Sokolowski · · Post #6869

piet wrote:"we" already pay 4% more compared to other pools... for this 4% you can`t offer a decent uptime / service / ddos protection ?

Lets do some math;
40.000 earning per day, 5% of this is 2.000 per day = 60k monthly, this isnt enough for some decent uptime !?

I switched to another pool and i`m quite happy with it, earnings are (only) slightly lower but constant! and no payout problems, coin problems, router problems, holiday errors, weather problems, etc, etc, etc, etc, etc...
Unfortunately, the big picture isn't as rosy as that.

Of all revenue, about 0.5% is lost in exchange trading fees, 0.25% in withdrawal fees, 0.25% in network transaction fees, 1% in slippage, 0.5% in servers, bandwidth, and electricity usage of the servers, a small amount (currently) in DDoS attack protection, and 0.4% in salaries for freelancers, including the customer service representative budgeted for hire.

Thus, about 2% actually remains for profit. Of that, 35-39.6% goes to the IRS, 3% to state taxes, 1.45% to local taxes, and 6% to sales taxes, for a total of about 50% in taxation. That means that remaining actual profit is 1% of revenue.

To make things worse, when scrypt profitability falls back below 1 cent when the bubble ends, we should expect pool profit to be cut by at least 75%. The pool was making about 1/4 of what it does now before the bubble.

When you look at this analysis, you can see why Chris is trying to negotiate a monthly rate with Comcast for unlimited attack protection. Even if there were $60k in profit per month, half of that would be taken up by $1095/day attack protection.
Last edited Fri Jun 30, 2017 04:43 PM UTC by Steve Sokolowski; edited 1 time(s).
jaybizz
Archived posts: 16
Joined: Jun 18, 2017

Re: Status as of Friday, June 30, 2017

by jaybizz · · Post #6870

Unless you can get some kind of monthly rate for protection, I'd say Comcast is a no go. Yes, the downtime can be frustrating, but so long as javapipe is able to keep adapting relatively quickly, I think that is the overall better way to go. $1100 per attack is a lot of money to be throwing down the drain. At the end of the day, though, you guys need to make the best decision for your business. Unfortunately there really isn't enough data to figure out how often this will happen in the future, and how well Javapipe will respond each time. But, either way you're going to have people dissatisfied, and some will end up leaving at some point. It sucks, but that's the world we live in unfortunately.
Steve Sokolowski avatar
Steve Sokolowski
Archived posts: 4559
Joined: Aug 27, 2014

Re: Status as of Friday, June 30, 2017

by Steve Sokolowski · · Post #6873

Mrrt wrote:I would be less interested in additional DDoS mitigation solutions at this point as I would be in having more information about my network traffic.

DDoS attacks are commonly used as smokescreens to divert attention while real info-gathering/hacks are taking place, so I'd be more interested in seeing what other abnormal traffic may be headed to the servers to either identify or rule out more serious potential security threats.
While this sounds intriguing, if there were other traffic going to the servers, they were unsuccessful in exploiting them. There was so much attack traffic that Chris couldn't even log in, so I doubt attackers would have been able to do any damage considering that Chris couldn't even get characters from an SSH terminal to display.