BLOCK_HISTORY_ESTIMATOR_EIP1559_FEE_CAP_BUFFER_BLOCKS - if EIP1559 mode is enabled, this optional env var controls the buffer blocks to add to the current base fee when sending a transaction. By default, the gas bumping threshold + 1 block is used. It is not recommended to change this unless you know what you are doing.
EVM_GAS_FEE_CAP_DEFAULT - if EIP1559 mode is enabled, and FixedPrice gas estimator is used, this env var controls the fixed initial fee cap.
Fixed
Fixed issues with EIP-1559 related to gas bumping. Due to go-ethereum's implementation which introduces additional restrictions on top of the EIP-1559 spec, we must bump the FeeCap at least 10% each time in order for the gas bump to be accepted.
The new EIP-1559 implementation works as follows:
If you are using FixedPriceEstimator:
With gas bumping disabled, it will submit all transactions with feecap=ETH_MAX_GAS_PRICE_WEI and tipcap=EVM_GAS_TIP_CAP_DEFAULT
With gas bumping enabled, it will submit all transactions initially with feecap=EVM_GAS_FEE_CAP_DEFAULT and tipcap=EVM_GAS_TIP_CAP_DEFAULT.
If you are using BlockHistoryEstimator (default for most chains):
With gas bumping disabled, it will submit all transactions with feecap=ETH_MAX_GAS_PRICE_WEI and tipcap=<calculated using past blocks>
With gas bumping enabled (default for most chains) it will submit all transactions initially with feecap=current block base fee * (1.125 ^ N) where N is configurable by setting BLOCK_HISTORY_ESTIMATOR_EIP1559_FEE_CAP_BUFFER_BLOCKS but defaults to gas bump threshold+1 and tipcap=<calculated using past blocks>
Added support for Sentry error reporting. Set SENTRY_DSN at compile- or run-time to enable reporting.
Added Prometheus counters: log_warn_count, log_error_count, log_critical_count, log_panic_count and log_fatal_count representing the corresponding number of warning/error/critical/panic/fatal messages in the log.
The new prometheus metric tx_manager_tx_attempt_count is a Prometheus Gauge that should represent the total number of Transactions attempts that awaiting confirmation for this node.
The new prometheus metric version that displays the node software version (tag) as well as the corresponding commit hash.
CLI command keys eth list is updated to display key specific max gas prices.
CLI command keys eth create now supports optional maxGasPriceGWei parameter.
CLI command keys eth update is added to update key specific parameters like maxGasPriceGWei.
Add partial support for Moonriver chain
Two new log levels have been added.
[crit]: Critical level logs are more severe than [error] and require quick action from the node operator.
[debug] [trace]: Trace level logs contain extra [debug] information for development, and must be compiled in via -tags trace.
[Beta] Multichain support added
As a beta feature, Chainlink now supports connecting to multiple different EVM chains simultaneously.
This means that one node can run jobs on Goerli, Kovan, BSC and Mainnet (for example). Note that you can still have as many eth keys as you like, but each eth key is pegged to one chain only.
BLOCK_HISTORY_ESTIMATOR_EIP1559_FEE_CAP_BUFFER_BLOCKS - if EIP1559 mode is enabled, this optional env var controls the buffer blocks to add to the current base fee when sending a transaction. By default, the gas bumping threshold + 1 block is used. It is not recommended to change this unless you know what you are doing.
EVM_GAS_FEE_CAP_DEFAULT - if EIP1559 mode is enabled, and FixedPrice gas estimator is used, this env var controls the fixed initial fee cap.
Allow dumping pprof even when not in dev mode, useful for debugging (go to /v2/debug/pprof as a logged in user)
Fixed
Update timeout so we don’t exit early on very large log broadcaster backfills
EIP-1559 Fixes
Fixed issues with EIP-1559 related to gas bumping. Due to go-ethereum's implementation which introduces additional restrictions on top of the EIP-1559 spec, we must bump the FeeCap at least 10% each time in order for the gas bump to be accepted.
The new EIP-1559 implementation works as follows:
If you are using FixedPriceEstimator:
With gas bumping disabled, it will submit all transactions with feecap=ETH_MAX_GAS_PRICE_WEI and tipcap=EVM_GAS_TIP_CAP_DEFAULT
With gas bumping enabled, it will submit all transactions initially with feecap=EVM_GAS_FEE_CAP_DEFAULT and tipcap=EVM_GAS_TIP_CAP_DEFAULT.
If you are using BlockHistoryEstimator (default for most chains):
With gas bumping disabled, it will submit all transactions with feecap=ETH_MAX_GAS_PRICE_WEI and tipcap=<calculated using past blocks>
With gas bumping enabled (default for most chains) it will submit all transactions initially with feecap = ( current block base fee * (1.125 ^ N) + tipcap ) where N is configurable by setting BLOCK_HISTORY_ESTIMATOR_EIP1559_FEE_CAP_BUFFER_BLOCKS but defaults to gas bump threshold+1 and tipcap=<calculated using past blocks>
Added support for Sentry error reporting. Set SENTRY_DSN at run-time to enable reporting.
Added Prometheus counters: log_warn_count, log_error_count, log_critical_count, log_panic_count and log_fatal_count representing the corresponding number of warning/error/critical/panic/fatal messages in the log.
The new prometheus metric tx_manager_tx_attempt_count is a Prometheus Gauge that should represent the total number of Transactions attempts that awaiting confirmation for this node.
The new prometheus metric version that displays the node software version (tag) as well as the corresponding commit hash.
CLI command keys eth list is updated to display key specific max gas prices.
CLI command keys eth create now supports optional maxGasPriceGWei parameter.
CLI command keys eth update is added to update key specific parameters like maxGasPriceGWei.
Add partial support for Moonriver chain
For OCR jobs, databaseTimeout, observationGracePeriod and contractTransmitterTransmitTimeout can be specified to override chain-specific default values.
Two new log levels have been added.
[crit]: Critical level logs are more severe than [error] and require quick action from the node operator.
... (truncated)
Commits
11788e2 Merge pull request #6000 from smartcontractkit/release/1.1.1-rc1
0ad4543 Merge pull request #5999 from smartcontractkit/chore/changelog-1.1.1-rc1
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps @chainlink/contracts from 1.0.0 to 1.1.1.
Release notes
Sourced from
@chainlink/contracts's releases.... (truncated)
Changelog
Sourced from
@chainlink/contracts's changelog.... (truncated)
Commits
11788e2Merge pull request #6000 from smartcontractkit/release/1.1.1-rc10ad4543Merge pull request #5999 from smartcontractkit/chore/changelog-1.1.1-rc122ec1edBump version number1a13d27Update CHANGELOG release date for core v1.1.1734357dMerge pull request #5969 from smartcontractkit/chore/changelog-1.1.1b48adbfUpdate CHANGELOG for core v1.1.105e4c17Merge pull request #5963 from smartcontractkit/release/1.1.0-eip1559-testing6df243fAdd EIP-1559 notes to changelog1fa57afMerge remote-tracking branch 'origin/release/1.1.1-rc0' into release/1.1.0-ei...c1e70accore/chains/evm: broadcaster backfill from min pending block on resubscriptio...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show