Add BRC-X: Consensus-Unique Name Tokens — Identity Binding and Verified Resolution - #234
Open
BSVArchie wants to merge 1 commit 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.
This pull request:
Proposes a new standard by creating a new markdown file in the appropriate directory and requests discussion and assignment of a BRC number
Summary
Proposes a standard for names carried as single-satoshi tokens whose uniqueness is enforced at mint by a covenant, with an identity binding carried on the name token's own output and a resolution procedure the client verifies locally.
Number: submitted as BRC-X per the numbering convention — whatever number is available at merge is fine. Filename follows the existing
BRC-X-*.mdplaceholder pattern; no index files touched.Relation to existing BRCs: specifies the verification and resolution rules around the OpNS identity bind deployed in the
@1sat/actionsSDK — it does not invent the binding. Builds on BRC-159/160 (1Sat ordinals, inscription envelopes) and BRC-48 (PushDrop). Complementary to BRC-169, which addresses domain-scoped handles; § 2.3 discusses the relationship.Implementation status is disclosed in the document: the § 3 binding format is deployed in the SDK and its derivation was reproduced against the SDK's own primitives; the § 4 resolver is not yet implemented by the authors.
§ 10 is a request for comment, primarily § 10.1: how discovery overlays should be compensated.