search

bandprotocol / bandchain

BandChain - Decentralized Data Delivery Network
https://bandprotocol.com
Apache License 2.0
222 stars 51 forks source link

Bump github.com/ethereum/go-ethereum from 1.9.19 to 1.10.5 in /chain #3424

Closed dependabot-preview[bot] closed 3 years ago

dependabot-preview[bot] commented 3 years ago

Bumps github.com/ethereum/go-ethereum from 1.9.19 to 1.10.5.

Release notes

Sourced from github.com/ethereum/go-ethereum's releases.

Exodus Cluster (v1.10.5)

Geth v1.10.5 enables the London hard fork for the Ethereum mainnet at block [#12965000](https://github.com/ethereum/go-ethereum/issues/12965000), estimated for the 4th of August, 2021. Reiterating the London hardfork summary from our previous release (note, extended):

London Fork EIPs

  • [EIP-1559]: Fee market change for ETH 1.0 chain (#22837, #22888, #22970)
  • [EIP-3198]: BASEFEE opcode (included in EIP-1559 changes)
  • [EIP-3529]: Reduction in refunds (#22733)
  • [EIP-3541]: Reject new contracts starting with the 0xEF byte (#22809)
  • [EIP-3554]: Difficulty Bomb Delay to December 1st 2021 (#22840, #22870)

Additional notes about the London changes

  • This release contains mainnet activation block number for the London hard fork. (#23176)

  • As with all previous fork-related releases, we have added an override flag which can be used to set the activation block. This flag is temporary and will be removed some time after the fork has successfully activated on mainnet. (#22822, #22972)

  • The Geth transaction pool has been redesigned in order to handle the new fee market created by EIP-1559. Our new pool design attempts to cater to the demands of users—timely inclusion of transactions—as well as allowing efficient ordering of transactions by their effective mining reward. You can read more about how the new pool functions in the [transaction pool design document]. (#22898)

  • For miners: The transaction selection algorithm provided by Geth specifically picks transactions with the highest effective reward. If a minimum price is configured using the --miner.gasprice command-line flag, transactions providing less miner tips will not be included in blocks. (#22896, #22995)

    EIP-1559 also changes the gas limit voting system. After the London fork, the block gas amount available for transactions is adjusted based on demand. The block capacity is called the gas target, and EIP-1559 defines this target as half the gas limit.

    To ensure that the gas available for transactions is the same as before the fork, the gas limit is doubled at the fork block. If you are using the --miner.gaslimit flag to participate in voting, you need to double the value of this flag to keep voting for the same value as before. You can use the miner_setGasLimit RPC API to update the target without downtime, but be aware that this does not survive a restart. The previous --miner.gastarget flag is deprecated post London and its value will be ignored.

    Example: You are using --miner.gaslimit to vote for a limit of 20M, and the actual block gas limit is 20M. When London activates, the block gas limit will adjust to 40M, but you will still be voting it down towards to 20M if you keep using the same --miner.gaslimit setting. So at some point after the fork, you need to double your --miner.gaslimit value to ensure the gas limit stays at 40M gas.

  • For wallet providers: The default transaction price calculation algorithm for EIP-1559 (eth_maxPriorityFeePerGas) follows the old mechanism, setting the max priority fee to the effective price paid on the network minus the current base fee; and setting the max fee to the priority fee + 2x base fee. This ensures that the total price paid per gas remains the same after the London transition if no explicit user involvement has been made.

    Alternatively, Geth exposes a new eth_feeHistory(blocks, head, percentiles) API endpoint which allows the user to query recent statistical infos about the amount of tips paid to miners and fees burned by transactions. Wallets are recommended to use this endpoint to give users multiple fee options to choose from (#23033).

  • Note for JSON-RPC users: eth_sendTransaction and eth_fillTransaction will create EIP-1559 transactions by default after the fork has activated.

  • Note for users of Go/Java/ObjC contract bindings: accounts/abi/bind will create EIP-1559 transactions automatically after the fork. To take advantage of EIP-1559 in Go applications, please remember to update the go-ethereum module dependency to v1.10.4 or newer in your application's go.mod file. (#23038)

  • Note for users of ethclient: If you send transactions using the ethclient package and want to take advantage of the new fee model provided by EIP-1559, you must adapt your code to create transactions using types.NewTx(&types.DynamicFeeTx{...}). In order to know whether the fork has activated and the new transaction type can be used yet, simply check whether the BaseFee field of the latest block header is non-nil.

Other changes in this release:

  • Expose contextual infos (block/tx hash, tx index) into the transaction tracer (#23104, #23108).
  • Implement fee history API for better 1559 transaction price suggestions (#23033, #23178).
  • Implement clique_getSinger API for deriving the miner on Clique neworks (#22987).
  • Implement txpool_contentFrom API for retrieving txs of a single account (#22992).
  • Implement miner_setGasPrice API modify the mining gas limit on the fly (#23134).
  • Create new gethclient package for accessing Geth specific RPC APIs. (#22977).
  • Increase the downloader's scratch space to better saturate fast links (#23074).
  • Introduce a mechanism to deprecate config file fields without errors (#23118).
  • Remove the notions of a block hash from the state db (#23126).
  • Improve opcode tracing speed by around 80% (#23016).
  • Sanity check the length of the baseFee field (#23171).
  • Shorter shutdown time for the trie syncer (#23020).
  • Avoid some memory allocations in Clique (#23149).
  • Better build constraints for the fuzzers (#23089, #23137).
  • Alternate builders for docker images (#23069, #23078, #23082, #23083).
  • Remove make as a Dockerfile dependency (#23167).
  • Remove the deprecated LogforStorage type (#23173).

... (truncated)

Commits
  • 33ca98e params: release Geth v1.10.5, Exodus Cluster
  • 1fac96c internal/web3ext: remove unused console APIs (#23208)
  • b9e6e43 consensus/clique: implement getSigner API method (#22987)
  • c49e065 internal: get pending and queued transaction by address (#22992)
  • 846badc internal/ethapi: fix transaction APIs (#23179)
  • 8fe47b0 core/state: avoid unnecessary alloc in trie prefetcher (#23198)
  • 58b0420 Merge pull request #23183 from karalabe/cht-1.10.5
  • afd4227 params: update CHTs for the 1.10.5 release
  • 9624f92 Merge pull request #23178 from karalabe/feeapi-fixes
  • dea7155 eth/gasprice, internal/ethapi, miner: minor feehistory fixes
  • Additional commits viewable in compare view


Dependabot compatibility score

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 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
render[bot] commented 3 years ago

Your Render PR Server URL is https://d3n-scan-pr-3424.onrender.com.

Follow its progress at https://dashboard.render.com/static/srv-c3nt112p7h3lv6b3glh0.

dependabot-preview[bot] commented 3 years ago

Superseded by #3435.