We propose to swap an existing Council member with someone representing the behalf of the community. In the long run, we want to move to the new Polkadot governance. However, for the time being we would like to decentralize the Council, representing all relevant interest groups for KILT Protocol by one seat. In the following weeks, you can expect proposals for follow-up swaps.

Proposed council: 

```
[
  4nvZhWv71x8reD9gq7BUGYQQVvTiThnLpTTanyru9XckaeWa
  4oHvgA54py7SWFPpBCoubAajYrxj6xyc8yzHiAVryeAq574G
  4oRRardEGiqYxzqsDyV4oJUc1GUm4qP6CnBxyAnDbo7nBrCi
  4qTuS5ymocwsPJ3uK5FKG7d2nVhV3CawDMwhWyKz2FBXq2gX
  4rnBT8jRfs24JTdZTrxmECGgVpa8mdx5E3t5wHwBxc2V22gn
  - 4tK95nW2hHjk4L6qkuwXyVvc5EtrSv3JJoJepmLCnbY7AbYV
  + 4sMQn3JyWwB18YwnWyagBg2B4GGN1iivrA67qB2pgZBBkQzK
]
```

The proposal seeks funding for OpenZeppelin's security review of Polkadot's ink! smart contract language and Substrate's smart contracts pallet. The review, conducted between January 23rd and February 17th, identified and addressed security vulnerabilities, ensuring the safety of users. Ink! serves as a crucial component for Polkadot parachains, attracting developers and enabling easy migration to parachain runtimes. OpenZeppelin, a trusted security firm, collaborated closely with Parity Technologies, the ink! team, and other contributors throughout the process. The proposal outlines milestone deliverables and payment conditions, emphasizing transparency and accountability.

Set the collective's membership.

- `new_members`: The new member list. Be nice to the chain and provide it sorted.
- `prime`: The prime member whose vote sets the default.
- `old_count`: The upper bound for the previous number of members in storage. Used for
  weight estimation.

Requires root origin.

NOTE: Does not enforce the expected `MaxMembers` limit on the amount of members, but
      the weight estimations rely on it to estimate dispatchable weight.

# WARNING:

The `pallet-collective` can also be managed by logic outside of the pallet through the
implementation of the trait [`ChangeMembers`].
Any call to `set_members` must be careful that the member set doesn't get out of sync
with other logic managing the member set.

# <weight>
## Weight
- `O(MP + N)` where:
  - `M` old-members-count (code- and governance-bounded)
  - `N` new-members-count (code- and governance-bounded)
  - `P` proposals-count (code-bounded)
- DB:
  - 1 storage mutation (codec `O(M)` read, `O(N)` write) for reading and writing the
    members
  - 1 storage read (codec `O(P)`) for reading the proposals
  - `P` storage mutations (codec `O(M)`) for updating the votes for each proposal
  - 1 storage write (codec `O(1)`) for deleting the old `prime` and setting the new one
# </weight>

- They want to change one of the Council members to someone who represents the community.
- They eventually want to move to a new governance system called Polkadot.
- For now, they want to make the Council more decentralized by adding one seat for the KILT Protocol interest groups.
- They will have more proposals for changes in the future.
- They have a list of proposed Council members.

#24 Swap a single council member

No Active Proposals