> For the complete documentation index, see [llms.txt](https://docs.global-entertainment-token.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.global-entertainment-token.org/2.-problem-recognition-and-market-background/2.3-the-new-possibilities-of-web3.md).

# 2.3 The New Possibilities of Web3

<figure><img src="/files/4P8Vh1Ms75E3Uds8PVMK" alt=""><figcaption></figcaption></figure>

**Web3 technology has the potential to fundamentally reshape entertainment:**

* Direct support and participation\
  Fans can fund and support projects through tokens and NFTs.
* Tokenization of “ownership” of content and experiences\
  Content access and experience rights can be minted as tradable NFTs.
* DAO-Driven decision-making\
  Community can guide project directions through governance votes.
* Contribution-Based Reward Models\
  Participation and activity are incentivized via co-creation economies.

GET is purposefully designed around these Web3 innovations, offering a high degree of alignment with the evolving entertainment landscape.

The characteristics of Web3, such as democratization of decision-making and immediacy of value distribution, have an extremely high affinity with the use cases provided by GET.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.global-entertainment-token.org/2.-problem-recognition-and-market-background/2.3-the-new-possibilities-of-web3.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.