status-go

History

Stefan 524c21834b fix(wallet) propagate multi-transactions IDs to transfers Mainly refactor API to have control on pending_transactions operations. Use the new API to migrate the multi-transaction ID from to transfers in one SQL transaction. The refactoring was done to better mirror the purpose of pending_transactions Also: - Externalize TransactionManager from WalletService to be used by other services - Extract walletEvent as a dependency for all services that need to propagate events - Batch chain requests - Remove unused APIs - Add auto delete option for clients that fire and forget transactions Updates status-desktop #11754		2023-08-22 18:39:42 +02:00
..
README.md	Upgrade to london signer and cleanup	2021-07-20 10:57:38 +02:00
get_status_node.go	fix(wallet) propagate multi-transactions IDs to transfers	2023-08-22 18:39:42 +02: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	fix(tests): moved test db setup to a common place 't/helpers', created	2023-08-18 09:00:56 +02:00
status_node_services.go	fix(wallet) propagate multi-transactions IDs to transfers	2023-08-22 18:39:42 +02: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