status-go/rpc
Richard Ramos ee41e30881
feat: extract node config from settings to individual tables (#2470)
2022-01-12 16:04:43 -04:00
..
network feat: extract node config from settings to individual tables (#2470) 2022-01-12 16:04:43 -04:00
README.md [#856] move geth subpackages to root level (#1007) 2018-06-08 13:29:50 +02:00
call_raw.go feat: Rpc client manage multiple eth client (#2359) 2021-09-22 13:49:20 -04:00
call_raw_test.go feat: Rpc client manage multiple eth client (#2359) 2021-09-22 13:49:20 -04:00
client.go feat: extract node config from settings to individual tables (#2470) 2022-01-12 16:04:43 -04:00
client_test.go feat: extract node config from settings to individual tables (#2470) 2022-01-12 16:04:43 -04:00
doc.go [#856] move geth subpackages to root level (#1007) 2018-06-08 13:29:50 +02:00
route.go Add some eip 1559 related rpc methods to router 2021-07-20 10:57:38 +02:00
route_test.go Block some JSON-RPC methods completely 2018-08-02 09:07:55 +02:00

README.md

rpc GoDoc

Package rpc - JSON-RPC client with custom routing.

Download:

go get github.com/status-im/status-go/rpc

Package rpc - JSON-RPC client with custom routing.

Package rpc implements status-go JSON-RPC client and handles requests to different endpoints: upstream or local node.

Every JSON-RPC request coming from either JS code or any other part of status-go should use this package to be handled and routed properly.

Routing rules are following:

  • if Upstream is disabled, everything is routed to local ethereum-go node
  • otherwise, some requests (from the list, see below) are routed to upstream, others - locally.

List of methods to be routed is currently available here: https://docs.google.com/spreadsheets/d/1N1nuzVN5tXoDmzkBLeC9_mwIlVH8DGF7YD2XwxA8BAE/edit#gid=0

Note, upon creation of a new client, it ok to be offline - client will keep trying to reconnect in background.


Automatically generated by autoreadme on 2017.09.18