status-go

History

Ivan Folgueira Bande 3107c1eb0b refactor_: start using nwaku - some minor progress to add nwaku in status-go - nwaku.go: GetNumConnectedPeers controls when passed pubsub is empty - waku_test.go: adapt TestWakuV2Store - add missing shard.go - feat_: build nwaku with nix and use build tags to choose between go-waku and nwaku (#5896) - chore_: update nwaku - nwaku bump (#5911) - bump: nwaku - chore: add USE_NWAKU env flag - fix: build libwaku only if needed - feat: testing discovery and dialing with nwaku integration (#5940)		2024-10-17 15:26:24 -04:00
..
README.md	Upgrade to london signer and cleanup	2021-07-20 10:57:38 +02:00
get_status_node.go	feat_: RPC providers detailed statuses #5923 (#5924 )	2024-10-15 19:59:17 +04:00
geth_node.go	Feat: implement connector service for browser plugin (#5433 )	2024-07-18 17:30:10 +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	refactor_: remove status-im/rendezvous (#5685 )	2024-08-22 13:12:37 -04:00
rpc.go	bump version	2021-07-20 10:57:38 +02:00
status_node_rpc_client_test.go	chore(wallet)_: remove unused upstream client (#5934 )	2024-10-11 21:01:14 +04:00
status_node_services.go	refactor_: start using nwaku	2024-10-17 15:26:24 -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