Repository navigation
Preserve issuer revocation across local authority rollback - #432
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
epochAnchorwith atomicadvanceEpochand epoch-awareclaimOncemethods on one independently held host store. A successful dispatch requires a new claim and an issuer epoch match in one transaction.revokeIssuerAnchored, which holds the local authority lock across the external epoch compare-and-advance and local write. The older synchronous revocation route refuses to run in this mode. Rejected or uncertain advances strand the lock for reconciliation.Verification
npm test: 992 passed.node scripts/check-package-artifact.mjs: 42 checks, no failures.npm run compatibility:consumer: passed.npm run check:links: passed.Boundary
This rejects unspent stale grants after a local store rollback only when the external store is durable, linearizable, unchanged, and all local workers and revocation routes share the same local authority lock. It does not authenticate approvals, guard bypass paths, cover a rolled-back external store, provide a multi-machine handoff guarantee, or prove provider acceptance.