History

Sale Djenic 752d1a47f6 fix: networks get updated from a single place now, network.Manager Runtime networks related env vars are being in use now, updating necessary rpc urls.		2023-11-08 11:31:15 +01:00
..
chain	Scanning of ERC20 tail of transfers history	2023-10-01 10:09:11 +02:00
network	fix: networks get updated from a single place now, network.Manager	2023-11-08 11:31:15 +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	Scanning of ERC20 tail of transfers history	2023-10-01 10:09:11 +02:00
client_test.go	fix(tests): moved test db setup to a common place 't/helpers', created	2023-08-18 09:00:56 +02: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	Block some JSON-RPC methods completely	2018-08-02 09:07:55 +02:00
verif_proxy.go	Add LoginAccount endpoint	2023-06-01 10:05:11 +01:00
verif_proxy_test.go	Add LoginAccount endpoint	2023-06-01 10:05:11 +01:00

rpc

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.

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