Untitled - motion #59

Untitled - motion #58

Register Tether USD (Polkadot AssetHub)

Register USD Coin (Polkadot AssetHub)

Increase active collator set size to 32

- Polkadot is a platform that allows people to nominate validators to help secure the network.
- A proposal was made to temporarily increase the nomination limit to 160 DOTs to keep the nomination ecosystem active.
- The proposal had a mistake where the numerical values were not in DOTs, but in PLANKs, the smallest unit of the DOT currency.
- The correct value for minimum nominator bond should have been set to 160 * (10^10), i.e. 1600,000,000,000.
- All values are unchanged except for minNominatorBond.

Polkadot’s Update to 160 DOTs as minimum nomination limit: A follow-up proposal fixing a unit mistake

Unlock manager account

- Shell and Statemint were working together to produce blocks on a blockchain.
- They had a problem because the keys they were using didn't match.
- They made a temporary fix by creating a new runtime that allowed them to use the keys they had.
- This fixed the problem and they were able to start producing blocks again.
- They will make another change later to use the keys they originally wanted to use.

Fix Statemint - Aura Key Scheme

- Polkadot Runtime is getting an upgrade to v9140.
- The upgrade will disable xcm teleports and reserve transfers.
- This is a runtime-only release.
- The proposal hash is 0x317c7862dc523bd083e4dd6545079bdc18058f561bada9e5e5646935b1cc04af.
- People can vote on the proposal.

Runtime v9140 on Polkadot Network

Redspot v0.1, applied by Patract Labs

For a second-grade student:

- Bifrost on Kusama wants to register their token, BNC, on Moonriver.
- They want to call it xcBNC and it will have a symbol of xcBNC.
- They will charge a fee of 35230000000000 units per second.
- They have a plan to register it and set the amount of tokens charged per second.
- Once it's registered, xcBNC will have an ID and an address on Moonriver.

Register Bifrost (on Kusama) native token as xcBNC on Moonriver

- Polkadot is planning to hold its first set of parachain auctions.
- The auctions will be held in two batches, with the first batch starting on November 11th and the second batch starting on December 23rd.
- The auctions will last for seven days each and will begin every seven or fourteen days.
- The lease periods for the auctions will be between 6-14.
- The Council and network governance will limit the number of parachain slots on Polkadot to 75% of that on Kusama to ensure stability guarantees.

Proposal for First Parachain Auctions on Polkadot

On chain council motion

- A vote was taken to open a channel to HydraDX.
- The vote passed and the XCM was executed.
- The channel was not opened because there was not enough money in the account.
- The account has been funded and the XCM can be resent.
- This will allow the channel to be opened.

Init HRMP open channel request to HydraDX

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

Unbrick Council collective

Deploy post-migration production runtime

Deploy migration runtime

Unlock parachain manager account

SubSquare is proposing to add DOT as a foreign asset on Zeitgeist and allow it in pools to help with liquidity issues. DOT is worth 7 billion dollars and can be easily transferred to the chain. DOT has 10 decimal places like ZTG, so it can be used in markets without any adjustments. DOT integration was tested on all technical levels and approved to move forward on the mainnet. You can see and interact with the prediction market that uses (fake) DOT as a base asset. Fees are charged in DOT when receiving it from Polkadot on Zeitgeist, and the amount charged is derived from the ZTG and DOT price averages.

Runtime upgrade to v26

1. There was a plan called Referendum 7 that was supposed to happen, but it didn't work because of a mistake in the code.
2. The mistake was that the code was set to 0 instead of 1, which meant that it couldn't work properly.
3. The person who made the mistake is proposing to try again with the same plan, but with the correct code this time.
4. They want the people in charge (called the Council) to agree to this plan and put it in a queue to be voted on (called the referenda queue).
5. This is important because they want to make sure that the plan can work the way it was supposed to and have a chance to be voted on.

Proposal to gradually increase the number of validators

- A proposal has been made to limit the maximum number of validators to 1200.
- This proposal needs to be voted on by the community before it can be executed.
- There may be a discussion in the future about setting a minimum DOT stake limit for validators.
- These limits are important for the safety of the network and will grow as the network grows.
- More information about this proposal can be found in the provided links.

Tech. Comm. Proposals