flare-foundation/flare-systems-deployment v1.8.0

on GitHub

Mandatory upgrade. Songbird providers must run this version before reward
epoch 437, Flare providers before reward epoch 441. From that epoch on the
Relay switches to the redeployed contract.

Added

• [relay_cutover] for the system client is generated on every network from
  config/<network>/relay_cutover.json: the redeployed Relay address and the
  reward epoch it takes over, 5991 on Coston, 6047 on Coston2, 437 on Songbird
  and 441 on Flare.
• the tee-relay-client config gains [relay_cutover] with the same epoch, or
  -1 where no cutover is scheduled: the relay treats an omitted section as
  already switched.

Changed

• bumped flare-system-client to v1.2.0, ftso-scaling to v1.2.0 and
  c-chain-indexer to v2.0.2, the versions supporting the Relay switch.
• bumped fdc-client to v1.4.2, whose bundled system configs carry the same
  epochs.
• bumped tee-relay-client to v0.0.3. It requires FDC2 verifiers that answer
  with the {status, responseBody, message} envelope of go-verifier-api
  v0.1.0, whose routes also changed — re-check the verifier *_URL values in
  .env.

Upgrading

If you run the tee profile on Songbird, first upgrade your FDC2 verifiers to
go-verifier-api v0.1.0 and update the *_URL values in .env: tee-relay-client
v0.0.3 fails every verification against older verifiers.

git fetch --tags
git checkout v1.8.0
./populate_config.sh
docker compose pull
docker compose down
docker compose up -d

• ./populate_config.sh is required: the system-client and tee-relay-client
  configs gain the [relay_cutover] section.

Full Changelog: https://github.com/flare-foundation/flare-systems-deployment/blob/v1.8.0/CHANGELOG.md