status-go

History

Richard Ramos a15c27c588 feat: unified chat API pt. 3 (#2535 )		2022-03-03 15:37:07 -04:00
..
README.md	Upgrade to london signer and cleanup	2021-07-20 10:57:38 +02:00
get_status_node.go	fix: code review	2022-03-03 15:37:07 -04:00
geth_node.go	linting and remove unused code	2021-07-20 10:57:38 +02:00
geth_node_api_test.go	feat: desktop browser provider (#2465 )	2021-12-21 11:44:37 -04:00
geth_node_test.go	fix topic pool tests	2021-07-20 10:57:38 +02:00
geth_status_node_test.go	feat: desktop browser provider (#2465 )	2021-12-21 11:44:37 -04:00
rpc.go	bump version	2021-07-20 10:57:38 +02:00
status_node_rpc_client_test.go	feat: desktop browser provider (#2465 )	2021-12-21 11:44:37 -04:00
status_node_services.go	feat: unified chat API pt. 3 (#2535 )	2022-03-03 15:37:07 -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