# BRC20 IP1: Issuance and Burn Enhancements

### Proposal:

{% embed url="<https://l1f.discourse.group/t/brc-20-proposal-for-issuance-and-burn-enhancements-brc20-ip-1/621>" %}

### Block Height:

837090

### Impact:

#### Overview:

* **Introduction of Self-Issuance Mechanism**
  * Incorporation of a self\_mint option empowers asset deployers with exclusive rights to mint, enhancing control over asset issuance.
* **Adoption of 5-byte Tickers**
  * Facilitates a clearer distinction between self-issued and publicly issued assets, improving asset management and identification.
  * Increases constrained namespace
* **Consensus on the Burn Method**
  * Standardizes the asset destruction process, providing clarity and uniformity across the BRC-20 ecosystem.

#### Implications:

* **General Benefits**
  * Enhances the protocol's flexibility and functionality, allowing for more innovative asset issuance and management methodologies.
* **General Considerations**
  * Requires additional development effort and adaptation from the community, which could temporarily affect compatibility and integration with existing systems.

### Implementation:

#### Self issuance:

{% embed url="<https://github.com/bestinslot-xyz/OPI/commit/942468629f7e9959f531299041bb655e7c961872>" %}

#### Consensus on burn method:

{% embed url="<https://github.com/bestinslot-xyz/OPI/commit/a939521284d5a91056407de60404d4119e033b4e>" %}


---

# 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://layer1.gitbook.io/layer1-foundation/protocols/brc-20/proposals/brc20-ip1-issuance-and-burn-enhancements.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.