Author

Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 905. (Read 4382653 times)

member
Activity: 106
Merit: 10
Thanks for being honest slush.  Password changed, I'll send a sizeable donation to you tomorrow.
legendary
Activity: 1386
Merit: 1097
Summary of what happen today:

Somebody hacked my backup machine with pool data hosted on Linode and steal 3094 BTC ("hot" coins ready for payouts). Cold backup was not affected in any way by this hack.

It looks that also user database has been compromised. Although passwords are stored in SHA1 with salt, I strongly recommend to change your password on the pool immediately.

Robery of Bitcoins has no impact to pool users, I'm covering the loss from my own income (although it means that many months of my work is wasted  Roll Eyes ).

Continue of story: https://bitcointalksearch.org/topic/hacked-linode-coins-stolen-to-1nry8gbx56mymbhdym-66916

Please discuss the issue in thread above, thank you!
legendary
Activity: 1386
Merit: 1097
Payouts are working again, I'm writing longer story what happen this time...
legendary
Activity: 1386
Merit: 1097
I stopped payouts few hours ago, resolving one issue. Processing & payouts will be enabled again in one or two hours, sorry for delay.
full member
Activity: 123
Merit: 100
Looking at the "my account" section seems to show me that the last 4 blocks that have finished confirming have not added themselves into the "confirmed reward" for BTC. I don't know about the NMC totals since I wasn't paying attention there, but I expected a payout overnight when btc exceeded my threshhold total, and that didn't happen. I check on the site this morning and the "confirmed reward" number hadn't risen from last nights number despite 4 blocks I have rewards listed for having finished confirming. Don't know if some prior to those 4 have the same issue since I have a set of 7 blocks before those 4 that list 'none' for me (don't mine overnight).

Something up with the confirmation process or the portion that adds the awards to our totals?

Thralen
legendary
Activity: 1386
Merit: 1097
So Slush's Pool has been performing at 93% for the month or more. Is this just really bad luck or am I missing something?

You're not missing anything, two or three weeks ago there was really bad luck on the pool, so 30day average lowered...
donator
Activity: 2058
Merit: 1007
Poor impulse control.
So Slush's Pool has been performing at 93% for the month or more. Is this just really bad luck or am I missing something?

Depends on how 'Pool luck' is defined. Anyone have a quick link for lazy person?
hero member
Activity: 742
Merit: 500
About Tor mining - it works even behind strict firewalls, open port 443 is enough.
So if I were to use diablominer would I still need to put port 8332, or could I use 443?
Port 8332 is blocked (and nearly everything else).
Do I need to have the bitcoin client installed on every computer that I mine on?  I remember once having to create a bitcoin.conf file.  It wouldn't even be able to update because of the blocked 8332.
BTW I never solo mine, so that is not an issue.
He means 443 outbound. It's a pretty rare thing to block. You still connect to port 8332
donator
Activity: 1736
Merit: 1014
Let's talk governance, lipstick, and pigs.
So Slush's Pool has been performing at 93% for the month or more. Is this just really bad luck or am I missing something?
full member
Activity: 149
Merit: 100
About Tor mining - it works even behind strict firewalls, open port 443 is enough.
So if I were to use diablominer would I still need to put port 8332, or could I use 443?
Port 8332 is blocked (and nearly everything else).
Do I need to have the bitcoin client installed on every computer that I mine on?  I remember once having to create a bitcoin.conf file.  It wouldn't even be able to update because of the blocked 8332.
BTW I never solo mine, so that is not an issue.
full member
Activity: 123
Merit: 100
Yes, it's really invalid. You can everytime check it by clicking blocknumber and see details on blockexplorer. here you can see that block is orphaned.

Sorry, I knew that. I just wasn't thinking at the time.

Thralen
legendary
Activity: 1274
Merit: 1004
All fixed now  Grin I dunno if slush fixed the invalid blocks manually or whether he's got some script that does additional checks (besides the use of block explorer), but either way it's all good.

Also I must say I am quite happy to see our luck level so high recently. This nicely makes up for that period of bad luck we've had a week or two ago.


Heh, of course the day that we get 4 blocks in the span of 65 minutes overnight is also the night that my computer decided to shut itself off. Why does that never happen during a 10 hour block?
legendary
Activity: 1386
Merit: 1097
So block 168920 is actually a real invalid? Just wondering...

Yes, it's really invalid. You can everytime check it by clicking blocknumber and see details on blockexplorer. here you can see that block is orphaned.
full member
Activity: 123
Merit: 100
So block 168920 is actually a real invalid? Just wondering...

Thralen
legendary
Activity: 1386
Merit: 1097
I was on holiday for few days and I was just checking pool few times per day for manual block validations - so sorry for some false invalids. Block explorer looks fine now and also blockchain.info added information if some block is part of main blockchain, so I'll eventually add blockchain.info as fallback alternative to blockexplorer.com.

About Tor mining - it works even behind strict firewalls, open port 443 is enough.
legendary
Activity: 3080
Merit: 1080
Also I must say I am quite happy to see our luck level so high recently. This nicely makes up for that period of bad luck we've had a week or two ago.

Don't speak too soon!

lol I hope I did not jinx it!

newbie
Activity: 10
Merit: 0
Also I must say I am quite happy to see our luck level so high recently. This nicely makes up for that period of bad luck we've had a week or two ago.

Don't speak too soon!
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
oh nice, why does it need to call sha256 function twice though?
That is what mining is doing. It performs sha256(sha256()) on the block data and a nonce. The nonce is incremented until the result matches or exceeds the difficulty level.
newbie
Activity: 46
Merit: 0
I Found my first block too on slush during a 5 hour marathon, or right after. How do I check in block explorer my hash that found the block? Or how do I recognize it's from me?

If you don't log submitted shares, there's no way to check in blockexplorer which block you mined. If you're loggin submitted shares, then sha256(sha256(submitted_data)) == block hash on blockexplorer.

oh nice, why does it need to call sha256 function twice though?

Would I have to be logging in verbose mode?
legendary
Activity: 3080
Merit: 1080
All fixed now  Grin I dunno if slush fixed the invalid blocks manually or whether he's got some script that does additional checks (besides the use of block explorer), but either way it's all good.

Also I must say I am quite happy to see our luck level so high recently. This nicely makes up for that period of bad luck we've had a week or two ago.

Jump to: