Substrate JSON RPC Gateway.

This is a generalized JSON RPC proxy server with features specifically designed for Substrate RPC and Ethereum RPC.

Pull vendors: git submodule update --init --recursive

Quick start: cargo run -- --config config.yml

This will run a proxy server with config.yml as the configuration file.

Run with RUSTFLAGS="--cfg tokio_unstable" to enable tokio-console

• RUST_LOG
  • Log level. Default: info.
• PORT
  • Override port configuration in config file.
• LOG_FORMAT
  • Log format. Default: full.
  • Options: full, pretty, json, compact

Subway is build with middleware pattern.

Method Middlewares

• Cache
  • Cache responses from upstream middleware.
• Call
  • Forward requests to upstream servers.
• Inject Params (Substrate)
  • For Substrate RPC
  • Inject optional blockAt or blockHash params to requests to ensure downstream middleware such as cache can work properly.
• Inject Params (Ethereum)
  • For Ethereum RPC
  • Inject optional defaultBlock parameter to requests to ensure downstream middleware such as cache can work properly.
• Subscription
  • Forward requests to upstream servers.
  • TODO: Merge duplicated subscriptions.
• TODO: Rate Limit
  • Rate limit requests from downstream middleware.
• TODO: Parameter filter
  • Deny requests with invalid parameters.

• Advance JSON RPC Client
  • Supports multiple upstream servers and rotate & reconnect on failure.
  • TODO: Load balance requests to upstream servers.
• Batch Request
  • TODO: Process requests individually so they can be cached properly by downstream middlewares.
  • TODO: Limit batch size, request size and response size.
• TODO: Metrics
  • Getting insights of the RPC calls and server performance.

To run all benchmarks:

cargo bench

It's also possible to run individual benchmarks by:

cargo bench --bench bench ws_round_trip

This middleware will intercept all method request/responses and compare the result directly with healthy endpoint responses. This is useful for debugging to make sure the returned values are as expected. You can enable validate middleware on your config file.

middlewares:
  methods:
    - validate

NOTE: Keep in mind that if you place validate middleware before inject_params you may get false positive errors because the request will not be the same.

Ignored methods can be defined in extension config:

extensions:
  validator:
    ignore_methods:
      - system_health
      - system_name
      - system_version
      - author_pendingExtrinsics