status-go/node
Michal Iskierko 7d9092e295 fix(Collectibles): Trigger transaction event when creating transaction
Issue #11565
2023-07-18 16:21:20 +02:00
..
README.md Upgrade to london signer and cleanup 2021-07-20 10:57:38 +02:00
get_status_node.go feat: media server and colorhash related change (#3500) 2023-05-18 14:27:16 +08:00
geth_node.go revert changes to geth_node.go 2023-02-24 07:33:10 +08: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 test: use `T.TempDir` to create temporary test directory (#2746) 2023-04-26 21:39:51 +01:00
rpc.go bump version 2021-07-20 10:57:38 +02:00
status_node_rpc_client_test.go tests: updated due to updating old accounts as a part of migration process 2023-03-28 16:19:27 +02:00
status_node_services.go fix(Collectibles): Trigger transaction event when creating transaction 2023-07-18 16:21:20 +02:00

README.md

Structure

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