- There will be an NFT event at UNESCO HQ in Paris on November 25-26.
- It will showcase NFT experiences using the Polkadot Network.
- The event includes an exhibition in person, online, and on 1,600 video billboards in France.
- There will be discussions about the environment, art, and blockchain technology.
- Over 8,000 visitors are expected to attend.
- Many important people from 193 countries and various cultural institutions will be there.
- Technologies like Unique, Moonbeam, and RMRK will be part of the experiences.

proposalId


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)

NFT exhibition about environment at UNESCO HQ, Paris

- The minimum amount to join a nomination pool in Polkadot should be 1 DOT, not 5.
- A new proposal is currently being voted on to set this correct minimum.
- Nomination pools will help DOT-holders stake their tokens more easily.
- To create a nomination pool, 200 DOTs are needed, which will earn rewards.
- There will be a maximum of 64 pools and 16,000 members across all pools.
- These limits can be changed later if everything works well.
- The proposal has been submitted for community vote after Council approval.

proposalHash

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

- Polkadot is launching new nomination pools for DOT-holders to make staking easier.
- You can join a pool with just 1 DOT, making it accessible for more people.
- Creating a pool will require 200 DOTs as initial collateral, which can earn rewards.
- There will be a limit of 64 pools and 16,000 members in total, but these limits can be increased later if needed.
- The proposal aims to ensure that Pools can scale up as needed.
- The community will vote to decide if this proposal is approved after council approval.

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. 

Polkadot Nomination Pools Initial Configuration

- Sota, the founder of Astar Network, is organizing the Polkadot Summit.
- The event will take place on November 3rd in San Francisco at the Fort Mason Center.
- There will be two tracks: a business track and a technical track.
- The summit is to educate people about the Polkadot Network's developments.
- Confirmed speakers are from well-known teams like Parity, Astar, and Acala.
- The goal is to raise awareness of Polkadot in the US.
- The event will last all day, from 9 AM to 5 PM.
- The estimated cost for the event is about $47,215, which can be paid in DOT tokens.

Hello everyone. This is Sota, founder of Astar Network. We are organizing the Polkadot Summit on November 3rd during one of the biggest Blockchain Weeks in the world to educate about the latest developments in Polkadot Network. We will have two tracks, a business and a technical track for a full-day event at the historic Fort Mason Center on the water in San Francisco from 9AM - 5PM. This is the timeline of the summit (WIP)

The motivation behind this initiative is that we think that Polkadot needs more exposure in the US. Having a Polkadot local event during a big conference is effective and needed.

We have confirmed speakers from the following top teams in Dotsama including Parity, Astar, Acala, Parallel, Nodle, Zeitgeist, Oak, Phala, Polkahaus, and Manta, and trying to invite more ecosystem projects.

