Using a `batch` call, this Referendum aims to cancel proposals that have been approved by the community but have failed to enact on time due to UI misconfiguration.

Namely, as we started to navigate OpenGov, it was brought to our attention that a misinterpretation of the parameter `after`, which is NOT an absolute block number but a delay expressed in blocks, implied that after approval, these referenda would take years to enact.

Among others, Referenda: [4](https://kusama.subsquare.io/referenda/referendum/4), [5](https://kusama.subsquare.io/referenda/referendum/5), [6](https://kusama.subsquare.io/referenda/referendum/6), [7](https://kusama.subsquare.io/referenda/referendum/7), [9](https://kusama.subsquare.io/referenda/referendum/9), [10](https://kusama.subsquare.io/referenda/referendum/10), [11](https://kusama.subsquare.io/referenda/referendum/11), currently sitting in the scheduler, are expected to be approved from 1025-1100 days from now.

However, as the teams have already resubmitted their proposals with the updated parameters (see [referenda history](https://kusama.subsquare.io/referenda) of various tracks), I am bringing forward the following call to cancel the proposals and avoid any complications in the future.

![](https://i.postimg.cc/zGG0cDTX/Screenshot-2023-02-06-at-14-43-33.png)

Send a batch of dispatch calls.

May be called from any origin except `None`.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then the calls are dispatched without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

This will return `Ok` in all circumstances. To determine the success of the batch, an
event is deposited. If a call failed and the batch was interrupted, then the
`BatchInterrupted` event is deposited, along with the number of successful calls made
and the error of the failed call. If all were successful, then the `BatchCompleted`
event is deposited.

- There was a mistake in how some proposals were set up, so they would take a long time to happen.
- Some proposals are expected to be approved in the future, but they need to be canceled because of the mistake.
- The teams have fixed the mistake and resubmitted their proposals.
- The person is asking to cancel the proposals to avoid problems in the future.
- There is a picture showing the call to cancel the proposals.

#122 Cancellation of the proposals that are wrongly scheduled

No Active Proposals