Previous: 2024-07-16 Technical Fellowship OpenDev Call
Video: https://www.youtube.com/watch?v=hAMo6wMOuak
Fellowship
New Fellowship Dashboard - New URL - https://polkadot-fellows.xyz/
New Fellowship Statistics Page by SubSquare
Members
- Approved
- Promote Rank 1: Andrei Eres, Alexandru Gheorghe, George,
- Retain Rank 1: Alin Dima, emalkaleci, Liam, s0me0ne-unk0wn, clangenb, timwu20, serban300, dharjeezy, bkontur, Cisco, Pablo Dorado, gupnik
- Retain Rank 2: sandreim, Adrian Catangiu., muharem, davxy, skundert
- Retain Rank 3: Alex
- Retain Rank 4: Andre
- Retain Rank 5: André Silva
- Ongoing
- Retain Rank 1: tdimitrov
- Retain Rank 2: Joe
- Retain Rank 6: bkchr
- Rejected
- Retain Wei at Rank III - 0 votes
- New Evaluations repo + manual
- Oliver: previously it was just a list of links. Now we have a more human-focused evaluation. No big change, just better to understand.
- FYI: Gavin’s evidence criteria - Fellowship Evidence Guidelines. - HackMD
Whitelistings
Approved
- Fixes & small updates
- Corrects the asset rates for USDT and USDC (& DED)
- Whitelist for 1127: Updating Snowbridge Pricing Parameters
- Whitelist for 1129: Increase validator set size to 400
- Robert K:
- pretty soon be able to go to 500, next goal is to have 1000
- Cores:
- 5 validators per core
- Kusama 100, next year 200; same for Polkadot
- Robert K:
- Features & Upgrades
- [Fellows] Referendum #173 - [Whitelisted Caller] Enable Elastic Scaling MVP node feature
- Robert K: fully live on Kusama, coming to Polkadot in the next months
- Whitelist: Upgrade BridgeHub: v1.2.8
- [Fellows] Referendum #192 Coretime Chain Registration
- [Fellows] Whitelist Runtime Upgrades to 1.3
- Whitelist referendum 1161
- [Fellows] Referendum #173 - [Whitelisted Caller] Enable Elastic Scaling MVP node feature
Fellowship Treasury
- Ecosystem Test Environment: Milestone 1 - 70k USD to Bryan Chen from the Fellowship Treasury
- but now resubmitted because of wrong units used - Ecosystem Test Environment: Milestone 1 (Attempt 2)
- Basti: Parachain can register XCM use cases. If there are XCM changes, they can be tested beforehand. Right now, if something is changed it might not show up as failing before production.
- Interim funding for Fellowship Secretary
RFCs
- Discussion
- Adrian: Ideally RFCs should be read before voting
- Bastian: The people voting should read it before voting. Not just vote to show up in the voting stats
- Adrian: Many in the Fellowship don’t even vote
- Approved
- XCM
- Approve RFC100: Introduce new XCM instruction: InitiateAssetsTransfer for complex asset transfers
- SubSquare | governance platform - Remove `require_weight_at_most` from XCM Transact by acatangiu · Pull Request #101 · polkadot-fellows/RFCs · GitHub - Remove
require_weight_at_most
from XCM Transact - RFC 105: Improved fee mechanism
- Adrian: shift in design of how we look at XCM fees. previously a more specific approach, this one is more general approach. available with V5. previously, consumer had high control over buying execution fees, but not everything else (e.g. transfer fees). Expect changes to happen slowly
- Voting for RFC #107: XCM hints.
- Francisco: freedom to add more instructions
- Approval for RFC 108 - [XCM]: Remove NetworkIds for testnets
- Franciso: small one. Testnets change every so often, so we should stay on the mainnet. In the future refer by genesis hash
- Approval for RFC 90 - Merkleized Metadata: Bring some clarification for the extrinsic inclusion
- Approve RFC 97 (Unbonding Queue)
- Approval for RFC 99 - Introduce a transaction extension version
- Approve RFC 103 - Constrain parachain block validity on a specific core #103
- Robert K: for elastic scaling. Currently launching MVP. But the full thing needs this RFC. Changes to the candidate descriptor in a binary compatible way (no parachain will break). Change for people building tooling. Specifically collator signature and collator description will change meaning in the descriptor.
- XCM
- Open
- Pure Proxy Replication by muharem · Pull Request #111 · polkadot-fellows/RFCs · GitHub - Pure Proxy Replication #111 - Joe, muharem
- Muharem: please read and comment
- Compress the State Response Message in State Sync by liuchengxu · Pull Request #112 · polkadot-fellows/RFCs · GitHub - Compress the State Response Message in State Sync #112
- Basti: faster fast sync for nodes
- The Unbrick Collective by pandres95 · Pull Request #117 · polkadot-fellows/RFCs · GitHub - Unbrick Collective
- Basti: unbricking needs to happen fast. but Fellowship shouldn’t fast-track those proposals. Having a dedicated group would also likely be faster.
- Pure Proxy Replication by muharem · Pull Request #111 · polkadot-fellows/RFCs · GitHub - Pure Proxy Replication #111 - Joe, muharem
Other Fellowship Issues
- New RFP repo! GitHub - polkadot-fellows/RFPs: Request for Proposals administered by the Fellowship.
- What are RFPs?
- Basti: If something needs to be done and funding from the Fellowship Treasury can be provided, this might be the case for RFPs. But the lines are still blurry on how it differs from RFCs
- RFP #1 - Fellowship UIs
- Basti: It is still complicated to do Fellowship things with the current UIs
- What are RFPs?
- FYI: Bryan Chen gave an update on XCQ - Cross-Consensus Query Language (XCQ) - #18 by indirection42
Roadmap
New Runtime Release Guidelines
- add runtime release guidelines in the README and update the PR template by anaelleltd · Pull Request #439 · polkadot-fellows/runtimes · GitHub
- Oliver: a checklist to not forget things
What’s next for Polkadot Runtime?
- Tommi: 1.4?
- Oliver: upgrade to stable2409, probably to stable2407 first
- Shawn: Merklized Distribution of Assets
- rather than minting for every individual user, submit a Merkle root that is generated offline
- e.g. for airdrops, DED airdrop had to distribute ED to every individual account
- with merklized distribution, every user would have to claim individually
- Kian:
- PR to make Inflation arguments parameterizable merged soon hopefully
- Adrian: Bridge
- Polkadot-Kusama
- transfer any asset
- exposure to Snowbridge assets on Kusama
- Snowbridge:
- “exporting” Polkadot-native assets to Ethereum
- already built, still to be integrated into the runtime
- then: XCMv5
- Snowbridge V2 (needs XCMv5)
- lower fees
- allow unordered messages
- improve UX: 1 click end-to-end, pay with ETH everywhere
- “exporting” Polkadot-native assets to Ethereum
- Polkadot-Kusama
- Seyed
- writing an RFC to make validators sign BLS (?) for BEEFY to make the bridge more efficient.
Coretime
- Bulk Coretime
- Robert K: Auto-Renew is an upcoming feature to place DOT in an account and renew bulk coretime
- Donal: There is a market for secondary markets
- On-Demand
- Robert K:
- about to launch on Polkadot
- we de-prioritized super-easy integration for teams. The basic offer is there, but on-demand is so cheap that there won’t be a big demand for on-demand atm
- basic functionality available
- Donal: But no cores made available yet
- Robert K:
Elastic Scaling
- Robert K: MVP live on Testnets, not yet on Kusama
Plaza (Joe)
- Joe
- 3 projects
- EVM compatibility
- moving staking, governance, and balances to AssetHub
- changing the APIs, view functions
- will report more in the coming weeks
- 3 projects
- Shawn: what can be done to add more ppl to the project?
- Joe: refactor assets, block number / time relationships, implementing view functions, high level APIs so more devs can use it
- Bast: putting abstractions in the runtime might not be a good idea
- Joe: The 3 projects don’t depend on each other, people work on those are quite different, so no need to prioritize one over the other
- Shawn: how many L3 and L4 can we add to the project? form open chat groups?
- Joe: quite a few
- Robert K: would be great to have wrapping library
- Joe: yes, imagine you have the same asset on multiple chains. Would be good to query the balance of those. Kian and James on this.
- Kian: tldr on view function - it nicely complements Plaza. We started talking about it a year ago. We would like to have a high-level spec of engaging with Polkaot and not this chain or that chain. Or at least give the consumer view functions.
Stabilizing Polkadot (Oliver)
- GitHub - paritytech/release-registry: Tracking past and future releases of the Polkadot SDK. is a new repo that gives timelines for when releases go out of support
- will also be relevant for AssetHub migration in Plaza
Total Issuance Fix (Oliver)
total balance shown on the RPC was different from the real issuance
KSM is off by 56
DOT is off by 21.6k
JAM
- some important changes to the GrayPaper → on the website
- Final piece of functionality: audit accumulation
- Getting work packages that want to use the data of previous work packages in a low latency fashion
- Get Parachains in all situations, including async backing