docs(design): relay write-admission forward path — close the grant→relay gap (ready-3279) - #238
Open
baron-3dl wants to merge 2 commits into
Open
docs(design): relay write-admission forward path — close the grant→relay gap (ready-3279)#238baron-3dl wants to merge 2 commits into
baron-3dl wants to merge 2 commits into
Conversation
…lay gap (ready-3279) A new ready writer identity has no working forward path to relay write access: `rd relay sync-allowlist` writes scripts/relay-policy/write-allowlist.json (a strfry-era file), but the deployed cosmos/khatru relay ignores it and admits only via manual NIP-86. So invite→join→grant dead-ends — grant-derived keys never reach the relay. Documents the target: one capability-sourced write gate (author-self | admin | valid-39301-owner-grant | public-PoW), building on the already-DECIDED identity model (nostr-identity-model.md) and the FROZEN confidential envelope (so reads can be open — confidentiality is encryption, orthogonal to admission). Frames the decision (§6): A interim (sync-allowlist → NIP-86 reconcile) vs B end-state (relay derives admission from 39301 grants). Vibrant open+PoW (nostr-relay nostrrelay-164) already implements the public-PoW case. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…eady-3279 Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Design doc for ready-3279. Written after diagnosing why a new ready writer identity has no working forward path to relay write access.
The break (concrete)
rd relay sync-allowlist(pkg/sync/allowlist.go:21) writesscripts/relay-policy/write-allowlist.json— a strfry-era file. The deployed cosmos/khatru relay (nostr-relaynostrrelay-8d2) ignores it and admits writers only via manual NIP-86allowpubkey(admin-gated). So the designed invite→join→grant→sync path dead-ends: grant-derived keys never reach the relay.What this doc does
nostr-identity-model.md(owner-rooted 39301 delegation, generate-then-authorize, invite lifecycle are all DECIDED).confidential-boards-envelope.md, FROZEN) and orthogonal to admission — so reads can be open.author-self | admin | valid-39301-owner-grant | public-PoW.Decision needed (§6)
sync-allowlist --applyfrom the dead JSON to a NIP-86 reconcile — forward path works this week, allowlist is a grant cache.Recommendation: B end-state, A acceptable interim; they're compatible.
Cross-repo: enforcement code lands in
~/projects/nostr-relay/internal/cosmosstore. Vibrant open+PoW (nostr-relaynostrrelay-164, shipped 2026-08-19) already implements the public-PoW case and is forward-compatible.🤖 Generated with Claude Code