# Quick Start

{% hint style="info" %}
POI currently functions as a standalone index. During its design phase, we took cues from the foundational code of ORC-20 to ensure better compatibility. Once the ORC-20 community integrates POI, it will seamlessly align with the ORC-20 system. Stay tuned for updates from the community!
{% endhint %}

## Mint

```
* Inscribe any inscription
* Valid range: #0 to #734999999
* The genesis allocation for each inscription is 210 $POI, halving every 21 million inscriptions. 

```

## Claim

<table><thead><tr><th>Key</th><th width="115">SubKey</th><th width="124">Required ？</th><th width="151">Fixed Value</th><th>Description</th></tr></thead><tbody><tr><td>p</td><td></td><td>Yes</td><td>“orc-20”</td><td><strong>Protocol</strong>: help other systems identify and process POI operations.</td></tr><tr><td>op</td><td></td><td>Yes</td><td>“minting-claim”</td><td><strong>Operation</strong>: type of operation</td></tr><tr><td>params</td><td>tick</td><td>Yes</td><td>poi</td><td><strong>Ticker</strong>: symbol of the POI</td></tr><tr><td>params</td><td>tid</td><td>Yes</td><td>1</td><td><strong>Token ID</strong>: identifier of the POI, the inscription ID where the token is deployed.</td></tr><tr><td>params</td><td>amt</td><td>Yes</td><td></td><td><strong>Amount to mint</strong>: it states the amount of the POI to claim. It needs to be less than or equal to the claimable amount.</td></tr></tbody></table>

**Example:** Inscribe a claim-inscription and claim all of your $poi.

```
{
  "p": "orc-20",  
  "op": "minting-claim", 
  "params": {
    "tick": "poi", 
    "tid": "1",
    "amt": "210" 
  }
}
```

## Transfer

| Key    | SubKey | Required ？ | Fixed Value | Description                                                                          |
| ------ | ------ | ---------- | ----------- | ------------------------------------------------------------------------------------ |
| p      |        | Yes        | “orc-20”    | **Protocol**: help other systems identify and process POI operations.                |
| op     |        | Yes        | “transfer”  | **Operation**: type of operation                                                     |
| params | tick   | Yes        | “poi”       | **Ticker**: symbol of the POI                                                        |
| params | tid    | Yes        | 1           | **Token ID**: identifier of the POI, the inscription ID where the token is deployed. |
| params | amt    | Yes        |             | **Amount to transfer**: it states the amount of the POI to transfer.                 |

**Example:** Inscribe a transfer-inscription and send it to receiver's address.

```
{
	"p": "orc-20",
	"op": "transfer",
	"params": {
		"tick": "poi",
		"tid": "1",
		"amt": "1000"
	}
}
```

## Burn <a href="#burn" id="burn"></a>

| Key    | SubKey | Required ？ | Fixed Value | Description                                                                          |
| ------ | ------ | ---------- | ----------- | ------------------------------------------------------------------------------------ |
| p      |        | Yes        | “orc-20”    | **Protocol**: help other systems identify and process poi operations.                |
| op     |        | Yes        | “burn”      | **Operation**: type of operation                                                     |
| params | tick   | Yes        | poi         | **Ticker**: symbol of the poi                                                        |
| params | tid    | Yes        | 1           | **Token ID**: identifier of the poi, the inscription ID where the token is deployed. |
| params | amt    | Yes        | 1000        | **Amount to burn**: it states the amount of the poi to burn.                         |

1. **After the inscription is inscribed, it does not take effect immediately. It requires a single transfer of the inscription to become effective, and simultaneously, the inscription itself becomes inactive.**
2. Sending the burn-inscription to your own address; sending them to other addresses will be invalid.
3. During the transfer of the inscription, the 'amt' value should be less than or equal to the user's **`available balance`**. If the 'amt' value exceeds the user's balance, the operation becomes invalid, and the inscription becomes inactive.

#### &#x20;<a href="#undefined-2" id="undefined-2"></a>

### Step 1 &#x20;

### Inscribe a burn-inscription

Example：

```json
{
	"p": "orc-20",
	"op": "burn",
	"params": {
		"tick": "poi",
		"tid": "1",
		"amt": "1000"
	}
}
```

### Step 2

**Execute burn**

Transfer `burn-inscription` to your address


---

# 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://orcmarket.gitbook.io/orcmarket/proof-of-inscription/quick-start.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.