Go-ethereum installed and problem persists

[acmLL]

Hi,

I have done the steps found here: https://geth.ethereum.org/docs/getting-started/installing-geth.

With the command: heth --help, I get:

NAME:
geth - the go-ethereum command line interface

Copyright 2013-2021 The go-ethereum Authors

USAGE:
geth [options] [command] [command options] [arguments...]

VERSION:
1.10.16-stable-20356e57

COMMANDS:
ETC.

But when I run: efcfuzz --timeout 300 --live-state 0xfffF8D17CB019E0825c478c666B251A7099df3FD
2023-04-27 09:33:06 413e7772091d INFO launching EF/CF [2743 /efcf]
2023-04-27 09:33:06 413e7772091d WARNING Could not locate fuzzing directory mount point [2743 /efcf]
2023-04-27 09:33:06 413e7772091d WARNING Your fuzzing directory '/tmp/efcf' is not located on a ramdisk - we recommend to use a big tmpfs or zram device for the fuzzing directory. [2743 /efcf]
2023-04-27 09:33:06 413e7772091d WARNING encountered exception 'HTTPConnectionPool(host='localhost', port=8545): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f10717ac940>: Failed to establish a new connection: [Errno 111] Connection refused'))' while performing RPC call 'eth_blockNumber' with [] [2743 /efcf]
2023-04-27 09:33:06 413e7772091d ERROR Failed to get blockNumber from go-ethereum url http://localhost:8545 [2743 /efcf]
2023-04-27 09:33:06 413e7772091d CRITICAL no go-etherum node available [2743 /efcf]

What can I do now?

[f0rki]

EF/CF does not launch go-ethereum for you. You need to do that yourself. Just installing geth is not enough.

So the way it works is you need to launch go ethereum as a full node (--syncmode full) and synchronize it with the ethereum network. Then add --http and --http.api admin,debug,eth,miner,net,personal,txpool,web3 to the geth command line to enable EF/CF accessing the debug_storageRangeAt RPC API via http. You should probably bind the http RPC API to localhost.

If you want to access anything but the "latest" blockchain state, you need to run an archive node.

Note that synchronzing a full node can take quite a while and requires quite a bit of disk space.

Note that using erigon might help with disk space and sync efficiency, but setup is a bit more tricky.