Untitled - public proposal #20

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

Authorize runtime upgrade to v0.4.2

This proposal aims to register the foreign asset USD Coin (Moonbeam Wormhole).

It utilizes the `MultiLocation` of the USDC Wormhole contract on Moonbeam that's located at address [0x931715FEE2d06333043d11F658C8CE934aC61D0c](https://moonscan.io/address/0x931715FEE2d06333043d11F658C8CE934aC61D0c#code).
USDC will immediately be available as a base asset in prediction markets.
Furthermore, USDC can be utilized to pay fees. A fee factor of approximately 0.038 (USDC/ZTG) is initially used for the conversion.

- The proposal wants to register a foreign asset called USD Coin (Moonbeam Wormhole).
- The proposal uses something called MultiLocation and a contract on Moonbeam with a specific address.
- USD Coin will be available right away for prediction markets.
- People can use USD Coin to pay fees.
- The conversion rate for fees is about 0.038 USDC for every ZTG.

Onboard USD Coin (Moonbeam Wormhole)

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

As the governance body of [Moonbeam accepted the the batch call to accept the HRMP channel request from Zeitgeist to Moonbeam, requesting to open a channel to Zeitgeist and onboarding the ZTG token on Moonbeam](https://apps.moonbeam.network/moonbeam/referendum/16), the last step to enable bi-directional communication is to accept Moonbeam's hrmp channel request to Zeitgeist.

Accept HRMP open channel request from Moonbeam

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

Authorize runtime upgrade to v0.3.11

Untitled - public proposal #23

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)

Please reject this proposal, as the associated calldata contains a bug.

Correct proposal: https://zeitgeist.subsquare.io/democracy/proposal/22

Remove open channel request to AssetHub (formerly Statemint)

