# Issue Operation

### Description

The issue operation will create a new BTC-SBT token identified by the given unique symbol.

The issuer can specify a public key used to verify the subsequent operations.

The metadata can be attached to present the descriptive information about the SBT.

The issuer itself is decided by the first output.

### Payload Schema

<pre class="language-json"><code class="lang-json">{
<strong>  "op": "issue",
</strong>  "symbol": "&#x3C;symbol>",
  "max": &#x3C;max supply>,
  "authpk": "&#x3C;public key of the authority>",
  "end": &#x3C;end block height for mint>
  "metadata": "&#x3C;serialized metadata JSON object>"
}
</code></pre>

| Field    | Type   | Description                                                                        | Memo                                                                   |
| -------- | ------ | ---------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| symbol   | string | The unique symbol in the UTF-8 charset                                             | Size ranges between \[3,8] in bytes                                    |
| max      | uint64 | The maximum supply of the SBT                                                      | Unlimited if not provided or being zero                                |
| authpk   | string | Optional public key of the issuing authority in the compressed format              | If provided, the corresponding signature will be required on mint      |
| end      | int64  | Optional end block height after which mint operations will not be allowed any more | No constraint if not provided or being zero                            |
| metadata | string | The serialized metadata of the SBT                                                 | Top level metadata such as name, description,  image, other attributes |


---

# 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://btc-sbt.gitbook.io/btc-sbt-protocol/protocol-spec/issue-operation.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.