# Argument-0000: Retention at Rank 5 
|                 |                                                                                             |
| --------------- | ------------------------------------------------------------------------------------------- |
| **Report Date** | (2025/10/27)                                             |
| **Submitted by**|    1eTPAR2TuqLyidmPT9rMmuycHVm9s9czu78sePqg2KHMDrE                                                                 | 

## Member details

- Matrix username: @kianenigma
- Polkadot address: `1eTPAR2TuqLyidmPT9rMmuycHVm9s9czu78sePqg2KHMDrE`
- Current rank: 5
- Date of initial induction: seeding
- Date of last report: [10/05/2025](https://collectives.subsquare.io/fellowship/referenda/342)
- Area(s) of Expertise/Interest: 
    - FRAME
    - Staking / NPoS
    - JAM
- Status: Active

## Reporting period
- Start date: 2025/05/10
- End date: 2025/11/31


## Argument
My work on Polkadot has continued since promotion to Rank V primarily around the Hub migration and related changes to the staking system. Through this project, I am taking a leading role again in the staking system and ensuring the system works flawlessly in AssetHubs, and addressing issues that are raised by validators and nominators in support chats.

### Engineering Efforts

More specifically, since the last reporting period, I have: 

* Most importantly, make Polkadot's future staking system bullet-proof by: 
  * implementing a more resilient [VMP messaging scheme](https://github.com/polkadot-fellows/runtimes/pull/950)
  * Moving all operations outside of [`on_initialize` to `on_poll`](https://github.com/paritytech/polkadot-sdk/pull/9925)
  * Provided and signed-off on the final configurations of the staking system in [Kusama](https://github.com/polkadot-fellows/runtimes/pull/883) and [Polkadot](https://github.com/polkadot-fellows/runtimes/pull/969)
  * Thanks to reports from validators, identified and hot-fixed to (so far) [only bug](https://forum.polkadot.network/t/psa-disruption-to-kusama-validators-self-stake-and-rewards/15599) that was introduced as a part of Kusama AHM
* Secondly, on the overall testing of AHM, I have contributed by [providing a clear goal and mentoring others towards it](https://github.com/paritytech/polkadot-sdk/issues/8764), making AHM Dryruns reproducible and debug-able, consequently enabling other fellowship members to verify the process. 
* Last but not least, I am actively reviewing and planning around making sure the following community approved initiatives are on the right track to be enacted right after AHM:
  * [New issuance model](https://github.com/polkadot-fellows/runtimes/pull/898)
  * [New flexible unbonding queue](https://github.com/paritytech/polkadot-sdk/pull/8298)

### Education and Publication

While my side-activities has been on the decline due to the intense workload of AHM, some work is being done there as usual.

* Participated as a JAM lecturer in PBA6 Bali
* A number of new talks given and blog post published, all visible and dated in [my website](https://blog.kianenigma.com/)
* I am in the process of distilling all of my knowledge about the Web3 technologies as a whole (and not just Polkadot) in [a long format blog post](https://blog.kianenigma.com/blockchain-reimagined-draft/), which I expect to finish by end of the year. 

## Voting record
*Provide your voting record in relation to required thresholds for your rank.* 

|  Ranks | Activity thresholds | Agreement thresholds | Member's voting activities | Comments |
|---|---|---|---|---|
|V  |50%   |80%   | 90%+ Activity with 100% agreement   | My participation rate has been more than 90% in [the last reporting period](https://collectives.subsquare.io/user/1eTPAR2TuqLyidmPT9rMmuycHVm9s9czu78sePqg2KHMDrE/fellowship) |