status-go

History

Andrey Bocharnikov f07e3a83a3 fix(wallet)_: Ignore chain down notifications when connection is lost fixes #21071		2024-09-24 17:26:33 +04:00
..
README.md	Upgrade to london signer and cleanup	2021-07-20 10:57:38 +02:00
get_status_node.go	fix_: send accounts event on handling backed up accounts (#5739 )	2024-08-31 00:58:03 +05:30
geth_node.go	Feat: implement connector service for browser plugin (#5433 )	2024-07-18 17:30:10 +02:00
geth_node_api_test.go	Feat/sync customization color (#3702 )	2023-07-18 21:35:06 +08:00
geth_node_test.go	Remove Ropsten and Rinkeby test networks	2022-10-24 14:17:46 +02:00
geth_status_node_test.go	refactor_: remove status-im/rendezvous (#5685 )	2024-08-22 13:12:37 -04:00
rpc.go	bump version	2021-07-20 10:57:38 +02:00
status_node_rpc_client_test.go	fix(wallet) fix pending transactions by using the wallet DB	2023-08-23 12:34:59 +02:00
status_node_services.go	fix(wallet)_: Ignore chain down notifications when connection is lost	2024-09-24 17:26:33 +04:00

A Status node is a container of services. These services are passed to geth and registered with geth as APIs and Protocols.

Status node manages all the services and the geth node.

Status node is managed by api/geth_backend.go

So:

GethBackend manages StatusNode, StatusNode manages GethNode