Skip to content

docs(remote): state what the relay enforces for NIP-OA grants - #915

Merged
avivsinai merged 1 commit into
mainfrom
docs/relay-grant-enforcement
Sep 28, 2026
Merged

avivsinai merged 1 commit into
mainfrom
docs/relay-grant-enforcement

Conversation

@avivsinai

Copy link
Copy Markdown
Owner

The amq-remote README and the ADR now say what a Buzz relay checks for a strict-share body: the owner signature always; the grant expiry only on relays that include block/buzz#7004; kind= conditions never at connection admission, so per-kind limits are enforced by amq-remote itself. It also says how to revoke a body key on the relay. Found by reading the relay source (crates/buzz-sdk/src/nip_oa.rs, verify_auth_tag_for_auth_event).

🤖 Generated with Claude Code

A Buzz relay checks the owner signature at AUTH. Time bounds are refused
only by relays that include block/buzz#7004, and no relay checks kind=
conditions at admission, so per-kind limits are the endpoint's own.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@avivsinai
avivsinai merged commit 691ebfe into main Sep 28, 2026
6 checks passed
@avivsinai
avivsinai deleted the docs/relay-grant-enforcement branch September 28, 2026 16:40
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