> For the complete documentation index, see [llms.txt](https://relationlabs.gitbook.io/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://relationlabs.gitbook.io/protocol/appendix/semantic-sbt-deployment-tool.md).

# SemanticSBT Deployment tool

## Quick Start

### Download the tool

Clone the repository from github:

```
git clone git@github.com:relationlabs/sbt-deployment-utils.git
```

### Install dependencies:

```
yarn
```

### run the project:

```
yarn dev
```

If successful, you can access <http://localhost:3000>.

## Contract deployment

### Login via metamask:

<figure><img src="/files/aqS6hKqEMkoAZyXx1RGa" alt=""><figcaption><p>Figure 9-1 Connect Wallet</p></figcaption></figure>

### Choose the blockchain which the contract will be deployed on:

Here we use Polygon as an example:

<figure><img src="/files/2czPVC2p7CpvcpANSAg3" alt=""><figcaption><p>Figure 9-2 Select a Network</p></figcaption></figure>

### Create a new SBT contract and deploy it:

<figure><img src="/files/fIiJL59hClN1LPPg5Uji" alt=""><figcaption><p>Figure 9-3 Start Deploy</p></figcaption></figure>

#### The contract deployment procedure includes: 1. Deploying the SBT and Verification contract. 2. Initialize the SBT contract. 3. Initialize the Verification contract. 4. Add to the whitelist. 5. Mint SBT (These subsequent procedures need enough gas fee in the wallet).

#### 1. Deploy the contract:

Deploy the SBT contract and its Verification contract:

<figure><img src="/files/BR92Mlx7qpe16ZHV50b1" alt=""><figcaption><p>Figure 9-4 Deploy Contract</p></figcaption></figure>

#### 2. Initialize the SBT contract:

If the contract deployment is successful, you can see its contract address. Then the initialization process of the SBT can begin.

<figure><img src="/files/mS3col1QdgniuKYiyZ8j" alt=""><figcaption><p>Figure 9-5 Start Init Contract</p></figcaption></figure>

During initializing the SBT, we will need to fill in certain properties of the SBT based on the needs of the project. Here we take the TestSBT as an example:

<figure><img src="/files/DYrheTNh1utlxs0k4RD1" alt=""><figcaption><p>Figure 9-6 Init Contract</p></figcaption></figure>

#### 3. Initialize the Verification contract:

Based on the needs of the project, we should fill in the name of the Object. Here we will use the Token2049 as an example:

<figure><img src="/files/xgVMXmvtjytLtkKc4uVN" alt=""><figcaption><p>Figure 9-7 Init Verification Contract</p></figcaption></figure>

#### 4. Add to the whitelist

To specify addresses which can mint the SBT. You can add multiple addresses at a time.

<figure><img src="/files/kfsIP2OGeGFwwtyQx15m" alt=""><figcaption><p>Figure 9-8 Add Whitelist</p></figcaption></figure>

#### 5. Mint SBT

<figure><img src="/files/SFXBgYaKDdbHAdxJtHbq" alt=""><figcaption><p>Figure 9-9 Mint SBT</p></figcaption></figure>


---

# 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://relationlabs.gitbook.io/protocol/appendix/semantic-sbt-deployment-tool.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.
