| Report Date | 2024/11/08 |
| Submitted by | Francisco Aguirre |
@cisco:parity.io129EYiTbv2J4LkYqRNssUfMuxNLYN8TW2LgfG1Gqyj8wCcs712024/05/312024/08/14XCM2024/08/142024/11/08During the reporting period covered by this letter, my main focus was the newest iteration of the XCM format, version 5. I also helped design Snowbridge V2 and continued my efforts in improving and integrating the new XCM runtime APIs in the ecosystem.
I participated in a retreat with the snowfork team where we all worked together to design Snowbridge V2. It was a good step to understand how the bridge worked and bridges in general. The final design ended up heavily using some XCMv5 features to provide a simpler and cheaper protocol for users.
XCMv5 was merged recently. Most of my effort this period went into it. I started it as its own milestone branch from where we created a branch per RFC implementations. This way we could review each smaller PR individually but make only one merge to master, not needing feature flags for the new version. I worked on making sure the milestone branch was always up-to-date with master. I also implemented some of the PRs that went into it, like not needing to specify weight on Transact and the new fee payment instruction. These improvements, along with the whole of XCMv5, will make errors rarer, improving the current situation.
I continued development on the XcmPaymentApi and DryRunApi. I fixed some bugs like removing redundant information and clearing messages before dry-running and continued integrating it in runtimes with returning assets in pools with the native asset as fee payment options (PRs SDK#5599 and SDK#6080). Some of these fixes are not yet in the fellowship runtimes since the SDK version is lagging behind. I updated asset hub foreign asset ids from XCMv3 to XCMv4 to prepare for integrating sdk stable2490.
These APIs are already live in the runtimes but apps still need time to integrate them. I made an app to allow users and devs to use them and show how they can be used. I also worked with the PAPI (Polkadot-API) team to develop an XCM SDK that integrates these APIs to estimate fees along the whole journey of an XCM, still under development. The runtime APIs and new fee payment mechanism will enable apps to correctly estimate XCM fees.
Next period, my focus will be in getting XCMv5 to the hands of developers and users and making it as easy as possible to use it.
Provide your voting record in relation to required thresholds for your rank.
| Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments |
|---|---|---|---|---|
| I | 90% | N/A | I have voted on 0 out of 1 referenda in which I was eligible to vote (0% voting activity) | There's not much I can vote on as a rank I. However, there was 1 referendum that was open to anyone. I will start to look at referenda frequently, despite my rank. |
| II | 80% | N/A | ||
| III | 70% | 100% | ||
| IV | 60% | 90% | ||
| V | 50% | 80% | ||
| VI | 40% | 70% |
Threshold