Argument-0002: Retention at Rank I

Member details

• Matrix username: @kanas0:matrix.org
• Polkadot address: 12pCUGSwoW4Xek48TLUHCFhrvAdjmciMMLJoRJD8HWP5saXH
• Current rank: I
• Date of initial induction: 2025/10/31
• Date of last report: 2026/05/25
• Link to last report: Argument-0001: Promotion to Rank I
• Area(s) of Expertise/Interest: FRAME, XCM, Omni-Node, consensus (BABE/GRANDPA), System parachain runtimes

Reporting period

• Start date: 2026/05/26
• End date: 2026/08/25

Argument

I am Nasihudeen Jimoh (Kanasjnr on GitHub), seeking retention at Rank I. Since promotion in June (referendum #541), I have continued contributing to polkadot-sdk, with supporting work toward polkadot-fellows/runtimes and public protocol analysis on the Polkadot Forum.

I took ownership of polkadot-sdk#11561 and drove deprecation cleanup across the SDK, landing one removal per PR as reviewers requested. The goal is to retire dead APIs so runtime authors are not steered toward unsupported paths. The most impactful merges this period dropped long-deprecated surfaces that had already been superseded for multiple release cycles — schedule::v1 (#12584), GenesisBuild (#12529), XCM builder and executor re-exports (#12503, #12505), and deprecated native/wasm executor helpers (#12669). Further removals across FRAME, XCM, node, and pallets are tracked in the issue; see all merged PRs and open PRs.

Beyond deprecation, I landed try-runtime exposure in bridge-hub-test-utils. ExtrinsicBaseWeight refinement, which corrects base extrinsic weight for FRAME-benchmarked runtimes, and descriptive module invalidity, which gives wallets and indexers actionable rejection reasons instead of opaque module indices, have both been approved and are pending merge. I am also working on XCM barrier weight accounting (#11302) and Asset Hub safe-mode / tx-pause deployment (runtimes#1164).

For knowledge-sharing, I published the concluding part of my consensus-lab series: The Double-Edged Sword of Finality. Using substrate-consensus-lab, I showed that GRANDPA finality is correctness-agnostic: a minority migration bug is quarantined by state-root divergence, but a supermajority-infected upgrade finalizes corrupt state permanently. The post ties those results to why Polkadot relies on governance delay, staging networks, and try-runtime before mainnet upgrades.

I intend to keep this mix of steady SDK maintenance and deeper FRAME/XCM work, and to participate more actively in Fellowship review and RFC discussion.

Voting record

Misc

• Question(s):
• Concern(s):
• Comment(s):