jerry/buzz
1
0
Fork 0
mirror of https://github.com/block/buzz.git synced 2026-10-28 21:11:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(testing): clarify invite ban regression contract

Browse Source 
Signed-off-by: seiler <seiler@squareup.com>
Co-authored-by: Codex <noreply@openai.com>
(cherry picked from commit 5bbf2b64a82115c40fdadeb981dbfdf7122241f2)
Signed-off-by: Brad Seiler <seiler@squareup.com>
This commit is contained in:
seiler
2026-10-05 21:27:19 +00:00
committed by Brad Seiler
parent 918ef4e199
commit cb852abf68
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
TESTING.md
View File

@@ -66,9 +66,12 @@ principal to restrict. Invite claim is also pre-membership, but it carries a
verified NIP-98 principal and remains restriction-enforced: it is the sole
row marked pending in the inventory until BUZZ-268 qualifies the updated
v1/v2 lifecycle:
retain valid unexpired v1 codes, mint only v2, reject banned claimants and
owners transactionally, permanently invalidate v2 on issuer ban, and honor the
optional absolute invalid-after boundary for v1. Legacy v1 codes have no issuer
retain valid unexpired v1 codes and mint only v2, with a 72-hour default and
30-day maximum lifetime. Both formats reject banned claimants and owners
transactionally, and issuer bans permanently invalidate v2. For v1, an unset
operator `invalid_after` uses natural expiry; when set, the code rejects at or
after that absolute boundary, while an earlier code expiry still takes effect.
That operator boundary does not affect v2. Legacy v1 codes have no issuer
identity, so issuer-specific revocation remains limited until a verified fleet
drain or security approval. Relay-operator APIs, deployment-admin APIs,
NIP-FI commands, the localhost Git hook, and the gated mesh test endpoint use