> For the complete documentation index, see [llms.txt](https://docs.spellsofgenesis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spellsofgenesis.com/spells-of-genesis/cards/blockchain-cards.md). # Blockchain Cards Spells of Genesis possess more than 250 blockchain NFT cards and the collection keeps growing! It’s compatible with three blockchains: Bitcoin (via Counterparty), Ethereum and Klaytn, this last chain is used for the back-end of our system but it is not inegrated in our wallet Casa Tookan. Furthermore, there are cards that are unique to Counterparty, the blockchain that Spells of Genesis has been using since 2015. Additionally, some cards have been issued on both Ethereum and Counterparty, which are the two blockchain platforms currently supported by the game. To unlock the power of your blockchain cards in-game, start by linking your Casa Tookan blockchain wallet to your game account. Unleashing the magic of your cards had never been as easy… --- # 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.spellsofgenesis.com/spells-of-genesis/cards/blockchain-cards.md?ask=&goal= ``` `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.