Node Versions and Upgrades

You can find a list of release notes for Chainlink nodes in the smartcontractkit GitHub repository. Docker images are available in the Chainlink Docker hub.

Changes in v1.10.0 nodes

v1.10.0 release notes

Added

Changed

  • The default maximum gas price on most networks is now effectively unlimited.
  • If the EVMChainID is not set explicitly in the job spec for a new OCR job, the field is now automatically added with a default chain ID.
    • Old OCR jobs missing EVMChainID continue to run on any chain that the ETH_CHAIN_ID variable is set to (or the first chain if it is not set). This can be changed after a restart.
    • Newly created OCR jobs run only on a single fixed chain and are unaffected by changes to ETH_CHAIN_ID after the job is added.
    • It should no longer be possible to end up with multiple OCR jobs for a single contract running on the same chain. Only one job per contract per chain is allowed.
    • If there are any existing duplicate jobs per contract and per chain, all but the jobs with the latest creation date will be pruned during the upgrade.

Fixed

  • Fixed minor bug where Chainlink would attempt and fail to estimate a tip cap higher than the maximum configured gas price in EIP1559 mode. It now caps the tipcap to the max instead of erroring.
  • Fixed a bug where it was impossible to remove ETH keys that had extant transactions. Now, removing an ETH key will drop all associated data automatically, including past transactions.

Automatic connectivity detection

Chainlink will no longer bump excessively if the network is broken.

This feature only applies on EVM chains when using BlockHistoryEstimator (the most common case). Chainlink will now try to automatically detect if there is a transaction propagation/connectivity issue and prevent bumping in these cases. This can help avoid the situation where RPC nodes are not propagating transactions for some reason (e.g., go-ethereum bug, networking issue …etc) and Chainlink responds in a suboptimal way by bumping transactions to a very high price in an effort to get them mined. This can lead to unnecessary expense when the connectivity issue is resolved and the transactions are finally propagated into the mempool.

This feature is enabled by default with fairly conservative settings: if a transaction has been priced above the 90th percentile of the past 12 blocks, but still wants to bump due to not being mined, a connectivity/propagation issue is assumed and all further bumping will be prevented for this transaction. In this situation, Chainlink will start firing the block_history_estimator_connectivity_failure_count prometheus counter and logging at critical level until the transaction is mined.

The default settings should work fine for most users. For advanced users, the values can be tweaked by changing BLOCK_HISTORY_ESTIMATOR_CHECK_INCLUSION_BLOCKS and BLOCK_HISTORY_ESTIMATOR_CHECK_INCLUSION_PERCENTILE.

To disable connectivity checking completely, set BLOCK_HISTORY_ESTIMATOR_CHECK_INCLUSION_BLOCKS=0.

Changes in v1.9.0 nodes

v1.9.0 release notes

  • Added the length task and the lessthan task for jobs.
  • Added the gasUnlimited parameter to the ethcall task.
  • The Keys page in Operator UI includes several admin commands that were previously available only by using the keys eth chain commands:
    • Ability to abandon all current transactions: This is the same as the abandon CLI command. Previously it was necessary to edit the database directly to abandon transactions. This command makes it easier to resolve issues that require transactions to be abandoned.
    • Ability to enable/disable a key for a specific chain: This allows you to control keys on a per-chain basis.
    • Ability to manually set the nonce for a key. This gives you a way to set the next nonce for a specific key in the UI, which can be useful for debugging.

Changes in v1.8.1 nodes

v1.8.1 release notes

  • Added several improvements for Arbitrum Nitro including a multi-dimensional gas model, with dynamic gas pricing and limits.
    • The new default estimator for Arbitrum networks uses the suggested gas price up to ETH_MAX_GAS_PRICE_WEI with a 1000 gwei default value and an estimated gas limit up to ETH_GAS_LIMIT_MAX with a 1,000,000,000 default.
    • Remove the GAS_ESTIMATOR_MODE environment variable to use the new defaults.
  • ETH_GAS_LIMIT_MAX to puts a maximum on the gas limit returned by the Arbitrum estimator.

Changes in v1.8.0 nodes

v1.8.0 release notes

Added

  • Added the hexencode and base64encode tasks (pipeline). See the Hex Encode Task and Base64 Encode Task pages for examples.
  • forwardingAllowed per job attribute to allow forwarding txs submitted by the job.
  • Added Arbitrum Goerli configuration support.
  • Added the NODE_SELECTION_MODE (EVM.NodePool.SelectionMode) environment variable, which controls node picking strategy. Supported values are:
    • HighestHead is the default mode, which picks a node that has the highest reported head number among other alive nodes. When several nodes have the same latest head number, the strategy sticks to the last used node. This mode requires NODE_NO_NEW_HEADS_THRESHOLD to be configured, otherwise it will always use the first alive node.
    • RoundRobin mode iterates among available alive nodes. This was the default behavior prior to this release.
  • New evm keys chain command. This can also be accessed at /v2/keys/evm/chain. This command has the following uses:
    • Manually set or reset a nonce: chainlink evm keys chain --address "0xEXAMPLE" --evmChainID 99 --setNextNonce 42
    • Enable a key for a particular chain: chainlink evm keys chain --address "0xEXAMPLE" --evmChainID 99 --setEnabled true
    • Disable a key for a particular chain: chainlink evm keys chain --address "0xEXAMPLE" --evmChainID 99 --setEnabled false
  • It is now possible to use the same key across multiple chains.

Changed

  • The chainlink admin users update command is replaced with chainlink admin users chrole. Only the role can be changed for a user.
  • Keypath now supports paths with any depth, instead of limiting it to 2.
  • Arbitrum chains are no longer restricted to only FixedPrice GAS_ESTIMATOR_MODE.
  • Updated Arbitrum Rinkeby & Mainnet configurations for Nitro.

Removed

  • The setnextnonce local client command is removed and is replaced by the more general evm keys chain command client command.

Changes in v1.7.1 nodes

v1.7.1 release notes

Fixed

  • Arbitrum Nitro client error support

Changes in v1.7.0 nodes

v1.7.0 release notes

Added

  • p2pv2Bootstrappers is added as a new optional property of OCR1 job specs. The default can still be specified with the P2PV2_BOOTSTRAPPERS environment variable.

  • Added official support for the Sepolia testnet on Chainlink nodes.

  • Added hexdecode task and the base64decode task (pipeline).

  • Added support for the Besu execution client. Although Chainlink supports Besu, Besu itself has several issues that can make it unreliable. For additional context, see the following issues:

  • Added Multi-user and Role Based Access Control functionality. This allows the root admin CLI user and additional admin users to create and assign tiers of role-based access to new users. These new API users are able to log in to the Operator UI independently and can each have specific roles tied to their account. There are four roles: admin, edit, run, and view.

    • User management can be configured through the use of the new admin CLI command chainlink admin users. Be sure to run chainlink admin login. For example, a readonly user can be created with: chainlink admin users create [email protected] --role=view.
    • Updated documentation repo with a break down of actions to required role level
  • Added gas limit control for individual job specs and individual job types. The following rule of precedence is applied:

    1. The task-specific parameter gasLimit overrides anything else when specified. For example, the ethtx task has a gasLimit parameter that overrides the other defaults for this specific task.

    2. The job-spec attribute gasLimit applies only to a specific job spec.

    3. The job-type limits affect any jobs of the corresponding type. The following environment variables are available:

    4. The global ETH_GAS_LIMIT_DEFAULT (EVM.GasEstimator.LimitDefault) value is used only when the preceding rules are not set.

Fixed

  • Addressed a very rare bug where using multiple nodes with differently configured RPC tx fee caps could cause missed transactions. Ensure that your RPC nodes have no caps. For more information, see the performance and tuning guide.
  • Improved handling of unknown transaction error types to make Chainlink more robust in certain cases on unsupported chains or RPC clients.

Changes in v1.6.0 nodes

