You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: build.sh compiles contracts but does not call generate-wasm-hash.sh or compare the resulting hash against a known-good value. A supply-chain attack or accidental dependency change would produce a different WASM silently. Integrate hash verification into the build script.
Implementation & verification: Treat this as a protocol-safety change: check authorization, storage/ABI compatibility, ledger-time behavior, and emitted events before changing the implementation. Add a contract-level regression test for both the invalid and successful paths.
**Required change set *: Change the relevant contract implementation together with its focused contract test, and include a type, error, or deployment-script adjustment only when required.
build.shcompiles contracts but does not callgenerate-wasm-hash.shor compare the resulting hash against a known-good value. A supply-chain attack or accidental dependency change would produce a different WASM silently. Integrate hash verification into the build script.contracts/build.sh,scripts/generate-wasm-hash.sh