Polkadot community, the time has finally come:

Nomination pools can go live any time now in Polkadot. This is a great milestone, removing any barrier for native relay chain staking for DOT-holders. This proposal suggests the following configuration for nomination pools on Polkadot, following Kian's advice from the staking team:

**1 DOT to join a pool.** "I actually used to suggest 5 DOTs for a slightly higher sybil resistance, but I think the 5x factor here is not that big of a difference, and allowing staker holders to join pools with at little as 1 DOT is a nice milestone. Moreover, this sybil attack is not really viable as we can easily lift the limit on maximum members (mentioned below) and then it would have no effect."

**200 DOTs to create a pool.** "This is not a cost or deposit. It is actually the initial collateral/stake of the pool, and by setting it to 200, it will ensure that all pools have an initial stake that’s more than the minimum that’s needed to earn rewards (~170 as of now). This initial stake still earns rewards for the creator of the pool, and can be unstaked once the pool is being dissolved."

**Maximum of 64 pools and 16k members in all pools**. "These are only there so that if there is a bug, we can easily migrate the data and perform a fix. If we reach these limits, they can trivially be lifted to a higher value. Moreover, if pools work fine for e.g. ~6 months, we can proceed with lifting them altogether."

"I have worked hard on communicating that: “Pools are designed to be infinitely scalable”, I am suggesting these limits only out of extra caution."

This initial configuration composition, aiming to be presented for a vote if the community agrees, can be found [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x270a0100e40b540200000000000000000000000100204aa9d101000000000000000000000140000000010040000000). Preimage is submitted. Please note this is an external motion needing root origin: after Council approval, the community will vote to approve or reject this proposal in referenda queue. 

proposalHash

Polkadot Nomination Pools Initial Configuration

The image composition is incorrect as it sets the min amount to join the pool to 5 DOTS instead of 1 DOT: the right proposal is [this one](https://polkadot.polkassembly.io/motion/270), up for vote now, 

________________________________________________________________________________

Polkadot community, the time has finally come:

Nomination pools can go live any time now in Polkadot. This is a great milestone, removing any barrier for native relay chain staking for DOT-holders. This proposal suggests the following configuration for nomination pools on Polkadot, following Kian's advice from the staking team:

**1 DOT to join a pool.** "I actually used to suggest 5 DOTs for a slightly higher sybil resistance, but I think the 5x factor here is not that big of a difference, and allowing staker holders to join pools with at little as 1 DOT is a nice milestone. Moreover, this sybil attack is not really viable as we can easily lift the limit on maximum members (mentioned below) and then it would have no effect."

**200 DOTs to create a pool.** "This is not a cost or deposit. It is actually the initial collateral/stake of the pool, and by setting it to 200, it will ensure that all pools have an initial stake that’s more than the minimum that’s needed to earn rewards (~170 as of now). This initial stake still earns rewards for the creator of the pool, and can be unstaked once the pool is being dissolved."

**Maximum of 64 pools and 16k members in all pools**. "These are only there so that if there is a bug, we can easily migrate the data and perform a fix. If we reach these limits, they can trivially be lifted to a higher value. Moreover, if pools work fine for e.g. ~6 months, we can proceed with lifting them altogether."

"I have worked hard on communicating that: “Pools are designed to be infinitely scalable”, I am suggesting these limits only out of extra caution."

This initial configuration composition, aiming to be presented for a vote if the community agrees, can be found [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Frpc.polkadot.io#/extrinsics/decode/0x270a0100743ba40b00000000000000000000000100204aa9d101000000000000000000000140000000010040000000). Preimage is submitted. Please note this is an external motion needing root origin: after Council approval, the community will vote to approve or reject this proposal in referenda queue. 

[PLEASE REJECT] Polkadot Nomination Pools Initial Configuration


Hello everyone,

We are thrilled to propose an NFT event at UNESCO HQ (Paris, France) on November 25-26 to showcase NFT experiences on the Polkadot Network. This event consists of a ubiquitous NFT exhibition (IRL, virtual and on 1,600 video billboards across France) and a roundtable discussion on environment, art and blockchain and how to leverage Polkadot solutions.

We are convinced that there is an opportunity for Polkadot to gain more visibility and stimulate adoption in the cultural industries, which is why we will target during this event the general audience (more than 8,000 visitors are expected), UNESCO Permanent delegations from 193 countries, and our own network of galleries, libraries, archives, museums and artists.

Our experiences will be built on Unique, Moonbeam, and RMRK. Parity will also join a panel to speak about Polkadot initiatives.

Feel free to post any question!

[https://docs.google.com/document/d/10FM8naMdJbD3skrBnuSSa1gHuwhUX1uB/edit#heading=h.gjdgxs](https://docs.google.com/document/d/10FM8naMdJbD3skrBnuSSa1gHuwhUX1uB/edit#heading=h.gjdgxs)

proposalId

NFT exhibition about environment at UNESCO HQ, Paris

The proposal aims to cover the costs for further development of **Gossamer**: a Polkadot host written in Go - a framework to build and run nodes for different blockchain protocols compatible with the Polkadot ecosystem. The timeline of the proposal is 12 months, after the successful collaboration with the Web3 Foundation Grants Program on the initial steps of this development. 

The overall goal is for Gossamer is **to provide the functionality needed to bring true client diversity to the Polkadot ecosystem** Budget, milestones and overall roadmap can be found on [the post](https://polkadot.polkassembly.io/motion/267). Please note that this is up for vote as an external motion: after/if the Council approves, this will be up for vote by the community. Make sure to review and vote at your convenience!

Original Treasury post: [https://polkadot.polkassembly.io/treasury/168](https://polkadot.polkassembly.io/treasury/168)

Original discussion post: [https://polkadot.polkassembly.io/post/1260](https://polkadot.polkassembly.io/post/1260)

External Motion: #168 Gossamer Ongoing Development Grant

Please note this motion replaces [motion 256](https://polkadot.polkassembly.io/motion/256) due to an error on the proposal weight and [motion 257](https://polkadot.polkassembly.io/motion/257) due to an error downgrading the call from the relay chain to native: the proposal fixes both mistakes.

Five more parachains have requested an HRMP channel with Statemint. This motion accepts them all and opens return channels.

**Handy Info**

- **Treasury Address**: `13UVJyLnbVp9RBZYFwFGyDvVd1y27Tt8tkntv6Q7JVPhFsTB`
- **Treasury AccountId:** `0x6d6f646c70792f74727372790000000000000000000000000000000000000000`
- **Statemint Address:** `13YMK2edbuhwMBxeUWm9c643A2wyYHwSVh1bCM7tShtg7Dtk`
- **Statemint AccountId:** `0x70617261e8030000000000000000000000000000000000000000000000000000`

- **Parachains that aim to open channels**: 2021, 2031, 2032, 2035, 2046.

**Call Construction**

These are constructed backwards. That is, the call to use as the proposal is at the end.

**Relay Chain Call to Execute**

First, we need the call that Statemint will execute on the Relay Chain. This accepts all channel requests and returns channel requests to the initiators.

- Encoded Call Data (Polkadot): 

```
0x1a02283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100
```

**Message from Statemint**

The above message needs to come from Statemint. So we put it into an XCM (the “Transact” instruction) along with purchasing some execution capacity and returning any leftover fees to the Treasury.

- Encoded Call Data (Statemint): 

```
0x1f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000
```

**Proposal on the Relay Chain**

But, governance is on the Relay Chain, not Statemint. So take some DOT from the Treasury (100 DOT for 10 channels at 10 DOT each plus 2 DOT for fees) and send a message to Statemint telling it to send a message back. This is the proposal to vote on.

- Encoded Call Data (Polkadot): 

``` 
0x1a02080502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d8bc7ced630001000100a10f0204060202286beef5021f0001010002140004000000000700c817a80413000000000700c817a8040006000700e40b54029d011a04283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000
```

- Call Hash: `0xfa5da8a4d9ef08dd22dfbc189861cbb9275dc8c52e4ce9b04f21cc830b3d5617`

Preimage has already been submitted for verification by the community as well. After/if Council votes and passes this proposal, this will need to be voted by the community in referenda queue. 

Second Batch Of Statemint HRMP Channels (replacing motions 256 and 257)

votingPeriod

delay

Task 10 General curator reward- Abdulbee

Task 11: Maintenance of phishing repo- Tim Janssen

Task 11: Maintenance of phishing repo- pastaMan

Previous discussion: <https://polkadot.polkassembly.io/post/1260>

---

- **Treasury Proposal:** Gossamer Ongoing Development Grant
- **Proponent:** AFRI, `1dvvq2sZg55LfLqFmegU493oUaPWxJfjiYysP1eyovkX6hP` (`1413`)
- **Beneficiary:** CHAINSAFE, `14gaKBxYkbBh2SKGtRDdhuhtyGAs5XLh55bE5x4cDi5CmL75`
- **Date:** 09.09.2022
- **Requested amount:** USD 1,998,117.60 in DOT on the day of submission using EMA30 rate by Subscan _(Oct 1st, 2022: EMA30 6.815 USD/DOT)_
- **Scope:** Software development / Protocol 

**Short description:** Gossamer is a Polkadot host written in Go: a framework to build and run nodes for different blockchain protocols compatible with the Polkadot ecosystem, mainly but not limited to the Polkadot and Kusama relay chains. This proposal addresses the Polkadot treasury to consider a grant for the ongoing development by ChainSafe's Gossamer team for another 12 months after the successful collaboration with the Web3 Foundation Grants Program on the initial steps of this development. 

---

**Context:** ChainSafe Systems [0], founded in 2017 in Toronto, is a Canadian blockchain development studio with more than 100 employees worldwide. Our vision is to move the various blockchain ecosystems closer, building bridges and increasing client diversity by providing alternative protocol implementations. With a strong emphasis on protocol engineering, we have been engaged by various clients and foundations, among others, in the Ethereum, Polkadot, COSMOS, and Filecoin ecosystems.

Initially funded through a Web3 Foundation grant [1], our protocol team started implementing a Go-Lang Polkadot host in January 2019. Ever since three years and 1300 merged pull requests later, the client has seen more than 40 contributors. As a result, a Gossamer node today can act as an alternative full node for chains such as Polkadot or Kusama. However, it is not yet feature complete. A treasury allocation should cover the pending developments with approval from the community. We want to continue developing and maintaining Gossamer to extend its capabilities further to grow and stabilize the Polkadot ecosystem with an alternative client implementation that is actively used by the community.

The current team consists of seven full-time protocol engineers and a dedicated project manager. The source code is available on GitHub [2] under the terms of an LGPL v3.0 license.

While the Web3 Foundation has entirely covered funding for the development in the past, this will be our first treasury proposal. Hopefully, this will secure our future operations, allow us to scale the team, and continue to broaden our scope while fostering our presence in the Polkadot ecosystem.

**Problem Statement:** The Substrate blockchain framework enables developers to quickly assemble blockchains for many different use cases. However, it is locking the ecosystem down onto a single programming language, Rust, competing for resources in areas where collaboration is desired.

Offering alternative frameworks in other programming languages should be a high-valued goal of the Polkadot community **as it opens up the ecosystem to a larger pool of engineers**. Thus far, Gossamer is not yet a generalized framework for building blockchains in Go; however, this will always be our central mission for the project.

**Objective:** The overall goal is for Gossamer to provide the functionality needed to bring true client diversity to the Polkadot ecosystem. This entails, but is not limited to:
- A **full-node client** capable of peering, synchronizing and seeding the most prominent relay chains and parachains of the Polkadot ecosystems.
- **Block-production and finality** capability for relay chains and parachains (validators, collators).
- **API services** to allow sharing chain and node states through standardized interfaces.
- **Runtimes** generated in alternative programming languages such as Go.

The primary focus of Gossamer development has been implementing the protocols of the Polkadot host, the client architecture that hosts the Wasm runtime of a Polkadot-like relay chain. The first milestone on the Gossamer roadmap is to allow members of the Polkadot community to stake cryptocurrency behind a Gossamer block-authoring node on the Polkadot Network.

**Deliverables:** The objectives of this proposal can be broken down into the following milestones in no particular order.
- **Validator specification:** Gossamer currently runs in single-node development environments or in sync with other Gossamer nodes or older Substrate versions. A desirable goal for the next year would be **implementing the latest validator specification**, which breaks down into three major components.
  - Transaction queue: Gossamer must be able to receive user-submitted extrinsics [3] and deliver them to the network. Furthermore, Gossamer must implement the transaction queue logic [4] to handle user-submitted transactions efficiently.
  - Block production: Gossamer must be able to author blocks using the latest BABE block production protocol [5].
  - Block finality: Gossamer must be able to participate in the latest GRANDPA block finalization protocol [6].
- **Sync modes:** Gossamer can currently conduct a full bootstrap synchronization to the tip of the chain. This means that the node can use the chain specification [7] of a Polkadot-like network to connect to that network and to import and verify the blocks that make up the network's canonical chain; these blocks will be stored in Gossamer's key-value database. A desirable goal for next year's development would be to **update BABE and GRANDPA implementations to the latest specification and provide alternative synchronization modes**. 
  - State Integrity: Gossamer must implement Polkadot's Patricia-Merkle trie [8] and use it to generate proofs correctly.
  - Fork Choice: Gossamer must tip-sync with a Polkadot-like network, which implies tracking multiple candidate forks at the head of the chain and following the best according to the specification.
  - Warp Sync: Besides providing a full-synchronization service, it would be desirable to provide other modes such as warp sync.
  - DB Imports: A Gossamer node should be able to bootstrap with a database snapshot at a given block height.
- **RPC APIs:** Gossamer must implement the same WebSocket JSON-RPC APIs as the Substrate Polkadot implementation (PSP-6, [9]); this means that the Polkadot-JS API [a] should be able to **work seamlessly with a Gossamer host**.
- **Telemetry:** A Gossamer client should be able to natively connect to any Polkadot Telemetry Service [b] to announce its presence. These Go-hosts should be identifiable by the Telemetry UI reporting the existence of alternative clients.
- **Performance:** To make the client attractive, it's crucial to adjust the reality to the user's performance expectations concerning CPU usage, memory usage, and synchronization time. Metrics can be comparable with Parity's implementation.

The focus for the next development cycle is **matching the latest specification to be able to bootstrap a full Polkadot node and participate in consensus**, e.g., on a public testnet such as Westend. Success metrics can be defined by passing the respective test suites provided by the Web3 Foundation; the organization will partner on this proposal as technical advisor and deliverables auditor to ensure the completed milestones are technically sound. If unavailable, an additional deliverable could entail providing test suites for the respective deliverable above.

Please note that funds are requested from the community treasury. The Web3 Foundation technical team has no control over these funds and will not be rewarded as a reviewer of the milestones. The team will serve the sole purpose of evaluating deliverables in alignment with the community approval of this proposal. This role is based on their past participation in this project. It is expected for the ChainSafe team to publish deliverable reports after the Web3 Foundation's technical evaluation and before continuing with subsequent milestones.

**Payment Conditions**: The requested amount for a 12-months ongoing development grant is USD 1,998,117.60 in DOT on the day of submission using the EMA30 rate by Subscan [c]. The allocation is asked for as a single, up-front payment to cover our ongoing development costs and for the team to be able to provide a runway to their developer resources.

The following resource table outlines the expected costs for the Gossamer team. The table consists of:
- the current base cost to operate the team,
- an 18% operational overhead to cover the costs of running the project as a team within ChainSafe Systems (e.g., operations, offices, equipment, tooling, infrastructure, legal, travel),
- the potential to grow the team sustainability by another two engineers over the course of the following year,
- as well as a 3% margin to protect against market volatility of the underlying DOT assets.

```
             | E2*    | E3*    | E4*    | TPM*   | Base Cost        | Cost +18% overhead |
| ---------- | ------ | ------ | ------ | ------ | ---------------- | ------------------ |
| Month 0    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 1    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 2    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 3    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 4    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 5    | 3 FTE* | 3 FTE* | 1 FTE* | 1 FTE* | USD   120,000.00 | USD     141,600.00 |
| Month 6    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 7    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 8    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 9    | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 10   | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| Month 11   | 4 FTE* | 4 FTE* | 1 FTE* | 1 FTE* | USD   154,000.00 | USD     181,720.00 |
| ---------- | ------ | ------ | ------ | ------ | ---------------- | ------------------ |
| USD Sum    |        |        |        |        | USD 1,644,000.00 | USD   1,939,920.00 |
| +3% margin |        |        |        |        |                  | USD      58,197.60 |
| ---------- | ------ | ------ | ------ | ------ | ---------------- | ------------------ |
| USD Total  |        |        |        |        |                  | USD   1,998,117.60 |
                                                                     ====================
```

_[*] Abbreviations: E2 - Engineer II (Mid-level Engineer), E3 - Engineer III (Senior Engineer), E4 - Engineer IV (Technical Lead), TPM - Technical Project Manager, FTE - Full-Time Employee_

The beneficiary of this proposal is ChainSafe Systems Inc, Toronto, Canada. The on-chain address is `14gaKBxYkbBh2SKGtRDdhuhtyGAs5XLh55bE5x4cDi5CmL75`. The funds' manager is Hatcher Lipton, COO at ChainSafe Systems, reachable through <hatcher@chainsafe.io> for any questions regarding the payment conditions.

For any questions about the technical nature of this proposal, you can message me, Afri Schoedon, Head of Protocol Engineering at ChainSafe Systems, at <afri@chainsafe.io>, or Dan Forbes, Technical Project Manager for the Gossamer team, at <dan.forbes@chainsafe.io>.

References:
- [0] <https://chainsafe.io/>
- [1] <https://github.com/w3f/Grants-Program/blob/master/docs/accepted_grant_applications.md>
- [2] <https://github.com/ChainSafe/gossamer>
- [3] <https://spec.polkadot.network/#_extrinsics>
- [4] <https://spec.polkadot.network/#sect-runtime-txqueue-module>
- [5] <https://spec.polkadot.network/#sect-block-production>
- [6] <https://spec.polkadot.network/#sect-finality>
- [7] <https://github.com/paritytech/polkadot/tree/master/node/service/chain-specs>
- [8] <https://spec.polkadot.network/#chap-state-spec>
- [9] <https://github.com/w3f/PSPs/blob/master/PSPs/drafts/psp-6.md>
- [a] <https://github.com/polkadot-js/api>
- [b] <https://telemetry.polkadot.io/>
- [c] <https://polkadot.subscan.io/tools/charts?type=price>


Gossamer Ongoing Development Grant

Hello, we would like to complete [our grant application](https://polkadot.polkassembly.io/post/1049#5de91eb5-1256-41ee-91b0-a7ec4eec809d) that we started before the actual event took place. The conference was a great success beyond our expectations! We educated the wider public about cryptocurrencies, Polkadot being among the most mentioned ones, and did connect Czech communities together. The [newly updated grant application](https://docs.google.com/document/d/1QVUaw6EgLqvkQMDE4HOh5X7U2sKNn1Z1ObS1yBV3DIM/edit?usp=sharing) can be found here: https://docs.google.com/document/d/1QVUaw6EgLqvkQMDE4HOh5X7U2sKNn1Z1ObS1yBV3DIM/edit?usp=sharing

UTXO.22

tl:dr proposal for treasury tip for organizing a meetup about Polkadot

Short description of the meetup: presentation about architecture and governance behind Polkadot, introducing specific parachains on Polkadot and Kusama, open discussion about various topics regarding Dotsama ecosystem.

More detailed info in this [link](https://docs.google.com/document/d/11CkD24oqrnE9unO7epAK2MOaErkyBfvx6m_L0bj8H9M/edit?usp=sharing)