v1.6.0 release notes

  • Simplified password complexity requirements. All passwords used with Chainlink must meet the following requirements:
    • Must be 16 characters or more
    • Must not contain leading or trailing whitespace
    • User passwords must not contain the user’s API email
  • Simplified the Keepers job spec by removing the observation source from the required parameters.

Changes in v1.5.0 nodes

v1.5.0 release notes

  • Chainlink will not boot if the Postgres database password is missing or insecure. Passwords must conform to the following rules:

    • Must be longer than 12 characters
    • Must comprise at least 3 of the following items:
      • 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, you can bypass this check at your own risk by setting SKIP_DATABASE_PASSWORD_COMPLEXITY_CHECK=true.

  • The following environment variables are deprecated and will be removed in a future release. They are are replaced by the following command line arguments:

    • INSECURE_SKIP_VERIFY: Replaced by the --insecure-skip-verify CLI argument
    • CLIENT_NODE_URL: Replaced by the --remote-node-url URL CLI argument
    • ADMIN_CREDENTIALS_FILE: Replaced by the --admin-credentials-file FILE CLI argument

    Run ./chainlink --help to learn more about these CLI arguments.

  • The Optimism2 GAS_ESTIMATOR_MODE has been renamed to L2Suggested. The old name is still supported for now.

  • The p2pBootstrapPeers property on OCR2 job specs has been renamed to p2pv2Bootstrappers.

Added

  • Added the ETH_USE_FORWARDERS config option to enable transactions forwarding contracts.

  • In the directrequest job pipeline, three new block variables are available:

    • $(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)
  • ethtx tasks can now be configured to error if the transaction reverts on-chain. You must set failOnRevert=true on the task to enable this behavior:

    foo [type=ethtx failOnRevert=true ...]

    The 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.
    • If minConfirmations is not set on the task, the chain default will be used which is usually 12 and always greater than 0.
  • http task now allows specification of request headers. Use it like the following example:

    foo [type=http headers="[\\"X-Header-1\\", \\"value1\\", \\"X-Header-2\\", \\"value2\\"]"].

Fixed

  • Fixed max_unconfirmed_age metric. 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 the Metis internal fee change.

Removed

  • The Optimism OVM 1.0 GAS_ESTIMATOR_MODE has been removed and the Optimism2 GAS_ESTIMATOR_MODE has been renamed to L2Suggested.

  • MIN_OUTGOING_CONFIRMATIONS has been removed and no longer has any effect. The ETH_FINALITY_DEPTH environment variable is now used as the default for ethtx confirmations instead. You can override this on a per-task basis by setting minConfirmations in the task definition. For example, foo [type=ethtx minConfirmations=42 ...].

    This setting might have a minor impact on performance for very high throughput chains. If you don’t care about reporting task status in the UI, set minConfirmations=0 in your job specs. For more details, see the Optimizing EVM Performance page.

Changes in v1.4.1 nodes

v1.4.1 release notes

  • Added a fix to ensure that a failed EthSubscribe does not register (*rpc.ClientSubscription)(nil), which leads to a panic when unsubscribing.
  • Fix parsing of float values on job specs.

Changes in v1.4.0 nodes

v1.4.0 release notes

  • JSON parse tasks in TOML now support a custom separator parameter to substitute for the default ,.
  • Slow SQL queries are now logged.
  • Updated the block explorer URLs to include FTMScan and SnowTrace.
  • Keeper upkeep order can now be shuffled. See KEEPER_TURN_FLAG_ENABLED for details.
  • Several fixes. See the release notes for a full list of changes.

Changes in v1.3.0 nodes

v1.3.0 release notes

  • Added disk rotating logs. See the Node Logging and LOG_FILE_MAX_SIZE documentation for details.
  • Added support for the force flag on the chainlink blocks replay CLI command. If set to true, already consumed logs that would otherwise be skipped will be rebroadcasted.
  • Added a version compatibility check when using the CLI to login to a remote node. The bypass-version-check flag skips this check.
  • Changed default locking mode to “dual”. See the DATABASE_LOCKING_MODE documentation for details.
  • Specifying multiple EVM RPC nodes with the same URL is no longer supported. If you see ERROR 0106_evm_node_uniqueness.sql: failed to run SQL migration, you have multiple nodes specified with the same URL and you must fix this before proceeding with the upgrade.
  • EIP-1559 is now enabled by default on the Ethereum Mainnet. See the EVM_EIP1559_DYNAMIC_FEES documentation for details.
  • Added new Chainlink Automation feature that includes gas price in calls to checkUpkeep(). To enable the feature, set KEEPER_CHECK_UPKEEP_GAS_PRICE_FEATURE_ENABLED to true. Use this setting only on Polygon networks.

