Dear community, This referendum falls under the purview of janitorial activites.&nbsp; It seeks to close bounty 23 which was submitted in error.&nbsp; The submitter is attempting to do so with <a href="266">referendum 266</a> but is using a track with the wrong origin.&nbsp;&nbsp; I am also taking the opportunity to close bounty 22 which was submitted by Bill 27 days ago with no affirmative movements since. Regards, Will | Paradox | RCJ (Relay-Chain Janitor).

Send a batch of dispatch calls.
Unlike `batch`, it allows errors and won't interrupt.

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 dispatch without checking origin filter. (This
includes bypassing `frame_system::Config::BaseCallFilter`).

## Complexity
- O(C) where C is the number of calls to be batched.

- There is a referendum to close bounty 23 because it was submitted by mistake.
- The person who submitted the referendum is trying to close it with referendum 266, but they made a mistake.
- There is also a bounty 22 that was submitted by Bill 27 days ago, but nothing has happened with it.
- The person writing the message is called Will and they are a janitor for the relay-chain.
- Will wants to close both bounty 23 and bounty 22.

#268 To close erroneous and spam bounties