# Cartridge creation

The creation of ERC20 Cartridges is accomplished using the GameContract.io platform. The name GameContract refers to the "Smart Contract", which is the license carrier for a computer game. Creating ERC20 Cartridges can be outlined with a few simple steps.

1. Selecting the [type of cartridge](/get-started/erc20-cartridge/types-of-cartridges.md). 
2. Filling in the basic cartridge data, the secondary market trading rules, and protection time before aftermarket. Protective period means no exchange for a certain time after release to prevent the emergence of a secondary market. 
3. Populating the metadata and visual aspects of the profile on GameXplorer.io. 
4. Creating the ERC20 Cartridge with the help of Metamask. 
5. Connecting the ERC20 Cartridge with the game files. 
6. Setting the price and number of cartridges for sale. 
7. Verification of the game's copyright is performed by the HashUp team. 
8. Official sale on GameXplorer.io and GameCap.io platforms. 
9. After the protection period before the secondary market, it is possible to transfer games between players and provide liquidity on DEX. From then on, the price of the software is set by the free market using AMM (Automated Market Maker).

{% hint style="info" %}
Games are being sold on the platform with any token that is approved by the creator. This indicates that the creator can earn in USDC, WBTC, ETH, MATIC. The solution is scalable and facilitates easy switching from FIAT = > CRYPTO .
{% endhint %}


---

# Agent Instructions: 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://wiki.hashup.it/get-started/erc20-cartridge/cartridge-creation.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.