> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/quick-start/developer-toolbox/deploy-and-verify-a-contract.md).

# Deploy and verify a contract

{% hint style="info" %}
**Prerequisites**

1. This documentation assumes you have already installed MetaMask on your system. If not, please [install MetaMask](/learn/about-wallets/how-to-use-metamask/install-metamask.md) first, either the web-based extension or the mobile app.
2. For your convenience, pin 📍 the MetaMask extension to your preferred browser.
   {% endhint %}

Building a smart contract is an essential part of the creative project that leads to a dApp for Chiliz Chain — or any blockchain, really.

There are two steps that you **must** go through once you have built your dApp's smart contract:

1. Deploying the contract on Chiliz Chain.
2. Verifying that contract.

These two steps are documented here.

{% hint style="success" %}
To ensure that your transaction doesn't remain in "pending" status for too long, you should include enough to cover the fees:

* Minimum gas fee: 2,501 gwei.
* Minimum priority fee: 1 gwei.
  {% endhint %}

## Step 1: Deploy your smart contract

You can use either of these options:

{% content-ref url="/pages/cwZqLlr1ee8FwupJJUCc" %}
[Deploy with Remix](/develop/basics/deploy-a-smart-contract/deploy-with-remix.md)
{% endcontent-ref %}

{% content-ref url="/pages/RFojVMHPNEiBunOWwzIL" %}
[Deploy with thirdweb](/develop/basics/deploy-a-smart-contract/deploy-with-thirdweb.md)
{% endcontent-ref %}

## Step 2: Verify your smart contract

{% hint style="success" %}
After creating a smart contract, it is **necessary** to verify it.\
Only **you** can do it, and you should do it as soon as possible.
{% endhint %}

Here are guides for each:

{% content-ref url="/pages/QmhlZEvcZGdhu1QvIR0p" %}
[Verify with Chiliscan](/develop/basics/verify-a-smart-contract/verify-with-chiliscan.md)
{% endcontent-ref %}

{% content-ref url="/pages/uYTtcHioYwh7WkNtwSzW" %}
[Verify with Chiliz Block Explorer](/develop/basics/verify-a-smart-contract/verify-with-chiliz-block-explorer.md)
{% endcontent-ref %}

Once your contract is verified, it will receive a "green dot" on the block explorer interface, indicating that your contract can be trusted.

<figure><img src="/files/lngpQYk6z7xBV5obbjP9" alt=""><figcaption><p>Chiliscan example</p></figcaption></figure>

<figure><img src="/files/18PmrFDXwX6vtWqdJIjs" alt=""><figcaption><p>Chiliz Block Explorer example</p></figcaption></figure>

See for instance the PSG Fan Token contract:

{% embed url="<https://chiliscan.com/token/0xc2661815C69c2B3924D3dd0c2C1358A1E38A3105/contract/code>" %}
PSG Fan Token on Chiliscan
{% endembed %}

{% embed url="<https://scan.chiliz.com/address/0xc2661815C69c2B3924D3dd0c2C1358A1E38A3105/contracts#address-tabs>" %}
PSG Fan Token on Chiliz Block Explorer
{% endembed %}


---

# 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.chiliz.com/quick-start/developer-toolbox/deploy-and-verify-a-contract.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.