go-ethereum
go-ethereum copied to clipboard
Go implementation of the Ethereum protocol
# Rationale - The `readLoop` must wait until the previous packet has been processed before going to conn to read the next package. Causing 'dispatchLoop' and 'readLoop' to wait frequently....
Geth provides an RPC endpoint to rewind the chain head: debug.setHead(). However, the entire procedure is highly inefficient, it takes around 500ms to revert a single block on my machine....
After exposing additional Pebble metrics, one notable observation is that Pebble shows around 8-9GB of compaction debt. This indicates that there is approximately 8-9GB of data pending compaction, but compactions...
``` Build ID: 15e9e5882df65907942fa3b5d1ec150f3a7d3b90 Type: inuse_space Time: 2025-05-11 15:03:46 CST Entering interactive mode (type "help" for commands, "o" for options) (pprof) alloc_space (pprof) top Showing nodes accounting for 75.21TB, 54.11%...
#### System information OS & Version: Linux and macOS Commit hash : c8be0f9a74fdabe5f82fa5b647e9973c9c3567ef #### Expected behaviour I expect the following code to print out wallets when my Trezor is attached...
This is a placeholder issue to reminder to myself to look into upstreaming https://github.com/ethereum-optimism/op-geth/pull/611
Bumps [golang.org/x/net](https://github.com/golang/net) from 0.36.0 to 0.38.0. Commits e1fcd82 html: properly handle trailing solidus in unquoted attribute value in foreign... ebed060 internal/http3: fix build of tests with GOEXPERIMENT=nosynctest 1f1fa29 publicsuffix: regenerate...
This PR allows `--vmodule` to also downgrade the log level for packages. closes https://github.com/ethereum/go-ethereum/issues/30717 This does have some performance implications that I'm not sure about yet Before ``` ./build/bin/geth --dev...
This PR implements initial FOCIL specifications. For more information, please refer to [EIP-7805](https://eips.ethereum.org/EIPS/eip-7805) and this [PR](https://github.com/ethereum/execution-apis/pull/609).
Hello. Since I have no kind of fetish or voyeurism of spying broadcasted raw transactions though local node it would be great if we have any kind of ENV variable...