> For the complete documentation index, see [llms.txt](https://whitepaper.cryptoknights.games/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.cryptoknights.games/technical/account-types.md).

# Account Types

### Tier 1: Guest Account

* Server generates virtual account when a new player installs the game.
* New player does not have to log in to play.
* Account linked to device.
* Player can earn Off-Chain Asset rewards only.
* Player can provide their email to upgrade to Tier 2.

### Tier 2: Email Account

* Use “Email + Password” to log in.
* Account can be shared between multiple devices.
* Player can earn Off-Chain Asset rewards only.
* More in-game purchasing options, but can’t mint as On-Chain Assets.
* Player can link account to crypto wallet to upgrade to Tier 3.

### Tier 3: Wallet Account

* Account links to both email and wallet address.
* Use “Email + Password” to log in, but sometimes need to sign digital signatures with their crypto wallet.
* Player can earn both Off-Chain Assets and On-Chain Assets.
* Player can mint assets as ERC tokens and withdraw to their wallet.
* All advanced NFT features will require this account tier.


---

# 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://whitepaper.cryptoknights.games/technical/account-types.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.