status-go

History

Sale Djenic f69ee07593 fix: calculating next nonce for optimism chain improved to align with calculation on mainnet and arbitrum		2024-03-13 15:21:33 +01:00
..
README.md	…
get_status_node.go	chore: refactor DB closure to check for errors before returning (#4808 )	2024-02-27 07:03:57 +08:00
geth_node.go	…
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	fix: calculating next nonce for optimism chain improved to align with calculation on mainnet and arbitrum	2024-03-13 15:21:33 +01: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