status-go

History

Sale Djenic f80042c5cb chore(wallet)_: ens resolver identified under ens api New EnsResolver type identified and will be responsible for network calls, while ens api will use it (until mobile app switches to a new sending flow) and continue managing other (db) interactions.		2024-11-22 13:32:49 +01:00
..
README.md	…
get_status_node.go	chore_: remove CLI option MEDIA_HTTPS (#6112 )	2024-11-22 10:23:17 +08: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	…
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)_: ens resolver identified under ens api	2024-11-22 13:32:49 +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