BIP-XX: MRK On-Chain Marking Protocol #6
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
Introduces a compact protocol for timestamping and attributing content references using OP_RETURN transactions. Supports: URL, Address, Content, Nostr, Git Commit, Document types. See: #5
- Type 0x04: Nostr Profile - raw 32-byte pubkey (no hashing) - Type 0x08: Nostr Event - raw 32-byte event id (no hashing) Nostr identifiers are already 32 bytes, so they're stored directly without SHA256 hashing unlike URL/Content types.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Introduces the MRK protocol for on-chain content marking using OP_RETURN transactions.
Closes #5
Specification
MRK+ version + type + SHA256 hashMotivation
Marks provide the primitive for building reputation, attribution, and proof-of-existence systems on Bitmark.
Status
Draft - awaiting BIP number assignment.