Authorize the upgrade to zeitgeist-runtime v0.4.1 (spec_version 50)

https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.4.1

Upgrade to v0.4.1 (spec_version 50)

Authorize the upgrade to zeitgeist-runtime v0.4.0 (spec_version 49)

https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.4.0

Upgrade to v0.4.0 (spec_version 49)

The next [runtime upgrade v0.4.0](https://zeitgeist.subsquare.io/council/motions/34) requires `polkadotXcm.safeXcmVersion` to be configured properly to be able to send XCM, as `pallet-xcm` uses the storage instead of a hard coded value from v0.4.0 onward.

Right now XCMv2 is deployed. The message format V1 is the oldest supported version, V2 is the current version. With v0.4.0, XCMv3 is deployed. The message format V1 will be deprecated, V2 will be the safe default and V3 will be the most recent version.

⚠ Not configuring this value before deployment of v0.4.0 results in the inability to send XCMs. 

- SubSquare is upgrading their system to v0.4.0.
- To send XCM, `polkadotXcm.safeXcmVersion` needs to be configured properly.
- XCMv2 is currently being used, but with v0.4.0, XCMv3 will be deployed.
- Message format V1 will be deprecated and V2 will be the safe default.
- If `polkadotXcm.safeXcmVersion` is not configured properly, XCMs cannot be sent.

Set safe default XCM version to 2

This motion proposes to spawn an external referendum to authorize the Zeitgeist runtime v0.3.10 (spec_version 47). The release can be inspected at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.10.

Propose external: Authorize runtime upgrade v0.3.10 (spec_version 47)

Accept an incoming HRMP channel request from HydraDX (2034).

Accept HRMP channel from HydraDX

The referendum to open a init a hrmp open channel request to HydraDX already passed: https://zeitgeist.subsquare.io/democracy/referendum/25

The XCM was executed: https://zeitgeist.subscan.io/xcm_message/polkadot-38b400483edbc6df7afb9ca87f1319f891f72846

However, although the message was sent to Polkadot and execute, the channel was not opened. This is due to the circumstance the parachain sovereign account of Zeitgeist on Polkadot had not enough funds to reserve for opening a channel. The account is now funded appropriately and the XCM can be resend.

- A vote was taken to open a channel request to HydraDX and it passed.
- The XCM was executed but the channel was not opened because there wasn't enough money in the account.
- The account has now been funded and the XCM can be resent.
- The channel will allow for communication between Zeitgeist and HydraDX.
- The situation has been resolved and the channel will be opened soon.

Init HRMP open channel request to HydraDX

The XCM contained in this proposal does request opening a channel to HydraDX. Once approved by the governance body, the channel request has also to be approved by the governance body of HydraDX before it becomes active.
Before migration of Battery Station to Rococo, opening a channel to HydraDX was successfully tested.
The XCM within the calldata of this proposal is sent to Polkadot, which then executes the calldata `0x3c00f2070000e803000000900100` that is contained within this XCM. The dispatchable call that is invoked on Polkadot is the following: `hrmp.hrmpInitOpenChannel(2034, 1000, 102400)`.


- A proposal has been made to open a channel to HydraDX using XCM.
- The proposal needs to be approved by the governance body of both XCM and HydraDX.
- A successful test was done before migrating Battery Station to Rococo.
- XCM sends a code to Polkadot which then executes a specific call.
- The call invoked on Polkadot is `hrmp.hrmpInitOpenChannel(2034, 1000, 102400)`.

Motion #17 in the Council (Collective) pallet contained invalid calldata. During a runtime upgrade the function signature of the `membership` pallet changed, such that the calldata could not be encoded and the storage at `Council.proposalOf()` was corrupted. This lead to the inability to close and execute motion #17 as well as decoding issues in the apps frontend.

This motion inserts the correct calldata to remove a member from the advsiory committee.


Unbrick Council collective

After the migration to Polkadot succeeded, the migration runtime has to be superseded by a production runtime again, that removes the adjustments necessary for the migration and unlocks the business logic again. More information at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.8-polkadot

Deploy post-migration production runtime

This is a duplicate of https://zeitgeist.subsquare.io/democracy/referendum/19, please reject.

Unlock manager account

To be able to migrate to Polkadot, some changes to the runtime are necessary. The referendum dispatches a call to authorized the runtime mentioned within the following release: https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.8-polkadot-migration

Deploy migration runtime

To be able to recover the parachain in case of failure during the migration to Polkadot, the manager account has to be unlocked.

Unlock parachain manager account

Adheres to https://zeitgeist.subsquare.io/post/2

Increase active collator set size to 16

More information about the changes at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.6

Authorize Zeitgeist runtime v0.3.6 upgrade

More information about the changes at https://github.com/zeitgeistpm/zeitgeist/releases/tag/v0.3.5

Tech. Comm. Proposals