- Chainlink will now fail to boot if the postgres database password is missing or too insecure. Passwords should conform to the following rules:
Must be longer than 12 characters Must comprise at least 3 of: lowercase characters uppercase characters numbers symbols Must not comprise: More than three identical consecutive characters Leading or trailing whitespace (note that a trailing newline in the password file, if present, will be ignored)
For backward compatibility all insecure passwords will continue to work, however in a future version of Chainlink insecure passwords will prevent application boot. To bypass this check at your own risk, you may set
MIN_OUTGOING_CONFIRMATIONShas been removed and no longer has any effect.
EVM_FINALITY_DEPTHis now used as the default for
ethtxconfirmations instead. You may override this on a per-task basis by setting
minConfirmationsin the task definition e.g.
foo [type=ethtx minConfirmations=42 ...]. NOTE: This may have a minor impact on performance on very high throughput chains. If you don't care about reporting task status in the UI, it is recommended to set
minConfirmations=0in your job specs. For more details, see the relevant section of the performance tuning guide.
The following ENV variables have been deprecated, and will be removed in a future release:
ADMIN_CREDENTIALS_FILE. These vars only applied to Chainlink when running in client mode and have been replaced by command line args, notably:
--admin-credentials-file FILErespectively. More information can be found by running
GAS_ESTIMATOR_MODEhas been renamed to
L2Suggested. The old name is still supported for now.
p2pBootstrapPeersproperty on OCR2 job specs has been renamed to
ETH_USE_FORWARDERSconfig option to enable transactions forwarding contracts.
- In job pipeline (direct request) the three new block variables are exposed:
$(jobRun.blockReceiptsRoot): the root of the receipts trie of the block (hash)
$(jobRun.blockTransactionsRoot): the root of the transaction trie of the block (hash)
$(jobRun.blockStateRoot): the root of the final state trie of the block (hash)
ethtxtasks can now be configured to error if the transaction reverts on-chain. You must set
failOnRevert=trueon the task to enable this behavior, like so:
foo [type=ethtx failOnRevert=true ...]
ethtx task now works as follows:
If minConfirmations == 0, task always succeeds and nil is passed as output
If minConfirmations > 0, the receipt is passed through as output
If minConfirmations > 0 and failOnRevert=true then the ethtx task will error on revert
minConfirmations is not set on the task, the chain default will be used which is usually 12 and always greater than 0.
httptask now allows specification of request headers. Use like so:
foo [type=http headers="[\\"X-Header-1\\", \\"value1\\", \\"X-Header-2\\", \\"value2\\"]"].
max_unconfirmed_agemetric. Previously this would incorrectly report the max time since the last rebroadcast, capping the upper limit to the EthResender interval. This now reports the correct value of total time elapsed since the first broadcast.
- Correctly handle the case where bumped gas would exceed the RPC node's configured maximum on Fantom (note that node operators should check their Fantom RPC node configuration and remove the fee cap if there is one)
- Fixed handling of Metis internal fee change
GAS_ESTIMATOR_MODEhas been removed.