Engraving successfully completed!  You can now read the winning entries here.

The winners have been drawn, and engraving has started!
In addition to the 10 randomly-selected winners, I have decided to personally pick 5 messages that I liked the most, so a total of 15 messages will be inserted in the blockchain.
All the messages will be prefixed with the string /LP^2/, so if you are on a Unix-like system you can see the messages engraved so far with:

Time's up! The winning messages will be drawn shortly. The engraving process will probably start tomorrow.

Messages will only be made public after they are engraved in a block.

I have heard some people are already working on it.

To all miners who haven't submitted a message yet: Hurry up! The deadline is tomorrow.

This is not a graphical application, it needs to be run from a console, so some experience with the command line is required. I am not a Mac user, so I'm probably not the best person to help you get started with this.

This is not currently supported by cpuminer. If you want a failover solution, you can find some wrapper scripts here.

Today the pool officially turns 2!

I wanted to find some original and witty way to celebrate, and after consulting with some of our long-time members, here's what we've come up with. I hope you'll like the idea!

Sorry for the misunderstanding. When I posted my report, it was referred to the latest git master (that's why I suggested users to revert to v3.6.6 instead of just pulling the latest commits). Since no related commit appeared after my post, I thought you were working on a fix and you still had to push it to the git repo. My bad, I should probably have been more explicit.

Did you commit the fix? I cannot find it in the commit history.
I have tried the latest master (tag v3.7.0) from the git repo, and the bug is still there.

I thought I'd confirm this, as more and more scrypt miners are getting confused.
Commits 3f6b9d67 and 36c6da8 introduce an inconsistency between share difficulty and network difficulty when cgminer is in scrypt mode. This causes many shares to be considered as blocks, even when they are not.
This doesn't seem to cause any real issue, but if you're getting annoyed by all those fake "Found block" messages, just use the stable version (tag v3.6.6).

igormkd: No, I didn't ask for the specifications of your CPU. I asked for the command-line options that you passed to minerd.

Hard to say without knowing what settings you are using.

Yes, sorry, I didn't forget about you. What I really meant is that I had never heard of this problem by any cpuminer user, so I wanted to know if Christian knew of a way to reproduce the issue with cpuminer.

I think it's the first time I hear about this problem. Do you know of a way to reproduce the issue? It would be nice if you could file a bug report via the issue tracker at GitHub.

EDIT: For future reference, here's the link to bug report. (It turned out to be an issue with the Windows port used for cudaMiner.)

I have done some further tests with Firefox 17, but I still cannot reproduce what you're reporting. I also had another pool user test this with his account, and he said everything is working as expected, both with Firefox 24 and with Chrome 30 on Windows 7.
I have even reviewed the login code, but couldn't find any way to bypass the 2-factor check.

Could you please try to log in using a wrong password and tell me if at least in that case you get asked for the one-time token?

I have just made some tests using my account, and I cannot seem to reproduce the issue. If I log out and try to log back in, I always get asked for the one-time code. Are you sure this isn't some strange browser cache issue? What browser are you using? Also, could you please try to log in using a wrong password and tell me what happens in that case?
Anybody else experiencing this?

Actually, it is. Are you sure you logged out and back in after enabling it?

Everything seems to be working fine here.
Remember that automatic payouts are not instant: once the payout threshold is reached, it may take up to a couple of hours before the actual payment is processed.

Just a quick message to let you know about the recent changes and additions.

• The charts page has been updated to use a newer client-side charting library, which is faster, allows you to zoom and pan, and has better browser compatibility.
• A few statistics have been added to the "My Account" page, such as per-worker 24-hour average hash rates.
• Users now have the choice to hide their username from public statistics.
• The FAQ has been expanded to address a number of common questions.

I'm also happy to announce that the new Stratum implementation has been doing wonders: we now have users with stale rates as low as 0.03%, even on servers handling over 1000 workers!
Even miners from China have stale rates as low as 0.15% on our West-Coast servers, which has pretty much convinced me that setting up additional servers in Asia would be pointless.
(Note: if your stale rates are significantly higher, it is almost certainly due to additional latency generated by your mining software. See the FAQ.)

The "Last 30 Days Summary" table is simply a day-by-day summary for the last 30 days.
The "Lifetime Rewards History" on the other hand, is not calendar-based. It subdivides your rewards by PPS rate (and difficulty), so a new row only appears when the PPS rate changes (so basically when the network difficulty changes). The timestamp displayed in each row is the last time at which you submitted a share for a given PPS rate (that's why the column header says "Last Time"). On average, the PPS rate should change every 3.5 days, and that's why not all dates appear in this table.