Repository navigation
fix(enforcement): refuse live-ledger replay after record loss - #805
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.
If an operation effect deletes its spent record before settlement, the same live ledger could dispatch that operation again under a newly issued capability. Retain hashes of successfully consumed operation IDs in private bounded memory, refuse replay before filesystem admission, and report missing persisted history as unavailable.
Failed consumption does not reserve an ID. History has the existing 256-entry ceiling, with no eviction. This guarantee applies to the same live ledger; restart after complete record erasure, rollback and power-loss qualification still require protected durable ownership.
Validation: 68 tests across the affected ledger/broker and four direct-caller suites passed after integration; scoped ESLint and formatting passed. Independent Astra requirements, engineering and integration binding reviews passed. Required GitHub contexts must pass on this PR head before merge.