> For the complete documentation index, see [llms.txt](https://docs.hypersign.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hypersign.id/hypersign-kyc/on-chain-kyc/contracts-deployment.md).

# Contracts Deployment

Please read [introduction](/hypersign-kyc/on-chain-kyc.md#introduction) before proceeding with the contract deployments on this page. &#x20;

Head over to Entity Studio dashboard, choose your KYC service and click on **OnChain KYC**  under setting tab in left nav bar.&#x20;

<figure><img src="/files/KGVw7rbmb46GO1NhgSPn" alt=""><figcaption></figcaption></figure>

Click on **Deploy OnChain KYC** button to start the process of contract deployments.&#x20;

### Deploy Hypersign KYC Issuer Contract

Step 1 is to deploy your KYC Issuer contract through the right slider window. Select blockchain of your choice then select a DID which you want to associate with this contract.  Finally, connect your wallet and click on "**Deploy KYC Contract**" button.&#x20;

{% hint style="info" %}
If you do not have any DID yet, kindly refer to [this](/hypersign-ssi/setup-ssi-service/create-your-first-did.md) documentation.
{% endhint %}

{% content-ref url="/pages/Ran74Cx714lUWZJqqH6O" %}
[Supported Blockchains](/hypersign-kyc/on-chain-kyc/supported-blockchains.md)
{% endcontent-ref %}

<figure><img src="/files/J9sdM5l8xAIFdFyPpf0O" alt=""><figcaption></figcaption></figure>

You need to authorise the transaction to instantiate your KYC issuer contract through wallet. If everything works, you will see your KYC contract address in the slider.&#x20;

<figure><img src="/files/RfVFV42QDPl0rTcnYhRg" alt=""><figcaption></figcaption></figure>

Click on "**Next**" button to deploy your KYC token contract in the next step.

### Deploy Hypersign KYC Token Contract (SBT)

Same as before, authorize the transaction through your wallet to deploy your brand new KYC token contract.&#x20;

<figure><img src="/files/tmF7Sf2HWU2cmy3VnIo2" alt=""><figcaption></figcaption></figure>

Once the transaction is successfull, you will see KYC token contract address in the slider.&#x20;

<figure><img src="/files/aXHlcT9Zl9f19nndUs8h" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/OcwOcf2qEWAZdizPKQCi" alt=""><figcaption></figcaption></figure>

And your configuration is completed. Please note the configuration ID (2nd column) in the configuration record, we would need to set this configuration ID in the widget configuration.&#x20;

<figure><img src="/files/7N7WY954DbjaKthr6SrZ" alt=""><figcaption></figcaption></figure>

Now that we have deployed our contracts, let's go ahead and enable this [on chain kyc configuration](/hypersign-kyc/integrations/widget-configuration.md#on-chain-kyc) in the widget setting page:&#x20;

{% content-ref url="/pages/xBCcYcpL4pIdVZ2xEhiP" %}
[Widget Configuration](/hypersign-kyc/integrations/widget-configuration.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 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.hypersign.id/hypersign-kyc/on-chain-kyc/contracts-deployment.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.
