Design discussion / RFC: enforce token + grant lifecycle at sign time (the root behind #24)
Option D (leaning D1) implemented and deployed to all servers via #27 (merge 992c6a8):
Token
expiresAt (TTL) is not enforced post-bind — sign-time ACL ignores it
Fixed by #27 (merge 992c6a8), deployed to all servers 2026-06-19.
fix(acl): enforce token grant lifecycle live at sign time (#24, #25)
Correction: on LNbits-connected instances, the remediation is targeted delete only — never a full wipe
Remove the redundant, always-failing
npm run prisma:migrate step in start.js
padreug
deleted branch 2026-06-19 16:05:20 +00:00
issue-25-live-grant-lifecycle from aiolabs/nsecbunkerd
fix(acl): enforce token grant lifecycle live at sign time (#24, #25)
fix(acl): enforce token grant lifecycle live at sign time (#24, #25)
Note: the "clean DB assumed" stance has a shelf life (it ends at launch / #18)
fix(acl): enforce token grant lifecycle live at sign time (#24, #25)
Thanks — sharp review. Addressed below; pushed 7dcf97a.
flake devShell exports prisma-engines 7.x — breaks
prisma migrate/validate in the dev shell
Add a DB-backed test harness + integration tests for checkIfPubkeyAllowed
Enforce PolicyRule.maxUsageCount live at sign time (needs a durable signing log)
padreug
created branch issue-25-live-grant-lifecycle in aiolabs/nsecbunkerd
2026-06-19 13:17:25 +00:00
Design discussion / RFC: enforce token + grant lifecycle at sign time (the root behind #24)
Prior-art survey, source-verified — the complete picture
NDK NIP-46 backend: get_public_key bypasses the permit callback — pubkey disclosure is ungated/unauditable through our ACL seam
Design discussion / RFC: enforce token + grant lifecycle at sign time (the root behind #24)
Prior art #2: