status-go

History

frank a2ed1b78dd feat:support backup/sync ens name (#3415 )		2023-04-26 23:37:18 +08:00
..
README.md	Upgrade to london signer and cleanup	2021-07-20 10:57:38 +02:00
get_status_node.go	Changed connection state now correctly propagates to messenger (#3310 )	2023-03-20 11:52:24 +00:00
geth_node.go	revert changes to geth_node.go	2023-02-24 07:33:10 +08:00
geth_node_api_test.go	tests: updated due to updating old accounts as a part of migration process	2023-03-28 16:19:27 +02:00
geth_node_test.go	Remove Ropsten and Rinkeby test networks	2022-10-24 14:17:46 +02:00
geth_status_node_test.go	tests: updated due to updating old accounts as a part of migration process	2023-03-28 16:19:27 +02:00
rpc.go	bump version	2021-07-20 10:57:38 +02:00
status_node_rpc_client_test.go	tests: updated due to updating old accounts as a part of migration process	2023-03-28 16:19:27 +02:00
status_node_services.go	feat:support backup/sync ens name (#3415 )	2023-04-26 23:37:18 +08: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