Skip to content

Commit 2230422

Browse files
committed
update README.md
1 parent 7a5848b commit 2230422

1 file changed

Lines changed: 12 additions & 2 deletions

File tree

README.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,14 +38,24 @@ cargo build-sbf --manifest-path program/Cargo.toml
3838
make build-sbf-program
3939
```
4040

41-
The BPF program deployed on all clusters is built with [solana-verify](https://solana.com/developers/guides/advanced/verified-builds). It may be verified independently by comparing the output of:
41+
The BPF program deployed on all clusters is built with [solana-verify](https://solana.com/developers/guides/advanced/verified-builds) and can be verified independently. First, find the program hash from the deployed build on Mainnet-Beta:
4242

4343
```console
4444
solana-verify get-program-hash -um SVSPxpvHdN29nkVg9rPapPNDddN5DipNLRUFhyjFThE
4545
```
4646

47-
with:
47+
As of v5.1.0, the Github release tag will be embedded in the deployed program binary. If you do not know the currently deployed Single Pool version, you may perform:
48+
49+
```console
50+
query-security-txt -um SVSPxpvHdN29nkVg9rPapPNDddN5DipNLRUFhyjFThE
51+
```
52+
53+
And observe the "Source release" field. Note the above command will not work until v5.1.0 is live.
54+
55+
Once this is done, or if you already know the proper release tag, you may check it out and determine the progam hash via:
4856

4957
```console
5058
solana-verify build --library-name spl_single_pool
5159
```
60+
61+
The hash from Mainnet-Beta and the hash you compute locally should be identical.

0 commit comments

Comments
 (0)