Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge/foundation release/1.12 #551

Merged
merged 111 commits into from
Jul 5, 2023
Merged

Conversation

ziogaschr
Copy link
Member

@ziogaschr ziogaschr commented Jul 3, 2023

Merges ethereum/go-ethereum branch release/1.12 to core-geth master.

In this merge we had to revert the changes made upstream with regards proof-of-work removal.
Also, core-geth now defaults to use Pebble as a backend if no existing database is found (ethereum/go-ethereum#27136). If a previous LevelDB database exists Geth will keep using that, and if you must have LevelDB for some compatibility reasons, you can force it in Geth with the --db.engine=leveldb flag.

holiman and others added 30 commits April 20, 2023 20:16
…27049)

* core/types, params: add blob transaction type, RLP encoded for now

* all: integrate Cancun (and timestamp based forks) into MakeSigner

* core/types: fix 2 back-and-forth type refactors

* core: fix review comment

* core/types: swap blob tx type id to 0x03
…27136)

* cmd/utils, node: switch to Pebble as the default db if none exists

* node: fall back to LevelDB on platforms not supporting Pebble

* core/rawdb, node: default to Pebble at the node level

* cmd/geth: fix some tests explicitly using leveldb

* ethdb/pebble: allow double closes, makes tests simpler
…7147)

* all: remove notion of trusted checkpoints in the post-merge world

* light: remove unused function

* eth/ethconfig, les: remove unused config option

* les: make linter happy

---------

Co-authored-by: Gary Rong <garyrong0905@gmail.com>
* core, trie: rework trie database

* trie: fix comment
Co-authored-by: Exca-DK <dev@DESKTOP-RI45P4J.localdomain>
Co-authored-by: rjl493456442 <garyrong0905@gmail.com>
* cmd/geth: fix test to not use explicit db

* cmd/geth: remove dao-test
This is a breaking GraphQL API change. All numeric values are now encoded as
hex strings. The motivation for this change is matching JSON-RPC outputs more
closely.

Numbers in query parameters are accepted as both decimal integers and hex strings.
eth: fix crash on querying nil finalized block
* trie: add node type common package

In trie/types package, a few node wrappers are defined, which will be used
in both trie package, trie/snap package, etc. Therefore, a standalone common
package is created to put these stuffs.

* trie: rename trie/types to trie/trienode
…g tags (#27114)

Regenerate receipt json code to remove omit empty. Previously, there was a discrepancy between the generated code and the source. 

---------

Co-authored-by: lightclient@protonmail.com <lightclient@protonmail.com>
Co-authored-by: Martin Holst Swende <martin@swende.se>
* light: use atomic type

* light: use a suitable name for the stopped switch in LightChain
Makes the `geth account ... ` commands usable even if a geth-process is already executing, since the account commands do not read the chaindata, it was not required for those to use the same locking mechanism. 

---
Signed-off-by: jsvisa <delweng@gmail.com>
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: Sina Mahmoodi <itz.s1na@gmail.com>
This changes TALKREQ message processing to run the handler on separate goroutine,
instead of running on the main discv5 dispatcher goroutine. It's better this way because
it allows the handler to perform blocking actions.

I'm also adding a new method TalkRequestToID here. The method allows implementing
a request flow where one node A sends TALKREQ to another node B, and node B later
sends a TALKREQ back. With TalkRequestToID, node B does not need the ENR of A to
send its request.
Adds an optional config parameter to eth_call which allows users to override block context fields (same functionality that was added to traceCall in #24871)

---------

Co-authored-by: Martin Holst Swende <martin@swende.se>
Fixes a discrepancy between source and generated files, which was introduced when ExcessDataGas was added in ethereum/go-ethereum#27046.
* ✏️ Fix typos

* ⏪️ Revert changes

* Update internal/web3ext/web3ext.go

---------

Co-authored-by: Martin Holst Swende <martin@swende.se>
…r (#26999)

This adds logic to prepend 'M' or 'E' to Solidity identifiers when they would
otherwise violate Go identifier naming rules.

Closes #26972

---------

Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: Sina Mahmoodi <itz.s1na@gmail.com>
…sts (#27178)

* all: remove ethash pow, only retain shims needed for consensus and tests

* all: thank you linter

* all: disallow launching Geth in legacy PoW mode

* cmd/env/internal/t8ntool: remove dangling ethash flag
rpc: use atomic type
ziogaschr and others added 24 commits June 8, 2023 18:22
… trusted checkpoints in the post-merge world (#27147)"

This reverts commit 1e556d2.
…lock

The RPCMarshalBlock function returns an RPCMarshalBlockT struct in core-geth instead of map[string]interface{} that geth returns.
This affects the JSON key ordering based on:
- Maps have their keys sorted lexicographically
- Structs keys are marshalled in the order defined in the struct
This is ugly, but I don't see any other
way yet, and it doesn't seem that
different from what's going on
upstream.

1e5b446

Co-authored-by: meows <b5c6@protonmail.com>
…md/geth,cmd/utils,core/forkid,core,docs/getting-started,docs,tests/regression/shasums,tests/regression/simulated: drop kotti support
@ziogaschr ziogaschr requested a review from diega July 3, 2023 16:38
Copy link
Contributor

@diega diega left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome! let's 🚢 it

@ziogaschr ziogaschr merged commit e936c4a into master Jul 5, 2023
@ziogaschr ziogaschr deleted the merge/foundation-release/1.12 branch July 5, 2023 14:50
@ziogaschr ziogaschr mentioned this pull request Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.