tornadocontrib/ web3-proxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
105 Commits 1 Branch 0 Tags 12 MiB
Rust 97%
Shell 2.4%
Dockerfile 0.5%
Go to file
Bryan Stitt 10cd52f19a this works but i dont like it 2022-05-12 03:54:42 +00:00
config remove debug logs 2022-05-12 01:38:27 +00:00
linkedhashmap quick lru cache 2022-05-05 19:07:09 +00:00
web3-proxy this works but i dont like it 2022-05-12 03:54:42 +00:00
wrk move data files 2022-05-06 01:40:43 +00:00
.dockerignore docker-compose 2022-05-06 01:57:37 +00:00
.gitignore move data files 2022-05-06 01:40:43 +00:00
Cargo.lock handle batched requests 2022-05-11 23:51:03 +00:00
Cargo.toml first pass at caching 2022-05-05 19:06:03 +00:00
Dockerfile new default port 2022-05-06 06:33:29 +00:00
LICENSE add LICENSE 2022-03-04 19:56:05 -08:00
README.md Update README.md 2022-05-06 18:53:16 -07:00
TODO.md set overall max inside the lock 2022-05-06 20:44:12 +00:00
docker-compose.common.yml docker-compose 2022-05-06 01:57:37 +00:00
docker-compose.yml docker-compose 2022-05-06 01:57:37 +00:00

README.md

web3-proxy

quick and dirty proxy for ethereum rpcs (or similar)

Signed transactions are sent to the configured private RPC (eden, flashbots, etc.). All other requests are sent to an RPC server on the latest block (alchemy, moralis, rivet, your own node, or one of many other providers).

cargo run --release -- --help

    Finished release [optimized] target(s) in 0.13s
     Running `target/release/web3-proxy --help`
Usage: web3-proxy [--listen-port <listen-port>] [--rpc-config-path <rpc-config-path>]

Reach new heights.

Options:
  --listen-port     what port the proxy should listen on
  --rpc-config-path what port the proxy should listen on
  --help            display usage information

cargo run --release

curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"web3_clientVersion","params":[],"id":67}' 127.0.0.1:8544/eth

Flame Graphs

$ cat /proc/sys/kernel/kptr_restrict
1
$ echo 0 |sudo tee /proc/sys/kernel/kptr_restrict
0
$ CARGO_PROFILE_RELEASE_DEBUG=true cargo flamegraph

Load Testing

Test the proxy:

wrk -s ./data/wrk/getBlockNumber.lua -t12 -c400 -d30s --latency http://127.0.0.1:8544
wrk -s ./data/wrk/getLatestBlockByNumber.lua -t12 -c400 -d30s --latency http://127.0.0.1:8544

Test geth:

wrk -s ./data/wrk/getBlockNumber.lua -t12 -c400 -d30s --latency http://127.0.0.1:8545
wrk -s ./data/wrk/getLatestBlockByNumber.lua -t12 -c400 -d30s --latency http://127.0.0.1:8545

Test erigon:

wrk -s ./data/wrk/getBlockNumber.lua -t12 -c400 -d30s --latency http://127.0.0.1:8945
wrk -s ./data/wrk/getLatestBlockByNumber.lua -t12 -c400 -d30s --latency http://127.0.0.1:8945

Todo

  • simple proxy
  • better locking. when lots of requests come in, we seem to be in the way of block updates
  • proper logging
  • load balance between multiple RPC servers
  • support more than just ETH
  • option to disable private rpc and send everything to primary
  • health check nodes by block height
  • measure latency to nodes
  • Dockerfile
  • testing getLatestBlockByNumber is not great because the latest block changes and so one run is likely to be different than another
  • if a request gets a socket timeout, try on another server
    • maybe always try at least two servers in parallel? and then return the first? or only if the first one doesn't respond very quickly?