# Q2

#### April ‘25 - May ‘25:

1. GPUnet’s new product Quest was launched. We facilitated over 1M diverse users to participate and earn fair rewards. Major marketing correlations were done with projects like Monad, U2U, Huddle01, Zerion etc.
2. In parallel to the success of Quests, Subnets page was also revamped with a better UI and UX. New features like timeline updates, display videos, etc were added for subnet owners.
3. On the DApp, new compute providers were added, we increased the availability and uptime of the GPUs.
4. The tech-team was gearing up for the upcoming TGE and Nova Mainnet upgrade. The core of the chain was made more solid and decentralised.
5. GAN Chain moved to Mainnet, with a smooth upgrade without the need of restarting validator nodes. In the Nova upgrade, the block rewards were increased for the subnets and queens. Overall daily block rewards were increased to 2880 $GPU.

<br>

#### June ‘25 - mid July ‘25:

1. Season 1 of GPU Airdrop ended, with over 100K guaranteed $GPU airdropped to questers, and over 3M to node runners.
2. A Roadshow plan was launched for $GPU to be on all the top chains, we started with launching a token on Ethereum, touched $3 on all time high.
3. GAN Chain to Ethereum bridge was developed and deployed with a decentralized and verified protocol.
4. Next up $GPU was launched on Base. Base to GAN Chain bridge was developed and deployed under a secure protocol.
5. EVM to SS58 and vice versa, transfer of tokens was developed and deployed for the node runners to move funds to and fro.
6. For complete transparency, the history of rewards was now made accessible for the subnet users in their profile page.
7. The updates from the whole GPUnet multiverse were displayed in the subnets page in real time. Users could now know what is happening with the token, who is booking machines on dapp, who is creating a subnet, etc on their live feed.

<br>


---

# 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.gpu.net/dev-updates/q2.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.