# Why now

> The intersection of the cryptocurrency boom, technological readiness, and evolving trader strategies marks a breakthrough moment for the trading world. DAY is at the forefront, ready to redefine the prop trading ecosystem.

<details>

<summary><strong>Growth in Cryptocurrency Interest</strong></summary>

The current surge in cryptocurrency popularity is attracting unprecedented engagement from crypto enthusiasts. This growing curiosity creates ideal conditions for innovative trading solutions like DAY, attracting a dynamic community ready to explore new financial frontiers.

</details>

<details>

<summary><strong>Technological Evolution</strong></summary>

Until recently, the vision of decentralized prop trading was limited by technological barriers. The emergence of perpetual DEXs, combined with their increasing liquidity, makes decentralized prop trading not only feasible but also ready for adoption. This leap in infrastructure is a game-changer, marking this moment as the starting point for DAY.

</details>

<details>

<summary><strong>Changing Trading Paradigms</strong></summary>

The landscape of leveraged trading is evolving. Traders now strive for financial freedom by strategically leveraging significant capital—achieving small percentages from large funds rather than risking more for the same profit. Funded accounts democratize access to substantial capital, enabling traders to adopt less risky strategies without compromising their financial goals.

</details>


---

# 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://docs.dayhub.io/meet-the-dayhub/why-now.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.