status-go

History

Mikhail Rogachev 4c6ca00520 Feat: implement connector service for browser plugin (#5433 ) * feat(connector)_: impl `eth_requestAccounts` for browser plugin * feat(connector)_: add impl for `wallet_switchEthereumChain` and `eth_chainId` * feat(connector)_: add impl for `eth_sendTransaction` * feat(connector)_: add a signal and an endpoint for wallet ui side * chore_: refactor connector tests * feat(connector)_: impl `eth_requestAccounts` with signal * chore(connector)_: Add test, covering full transaction flow And polish impl & test for connector endpoints * fix(connector)_: temporary allow all origins for ws connection * chore_: review fixes * fix(connector)_: make user select chain id for dApp * fix(connector)_: add requestID and fine tune endpoints * chore(connector)_: naming fixes and tests improvments		2024-07-18 17:30:10 +02:00
..
README.md	…
get_status_node.go	feat_: implement connector service (#5375 ) (#5403 )	2024-06-24 07:29:40 -07: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	fix(wallet) fix pending transactions by using the wallet DB	2023-08-23 12:34:59 +02:00
rpc.go	…
status_node_rpc_client_test.go	fix(wallet) fix pending transactions by using the wallet DB	2023-08-23 12:34:59 +02:00
status_node_services.go	Feat: implement connector service for browser plugin (#5433 )	2024-07-18 17:30:10 +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