Add native full-build v2 snapshot evidence - #8
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.
Summary
full_buildevidence for snapshot buildsWhy
Production snapshot builds need one internally consistent generation for the runtime database, proof directory, Direct ORAM inputs, and v2 attestation evidence. The existing v2 path only re-attested an earlier v1 proof and could not represent a native full build.
Validation
cargo test -p dbpipeline existing_onion_layout_v2_accepts_only_empty_single_bin_tree_topscargo test -p pir-attested-builder(31 passed)bash -n scripts/build-snapshot-database.sh scripts/local-regtest-e2e.shscripts/local-regtest-e2e.shcargo check -p pir-attested-buildergit diff --checkNo SEV, mainnet, browser, or production operation was performed.