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

Unrecognized even fields render inscriptions invalid #1107

Merged
merged 3 commits into from
Dec 29, 2022
Merged

Conversation

casey
Copy link
Collaborator

@casey casey commented Dec 29, 2022

Fixes #1046. This doesn't add a version, but allows us to add one in the future. We can add a version field with an even tag, which will render it invalid for old clients, allowing for future upgrades.

@casey casey requested a review from raphjaph December 29, 2022 06:19
for tag in fields.keys() {
if let Some(lsb) = tag.first() {
if lsb % 2 == 0 {
return Err(InscriptionError::UnrecognizedEvenField);
Copy link
Collaborator

Choose a reason for hiding this comment

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

So non-breaking changes cause an InscriptionError?

Copy link
Collaborator

@raphjaph raphjaph left a comment

Choose a reason for hiding this comment

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

Odd version number means breaking change and even means non-breaking?

@casey casey enabled auto-merge (squash) December 29, 2022 18:15
@casey casey merged commit eb1b371 into master Dec 29, 2022
@casey casey deleted the its-okay-to-be-odd branch December 29, 2022 18:16
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.

Add version number to inscriptions
2 participants