Committing update to websockets api copy
Co-Authored-By: Łukasz Magiera <magik6k@users.noreply.github.com>
This commit is contained in:
parent
dea55f3310
commit
c20854241f
@ -214,7 +214,7 @@ Now go to http://127.0.0.1:2222.
|
|||||||
|
|
||||||
Lotus is architected modularly, and aims to keep clean API boundaries between everything, even if they are in the same process. Notably, the 'lotus full node' software, and the 'lotus storage miner' software are two separate programs.
|
Lotus is architected modularly, and aims to keep clean API boundaries between everything, even if they are in the same process. Notably, the 'lotus full node' software, and the 'lotus storage miner' software are two separate programs.
|
||||||
|
|
||||||
The lotus storage miner is intended to be run on the machine that manages a single storage miner instance, and is meant to communicate with the full node via the websockets api for all of its chain interaction needs. This way, a mining operation may easily run one or many storage miners, connected to one or many full node instances.
|
The lotus storage miner is intended to be run on the machine that manages a single storage miner instance, and is meant to communicate with the full node via the websockets jsonrpc api for all of its chain interaction needs. This way, a mining operation may easily run one or many storage miners, connected to one or many full node instances.
|
||||||
|
|
||||||
## Notable Modules
|
## Notable Modules
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user