# 19 MAY CRYPTO FLASH CRASH

The cryptocurrency universe experienced a real crack on Wednesday 19 June.

Some tokens lost more than 50% in extreme value on the day.

Bitcoin, although more liquid, saw its value drop from 60,000 to 30,000 USD in a few days.

Although these declines are part of the landscape, this movement will remain exceptional in its violence.

There was no macroeconomic news to fuel this movement. It is only due to a series of cascading liquidations of portfolios that were surely built with significant leverage. The Diabolo team did its best to limit the losses, and as a risk manager I can say that the traders were reactive and prudent.

Such moves put our risk management to the test but also allow us to test the limits. We will continue to work in this direction with more and more tools to better calibrate positions and continue a rigorous selection of traders.

Some of you may have had a very stressful day. Diabolo is positioned for the long term and aims to offer attractive performances over the long term. Although the month of May will be for many in the red, the annual performance remains at very good levels. Our traders will take advantage of this event to build new positions and, in compliance with our risk rules, to increase their profits.

Diabolo thanks you for your confidence and hopes to continue to be your preferred partner for asset management in the crypto-currency market.

Arnaud Gaboury

Risk Manager Diabolo.io


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://diabolo-wiki.gitbook.io/diabolo/news-et-communautes/crypto-flash-crash-du-19-mai.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.