๐งOrdinals Standards Proposals
A concentrated list of proposed standards for Ordinals
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.
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.
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.
Please feel free to contribute new links and information in pull requests, or DM me on twitter at: @TMCC_Patches
Documents for proposed standards:
---------------------------------------------
---------------------------------------------
Tips:
patches.sats patches.xbt
Native Segwit: bc1qdc2uh5khgwn7urqm9yndz0a2uqhcp3v65qsd7j Taproot: bc1pc59yxamfghnhw4h3h0g975te2ah6uzapkdj2e3uqvsd6x9fu0awqln672n Segwit: 3C3E3xysqVHzCApfyo3LE6TAHG1ovfU3nS Non-segwit: 1J6EFALfT6sTpTFAdx3dswTDKs41K8Xx2w ETH Address: 0xd3fFdF4b910555a8Fc0B332a5aC8Dba508c472D1
Last updated