status-go

History

richΛrd 56cc5c96c5 feat_: bump go-waku to introduce new keep alive interval (#5484 ) - Also renames the existing keepAliveInterval to randomPeerKeepAliveInterval, and uses time.Duration instead of int		2024-07-11 14:36:34 -04:00
..
README.md	Upgrade to london signer and cleanup	2021-07-20 10:57:38 +02:00
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	Remove Ropsten and Rinkeby test networks	2022-10-24 14:17:46 +02:00
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	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	feat_: bump go-waku to introduce new keep alive interval (#5484 )	2024-07-11 14:36:34 -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