Skip to content

contracts/build.sh — missing verification that WASM hash matches after build #277

Description

@Nabeelahh
  • Area: Smart Contract
  • 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.
  • File(s): contracts/build.sh, scripts/generate-wasm-hash.sh
  • Priority: Medium
  • 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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions