> For the complete documentation index, see [llms.txt](https://patches-1.gitbook.io/ordinals-standards-discussions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://patches-1.gitbook.io/ordinals-standards-discussions/ordinals-standards-proposals.md).

# Ordinals Standards Proposals

This gitbook is meant to serve as a centralization of information and proposals until a de-facto location by the Ordinals developer community is set.

## Want to help build this gitbook?

You can sign up here to become an editor who can propose change requests\
<https://app.gitbook.com/invite/XzFkio9xZudOfWX27ZPn/KMViWVeEJvsTT47im1wT>

### Ordinals Standardization Process:

There is none currently, but here's my proposal:\
<https://github.com/ordinals/ord/discussions/2156>

### Why Standards Matter:

Standards need to be set as soon as possible so developers and consumers don't get trapped building and purchasing a NFT or token that ultimately has no support and goes to 0.&#x20;

Ordinals needs a strong foundation of standards to allow new developers to easily join the eco-system, and for current dApp developers to understand what they need to support, and what is an idea that isn't vetted yet or rejected by the development community.&#x20;

I've started by consolidating the known protocols I've heard about and creating pages found below that aim to explain and consolidate information on each.&#x20;

Please feel free to contribute new links and information in pull requests, or DM me on twitter at: \
[@TMCC\_Patches](https://twitter.com/TMCC_Patches)&#x20;

### Documents for proposed standards:

1. [BRC-20](/ordinals-standards-discussions/ordinals-standards-proposals/brc-20.md)
2. [BRC-20 (Update Proposal)](/ordinals-standards-discussions/ordinals-standards-proposals/brc-20-update-proposal.md)
3. [ORC-20](/ordinals-standards-discussions/ordinals-standards-proposals/orc-20.md)
4. [SRC-20](/ordinals-standards-discussions/ordinals-standards-proposals/src-20.md)
5. [BRC-30](/ordinals-standards-discussions/ordinals-standards-proposals/brc-30.md)
6. [BRC-69](/ordinals-standards-discussions/ordinals-standards-proposals/brc-69.md)
7. [SRC-721](/ordinals-standards-discussions/ordinals-standards-proposals/src-721.md)
8. [BRC-721](/ordinals-standards-discussions/ordinals-standards-proposals/brc-721.md)
9. [BRC-721.com](/ordinals-standards-discussions/ordinals-standards-proposals/brc-721.com.md)
10. [BRC-721E](/ordinals-standards-discussions/ordinals-standards-proposals/brc-721e.md)
11. [GORC-721](/ordinals-standards-discussions/ordinals-standards-proposals/orc-721.md)
12. [GBRC-721](/ordinals-standards-discussions/ordinals-standards-proposals/gbrc-721.md)
13. [BRC-1202](/ordinals-standards-discussions/ordinals-standards-proposals/brc-1202-voting.md)

\---------------------------------------------&#x20;

\---------------------------------------------<br>

### Tips:

patches.sats\
patches.xbt

**Native Segwit:**\
bc1qdc2uh5khgwn7urqm9yndz0a2uqhcp3v65qsd7j\
**Taproot:**\
bc1pc59yxamfghnhw4h3h0g975te2ah6uzapkdj2e3uqvsd6x9fu0awqln672n\
**Segwit:**\
3C3E3xysqVHzCApfyo3LE6TAHG1ovfU3nS\
**Non-segwit:**\
1J6EFALfT6sTpTFAdx3dswTDKs41K8Xx2w\
\
**ETH Address:**\
0xd3fFdF4b910555a8Fc0B332a5aC8Dba508c472D1


---

# 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://patches-1.gitbook.io/ordinals-standards-discussions/ordinals-standards-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.