File data meta gzip generic versioning#10
Open
JawedAshraf wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'd like to open up a proposal for versioning of data in OP_RETURN, using two new optional elements that allow a chain of OP_RETURNS to be identified by clients.
With the right kind of crypto I believe it is possible for a publisher to authenticate each newly published version. This allows clients to reject OP_RETURNS that purport to be new versions if they do not provide the correct elements. But IANAC (I am not a cryptographer) so I'm assuming that this chain based on pairs of keys will work.
Essentially the publisher of an OP_RETURN adds a key which allows them to "spend" the OP_RETURN with a replacement (new version) OP_RETURN, which also provides a new key that they can spend later.
There may be a requirement to allow version-forking (versions 2 and 3 can exist both forked from version 1). I don't want to go deep into that, because I'm initially interested in whether versioning is seen as worthwhile.