This referendum updates the collator sets and configurations for all Polkadot system parachains. For Asset Hub, it adds five new "invulnerables" to the existing two, and changes the number of candidates from six to seven.

For Collectives and Bridge Hub both, it initializes the candidate deposit to 1,000 DOT (same as Asset Hub), opens up seven candidate positions, and also sets seven invulnerables per chain.

The seven invulnerables per chain were chosen by a group of node operators who have self-organized around providing collation services and demonstrated the ability to run nodes on other system parachains.

For more details on the motivation of adding so many invulnerables, see [Fellowship RFC-7](https://github.com/polkadot-fellows/RFCs/pull/7).

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.

- This referendum is about updating the collator sets and configurations for Polkadot system parachains.
- It adds new "invulnerables" to Asset Hub and changes the number of candidates.
- It also makes changes to Collectives and Bridge Hub, including candidate deposit and positions.
- The invulnerables were chosen by node operators who can run nodes on other parachains.
- For more details, you can check out the Fellowship RFC-7.

#84 [Staking Admin] Referendum #84: Update System Collator Sets and Configurations

No Active Proposals