# Deploy (D)

### Deploy (D):

Deploy transactions are used to create new tokens on the Dogecoin blockchain.

* **Type**: D (Deploy)
* **Action**: D
* **Fields**:
  * `token`: The unique identifier for the token.
  * `total`: The total supply of the token.
  * `limit`: The maximum amount of tokens that can be minted per one mint.
  * `decimal`: The number of decimal places the token supports.

### **Example OP\_RETURN Data**:

```mathematica
D D TOKEN_NAME 1000000 1000 2
```

### **Role of UTXOs**:

* A UTXO is created to hold the data of the token deployment.
* This UTXO contains the OP\_RETURN data with information about the token's creation.
* It does not represent a balance but serves as a historical record of the token's deployment.

#### Example Transaction Processing:

### Deploy Transaction:

1. **Extract OP\_RETURN Data**: Decode the hex-encoded string to extract token details.
2. **Validate Fields**: Ensure all required fields (token, total, limit, decimal) are present.
3. **Store Token Data**: Save the token details, including the deployer address and block metadata.

<br>

<br>


---

# 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://dipe.gitbook.io/dipe-protocol-on-dogecoin/transaction-types/deploy-d.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.