RFC-009: Nostr-addressing as the primary delivery path (for comment)#356
Open
laulpogan wants to merge 1 commit into
Open
RFC-009: Nostr-addressing as the primary delivery path (for comment)#356laulpogan wants to merge 1 commit into
laulpogan wants to merge 1 commit into
Conversation
…or comment) Inversion of RFC-007 (which added Nostr as an additive fallback): make pubkey-addressed publish/filter the primary delivery semantics on wire-OPERATED relays, removing the structural PENDING_ACK window and the single-mailbox outage surface, and retiring the bespoke slot+token relay. Status: Discussion (open for comment). Tracking issue #355. Target v0.17 (post-1.0, not a soak-window change). Recommends the direction while soliciting comment on five open questions (key curve, fleet ownership, consent semantics, retire-vs-coexist, relay impl). Honest on the cost: NIP-42 AUTH + receiver pin-filter replace slot_token write-authz at the same trust boundary; clear p-tag means NIP-17 is a hard precondition for any public-relay use; wire-x25519.v1 != nip44.v2 so no free DM interop. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
RFC for comment — adds
docs/rfc/0009-nostr-addressing-primary.md, status Discussion. Tracking: #355.This is the inversion of RFC-007 (Nostr as an additive fallback) → Nostr-addressing as the primary delivery path on wire-OPERATED relays.
The ask
Comment on the direction and the five open questions — this is a doc PR, no code. Recommendation is "yes, v0.17, scoped to wire-operated relays, gated on NIP-17 for any public use, justified by resilience+maintenance not PENDING_ACK."
Why (the real trigger, not the gap)
PENDING_ACK(now labeled by fix(dial): bare-nick dial surfaces the same unsendable reasonwire sendemits #354) is the symptom that raised the question, but a minor wart — the wrong reason to swap a substrate.What it buys / what it costs
slot_tokenwrite-authz → NIP-42 AUTH + receiver pin-filter (same trust boundary on wire-operated relays); clear recipientp-tag → NIP-17 is a hard precondition for any public-relay delivery (named in RFC-007, unbuilt);wire-x25519.v1≠nip44.v2→ no free third-party DM interop.Guardrails
Post-1.0 (v0.17), not a soak-window change — 1.0 ships on the current substrate. Wire-operated relays only; public-relay delivery deferred behind NIP-17.
🤖 Generated with Claude Code