Skip to content

Conversation

XuJiandong
Copy link
Collaborator

@XuJiandong XuJiandong commented Sep 23, 2025

Please review the deployment configuration by reading this guide first.

After completing your review, please approve this deployment or leave a comment with "LGTM" if you don't have approval permissions. Once we receive approval from all 5 reviewers, the deployment will be signed and broadcast to the P2P network.

@XuJiandong XuJiandong requested review from quake and xxuejie September 23, 2025 01:49
@XuJiandong
Copy link
Collaborator Author

If you prefer not to make your email address public, please provide one of the following alternatives instead:

  • GitHub account
  • X (Twitter) account
  • Discord account
  • Well-known nickname in the CKB community

Anyone can use the information you provide to verify that you own the CKB address.

## step 1: verify binary
function verify_binary() {
get_expected_hash() {
grep "build/release/c-sphincs-all-in-one-lock$" ../../checksums.txt | awk '{print $1}'
Copy link

Choose a reason for hiding this comment

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

I got a question.

Shouldn't checksum be calculated on the binary instead of being grepped from checksum.txt?
Or maybe there should be a checksum validation prior to this function?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The checksums.txt is from reproducible build. See

if [[ "${UPDATE}" = "yes" ]]; then
echo "${CHECKSUM_FILE_PATH} file is updated with latest binary hashes!"
else
shasum -a 256 -c ${CHECKSUM_FILE_PATH}
fi

So we don't need to build it from scratch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants