status-go

History

saledjenic c040cc753e chore(wallet)_: router tx improvements (#6020 ) * chore(wallet)_: stickers service removed from the router, not needed after recent changes * chore(wallet)_: missed check for error added to few processors		2024-11-01 08:45:53 -03:00
..
README.md	Upgrade to london signer and cleanup	2021-07-20 10:57:38 +02:00
get_status_node.go	chore_: replace geth logger with zap logger (#5962 )	2024-10-28 20:54:17 +00:00
geth_node.go	chore_: replace geth logger with zap logger (#5962 )	2024-10-28 20:54:17 +00:00
geth_node_api_test.go	Feat/sync customization color (#3702 )	2023-07-18 21:35:06 +08:00
geth_node_test.go	chore_: completely remove goerli from the code	2024-10-21 17:30:51 +02:00
geth_status_node_test.go	chore_: replace geth logger with zap logger (#5962 )	2024-10-28 20:54:17 +00:00
rpc.go	bump version	2021-07-20 10:57:38 +02:00
status_node_rpc_client_test.go	chore_: replace geth logger with zap logger (#5962 )	2024-10-28 20:54:17 +00:00
status_node_services.go	chore(wallet)_: router tx improvements (#6020 )	2024-11-01 08:45:53 -03: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