Technical note on Transparency Logs for SCAL3 #1
Conversation
This file contains 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.
I’m curious about community feedback on using tlogs for SCAL3 systems. To get the conversation started, this technical note contains our current ideas and can be read independently from other SCAL3 docs.
When you provide feedback that leads to an update of this note or related docs, I’d like to include acknowledgement of your contributions. Please indicate upfront if you don’t appreciate this.
Update: Some of the changes have now been included in a refactoring of the
mainbranch. I’m keeping this fork open since not all improvements are yet included, and the newtlog.mddoc may be easier for technical feedback on the tlog design.