Skip to content

[Futarchy] Prevent unexpected scheduler error #1410

@Chralt98

Description

@Chralt98

Self::deposit_event(Event::<T>::UnexpectedSchedulerError);

This case is unfortunate. This can obviously lead to the following scenario: A proposal is submitted and stored in Proposals, but because the scheduler has too many scheduled calls at proposal.when, it fails and the whole proposal is removed from the storage, although it has been evaluated to be approved. It might be better to have another extrinsic call that allows approved proposals to be scheduled at the time of the root origins choosing. So essentially this function here could be called evaluate_proposal that either emits Approved and stores a boolean flag approved in the proposal or Rejected that removes the proposal. After the successful scheduling from the root origin, the proposal can be removed too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    l:MSolving the issue takes daysp:lowLow priority, resolution of this issue can wait

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions