mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2024-12-25 13:07:17 +00:00
c5ffc971c5
* badger v2 investigation * buf pool - use native New method and avoid double checks * db.Open prototype * db.Tx/Bucket/Cursor prototypes * Chained config * Item concept added * save changes to test on master * make hack resumable * Design document v0 * Cursor concept * less brackets syntax of cursor builder * benchmarks * cleanup fs * test for context cancelations * test for context cancelations * test for cursor.Prefix option * add ForEachKey method * add ForEachKey method * add naming explanation * experiment of non-pointers cursor/bucket * .Bucket() and .Cursor() doesn't returns error * .Bucket() and .Cursor() doesn't returns error * .Bucket() and .Cursor() doesn't returns error * remove CursorOpts concept * more test-cases * simplify open api * Tx, Bucket, Cursor - now are interfaces * Tx, Bucket, Cursor - now are interfaces * switch to interfaces * rebase master Co-authored-by: alex.sharov <alex.sharov@lazada.com> |
||
---|---|---|
.. | ||
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}