You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Boost matures, it will be default market implementation for Lotus users. Part of this would deprecating the existing lotus markets module and remove the code base from the lotus repo. This change will require moving all market related code from lotus to boost repo and further uncoupling Boost and Lotus.
Milestones
1. Disable lotus markets
Disabling the APIs and CLIs can be a starting point along with removing market components from lotus-miner definition
Milestone 1 can be done in parallel with any other milestone depending upon the readiness of both teams
2. Identify all the lotus modules and packages used by Boost which are specific to markets
3. Copy over the code base for above modules from Lotus repo to Boost
4. Enable graphsync retrievals in Boost client
We need to make a decision on payment channels integration here
Summary
As Boost matures, it will be default market implementation for Lotus users. Part of this would deprecating the existing lotus markets module and remove the code base from the lotus repo. This change will require moving all market related code from lotus to boost repo and further uncoupling Boost and Lotus.
Milestones
1. Disable lotus markets
lotus-miner
definition2. Identify all the lotus modules and packages used by Boost which are specific to markets
3. Copy over the code base for above modules from Lotus repo to Boost
4. Enable graphsync retrievals in Boost client
We need to make a decision on payment channels integration here
Porting go-fil-markets retrieval provider to boost #883
5. Remove all market code base from Lotus
6. Identify other lotus packages which are used by Boost but are not necessarily related to markets like
cliutils
,repo
etcThe text was updated successfully, but these errors were encountered: