status-go/rpc
Stefan a6d553c937 fix(wallet) ClientWithFallback handling state errors required by BH
The "not found" and "no contract" expected error is caught and wrapped
by ClientWithFallback. The fetching of balance history of next blocks
is aborted which is not desired.

Fix by not treating the error as a connection error in
ClientWithFallback.
2023-05-02 12:07:06 +02:00
..
chain fix(wallet) ClientWithFallback handling state errors required by BH 2023-05-02 12:07:06 +02:00
network feat: fallback rpc endpoint 2023-02-28 08:43:57 +01:00
README.md
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 fix: collectible status event 2023-03-31 19:22:53 +02:00
client_test.go feat: make kdf iterations configurable when creating a multiaccount (#2796) 2022-09-27 16:27:20 -04:00
doc.go synchronize display name (#2989) 2022-12-29 14:16:19 +08:00
route.go synchronize display name (#2989) 2022-12-29 14:16:19 +08:00
route_test.go

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