> 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-structure-and-standards.md).

# Ordinals: Structure & Standards

As Ordinals gains adoption and scales, the need for a robust and decentralized consensus mechanism and general standardization becomes crucial. The solutions proposed in this gitbook aim not only to address the existing challenges but also to **ignite broader discussion within the community to guide the protocol's future growth trajectory**.

I broke up this document into three parts. 

First, I go over potential consensus mechanisms that could be implemented on Ordinals and the ramifications for each potential path. 

Second, I define a process heavily inspired by Bitcoin's process for the start to standardization in the ecosystem. 

Last, I show an example of what OIP-001 could look like if the standardization  process was adopted by Ordinals.

1. [Consensus Solutions](/ordinals-standards-discussions/ordinals-structure-and-standards/consensus-solutions.md)
2. [Standardization Proposal](/ordinals-standards-discussions/ordinals-structure-and-standards/standardization-proposal.md)
3. [Sample OIP-001](/ordinals-standards-discussions/ordinals-structure-and-standards/sample-oip-001.md)

### Author Bio

[Patches](https://twitter.com/TMCC_Patches) is the CEO of [Turtle Moon](https://turtlemoon.io) and Co-founder of [Hgraph](https://hgraph.io). With 15 years of engineering experience and around 2 years in Web3 development, Patches has contributed to solidifying NFT metadata standards on Hedera and is an active participant in 3 working groups building standards. This document is an attempt to contribute to the discussion on the development trajectory of Ordinals and it hopes to help bring longevity and structure to the protocol.<br>

Please note that the contents of this document are the opinions of the author and are **intended to spark discussion rather than dictate a particular solution**.

**Tips:** \
patches.sats