mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2024-12-24 20:47:16 +00:00
9324d83cb2
* - handle cursor.Prefix on server - move state reports to KV interface * add CmdCursorSeekKey * tests for abstract_kv * avoid reading configs of databases * avoid reading configs of databases * make linter happy * make linter happy * cleanup * port badger features from original implementation * try to fix test * try to fix test * .Close() don't return error anymore - defer friendly * try to enable badger now * try to enable badger now * badger can't run on CI yet * badger can't run on CI yet * re-run ci * skip ctx cancelation for badger |
||
|---|---|---|
| .. | ||
| commands | ||
| .gitignore | ||
| main.go | ||
| Readme.md | ||
Getting Started
In order to build and run turbo-geth node together with RPC daemon, you need to do the following:
- Clone turbo-geth repo
- Build it by running
make - Start it (it will start syncing to the mainnet) like this:
./build/bin/geth --remote-db-listen-addr localhost:9999
- Look out for this in the console/log file:
INFO [11-30|18:34:12.687] Remote DB interface listening on address=localhost:9999
- In another terminal/tab, build RPC daemon:
make rpcdaemon
- Run it:
./build/bin/rpcdaemon --rpcapi eth
By default, it will connect to the turbo-geth node on the localhost:9999, but this can be changed via command line parameters. Note that it does not matter in which order you start these two processes, RPC daemon will only try to connect to turbo-geth node when serving its first RPC request, and then it will reconnect if connection is lost (for example, if you restart turbo-geth)
7. Try eth_blockNumber call. In another console/tab, use curl to make RPC call:
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_blockNumber", "params": [], "id":1}' localhost:854
- It should return something like this (depending on how far your turbo-geth node has synced):
{"jsonrpc":"2.0","id":1,"result":823909}