# Evidence-0002: Retention at Rank I

|                 |                                                                                             |
| --------------- | ------------------------------------------------------------------------------------------- |
| **Report Date** | 2024/09/30                                                             |
| **Submitted by**| s0me0ne-unkn0wn                                                                        |


## Member details

- Current rank: I
- Polkadot address: 13WGadgNgqSjiGQvfhimw9pX26mvGdYQ6XgrjPANSEDRoGMt
- Date of initial induction: 2024/04/22
- Date of last report: 2024/07/01
- Area(s) of Expertise/Interest: WebAssembly, PVF execution, Async backing integration, throughput benchmarking

## Reporting period

- Start date: 2024/07/02
- End date: 2024/09/30

## Evidence

I participated in the Coretime revenue integration into the production relay chains (polkadot-fellows/runtimes#384), a valuable contribution that brought us closer to the finalization of the Coretime enablement roadmap and made the chain [RFC-5](https://github.com/polkadot-fellows/RFCs/blob/main/text/0005-coretime-interface.md) complaint (to the extent that makes sense in the scope of the current protocol implementation). To prove the correctness of changes, I also co-authored a respective smoke test (paritytech/polkadot-sdk#4883), which became the very first CI test utilizing Zombienet v2 API.

Besides that, I performed refactoring to move blocking operations performed by the candidate validation subsystem to the external workers (paritytech/polkadot-sdk#5142). It's an optimization that allows smoother subsystem operation in case of high backpressure.

I also kept cleaning up the `im-online` removal mess (polkadot-fellows/runtimes#267), which is essential for maintaining the purity of the codebase.

My recent work included sophisticated research on how the state size affects throughput; its results have yet to be published. However, as a side effect of the study, I found, investigated, and reported a severe bug in block weight calculation (paritytech/polkadot-sdk#5229).

To sum up, my work during the reporting period was valuable, and thus, I'm applying for retention at Rank I.

## Voting record

|  Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments |
|---|---|---|---|---|
|I  |90%   |N/A   | I have voted on 0 out of 1 referendum in which I was eligible to vote (i.e 0% 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 0% voting agreement).  | The voting period of the only referendum I was eligible to vote on, fell on the period when I was OOO travelling. |
|II |80%   |N/A   |   |  |
|III|70%   |100%  |   |  |
|IV |60%   |90%   |   |  |
|V  |50%   |80%   |   |  |
|VI |40%   |70%   |   |  |


## Misc

- [ ] Question(s): 

- [ ] Concern(s): 

- [ ] Comment(s):