Skip to content

v7.4.0

Latest

Choose a tag to compare

@guo guo released this 13 Nov 19:41
90e548a

V7.4 Release bundle install

  • Install without a source checkout. Each release now has iotube-witness-X.Y.Z.tar.gz and its .sha256, attached by CI. The bundle holds a docker compose file (one container per route, chosen with COMPOSE_PROFILES), .env.example pinned to the release, and the per-route configs. Operators edit only .env. See "Install" in witness-service/README.md.
  • Upgrades unpack the new bundle over the install, which keeps .env and the database. Then add any new settings, set WITNESS_TAG, and run docker compose up -d --force-recreate.
  • BSC witness config: interval: 15s, batchSize: 2000. BSC blocks are about 0.45s now, so the previous 10s / 10 fell behind the chain. Existing start_witness.sh installs still on 10s / 10 must set these two values in their deployed witness-config-bsc-payload.yaml and recreate the BSC witness, because upgrade.sh does not copy configs.
  • Signing key required with the bundle. A witness started from the bundle without a signing key now stops at startup instead of running without signing (WITNESS_REQUIRE_SIGNER).
  • start_witness.sh keeps working. The README describes moving an existing install to the bundle.
  • BSC RPC: use a provider with enough log history. Some public endpoints return an empty eth_getLogs result for older blocks instead of an error.
  • The relayer is unchanged from v7.3.

Images: ghcr.io/iotubeproject/iotube-witness:7.4.0, ghcr.io/iotubeproject/iotube-relayer:7.4.0