status-go/rpc
Igor Sirotin e938635d04
chore_: get version with go generate (#6014)
* chore_: get version with go generate

* fix_: test-functional

* fix_: trip space in version and gitcommit

* fix_: TestUserAgent
2024-11-03 00:47:15 +00:00
..
chain chore_: replace geth logger with zap logger (#5962) 2024-10-28 20:54:17 +00:00
network chore_: completely remove goerli from the code 2024-10-21 17:30:51 +02:00
README.md chore_: remove rpc doc automation (#5893) 2024-09-30 17:47:29 +01:00
call_raw.go chore_: replace geth logger with zap logger (#5962) 2024-10-28 20:54:17 +00:00
call_raw_test.go feat: Rpc client manage multiple eth client (#2359) 2021-09-22 13:49:20 -04:00
client.go chore_: get version with go generate (#6014) 2024-11-03 00:47:15 +00:00
client_test.go chore_: get version with go generate (#6014) 2024-11-03 00:47:15 +00:00
provider.go chore_: replace geth logger with zap logger (#5962) 2024-10-28 20:54:17 +00:00
route.go synchronize display name (#2989) 2022-12-29 14:16:19 +08:00
route_test.go Revert "test: bump go-libp2p" 2024-01-18 20:29:33 +00:00
verif_proxy.go Add LoginAccount endpoint 2023-06-01 10:05:11 +01:00
verif_proxy_test.go feat_: RPC providers detailed statuses #5923 (#5924) 2024-10-15 19:59:17 +04: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.