> 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/jp/kaihatsu/kihon/smart-contract-deploy.md).

# Smart Contract をデプロイする

Remix IDE または thirdweb を使用して Chiliz Chain 上に smart contract を deploy する方法。最低 gas fee 要件（2,501 gwei）と verification ガイドへのリンクを含みます。

smart contract の構築は、Chiliz Chain（あるいはどのブロックチェーンでも）向けの dApp につながるクリエイティブなプロジェクトに欠かせない要素です。

dApp の smart contract を構築したら、**必ず**通過しなければならないステップが2つあります。

1. Chiliz Chain 上に contract を deploy する。
2. その contract を verify する。

このセクションでは smart contract の deployment に焦点を当てます。

{% hint style="success" %}
deployment トランザクションが「pending」状態のまま長く留まらないようにするには、fee をカバーするのに十分な量を含めるべきです。

* 最低 gas fee: 2,501 gwei。
* 最低 priority fee: 1 gwei。
  {% endhint %}

Chiliz Chain 上に smart contract を deploy するには、次のいずれかのオプションをおすすめします。

{% content-ref url="/pages/teCwJVifqSuwhIGMAp5B" %}
[Remix でデプロイする](/jp/kaihatsu/kihon/smart-contract-deploy/remix-deploy.md)
{% endcontent-ref %}

{% content-ref url="/pages/i4UuJSkJIkMYDq7yze44" %}
[thirdweb でデプロイする](/jp/kaihatsu/kihon/smart-contract-deploy/thirdweb-deploy.md)
{% endcontent-ref %}

{% hint style="success" %}
smart contract を作成した後は、それを verify することが**必要**です。\
これを行えるのは**あなた**だけであり、contract が deploy されたらすぐに行うべきです。
{% endhint %}

{% content-ref url="/pages/hBRS9pN8P3M4cJr6vWVT" %}
[Smart Contract を verify する](/jp/kaihatsu/kihon/smart-contract-verify.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.chiliz.com/jp/kaihatsu/kihon/smart-contract-deploy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.