Author

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

legendary
Activity: 1386
Merit: 1097
All backends seems fine, I'm not aware of any problem. Also most block rewards are fine, so there's no indicator anything is wrong with the pool. I wouldn't be surprised it is yet another routing problem on the internet, as I saw many times in few last weeks :-/.

Although I have an office near the explosion place, I'm fine!
full member
Activity: 427
Merit: 100
Slush,

Are you OK?  Just heard about major explosion in Prague, CZ....
KNK
hero member
Activity: 692
Merit: 502
Same here - half for 17749 and my hashrate also dropped in half

It seems one of the backends is still causing problems as another worker in the same network is OK i.e. not a connection problem
newbie
Activity: 18
Merit: 0
What happened to block 17749?

My reward is 0.00000000 even though I had 2070 shares of the total 20072069...
KNK
hero member
Activity: 692
Merit: 502
I get the rare/occasional NMC reward does that mean I failed over to getwork for that block?
As stated before in this thread, NMC is only worked on from the getwork miners, but the reward is divided among those who have provided NMC address
hero member
Activity: 826
Merit: 1000
Was NMC complitly removed? I don't see them any more at statistics...

EDIT: Why didn't I see all new comments on the forum? OK so we still mine NMC...
member
Activity: 98
Merit: 10
I get the rare/occasional NMC reward does that mean I failed over to getwork for that block?
legendary
Activity: 1386
Merit: 1097
During rounds 17736 and 17737 there were issues with counting shares on one of nine backends. Before I noticed it and corrected it, pool found these blocks. So this time I don't have any data to recalculate and fix these two rounds, I'm sorry Sad. I already added new metrics to monitoring system to prevent this to happen next time.

Ad Namecoin - pool is still mining namecoins, but only with 2-3% hashrate (200 GHash/s), and it was recently quite unlucky, so no block in two days.

newbie
Activity: 31
Merit: 0
Both of those blocks have now been fully confirmed and the Shares/Reward has still remained unchanged.
hero member
Activity: 574
Merit: 500
I do have issues in last 3 blocks. What happened? Miners are up and running and this is what I got.





17737 appeared strange to me too,  17736 I got 5 shares in and a decent reward for a couple minute round.
but I agree 17737 looked strange to me too.  I got zip for that too.  Granddaughter was over at the time and may have messed up one of my miners,
but I thought I'd get something for that block.


17736 was such a short round, the shares for this this one are OK.

17737 and 17719 are incorrect and need recalculating I think - how does it happen that a block can be mis-calculated and do we have to keep monitoring for this?
legendary
Activity: 1358
Merit: 1001
https://gliph.me/hUF
Great work as usual slush. One question, what happened to NMC?

They're not compatible with stratum protocol, so have pretty much been dropped, as hardly anyone still uses getwork.

K.
Then how do Bitminter and Bitparking do it? Both mine NMC (and some others in Bitparkings' case) on stratum.
member
Activity: 109
Merit: 10
Great work as usual slush. One question, what happened to NMC?

They're not compatible with stratum protocol, so have pretty much been dropped, as hardly anyone still uses getwork.

K.

k, thanks.



If NMC gets officially dropped by slush for whatever reason, can you lower the NMC transaction minimums then so we can cash out?
legendary
Activity: 922
Merit: 1003
Great work as usual slush. One question, what happened to NMC?
They're not compatible with stratum protocol, so have pretty much been dropped, as hardly anyone still uses getwork.
That's one thing I never quite understood: the rapid migration to stratum. I understand that with increasing hashrates and the desire to reduce network traffic, clearly the 'diff 1' getwork protocol was unsuitable. But using the more mature getwork (LP) with vardiff has, in my experience to date, been more stable (in terms of cgminer/bfgminer crashes) than using stratum. Just today I've had 2 mining software crashes running stratum, while 2 other instances on getwork/vardiff are still running without issue. I like the reduced stales on stratum, but if I have to continually monitor and restart my mining software when it crashes I'm losing more shares than any benefit the reduced stales can have.

Regarding NMC on slush: only the getwork clients are merge-mining NMC (current that's only a few % of the total pool); stratum clients (the vast majority) are not. But NMC rewards are distributed to everyone with an NMC wallet defined. This is why the NMC payout are so small.
sr. member
Activity: 282
Merit: 250
can someone help me how to set up NMC mining in slush pool?
i followed this http://dot-bit.org/InstallAndConfigureNamecoin until the end, and its still currently building the blockchain, but so far i havent found any micro NMC yet =(
note: im running 2x7950.

do i have to wait untill all the NMC blockchain has been downloaded? what do i do wrong?

thankyou.
sr. member
Activity: 644
Merit: 250
Great work as usual slush. One question, what happened to NMC?

They're not compatible with stratum protocol, so have pretty much been dropped, as hardly anyone still uses getwork.

K.
member
Activity: 109
Merit: 10
Great work as usual slush. One question, what happened to NMC?
sr. member
Activity: 299
Merit: 252


Correct, please!
I want to see yesterday, on the graph.
Previously, and it was.
member
Activity: 112
Merit: 100
Can anyone confirm how the passwords of the database were protected? I'm assuming hash'd + salted right?

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.

It's an old quote, but still correct I believe.

K.

No problem, thanks.

Horrible hash but at least they were hashed in the first place.

I tried looking back a few pages but I didn't know when it had occurred so I couldn't see. Thanks!
sr. member
Activity: 644
Merit: 250
Can anyone confirm how the passwords of the database were protected? I'm assuming hash'd + salted right?

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.

It's an old quote, but still correct I believe.

K.
member
Activity: 112
Merit: 100
Can anyone confirm how the passwords of the database were protected? I'm assuming hash'd + salted right?
Jump to: