Repository navigation
V7.4 Release bundle install
- Install without a source checkout. Each release now has
iotube-witness-X.Y.Z.tar.gzand its.sha256, attached by CI. The bundle holds a docker compose file (one container per route, chosen withCOMPOSE_PROFILES),.env.examplepinned 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
.envand the database. Then add any new settings, setWITNESS_TAG, and rundocker compose up -d --force-recreate. - BSC witness config:
interval: 15s,batchSize: 2000. BSC blocks are about 0.45s now, so the previous10s/10fell behind the chain. Existingstart_witness.shinstalls still on10s/10must set these two values in their deployedwitness-config-bsc-payload.yamland recreate the BSC witness, becauseupgrade.shdoes 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.shkeeps 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_getLogsresult 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