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
This is not brainstorming ideas. If you have an idea you'd like to discuss, please open a new discussion on the lotus forum and select the category as Ideas.
I have a specific, actionable, and well motivated feature request to propose.
Lotus component
lotus daemon - chain sync
lotus fvm/fevm - Lotus FVM and FEVM interactions
lotus miner/worker - sealing
lotus miner - proving(WindowPoSt/WinningPoSt)
lotus JSON-RPC API
lotus message management (mpool)
Other
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
When having enabling a Snap pipeline you usually have different workers for the following Pipelines :
A CC pipeline
A Snap pipeline
In that scenario, you donc want your PC1 working doing CC AP and your Snap Worker doing APSnap.
Today AddPieceCC and AddPieceSnap are not differentiated on the workers.
Describe the solution you'd like
Create a new type of AP for snap (APS) that we can configure on a snap workers and disable on other workers.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Checklist
Ideas
.Lotus component
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
When having enabling a Snap pipeline you usually have different workers for the following Pipelines :
In that scenario, you donc want your PC1 working doing CC AP and your Snap Worker doing APSnap.
Today AddPieceCC and AddPieceSnap are not differentiated on the workers.
Describe the solution you'd like
Create a new type of AP for snap (APS) that we can configure on a snap workers and disable on other workers.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: