docker, cli, lang: Deterministic and verifiable builds #100
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
|
I can be boring but while system dependencies are not pinning too there is a high probability that builds will not be deterministic. |
|
@fanatid I assume this can be overcome? I haven't run into this yet. |
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.
Features
--verifiableflag toanchor build --verifiableandanchor launch --verifiable, which runs the build inside a docker image so that the output binary is deterministic (assuming one uses a Cargo.lock file)anchor verify <program-id>command, checking the deterministic build from source of the local anchor program matches what is deployed at the givenprogram-idon chain.