squid3

Caching Proxy for EVM RPC.

• Proxy understand batch requests and can cache individual requests inside the batch

• Proxy supports latest to cache it as block number

• Cache is controlled:

  • cach.ttl : time to live for response.
  • cache.latest : time to live to latest block response. Special case which can control how Cache may lag behind. It should be generally set to the Block interval (e.g. 12000 for Ethereum)
  • cache.gc: Garbage Collection for expired requests

• Multiple RPC nodes Pool:

  • lb : load-balancing round-robin with periodic retry of failed
  • sticky: stays on healthy node and does not fail-back

The size of cache is not limited, use cache.gc option

Authorization

Url key

Simple style url suffix configured with --api.key=<KEY>

./run-rpc3.sh --api.key=1111

curl http://localhost:8080/api/v1/rpc3/1111

Run

Run with cache 12 seconds

./run-rpc3.sh --pool=http://geth:8545 --cache.ttl=120000

Run with 4 Threads pool

./run-rpc3.sh --pool=http://geth:8545 --proxy.threads=4

Run with Round-robin load-balancing Nodes Pool

./run-rpc3.sh --pool=lb://http://geth-1:8545,http://geth-2:8545

It is possible to specify rpc nodes as free arguments:

./run-rpc3.sh --pool=lb:// http://geth-1 http://reth-2 http://node-3

Testing fail-over scenario

This scenario simulates the connection failure of the first node and fail-over to the second. Proxy must stay on the healthy node as long as possible.

All network and protocol failures are retry-enabled with: --rpc.retry=3 --rpc.delay=1000

Run one HTTP pong:

./http-server.sh RSP_Batch_1.json

Run proxy with One node failure:

./run-rpc3.sh --pool=http://localhost:8000,http://localhost:8300

Execute request:

./rpc3-post.sh REQ_Batch_latest-Tx.json

Testing retry

This scenario simulates first node 429 and fail-over to the second node

Run HTTP server with 429 Response

CODE=429 ./http-server.sh RSP_Batch_1.json

./run-rpc3.sh --pool=http://localhost:8300,http://geth1:8545

Execute request:

./rpc3-post.sh REQ_Batch_latest-Tx.json

Testing Failed Batch resposnse

This scenario simulates all 32000 in batch reponse and fail-over with retry

PORT=8300 ./http-server.sh RSP_Batch_error_32000.json
PORT=8301 ./http-server.sh RSP_Batch_error_32000.json

./run-rpc3.sh --pool=sticky:// http://localhost:8300 http://localhost:8301

Execute request:

./rpc3-post.sh REQ_Batch_latest-Tx.json