Zeitgeist was included in the [last Gov1 referendum](https://polkadot.polkassembly.io/referendum/123) spawned by the Council to open channels with Statemint (now AssetHub). Unfortunately the channel request from Zeitgeist to Statemint was not closed before the proposed call within that referendum was executed, [thus resulting in an error](https://polkadot.subscan.io/block/16263631?tab=event&event=16263631-1) when trying to force open channels between Zeitgeist and Statemint.

Polkadot now uses OpenGov (Gov2) and every parachain is responsible for spawning a referendum to open channels with system parachains like AssetHub. [A process](https://wiki.polkadot.network/docs/build-hrmp-channels#opening-hrmp-channels-with-system-parachains) was defined for that, which does not include opening a channel request prior to the referendum anymore. Previously opening a channel was a signal for the Council to include the channel opening request in a referendum that batches channel openings for potentially multiple parachains.

1. Zeitgeist was part of a vote to talk to Statemint.
2. There was a mistake and the channels between Zeitgeist and Statemint didn't open.
3. Polkadot now uses OpenGov and each group has to vote to talk to other groups.
4. There is a new process for voting to talk to other groups.
5. Before, opening a channel was a signal for a vote, but now it's different.

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

Authorize runtime upgrade to v0.3.9

Untitled - public proposal #18

Currently the manager account of Zeitgeist, the account that registered the parachain id 2092, has a some special privileges that were unlocked by the parachain (using governance) during the migration to provide the capability to recover after a failed migration. This includes setting the state and the state transition logic (runtime) for the Zeitgeist parachain as well as swapping leases (the privilege to be a parachain during a given timeframe). Currently the manager account can be targeted by attackers. In case of a successful attack, the attackers have complete control over the parachain.

This proposal aims to remove any privileges from the manager account of the Zeitgeist parachain by locking the chain, as the migration was successfully completed and emergency recovery is not required anymore.

Should the proposal pass, a call is executed that sends an XCM to Polkadot to execute the calldata `0x46062c080000`, which translates to `registrar.addLock(2092)`.

- Zeitgeist is a special account that has some special powers for a computer program called a parachain.
- The powers include controlling the program and being able to change how it works.
- Bad people could try to take over Zeitgeist and control the program themselves.
- This proposal wants to take away the special powers from Zeitgeist because they are not needed anymore.
- If the proposal passes, a message will be sent to another program called Polkadot to lock the special powers.

Lock parachain

Align existential deposits of foreign assets with ZTG #16

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 is proposing to register DOT as a foreign asset on Zeitgeist and allow it in pools to tackle liquidity issues. DOT has 10 fractional decimal places like ZTG, making it easy to use in markets without further adjustments. DOT integration was tested on all technical levels on Battery Station 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 on the test website. When receiving DOT from Polkadot on Zeitgeist, fees are charged in DOT, and the amount charged is specified as `143120520` times the fees in ZTG.

Register DOT and enable it as a prediction market base asset

The XCM contained in this proposal does express the request to open a channel to Statemint. Once approved by the governance body, the channel request has also to be approved by the governance body of Polkadot before it becomes active.
The reason behind this proposal is to prepare the onboarding of USDT on Zeitgeist. Due to technical reasons the usage of USDT in markets is not completely supported yet, however, since the Polkadot governance body moves slowly I'd like to ensure that the channel is ready once USDT support in markets has been added to the runtime.
The XCM within the calldata of this proposal is sent to Polkadot, which then executes the calldata `0x3c00e8030000e803000000900100` that is contained within this XCM. The dispatchable call that is invoked on Polkadot is the following: `hrmp.hrmpInitOpenChannel(1000, 1000, 102400)`.


- A proposal has been made to open a channel to Statemint.
- The channel request needs to be approved by the governance body of Polkadot before it becomes active.
- The proposal is to prepare for the onboarding of USDT on Zeitgeist.
- The channel will be ready once USDT support in markets has been added to the runtime.
- A code is sent to Polkadot to execute the dispatchable call `hrmp.hrmpInitOpenChannel(1000, 1000, 102400)`.

Request opening an HRMP channel to Statemint (USDT)

The objective of this proposal is to elect the first prime member of the Advisory Committee.

As you may be aware, the Advisory Committee oversees the approval or rejection of advised markets and has been instrumental in establishing a substantial majority of the markets on the mainnet. Additionally, the Committee regulates registrars and eliminates markets that grossly violate our community and market creation guidelines. The latter function might be replaced in the future with a less aggressive approach to enforcing proper conduct among market creators. All these responsibilities are carried out through Substrate's proposal system.

One of the Committee's long-term objectives is to achieve sufficient decentralization by incorporating community members. A step towards this goal was taken in https://github.com/zeitgeistpm/zeitgeist/pull/975, which modified the Committee's thresholds for approving or rejecting markets. Specifically, starting from version 0.3.9, a single vote will no longer suffice to approve a market.

However, as thresholds and membership numbers increase, abstentions become an issue. The prime member's role offers a straightforward solution. At the conclusion of a proposal's duration, all abstentions are delegated to the prime member.

The current advisors have conducted an internal vote for their prime member using on-chain remarks:

- https://zeitgeist.subscan.io/extrinsic/2627483-3
- https://zeitgeist.subscan.io/extrinsic/2677163-3
- https://zeitgeist.subscan.io/extrinsic/2715281-3

This proposal aims to subject this decision to public scrutiny.

SubSquare is a group that helps decide which markets can be used on a website. They also make sure people follow the rules. They want to add more people to their group to make it fair. They made a new rule that one person can't decide everything. But sometimes people don't vote, so they made a new job called the "prime member" to help with that. They had a vote to choose the prime member, and now they want people to check if it was a good choice.

Elect first prime member of the Advisory Committee - public proposal #13

The XCM contained in this proposal does request opening a channel to Moonbeam. Once approved by the governance body, the channel request has also to be approved by the governance body of Moonbeam before it becomes active.
Opening channels and reserve asset transfers in both directions have been tested on Moonbase Alpha Relaynet.
The XCM within the calldata of this proposal is sent to Polkadot, which then executes the calldata `0x3c00d4070000e803000000900100` that is contained within this XCM. The dispatchable call that is invoked on Polkadot is the following: `hrmp.hrmpInitOpenChannel(2004, 1000, 102400)`.


- A request has been made to open a channel to Moonbeam.
- Both governance bodies need to approve the request before it becomes active.
- Testing has been done for opening channels and transferring reserve assets in both directions on Moonbase Alpha Relaynet.
- The XCM within the proposal is sent to Polkadot.
- A specific call is made to Polkadot to initiate the opening of the channel.

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


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

Superseded by https://zeitgeist.subsquare.io/democracy/referendum/21. **Please vote Nay**

Unlock manager account

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.


Democracy Referenda