Report Date | 2025/03/19 |
Submitted by | s0me0ne-unkn0wn |
During the reporting period, I was busy pushing forward the PolkaVM integration. That included filing and getting approved RFC-135, which standardized binary blob prefixes to make it possible to use different execution engines effectively. The implementation of said RFC is already a part of the PolkaVM integration PR. That is a valuable contribution as it paves the way to more performant and deterministic execution, thus making Polkadot more secure. It also agrees with principles or JAM, which will use PolkaVM as a main execution engine.
Besides that, I started my way toward implementing the long-awaited RFC-4 which will enable in-runtime allocation, making runtime execution faster and solving some significant problems regarding execution determinism. As the first step, I picked up a relevant but stale PR and revived it, and now I'm collecting reviews for that breaking runtime interface change.
I have also worked on NFT throughput benchmarking for specific cases involving large chain states and have created some tooling to support that need: a specialized version of the sTPS tool and a simple state bloater. That is crucial to prevent future problems that could emerge in parachains with quickly growing state size. For the same reason, I proposed increasing the PoV size on Polkadot to 10 MiB.
To sum up, my work during the reporting period was valuable, and thus, I'm applying for retention at Rank I.
Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments |
---|---|---|---|---|
I | 90% | N/A | I have voted on 0 out of 0 referendum in which I was eligible to vote (i.e undefined% voting activity). Out of 0 referenda in which members of higher ranks were in complete agreement, I have voted in line with the consensus 0 times (i.e undefined% voting agreement). | |
II | 80% | N/A | ||
III | 70% | 100% | ||
IV | 60% | 90% | ||
V | 50% | 80% | ||
VI | 40% | 70% |
Question(s):
Concern(s):
Comment(s):
Threshold