> For the complete documentation index, see [llms.txt](https://layer1.gitbook.io/layer1-foundation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://layer1.gitbook.io/layer1-foundation/protocols/brc-20/proposals.md).

# Proposals

A number of improvement proposals have been submitted to L1F. 

## Modular Complexity \[-]

The post proposes a new approach to support various inscription-based applications within the existing brc-20 framework. Modules operate independently of each other, and each Indexer only needs to parse data relevant to their interested module while still maintaining brc-20 balance consistency with other indexers.

{% embed url="<https://l1f.discourse.group/t/brc-20-the-modular-proposal-by-unisat/35>" %}

## The Freeze \[✓]

Given past issues in older versions of Ord and in anticipation of significant updates, this post proposes that indexers standardize on the current reference version (0.9) to ensure consistent inscription validity and state stability in brc-20. Introduced at block height 816000.

{% embed url="<https://l1f.discourse.group/t/brc-20-the-freeze/85>" %}

## Core Cleanup Phase 1 \[-]

This post proposes the integration of a new core function, named “fraction,” into the brc-20 protocol to improve the experience of token transfers for all users. The fraction function is introduced to safeguard against unwanted transfer inscriptions that could disrupt tokens and disrupt a user’s operations.

{% embed url="<https://l1f.discourse.group/t/brc-20-core-function-cleanup-phase-1/118>" %}

## BRC20 IP1: Issuance and Burn Enhancements \[✓]

New issuance method (self mint) enabled for 5 digit tickers. Burn methodology consensus reached.

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


---

# 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://layer1.gitbook.io/layer1-foundation/protocols/brc-20/proposals.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.