v2.12.0
Added
-
Added a mechanism to validate forwarders for OCR2 and fallback to EOA if necessary
-
Added a new CLI command,
blocks find-lca,
which finds the latest block that is available in both the database and on the chain for the specified chain. Added a new CLI command,node remove-blocks,
which removes all blocks and logs greater than or equal to the specified block number. -
Re-enable abandoned transaction tracker
-
Enable configurable client error regexes for error classification. New toml configuration options for [EVM.NodePool.Errors] to pass regexes on NonceTooLow, NonceTooHigh, ReplacementTransactionUnderpriced, LimitReached, TransactionAlreadyInMempool, TerminallyUnderpriced, InsufficientEth, TxFeeExceedsCap, L2FeeTooLow, L2FeeTooHigh, L2Full, TransactionAlreadyMined, Fatal, and ServiceUnavailable.
-
Validate user email before asking for a password in the chainlink CLI.
-
Add configurability to mercury transmitter
[Mercury.Transmitter] TransmitQueueMaxSize = 10_000 # Default TransmitTimeout = "5s" # Default
Updated
- core/chains/evm/logpoller: Stricter finality checks in LogPoller, to be more robust during rpc failover events
- Reducing the scope of 0233 migration to include only 5th word index which is required for CCIP
- Fixed CPU usage issues caused by inefficiencies in HeadTracker. HeadTracker's support of finality tags caused a drastic increase in the number of tracked blocks on the Arbitrum chain (from 50 to 12,000), which has led to a 30% increase in CPU usage. The fix improves the data structure for tracking blocks and makes lookup more efficient. BenchmarkHeadTracker_Backfill shows 40x time reduction.
- Validate support for postgresql-client 16, and update docker image's bundled postgresql-client from 15 to 16.
Upcoming change in 2.13.0
- The
xdai
ChainType
has been renamed tognosis
to match the chain's new name. The old value is still supported but has been deprecated and will be removed in v2.13.0.