# Market

<figure><img src="https://380441044-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKbhFiDiAFgSMaJHngLe1%2Fuploads%2FMZsJSargd49iJopDIa4g%2Fimage.png?alt=media&#x26;token=645a8eca-7d8a-4c2d-a659-5c73cfd85eec" alt=""><figcaption></figcaption></figure>

We are approaching the Web 3.0 age. In a recent survey, global research firm Straits projected that the Web 3.0 blockchain market will grow to $70 billion by 2030.  As a result, Web 3.0 businesses in various industries, including virtual asset wallets, blockchain point integration platforms, communities, and NFT developers, are actively growing their ecosystems by enhancing their connections with Web 2.0 services.

One of the most important aspects of Web 3.0 that Web 2.0 businesses already in operation should consider is business expansion. One important characteristic of decentralized services is that they allow individualized platforms. For distribution companies, decentralization can also improve the relationship between customers and actual items through blockchain technology. The market is growing, and there are more and more business cases for collaboration amongst companies in the sector, ranging from crypto wallets to loyalty programs to NFTs. Nike declared it will include NFTs generated by their virtual clothing NFT platform 'DotSwoosh' (.Swoosh) into Electronic Arts (EA) sports games. DotSwoosh is a web 3.0 platform that Nike introduced for exchanging digital collectibles.


---

# 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://hiros-organization-1.gitbook.io/hiro-whitepaper/market.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.