> 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/6.-web3-design-philosophy-and-ux-design/6.1-adopted-blockchain-and-web3-unaware-design-philosophy.md).

# 6.1 Adopted Blockchain and “Web3-unaware” Design Philosophy

<figure><img src="/files/lAC0uGi4Cj0UFjQUPdIn" alt=""><figcaption></figcaption></figure>

GET tokens are built on the Cardano blockchain. A choice made not simply for performance metrics, but based on the core principle:

"Web3 functionality should be invisible to the user."

&#x20;

**Why not make people aware of Web3?**

* Typical Web3 interactions like "wallet connections," "gas fee payments," and "private key management" are non-intuitive for the general public.
* Most users seek content engagement, not technical processes.
* By embedding Web3 features like transparency, decentralization, and ownership into the UX, GET enables to adopt with no frictions.

&#x20;

Cardano was selected because it best aligned with these requirements, as detailed in the next chapter.


---

# 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:

```
GET https://docs.global-entertainment-token.org/6.-web3-design-philosophy-and-ux-design/6.1-adopted-blockchain-and-web3-unaware-design-philosophy.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.