status-go

History

Mikhail Rogachev 1ba4b86c7e feat_: Add WS settings to the node config (#5346 ) * feat_: add ability to enable http and ws connections from the client app * feat_: add websocket option for api config * fix_: use new api options in statusd * chore_: add test for `overrideApiConfig`		2024-06-26 16:33:22 +02:00
..
README.md	…
get_status_node.go	feat_: implement connector service (#5375 ) (#5403 )	2024-06-24 07:29:40 -07:00
geth_node.go	feat_: Add WS settings to the node config (#5346 )	2024-06-26 16:33:22 +02:00
geth_node_api_test.go	Feat/sync customization color (#3702 )	2023-07-18 21:35:06 +08:00
geth_node_test.go	…
geth_status_node_test.go	fix(wallet) fix pending transactions by using the wallet DB	2023-08-23 12:34:59 +02:00
rpc.go	…
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	feat_: implement connector service (#5375 ) (#5403 )	2024-06-24 07:29:40 -07: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