2021-05-18 06:14:24 +00:00
# Erigon
2019-05-27 13:51:49 +00:00
2021-05-22 09:40:30 +00:00
Erigon is an implementation of Ethereum (aka "Ethereum client"), on the efficiency frontier, written in Go.
2021-04-08 07:39:40 +00:00
2021-05-18 06:14:24 +00:00
2019-05-27 13:51:49 +00:00
2020-08-04 08:03:59 +00:00
<!-- ts -->
2021-07-18 08:22:35 +00:00
2021-03-23 07:28:04 +00:00
- [System Requirements ](#system-requirements )
- [Usage ](#usage )
2021-07-18 08:22:35 +00:00
+ [Getting Started ](#getting-started )
+ [Testnets ](#testnets )
+ [Mining ](#mining )
+ [Windows ](#windows )
+ [GoDoc ](https://godoc.org/github.com/ledgerwatch/erigon )
2021-08-29 06:43:31 +00:00
+ [Beacon Chain ](#beacon-chain )
2021-11-09 10:48:16 +00:00
+ [Dev Chain ](#dev-chain )
2021-03-23 07:28:04 +00:00
- [Key features ](#key-features )
2021-07-18 08:22:35 +00:00
+ [More Efficient State Storage ](#more-efficient-state-storage )
+ [Faster Initial Sync ](#faster-initial-sync )
+ [JSON-RPC daemon ](#json-rpc-daemon )
+ [Run all components by docker-compose ](#run-all-components-by-docker-compose )
+ [Grafana dashboard ](#grafana-dashboard )
2021-06-06 13:02:15 +00:00
- [FAQ ](#faq )
2021-03-23 07:28:04 +00:00
- [Getting in touch ](#getting-in-touch )
2021-07-18 08:22:35 +00:00
+ [Erigon Discord Server ](#erigon-discord-server )
+ [Reporting security issues/concerns ](#reporting-security-issues-concerns )
+ [Team ](#team )
2021-03-23 07:28:04 +00:00
- [Known issues ](#known-issues )
2021-07-18 08:22:35 +00:00
+ [`htop` shows incorrect memory usage ](#htop-shows-incorrect-memory-usage )
2020-08-04 08:03:59 +00:00
<!-- te -->
2019-05-27 13:51:49 +00:00
2015-02-05 20:34:47 +00:00
2020-08-02 15:56:56 +00:00
NB! < code > In-depth links are marked by the microscope sign (🔬) < / code >
2021-08-30 02:48:04 +00:00
**Disclaimer: this software is currently a tech preview. We will do our best to keep it stable and make no breaking
2021-07-18 08:22:35 +00:00
changes but we don't guarantee anything. Things can and will break.**
2015-02-05 20:34:47 +00:00
2015-01-24 17:48:19 +00:00
2020-08-04 08:03:59 +00:00
System Requirements
===================
2020-08-02 16:23:40 +00:00
2022-03-03 14:54:17 +00:00
For a full archive node we recommend >=3TB storage space on a single partition: 1.8TB state (as of March 2022),
200GB temp files (can symlink or mount folder `<datadir>/etl-tmp` to another disk).
Bear in mind that SSD performance deteriorates when close to capacity.
2020-08-02 16:23:40 +00:00
2022-03-03 14:54:17 +00:00
RAM: >=16GB, 64-bit architecture, [Golang version >= 1.16 ](https://golang.org/doc/install ), GCC 10+
2020-08-02 16:23:40 +00:00
2022-03-03 14:54:17 +00:00
< code > 🔬 more info on disk storage is [here ](https://ledgerwatch.github.io/turbo_geth_release.html#Disk-space ).</ code >
2020-08-01 07:55:30 +00:00
2020-08-04 08:03:59 +00:00
Usage
=====
2014-10-27 16:22:29 +00:00
2021-03-23 07:28:04 +00:00
### Getting Started
2020-07-30 11:04:46 +00:00
```sh
2021-09-01 15:53:01 +00:00
git clone --recurse-submodules -j8 https://github.com/ledgerwatch/erigon.git
cd erigon
make erigon
./build/bin/erigon
2020-07-30 11:04:46 +00:00
```
2015-04-28 10:13:42 +00:00
2022-01-25 17:36:21 +00:00
### Optional stages
There is an optional stage that can be enabled through flags:
* `--watch-the-burn` , Enable WatchTheBurn stage which keeps track of ETH issuance and is required to use `erigon_watchTheBurn` .
2021-03-23 07:28:04 +00:00
### Testnets
2022-03-03 14:54:17 +00:00
If you would like to give Erigon a try, but do not have spare 2TB on your drive, a good option is to start syncing one
2021-07-18 08:22:35 +00:00
of the public testnets, Görli. It syncs much quicker, and does not take so much disk space:
2021-03-20 16:51:29 +00:00
```sh
2021-09-01 15:53:01 +00:00
git clone --recurse-submodules -j8 https://github.com/ledgerwatch/erigon.git
cd erigon
make erigon
./build/bin/erigon --datadir goerli --chain goerli
2021-03-20 16:51:29 +00:00
```
2021-07-18 08:22:35 +00:00
Please note the `--datadir` option that allows you to store Erigon files in a non-default location, in this example,
2021-09-05 08:53:35 +00:00
in `goerli` subdirectory of the current directory. Name of the directory `--datadir` does not have to match the name of
2021-07-18 08:22:35 +00:00
the chain in `--chain` .
2021-03-20 16:51:29 +00:00
2021-03-30 09:18:57 +00:00
### Mining
Support only remote-miners.
* To enable, add `--mine --miner.etherbase=...` or `--mine --miner.miner.sigkey=...` flags.
* Other supported options: `--miner.extradata` , `--miner.notify` , `--miner.gaslimit` , `--miner.gasprice`
, `--miner.gastarget`
* RPCDaemon supports methods: eth_coinbase , eth_hashrate, eth_mining, eth_getWork, eth_submitWork, eth_submitHashrate
* RPCDaemon supports websocket methods: newPendingTransaction
* TODO:
2021-07-18 08:22:35 +00:00
+ we don't broadcast mined blocks to p2p-network
yet, [but it's easy to accomplish ](https://github.com/ledgerwatch/erigon/blob/9b8cdc0f2289a7cef78218a15043de5bdff4465e/eth/downloader/downloader.go#L673 )
+ eth_newPendingTransactionFilter
+ eth_newBlockFilter
+ eth_newFilter
+ websocket Logs
2021-03-30 09:18:57 +00:00
< code > 🔬 Detailed mining explanation is [here ](/docs/mining.md ).</ code >
2021-03-23 07:28:04 +00:00
### Windows
2021-03-19 12:53:52 +00:00
2021-05-29 13:16:53 +00:00
Windows users may run erigon in 3 possible ways:
2021-03-19 12:53:52 +00:00
2021-07-18 08:22:35 +00:00
* Build executable binaries natively for Windows using provided `wmake.ps1` PowerShell script. Usage syntax is the same
as `make` command so you have to run `.\wmake.ps1 [-target] <targetname>` . Example: `.\wmake.ps1 erigon` builds erigon
executable. All binaries are placed in `.\build\bin\` subfolder. There are some requirements for a successful native
build on windows :
* [Git ](https://git-scm.com/downloads ) for Windows must be installed. If you're cloning this repository is very
likely you already have it
* [GO Programming Language ](https://golang.org/dl/ ) must be installed. Minimum required version is 1.16
2021-11-18 07:03:25 +00:00
* GNU CC Compiler at least version 10 (is highly suggested that you install `chocolatey` package manager - see
following point)
2021-07-18 08:22:35 +00:00
* If you need to build MDBX tools (i.e. `.\wmake.ps1 db-tools` )
then [Chocolatey package manager ](https://chocolatey.org/ ) for Windows must be installed. By Chocolatey you need
to install the following components : `cmake` , `make` , `mingw` by `choco install cmake make mingw` .
2021-05-29 13:16:53 +00:00
2021-05-30 18:14:28 +00:00
**Important note about Anti-Viruses**
2021-07-18 08:22:35 +00:00
During MinGW's compiler detection phase some temporary executables are generated to test compiler capabilities. It's
been reported some anti-virus programs detect those files as possibly infected by `Win64/Kryptic.CIS` trojan horse (or
a variant of it). Although those are false positives we have no control over 100+ vendors of security products for
Windows and their respective detection algorythms and we understand this might make your experience with Windows
2022-01-05 16:19:12 +00:00
builds uncomfortable. To workaround the issue you might either set exclusions for your antivirus specifically
2021-07-18 08:22:35 +00:00
for `build\bin\mdbx\CMakeFiles` sub-folder of the cloned repo or you can run erigon using the following other two
options
2021-05-30 18:14:28 +00:00
2021-03-19 12:53:52 +00:00
* Use Docker : see [docker-compose.yml ](./docker-compose.yml )
2021-07-18 08:22:35 +00:00
* Use WSL (Windows Subsystem for Linux) **strictly on version 2** . Under this option you can build Erigon just as you
would on a regular Linux distribution. You can point your data also to any of the mounted Windows partitions (
eg. `/mnt/c/[...]` , `/mnt/d/[...]` etc) but in such case be advised performance is impacted: this is due to the fact
those mount points use `DrvFS` which is a [network file system ](#blocks-execution-is-slow-on-cloud-network-drives )
and, additionally, MDBX locks the db for exclusive access which implies only one process at a time can access data.
This has consequences on the running of `rpcdaemon` which has to be configured as [Remote DB ](#for-remote-db ) even if
it is executed on the very same computer. If instead your data is hosted on the native Linux filesystem non
limitations apply.
**Please also note the default WSL2 environment has its own IP address which does not match the one of the network
interface of Windows host: take this into account when configuring NAT for port 30303 on your router.**
2021-03-03 08:35:12 +00:00
2021-08-29 06:43:31 +00:00
### Beacon Chain
2021-09-02 05:55:04 +00:00
Erigon can be used as an execution-layer for beacon chain consensus clients (Eth2). Default configuration is ok. Eth2
2022-01-05 16:19:12 +00:00
relies on availability of receipts - don't prune them: don't add character `r` to `--prune` flag. However, old receipts
are not needed for Eth2 and you can safely prune them with `--prune.r.before=11184524` in combination with `--prune htc` .
2021-08-29 06:43:31 +00:00
2021-08-29 06:51:26 +00:00
You must run the [JSON-RPC daemon ](#json-rpc-daemon ) in addition to the Erigon.
2021-08-29 06:43:31 +00:00
2021-09-02 05:55:04 +00:00
If beacon chain client on a different device: add `--http.addr 0.0.0.0` (JSON-RPC daemon listen on localhost by default)
.
2021-08-29 06:43:31 +00:00
2021-09-02 05:55:04 +00:00
Once the JSON-RPC daemon is running, all you need to do is point your beacon chain client to `<ip address>:8545` ,
2022-01-05 16:19:12 +00:00
where `<ip address>` is either localhost or the IP address of the device running the JSON-RPC daemon.
2021-08-29 06:43:31 +00:00
Erigon has been tested with Lighthouse however all other clients that support JSON-RPC should also work.
2021-11-09 10:48:16 +00:00
2022-02-09 22:11:47 +00:00
### Multiple Instances / One Machine
Here's an example of running multiple instances of Erigon against different chains on the same machine:
Against mainnet:
```
./build/bin/erigon --datadir "< your-mainnet-data-path > " --private.api.addr=localhost:9091 -port 30303 --chain mainnet
./build/bin/rpcdaemon --datadir "< your-mainnet-data-path > " --private.api.addr=localhost:9091 --http.api=eth,debug,net,trace,web3,erigon --http.port 8546
```
As usual, use the same `datadir` and `private.api.addr` for both Erigon and RPC. Explicitly specify the chain and the other ports to make things clearer. Quote your path if it has spaces.
Against rinkeby:
```
./build/bin/erigon --datadir "< your-rinkeby-data-path > " --private.api.addr=localhost:9092 -port 30304 --chain rinkeby
./build/bin/rpcdaemon --datadir "< your-rinkeby-data-path > " --private.api.addr=localhost:9092 --http.api=eth,debug,net,trace,web3,erigon --http.port 8547
```
Same command, but use different `datadir` and different ports throughout.
2021-11-09 10:48:16 +00:00
### Dev Chain
< code > 🔬 Detailed explanation is [DEV_CHAIN ](/DEV_CHAIN.md ).</ code >
2021-08-29 06:43:31 +00:00
2020-08-04 08:03:59 +00:00
Key features
============
2015-04-28 10:13:42 +00:00
2021-07-18 08:22:35 +00:00
< code > 🔬 See more
detailed [overview of functionality and current limitations ](https://ledgerwatch.github.io/turbo_geth_release.html ). It
is being updated on recurring basis.< / code >
2015-04-28 10:13:42 +00:00
2021-03-23 07:28:04 +00:00
### More Efficient State Storage
2015-04-28 10:13:42 +00:00
2021-07-18 08:22:35 +00:00
**Flat KV storage.** Erigon uses a key-value database and storing accounts and storage in a simple way.
2020-08-02 15:56:56 +00:00
< code > 🔬 See our detailed DB walkthrough [here ](./docs/programmers_guide/db_walkthrough.MD ).</ code >
2016-05-23 13:19:17 +00:00
2021-07-18 08:22:35 +00:00
**Preprocessing**. For some operations, Erigon uses temporary files to preprocess data before inserting it into the main
DB. That reduces write amplification and DB inserts are orders of magnitude quicker.
2016-05-23 13:19:17 +00:00
2021-09-12 07:50:17 +00:00
< code > 🔬 See our detailed ETL explanation [here ](https://github.com/ledgerwatch/erigon-lib/blob/main/etl/README.md ).</ code >
2020-08-06 12:02:41 +00:00
2020-07-30 11:04:46 +00:00
**Plain state**.
2014-02-14 23:04:46 +00:00
2021-05-30 18:14:28 +00:00
**Single accounts/state trie**. Erigon uses a single Merkle trie for both accounts and the storage.
2014-02-15 12:27:23 +00:00
2021-03-23 07:28:04 +00:00
### Faster Initial Sync
2016-07-12 09:51:31 +00:00
2021-05-23 14:50:44 +00:00
Erigon uses a rearchitected full sync algorithm from
2020-07-30 11:04:46 +00:00
[Go-Ethereum ](https://github.com/ethereum/go-ethereum ) that is split into
"stages".
2016-07-12 09:51:31 +00:00
2021-05-30 18:14:28 +00:00
< code > 🔬 See more detailed explanation in the [Staged Sync Readme ](/eth/stagedsync/README.md )</ code >
2020-08-02 12:35:05 +00:00
2021-07-18 08:22:35 +00:00
It uses the same network primitives and is compatible with regular go-ethereum nodes that are using full sync, you do
not need any special sync capabilities for Erigon to sync.
2016-07-12 09:51:31 +00:00
2021-09-22 08:39:51 +00:00
When reimagining the full sync, with focus on batching data together and minimize DB overwrites. That makes it possible
2021-07-18 08:22:35 +00:00
to sync Ethereum mainnet in under 2 days if you have a fast enough network connection and an SSD drive.
2016-07-12 09:51:31 +00:00
2020-07-30 11:04:46 +00:00
Examples of stages are:
2016-07-12 09:51:31 +00:00
2020-07-30 11:04:46 +00:00
* Downloading headers;
* Downloading block bodies;
2016-07-12 09:51:31 +00:00
2021-05-23 14:50:44 +00:00
* Recovering senders' addresses;
2020-07-30 11:04:46 +00:00
* Executing blocks;
2019-06-13 13:23:22 +00:00
2020-07-30 11:04:46 +00:00
* Validating root hashes and building intermediate hashes for the state Merkle trie;
2019-06-13 13:23:22 +00:00
2021-05-23 14:50:44 +00:00
* [...]
2019-08-19 11:07:23 +00:00
2021-03-23 07:28:04 +00:00
### JSON-RPC daemon
2016-07-12 09:51:31 +00:00
2021-07-18 08:22:35 +00:00
In Erigon RPC calls are extracted out of the main binary into a separate daemon. This daemon can use both local or
remote DBs. That means, that this RPC daemon doesn't have to be running on the same machine as the main Erigon binary or
2021-05-27 13:54:55 +00:00
it can run from a snapshot of a database for read-only calls.
2020-08-02 15:56:56 +00:00
2020-09-26 12:38:10 +00:00
< code > 🔬 See [RPC-Daemon docs ](./cmd/rpcdaemon/README.md )</ code >
2018-02-10 10:50:14 +00:00
2021-05-29 13:16:53 +00:00
#### **For local DB**
2021-03-20 16:55:13 +00:00
2021-07-18 08:22:35 +00:00
This is only possible if RPC daemon runs on the same computer as Erigon. This mode uses shared memory access to the
database of Erigon, which has better performance than accessing via TPC socket (see "For remote DB" section below).
Provide both `--datadir` and `--private.api.addr` options:
2021-09-01 15:53:01 +00:00
```sh
make erigon
./build/bin/erigon --private.api.addr=localhost:9090
make rpcdaemon
2021-09-25 15:28:25 +00:00
./build/bin/rpcdaemon --datadir=< your_data_dir > --private.api.addr=localhost:9090 --http.api=eth,erigon,web3,net,debug,trace,txpool
2020-07-30 11:04:46 +00:00
```
2018-02-10 10:50:14 +00:00
2021-05-29 13:16:53 +00:00
#### **For remote DB**
2021-03-20 16:55:13 +00:00
2021-07-18 08:22:35 +00:00
This works regardless of whether RPC daemon is on the same computer with Erigon, or on a different one. They use TPC
socket connection to pass data between them. To use this mode, run Erigon in one terminal window
geth 1.9.13 (#469)
* core: initial version of state snapshots
* core/state: lazy sorting, snapshot invalidation
* core/state/snapshot: extract and split cap method, cover corners
* snapshot: iteration and buffering optimizations
* core/state/snapshot: unlink snapshots from blocks, quad->linear cleanup
* 123
* core/rawdb, core/state/snapshot: runtime snapshot generation
* core/state/snapshot: fix difflayer origin-initalization after flatten
* add "to merge"
* core/state/snapshot: implement snapshot layer iteration
* core/state/snapshot: node behavioural difference on bloom content
* core: journal the snapshot inside leveldb, not a flat file
* core/state/snapshot: bloom, metrics and prefetcher fixes
* core/state/snapshot: move iterator out into its own files
* core/state/snapshot: implement iterator priority for fast direct data lookup
* core/state/snapshot: full featured account iteration
* core/state/snapshot: faster account iteration, CLI integration
* core: fix broken tests due to API changes + linter
* core/state: fix an account resurrection issue
* core/tests: test for destroy+recreate contract with storage
* squashme
* core/state/snapshot, tests: sync snap gen + snaps in consensus tests
* core/state: extend snapshotter to handle account resurrections
* core/state: fix account root hash update point
* core/state: fix resurrection state clearing and access
* core/state/snapshot: handle deleted accounts in fast iterator
* core: more blockchain tests
* core/state/snapshot: fix various iteration issues due to destruct set
* core: fix two snapshot iterator flaws, decollide snap storage prefix
* core/state/snapshot/iterator: fix two disk iterator flaws
* core/rawdb: change SnapshotStoragePrefix to avoid prefix collision with preimagePrefix
* params: begin v1.9.13 release cycle
* cmd/checkpoint-admin: add some documentation (#20697)
* go.mod: update duktape to fix sprintf warnings (#20777)
This revision of go-duktype fixes the following warning
```
duk_logging.c: In function ‘duk__logger_prototype_log_shared’:
duk_logging.c:184:64: warning: ‘Z’ directive writing 1 byte into a region of size between 0 and 9 [-Wformat-overflow=]
184 | sprintf((char *) date_buf, "%04d-%02d-%02dT%02d:%02d:%02d.%03dZ",
| ^
In file included from /usr/include/stdio.h:867,
from duk_logging.c:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 25 and 85 bytes into a destination of size 32
36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
37 | __bos (__s), __fmt, __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
* core/rawdb: fix freezer table test error check
Fixes: Condition is always 'false' because 'err' is always 'nil'
* core/rawdb: improve table database (#20703)
This PR fixes issues in TableDatabase.
TableDatabase is a wrapper of underlying ethdb.Database with an additional prefix.
The prefix is applied to all entries it maintains. However when we try to retrieve entries
from it we don't handle the key properly. In theory the prefix should be truncated and
only user key is returned. But we don't do it in some cases, e.g. the iterator and batch
replayer created from it. So this PR is the fix to these issues.
* eth: when triggering a sync, check the head header TD, not block
* internal/web3ext: fix clique console apis to work on missing arguments
* rpc: dont log an error if user configures --rpcapi=rpc... (#20776)
This just prevents a false negative ERROR warning when, for some unknown
reason, a user attempts to turn on the module rpc even though it's already going
to be on.
* node, cmd/clef: report actual port used for http rpc (#20789)
* internal/ethapi: don't set sender-balance to maxuint, fixes #16999 (#20783)
Prior to this change, eth_call changed the balance of the sender account in the
EVM environment to 2^256 wei to cover the gas cost of the call execution.
We've had this behavior for a long time even though it's super confusing.
This commit sets the default call gasprice to zero instead of updating the balance,
which is better because it makes eth_call semantics less surprising. Removing
the built-in balance assignment also makes balance overrides work as expected.
* metrics: disable CPU stats (gosigar) on iOS
* cmd/devp2p: tweak DNS TTLs (#20801)
* cmd/devp2p: tweak DNS TTLs
* cmd/devp2p: bump treeNodeTTL to four weeks
* cmd/devp2p: lower route53 change limit again (#20819)
* cmd/devp2p: be very correct about route53 change splitting (#20820)
Turns out the way RDATA limits work is documented after all,
I just didn't search right. The trick to make it work is to
count UPSERTs twice.
This also adds an additional check to ensure TTL changes are
applied on existing records.
* graphql, node, rpc: fix typos in comments (#20824)
* eth: improve shutdown synchronization (#20695)
* eth: improve shutdown synchronization
Most goroutines started by eth.Ethereum didn't have any shutdown sync at
all, which lead to weird error messages when quitting the client.
This change improves the clean shutdown path by stopping all internal
components in dependency order and waiting for them to actually be
stopped before shutdown is considered done. In particular, we now stop
everything related to peers before stopping 'resident' parts such as
core.BlockChain.
* eth: rewrite sync controller
* eth: remove sync start debug message
* eth: notify chainSyncer about new peers after handshake
* eth: move downloader.Cancel call into chainSyncer
* eth: make post-sync block broadcast synchronous
* eth: add comments
* core: change blockchain stop message
* eth: change closeBloomHandler channel type
* eth/filters: fix typo on unindexedLogs function's comment (#20827)
* core: bump txpool tx max size to 128KB
* snapshotter/tests: verify snapdb post-state against trie (#20812)
* core/state/snapshot: basic trie-to-hash implementation
* tests: validate snapshot after test
* core/state/snapshot: fix review concerns
* cmd, consensus: add option to disable mmap for DAG caches/datasets (#20484)
* cmd, consensus: add option to disable mmap for DAG caches/datasets
* consensus: add benchmarks for mmap with/with lock
* cmd/clef: add newaccount command (#20782)
* cmd/clef: add newaccount command
* cmd/clef: document clef_New, update API versioning
* Update cmd/clef/intapi_changelog.md
Co-Authored-By: ligi <ligi@ligi.de>
* Update signer/core/uiapi.go
Co-Authored-By: ligi <ligi@ligi.de>
Co-authored-by: ligi <ligi@ligi.de>
* eth: add debug_accountRange API (#19645)
This new API allows reading accounts and their content by address range.
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: Felix Lange <fjl@twurst.com>
* travis: allow cocoapods deploy to fail (#20833)
* metrics: improve TestTimerFunc (#20818)
The test failed due to what appears to be fluctuations in time.Sleep, which is
not the actual method under test. This change modifies it so we compare the
metered Max to the actual time instead of the desired time.
* README: update private network genesis spec with istanbul (#20841)
* add istanbul and muirGlacier to genesis states in README
* remove muirGlacier, relocate istanbul
* cmd/evm: Rework execution stats (#20792)
- Dump stats also for --bench flag.
- From memory stats only show number and size of allocations. This is what `test -bench` shows. I doubt others like number of GC runs are any useful, but can be added if requested.
- Now the mem stats are for single execution in case of --bench.
* cmd/devp2p, cmd/wnode, whisper: add missing calls to Timer.Stop (#20843)
* p2p/server: add UDP port mapping goroutine to wait group (#20846)
* accounts/abi faster unpacking of int256 (#20850)
* p2p/discv5: add missing Timer.Stop calls (#20853)
* miner/worker: add missing timer.Stop call (#20857)
* cmd/geth: fix bad genesis test (#20860)
* eth/filters: add missing Ticker.Stop call (#20862)
* eth/fetcher: add missing timer.Stop calls (#20861)
* event: add missing timer.Stop call in TestFeed (#20868)
* metrics: add missing calls to Ticker.Stop in tests (#20866)
* ethstats: add missing Ticker.Stop call (#20867)
* p2p/discv5, p2p/testing: add missing Timer.Stop calls in tests (#20869)
* core: add missing Timer.Stop call in TestLogReorgs (#20870)
* rpc: add missing timer.Stop calls in websocket tests (#20863)
* crypto/ecies: improve concatKDF (#20836)
This removes a bunch of weird code around the counter overflow check in
concatKDF and makes it actually work for different hash output sizes.
The overflow check worked as follows: concatKDF applies the hash function N
times, where N is roundup(kdLen, hashsize) / hashsize. N should not
overflow 32 bits because that would lead to a repetition in the KDF output.
A couple issues with the overflow check:
- It used the hash.BlockSize, which is wrong because the
block size is about the input of the hash function. Luckily, all standard
hash functions have a block size that's greater than the output size, so
concatKDF didn't crash, it just generated too much key material.
- The check used big.Int to compare against 2^32-1.
- The calculation could still overflow before reaching the check.
The new code in concatKDF doesn't check for overflow. Instead, there is a
new check on ECIESParams which ensures that params.KeyLen is < 512. This
removes any possibility of overflow.
There are a couple of miscellaneous improvements bundled in with this
change:
- The key buffer is pre-allocated instead of appending the hash output
to an initially empty slice.
- The code that uses concatKDF to derive keys is now shared between Encrypt
and Decrypt.
- There was a redundant invocation of IsOnCurve in Decrypt. This is now removed
because elliptic.Unmarshal already checks whether the input is a valid curve
point since Go 1.5.
Co-authored-by: Felix Lange <fjl@twurst.com>
* rpc: metrics for JSON-RPC method calls (#20847)
This adds a couple of metrics for tracking the timing
and frequency of method calls:
- rpc/requests gauge counts all requests
- rpc/success gauge counts requests which return err == nil
- rpc/failure gauge counts requests which return err != nil
- rpc/duration/all timer tracks timing of all requests
- rpc/duration/<method>/<success/failure> tracks per-method timing
* mobile: use bind.NewKeyedTransactor instead of duplicating (#20888)
It's better to reuse the existing code to create a keyed transactor
than to rewrite the logic again.
* internal/ethapi: add CallArgs.ToMessage method (#20854)
ToMessage is used to convert between ethapi.CallArgs and types.Message.
It reduces the length of the DoCall method by about half by abstracting out
the conversion between the CallArgs and the Message. This should improve the
code's maintainability and reusability.
* eth, les: fix flaky tests (#20897)
* les: fix flaky test
* eth: fix flaky test
* cmd/geth: enable metrics for geth import command (#20738)
* cmd/geth: enable metrics for geth import command
* cmd/geth: enable metrics-flags for import command
* core/vm: use a callcontext struct (#20761)
* core/vm: use a callcontext struct
* core/vm: fix tests
* core/vm/runtime: benchmark
* core/vm: make intpool push inlineable, unexpose callcontext
* docs/audits: add discv5 protocol audits from LA and C53 (#20898)
* .github: change gitter reference to discord link in issue template (#20896)
* couple of fixes to docs in clef (#20900)
* p2p/discover: add initial discovery v5 implementation (#20750)This adds an implementation of the current discovery v5 spec.There is full integration with cmd/devp2p and enode.Iterator in thisversion. In theory we could enable the new protocol as a replacement ofdiscovery v4 at any time. In practice, there will likely be a few morechanges to the spec and implementation before this can happen.
* build: upgrade to golangci-lint 1.24.0 (#20901)
* accounts/scwallet: remove unnecessary uses of fmt.Sprintf
* cmd/puppeth: remove unnecessary uses of fmt.Sprintf
* p2p/discv5: remove unnecessary use of fmt.Sprintf
* whisper/mailserver: remove unnecessary uses of fmt.Sprintf
* core: goimports -w tx_pool_test.go
* eth/downloader: goimports -w downloader_test.go
* build: upgrade to golangci-lint 1.24.0
* accounts/abi/bind: Refactored topics (#20851)
* accounts/abi/bind: refactored topics
* accounts/abi/bind: use store function to remove code duplication
* accounts/abi/bind: removed unused type defs
* accounts/abi/bind: error on tuples in topics
* Cosmetic changes to restart travis build
Co-authored-by: Guillaume Ballet <gballet@gmail.com>
* node: allow websocket and HTTP on the same port (#20810)
This change makes it possible to run geth with JSON-RPC over HTTP and
WebSocket on the same TCP port. The default port for WebSocket
is still 8546.
geth --rpc --rpcport 8545 --ws --wsport 8545
This also removes a lot of deprecated API surface from package rpc.
The rpc package is now purely about serving JSON-RPC and no longer
provides a way to start an HTTP server.
* crypto: improve error messages in LoadECDSA (#20718)
This improves error messages when the file is too short or too long.
Also rewrite the test for SaveECDSA because LoadECDSA has its own
test now.
Co-authored-by: Felix Lange <fjl@twurst.com>
* changed date of rpcstack.go since new file (#20904)
* accounts/abi/bind: fixed erroneous filtering of negative ints (#20865)
* accounts/abi/bind: fixed erroneous packing of negative ints
* accounts/abi/bind: added test cases for negative ints in topics
* accounts/abi/bind: fixed genIntType for go 1.12
* accounts/abi: minor nitpick
* cmd: deprecate --testnet, use named networks instead (#20852)
* cmd/utils: make goerli the default testnet
* cmd/geth: explicitly rename testnet to ropsten
* core: explicitly rename testnet to ropsten
* params: explicitly rename testnet to ropsten
* cmd: explicitly rename testnet to ropsten
* miner: explicitly rename testnet to ropsten
* mobile: allow for returning the goerli spec
* tests: explicitly rename testnet to ropsten
* docs: update readme to reflect changes to the default testnet
* mobile: allow for configuring goerli and rinkeby nodes
* cmd/geth: revert --testnet back to ropsten and mark as legacy
* cmd/util: mark --testnet flag as deprecated
* docs: update readme to properly reflect the 3 testnets
* cmd/utils: add an explicit deprecation warning on startup
* cmd/utils: swap goerli and ropsten in usage
* cmd/geth: swap goerli and ropsten in usage
* cmd/geth: if running a known preset, log it for convenience
* docs: improve readme on usage of ropsten's testnet datadir
* cmd/utils: check if legacy `testnet` datadir exists for ropsten
* cmd/geth: check for legacy testnet path in console command
* cmd/geth: use switch statement for complex conditions in main
* cmd/geth: move known preset log statement to the very top
* cmd/utils: create new ropsten configurations in the ropsten datadir
* cmd/utils: makedatadir should check for existing testnet dir
* cmd/geth: add legacy testnet flag to the copy db command
* cmd/geth: add legacy testnet flag to the inspect command
* les, les/lespay/client: add service value statistics and API (#20837)
This PR adds service value measurement statistics to the light client. It
also adds a private API that makes these statistics accessible. A follow-up
PR will add the new server pool which uses these statistics to select
servers with good performance.
This document describes the function of the new components:
https://gist.github.com/zsfelfoldi/3c7ace895234b7b345ab4f71dab102d4
Co-authored-by: rjl493456442 <garyrong0905@gmail.com>
Co-authored-by: rjl493456442 <garyrong0905@gmail.com>
* README: update min go version to 1.13 (#20911)
* travis, appveyor, build, Dockerfile: bump Go to 1.14.2 (#20913)
* travis, appveyor, build, Dockerfile: bump Go to 1.14.2
* travis, appveyor: force GO111MODULE=on for every build
* core/rawdb: fix data race between Retrieve and Close (#20919)
* core/rawdb: fixed data race between retrieve and close
closes https://github.com/ethereum/go-ethereum/issues/20420
* core/rawdb: use non-atomic load while holding mutex
* all: simplify and fix database iteration with prefix/start (#20808)
* core/state/snapshot: start fixing disk iterator seek
* ethdb, rawdb, leveldb, memorydb: implement iterators with prefix and start
* les, core/state/snapshot: iterator fixes
* all: remove two iterator methods
* all: rename Iteratee.NewIteratorWith -> NewIterator
* ethdb: fix review concerns
* params: update CHTs for the 1.9.13 release
* params: release Geth v1.9.13
* added some missing files
* post-rebase fixups
Co-authored-by: Péter Szilágyi <peterke@gmail.com>
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: gary rong <garyrong0905@gmail.com>
Co-authored-by: Alex Willmer <alex@moreati.org.uk>
Co-authored-by: meowsbits <45600330+meowsbits@users.noreply.github.com>
Co-authored-by: Felix Lange <fjl@twurst.com>
Co-authored-by: rene <41963722+renaynay@users.noreply.github.com>
Co-authored-by: Ha ĐANG <dvietha@gmail.com>
Co-authored-by: Hanjiang Yu <42531996+de1acr0ix@users.noreply.github.com>
Co-authored-by: ligi <ligi@ligi.de>
Co-authored-by: Wenbiao Zheng <delweng@gmail.com>
Co-authored-by: Adam Schmideg <adamschmideg@users.noreply.github.com>
Co-authored-by: Jeff Wentworth <jeff@curvegrid.com>
Co-authored-by: Paweł Bylica <chfast@gmail.com>
Co-authored-by: ucwong <ucwong@126.com>
Co-authored-by: Marius van der Wijden <m.vanderwijden@live.de>
Co-authored-by: Luke Champine <luke.champine@gmail.com>
Co-authored-by: Boqin Qin <Bobbqqin@gmail.com>
Co-authored-by: William Morriss <wjmelements@gmail.com>
Co-authored-by: Guillaume Ballet <gballet@gmail.com>
Co-authored-by: Raw Pong Ghmoa <58883403+q9f@users.noreply.github.com>
Co-authored-by: Felföldi Zsolt <zsfelfoldi@gmail.com>
2020-04-19 17:31:47 +00:00
2021-09-01 15:53:01 +00:00
```sh
make erigon
./build/bin/erigon --private.api.addr=localhost:9090
make rpcdaemon
2021-09-25 15:28:25 +00:00
./build/bin/rpcdaemon --private.api.addr=localhost:9090 --http.api=eth,erigon,web3,net,debug,trace,txpool
geth 1.9.13 (#469)
* core: initial version of state snapshots
* core/state: lazy sorting, snapshot invalidation
* core/state/snapshot: extract and split cap method, cover corners
* snapshot: iteration and buffering optimizations
* core/state/snapshot: unlink snapshots from blocks, quad->linear cleanup
* 123
* core/rawdb, core/state/snapshot: runtime snapshot generation
* core/state/snapshot: fix difflayer origin-initalization after flatten
* add "to merge"
* core/state/snapshot: implement snapshot layer iteration
* core/state/snapshot: node behavioural difference on bloom content
* core: journal the snapshot inside leveldb, not a flat file
* core/state/snapshot: bloom, metrics and prefetcher fixes
* core/state/snapshot: move iterator out into its own files
* core/state/snapshot: implement iterator priority for fast direct data lookup
* core/state/snapshot: full featured account iteration
* core/state/snapshot: faster account iteration, CLI integration
* core: fix broken tests due to API changes + linter
* core/state: fix an account resurrection issue
* core/tests: test for destroy+recreate contract with storage
* squashme
* core/state/snapshot, tests: sync snap gen + snaps in consensus tests
* core/state: extend snapshotter to handle account resurrections
* core/state: fix account root hash update point
* core/state: fix resurrection state clearing and access
* core/state/snapshot: handle deleted accounts in fast iterator
* core: more blockchain tests
* core/state/snapshot: fix various iteration issues due to destruct set
* core: fix two snapshot iterator flaws, decollide snap storage prefix
* core/state/snapshot/iterator: fix two disk iterator flaws
* core/rawdb: change SnapshotStoragePrefix to avoid prefix collision with preimagePrefix
* params: begin v1.9.13 release cycle
* cmd/checkpoint-admin: add some documentation (#20697)
* go.mod: update duktape to fix sprintf warnings (#20777)
This revision of go-duktype fixes the following warning
```
duk_logging.c: In function ‘duk__logger_prototype_log_shared’:
duk_logging.c:184:64: warning: ‘Z’ directive writing 1 byte into a region of size between 0 and 9 [-Wformat-overflow=]
184 | sprintf((char *) date_buf, "%04d-%02d-%02dT%02d:%02d:%02d.%03dZ",
| ^
In file included from /usr/include/stdio.h:867,
from duk_logging.c:5:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 25 and 85 bytes into a destination of size 32
36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
37 | __bos (__s), __fmt, __va_arg_pack ());
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
* core/rawdb: fix freezer table test error check
Fixes: Condition is always 'false' because 'err' is always 'nil'
* core/rawdb: improve table database (#20703)
This PR fixes issues in TableDatabase.
TableDatabase is a wrapper of underlying ethdb.Database with an additional prefix.
The prefix is applied to all entries it maintains. However when we try to retrieve entries
from it we don't handle the key properly. In theory the prefix should be truncated and
only user key is returned. But we don't do it in some cases, e.g. the iterator and batch
replayer created from it. So this PR is the fix to these issues.
* eth: when triggering a sync, check the head header TD, not block
* internal/web3ext: fix clique console apis to work on missing arguments
* rpc: dont log an error if user configures --rpcapi=rpc... (#20776)
This just prevents a false negative ERROR warning when, for some unknown
reason, a user attempts to turn on the module rpc even though it's already going
to be on.
* node, cmd/clef: report actual port used for http rpc (#20789)
* internal/ethapi: don't set sender-balance to maxuint, fixes #16999 (#20783)
Prior to this change, eth_call changed the balance of the sender account in the
EVM environment to 2^256 wei to cover the gas cost of the call execution.
We've had this behavior for a long time even though it's super confusing.
This commit sets the default call gasprice to zero instead of updating the balance,
which is better because it makes eth_call semantics less surprising. Removing
the built-in balance assignment also makes balance overrides work as expected.
* metrics: disable CPU stats (gosigar) on iOS
* cmd/devp2p: tweak DNS TTLs (#20801)
* cmd/devp2p: tweak DNS TTLs
* cmd/devp2p: bump treeNodeTTL to four weeks
* cmd/devp2p: lower route53 change limit again (#20819)
* cmd/devp2p: be very correct about route53 change splitting (#20820)
Turns out the way RDATA limits work is documented after all,
I just didn't search right. The trick to make it work is to
count UPSERTs twice.
This also adds an additional check to ensure TTL changes are
applied on existing records.
* graphql, node, rpc: fix typos in comments (#20824)
* eth: improve shutdown synchronization (#20695)
* eth: improve shutdown synchronization
Most goroutines started by eth.Ethereum didn't have any shutdown sync at
all, which lead to weird error messages when quitting the client.
This change improves the clean shutdown path by stopping all internal
components in dependency order and waiting for them to actually be
stopped before shutdown is considered done. In particular, we now stop
everything related to peers before stopping 'resident' parts such as
core.BlockChain.
* eth: rewrite sync controller
* eth: remove sync start debug message
* eth: notify chainSyncer about new peers after handshake
* eth: move downloader.Cancel call into chainSyncer
* eth: make post-sync block broadcast synchronous
* eth: add comments
* core: change blockchain stop message
* eth: change closeBloomHandler channel type
* eth/filters: fix typo on unindexedLogs function's comment (#20827)
* core: bump txpool tx max size to 128KB
* snapshotter/tests: verify snapdb post-state against trie (#20812)
* core/state/snapshot: basic trie-to-hash implementation
* tests: validate snapshot after test
* core/state/snapshot: fix review concerns
* cmd, consensus: add option to disable mmap for DAG caches/datasets (#20484)
* cmd, consensus: add option to disable mmap for DAG caches/datasets
* consensus: add benchmarks for mmap with/with lock
* cmd/clef: add newaccount command (#20782)
* cmd/clef: add newaccount command
* cmd/clef: document clef_New, update API versioning
* Update cmd/clef/intapi_changelog.md
Co-Authored-By: ligi <ligi@ligi.de>
* Update signer/core/uiapi.go
Co-Authored-By: ligi <ligi@ligi.de>
Co-authored-by: ligi <ligi@ligi.de>
* eth: add debug_accountRange API (#19645)
This new API allows reading accounts and their content by address range.
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: Felix Lange <fjl@twurst.com>
* travis: allow cocoapods deploy to fail (#20833)
* metrics: improve TestTimerFunc (#20818)
The test failed due to what appears to be fluctuations in time.Sleep, which is
not the actual method under test. This change modifies it so we compare the
metered Max to the actual time instead of the desired time.
* README: update private network genesis spec with istanbul (#20841)
* add istanbul and muirGlacier to genesis states in README
* remove muirGlacier, relocate istanbul
* cmd/evm: Rework execution stats (#20792)
- Dump stats also for --bench flag.
- From memory stats only show number and size of allocations. This is what `test -bench` shows. I doubt others like number of GC runs are any useful, but can be added if requested.
- Now the mem stats are for single execution in case of --bench.
* cmd/devp2p, cmd/wnode, whisper: add missing calls to Timer.Stop (#20843)
* p2p/server: add UDP port mapping goroutine to wait group (#20846)
* accounts/abi faster unpacking of int256 (#20850)
* p2p/discv5: add missing Timer.Stop calls (#20853)
* miner/worker: add missing timer.Stop call (#20857)
* cmd/geth: fix bad genesis test (#20860)
* eth/filters: add missing Ticker.Stop call (#20862)
* eth/fetcher: add missing timer.Stop calls (#20861)
* event: add missing timer.Stop call in TestFeed (#20868)
* metrics: add missing calls to Ticker.Stop in tests (#20866)
* ethstats: add missing Ticker.Stop call (#20867)
* p2p/discv5, p2p/testing: add missing Timer.Stop calls in tests (#20869)
* core: add missing Timer.Stop call in TestLogReorgs (#20870)
* rpc: add missing timer.Stop calls in websocket tests (#20863)
* crypto/ecies: improve concatKDF (#20836)
This removes a bunch of weird code around the counter overflow check in
concatKDF and makes it actually work for different hash output sizes.
The overflow check worked as follows: concatKDF applies the hash function N
times, where N is roundup(kdLen, hashsize) / hashsize. N should not
overflow 32 bits because that would lead to a repetition in the KDF output.
A couple issues with the overflow check:
- It used the hash.BlockSize, which is wrong because the
block size is about the input of the hash function. Luckily, all standard
hash functions have a block size that's greater than the output size, so
concatKDF didn't crash, it just generated too much key material.
- The check used big.Int to compare against 2^32-1.
- The calculation could still overflow before reaching the check.
The new code in concatKDF doesn't check for overflow. Instead, there is a
new check on ECIESParams which ensures that params.KeyLen is < 512. This
removes any possibility of overflow.
There are a couple of miscellaneous improvements bundled in with this
change:
- The key buffer is pre-allocated instead of appending the hash output
to an initially empty slice.
- The code that uses concatKDF to derive keys is now shared between Encrypt
and Decrypt.
- There was a redundant invocation of IsOnCurve in Decrypt. This is now removed
because elliptic.Unmarshal already checks whether the input is a valid curve
point since Go 1.5.
Co-authored-by: Felix Lange <fjl@twurst.com>
* rpc: metrics for JSON-RPC method calls (#20847)
This adds a couple of metrics for tracking the timing
and frequency of method calls:
- rpc/requests gauge counts all requests
- rpc/success gauge counts requests which return err == nil
- rpc/failure gauge counts requests which return err != nil
- rpc/duration/all timer tracks timing of all requests
- rpc/duration/<method>/<success/failure> tracks per-method timing
* mobile: use bind.NewKeyedTransactor instead of duplicating (#20888)
It's better to reuse the existing code to create a keyed transactor
than to rewrite the logic again.
* internal/ethapi: add CallArgs.ToMessage method (#20854)
ToMessage is used to convert between ethapi.CallArgs and types.Message.
It reduces the length of the DoCall method by about half by abstracting out
the conversion between the CallArgs and the Message. This should improve the
code's maintainability and reusability.
* eth, les: fix flaky tests (#20897)
* les: fix flaky test
* eth: fix flaky test
* cmd/geth: enable metrics for geth import command (#20738)
* cmd/geth: enable metrics for geth import command
* cmd/geth: enable metrics-flags for import command
* core/vm: use a callcontext struct (#20761)
* core/vm: use a callcontext struct
* core/vm: fix tests
* core/vm/runtime: benchmark
* core/vm: make intpool push inlineable, unexpose callcontext
* docs/audits: add discv5 protocol audits from LA and C53 (#20898)
* .github: change gitter reference to discord link in issue template (#20896)
* couple of fixes to docs in clef (#20900)
* p2p/discover: add initial discovery v5 implementation (#20750)This adds an implementation of the current discovery v5 spec.There is full integration with cmd/devp2p and enode.Iterator in thisversion. In theory we could enable the new protocol as a replacement ofdiscovery v4 at any time. In practice, there will likely be a few morechanges to the spec and implementation before this can happen.
* build: upgrade to golangci-lint 1.24.0 (#20901)
* accounts/scwallet: remove unnecessary uses of fmt.Sprintf
* cmd/puppeth: remove unnecessary uses of fmt.Sprintf
* p2p/discv5: remove unnecessary use of fmt.Sprintf
* whisper/mailserver: remove unnecessary uses of fmt.Sprintf
* core: goimports -w tx_pool_test.go
* eth/downloader: goimports -w downloader_test.go
* build: upgrade to golangci-lint 1.24.0
* accounts/abi/bind: Refactored topics (#20851)
* accounts/abi/bind: refactored topics
* accounts/abi/bind: use store function to remove code duplication
* accounts/abi/bind: removed unused type defs
* accounts/abi/bind: error on tuples in topics
* Cosmetic changes to restart travis build
Co-authored-by: Guillaume Ballet <gballet@gmail.com>
* node: allow websocket and HTTP on the same port (#20810)
This change makes it possible to run geth with JSON-RPC over HTTP and
WebSocket on the same TCP port. The default port for WebSocket
is still 8546.
geth --rpc --rpcport 8545 --ws --wsport 8545
This also removes a lot of deprecated API surface from package rpc.
The rpc package is now purely about serving JSON-RPC and no longer
provides a way to start an HTTP server.
* crypto: improve error messages in LoadECDSA (#20718)
This improves error messages when the file is too short or too long.
Also rewrite the test for SaveECDSA because LoadECDSA has its own
test now.
Co-authored-by: Felix Lange <fjl@twurst.com>
* changed date of rpcstack.go since new file (#20904)
* accounts/abi/bind: fixed erroneous filtering of negative ints (#20865)
* accounts/abi/bind: fixed erroneous packing of negative ints
* accounts/abi/bind: added test cases for negative ints in topics
* accounts/abi/bind: fixed genIntType for go 1.12
* accounts/abi: minor nitpick
* cmd: deprecate --testnet, use named networks instead (#20852)
* cmd/utils: make goerli the default testnet
* cmd/geth: explicitly rename testnet to ropsten
* core: explicitly rename testnet to ropsten
* params: explicitly rename testnet to ropsten
* cmd: explicitly rename testnet to ropsten
* miner: explicitly rename testnet to ropsten
* mobile: allow for returning the goerli spec
* tests: explicitly rename testnet to ropsten
* docs: update readme to reflect changes to the default testnet
* mobile: allow for configuring goerli and rinkeby nodes
* cmd/geth: revert --testnet back to ropsten and mark as legacy
* cmd/util: mark --testnet flag as deprecated
* docs: update readme to properly reflect the 3 testnets
* cmd/utils: add an explicit deprecation warning on startup
* cmd/utils: swap goerli and ropsten in usage
* cmd/geth: swap goerli and ropsten in usage
* cmd/geth: if running a known preset, log it for convenience
* docs: improve readme on usage of ropsten's testnet datadir
* cmd/utils: check if legacy `testnet` datadir exists for ropsten
* cmd/geth: check for legacy testnet path in console command
* cmd/geth: use switch statement for complex conditions in main
* cmd/geth: move known preset log statement to the very top
* cmd/utils: create new ropsten configurations in the ropsten datadir
* cmd/utils: makedatadir should check for existing testnet dir
* cmd/geth: add legacy testnet flag to the copy db command
* cmd/geth: add legacy testnet flag to the inspect command
* les, les/lespay/client: add service value statistics and API (#20837)
This PR adds service value measurement statistics to the light client. It
also adds a private API that makes these statistics accessible. A follow-up
PR will add the new server pool which uses these statistics to select
servers with good performance.
This document describes the function of the new components:
https://gist.github.com/zsfelfoldi/3c7ace895234b7b345ab4f71dab102d4
Co-authored-by: rjl493456442 <garyrong0905@gmail.com>
Co-authored-by: rjl493456442 <garyrong0905@gmail.com>
* README: update min go version to 1.13 (#20911)
* travis, appveyor, build, Dockerfile: bump Go to 1.14.2 (#20913)
* travis, appveyor, build, Dockerfile: bump Go to 1.14.2
* travis, appveyor: force GO111MODULE=on for every build
* core/rawdb: fix data race between Retrieve and Close (#20919)
* core/rawdb: fixed data race between retrieve and close
closes https://github.com/ethereum/go-ethereum/issues/20420
* core/rawdb: use non-atomic load while holding mutex
* all: simplify and fix database iteration with prefix/start (#20808)
* core/state/snapshot: start fixing disk iterator seek
* ethdb, rawdb, leveldb, memorydb: implement iterators with prefix and start
* les, core/state/snapshot: iterator fixes
* all: remove two iterator methods
* all: rename Iteratee.NewIteratorWith -> NewIterator
* ethdb: fix review concerns
* params: update CHTs for the 1.9.13 release
* params: release Geth v1.9.13
* added some missing files
* post-rebase fixups
Co-authored-by: Péter Szilágyi <peterke@gmail.com>
Co-authored-by: Martin Holst Swende <martin@swende.se>
Co-authored-by: gary rong <garyrong0905@gmail.com>
Co-authored-by: Alex Willmer <alex@moreati.org.uk>
Co-authored-by: meowsbits <45600330+meowsbits@users.noreply.github.com>
Co-authored-by: Felix Lange <fjl@twurst.com>
Co-authored-by: rene <41963722+renaynay@users.noreply.github.com>
Co-authored-by: Ha ĐANG <dvietha@gmail.com>
Co-authored-by: Hanjiang Yu <42531996+de1acr0ix@users.noreply.github.com>
Co-authored-by: ligi <ligi@ligi.de>
Co-authored-by: Wenbiao Zheng <delweng@gmail.com>
Co-authored-by: Adam Schmideg <adamschmideg@users.noreply.github.com>
Co-authored-by: Jeff Wentworth <jeff@curvegrid.com>
Co-authored-by: Paweł Bylica <chfast@gmail.com>
Co-authored-by: ucwong <ucwong@126.com>
Co-authored-by: Marius van der Wijden <m.vanderwijden@live.de>
Co-authored-by: Luke Champine <luke.champine@gmail.com>
Co-authored-by: Boqin Qin <Bobbqqin@gmail.com>
Co-authored-by: William Morriss <wjmelements@gmail.com>
Co-authored-by: Guillaume Ballet <gballet@gmail.com>
Co-authored-by: Raw Pong Ghmoa <58883403+q9f@users.noreply.github.com>
Co-authored-by: Felföldi Zsolt <zsfelfoldi@gmail.com>
2020-04-19 17:31:47 +00:00
```
2021-05-26 10:35:39 +00:00
**gRPC ports**: `9090` erigon, `9091` sentry, `9092` consensus engine, `9093` snapshot downloader, `9094` TxPool
2021-04-30 15:09:03 +00:00
2021-07-18 08:22:35 +00:00
Supported JSON-RPC calls ([eth](./cmd/rpcdaemon/commands/eth_api.go), [debug ](./cmd/rpcdaemon/commands/debug_api.go )
, [net ](./cmd/rpcdaemon/commands/net_api.go ), [web3 ](./cmd/rpcdaemon/commands/web3_api.go )):
2020-09-14 06:59:07 +00:00
2021-07-18 08:22:35 +00:00
For a details on the implementation status of each
command, [see this table ](./cmd/rpcdaemon/README.md#rpc-implementation-status ).
2020-08-29 14:37:05 +00:00
2021-03-23 07:28:04 +00:00
### Run all components by docker-compose
2020-08-01 07:39:04 +00:00
2021-05-26 10:35:39 +00:00
Next command starts: Erigon on port 30303, rpcdaemon 8545, prometheus 9090, grafana 3000
2020-08-01 07:39:04 +00:00
2021-09-01 15:53:01 +00:00
```sh
2021-07-18 08:22:35 +00:00
make docker-compose
2021-09-01 15:53:01 +00:00
# or
2021-07-18 08:22:35 +00:00
XDG_DATA_HOME=/preferred/data/folder make docker-compose
2020-08-01 07:39:04 +00:00
```
2016-07-12 09:51:31 +00:00
Pruning for: exec, log_index, tx_lookup, history stages (#2399)
* Pruning for: exec, log_index, tx_lookup, history stages
* Pruning for: exec, log_index, tx_lookup, history stages
* Pruning for: exec, log_index, tx_lookup, history stages
* Pruning for: exec, log_index, tx_lookup, history stages
* add tvm flag
* save
* db migration for storage mode
add flag --prune=
remove flag --storage-mode=
add flag --experiments=tevm,...
rename integration set_storage_mode to set_prune
* fix
* forward move of stages must skip everything before PruneTo
* keep in db progress of prune method
* keep in db progress of prune method
* simplify logs
* simplify logs
* simplify logs
* fix test
* simplify logs
* simplify logs
* simplify logs
* simplify logs
* remove callTraceSet as dupsort
use etl transform for txlookup prune
remove some logs
* cleanup tests a bit
* print_stages and eth_sync to show prune progress
* fix print_stages
* add readme about --prune.to flag
* more docs
* add --prune.history.older and other flags support
* fix migration on empty db
* better toString
* better toString
2021-07-20 20:03:19 +00:00
Makefile creates the initial directories for erigon, prometheus and grafana. The PID namespace is shared between erigon
and rpcdaemon which is required to open Erigon's DB from another process (RPCDaemon local-mode).
2021-07-18 08:22:35 +00:00
See: https://github.com/ledgerwatch/erigon/pull/2392/files
Windows support for docker-compose is not ready yet. Please help us with .ps1 port
2021-03-23 07:28:04 +00:00
### Grafana dashboard
`docker-compose up prometheus grafana` , [detailed docs ](./cmd/prometheus/Readme.md ).
Pruning for: exec, log_index, tx_lookup, history stages (#2399)
* Pruning for: exec, log_index, tx_lookup, history stages
* Pruning for: exec, log_index, tx_lookup, history stages
* Pruning for: exec, log_index, tx_lookup, history stages
* Pruning for: exec, log_index, tx_lookup, history stages
* add tvm flag
* save
* db migration for storage mode
add flag --prune=
remove flag --storage-mode=
add flag --experiments=tevm,...
rename integration set_storage_mode to set_prune
* fix
* forward move of stages must skip everything before PruneTo
* keep in db progress of prune method
* keep in db progress of prune method
* simplify logs
* simplify logs
* simplify logs
* fix test
* simplify logs
* simplify logs
* simplify logs
* simplify logs
* remove callTraceSet as dupsort
use etl transform for txlookup prune
remove some logs
* cleanup tests a bit
* print_stages and eth_sync to show prune progress
* fix print_stages
* add readme about --prune.to flag
* more docs
* add --prune.history.older and other flags support
* fix migration on empty db
* better toString
* better toString
2021-07-20 20:03:19 +00:00
### Prune old data
Disabled by default. To enable see `./build/bin/erigon --help` for flags `--prune`
2021-06-06 13:02:15 +00:00
FAQ
================
### How much RAM do I need
2021-11-16 08:29:42 +00:00
- Baseline (ext4 SSD): 16Gb RAM sync takes 6 days, 32Gb - 5 days, 64Gb - 4 days
2021-06-06 13:27:01 +00:00
- +1 day on "zfs compression=off". +2 days on "zfs compression=on" (2x compression ratio). +3 days on btrfs.
2021-07-18 08:22:35 +00:00
- -1 day on NVMe
2021-06-06 13:02:15 +00:00
Detailed explanation: [./docs/programmers_guide/db_faq.md ](./docs/programmers_guide/db_faq.md )
2021-08-23 04:12:20 +00:00
### Default Ports and Protocols / Firewalls?
#### `erigon` ports
2021-09-02 05:55:04 +00:00
2021-08-23 04:12:20 +00:00
| Port | Protocol | Purpose | Expose |
|:-----:|:---------:|:----------------:|:-------:|
| 30303 | TCP & UDP | eth/66 peering | Public |
| 9090 | TCP | gRPC Connections | Private |
2021-09-02 05:55:04 +00:00
Typically 30303 and 30304 are exposed to the internet to allow incoming peering connections. 9090 is exposed only
internally for rpcdaemon or other connections, (e.g. rpcdaemon -> erigon)
2021-08-23 04:12:20 +00:00
#### `rpcdaemon` ports
2021-09-02 05:55:04 +00:00
2022-03-02 13:58:46 +00:00
| Port | Protocol | Purpose | Expose |
|:-----:|:---------:|:------------------:|:-------:|
| 8545 | TCP | HTTP & WebSockets | Private |
| 8550 | TCP | HTTP | Private |
| 8551 | TCP | HTTP with JWS auth | Private |
2021-08-23 04:12:20 +00:00
2022-01-25 16:44:35 +00:00
Typically 8545 is exposed only internally for JSON-RPC queries. Both HTTP and WebSocket connections are on the same port.
2022-03-02 13:58:46 +00:00
Typically 8550 (unauthenticated) and 8551 (authenticated) are exposed only internally for the Engine API JSON-RPC queries.
2021-08-23 04:12:20 +00:00
#### `sentry` ports
2021-09-02 05:55:04 +00:00
2021-08-23 04:12:20 +00:00
| Port | Protocol | Purpose | Expose |
|:-----:|:---------:|:----------------:|:-------:|
| 30303 | TCP & UDP | Peering | Public |
| 9091 | TCP | gRPC Connections | Private |
2021-09-02 05:55:04 +00:00
Typically a sentry process will run one eth/xx protocl (e.g. eth/66) and will be exposed to the internet on 30303. Port
9091 is for internal gRCP connections (e.g erigon -> sentry)
2021-08-23 04:12:20 +00:00
#### Other ports
2021-09-02 05:55:04 +00:00
2021-08-23 04:12:20 +00:00
| Port | Protocol | Purpose | Expose |
|:----:|:--------:|:-------:|:-------:|
| 6060 | TCP | pprof | Private |
| 6060 | TCP | metrics | Private |
2021-09-02 05:55:04 +00:00
Optional flags can be enabled that enable pprof or metrics (or both) - however, they both run on 6060 by default, so
you'll have to change one if you want to run both at the same time. use `--help` with the binary for more info.
2021-08-23 04:12:20 +00:00
2021-09-02 05:55:04 +00:00
Reserved for future use: **gRPC ports** : `9092` consensus engine, `9093` snapshot downloader, `9094` TxPool
2021-08-23 04:12:20 +00:00
2021-09-17 03:31:20 +00:00
### How to get diagnostic for bug report?
- Get stack trace: `kill -SIGUSR1 <pid>` , get trace and stop: `kill -6 <pid>`
- Get CPU profiling: add `--pprof flag`
run `go tool pprof -png http://127.0.0.1:6060/debug/pprof/profile\?seconds\=20 > cpu.png`
- Get RAM profiling: add `--pprof flag`
run `go tool pprof -inuse_space -png http://127.0.0.1:6060/debug/pprof/heap > mem.png`
2021-11-09 10:48:16 +00:00
### How to run local devnet?
< code > 🔬 Detailed explanation is [here ](/DEV_CHAIN.md ).</ code >
2021-09-17 03:31:20 +00:00
2020-08-04 08:03:59 +00:00
Getting in touch
================
2016-07-12 09:51:31 +00:00
2021-05-23 14:50:44 +00:00
### Erigon Discord Server
2016-07-12 09:51:31 +00:00
2021-07-18 08:22:35 +00:00
The main discussions are happening on our Discord server. To get an invite, send an email to `tg [at] torquem.ch` with
your name, occupation, a brief explanation of why you want to join the Discord, and how you heard about Erigon.
2016-07-12 09:51:31 +00:00
2021-03-23 07:28:04 +00:00
### Reporting security issues/concerns
2016-07-12 09:51:31 +00:00
2020-07-30 11:04:46 +00:00
Send an email to `security [at] torquem.ch` .
2016-07-12 09:51:31 +00:00
2021-03-23 07:28:04 +00:00
### Team
2016-07-12 09:51:31 +00:00
2021-05-22 09:39:06 +00:00
Core contributors (in alpabetical order of first names):
* Alex Sharov ([AskAlexSharov](https://twitter.com/AskAlexSharov))
2016-07-12 09:51:31 +00:00
2020-07-30 11:04:46 +00:00
* Alexey Akhunov ([@realLedgerwatch](https://twitter.com/realLedgerwatch))
2016-07-12 09:51:31 +00:00
2021-05-23 14:50:44 +00:00
* Andrea Lanfranchi([@AndreaLanfranchi](https://github.com/AndreaLanfranchi))
2020-07-30 11:04:46 +00:00
* Andrew Ashikhmin ([yperbasis](https://github.com/yperbasis))
2016-07-12 09:51:31 +00:00
2021-05-23 14:50:44 +00:00
* Artem Vorotnikov ([vorot93](https://github.com/vorot93))
2021-05-22 09:39:06 +00:00
2020-07-30 11:04:46 +00:00
* Boris Petrov ([b00ris](https://github.com/b00ris))
2016-07-12 09:51:31 +00:00
2020-07-30 11:04:46 +00:00
* Eugene Danilenko ([JekaMas](https://github.com/JekaMas))
2013-12-26 12:29:45 +00:00
2020-07-30 11:04:46 +00:00
* Igor Mandrigin ([@mandrigin](https://twitter.com/mandrigin))
2015-03-02 18:44:29 +00:00
2021-05-23 14:50:44 +00:00
* Giulio Rebuffo ([Giulio2002](https://github.com/Giulio2002))
2015-03-02 18:44:29 +00:00
2020-10-22 15:44:28 +00:00
* Thomas Jay Rush ([@tjayrush](https://twitter.com/tjayrush))
2020-10-22 15:40:37 +00:00
2020-07-30 11:04:46 +00:00
Thanks to:
2014-02-08 21:16:11 +00:00
2021-05-26 10:35:39 +00:00
* All contributors of Erigon
2015-03-02 18:44:29 +00:00
2020-07-30 11:04:46 +00:00
* All contributors of Go-Ethereum
2016-04-29 14:40:19 +00:00
2021-07-18 08:22:35 +00:00
* Our special respect and graditude is to the core team of [Go-Ethereum ](https://github.com/ethereum/go-ethereum ). Keep
up the great job!
2014-01-11 14:27:08 +00:00
2020-07-30 11:04:46 +00:00
Happy testing! 🥤
2020-08-04 08:03:59 +00:00
Known issues
============
2021-06-16 10:57:58 +00:00
### `htop` shows incorrect memory usage
2020-08-04 08:03:59 +00:00
2021-07-18 08:22:35 +00:00
Erigon's internal DB (MDBX) using `MemoryMap` - when OS does manage all `read, write, cache` operations instead of
Application
([linux](https://linux-kernel-labs.github.io/refs/heads/master/labs/memory_mapping.html)
, [windows ](https://docs.microsoft.com/en-us/windows/win32/memory/file-mapping ))
2020-08-04 08:03:59 +00:00
2021-07-18 08:22:35 +00:00
`htop` on column `res` shows memory of "App + OS used to hold page cache for given App", but it's not informative,
because if `htop` says that app using 90% of memory you still can run 3 more instances of app on the same machine -
because most of that `90%` is "OS pages cache".
OS automatically free this cache any time it needs memory. Smaller "page cache size" may not impact performance of
Erigon at all.
2020-08-04 08:03:59 +00:00
2021-05-27 13:54:55 +00:00
Next tools show correct memory usage of Erigon:
2021-07-18 08:22:35 +00:00
- `vmmap -summary PID | grep -i "Physical footprint"` . Without `grep` you can see details
- `section MALLOC ZONE column Resident Size` shows App memory usage, `section REGION TYPE column Resident Size`
shows OS pages cache size.
- `Prometheus` dashboard shows memory of Go app without OS pages cache (`make prometheus`, open in
browser `localhost:3000` , credentials `admin/admin` )
2020-08-04 08:03:59 +00:00
- `cat /proc/<PID>/smaps`
2021-07-18 08:22:35 +00:00
Erigon uses ~4Gb of RAM during genesis sync and ~1Gb during normal work. OS pages cache can utilize unlimited amount of
memory.
2020-08-04 08:03:59 +00:00
2021-07-18 08:22:35 +00:00
**Warning:** Multiple instances of Erigon on same machine will touch Disk concurrently, it impacts performance - one of
main Erigon optimisations: "reduce Disk random access".
"Blocks Execution stage" still does much random reads - this is reason why it's slowest stage. We do not recommend run
multiple genesis syncs on same Disk. If genesis sync passed, then it's fine to run multiple Erigon on same Disk.
2021-03-23 07:28:04 +00:00
2021-04-15 04:50:42 +00:00
### Blocks Execution is slow on cloud-network-drives
2021-05-18 06:14:24 +00:00
Please read https://github.com/ledgerwatch/erigon/issues/1516#issuecomment-811958891
2021-07-18 08:22:35 +00:00
In short: network-disks are bad for blocks execution - because blocks execution reading data from db non-parallel
non-batched way.
2021-08-19 08:29:28 +00:00
### Filesystem's background features are expensive
For example: btrfs's autodefrag option - may increase write IO 100x times
2021-09-21 10:35:28 +00:00
### Gnome Tracker can kill Erigon
2021-09-25 15:28:25 +00:00
[Gnome Tracker ](https://wiki.gnome.org/Projects/Tracker ) - detecting miners and kill them.