Changes in v1.2.0 nodes

v1.2.0 release notes

Significant changes:

  • Added support for the Nethermind Ethereum client.
  • Added support for batch sending telemetry to the ingress server to improve performance.
  • New environment variables: See the release notes for details.
  • Removed the deleteuser CLI command.
  • Removed the LOG_TO_DISK environment variable.

See the v1.2.0 release notes for a complete list of changes and fixes.

Changes in v1.1.0 nodes

v1.1.0 release notes

The v1.1.0 release includes several substantial changes to the way you configure and operate Chainlink nodes:

  • Legacy environment variables: Legacy environment variables are supported, but they might be removed in future node versions. See the Configuring Chainlink Nodes page to learn how to migrate your nodes away from legacy environment variables and use the API, CLI, or GUI exclusively to administer chains and nodes.
  • Full EIP1559 Support: Chainlink nodes include experimental support for submitting transactions using type 0x2 (EIP-1559) envelope. EIP-1559 mode is off by default, but can be enabled either globally or on a per-chain basis.
  • New log level added:
    • [crit]: Critical level logs are more severe than [error] and require quick action from the node operator.
  • Multichain support (Beta): Chainlink now supports connecting to multiple different EVM chains simultaneously. This is disabled by default. See the v1.1.0 Changelog for details.

With multliple chain support, eth node configuration is stored in the database.

The following environment variables are DEPRECATED:

  • ETH_URL
  • ETH_HTTP_URL
  • ETH_SECONDARY_URLS

Setting ETH_URL will cause Chainlink to automatically overwrite the database records with the given ENV values every time Chainlink boots. This behavior is used mainly to ease the process of upgrading from older versions, and on subsequent runs (once your old settings have been written to the database) it is recommended to unset these ENV vars and use the API commands exclusively to administer chains and nodes.

If you wish to continue using these environment variables (as it used to work in 1.0.0 and below) you must ensure that the following are set:

  • ETH_CHAIN_ID (mandatory)
  • ETH_URL (mandatory)
  • ETH_HTTP_URL (optional)
  • ETH_SECONDARY_URLS (optional)

If, instead, you wish to use the API/CLI/GUI to configure your chains and eth nodes (recommended) you must REMOVE the following environment variables:

  • ETH_URL
  • ETH_HTTP_URL
  • ETH_SECONDARY_URLS

This will cause Chainlink to use the database for its node configuration.

NOTE: ETH_CHAIN_ID does not need to be removed, since it now performs the additional duty of specifying the default chain in a multichain environment (if you leave ETH_CHAIN_ID unset, the default chain is simply the “first”).

For more information on configuring your node, check the configuration variables in the docs.

Before you upgrade your nodes to v1.1.0, be aware of the following requirements:

  • If you are upgrading from a previous version, you MUST first upgrade the node to at least v0.10.15.
  • Always take a Database snapshot before you upgrade your Chainlink nodes. You must be able to roll the node back to a previous version in the event of an upgrade failure.

See the v1.1.0 release notes for a complete list of changes and fixes.

Changes in v1.0.0 and v1.0.1 nodes

v1.0.0 release notes v1.0.1 release notes

Before you upgrade your nodes to v1.0.0 or v1.0.1, be aware of the following requirements:

  • If you are upgrading from a previous version, you MUST first upgrade the node to at least v0.10.15.
  • Always take a Database snapshot before you upgrade your Chainlink nodes. You must be able to roll the node back to a previous version in the event of an upgrade failure.

Whats Next

Stay updated on the latest Chainlink news