> For the complete documentation index, see [llms.txt](https://docs.visiongame.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.visiongame.io/visiongame-ecosystem/cryptoshowdown/supporting-popular-chains.md).

# Supporting popular Chains

CryptoShowdown is set to launch on Solana, chosen for its low fees and strong user base, ensuring a smooth and accessible experience for players right from the start. Beyond Solana, the game itself incorporates a unique multi-chain concept, with cards themed around different blockchains and their defining traits. For instance, Ethereum cards favor slower, high-impact effects, while Solana cards excel in speed and quantity over raw power, capturing each chain’s personality in gameplay.

Looking to the future, we plan to expand CryptoShowdown by minting new card sets on other popular chains. This approach not only brings variety and fresh strategies into the game but also opens up new communities within the blockchain world. By supporting multiple chains in both gameplay and card availability, CryptoShowdown provides a rich, multi-chain experience that keeps players engaged and entertained.


---

# 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.visiongame.io/visiongame-ecosystem/cryptoshowdown/supporting-popular-chains.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.
