# Argument-0004: Retention at Rank I

|                  |                   |
| ---------------- | ----------------- |
| **Report Date**  | 2026-05-28        |
| **Submitted by** | Ludovic Domingues |

## Member details

- Matrix username: @krayt78:matrix.org
- Polkadot address: 14AgwoPjcRiEEJgjfHmvAqkjdERCG26WEvQUoGLuBzcXKMS2
- Current rank: Rank I (Humble Member)
- Date of initial induction: 2024-06-18
- Date of last report: 2026-02-17
- Area(s) of Expertise/Interest: 
    - FRAME
    - Runtime

## Reporting period

- Start date: 2026/03/01
- End date: 2026/05/28

---

## Argument

My focus throughout the period has mainly been on mentoring some new devs coming from the latest PBA program in Lisbon.
In terms of actual code I finished working on the pallet-multisig migration and am still tracking the ongoing Product `Currency` → `fungible`
migration in `polkadot-sdk`, tracked under
[paritytech/polkadot-sdk#226](https://github.com/paritytech/polkadot-sdk/issues/226):
replacing the legacy `ReservableCurrency` / `LockableCurrency` patterns across
in-scope pallets with the modern `fungible` hold/freeze model.


| Pallet           | PR                                                              | Status                  |
| ---------------- | --------------------------------------------------------------- | ----------------------- |
| pallet-referenda | [#10701](https://github.com/paritytech/polkadot-sdk/pull/10701) | Waiting for a dependency to be merged  |
| pallet-preimage  | [#11066](https://github.com/paritytech/polkadot-sdk/pull/11066) | Need review  |
| pallet-multisig  | [#11064](https://github.com/paritytech/polkadot-sdk/pull/11064) | Need review  |
| pallet-indices   | [#9610](https://github.com/paritytech/polkadot-sdk/pull/9610)   | Need review  |
| pallet-lottery   | [#10045](https://github.com/paritytech/polkadot-sdk/pull/10045) | Approved / Waiting for merge  |

All five are up to date. They are either already approved by maintainers and
sitting in the merge queue, or still awaiting review. They tend to get
deprioritised behind other PRs, so whenever one of those lands and
creates a merge conflict, I rebase mine and resolve it to keep them merge-ready.
None have landed during this period, but they are all in a ready-to-merge state
and I have kept them there throughout.

---

## Voting record

|  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 NaN% 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 NaN% voting agreement).  |  |
|II |80%   |N/A   |   |  |
|III|70%   |100%  |   |  |
|IV |60%   |90%   |   |  |
|V  |50%   |80%   |   |  |
|VI |40%   |70%   |   |  |


## Misc

- [ ] Question(s): 

- [ ] Concern(s): 

- [ ] Comment(s):