mtca: write to tiles#8900
Draft
jsha wants to merge 12 commits into
Draft
Conversation
Frontier is loaded at MTCA startup, tracks appended entries and hash tiles, and writes them to storage. Implementation is written by me. The unittest in tiles_test.go was written by Claude and reviewed and lightly edited by me (including rewriting the comments in my own words).
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.
This wires up tiles.Frontier from #8896 to the MTCA's initialization and sequencing code paths. It also adds mtca.LoadFrontier, which is called from main at startup and loads the tiles into memory.
As of this change we are writing correctly-calculated RootHashes into the DB and properly-formed TBSCertificateLogEntry (wrapped in MTCLogEntry) into the tiles, along with all the hashes needed.
Note: this change is based on top of both #8886 and #8896 but is only "stacked" on top of #8886. Please ignore the changes under trees/; they will disappear once #8886 is merged and this PR is rebased.