Repository navigation
v2.7.0
Added
- Added new configuration field named
LeaseDurationforEVM.NodePoolthat will periodically check if internal subscriptions are connected to the "best" (as defined by theSelectionMode) node and switch to it if necessary. Setting this value to0swill disable this feature. - Added multichain telemetry support. Each network/chainID pair must be configured using the new fields:
[[TelemetryIngress.Endpoints]]
Network = '...' # e.g. EVM. Solana, Starknet, Cosmos
ChainID = '...' # e.g. 1, 5, devnet, mainnet-beta
URL = '...'
ServerPubKey = '...'These will eventually replace TelemetryIngress.URL and TelemetryIngress.ServerPubKey. Setting TelemetryIngress.URL and TelemetryIngress.ServerPubKey alongside [[TelemetryIngress.Endpoints]] will prevent the node from booting. Only one way of configuring telemetry endpoints is supported.
-
Added bridge_name label to
pipeline_tasks_total_finishedprometheus metric. This should make it easier to see directly what bridge was failing out from the CL NODE perspective. -
LogPoller will now use finality tags to dynamically determine finality on evm chains if
UseFinalityTags=true, rather than the fixedFinalityDepthspecified in toml config
Changed
P2P.V1is now disabled (Enabled = false) by default. It must be explicitly enabled withtrueto be used. However, it is deprecated and will be removed in the future.P2P.V2is now enabled (Enabled = true) by default.
Upcoming Required Configuration Changes
Starting in v2.9.0:
TelemetryIngress.URLandTelemetryIngress.ServerPubKeywill no longer be allowed. Any TOML configuration that sets this fields will prevent the node from booting. These fields will be replaced by[[TelemetryIngress.Endpoints]]P2P.V1will no longer be supported and must not be set in TOML configuration in order to boot. UseP2P.V2instead. If you are using both,V1can simply be removed.
Removed
- Removed the ability to set a next nonce value for an address through CLI