> For the complete documentation index, see [llms.txt](https://micefia.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://micefia.gitbook.io/whitepaper/introduction/why-cardano.md).

# Why Cardano

Our team members have produced, served and invested in various blockchains at various times. When our team got together, they did community trials and launchpad applications on various blockchain networks.

When our project started to bear its first fruits, it was not determined which blockchain we would be on. While our partnership talks continue on the Solana and Ethereum network, we examined the communities of the projects. We wanted the content produced by MICEFIA to be valued as much as possible. We couldn't believe our eyes when we saw the activity in the Cardano NFT communities. After that, we contacted the JPGstore team and told them about our ideas. We ended our partnership talks with other networks when they said they would support us.

We, as MICEFIA, know very well that Cardano is at the beginning of the road. We believe that publishing our technological infrastructure and digital creations here will make us stronger in the future. As we continue to produce good contents, we aim to bring users from other networks to the Cardano ecosystem.\
\
As we always said "We build and grow together".


---

# 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://micefia.gitbook.io/whitepaper/introduction/why-cardano.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.