Followed by an istant drop back to original prices ...  

The spread is insane on YAC. After the last time I logged in I bought 10kYAC @ 0.05mBTC and could have sold them at 0.1mBTC even befor logging in again today. It hasn't been decided yet where it wants to go, but if it wants up it will be damm fast. 25kYAC market buy on cryptsy or bter and we'd quadruple for that moment.

"Followed by an istant drop back to original prices.. "

"problem" is that even at that price YAC is more profitabile then LTC, so miners just dump it.. this prevents price to really rise like somedays..

You have some fair points here, agreed.

Dunno, prolly because of that 2 and something hour period without blocks yesterday (or the day before? i don't remember). it looks ok now, though. haven't analyzed what exactly happened, yet. i plan to look at it sometime later.

I don't know what it was but it resolved itself pretty quickly and by itself from what I can tell. I do not believe it was a ford at all or we would be hearing it more from people affected. Any further ideas? I only noticed it when Cryptsy stopped the trades for a few hours.

I've asked all of the pool operators that I know of to upgrade to the latest stable version which has updated checkpoints.
Everyone else that has the ability to upgrade to the latest version should probably do so as well.

The poll has concluded with C being the chosen logo.

I have to say it again, thank you Mjbmonetarymetals for designing logos C & D. The two together almost have 70% of the votes.  

Big version of the winning logo:

As an attacker you mine on your own chain for a while (without broadcasting it to all the others), then suddenly add your blocks and so overrule the legit chain. All transactions on the legit chain while that period will be reversed so you can buy stuff without actually loosing coins.

Well, this might not have been intentional. Someone could have had a lot of PoS blocks found all at once or some PoS blocks were not broadcast to all nodes (and with PoS having a higher priority than PoW, they easily overtook the chain). Also, this was happening a lot in the early days of YAC (diff = 0 and stuff).

Nope,
was a PoS block that wiped out 34 PoW blocks. (You see it's a PoS by the hash's first bytes - 547db4922a8b8e71ff85 - no leading zeroes = very lwo difficulty = PoS block).

Surely there were some (if not all). I would advise exchanges to wait for at least 60 confirmations (or even 120 to be safe) before crediting funds to accounts as they are the most likely target of these attacks (if they even are attacks). Most likely this was just someone syncing their client while minting PoS blocks (haven't checked the code yet, but it's entirely possible that the PoS minter is enabled even before fully synced - or it might have had believed it was synced while it was 34 blocks behind [which is not a lot, since we have 60 second block target]).

IMHO the blockchain cummulative work calculation formula should be changed to something more sensible, eg. give PoS only a slightly higher priority than PoW. This would massively reduce such reorgs as seen in the posts above.