github forta-network/forta-node v0.8.4

latest releases: v0.9.10, v0.9.9, v0.9.8...
16 months ago

Shard ID fixes

We noticed a problem about some shard IDs failing to calculate using free APIs (polygon-rpc.com) and optimized the assignment list loading using our go-multicall library. This also helps reducing the load on the registry APIs and increases the general consistency.

Another problem that is fixed along with this release is the mixup in the shard ID that appears in the metrics. This helps avoid confusion while monitoring how the network operates bot shards.

New forta status all subcommand

Now instead of using forta status --show all --format oneline, operators can simply use forta status all!

More metrics

We added more metrics to increase visibility in the issues:

  • Errors during loading assigned bots
  • Bot alert processing response validation errors

Reduced docker pull concurrency

To remedy the pull retry issues visible in some nodes, we have reduced the concurrency to pull one image at a time and increased the timeout from 5 minutes to 10 minutes. This will help speed up the eventual start of bots.

Local mode improvements

  • Fixed standalone mode which was broken starting with v0.8.0
  • Fixed the zero block error which happens when working with Hardhat
  • Disabled the trace requirement for all chains

Other improvements

  • Fixed bot attachment bug that happens during graceful auto-upgrades
  • Started the JSON-RPC API health checker
  • Pinned docker/docker (moby/moby) version to the minimum requirement v20.10.x after dependency update issues
  • Reduced test coverage fluctuation between test runs (due to concurrent parts)

What's Changed

Full Changelog: v0.8.3...v0.8.4

Don't miss a new forta-node release

NewReleases is sending notifications on new releases.