Skip to content

Correct the stale claim that relay.damus.io rejects kind 31436 - #53

Merged
TheCryptoDonkey merged 1 commit into
mainfrom
fix/stale-damus-comment
Aug 7, 2026
Merged

Correct the stale claim that relay.damus.io rejects kind 31436#53
TheCryptoDonkey merged 1 commit into
mainfrom
fix/stale-damus-comment

Conversation

@TheCryptoDonkey

Copy link
Copy Markdown
Member

The default-relay comment in src/cli.ts and the operations doc both say damus rejects every kind 31436 document. That was true when written; it accepted a signed probe (kind 31436, 60s NIP-40 expiry) on 2026-08-07.

Probe results across the big public relays, for the record:

Relay kind 31436
nos.lol, primal, nostr.mom, snort.social, offchain.pub, nostr.oxtr.dev, damus accepted
relay.nostrplebs.com rejected (requires their NIP-05; all kinds)
nostr.wine, relay.nostr.band unreachable / write-restricted, untested

No kind-based rejection found anywhere; the failures are access control, not the kind. The comment and doc now state the project relay's role as the reliability anchor rather than the only relay that will carry the kind.

Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com

It did when the default relay list and the operations doc were written, but
it accepted a signed kind 31436 probe document on 2026-08-07. The rationale
for the project's own relay in the defaults is now stated as reliability:
policy and retention on relays you do not run change without notice.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@TheCryptoDonkey
TheCryptoDonkey merged commit 0a359b0 into main Aug 7, 2026
3 checks passed
@TheCryptoDonkey
TheCryptoDonkey deleted the fix/stale-damus-comment branch August 7, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant