This proposal aims to register a new foreign asset WSX. The WSX token is planned to be used in a campaign. It has the same properties as ZTG and can be used to pay fees. This will enable participants of the campaign to interact with the system using solely the WSX token, effectively reducing the entry barrier.
In addition, this proposal will distribute 10,000 WSX to an account owned by Zeitgeist. 10,000 WSX can be used to execute 400,000 transactions on average, thus effectively the proposal will gift an average of 400,000 transaction of execution time to the given address, which are then gifted to participant in a controlled manner.

Technically WSX is not a foreign asset. Due to technical limitations, this is currently the only way to achieve spawning a token that can be used to pay fees. This approach comes with the drawback that a manual cleanup of all accounts has to be executed after the campaign ended. Once the campaign is over, the token will be cleaned up which includes removing it from the list of foreign assets.

The tech team is currently working on a proper system for such scenarios, which can be used for future campaigns.

- A proposal is being made to create a new token called WSX.
- WSX will be used in a campaign and can be used to pay fees.
- This will make it easier for people to participate in the campaign.
- 10,000 WSX will be given to an account owned by Zeitgeist.
- After the campaign, the WSX token will be removed from the list of foreign assets.

proposal

Register campaign token WSX

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

If approved, this motion does spawn an external referendum that on approval does authorized the upgrade to zeitgeist-runtime v0.4.0 (spec_version 49)

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

Propose upgrade to v0.4.0 (spec_version 49)

calls

Untitled - motion #33

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)

Untitled - motion #31

Untitled - motion #30

Untitled - motion #28

Untitled - motion #29

This proposal aims to register DOT as a foreign asset on Zeitgeist and to allow it in pools. One of the reasons behind this is to tackle liquidity issues, as Tom stated:

> I think having DOT based markets on Zeitgeist is one of the best things we can do to help with liquidity issues. There is 7 billion dollars worth of DOT that can now easily be transferred to our chain, nothing else really comes close. For comparison, circulating DOT is worth around 10000x more than circulating ZTG

Since DOT has 10 fractional decimal places just like ZTG, it can be used right away in markets without further adjustments in the runtime code. This is one of the reasons why registering DOT before any stablecoin is recommended.

DOT integration was tested on all technical levels on Battery Station. Every involved party gave green lights to move forward on the mainnet. You can see and interact with the prediction market that uses (fake) DOT as a base asset at https://test.staging.zeitgeist.pm/markets/625 (request fake DOT from `Tom_#2021` or `sea212#9780`).

When receiving DOT from Polkadot on Zeitgeist, fees are charged in DOT as it is not certain that the receiving account has ZTG to pay the execution. The amount of DOT charged is specified as `143120520` (`0.0143120520`) times the fees in ZTG. This value was derived by dividing the 25 week moving average of the ZTG price by the 25 week moving average of the DOT price.

SubSquare has proposed to add DOT as a foreign asset on Zeitgeist and allow it in pools to tackle liquidity issues. DOT is worth 7 billion dollars and can be used in markets without further adjustments. DOT integration was tested on all technical levels and received approval to move forward on the mainnet. You can see and interact with the prediction market that uses (fake) DOT as a base asset. When receiving DOT from Polkadot on Zeitgeist, fees are charged in DOT. The amount of DOT charged is specified as `143120520` times the fees in ZTG.

proposalHash

Register DOT and enable it as a prediction market base asset

Send open HRMP channel request with Moonbeam

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)`.


- The proposal wants to connect with HydraDX through a channel.
- The connection needs approval from both governance bodies.
- A test was done before moving Battery Station to Rococo.
- The proposal has a code that will be executed by Polkadot.
- The code will initiate the opening of a channel with specific settings.

Dear council members, as Moises left Zeitgeist recently data now shows that he is not participating in the advisory committee anymore. The advisory committee needs to fulfill vote ratios to execute motions. Having an inactive member and no prime member elected raises the ratio and slows the advisory committee down in their motions.

Remove Moises from the advisory committee

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

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.

Increase active collator set size to 16

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

Duplicate of [Increase active collator set size to 16](https://zeitgeist.subsquare.io/council/motion/1579618_0xe4ba3f55cc5222f2cedf6c571680be73f26fb14da58594c7b0e85163a53b2cde), which got overwritten by [Authorize Zeitgeist runtime v0.3.6 upgrade](https://zeitgeist.subsquare.io/democracy/external/1614730_0xc52d5c7e2043e8f3ae2b8522f56688eec8a7cfbc981a5e28821e35875b52c347). Adheres to https://zeitgeist.subsquare.io/post/2

Council Motions