v0.8.16

Added

• The chainlink node now will bump a limited configurable number of transactions at once. This is configured with the ETH_GAS_BUMP_TX_DEPTH variable which is 10 by default. Set to 0 to disable (the old behaviour).

Fixed

• ETH_DISABLED flag works again

v0.8.15

Added

• Chainlink header images to the following README.md files: root, core,
  evm-contracts, and evm-test-helpers.
• Database migrations: new log_consumptions records will contain the number of the associated block.
  This migration will allow future version of chainlink to automatically clean up unneeded log_consumption records.
  This migration should execute very fast.

Fixed

Previously when the node was overloaded with heads there was a minor possibility it could get backed up with a very large head queue, and become unstable. Now, we drop heads instead in this case and noisily emit an error. This means the node should more gracefully handle overload conditions, although this is still dangerous and node operators should deal with it immediately to avoid missing jobs.

A new environment variable is introduced to configure this, called ETH_HEAD_TRACKER_MAX_BUFFER_SIZE. It is recommended to leave this set to the default of "3".

A new prometheus metric is also introduced to track dropped heads, called head_tracker_num_heads_dropped. You may wish to set an alert on a rule such as increase(chainlink_dropped_heads[5m]) > 0.

v0.8.14

Changed

• Fix for gas bumper
• Fix for broadcast-transactions function

v0.8.13

Changed

Performance improvements when using BulletproofTxManager.

explorer-v0.8.5

Merge pull request #3283 from smartcontractkit/release/explorer-0.8.5

Release/explorer 0.8.5

v0.8.12

Changed

Default max gas increased to 5000 Gwei

Fixed

Added a workaround for Infura users who are seeing "error getting balance: header not found".

This behaviour is due to Infura announcing it has a block, but when we request our balance in this block, the eth node doesn't have the block in memory. The workaround is to add a configurable lag time on balance update requests. The default is set to 1 but this is configurable via a new environment variable ETH_BALANCE_MONITOR_BLOCK_DELAY.

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