[Here](https://docs.google.com/document/d/1JCQCBFXDV84X-6r6EwWhhKTvsoYm-sVkZw7OssKAmlk/edit#heading=h.v6is2ta0txr1) is the proposal. Please feel free to post questions and we are happy to answer them.

- Proponent: 1j5YyEGdcPd9BxkzVNNjKkqdi5f7g3Dd7JMgaGUhsMrZ6dZ
- Date: August 30, 2022
- Requested DOT: USD $47,215.00 
- Submission date: September 30th
- The average price of DOT in the last 7 days: $6.38
- $47,215/$6.38=7400 DOTs

Proposal: San Francisco Blockchain Week Polkadot Summit 

- The proposal is about funding a project called Gossamer.
- Gossamer helps build and run nodes for different blockchains using a programming language called Go.
- It is designed for the Polkadot ecosystem, which is a system of interconnected blockchains.
- The project will take 12 months to complete after getting support from the Web3 Foundation Grants Program.
- The goal is to make the Polkadot ecosystem have different types of clients.
- The proposal needs to be approved and then voted on by the community.
- More details about the budget and plans are available in the post.

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

- A new open-source font is being created for the Dotsama ecosystem.
- It will be made for small screens and will have light, regular, and bold versions.
- There will also be italics and a special coding version of the font.
- The font will include icons and support both Latin and Cyrillic letters.
- It will be packaged as a modern variable font in one file.
- This font is different from the Polkadot brand font, which is for larger sizes.
- The goal is for the font to help users all over the world.

We propose the design and production of an open source user interface font for the Dotsama ecosystem and beyond. The font will be specifically designed for small size screen use, come in light, regular and bold weights with matching italics and a corresponding monospaced version for coding. The font will also come with a suite of variable iconography and cover both latin and cyrillic scripts. We aim to wrap this all up in a single file as a cutting edge variable font, offering both technical and design benefits.

Unlike the Polkadot brand font that was designed for large sizes, this typeface will be built specifically for small size use across the Dotsama ecosystem. As an open source font our aim is that it has utility for users around the world.

[Read full proposal](https://docs.google.com/document/d/1KlK51o5JfTAwJQlv7AkZtv5FL5oKDtiUd5GOtKFT5GA/edit#heading=h.v6is2ta0txr1)

Opensource UI font for the Dostama ecoysystem

### Kusama Runtime Upgrade Proposal

- **Purpose**: Upgrade Kusama’s runtime to version v9281 to fix a previous issue.
- **Key Fixes**:
  - Fixes a vulnerability affecting block authoring.
  - Includes several low-priority updates and minor fixes.
- **Audits**: Some changes have been audited, while others are pending.
- **Community Involvement**: Requires approval from the Council and a community vote.
- **How to Vote**: Community members should vote at their convenience.
- **Details**: Full release notes and runtime changes are available [here](https://github.com/paritytech/polkadot/releases/tag/v0.9.28).
- **Proposal Hash**: `0xe9a09ca478bb39406f131a5fd4dab46edbf75d9ae3a9950eb0a74094943be4be`

Runtime v9281 Upgrade On Polkadot

- YieldBay is a project started 9 months ago to help people who provide money to earn from tokens in the dotsama ecosystem.
- It aims to make it easier for these people and for protocols (projects) to find and join liquidity pools and yield farms.
- Many people have similar questions about finding these pools, so YieldBay wants to help by creating a central platform for listings.
- The project has already built a working example of this platform called YieldBay List, which has attracted over 350 visitors.
- Many protocols, like Tapio and BeamSwap, have requested to be listed on YieldBay List.
- The goal is to reduce confusion and make it easier for everyone involved, helping new projects succeed.

[YieldBay](https://yieldbay.io) started out, about 9 months ago, as an effort to reduce information asymmetry and lower the barrier to entry for liquidity providers and yield farmers within the dotsama ecosystem and make it easier for protocols to acquire liquidity for their token pools.

For details see [Introducing Yield Bay - by Batman](https://blog.yieldbay.io/p/intro).

Dotsama’s multi-chain and interoperable infrastructure enables novel solutions to be built, which were previously not possible. However, this novelty also brings complexity.

Spending time in various community chat servers, we noticed similar questions from community members, stemming from the problem of information asymmetry in finding and participating in liquidity pools and yield farms.

![Information asymmetry in finding and participating in liquidity pools and yield farms](https://i.postimg.cc/nL86ZKgm/collage.png)

This problem affects not only LPs and yield farmers but also protocols, as they suffer from low discoverability and lower conversions, resulting in lower liquidity for their token pools and higher slippage. That’s a big problem if you want people to be able to buy your token. Hence, it is a huge barrier to a new project’s success.

Our goal is to help reduce the time and effort costs of liquidity acquisition and provision for protocols and end-users (LP/yield farmers) respectively, by making it easier to find and list liquidity pools and yield farms in one central location.

In this proposal, we are seeking to fund the development of an aggregation platform for finding and listing liquidity pools and yield farms across the dotsama ecosystem to reduce problem of information asymmetry mentioned above. We believe such a platform will be mutually beneficial for users as well as protocols.

**Progress so far:**

- We've already built a proof-of-concept for this, which is live on [list.yieldbay.io](https://list.yieldbay.io)
- The platform has had 350+ unique visitors who spent an average time of over 4min on the site
- Within a week since we launched YieldBay List (on July 11th, 2022), we’ve received listing requests from over 5 different protocols including Tapio/Taiga, BeamSwap, Darwinia, et al. (**disclaimer:** please note that this **does NOT** imply a partnership or endorsement between YieldBay and these projects)

**NOTE:** This submission is only for the first milestone. We shall make separate submissions for the remaining milestones.

Please see the [full proposal here](https://docs.google.com/document/d/1fssDqgPtIjdwO0XfJW5po94JHMf1ozdjeLwM2a40zJ8/edit?usp=sharing).

Thank you to everyone who contributed during the [community feedback stage](https://polkadot.polkassembly.io/post/1171) of this proposal. We have corresponded with everyone that has provided their inputs in the comment section of the discussion thread.

YieldBay Proposal: Listing platform for all dotsama liquidity pools and yield farms

- A person named 12uokSRn2hmEWPZuzHK1xqnFxRgyoApLtXRBd4jFan2x2T1P wrote a proposal on December 9, 2022.
- They want to request 2,493 DOT, which is about $18,840.
- The proposal is about the DotSama ecosystem, which has many complex technologies.
- These technologies can be tricky and have risks like mistakes in money transfer and hacks.
- Dot.alert() is a knowledgebase that helps people learn to manage their assets safely in this ecosystem.
- The proposal aims to get funding from the Polkadot Treasury to help keep Dot.alert() running.
- More details about the proposal can be found in a linked document.

**Proponent:** 12uokSRn2hmEWPZuzHK1xqnFxRgyoApLtXRBd4jFan2x2T1P

**Date:** 12.09.2022

**Requested:** 2,493 DOT (i.e USD $18,840 calculated from the [7-day EMA](https://polkadot.subscan.io/tools/charts?type=price) price of DOT)

**Short description:** 

The DotSama ecosystem is fundamentally complex. 

Relay chains, Parachains, Crowdloans and Cross-chain transactions are technologies that require users to juggle a lot of new concepts in real-time.
With this alluring novelty come a lot of unwanted risks: errors when transferring funds, incompatibility between account types, limited integration of cold storage devices, hacks on experimental trading protocols, phishing on community forums, lack of clarity around legal obligations, etc.

**[Dot.alert()](https://dot-alert.gitbook.io/dot.alert/)** is a knowledgebase that provides practical guidelines for managing assets safely across the DotSama ecosystem.

**This proposal aims to establish a social contract between Dot.alert() and the Polkadot Treasury to fund the operational costs of the platform.**

You can find the full details of the proposal (including milestones, targets, tasks, and costs for the period October – December 2022) here: [Polkadot Spending Proposal – **Dot.alert()**](https://docs.google.com/document/d/1CiGYEa1AuzUnmhws-hGSDP60QpZM5a7F/edit?usp=sharing&ouid=112859871373269428690&rtpof=true&sd=true).


Treasury proposal: Dot.alert() operational costs

- A proposal wants to upgrade the Polkadot Runtime to version v9280.
- The upgrade includes changes and new features that can be found online.
- One important change is the addition of nomination pools.
- These nomination pools will need to be set up through governance.
- Several other low and medium priority updates are also included in the proposal.
- If the Council approves it, the community will get to vote on it.
- Everyone is encouraged to participate in the voting process.

The proposal proposes an upgrade of the Polkadot Runtime to **v9280** - Release notes, runtime changes and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.28). Feel free to use srtool yourself to check the proposal hash. Among other changes, this release most notably **adds nomination pools to the Polkadot runtime** - please note that these will need to be configured via governance after enactment of this runtime upgrade. 

**Runtime**

✅ audited #11918 Low - Make new storage layer truly default

✅ trivial #11690 Low - Add event to pallet asset-tx-payment

✅ audited #11796 Low - Auto-incremental collectionid

✅ trivial #11985 Low - Pallet-contracts: fix 16bit func_id

✅ trivial #11991 Low - Contracts: apply depth limit when decoding

⏳ pending non-critical audit #11819 ❗️ Medium - Transaction payment runtime api: query call info and fee details

✅ audited #11927 Low - Transactional: wrap pallet::calls directly in storage layers

✅ trivial #5582 Low - Add nomination pools to polkadot runtime

✅ trivial #5910 Low - Update weights

If passed by the Council, this proposal should be voted by the community for final decision and enacted after. Make sure to vote at your convenience!

Polkadot Runtime Upgrade to v0.9.28

- EasyA is asking for $40,000 for a hackathon they held with Polkadot.
- The event took place in London on July 30-31, 2022.
- 250 students from 30 universities participated and created 27 projects.
- They taught students how to build on the Polkadot platform.
- The hackathon helped many new developers learn about Polkadot.
- EasyA wants the money to give prizes and cover costs for the event.
- They have documented the event for future hackers to learn from.

**Requested Allocation:** $40,000 (milestone 2 hackathon for Polkadot)

*DOT amount calculated via EMA on 9 September 2022 at GMT+0 0845hrs: 1 DOT ~ USD$7.55. USD$40,000 ~ 5,298.01 DOT

**Proponent:** EasyA 5FQqvRHgBEUZG17qs9cNFH6ZSSVyAwhb7D6dKjGWb8xgKFkP

**Short Description:**
We’re thrilled to announce our report on the successful completion of the EasyA x Polkadot hackathon (check out the highlight reel [here](https://youtu.be/vo4McHKpchY))! We held the hackathon on 30-31 July in London and are delighted that we exceeded all our targets. Overall, 27 awesome projects were created by 250 students from 30 universities. We educated them on how to build parachains/dApps in Dotsama, and we raised huge awareness of the Polkadot ecosystem amongst thousands of new student developers while we were promoting the hackathon. We have documented the hackathon fully [here](https://docs.google.com/document/d/10GTdZby0vj1qrmmUKrmWpat2XDsB7W38i52gfTdq668/edit?usp=sharing), along with our key successes and learnings for others to draw on when hosting future hackathons. 

As we have completely fulfilled the objectives of the proposal, we are therefore requesting the reimbursement of Milestone 2 (to reward winners and cover final costs). The prizes will be distributed in DOT to the winners. Although the value of DOT has dropped since the Milestone 1 proposal, the participants were aware token prices fluctuate. This is in accordance with our original Milestone 1 proposal which was approved [here](https://polkadot.polkassembly.io/motion/215).

We’re looking forward to building on this momentum and bringing more students to the Polkadot ecosystem soon!

Milestone 2 Proposal: Polkadot Hackathon for 200 Students and Educators

- Sota Watanabe, founder of Astar Network, is asking for $25,000 to help with a Polkadot event in Asia.
- The event is called Token2049, and it's a big deal in Asia with over 3,000 people expected to attend.
- 21 projects, including Astar, Acala, and Moonbeam, are teaming up to make Polkadot more popular in Asia.
- The goal is to make Polkadot stronger and show how everyone in the ecosystem works together.
- They hope to get 300+ people to sign up and 200+ to come to the event.
- The event page is already up, and over 300 people have signed up so far.

- Discussion: https://polkadot.polkassembly.io/post/1223
- Requested Amount: $25k
- The average price of DOT in the last 7 days: $7.44
- Requested DOT: 3360 DOT

This is Sota Watanabe, founder of Astar Network. On behalf of the following projects, I submit this proposal on Polkassembly. (Astar, Acala, Ajuna, Bifrost, DFG, Efinity, Efficient Frontier, Integritee, Unique, LongHash, Jsquare, Moonbeam, OnFinality, Phala, SubQuery, Equilibrium,Tribe, Web3Go, SubWallet, CESS and Acurast)

Token2049 is the biggest event in Asia this year and more than 3000 people are going to attend. We think that having a great Polkadot presence during this event is important especially to be recognized in Asia. The above 21 projects are going to either participate in token2049 or visit Singapore. These teams have come together to organize a Polkadot event, inviting not only Polkadot team members but also non-Polkadot ecosystem members to help build the Polkadot brand in Asia.

The goal of this event is to make a stronger Polkadot brand and show the unity of the ecosystem. Our KPIs are 1. 300+ registrations and 2. 200+ attendees.

Please see the full proposal [here](https://docs.google.com/document/d/1HyBvtQ1ljW0r6-snUtFmoNDoDRzC1L1oJV3WSsLQ0n8/edit#heading=h.v6is2ta0txr1).

[The event page](https://www.eventbrite.com/e/polkadot-asia-lounge-party-tickets-413358926677
) is already published and more than 300 people already registered. 


Proposal: Polkadot Singapore Event During Token2049

- A new motion corrects mistakes from previous proposals related to channel requests between Statemint and parachains.
- Five parachains (2021, 2031, 2032, 2035, 2046) want to connect with Statemint.
- The motion accepts these requests and opens return channels.
- Important treasury addresses and account IDs are provided for reference.
- The proposal requires a vote from the Council and then the community.
- It includes specific encoded call data needed for execution.
- The call hash for this proposal is `0xfa5da8a4d9ef08dd22dfbc189861cbb9275dc8c52e4ce9b04f21cc830b3d5617`.

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)

- A new motion is being proposed to accept five parachains that want to connect with Statemint.
- This motion fixes an earlier mistake about the proposal weight but still has an incorrect origin.
- The parachains wanting to connect are numbered 2021, 2031, 2032, 2035, and 2046.
- The Treasury will spend 100 DOT to help create these connections and pay some fees.
- Statemint will receive and handle the requests for opening channels.
- Once the Council approves the proposal, the community will vote on it later.

Please note this motion replaces [motion 256](https://polkadot.polkassembly.io/motion/256) due to an error on the proposal weight - fixed on this one. BUT THE ORIGIN IS STILL INCORRECT. THIS WILL BE REPLACED BY A NEW MOTION.

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): 

```
0x1a02080502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d8bc7ced630001000100a10f020406020700e40b5402ed021f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000 
```

- Call Hash: `0x1502b8b1df9e3c49e8b99991ba10aa7559d92f0f557f7f89584d6006096e6784`

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. 

[PLEASE REJECT] Second Batch Of Statemint HRMP Channels 

- A proposal was made for five new parachains to connect with Statemint.
- The proposal was rejected because it didn’t have enough support.
- The new parachains are numbered 2021, 2031, 2032, 2035, and 2046.
- Statemint needs to send a message to the Relay Chain to accept these requests.
- Statemint's message has to go through a process called XCM.
- The Relay Chain will take some DOT (a type of currency) from the Treasury to pay for this.
- After the Council approves the proposal, the community will get to vote on it next.

**Note: PLEASE REJECT - The proposal will fail because it does not provide enough weight. A new proposal will be submitted for vote.**

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): 

```
0x1a02080502006d6f646c70792f747273727900000000000000000000000000000000000000000070617261e80300000000000000000000000000000000000000000000000000000700d8bc7ced630001000100a10f0204060202286beeed021f0001010002140004000000000700c817a80413000000000700c817a80400060002286bee9d011a02283c01e50700003c01ef0700003c01f00700003c01f30700003c01fe0700003c00e5070000e8030000009001003c00ef070000e8030000009001003c00f0070000e8030000009001003c00f3070000e8030000009001003c00fe070000e803000000900100140d01010000000004000101006d6f646c70792f74727372790000000000000000000000000000000000000000
```

- Call Hash: `0x66533cf91c782761160b5ed11a0f65ca5d7d752040f94750875ace851b3f697f`

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. 

[PLEASE REJECT] Second Batch Of Statemint HRMP Channels

- The project is called Kampela, named after a Finnish fish.
- It aims to create a low-cost device for secure storage of digital keys.
- The device looks like a flat card and has an e-paper screen.
- It is similar to an existing tool called Parity Signer but is designed to be simpler and cheaper.
- Kampela can read information using NFC and shows results on its screen.
- It does not work like a wallet, as it cannot track money or create transactions.
- The proposal focuses on development, not actual production, hoping for competition in the market.

This is proposal for Milestones 1&2.

DOT/EUR exchange rate calculated as 7.3481 by EMA7 (EMA with 168 period frame) by [Kraken](https://trade.kraken.com/snapshot/ccbh735b5aau6chkob5g-kraken-dot-eur)

Our team proposes to design an open source hardware storage for dotsama ecosystem.

[Please see complete proposal on Skiff](https://app.skiff.com/docs/6e1d3e9f-9e2c-4413-9190-9c39cda20763#yJcS2WZZbiuFk4Pe3W5nycQ7vcjEbrXkbfcf2EKIiV4=)

Project name is Kampela, Finnish word for flounder fish. The device is envisioned as flat card mostly consisting of e-paper screen and few controls (and it allows keys to stay safely in depth).

Kampela is a hardware version of Parity Signer. It is a small card-shaped device (ideally comparable to a credit card form factor, to be carried in a wallet when needed) that accepts data through unidirectional NFC port and shows output on a monochrome electronic paper screen. It has cryptographic strongbox with elliptic curves supported by Substrate — which only stores private keys (after initial import) and performs all signing operations on-chip.

Kampela is designed to be a comparatively low-cost (below €100, in contrast to €500+ for a Signer-compatible smartphone) single-purpose device, which would only support a single seed phrase per unit, operated via a drastically simplified user interface. However, it would have all the security features of Parity Signer: a full-featured SURI account derivation system, transactions preview, metadata updates, logging.

As something that supports the same QR code output formats as Signer, it would be able to drop-in replace Signer when providing signatures back to a mobile/desktop wallet. The only challenge would be in transforming the current QR-driven input format of Signer into a suitable NFC payload. Alongside with native support in some apps (which would require software modification) this can also be achieved with a tiny “translator” app for a regular (online, not necessary trusted — one’s usual daily driver) mobile phone: it would snap a QR code with the transaction details and (statelessly, without any extra features or complicated UI) transform that into an NFC payload.

Kampela is a natural (and long-discussed) extension of Parity Signer to leverage the most out of modern hardware-based crypto chips and drastically reduce Signer’s attack surface: no mobile OS, not extra platform features, no unexpected communication methods or airplane mode to take care of.

Kampela is not a wallet! It is a signing tool, it is not able to track on-chain balances, validate things over chain-provided information or generate transactions on itself.

The scope of this proposal does not include actual production, but does result in all preliminary development required for production. Hopefully, many assembly shops would rush in to compete with us and each other!

[This proposal was prevoiusly posted in Discussions](../post/1227)

Edit: [Milestone 1 report](https://app.skiff.com/docs/2b25845a-4a00-4bf4-aaff-3de4a70d4ad7#zSepFgAI0EetUe7eIp2Tlgu/RnhMjnAJRDecVUiVmhQ=)

Edit: [Milestone 2 report](https://app.skiff.com/docs/5dcbeadc-e5f3-4f29-8476-e8fcb7786585#ZNnc%2FdmSz3dYkUNc%2BI%2BiarGsZKa0W9uUN25ZqCySPAg%3D)

Hardware signer and key storage Kampela: Milestones 1&2

- A Ziggurat is a tall, stepped tower made of rectangles.
- It has three important layers for testing networks: Conformance, Performance, and Resistance.
- Conformance checks if the network follows the right rules.
- Performance sees how well the network works under a lot of pressure.
- Resistance checks if the network can handle attacks.
- Tools named Ziggurat help developers test these layers.
- This testing is important to keep networks safe from hacks.

A Ziggurat is a rectangular stepped tower that uses precise measurements to ensure that each foundation can support the layers above.

This metaphor can be applied to network testing by defining three layers:

1. Conformance: adherence to the network protocol
2. Performance: healthy throughput under pressure
3. Resistance: the withstanding of malicious behavior

Ziggurat, by [Equilibrium](https://equilibrium.co/), is a set of tools that allows node developers to test these three layers extensively and ensure that each new release does not introduce bugs, performance bottlenecks, or security flaws.

As mentioned in the conclusion of the recent Trail of Bits report: It’s only a matter of time before a blockchain network is completely toppled by a network-level hack. This proposal will detail why this work is critical, and how we will go about solving it.

For the full proposal, see https://docs.google.com/document/d/1HRhFKo5w73wP5Nz8hg3xtw5GmPseNrzsarJLNNZqDZo/edit?usp=sharing

Ziggurat: The Network Testing and Stability Framework

- SubWallet is proposing to support NFTs on Kusama and Statemine.
- They want to allow cross-chain transactions and show transaction history and staking details.
- They added a donation button to support charities, focusing on Ukraine.
- SubWallet can send and receive NFTs and has integrated with other tools to improve the user experience.
- As of June 2022, SubWallet supports over 60 networks and has more than 5,000 users.
- By August 2022, they increased support to over 70 networks and gained 15,000 installs.
- They are part of the Substrate Builders Program and collaborate with over 70 teams.

**SubWallet 2nd proposal:** NFT support on Kusama and Statemine, Cross-chain assets support for Statemine and Statemine, Transactions history, Crowdloan status and Staking information, Custom Networks, XCM Transfer and Integration with Substrate Connect - Light Client.

**Dear Councilors,**

**This is SubWallet's 2nd proposal for Milestone 2 - 12 Weeks: From Mar 2022 to May 2022 (which is completed):**

![](https://lh3.googleusercontent.com/B1THH26yM-lThu2tjrWBWOgwQg_uNZzF_aj55B35mCaQ-0jwPTXZ6l8riCzxCBAsm9VcQ10-H28M8xr8tunGfezm=w640-h400-e365-rj-sc0x00ffffff)

- Full proposal for Milestone 2 with a detailed description & costs: [Link](https://docs.google.com/document/d/1HJ7Jr1BkvyxjBcKZBoKCgmZlcJAXnrW1upJTe7rC0zM/edit#heading=h.v6is2ta0txr1) 
- Community Discussion for Milestone 1 & Milestone 2: [Link](https://polkadot.polkassembly.io/post/1113)
- For full details about all milestones and progress, please refer to this [link](https://github.com/Koniverse/SubWallet-Extension/milestones). (Milestone 1&2 are completed; Milestone 3, 4, and 5 are in progress)
 
**Complete set of the proposal: ([See proposal](https://docs.google.com/document/d/1HJ7Jr1BkvyxjBcKZBoKCgmZlcJAXnrW1upJTe7rC0zM/edit#heading=h.v6is2ta0txr1))**

- Added Donate Button for charity program (Currently, we only support the Ukrainian government according to information Mr. Gavin Wood has published on Twitter, You can see a demo of the feature [here](https://twitter.com/subwalletapp/status/1499786619880341505))
- Added RMRK 2.0: Singular & Kanaria on Kusama
- Send / Receive NFT: Singular & Kanaria on Kusama, Statemine ([Link](https://twitter.com/subwalletapp/status/1506581700775612416) and [Link](https://www.youtube.com/watch?v=fzRbcnafV3M))
- Added cross-chain assets for Statemine, Statemint ([Link](https://twitter.com/subwalletapp/status/1516249395867824130))
- Integrated with SubQuery & Subsquid to show Transactions History, Crowdloan Status, and Staking Information
- Compatible with Metamask and Support EVM Assets ([Link](https://twitter.com/subwalletapp/status/1506581700775612416), [Link](https://twitter.com/subwalletapp/status/1511316471246372874) and [Link](https://twitter.com/subwalletapp/status/1516249395867824130))
- External Security Audit: [Report](https://audit.verichains.io/certifications.html?search=SubWallet)
- Updated new transfer flow for multi-chain assets
- Added Send & Receive cross-chain assets
- Custom Endpoint / Network ([Link](https://twitter.com/subwalletapp/status/1531960712071094273))
- Integrated with Substrate Connect - Light Client ([Link](https://twitter.com/subwalletapp/status/1531960712071094273))
- [And more](https://github.com/Koniverse/SubWallet-Extension/milestone/2?closed=1)
 
**Our tractions as of 15 June 2022**

- 60+ networks supported (relaychains, parachains & solochains) in the Polkadot & Kusama ecosystem
- 5000+ organic installs and 4000+ weekly active users on Chrome Store & Firefox Store.
- Conversation rate ~ 100%
- Our users come from 70+ countries.
- 5000+ community members on Twitter, Telegram, and Discord
- A member of the Substrate Builders Program
- Working with 70+ teams in the ecosystem with the ultimate goal of bringing the best UI/UX for users. 

**Our tractions as of 31 August 2022**

- 70+ networks supported (relaychains, parachains & solochains) in the Polkadot & Kusama ecosystem
- 15.000+ organic installs and 12.000+ weekly active users on Chrome Store & Firefox Store.
- Our users come from 80+ countries.
- 6500+ community members on Twitter, Telegram, and Discord
- SubWallet on Polkadot Community Call on August 18, 2022: [Link](https://twitter.com/Polkadot/status/1560234806478356480)

**All the best,**

**SubWallet Team**

Milestone 2: SubWallet Proposes to Build the Web3 Multiverse Gateway for Polkadot & Kusama ecosystem

- The v9270 runtime is used by Polkadot and Kusama.
- It allows buying and selling NFTs, which are special digital items.
- This change was added to something called the Uniques pallet.
- Statemine can now use certain assets to pay for XCM fees.
- Statemine will get this feature first, before Statemint. 
- Statemint does not have enough assets for this change yet.
- Not having the feature on Statemint does not affect how it works right now.

The [v9270 runtime](https://github.com/paritytech/cumulus/releases/tag/parachains-v9270) is based on the same release as the Polkadot/Kusama v9270 runtimes. For both Statemint and Statemine, this release introduces the ability to buy and sell NFTs in the Uniques pallet, introduced in [this PR](https://github.com/paritytech/substrate/pull/11398). For Statemine only, this release also allows the use of sufficient assets to pay [XCM fees](https://github.com/paritytech/cumulus/pull/1278). This feature will run on Statemine before making its way to Statemint; Statemint does not have any assets deemed sufficient yet, so not having it there will not affect current interactions.

Upgrade Statemint to v9270

- This proposal is about updating the Polkadot Runtime to a new version called v9270.
- The new version has release notes and changes that can be checked online.
- A special code called a proposal hash (0x55507b53f5c37e97e3faf9a9274dba0c5eace970aa5c653c179126f679ed496e) is included.
- If the Council approves the proposal, the Polkadot community can vote on it.
- Voting is important, and everyone is encouraged to participate when they can.

This proposal aims to upgrade the Polkadot Runtime to [v9270](https://github.com/paritytech/polkadot/releases/tag/v0.9.27) - Release notes, runtime changes, and proposal hash can be found [HERE](https://github.com/paritytech/polkadot/releases/tag/v0.9.27). Feel free to use srtool yourself to check the proposal hash.

Proposal hash: `0x55507b53f5c37e97e3faf9a9274dba0c5eace970aa5c653c179126f679ed496e`

If passed by the Council, this proposal should be voted by the Polkadot community and enacted after. Make sure to vote at your convenience!

Polkadot Runtime Upgrade to v9270

- PolkaWorld is a community in China that focuses on Polkadot and has over 50,000 followers.
- They have worked with Polkadot and Web3 Foundation since 2019.
- PolkaWorld received a W3F community grant from 2019 to 2021.
- They made a social contract with Polkadot Treasury in June 2021.
- They are asking for money to cover community operation costs from September to November 2022.
- Details about their goals, tasks, and budget are available in a shared document.
- They welcome community advice and feedback.

Dear community and councilors! This is a social contract between PolkaWorld and the Polkadot Treasury. [This proposal](https://docs.google.com/document/d/12o8-i64KsxA2KGnuJg3SUghprqGKUteCAHy8TkqKvNo/edit#) is aimed to cover the community operation costs from Sep 2022 to Nov 2022.

PolkaWorld is the Polkadot community in China and has gathered more than 50,000 followers, we have collaborated with the Polkadot ecosystem and Web3 Foundation to build a strong community since 2019. We received the W3F community grant from 2019 to 2021, then make a social contract with Polkadot Treasury in June 2021, so far we have got 5 times Polkadot Treasury funds. 

Details for **milestones**, **tasks**, and the **budget** for the next 3 months, and all monthly reports can be found [here](https://docs.google.com/document/d/12o8-i64KsxA2KGnuJg3SUghprqGKUteCAHy8TkqKvNo/edit#). Love to hear all your advice or any feedback.

PolkaWorld Ops and Maintenance proposal：2022.9 - 2022.11

- Polkadot uses special technology called Substrate to create decentralized systems.
- Depending on how these systems are set up, they can be more or less decentralized.
- A tool named Polkawatch helps check how decentralized Polkadot is by looking at different factors.
- Currently, Polkadot's network is quite centralized, with few operators and regions handling most of the work.
- Polkawatch started working in the second quarter of 2022.
- There is a plan to keep improving Polkawatch and its software in the third quarter of 2022.
- The community can provide feedback on these plans through a discussion post.

Hello Community,

Polkadot, and generally speaking Substrate built block-chains have tremendous potential to deliver decentralized computing, however depending on how they are deployed and operated by the community the resulting system can be more or less centralized/decentralized.

When analyzing the degree of decentralization of the Polkadot Rely chain by the following variables: Region, Computing Network and Node Operator, it turns out that the network is very centralized with most of the public validation activity concentrated and a few Operators, Regions and Computing Networks.

Polkawatch is an analytic tool designed to measure effective decentralization of Polkadot’s Validation process. [Polkawatch](https://polkawatch.app/) entered in production in 2022 Q2.

This proposal aims to fund the 2022 Q3 Continued Operation and implement Software Development and infrastructure improvements.

Our detailed [proposal can be found here](https://docs.google.com/document/d/1Hh1Vjn2tPwx2fAPFoY5WfOeltEJy-B-1HlukPSHLTI0/edit?usp=sharing).

Community feedabck to our proposal can be found in the [Discussion Post](https://polkadot.polkassembly.io/post/1212).


Polkadot decentralization analytics, Continued Operation and Improvements.

- Daniel is a leader in building technology and is working on a project called Fido, which helps people use blockchain more easily.
- Fido is a special wallet designed to make Web3 simple for everyone, avoiding complicated words that might confuse users.
- It uses a friendly chat system to interact with users and can be installed on different devices like computers and small hardware.
- The team wants to build Fido in three stages, focusing on the design, core functions, and then adding more features.
- Their goal is to help people do everyday things, like buying items or ordering food, using blockchain technology without needing to understand all its complexities. 
- They are asking for feedback from early users to improve the software before it's ready for everyone to use.

👋 *Hola* dear community and council! I'm [Daniel](https://github.com/olanod), long time ecosystem builder, senior "king" ambassador and founder of the [Virto Network](https://virto.network), the future hub of sustainable d-commerce and services for Polkadot. 

Earlier this year [with your support](https://polkadot.polkassembly.io/post/825) my team and I built [`libwallet`](https://github.com/virto-network/libwallet), an ultra-light and portable framework for creating fast, secure wallets of all kinds(web apps, extensions, mobile, desktop, hardware, hosted, etc.). It has been an on-going effort of continuous redesign and iteration to get to a point where we are now comfortable with its current architecture to start building real-world and user facing products that accommodate the many interesting use cases of our interconnected ecosystem.

It's our mission to *reeally* bring blockchain to the masses, for more than two years we've been creating solid foundations* and have being learning first hand from regular citizens what might take for people to use blockchain technology without realizing it and how not to compromise decentralization in the process.

*_**Previous work**: Web3 grant for [orml-payments](https://github.com/open-web3-stack/open-runtime-module-library/tree/master/payments), Kusama funded [Sube](https://github.com/virto-network/sube), [Kreivo](https://kusama.polkassembly.io/post/1520) common good parachain for Kusama, [Bloque](https://bloque.app) insta-stores, decentralized on&off ramps._

## Problem

Although a lot of progress has been made all over the place to ease the entry barrier to the Web3, we are still miles away from reaching mass adoption, it's inspiring to see the many efforts the community put in educating new users in the ways of blockchains and decentralization but there's still a long, possibly never ending journey ahead.   

It's great to see how the blockchain industry has one of the highest levels of innovation and technology advancement ever seen, the field moves at incredible speeds that are hard even for seasoned technologists to catch up, trying to reeducate the world in "the new better ways" is a common approach in Web3 however it might not be the best option, we could be neglecting the big majority of the population that won't try to follow the latest and greatest, instead we need to be inclusive and find ways to translate the new revolutionary ideas to a common language that results familiar to the people.

## Solution

We want help newcomers to easily navigate the world of Web3, wallets are the first interaction point of a user but we are starting simple and a bit different, with a set of constraints that I'll call now _the mom rule_, any term or action that would  require me to explain my mom what it is should be avoided, terms like(at least initially) blockchain, private key, hash, staking, NFTs, browser extension, or even wallet don't pass the mom rule so they are not making it in the first cut since they need explanation.

No metaverse-enabled-NFT-capable killer wallet this time, instead let us introduce you what we hope will become your reliable partner in the quest of exploring the sometimes scary Web3.

## [**Fido**](http://fido.sh) 🐶  Your trustworthy Web3 companion
![Logo Fido](https://fido.sh/fido.svg) 

Fido is more than a wallet, it's a development platform. On top of `libwallet` and a plugin runtime we've [prototyped before](https://github.com/virto-network/valor) we are building an ecosystem of wallets for different use cases that can be extended with a variety of services(skills and tricks) developed by the community in their language of preference(JS and WASM). Our target audience being non crypto-native users(including developers) means our product has to feel familiar(e.g. easy login, familiar technologies) yet decentralized.  
The Fido project breaks down mainly in two pieces,

- **Fido bot**: Your companion as hosted wallet that can be interacted with via chat using Matrix, the decentralized communications protocol(bridges to other chats can come later) or other protocols like a traditional HTTP API that gives developers access the different **skills** your Fido has learned. There will be multiple ways to install Fido so it can stay alert 24/7 and give you a hand whenever you need, depending on the platform it will use the most appropriate libwallet vault backend to keep secrets secure, an interesting one being a vault based on Matrix's [SSSS](https://matrix.org/docs/guides/implementing-more-advanced-e-2-ee-features-such-as-cross-signing#3-implementing-ssss) that we have [prototyped](https://github.com/virto-network/summa/pull/9), it allows backing up your wallet securely in your Matrix account to reduce the risk of losing access.

  - **Self-hosted** provided as a binary, docker image, or per-configured OS image that can be burned directly to a linux computer as small as a RaspberryPi Zero.
  - **Embedded Hardware**: Mini-Fido provided as firmware for popular microchips. Initial support for ESP32(-C3) and (future bonus based on what I have available) nrf52840/nrf9160 or the super tiny SAM L11 that could become more of a complementary chewing toy/key-holder/jewellery for Fido that can be powered with just an NFC field.
  - **In browser**_(not yet in scope)_ backed by a combination of service/shared workers(cool web technology) that allows Fido running fully decentralized in your browser without having to install anything. We would also provide an embeddable iframe/web-component that allows third-party applications access the many skills of your Fido. For Virto Marketplaces it will be an important feature that allows executing payments or approve certain transactions.
  - **[Matrix app service](https://matrix.org/docs/guides/application-services)**_(not in scope)_ For communities(like Virto's local communities and marketplaces) with their own Matrix server, this allows non-technical users to have an exclusive companion created for them automatically as soon as they join.
  - **Desktop shell**_(not in scope)_ Embedded in the desktop application.👇

- **Fido Shell**: A decentralized super-app for the Web(not an extension), desktop, mobile and terminal. It's  the graphical interface and Matrix client used to manage your Fido(s), where you can teach it new skills or tricks(mini appplets) and aggregate the many compatible applications created by the community.
_NOTE:  Initiall functionality will be very basic, we will only provide an "accounts skill" with a simple applet for minimal token transfers support and a very simple chat._

  - **Web**: Hosted in [fido.sh](https://fido.sh) and in decentralized form.
  - **Desktop**: As single executable file that works(should) in most platforms(I'll personally only test on Linux but other team members and community will for extended support).
  - **Mobile**(not in scope): Very similar deployment as the desktop application for IOS and Android. 

> ⚠️ To set expectations right, this first delivery of the Fido bot and the Fido shell should be consider experimental software not suitable to for managing large amounts of money that could be lost due to bugs in any of the components of our system. After launch we hope to gather enough feedback from the early adopters in the community before we recommend Fido for production use. 

> 🤔 Hard-core crypto fans might initially find the wallet boring as we are focused more on the real-world use cases of Virto that need to pass the _mom rule_, like buying a t-shirt, ordering food, calling a taxi, etc.

## Development and Milestones

We will divide the work in 3 stages that will last a total of **4-5 months**, after previous experiences developing small pieces of software at a time that are hard to visualize as part of a bigger whole, this time we aim for a longer runway as it has proven difficult to attract/keep talent when working conditions are short term driven and uncertain.

### Stage 1 - Design and architecture
Estimated duration: **1 month**

```
| Task                                         | role  | hours |
|----------------------------------------------|-------|-------|
| Project planning and break-down in GH issues | lead  |  1w   |
| Shell concept design                         | desig |  1w   |
| Brand, logo, web design and components       | desig |  2w   |
| Basic fido.sh with chat for updates          | f-dev |  2w   |
```

### Stage 2 - Wallet backends, Skills API & Shell UI components
Estimated duration: **2 months**

**This is the main stage of development for creating the core building blocks with great emphasis in embedded(no_std) support.**

```
| Task                                         | role  | hours |
|----------------------------------------------|-------|-------|
| Libwallet embedded vault (hardware keys)     | e-dev |  2w   |
| Libwallet Matrix vault with embedded support | b-dev |  2w   |
| Libwallet `pass` vault for hosted Fido       | b-dev |  1w   |
| *Libwallet BLE proxy for Fido->mini-Fido     | e-dev |  3w   |
| APIs design and "Skills SDK" prototype       | lead  |  2w   |
| Web components for shell and tricks/applets  | f-dev |  4w   |
| Fido Skills JS+WASM runtime                  | b-dev |  3w   |
```
_* Bonus with low priority_

### Stage 3 - Integrations and deployments
Estimated duration: **1 month**
``` 
| Task                                         | role  | hours |
|----------------------------------------------|-------|-------|
| Bot and Skills management Skill/API          | b-dev |  1w   |
| Blockchain&Accounts skill with Sube library  | b-dev |  2w   |
| Shell implementation and bot integration     | f-dev |  3w   |
| Accounts applet implementation               | f-dev |  2w   |
| *Bot management applet                       | f-dev |  1w   |
| *Developer applet for debugging              | f-dev |  1w   |
| Shell and Bot packages(image,docker,bin,...) | f-dev |  1w   |
| Testing and QA                               | lead  |  1w   |
| Infrastructure set-up and server deployments | lead  |  1w   |
```
_* Bonus with low priority_

Estimated total hours = `31w * 30h/w = 930h`  
Total USD cost with avg. hourly rate = `930h * USD$75/h = USD$69_750`  
**Total DOT cost** = `USD$69_750 / 7.394 USD/DOT(EMA30) = 9_433 DOT`

Fido Wallet(s)

- A proposal was made on August 11, 2022, asking for $100,383.24 to support public infrastructure for Polkadot, Statemint, and Westend.
- The service is focused on providing reliable and high-performance operations.
- There were many activities for Polkadot, with over 224 million responses in one day.
- The uptime for the networks was very high, reaching 99.98% over the last 90 days.
- In total, the Polkadot API served over 12 billion responses.
- For Westend and Statemint, there were also many responses, totaling over 609 million and 353 million, respectively. 
- The goal is to improve service availability to 99.99%, which means less downtime.

**Proponent**: 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf

**Date:** 11th August 2022

**Requested DOT:** 12,471.517 (USD $100,383.24)

**Short description:** Ongoing costs for the running of high performance, scalable, and reliable public infrastructure for Polkadot, Statemint and Westend.

**Raw Data:** https://docs.google.com/spreadsheets/d/1XwZjMtHVV8OgvqeUZQgMvY45nSL3tD19RFfTyIcRDq8/edit?usp=sharing

**Full Proposal:** https://docs.google.com/document/d/1cpNAYIdSlF9_uofueNHMkmvEtUPExBnJ92zZRgk9Afs/edit?usp=sharing

---

### Service Details

The last quarter showed a number of ups and downs in terms of numbers but still recorded high demand for Polkadot and OnFinality. May had a higher activity than the rest of the quarter which also had our largest daily responses in the quarter of over 224 million in a single day to Polkadot. 

We continued to execute on our efforts to provide unprecedented service stability and reliability to this ecosystem. All supported networks exceeded our 99.9% target, including 99.98% uptime for Polkadot over the last 90 days . At this stage, OnFinality is operationally striving for a minimum of 99.99% availability, which means less than an hour of downtime each year.

Between 2022-04-01 and 2022-06-31 our Polkadot API service has:

- Served a total of 12,264,823,022 (12 billion) responses
- Accumulated over 85 TB of data egress 
- The highest daily total was 224,203,539 responses in a single 24 hour period
- Our rolling 7 day average at the end of this period was over 133 million responses each day.
- Westend had over 609  million API responses in the period
- Statemint had over 353 million API responses in the period
- All time totals for Polkadot is 65,360,914,521 (65 Billion) since November, 2020
- At the end of this period the 90 day uptime for Polkadot, Statemint, and Westend was 99.98%, 99.98%, and 99.99%

**Full Proposal:** [https://docs.google.com/document/d/1cpNAYIdSlF9_uofueNHMkmvEtUPExBnJ92zZRgk9Afs/edit?usp=sharing](https://docs.google.com/document/d/1cpNAYIdSlF9_uofueNHMkmvEtUPExBnJ92zZRgk9Afs/edit?usp=sharing)

Council Motions