Expand description
Node client abstraction
During farmer operation it needs to communicate with a node, for example, to receive slot notifications and send solutions to seal blocks.
Implementation is abstracted away behind a trait to allow various implementations depending on the use case. Implementation may connect to a node via RPC directly, through some kind of networked middleware, or even wired without a network directly if node and farmer are both running in the same process.
Modules§
- caching_
proxy_ node_ client - Node client wrapper around another node client that caches some data for better performance and proxies other requests through
- rpc_
node_ client - Node client implementation that connects to node via RPC (WebSockets)
Traits§
- Node
Client - Abstraction of the Node Client
- Node
Client Ext - Node Client extension methods that are not necessary for a farmer as a library but might be useful for an app