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.
Last year we set up lotus to never fallback to the default config. The reasoning was that the default config enabled splitstore discard and so default configs are dangerous for users to rely on as they were not yet used to a world with chain store discarding as the default.
It has been a year so I think everyone is pretty well warned. If not we need to find out how to properly warn them now.
Describe the solution you'd like
Remove the default config disallowing option.
Describe alternatives you've considered
We could just keep this forever but it is needlessly inconvenient.
Additional context
This came up because of a bug in a rare code / state path in lotus daemon hit by Zondax that hit this error without benefit.
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.
Last year we set up lotus to never fallback to the default config. The reasoning was that the default config enabled splitstore discard and so default configs are dangerous for users to rely on as they were not yet used to a world with chain store discarding as the default.
It has been a year so I think everyone is pretty well warned. If not we need to find out how to properly warn them now.
Describe the solution you'd like
Remove the default config disallowing option.
Describe alternatives you've considered
We could just keep this forever but it is needlessly inconvenient.
Additional context
This came up because of a bug in a rare code / state path in lotus daemon hit by Zondax that hit this error without benefit.
The text was updated successfully, but these errors were encountered: