Skip to content

feat: add create cluster sem checks#388

Merged
varex83 merged 2 commits into
mainfrom
bohdan/create-cluster-cmp
May 18, 2026
Merged

feat: add create cluster sem checks#388
varex83 merged 2 commits into
mainfrom
bohdan/create-cluster-cmp

Conversation

@varex83
Copy link
Copy Markdown
Collaborator

@varex83 varex83 commented May 11, 2026

No description provided.

Comment thread scripts/create-cluster-compare.sh Outdated
FEE_RECIPIENT_ADDRESS="0xDeaDbeefdEAdbeefdEadbEEFdeadbeEFdEaDbeeF"
WITHDRAWAL_ADDRESS="0xDeaDbeefdEAdbeefdEadbEEFdeadbeEFdEaDbeeF"

EXACT=0
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Can the exact work? since the seed for charon and pluto will be different.

Comment on lines +16 to +26
if [[ -z "${PLUTO_BIN:-}" ]]; then
PLUTO_BIN="${ROOT_DIR}/target/debug/pluto"
fi

if [[ -z "${CHARON_BIN:-}" ]]; then
if [[ -x "${ROOT_DIR}/../charon/charon" ]]; then
CHARON_BIN="${ROOT_DIR}/../charon/charon"
else
CHARON_BIN="charon"
fi
fi
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

should expect to set the path, the ../charon seems a bit off. Also the charon_bin should be required, otherwise we can run with different version of charon.

Removed the silent ../charon/charon and PATH fallbacks for CHARON_BIN so
runs cannot pick up a stale or mismatched charon version, and removed
the --exact mode since charon and pluto draw randomness from independent
CSPRNGs and cannot produce byte-identical locks.

Co-authored-by: varex83 <varex83@users.noreply.github.com>
@varex83 varex83 merged commit 70c8afa into main May 18, 2026
5 checks passed
@varex83 varex83 deleted the bohdan/create-cluster-cmp branch May 18, 2026 11:46
@emlautarom1
Copy link
Copy Markdown
Collaborator

@varex83 Could yo elaborate on what this PR achieves? It's not used on CI or any other place. When should we run this script? Should it be part of the test suite?

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.

4 participants