@councillors, two treasury proposals can be rejected based on the following info:

- [motion 137](https://kusama.polkassembly.io/treasury/137) is a proposal submitted mistakenly by Mr Excel. They have already submitted a corrected version of the proposal that was voted as [motion 445](https://kusama.polkassembly.io/motion/445) and already approved by Council a few weeks ago. The reason of the incorrect proposal is the use of extrinsics and the allocation unit measure in the extrinsics tab.

- [motion 141](https://kusama.polkassembly.io/treasury/141) is a proposal submitted by a UX developer studying the treasury submission process to work on some changes. This can be rejected with no issues. 

Send a batch of dispatch calls.

May be called from any origin.

- `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 call are dispatch 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.

- Mr Excel submitted a treasury proposal by mistake, but he has already submitted a corrected version that was approved by the Council.
- The incorrect proposal used extrinsics and the allocation unit measure in the extrinsics tab.
- A UX developer submitted a proposal to study the treasury submission process, but it can be rejected without any problems.

#450 Rejection of treasury proposals 137 and 141