Verification queue is not transactions
Come on el reg its right there in the title of the post you linked. Its the queue for a fully verified account (more deposit options etc) and nothing to do with the trading engine
Bitcoin exchange Mt.Gox has been attacked and its servers briefly taken offline. The service confirmed the attack at 2:00 AM Japan time on April 22nd, posting a tweet to warn users of the outage. UPDATE: This again appears to be another strong DDos attack. We are working hard to overcome it and will update... fb.me/14J8rINhm …
Of course it is news. Yet another orchestrated attempt by the Establishment to nip in the bud this major threat to their own money printing. They will try and extinguish bitcoin whatever it takes, similarly gold which they naked shortsold to an unprecedented scale last week, to stem it's popularity. The "currency wars" are alive and kicking.
The layer references are to the OSI Model. A layer 7 attack means the DDoS is interacting with their web application, rather than further down the protocol stack. For example, a typical DoS SYN flood is at layer 4 (transport) and is less sophisticated / potentially easier to filter.
Relevant URL:
http://en.wikipedia.org/wiki/OSI_model#Description_of_OSI_layers
BC is no more a threat to the conventional currency game than any other casino using their own chips at the tables. If you want a greater diversion of economic activity away from conventional currency have a look at the network money WirBank in Switzerland accounts. Doesn't create any problem for the authorities though either, SMEs in Switzerland which trade in CHW still have to pay taxes in conventional CHF.
@Mayday: Not the lot I worked at. Security was always an afterthought and a massive inconvenience. It took two attacks by the Russian's before they decided otherwise, then, in the spirit of corporate lunacy that prevails, threw money and resources are what they perceived to be the problem, without actually asking us (the one's who'd identified the attack) what was needed.
Year 1. Spend $10,000 on infrastructure
Year 2: Spend $5,000. Get hacked
Year 3: Spend $5,000 (it was, of course, a fluke)
Year 4: Spend $1,000 on some auditing software (and only because I'd been bitching and moaning about needing it for several years). Get hacked again (discovered through aforesaid Auditing software)
Year 5: Spend $500,000 and replace every last single solitary server we owned in a year long project. Yeah - knee-jerk time.
Jerks...