go-ethereum

Commit Graph

Author	SHA1	Message	Date
Péter Szilágyi	6b98d18789	cmd, core, params: add support for the Holesky testnet (#28007 ) * cmd, core, params: add support for the Holesky testnet * cmd/devp2p: add support for holesky for the dns crawler	1 year ago
Dan Laine	154b016b6c	core: use slices package for sorting (#27489 ) Co-authored-by: Felix Lange <fjl@twurst.com>	1 year ago
Felix Lange	b628d72766	build: upgrade to go 1.19 (#25726 ) This changes the CI / release builds to use the latest Go version. It also upgrades golangci-lint to a newer version compatible with Go 1.19. In Go 1.19, godoc has gained official support for links and lists. The syntax for code blocks in doc comments has changed and now requires a leading tab character. gofmt adapts comments to the new syntax automatically, so there are a lot of comment re-formatting changes in this PR. We need to apply the new format in order to pass the CI lint stage with Go 1.19. With the linter upgrade, I have decided to disable 'gosec' - it produces too many false-positive warnings. The 'deadcode' and 'varcheck' linters have also been removed because golangci-lint warns about them being unmaintained. 'unused' provides similar coverage and we already have it enabled, so we don't lose much with this change.	2 years ago
Felix Lange	8a134014b4	all: add go:build lines (#23468 ) Generated by go1.17 fmt ./...	3 years ago
Martin Holst Swende	7504dbd6eb	core/vm: 64 bit memory and gas calculations (#19210 ) * core/vm: remove function call for stack validation from evm runloop * core/vm: separate gas calc into static + dynamic * core/vm: optimize push1 * core/vm: reuse pooled bigints for ADDRESS, ORIGIN and CALLER * core/vm: use generic error message for jump/jumpi, to avoid string interpolation * testdata: fix tests for new error message * core/vm: use 64-bit memory calculations * core/vm: fix error in memory calculation * core/vm: address review concerns * core/vm: avoid unnecessary use of big.Int:BitLen()	6 years ago
Felix Lange	37dd9086ec	core: refactor genesis handling This commit solves several issues concerning the genesis block: * Genesis/ChainConfig loading was handled by cmd/geth code. This left library users in the cold. They could specify a JSON-encoded string and overwrite the config, but didn't get any of the additional checks performed by geth. * Decoding and writing of genesis JSON was conflated in WriteGenesisBlock. This made it a lot harder to embed the genesis block into the forthcoming config file loader. This commit changes things so there is a single Genesis type that represents genesis blocks. All uses of WriteGenesis are changed to use the new type instead. * If the chain config supplied by the user was incompatible with the current chain (i.e. the chain had already advanced beyond a scheduled fork), it got overwritten. This is not an issue in practice because previous forks have always had the highest total difficulty. It might matter in the future though. The new code reverts the local chain to the point of the fork when upgrading configuration. The change to genesis block data removes compression library dependencies from package core.	8 years ago

6 Commits (1f11d2d3402730fca32b37e1f3c012cd5bf7fc55)