Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tweak docs #2148

Merged
merged 1 commit into from
Jun 4, 2023
Merged

Tweak docs #2148

merged 1 commit into from
Jun 4, 2023

Conversation

raphjaph
Copy link
Collaborator

@raphjaph raphjaph commented Jun 4, 2023

No description provided.

Copy link
Collaborator

@veryordinally veryordinally left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is backwards compatible with all all previously-recognized inscriptions, and provides clarity for future extensions (for example, inscriptions that are not on the first input).

@raphjaph raphjaph enabled auto-merge (squash) June 4, 2023 13:07
@raphjaph raphjaph merged commit 0158189 into ordinals:master Jun 4, 2023
@huuep
Copy link

huuep commented Jun 29, 2023

This is a great PR. It clearly defines the simple and elegant Ordinals Protocol, one that will last for a long time. The Ordinals Protocol can be simply defined in 3 rules:

  1. Ordinal Theory - how individual satoshis can be uniquely identified and tracked across transactions using FIFO.
  2. Inscription - data written to the input of a transaction (Inscriptions are not ownable yet.)
  3. Define the Ordinal onto which an Inscription is inscribed: the first satoshi in the input of the Inscription. This is a simple definition and the first satoshi in the input is the closest point to the Inscription on the blockchain. (Now inscriptions are ownable)

@raphjaph raphjaph deleted the tweak-inscriptions-docs branch January 31, 2024 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants