18218 was fixed just right now, kudos to Slush for that.
I assume he will look at 18223 as well. I will start worrying later when the there will be less than 50 confirmations left for the block...

   T

Block 18176 is off for many of us. Have been waiting for the rewards to get recalculated, then sent a message to Slush at the time when there were only 12 confirmations left.
The block just got confirmed, no adjustments. Obviously, it would be chaotic and unmanagable if everyone cries about blocks, and there should be a proper way to escalate these issues and get them addressed on time. In many cases Slush is able to intervene, but on few occasions the issue does not get fixed.

What would be the preferred way of bringing attention to these issues - especially given that the spam-rate on this thread is rather high so Slush might not be able to notice/catch posts.

Cheers,
   T

PS: dear trolls, I am not complaining about the quality of service Slush provides, but seek a way how he could be notified of pool related issues is a smart way - without highly redundant communication -  in the future. This topic would have been the proper communication channel but given the white noise...

There is definitely a difference between reset and renormalization. While reset means zeroing out the scores, renormalization means scaling down the scored and modifying C accordingly. The first is simpler to implement and faster to execute while the second is mathematically more correct. Another options to protect against an arithmetic overflow would be using a logarithmic scale, but that is not how the exp scoring method is implemented.

BTW, I really liked reading http://organofcorti.blogspot.hu/2012/04/41-slushs-pool.html and http://organofcorti.blogspot.hu/2012/09/43-slushs-score-method-and-miner.html and suggest those articles to anyone with doubts and questions about how exp scoring works.

Cheers,
   T

Based on statistics I collected, there is a daily, periodic fluctuation - my conclusion is that more than 20% of the miners only mine part of the day. Probably some are running it in the background during working hours (not dedicated mining rigs, but generic workstation with GPU), but the opposite (mining at night) might also make sense based on how they are charged for electricity, especially for dedicated beefy GPU rigs which eat a lot of power. In both cases, this will lead to a repeating pattern in total hashrate fluctuation.

   T

You should really take some time and read a few more posts before commenting and writing things like "it could also have been an orphan, or an 8 hour long block". This could decrease the ever increasing rate of spam and FUD here.

Cheers,
   T

Did you at least try to read the last few posts before asking?

Cheers,
   T

http://www.catb.org/~esr/faqs/smart-questions.html

Many of us face the same situation with this block. This has happen quite a few times, most of the cases when the score reset is immediately before / very close to the end of the round. Slush has taken care of this, so on one side I agree - give it time, however, a timely notice will allow our pool master to take action in time, meaning before the block gets confirmed. He told that it is much harder to issue adjustments once the block is confirmed.

Cheers,
   T

Echoing the response: What is wrong with https://mining.bitcoin.cz/stats/graphs/ "Your daily reward"? Why not use that? Is there any particular reason why you are interested in the last 24 hours as opposed to last day?

I suggest you to check how DGM and other rewarding methods work. There are more sophisticated solutions than what you are suggesting. Just read up on the topic. A lot of useful links have been posted here recently, for example this one: https://bitcointalk.org/index.php?topic=39497.0

Cheers,
   T

Very good read indeed. I wonder how many of the forum members will take the time to read & understand (!) it. I see a rather wide spectrum of skills and attitude and many reoccurring questions that makes me assume the majority will just skip anything longer than a few paragraphs. Anyway, congratulations, I really recognize the full worth of these quality articles.

Cheers,
   T

If you take a closer look, you will see slush is fixing the earlier unconfirmed rewards for confirmed blocks.
You will see some fluctuation but keep waiting until he is done. I also see numbers going up and down, but I believe I see the way it is converging...

joolz, I am unsure if you are kidding or not...

As I interpret my observations, all rewards will stay unconfirmed even if the block itself is already confirmed. This is not the usual behavior, but is only to allow slush more time/flexibility in the current situation. He plans to get it sorted out in the afternoon his local time (UTC+2).

Hope this helps,
   T

I appreciate his efforts and this is why I decided to stay with him (his pool) even under suboptimal circumstances. I can mine without interruption, and I assume rewarding will be taken care of once things are back to normal. He will open up the front-end when he feels it is ok to do so. This is my personal opinion, based on what I have seen so far.

It is only him who can provide authoritative information - but I believe he has more urgent activities than focusing on communication. And I am ok with that.

Also note that your wallet comes with about 100 addresses preloaded, just not visible (https://en.bitcoin.it/wiki/Securing_your_wallet). This means, there are more keys in your wallet than you can see.
Key creation might not happen when you would think it happens. Take this into consideration as well...

Hope this helps.
   T

I believe Slush will just set up another one and distribute it as he sees fit. I am a bit curious but can live with it, np  

Cheers,
   T

PS: As far as I can see, all references have been masked/edited out by now.

And in all honesty, I did not even assume it was anything sensitive - as it was openly mentioned on the forum.

As you prefer, I edited it out, however note that is was publicly disclosed on this forum (by someone who got it via mail, not me), and whatever makes it to the internet, will stay there. Getting this info was really not rocket science, just paying attention & following the forum.

Reminds me a bit of Orwell's famous phrase "All animals are equal, but some animals are more equal than others".
And another famous one from here: http://www.catb.org/esr/writings/unix-koans/mcse.html
“A man who mistakes secrets for knowledge is like a man who, seeking light, hugs a candle so closely that he smothers it and burns his hand.”

While there might be legit reasons for some unpublished alternative service endpoints, providing unequal chances to connect to the pool under DDoS was surely not the original intention of Slush. Uberduber, are you aware of any details you are willing to share?

There is an address different than stratum*.bitcoin.cz indeed - but this one still points to an OVH IP.
Some received an email notification mentioning v??.bitcoin.cz - might be ASIC or just based on some informal criteria.

$ host v??.bitcoin.cz
v??.bitcoin.cz has address 94.23.174.94
$ host 94.23.174.94
94.174.23.94.in-addr.arpa domain name pointer 94-23-174-94.ovh.net.

As a side note, I did not receive any email with this info, just follow the forum, and puzzled out based on some chatty posts. This means obviously I am just drawing conclusions based on info that might be right or wrong.
I assume that pointing the miners to EC2 is the preferred approach, even for VIPs.

Cheers,
   T

You can check the logs of your miners for status/avg hashrate, the json api for rewards & server side stats are also part of the website which is down at the moment, so AFAIK you will have to wait a bit for that.

Cheers,
   T