NIP-73: add Namecoin name external content id#2353
Open
mstrofnone wants to merge 1 commit into
Open
Conversation
Adds a third blockchain artifact type alongside the existing `<blockchain>:tx:` and `<blockchain>:address:` shapes introduced in nostr-protocol#1846: `<blockchain>:name:<namespace>/<name>` for naming chains that expose names as a first-class on-chain primitive. Follows the same one-row-in-the-table + one-section-in-the-examples shape used by the ISO 3166 addition (nostr-protocol#2205) and the original blockchain transactions/addresses addition (nostr-protocol#1846). Example: ["i", "namecoin:name:d/example"] ["k", "namecoin:name"] The `<namespace>` (e.g. `d` for Domain Name Object names, `id` for identity names) and the `<name>` are matched byte-for-byte against the on-chain key. ifa-0001 is the canonical reference for both namespaces. Motivation: Namecoin names are not transactions and not addresses, so neither of the existing two artifact types fits. Adding `name:` as a parallel artifact type keeps the schema additive (existing parsers ignore unknown `k` tag values per NIP-73's general rule) and lets relays and indexers query for all Nostr events that reference a given Namecoin name with a single `#i` filter. This is independent of any other Namecoin-related NIP work and is useful regardless of whether further Namecoin-anchored discovery schemes are adopted.
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.
Adds a third blockchain artifact type to NIP-73 alongside the existing
<blockchain>:tx:and<blockchain>:address:shapes from #1846:For naming chains (Namecoin and similar) that expose names as a first-class on-chain primitive distinct from transactions and addresses.
Why
Namecoin names aren't transactions and aren't addresses, so neither of the existing two
<blockchain>:artifact types fits when an event references one. With this addition, a Nostr event that references the Namecoind/examplename (resolved asexample.bit) can be tagged:…and any relay that already indexes NIP-73
#ifilters can answer "show me every event that references this Namecoin name" without any new infrastructure or new NIP work. Useful for cross-system catalogs, name-anchored social graphs, attestations, and chain-anchored identity flows.Shape
+30/-1 in a single file. One row in the artifact-type table, one section in the examples (mirroring the existing Bitcoin and Ethereum sections), one mention of
namecoinin the introductory list of layer-1 chains. Existing references likebitcoin:tx:...andethereum:1:address:...are unaffected.No new event kinds. No new tags. No changes to existing NIPs. Additive only — clients that don't recognize
namecoin:name:ignore it the same way they already ignorekvalues they don't know.References
<namespace>semantics (d/,id/): namecoin/proposals ifa-0001.Relationship to other Namecoin work
This PR is independent of #2349 (NIP-05 verification via Namecoin) and #2330 (the broader Namecoin-track RFC). Whether or not those land, this one row makes Namecoin names referenceable through the existing NIP-73 discovery channel — which is useful for any tooling that wants to catalog or index references to Namecoin names from Nostr events, regardless of how identity verification is ultimately specified.