feat(store): scope-keyed RDS checkpoints and a proposals bucket - #54
Merged
Merged
Conversation
WHATIF §5.3 proposals bucket plus GROWTH §6 scope-keyed RDS checkpoints. The existing SaveEvidenceCheckpoint precedent is not scope-keyed: colliding keys would serve one region's history confidently as another's. The new checkpoint keys carry scope, and absent is kept distinct from present-but-unreadable so a read failure can never collapse into "no history". A forged blob's approved flag is not treated as an approval. Buckets bucketProposals and bucketRDSCheckpoints are created in Open alongside the existing five. Co-authored-by: kording <74226694+kording@users.noreply.github.com>
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
1 participant
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.
WHATIF §5.3 proposals bucket plus GROWTH §6 scope-keyed RDS checkpoints.
The existing SaveEvidenceCheckpoint precedent is not scope-keyed: colliding keys
would serve one region's history confidently as another's. The new checkpoint
keys carry scope, and absent is kept distinct from present-but-unreadable so a
read failure can never collapse into "no history". A forged blob's approved
flag is not treated as an approval.
Buckets bucketProposals and bucketRDSCheckpoints are created in Open alongside
the existing five.