Solutions considered

Custom Docker stage ❌

Instead of spinning up Docker ourselves and building it, make prod-build that calls anchor build --verifiable under the hood does the same thing. Hence, we don't need the Dockerfile changes to generate the artifacts.

anchor build --verifiable ❌

This fails when trying to build for Anchor v0.29.0. This is because Anchor v0.29.0 Dockerfile uses the old domain (release.solana.com) to install Solana CLI which now fails. Hence, we remove the prod-build target as well.

solana-verify build ✅

This works similar to anchor build --verifiable but uses the new recommended domain (release.anza.xyz) to install Solana CLI. We thus use this as the preferred solution.

Solutions considered

Custom Docker stage ❌

Instead of spinning up Docker ourselves and building it, make prod-build that calls anchor build --verifiable under the hood does the same thing. Hence, we don't need the Dockerfile changes to generate the artifacts.

anchor build --verifiable ❌

This fails when trying to build for Anchor v0.29.0. This is because Anchor v0.29.0 Dockerfile uses the old domain (release.solana.com) to install Solana CLI which now fails. Hence, we remove the prod-build target as well.

solana-verify build ✅

This works similar to anchor build --verifiable but uses the new recommended domain (release.anza.xyz) to install Solana CLI. We thus use this as the preferred solution.

To verify that the solutions generate equivalent artifacts, I generated solana-devnet artifacts using all 3 solutions and compared the executable hashes using:

solana-verify get-executable-hash artifacts-solana-devnet/deploy/example_native_token_transfers.so

All 3 solutions resulted in the same hash (66b5a2c0cd434050906dad40b9681407994e9755feb3c40ca7073fe7a251892f)