Skip to content

Accept operator revocation notifications - #7789

Open
jmecom wants to merge 4 commits into
mainfrom
jm/buzz-revocation-hook-wiring
Open

jmecom wants to merge 4 commits into
mainfrom
jm/buzz-revocation-hook-wiring

Conversation

@jmecom

@jmecom jmecom commented Sep 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

Adds POST /operator/revocation-notifications, which accepts upstream notifcations from KGoose to revoke sessions for a particular npub. The endpoint reuses the existing operator NIP-98 path.

This is a stub for now.

Signed-off-by: jm <jm@squareup.com>
Co-authored-by: Codex <noreply@openai.com>
@github-actions

github-actions Bot commented Sep 21, 2026

Copy link
Copy Markdown

🔐 Codex Security Review

Status: review required for the current range.

The current range is 77729abfb692b25a0f4ec4a69add86af2e32c0dd...5948e9a40652167c9c1beb0ab44303e5f50d741c.
A new review must complete for this exact range. When manual authorization
is required, a Block organization member must comment exactly
@buzz-security-review 5948e9a40652167c9c1beb0ab44303e5f50d741c to authorize a new review.
Any previous review applies only to its recorded range.

jmecom and others added 3 commits September 21, 2026 21:31
Signed-off-by: jm <jm@squareup.com>
Co-authored-by: Codex <noreply@openai.com>
Signed-off-by: jm <jm@squareup.com>
Co-authored-by: Codex <noreply@openai.com>
Signed-off-by: jm <jm@squareup.com>
Co-authored-by: Codex <noreply@openai.com>
@jmecom
jmecom marked this pull request as ready for review September 21, 2026 22:42
@jmecom
jmecom requested a review from a team as a code owner September 21, 2026 22:42
post(api::operator::transfer_community),
)
.route(
"/operator/revocation-notifications",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: let's include auth in this path maybe? Like /operator/auth/revocation-notifications or something. I'm working on adding something for the closing of a session, and was planning on some auth path like that.

This branch has not been deployed

No deployments
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.

2 participants