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 PR cuts a new release of solana-verify and bumps the version
0.4.0
.Changes since 0.3.1:
solana-verify verify-from-repo --remote
to skip local build first, and go straight to writing the verification data unchain, then submitting a job to the OSec APIsolana-verify verify-from-repo --compute-unit-price
solana-verify remote submit-job <program id> --uploader <uploader>
now submits a remote job for using only the PDA written bysolana-verify remote get-job --job-id <job-id>
gets the job status of a given job idsolana-verify remote get-status --program-id <program id>
gets the verification statuses by signer for a program IDsolana-verify export-pda-tx --encoding base58/base64 --compute-unit-price 0
will now give you a base58/base64 transaction that you can use to write verification PDA from squads multisigsolana-verify verify-from-repo --remote
to encourage mutlisig users to usesolana-verify submit-job
when they need to verify a specific uploader's verification arguments.