Repository navigation
executor-v1.182
What's Changed
- DAH-4689 - [P4] liumd shadow: read docker and ports right after machine_scrape by @surcyf123 in #2196
- DAH-2834 executor: vendor liumd from 53999a8d15b3 by @jam6099 in #2224
- DAH-4529 - [P4] Executor: update a bundled binary by @surcyf123 in #2021
Full Changelog: executor-v1.181...executor-v1.182
CVM attestation
- Approved executor-runner digest (
EXECUTOR_RUNNER_IMAGE_DIGESTin.env):sha256:f8421a1d93c62029326e86bbd5ad5192c480477c68e87811fe4084bd499c854c(the runner image pushed 2026-10-26; the approved digest does not change per release, so this digest is older than the release and still the approved one) - Expected compose hash of a CVM created from this release:
0cc30085543511090db2952809f104dd30ec7d8630abb9fc4cde8590068ec104
Check after sudo ./lium-cvm.sh new <name> and before run:
sha256sum run/vms/<name>/shared/app-compose.jsonFrom the checkout, python3 scripts/compose_hash.py --check run/vms/<name>/shared/app-compose.json does the comparison and exits 1 on a mismatch.
The output must equal the expected compose hash. Any other value means the measured files or the digest differ from the release, and the validator does not know the hash. What that costs depends on the validator's whitelist enforcement (ENABLE_ATTESTATION_WHITELIST): with it on, the validator rejects the CVM and it scores zero; with it off (the default), the validator accepts the unknown hash and scores the node as before. Do not run a CVM that does not match the release either way. Under enforcement a matching value scores only once the validator release that whitelists this hash is deployed; until then a correct CVM scores zero as well.