> 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/7.-technology-architecture-and-scalability/7.2-why-cardano.md).

# 7.2 Why Cardano?

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

After evaluating multiple public blockchains (Ethereum, Polygon, Solana, etc.), Cardano was chosen based on the following perspectives.

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Evaluation axis</td><td valign="top">Cardano</td><td valign="top">Ethereum</td><td valign="top">Polygon</td></tr><tr><td valign="top">Transaction Fee</td><td valign="top"><p>◎  Stable/</p><p>Low Cost</p></td><td valign="top"><p>× Volatile/</p><p>Tend to rise</p></td><td valign="top">◯ Relatively Stable</td></tr><tr><td valign="top">Scalability</td><td valign="top"><p>◎  High Through</p><p>Put with POS</p></td><td valign="top">△   Currently Limited</td><td valign="top">◯ Moderate Response</td></tr><tr><td valign="top">Native Token Support</td><td valign="top">◎  No Smart Contract Required</td><td valign="top"><p>× ERC-20</p><p>Required</p></td><td valign="top"><p>× ERC-based</p><p>dependency</p></td></tr><tr><td valign="top">Security and formal validation</td><td valign="top"><p>◎  Adopting</p><p>Formal Methods</p><p>(Plutus)</p></td><td valign="top"><p>△   Solidity-</p><p>Based</p></td><td valign="top">△   Same as above</td></tr><tr><td valign="top">RWA/NFT suitability</td><td valign="top"><p>◎  Lightweight &#x26;</p><p>transparent</p><p>issuance/</p><p>trading</p></td><td valign="top"><p>◯ Many Projects</p><p>implemented</p><p> </p></td><td valign="top">◯ Fast but with risk of congestion</td></tr></tbody></table>

&#x20;Cardano's security, cost-efficiency, and RWA support made it the best fit for GET’s philosophy.


---

# 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/7.-technology-architecture-and-scalability/7.2-why-cardano.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.