v0.8.11

Added

• Job specs now support pinning to multiple keys using the new fromAddresses field in the ethtx task spec.

Changed

• Using fromAddress in ethtx task specs has been deprecated. Please use fromAddresses instead.

Breaking changes

• Support for RunLogTopic0original and RunLogTopic20190123withFullfillmentParams logs has been dropped. This should not affect any users since these logs predate Chainlink's mainnet launch and have never been used on mainnet.

IMPORTANT: The selection mechanism for keys has changed. When an ethtx task spec is not pinned to a particular key by defining fromAddress or fromAddresses, the node will now cycle through all available keys in round robin fashion. This is a change from the previous behaviour where nodes would only pick the earliest created key.

This is done to allow increases in throughput when a node operator has multiple whitelisted addresses for their oracle.

If your node has multiple keys, you will need to take one of the three following actions:

1. Make sure all keys are valid for all job specs
2. Pin job specs to a valid subset of key(s) using fromAddresses
3. Delete the key(s) you don't want to use

If your node only has one key, no action is required.

explorer-v0.8.4

Merge pull request #2926 from smartcontractkit/release/explorer-0.8.4

Release/explorer 0.8.4

v0.8.10

Fixed

• Incorrect sequence on keys table in some edge cases

v0.8.9

Added

• Added a check on sensitive file ownership that gives a warning if certain files are not owned by the user running chainlink
• Added mechanism to asynchronously communicate when a job spec has an ethereum interaction error (or any async error) with a UI screen
• Gas Bumper now bumps based on the current gas price instead of the gas price of the original transaction

Fixed

• Support for multiple node addresses

v0.8.8

Added

• ethtx tasks now support a new parameter, minRequiredOutgoingConfirmations which allows you to tune how many confirmations are required before moving on from an ethtx task on a per task basis (only works with BulletproofTxManager). If it is not supplied, the default of MIN_OUTGOING_CONFIRMATIONS is used (same as the old behaviour).

Changed

• HeadTracker now automatically backfills missing heads up to ETH_FINALITY_DEPTH

Breaking changes

• admin withdraw command has been removed. This was only ever useful to withdraw LINK if the Oracle contract was owned by the Chainlink node address. It is no longer recommended to have the Oracle owner be the chainlink node address.
• Fixed txs create to send the amount in Eth not in Wei (as per the documentation)

v0.8.7

Added

This release contains a number of features aimed at improving the node's reliability when putting transactions on-chain.

• An experimental new transaction manager is introduced that delivers reliability improvements compared to the old one, especially when faced with difficult network conditions or spiking gas prices. It also reduces load on the database and makes fewer calls to the eth node compared to the old tx manager.
• Along with the new transaction manager is a local client command for manually controlling the node nonce - setnextnonce. This should never be necessary under normal operation and is included only for use in emergencies.
• ethtx tasks now support two new parameters (only available with BulletproofTxManager):
  • minRequiredOutgoingConfirmations - allows you to tune how many confirmations are required before moving on from an ethtx task on a per task basis. If not supplied, the default of MIN_OUTGOING_CONFIRMATIONS is used (same as the old behaviour).
  • fromAddress - enables multikey support by allowing you to peg a job spec to a particular ethereum address.
• New prometheus metrics for the head tracker:
  • head_tracker_heads_in_queue - The number of heads currently waiting to be executed. You can think of this as the 'load' on the head tracker. Should rarely or never be more than 0.
  • head_tracker_callback_execution_duration - How long it took to execute all callbacks. If the average of this exceeds the time between blocks, your node could lag behind and delay transactions.

Env var changes

• ENABLE_BULLETPROOF_TX_MANAGER - Experimental feature for transaction manager, do not enable!
• ETH_GAS_BUMP_PERCENT default value has been increased from 10% to 20%
• ETH_GAS_BUMP_THRESHOLD default value has been decreased from 12 to 3
• ETH_FINALITY_DEPTH specifies how deep protection should be against re-orgs. The default is 50. It only applies if BulletproofTxManager is enabled. It is not recommended to change this setting.
• ETH_HEAD_TRACKER_HISTORY_DEPTH specifies how many heads the head tracker should keep in the database. The default is 100. It is not recommended to change this setting.

v0.8.6

Added

• The node now logs the eth client RPC calls
• More reliable Ethereum block header tracking
• Limit the amount of an HTTP response body that the node will read
• Make Aggregator contract interface viewable
• More resilient handling of chain reorganizations

v0.8.5

Added

• The chainlink node can now be configured to backfill logs from n blocks after a connection to the ethereum client is reset. This value is specified with an environment variable BLOCK_BACKFILL_DEPTH.
• The chainlink node now sets file permissions on sensitive files on startup (tls, .api, .env, .password and secret)

Changed

• Solidity: Renamed the previous AggregatorInterface.sol to HistoricAggregatorInterface.sol. Users are encouraged to use the new methods introduced on the AggregatorInterface(getRoundData and latestRoundData), as they return metadata to indicate freshness of the data in a single cross-contract call.
• Solidity: Marked HistoricAggregatorInterface methods (latestAnswer, latestRound, latestTimestamp, getAnswer, getTimestamp) as deprecated on FluxAggregator, WhitelistedAggregator, AggregatorProxy, WhitelistedAggregatorProxy.

Fixed

• Fluxmonitor jobs now respect the minPayment field on job specs and won't poll if the contract does not have sufficient funding. This allows certain jobs to require a larger payment than MINIMUM_CONTRACT_PAYMENT.

v0.8.4

Breaking changes

None

Features

• Fluxmonitor initiators may now optionally include an absoluteThreshold parameter. To trigger a new on-chain report, the absolute difference in the feed value must change by at least the absoluteThreshold value. If it is unspecified or zero, fluxmonitor behavior is unchanged.

Bugfixes

• Fix incorrect permissions on some files written by the node
• Prevent a case where duplicate ethereum keys could be added
• Improve robustness and reliability of ethtx transaction logic

Database Migrations

• Add created_at and updated_at to all tables allowing for better historical insights. This migration may take a minute or two on large databases.

v0.8.3

Breaking changes

New cron jobs MUST now include time zone. For example if you want your jobs to run in UTC:
CRON_TZ=UTC * * * * *.

A full list can be found here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones. You need to specify the TZ Database name.

Previously, jobs specified without a time zone would run in the server's native time zone, which in most cases is UTC but this was never guaranteed. This behaviour is now disabled for new jobs, because it is ambiguous.

Old jobs will continue to run AS IS and run on the servers timezone.

Bugfixes

• Fix crash in experimental gas updater when run on Kovan network

Database Migrations

There a number of database migrations included in this release as part of our ongoing effort to make the node even more reliable and stable, and build a firm foundation for future development.

If you have made custom edits to your database, the migration might fail. If this happens you will need to fix the offending data manually and run the migration again.

If you have very large tables, these migrations may take several minutes.