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 a new feature or an enhancement to the Filecoin protocol. If it is, please open an FIP issue.
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 miner - mining and block production
lotus miner/worker - sealing
lotus miner - proving(WindowPoSt)
lotus miner/market - storage deal
lotus miner/market - retrieval deal
lotus miner/market - data transfer
lotus client
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.
If a lotus daemon sends a message to the blockchain but fails to confirm it with the miner and the subsequent failure needs to be investigated.
We should add retries to let the system recover but don't want the miner to accidentally send the same message twice
Describe the solution you'd like
Add a UUID to each message sent by the miner to the daemon
The daemon can then check if the message being retried by the miner has already been processed and sent to the chain
Checklist
Ideas
.Lotus component
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.
If a lotus daemon sends a message to the blockchain but fails to confirm it with the miner and the subsequent failure needs to be investigated.
We should add retries to let the system recover but don't want the miner to accidentally send the same message twice
Describe the solution you'd like
Add a UUID to each message sent by the miner to the daemon
The daemon can then check if the message being retried by the miner has already been processed and sent to the chain
Describe alternatives you've considered
No response
Additional context
This is a requirement for #9130
The text was updated successfully, but these errors were encountered: