# 7.3 “Web3-unaware design philosophy” for non-engineers

<figure><img src="/files/24qRLTQGF8ppnvsi5i9c" alt=""><figcaption></figcaption></figure>

To ensure accessibility for general users (fans, creators), GET was designed so that blockchain complexity is hidden behind familiar interfaces.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">UI/UX side (front)</td><td valign="top">System structure (back)</td></tr><tr><td valign="top">Participate and purchase with a single login</td><td valign="top">Authentication with Wallet Connect (Cardano)</td></tr><tr><td valign="top">QR Code payment with GET Pay</td><td valign="top">GET Token → point conversion logic</td></tr><tr><td valign="top">Participate in decision-making with voting button</td><td valign="top">Smart Contract execution with Plutus</td></tr><tr><td valign="top">Proof of ownership NFT will be automatically displayed</td><td valign="top">Link design with on-chain NFT + RWA</td></tr></tbody></table>

Thus, Web2-like simplicity is fully backed by Web3-grade security and decentralization.


---

# 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.global-entertainment-token.org/7.-technology-architecture-and-scalability/7.3-web3-unaware-design-philosophy-for-non-engineers.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.