[Following our discussion on Polkassembly](https://polkadot.polkassembly.io/post/150) - here is the proposal for on-ramp to polkadot ecosystem.

**Intro:**
We see the Polkadot ecosystem developing, but for usage numbers to come, easy access for new users must be ensured. Currently, the first-time user willing to enter the ecosystem must enter either via centralised exchange. These steps are bearable for the current users of the network and crypto-natives, but will be a huge obstacle to new participants.
To significantly improve the process for the end-user, networks need on-ramps for easy, streamlined access using fiat money.

**Solution**
Here enters Ramp. With Ramp the purchase process takes place in just one interface, it is directly correlated to the wallet user is using for the purchase and, usually, takes much less time and requires fewer data than centralised exchanges need.
Ramp offers a powerful SDK that allows developers to offer DOT purchases with cards, bank transfers and open banking within their apps. This means that Polkadot powered solutions requiring DOT to use wouldn't need to ask new users to leave the app to complete the purchase. Think of it as Stripe for crypto onboarding. 
With Ramp, we want to provide DOT users and developers with a battle-tested alternative to a centralised exchange: an on-ramp that easy to implement and delightful to use. It will shorten the onboarding process from a few days to a few minutes which will contribute to the overall development of the Polkadot ecosystem.

Details of the proposal: https://docs.google.com/document/d/1u0h1CRrK-a-a83mecWSzNfvlBxUCurFf6Z6cME_HHCA/edit?usp=sharing

proposalId

Adding DOT to Ramp's SDK and enabling frictionless on-ramping across multiple dapps and wallets

Following on from our initial [Polkassembly discussion post](https://polkadot.polkassembly.io/post/144#9a968c2d-15a1-4252-9015-303d83145838) we are pleased to submit our proposal for the first milestone of the LocalCoinSwap non-custodial trading implementation.

**Github:** https://github.com/LocalCoinSwap/

**Homepage:** https://localcoinswap.com/

**Intro:**

LocalCoinSwap is a P2P cryptocurrency exchange which focuses on providing trustless fiat on-ramp solutions, enabling global accessibility for cryptocurrencies. We bridge the gap between users and crypto where centralized exchanges fail, in particular across developing regions of the world where access to mainstream finance is limited.

After a successful proof of concept with Kusama, we are now looking to extend the underlying infrastructure that we have developed to make a single package that is generically useful for any arbitrary number of parachains and tokens. We will then use this package to develop an open-source non-custodial trading integration for Polkadot. This will allow a trustless non-custodial fiat on/off ramp for DOT.

Following on from the discussion in the original thread, we have updated the proposal to better reflect the full scope of the project. Please check out our detailed proposal below and we welcome any questions or feedback: 
https://docs.google.com/document/d/1vP54xXbJxPC1nJQ0RA7TC4S16mFAuNvSP6iDxfFFcPc/edit#

LocalCoinSwap Treasury Proposal - Python Substrate libraries upgrade & Polkadot integration

Untitled - treasury proposal #19

Previous discussion can be found at [post 138](https://polkadot.polkassembly.io/post/138).


# Problems
We got news about Kusama and Polkadot from twitter, social media, and blogs. But to get them, first we need to open the corresponding links in the browser and sometimes we may need to login. For knowledge, usually we search some topic with google, or go to [substrate.dev](https://substrate.dev/) to search the tip we are interested in.

Problems with current situation:  
- News are not fast enough and not effective to readers. Even in telegram when we share the link, though we can see a short description, it's not cool and not effective to audiences.
- Twitter message authoring and post writing is time consuming, while it's nearly impossible for a developer or marketing staff to create some cool images to polish the content.
- It's hard for developers to share some knowledge in a flash and effective way.
- Image is the most popular way to broadcast info in China. We broadcast them in wechat chat groups and friends circle, but currently there are no convenient ways to generate flash news or knowledge tips for Polkadot ecosystem projects.

# Authoring tool

We propose a **knowledge tip** and **flash news** authoring tool to solve the above problems. With this tool we can:
- Write only title and detail to generate a cool image which is very easy to broadcast and friendly to content audience.
- Some image banners are prepared, and authors just need to choose one from them.

Following scenarios will be supported to help Kusama, Polkadot and other ecosystem projects to broadcast news and knowledge tip.

1. Project may have a flash good news which they want to spread it fast. Then a developer generate a image contains the news, and broadcast it to the telegram channels. Telegram readers just click the image, and the full content is shown to them, and they don't have to open the browser.

2. A normal user open this cool, create a image which explain 'what is kusama council', then broadcast it to social media. The content readers can reach this explanation in a fast way and ecosystem users can get this knowledge in a very clear way.

# Design drafts of this tool

![](https://i.imgur.com/KxlccWi.png)

![](https://i.imgur.com/CPk8y4J.png)

And the generated image may look like follows:

![generated-image](https://i.imgur.com/LUurImp.png)

# Milestones

## M1(One week)
- Design, including the page layout and several banners for the templates. One designer and one developer will be involved.
- Front page components development and 2 developers will be involved.

Cost: 4000$ = 833Dots, while each Dot cost 4.8$.

# Future work

- More themes for Polkadot and Kusama
- More default banners for Polkadot and Kusama
- Support customized banner

---

We are [OpenSquare](https://www.opensquare.network/), and we are dedicated to facilitate the collaborations between Polkadot ecosystem projects and developers, designers, etc.

OpenSquare's treasury proposal for a knowledge tip authoring tool

This is copy from https://polkadot.polkassembly.io/post/141

Github: https://github.com/patractlabs/elara

Homepage: https://elara.patract.io

[Patract Hub](http://patract.io/) is a community based non-profit organization, developed and maintained by [Patract Labs](https://patractlabs.com/?lang=en-US). We develop local open source toolkits and one-stop cloud smart IDE, dedicated to provide free development toolkits and infrastructure services for the entire smart contract ecosystem. 

Elara's goal is to build a similar infrastructure and network public access services to provide developers with a unified access layer based on Substrate multi-chain. In addition, Elara will be used as part of the smart contract development service, and will be integrated with other components of the Patract toolchain in the future, in terms of contract development environment support, development tools component, contract deployment and DApp release. Elara will be Polkadot’s infrastructure, allowing developers to focus on building upper-level applications.

## Summary of Elara’s future plan:
- ~~v0.1: Implement a server-side framework and proxy access to automatically monitoring and provide statistics for the Substrate node’s RPC service~~
- v0.2: Expand features about developer’s account management, project management, data access and traffic statistics to provide public access services for Polkadot
- v0.3: Performance optimization and architecture upgrade, support multi-chain architecture, access to multiple mainnets in the Polkadot ecosystem
- v0.4: Automatically access and maintain blockchains in Polkadot ecosystem

We have finished the development work of Elara v0.1 on time, and written a treasury report at https://polkadot.polkassembly.io/post/139. This proposal focuses on Elara v0.2, and will continue to develop the following features on the basis of v0.1.

- Implement the account space features, supporting developers to use Github as a third-party login system to create an account space.
- Support the creating and management of multiple projects under the developer’s account space
- Provide developers with detailed access statistics features on the single project dimension, showing statistical indicators such as daily and weekly requests, calling methods, and source of user groups.
- Officially launch https://elara.patract.io, providing the community with public access services to the Polkadot mainnet

## Detailed design of v0.2 (5 weeks, 27 Oct ~ 1 Dec)
### M1: UX Design & Project Management ( (1 designer + 4 developers) \* 1 week )
1. Product requirements analysis and developer experience design
2. UX design, showing related information such as the project mainnet, developer console and project statistics
3. Project demand management, feature tracking and project development, testing, integration progress control
4. Data structure design, store account space information, project information and statistical index information
5. System architecture design, storage structure design and program module definition.

### M2：Development （4 developer \* 3 weeks）
1. Implement developer account space
	1. Apply for Github OAuth Apps
	2. Deploy Redis storage service
	3. Develop authentication interface, dock Github OAuth, implement account information access
	4. Develop an account system to implement the storage and reading of developer account information
	5. Develop a login system to implement the session management of the developer's Github account
	6. Develop API function and provide external account related API interface

2. Implement project management
	1. Deploy Redis storage service
	2. Develop project creation, information showing, list showing features
	3. Develop the frequency and traffic restriction functions for project usage
	4. Develop API functions and provide external management interfaces for projects

3. Implement project monitoring and statistics
	1. Deploy Kafka message middleware
	2. Deploy Redis storage service
	3. Develop a log reporting interface to implement asynchronous reception of data reporting from other modules
	4. Develop data timer to implement statistics and analysis of reported data
	5. Develop API functions, provide external statistics API interfaces, provide project’s statistics for the current day and recent weeks on dashboard

4. Implement the official website
	1. Develop the official website pages to display information
	2. Develop authorization interaction with Github OAuth to implement account information access
	3. Develop the docking with the account system to implement the login interaction between the developers and the system
	4. Develop the console page, display the account's project information, and the corresponding operation information
	5. Develop the project’s details page to display detailed information and statistical results.

5. Implement  the open access to Polkadot mainnet
	1. Develop the log reporting feature of the agent access module to implement the monitoring log of the requests
	2. Deploy the node for Polkadot mainnet
	3. Configure access to Polkadot mainnet

### M3：Integration （4 developer \* 1 week)
1. Integrate developer account service and authorized access of Github OAuth
2. Integrate developer account system, project management and Elara’s console page
3. Integrate Kafka message middleware access proxy service and monitoring statistical service
4. Integrate Elara’s dashboard, project information page and back-end statistical data service
5. Implement client access to Elara’s sample service to provide a demo sample

### M4： Testing（4 developer \* 1 week)
1. Test account services, statistical services, and proxy access service programs
2. Test official website, project console and functional interaction
3. Test the client request access function
4. Test server monitoring statistics function
5. Test the dashboard page

## Cost of v0.2 (1 designer \* week + 20 developers \* weeks)

* Operating activities: $4200 ( Rent and Devices: $200 per employee \* week )
* Designer payments: $1000 ($1000 per designer \* week)
* Developer payments: $30000 ($1500 per developer \* week)
* —————————— +
* Total Cost: $35200
* Exchange Rate: $4.8 / New DOT
* Treasury Proposal: 7333 New DOT

## Verification：Public service & Youtube demo & Github source

- Developers can use Github account to log in to the developer account space from https://elara.patract.io
- Developers can create new projects and access related API keys under the account
- Developers can access the Polkadot node in Elara through Http and web-socket protocols
- Developers can view the monitoring statistics of the projects on the day and the recent weeks
- You can view the relevant monitoring statistics from the Elara dashboard

Patract Hub’s treasury proposal for Elara v0.2

Untitled - treasury proposal #11

FYI: This is copy from: https://polkadot.polkassembly.io/post/103, and Elara is the fourth project that we planned in our roadmap https://polkadot.polkassembly.io/post/100.

Github: [https://github.com/patractlabs/elara](https://github.com/patractlabs/elara) and Homepage will be: [https://elara.patract.io](https://elara.patract.io)

In Polkadot, Kusama and other parachains, RPC is the interface between DApp and the network. As the Polkadot network continues to expand, more and more parachains will be online, and more and more parachains will support smart contract functions. Faced with more and more parallel chains, developers need to build and maintain multiple blockchain nodes in order to interact with them, which will be a huge development cost for them. Whether it is facing the development and testing needs of developers or users' online DApp usage requirements, a convenient, fast and stable network access is one of the necessary conditions, and it is also the infrastructure of the Polkadot ecosystem.

Elara is inspired by [Infura](https://infura.io/) from the Ethereum ecosystem, named after Jupiter’s seventh moon. Elara's goal is to build a similar infrastructure and network public access services to provide developers with a unified access layer based on Substrate multi-chain. In addition, Elara will be used as part of the smart contract development service, and will be integrated with other components of the Patract toolchain in the future, in terms of contract development environment support, development tools component, contract deployment and DApp release. Elara will be Polkadot’s infrastructure, allowing developers to focus on building upper-level applications.

### Summary of Elara's future plan:

1. ** v0.1: Implement Substrate node access**
	* Create a server-side framework to develop proxy access, automatic monitoring and data statistics to the RPC service of the Substrate node
	* Support developers to use http and websocket protocols to uniformly access the network through the server framework
	* Develop a front-end dashboard to display relevant monitoring statistics of the RPC service of the Substrate node

2. **v0.2: Implement function expansion and performance optimisation**
	* Create account space for developers, support developers to use Github as a third-party login method
	* Support multiple projects under the account space
	* Provide developers with detailed access information of the DApp project by multiple dimensions, including statistical indicators such as daily and weekly requests, calling methods, and source of user group requests
	* Optimise program performance

3. **v0.3: Implement multi-link entry**
	* Extended program structure, support multi-chain architecture
	* Access to Polkadot, Kusama, and other blockchains, such as Jupiter
	* Provide developers with public access services of Polkadot, Kusama, and other parachains, such as Jupiter
	* Provide multi-chain interface documentation

4. **v0.4: Implement Polkadot ecological access & service operation and maintenance**
	* Establish a parallel link in Github to enter the process automation specification
	* Access to more parallel chains in the Polkadot ecosystem
	* Deploy and maintain hundreds of nodes globally
	* Support 10,000 developers, each developer account can establish 20 DApp projects, and each DApp project can use 1M daily access service

### Detailed design of v0.1 (5 weeks, 21 Sept ~ 26 Oct)

**Milestone 1: Design ( (1 designer + 4 developers) * 1 week)**

* Design Dashboard UX, displaying relevant monitoring statistics
* Design the data structure to store information such as the number of requests, calling methods, response bandwidth, response codes, etc.
* Design the program framework and complete the technical selection

**Milestone 2: Development (4 developers * 2 weeks)**

* Deploy a local Substrate node
* Develop a server-side program framework to implement basic functions such as request monitoring, distribution and logging
* Develop proxy access module to implement proxy access for http and websocket requests
* Develop monitoring statistics module to implement the statistics and analysis of requested data
* Develop a front-end dashboard page to display relevant monitoring statistics of the RPC service of the Substrate node

**Milestone 3: Integration (4 developers * 1 weeks)**

* Integrate agent access module, monitoring statistics module to service program framework
* Integrate front-end dashboard and back-end statistical data services
* Develop a client request program to simulate access requests

**Milestone 4: Testing (4 developers * 1  weeks)**

* Deploy and test the back-end service program
* Test client request access functions
* Test server monitoring statistics functions
* Test dashboard page functions

### Cost of v0.1 (1 designer \* week + 20 developers \* weeks)

* Operating activities: $3400 ( Rent and Devices: $200 per employee * week )
* Designer payments: $1000 ($1000 per designer * week)
* Developer payments: $30000 ($1500 per developer * week)
* —————————— +
* Total Cost: $34400
* Exchange Rate: $4 / New DOT
* Treasury Proposal: 8600 New DOT

### How to verify v0.1: Youtube demo video & Github source

* The Substreate node of the service can be accessed through http and websocket protocols
* Can monitor RPC requests of Substrate nodes
* Can view the relevant monitoring statistics from the dashboard

Patract Labs' treasury proposal for Elara v0.1

Referendum 7 (passed by the Council and the community) failed to come into place given the parameter to be executed after was 0 (zero) instead of 1.

```
let when = match when {
			DispatchTime::At(x) => x,
			DispatchTime::After(x) => now.saturating_add(x)
		};

		if when <= now {
			return Err(Error::<T>::TargetBlockNumberInPast.into())
		}
```

0 fails to check, but 1 would happen next block after the referendum is passed. I am proposing the exact same motion to Council and requesting TC to pass to referenda queue in the same way as before.

proposalHash

Proposal to gradually increase the number of validators

Untitled - motion #29

FYI: This is copy from: https://polkadot.polkassembly.io/post/102, and Europa is the third project that we planned in our roadmap https://polkadot.polkassembly.io/post/100.

Github: [https://github.com/patractlabs/europa](https://github.com/patractlabs/europa)

Europa is inspired by [Ganache](https://www.trufflesuite.com/ganache), [Ethereumjs-VM](https://github.com/ethereumjs/ethereumjs-vm) and [Buidler EVM](https://buidler.dev/buidler-evm/) from the Ethereum ecosystem. Europa is a sandbox of Substrate runtime environment, which would be used to simplify the developing, debugging, and integration test when developers develop Substrate runtime applications and test pallet-contracts. The sandbox will remove P2P and consensus functions, just remaining the execution environment and RPC interface. We will wrap the core modules, then provide a local database, a detailed log print function, a concept of workspaces which isolates different developing environments, and interact with different front-end UIs. The sandbox has no time interval between producing blocks, so debugging can be optimised to be very quickly.


### Summary of Europa's future plan:

**1. v0.1: Have an independent runtime environment to facilitate more subsequent expansion directions.**

 The independent runtime environment of excluded nodes can be expanded more without the constraints of the node environment and WASM compilation, and can be easily integrated with other components. In this version, it is more like simulating the Ganache project in Ethereum ecosystem, enabling contract developers to develop without having to build a contract blockchain. Developers can quickly fire up a personal Substrate chain, which can be used to run tests, execute commands, and inspect state while controlling how the chain operates.

**2. v0.2: Modify at contract module level to provide more information **

In this version, we will fork the pallet-contracts module for secondary development. We will strengthen the part of the error notification for contract developers, such as providing:

* WASM stack traces, the function call stack during WASM contract execution;
* Contracts stack traces, the call stack of a contract calling another contract;
* Console.log, provides libraries and methods to print command lines during contract development;
* Strengthen the error type and error display of the contract module;
* Simple integration with Redspot;

** 3. v0.3: Improve the developement experience, strengthen collaboration with other tools, and extend the sandbox to be compatible with other runtime modules**

* Strengthen the integration with Redspot
* Strengthen the integration with polkadot.js.org/apps to achieve complete RPC support
* Support status data query


### Detailed design of v0.1 (6 weeks, 21 Sept ~ 2 Nov):

**Milestone 1 : (3 developers * 1 weeks)**

* Implement an independent runtime executive environment
* Implement `Externalities` trait for a `Externalities` -like object
* Implement needed `Extension` trait interface.

**Milestone 2 : (3 developers * 1 weeks)**

* Implement a local database for this runtime executive environment to store all trie data, block and extrinsic
* Implement a local database  to store a bypath k/v state data, for exporting and querying from those data.

**Milestone 3 :  (3 developers * 1 weeks)**

* Implement a block packing function to pack blocks directly rather than through consensus process, allowing to pack one or multiple extrinsics at once. 
* Providing a workspace concept to isolate different environment.

**Milestone 4 :  (3 developers * 1 weeks)**

* Implement RPC functions of "forward to height" and "backward to height"
* Providing a way to pack blocks directly to assigned height
* Revert current state to a reverted height

**Milestone 5 : (3 developers * 2 weeks)**

* Integration and testing


### Cost of v0.1 (18 developers * weeks)

* Operating activities: $3600 ( Rent and Devices: $200 per developer * week )
* Employee payments: $36000 ($1900 per developer * week)
* —————————— +
* Total Cost: $37800
* Exchange Rate: $4/ New DOT
* Treasury Proposal: 9450 New DOT


### How to verify v0.1: Youtube demo video & Github source

* Build and run in an independent executable file
* Can start from different workspaces, and a new workspace is an empty chain
* Can receive extrinsics to set_code, deploy and call contracts directly
* Can interact with Redspot
* Can use RPC to jump over some blocks and revert to a specified height to revert states

Patract Labs' treasury proposal for Europa v0.1

Description to be found here:
https://polkadot.polkassembly.io/post/111

SubstraTEE Scalability Proposal

Copy from: https://polkadot.polkassembly.io/post/101

Github: [https://github.com/patractlabs/redspot-0.2](https://github.com/patractlabs/redspot-0.2)

Redspot's goal is to standardise the contract development process, hide the underlying compilation details of the contract, and combine the sandbox, library, API, SDK and other plugins to create a one-stop smooth contract development process. We have finished the first [proposal](https://polkadot.polkassembly.io/motion/7) requirements for v0.1,  and written a development [report](https://polkadot.polkassembly.io/post/78).

### Summary of Redspot's future plan:

1. v0.1: Build core available functions based on Truffle framework.
2. v0.2: Migrate to the [Buidler](https://buidler.dev/) framework to enhance plugin extensibility and add some functions to provide a smoother development workflow.
3. v0.3: Imitating Buidler's plugins, combined with the characteristics of Substrate to add various plugins, such as waffle, and began to integrate multi-language SDK.
4. v0.4: Following the case of Buidler, add appropriate libraries, such as typechain, etc.

### Problems of Redspot v0.1:

Although we have completed all the basic functions of Redspot, there are still some inconveniences in use. E.g:

* There is no convenient interactive cli for simple interaction with deployed contracts;
* Only the private key in plain text is supported in the configuration file, derivation through seed is not supported, and the password cannot be hidden;
* Under the default instantiation address logic of pallet-contracts, the contract address generated by a single account with the same parameters and the same WASM code is unique. This is not like Ethereum's single account can repeatedly deploy the same contract with different addresses. Therefore, after the deployment script and test script are written in Redspot, they can only be executed once. Otherwise, during the second execution, the execution will be interrupted during the deployment phase because it cannot be deployed. This requires script developers to pay careful attention to the writing method, otherwise it is easy to make mistakes. Redspot hopes to simplify this process.
* When deploying scripts and test scripts are instantiating or calling contracts, gas_limit needs to be written in after estimated whether the current assets are sufficient to support contract execution. Redspot currently simply fills in a default value, and does not have an estimation method, and does not know the gas consumption after execution;

### Detailed design of v0.2 (6 weeks, 21 Sept ~ 2 Nov):

The Buidler framework provides a "plugin" model, which can give Redspot great scalability and flexibility. This framework can also support Redspot to connect with contract modules on different parachains. For example, you can replace the environment of the target chain through plugins, add SDKs in other languages, and add extensible functions. In v0.2, Redspot will migrate all the functions of v0.1 to the new Buidler framework, and write various plugins to solve the problems of v0.1.

**Milestone 1: (3 developers * 1 weeks )**

Fork Buidler framework and modify it to suit the Substrate blockchain, then migrate all the current features in  Redspot v0.1 as inner plugins to this new framework.

**Milestone 2: (3 developers * 1 weeks)**

Support an interactive cli to operate deployed contracts, this cli will include injected polkadot.js interface and other helper functions, global env, key pairs, and connected node.

**Milestone 3: (3 developers * 1 weeks)**

Plugin 1: key pair support.
* Developers can use a private key directly;
* Developers can use a seed, and can derive account from this seed;
* Developers can use indicate a path for the keystore file, so that the private key will not appear in the config file.

**Milestone 4: (3 developers * 1 weeks)**

Plugin 2: multiple executing test support. This plugin provides a way to allow developer to deploy contracts more than once using same account and parameters in tests.
* Developers can use “beforeTest” to derive accounts and transfer some balance to this new account.
* Developers can use this new account to deploy contracts.
* Every executing test command will derive new accounts automatically.

**Milestone 5: (3 developers * 0.5 week)**

Plugin 3: [Jupiter](https://github.com/patractlabs/jupiter) test-net support as deploying environment;
* Jupiter test-net will use a flag storage to allow developers to use same account, same parameters and same code to deploy more than once.
* This plugin will develop a matching interface to interactive with Jupiter to set flag.
* This plugin’s env will allow developers to do deploying and testing in a normal way.

**Milestone 6: (3 developers * 1.5 weeks)**

Plugin 4: gas usage report.
* This plugin can print gas usage per test phase and deploying actions.
* This plugin can print gas usage per interactive cli.

### Cost of v0.2 (18 developers * weeks)
* Operating activities: $3600 ( Rent and Devices: $200 per developer * week )
* Employee payments: $27000 ($1500 per developer * week)
* —————————— +
* Total Cost: $30600
* Exchange Rate: $4/ New DOT
* Treasury Proposal: 7650 New DOT

### How to verify v0.2: Youtube demo video & Github source

* Replay all v0.1 tests in v0.2
* Show how Redspot v0.2 interactive cli works

**Workflows:**

* Use "deploy" command and execute deploying scripts
* Use interactive cli
* Call deployed contract
* Send extrinsics to call a contract
* Deploy a new contract in cli

**Plugins:**

* key pair plugin:
    * allowing developers to use seed, private key or a keystore path in config
* multiple executing test plugin:
    * could repeat any test command without any changes in test scripts.
* Jupiter test-net plugin:
    * could connect with Jupiter test-net by using a config flag in config files
    * could repeat any test command without any changes in test scripts.
* Gas usage report plugin:
    * could print gas usage for every test phase
    * could print gas usage after calling a contract in interactive cli

Patract Labs' treasury proposal for Redspot v0.2

**Motion 25** schedules an increase of validators slots by 1 every era (14,400 blocks) with a repetition of 100 eras. 

The motion is to be voted on referenda queue if passed by council for approx. 7 days, after the TC fast-tracks, as explained [here](https://polkadot.polkassembly.io/post/93).   Councillors: **to verify presage hash** you can check [here](https://polkadot.polkassembly.io/post/93#3baa6f49-06c7-4d47-9cb8-44bd19f789d6). Feel free to add any comments or questions. 

Original proposal: https://polkadot.polkassembly.io/post/93

A proposal to gradually increase the number of validators

Untitled - motion #24

Untitled - treasury proposal #12

Motion 20 upgrading Polkadot Runtime to v24 is up for vote.

Upgrade priority: Medium (timely upgrade recommended) To see changes and for release notes and hash, please check [here](https://github.com/paritytech/polkadot/releases/tag/v0.8.24).

All council members please vote at your earliest convenience.

SetCode: Polkadot Runtime v24

Proposal:#10 (motion 17)

Proponent: 146GTTVAZhU8epotD6ymKpRfhUwVLYrhL8Ho28LVeox4GrWC

Proposal date: 7.9.2020

Requested DOT: 1500

Short description: Polkadot Meetup in China

8btc.com (the proponent)  hosted a Polkadot meetup in Hangzhou, China.

[8btc](https://www.8btc.com/) is one of earliest and biggest crypto media in China. 8btc was founded by Changjia and Jihan Wu in 2011, and translated the very first Chinese version of bitcoin whitepaper. 8btc is an information and education platform for crypto users and people interested in cryptos in China. In 2016, [8btc English News](https://news.8btc.com/) was founded to act as a bridge between Chinese and foreign communities. 

8btc is also a host of [Hangzhou Blockchain Week](https://www.8btc.com/gbsf-2020?lang=en) and [World Blockchain Conference](https://www.8btc.com/wbc-2019/?lang=en), which will be held every year. Besides these two conferences, 8btc will host plenty of meetups with different themes every year. [Chainge](https://www.8btc.com/author/61023) is the name we gave to tech-related meetups, which is also for the Polkadot meetup we are about to host. Chainge has seen most famous blockchain teams in China joined in, including IRISnet, Nervos and PlatOn.

As a validating node of Polkadot, 8btc appreciates what Polkadot brings to the blockchain world and Web3 development. Though Polkadot is already a well-known project in China, most people know little about the related tech and what Polkadot can bring to the blockchain revolution.

So the meetup named ‘[Polkadot and the Trust World it Brings](https://www.chainnode.com/event/469852)’ will get more people to truly learn about what Polkadot is and will be, instead of pure speculation. Hangzhou is only our first station, there will be more in different cities of China.

The meetup was from 1:30pm to 5:00pm, on Sep. 12th (GMT+8). Entrance was free and there were more than 130 people to attend the meetup.

Please checked [here](https://docs.google.com/document/d/1RDutByvYe6n5nvIl2Jbx7PmQQwtS5xzYOe6iKc1v_Js/edit#heading=h.z7n65nftppgq) to see more budget details.

Pls feel free to ask me anything. Thanks!

Wendy, 
Head of 8btc English News


Polkadot Meetup in China - Proposal:#10 (motion 17)

refIndex

Untitled - motion #19

During the evening of 10 August 2020 and the morning of 11 August 2020, Web3Italy validators suffered network flaps that caused their nodes to go on downtime along with other nodes offline. 

As a consequence of the downtime, Web3Italy validators got slashed on 11 August 2020, during era 69/70. A full report by Web3Italy can be found [here](https://drive.google.com/file/d/1HzHJaSenHvghEAvP4isIXzbIK1LeefQ6/view?usp=sharing). 

Motion 16 proposes the cancellation of the slash events during era 69 and 70 for Web3Italy. Below a summary of the most important points raised on Polkadot Direction channel: 

- The cancellation is designed to only cover Web3Italy validators.
- The incident seems most likely related to an issue with software/hardware that had effects on both polkadot and Kusama, but affecting one network worse than the other.
- Web3Italy would not have been slashed if the Web3 Foundation incident had not happened at the same time.
- Web3Italy went offline for a minimum of 14 hours.

The motion is up for vote: all council members please review the information and cast your vote - for questions or comments, you can use the [Polkadot Direction channel](https://matrix.to/#/!OwgojQyBzTlUQGGLhq:matrix.parity.io?via=matrix.parity.io&via=matrix.org&via=web3.foundation) or this post.


slashIndices

Concerning slashes in eras 69 and 70 - Web3Italy validator

please see https://polkadot.polkassembly.io/post/52 for the full description of our proposal