Duplicate of [Increase active collator set size to 16](https://zeitgeist.subsquare.io/council/motion/1614791_0xe4ba3f55cc5222f2cedf6c571680be73f26fb14da58594c7b0e85163a53b2cde), which got rejected due to insufficient number votes.

The proposal from Subsquid Lab Official outlines ongoing development and maintenance costs for public Subsquid Archives and the Giant Squid API. It covers the provision of archives, a crucial component of Polkadot and Kusama data infrastructure, offering access to on-chain data for various parachains. Additionally, the Giant Squid API provides GraphQL endpoints for exploring relay and parachain statistics, supporting a wide range of projects. The proposal seeks funding for the continued operation and expansion of these services. Overall, it aims to enhance accessibility and usability of on-chain data for developers and users within the Polkadot and Kusama ecosystems.

Schedule a majority-carries referendum to be tabled next once it is legal to schedule
an external referendum.

The dispatch of this call must be `ExternalMajorityOrigin`.

- `proposal_hash`: The preimage hash of the proposal.

Unlike `external_propose`, blacklisting has no effect on this and it may replace a
pre-scheduled `external_propose` call.

Weight: `O(1)`

Set the total number of collator candidates selected per round
- changes are not applied until the start of the next round

- **Problem Statement:** Lack of votes led to the rejection of increasing the active collator set size to 16.
- **Significance:** Enhancing the active collator set size is crucial for network efficiency and security.
- **Proposed Solution:** Proposing to increase the active collator set size to 16.
- **Expected Outcomes:** Improved network efficiency and security by expanding the active collator set size.

#15 Increase active collator set size to 16

No Active Proposals