runtimeverification / kasmer-multiversx

Wasm semantics for the Elrond/MultiversX blockchain network
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Config format with multicontract support and directory paths #163

Closed bbyalcinkaya closed 2 months ago

bbyalcinkaya commented 2 months ago

Input contracts can be specified in 2 ways:

  1. Directory path
    • Doesn't support multi-contracts. Expects exactly 1 wasm file in ./output.
    • Wasm file is resolved to <contract_dir>/output/*.wasm
  2. Dictionary
    • Supports multi-contracts
    • "name" is optional.

Examples:

{
  "contracts": [
    "../../../deps/mx-sdk-rs/contracts/examples/adder",
    {
      "path": "../../../deps/mx-sdk-rs/contracts/examples/adder"
    },
    {
      "path": "../../../deps/mx-sdk-rs/contracts/examples/multisig",
      "name": "multisig-full"
    }
  ]
}

The first two are identical.

Issue: #128