Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 806. (Read 4382671 times)
April 25, 2013, 03:50:39 PM
MtGox blows!!!! Banker wannabe's. They are messing up the whole concept, letting traders make little .01 trades - hundreds/thousands per day.
April 25, 2013, 03:48:05 PM
Hmmm MTGOX down again?
big drop in BTC valueCoincidence?
joolz
Big advantage over things like e-gold is things are not stored centrally it can not be confiscated by governments with control issues. If BTC is to really take off we need to keep single sites from causing panic.
April 25, 2013, 03:46:45 PM
maxbtc.com is down too
April 25, 2013, 03:45:43 PM
Its going up too fast there will be corrections just look at the longterm value. It was priced similar to LTC about 3 years ago!
Hmmm MTGOX down again?
big drop in BTC valueCoincidence?
joolz
April 25, 2013, 03:45:20 PM
My unconfirmed rewards seem accurate except that the blocks are from two days ago and should be confirmed by now (as you are already aware.)
April 25, 2013, 03:33:40 PM
Its going up too fast there will be corrections just look at the longterm value. It was priced similar to LTC about 3 years ago!
April 25, 2013, 03:32:21 PM
big BTC drop over 16%, 150 down to 125
joolz
joolz
And you will see more of them... But it will go up again... I already see green candles...
April 25, 2013, 03:30:55 PM
I've built a GUI frontend miner that's (at the moment) specifically designed to work with Slush's Pool, if anyone's interested in trying it out: https://sourceforge.net/projects/slushminer (main forum topic)
Odd it runs ok on the laptop but when I tried it on the main miner I got 40MH/s versus 880MH/s!
April 25, 2013, 03:28:59 PM
big BTC drop over 16%, 150 down to 125
joolz
joolz
April 25, 2013, 03:05:04 PM
I've built a GUI frontend miner that's (at the moment) specifically designed to work with Slush's Pool, if anyone's interested in trying it out: https://sourceforge.net/projects/slushminer (main forum topic)
April 25, 2013, 02:47:50 PM
I'm getting the "Some your workers are using deprecated 'Getwork' protocol." warning. But I don't think any of my workers even work with the getwork protocol. Last week or whenever it was that stratum was down and getwork was up, none of my workers were connecting. I think this is a mistake.
April 25, 2013, 02:36:55 PM
Before the attack I had 3.8 awaiting confirmation with .2 (or thereabout) confirmed.
Looking at the statistics I should have another 6 BTC on top of that. (I am still trying to work out the right amount via Excel)
Looking at the statistics I should have another 6 BTC on top of that. (I am still trying to work out the right amount via Excel)
God I wish I had ASIC and your problems... Just look at the block rewords... As long as you see consistent number it should be fine... It will be about 30% higher during the last stages of outage... You can't just say I'm getting that much per day since there is some element of luck... We have really bad one right now...
April 25, 2013, 02:05:36 PM
Hi all,
after more than a day of hardcore hacking, I finally recovered the database and website to normal state. As you can see, website statistics know about all mined blocks during the website and database outage, including worker shares of loyal miners :-). Thanks to logging onto stratum nodes I've been able to recover complete shares. Some block rewards may be a bit off, because the pool was down after the attack and miners also often didn't reconnected instantly when I restarted stratum nodes, but generally I think the stats are correct.
Pool is currently calculating block rewards, but payouts are not processed. I want to give you some time for a feedback, if block rewards are calculated +/- as expected. I need some rest now, but I'll incorporate your comments then and process payouts of your mined coins.
Thank you for your support during this incident. I made significant changes to pool infrastructure from security perspective which I'll announce in detail later. Shortly said, pool doesn't hold any coins on live servers anymore. I also moved database to trusted place with limited physical access and without any consoles, Managers etc. Database is now running in undisclosed data center and on unknown IP.
after more than a day of hardcore hacking, I finally recovered the database and website to normal state. As you can see, website statistics know about all mined blocks during the website and database outage, including worker shares of loyal miners :-). Thanks to logging onto stratum nodes I've been able to recover complete shares. Some block rewards may be a bit off, because the pool was down after the attack and miners also often didn't reconnected instantly when I restarted stratum nodes, but generally I think the stats are correct.
Pool is currently calculating block rewards, but payouts are not processed. I want to give you some time for a feedback, if block rewards are calculated +/- as expected. I need some rest now, but I'll incorporate your comments then and process payouts of your mined coins.
Thank you for your support during this incident. I made significant changes to pool infrastructure from security perspective which I'll announce in detail later. Shortly said, pool doesn't hold any coins on live servers anymore. I also moved database to trusted place with limited physical access and without any consoles, Managers etc. Database is now running in undisclosed data center and on unknown IP.
I know the unknown IP!
It's 127.0.0.1
Go and ping it, you will see I'm right
Also, big thanks to Slush for the hard work.
April 25, 2013, 01:58:01 PM
Slush's post still applies. Regardless of what you were referring to, when he turns on the confirmation and payouts those stats will then be accurate.
Slush quote was "Pool is currently calculating block rewards, but payouts are not processed. I want to give you some time for a feedback, if block rewards are calculated +/- as expected. I need some rest now, but I'll incorporate your comments then and process payouts of your mined coins."
I am not seeing unconfirmed block rewards being calculated as expected.... hence my post.
And I'm telling you they are connected. When he runs the payout/confirming process you will see your unconfirmed rewards sync with the block stats.
[/quote]
He specificallty said "I want to give you some time for a feedback, if block rewards are calculated +/- as expected."
He wants to give US some time for feedback as to if the block rewards are calulated correctly. Us...... feedback.... block rewards..... calulated correctly...
I am giving feedback.
They are not.
[/quote]
OMG
So on the stats page, your calculated reward for each block is incorrect? If so then its only you, and it's probably good that clarify, slush needs to know.
Or on the My Account page are you referring to the unconfirmed reward stat being incorrect? If so, then chill out, because that will get corrected when he enables the payout/confirmation process.
Now I'm done trying to help, it's not worth bs.
April 25, 2013, 01:55:04 PM
If somebody has a lot of BTC unpaid by the pool and it has been delayed without reason, one might be very angry (and at the extreme track down and sue Slush for financial damages!?) if they lose a lot due to the holdup. Not his problem right? Fortunately, today the BTC value has not dropped much more than a percent at any small period so far. So lets hope for the best...
Its not that I'm ungrateful towards Slush for trying to sort this mess out - quite the opposite. I was just pointing out the problem that even small delays in payments might have catastrophic results for users.
I suggest the minimum payout value be capped to minimize pool liability in case coins do get lost. This would somewhat lower the risk huge damage claims. Of course this would only help for coins mined in the past and not for coins mined during the time payments are not processed.
Its not that I'm ungrateful towards Slush for trying to sort this mess out - quite the opposite. I was just pointing out the problem that even small delays in payments might have catastrophic results for users.
I suggest the minimum payout value be capped to minimize pool liability in case coins do get lost. This would somewhat lower the risk huge damage claims. Of course this would only help for coins mined in the past and not for coins mined during the time payments are not processed.
Yer a fkn idiot! Anyone who thinks that Slush is responsible for them mining on Slush's pool or ANYTHING that results from that needs a trout upside their stupid head!
What?! So now I'm an idiot because the pool doesn't come with a proper disclaimer in the terms of service for such cases and some bastard tries to profit from that "legally" by sueing him? I guess such a person would certainly find some laws etc which regulate the pool in EU (assuming Slush operates from the EU) and could have very good arguments against him. If they just want to cash in, it wouldn't even matter to them whether Slush is responsible or not. And they might have a very good chance of winning such legal battles.
And you're calling me a fkn idiot for pointing to these risks?
EDIT: If this is impossible, prove me wrong.
Dude, holy sh1t, you need chill the fk out mang, or yer gonna have an embolism or some...
Ok so you are not an idiot for suggesting Slush cover his butt - maybe a few more disclaimers wouldn't be a bad idea, but... it says right on the front page:
Quote
Key features
Service lifetime & operator trust - Users have to trust pool operators, because pools aren't cheat-proof from the side of the operator. mining.bitcoin.cz was the first Bitcoin mining pool, has been operating consistently since December 2010 and has a long history of stable and accurate payouts.
Anyways, you are still an idiot if you think Slush is gonna get sued for a few BTC - LMAO!! Now where did I put that trout? hmmm...
April 25, 2013, 01:54:41 PM
Slush now that you get us running again give us a donating address to help you recover some of the lost income...
April 25, 2013, 01:48:28 PM
I had the same problem, just clear your browser cache and viola.
Yes, looks like local dns caches (browser-side or ISP).
I would say that Uliss wanted to say something different, his uncorfirmed reward according to the account stats is0.62 but according to he stats from the pool should be much less. there are 6 blocks which are not confirmed and his reward should be somewhere around 0.12 + not 0.62. I have also on my account some issues. Before the pool attack I had nearly 1,2 total and now have only 1,3 which seeems to me much more less than expected.
Before the attack I had 3.8 awaiting confirmation with .2 (or thereabout) confirmed.
Looking at the statistics I should have another 6 BTC on top of that. (I am still trying to work out the right amount via Excel)
April 25, 2013, 01:37:57 PM
If somebody has a lot of BTC unpaid by the pool and it has been delayed without reason, one might be very angry (and at the extreme track down and sue Slush for financial damages!?) if they lose a lot due to the holdup. Not his problem right? Fortunately, today the BTC value has not dropped much more than a percent at any small period so far. So lets hope for the best...
Its not that I'm ungrateful towards Slush for trying to sort this mess out - quite the opposite. I was just pointing out the problem that even small delays in payments might have catastrophic results for users.
I suggest the minimum payout value be capped to minimize pool liability in case coins do get lost. This would somewhat lower the risk huge damage claims. Of course this would only help for coins mined in the past and not for coins mined during the time payments are not processed.
Its not that I'm ungrateful towards Slush for trying to sort this mess out - quite the opposite. I was just pointing out the problem that even small delays in payments might have catastrophic results for users.
I suggest the minimum payout value be capped to minimize pool liability in case coins do get lost. This would somewhat lower the risk huge damage claims. Of course this would only help for coins mined in the past and not for coins mined during the time payments are not processed.
Yer a fkn idiot! Anyone who thinks that Slush is responsible for them mining on Slush's pool or ANYTHING that results from that needs a trout upside their stupid head!
in the end * trout to the head of %name%* ya need to look at things to see how it can be HELPFUL to the pool for the comments here.
[edited to add ]
First of all, Slush: great job!!
Second of all; Slush: great job!
[EDITED OUT EXTRA STUFF]
As far as luck goes, if any pool deserves is its yours!
Thanks again!
Tyrion
To which I also say Third: Slush: Great Job! Second of all; Slush: great job!
[EDITED OUT EXTRA STUFF]
As far as luck goes, if any pool deserves is its yours!
Thanks again!
Tyrion
April 25, 2013, 01:11:54 PM
Slush's post still applies. Regardless of what you were referring to, when he turns on the confirmation and payouts those stats will then be accurate.
Slush quote was "Pool is currently calculating block rewards, but payouts are not processed. I want to give you some time for a feedback, if block rewards are calculated +/- as expected. I need some rest now, but I'll incorporate your comments then and process payouts of your mined coins."
I am not seeing unconfirmed block rewards being calculated as expected.... hence my post.
[/quote]
And I'm telling you they are connected. When he runs the payout/confirming process you will see your unconfirmed rewards sync with the block stats.
[/quote]
He specificallty said "I want to give you some time for a feedback, if block rewards are calculated +/- as expected."
He wants to give US some time for feedback as to if the block rewards are calulated correctly. Us...... feedback.... block rewards..... calulated correctly...
I am giving feedback.
They are not.
April 25, 2013, 01:07:33 PM
Any noobs reading the above, don't forget if it's set to a too low value, say below 0.01, you may end up with a badly fragmented wallet and have to pay larger fees when you spend your coin.
Interesting glad I gave up on all those free .000001 etc BTC sites!
Jump to: