Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ #634

Closed
wants to merge 1 commit into from
Closed

Add FAQ #634

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions content/guides/advanced/verified-builds.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -422,6 +422,28 @@ verifiable and secure builds that align with your source code. Always take the
necessary precautions to use consistent environments, and consider governance
solutions for safe upgrades and deployments.

## Frequently Asked Questions

### My program compiles locally with `solana-verify build ...`, but fails with `solana-verify verify-from-repo <github> --remote ...`

If you get the error `The provided GitHub build does not match the on-chain hash` then there are two scenarios to consider.

- In the scenario where you built your program with `solana-verify build` before deploying (for example via Github Actions), then it is just a matter of finding the correct commit hash to use with `--remote`. You can specify this like so, `-solana-verify verify-from-repo --remote --commit-hash <my-commit-hash>`

- In the scenario where you built your program locally before deploying, you may have to redeploy your program. Build it by running `solana-verify build` before deploying.

However, if you get the error `Error: Error verifying program. Err(Failed to parse output)` while attempting to verify your program,
then it is likely that you need to specify the mount path to your program's workspace.
This can be set by specifying `--mount-path <path/to/program-dir>`.
Copy link
Collaborator

@Woody4618 Woody4618 Nov 19, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And make sure you are using the correct --library-name i think that was the actual problem squads ran into.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also need to run pnpm prettier:fix i think


### My program is not verifying with `--remote`, how do I debug?

Make sure that you are running the latest version of `solana-verify` (at least as recent as 0.3.0 or higher). You can update by running `cargo install solana-verify`.
Now run `solana-verify verify-from-repo --remote ...` again.
Now on failure you should see a logs url (like `https://verify.osec.io/logs/<uuid>`) that may help debug your build.
If there is still a problem, please open an issue on https://github.com/Ellipsis-Labs/solana-verifiable-build with your logs url.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Who will be managing these?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wdym? Managing what in particular?



## Security + Disclaimer

While verified builds are a powerful tool for ensuring the integrity of your
Expand Down
Loading