Retain Karol Kokoszka at rank 2

Deciding
No context provided.
Reply
Up
Share

Evidence for Retention

Argument-0002: Retention at Rank II

Report Date 2026/09/21
Submitted by Karol Kokoszka

Member details

Reporting period

  • Start date: 2026/06/03
  • End date: 2026/09/21

Argument

During this reporting period I focused on Levity. I took ownership of releasing and deploying its next phase to Polkadot. This included reviews, pallet releases, testnet verification, support for other teams, stress testing, and coordination with node operators. I also continued contributing to ecosystem projects: I completed Polkadot-Kusama bridge support in Chopsticks, added features to the referendum testing tool and maintained it, and added Bulletin Chain scenarios to the Polkadot Ecosystem Tests.

Levity (Bulletin Chain + HOP)

Preparing the Polkadot launch required onboarding more collators. I took technical ownership of preparing and testing referendum #1918, which added invulnerables to the Bulletin Chain collator set, and I submitted it on-chain. The referendum has been executed.

My most important work was taking over the integration of the Bulletin Chain into the Fellowship runtimes and completing it in #1170. This deployed the Bulletin Chain's main business logic on Polkadot in the 2.4.0 runtime release.

I worked on HOP testing and integration. I added HOP scenarios to the stress-testing tooling (#797), and gated HOP uploads on the HopRuntimeApi authorization check in the community iOS and Android apps.

I am one of the leading engineers on Levity. My work includes new features, improvements to the testing tools, and reviews of other people's changes. A full list exists in the polkadot-bulletin-chain repository, in the pull requests I am involved in.

Chopsticks

I completed the Polkadot-Kusama bridge support for Chopsticks, which allows testing of bridged scenarios. I merged it in #1029, and Chopsticks 1.5.0 contains it.

Governance: Polkadot Referenda Tester

I added support for the bridged scenario where the Polkadot Fellowship whitelists a call on the Kusama Asset Hub (#45). Other additions include chaining several referenda into a single dry run and running post-referendum test scripts (#54). I continue to maintain the project so that it works with the latest runtimes.

Polkadot Ecosystem Tests

I added the scenario where the Polkadot Fellowship whitelists a call on the Kusama Asset Hub (#643), and extended the existing system, upgrade and XCM suites to cover Bulletin Polkadot (#682).

Voting record

Ranks Activity thresholds Agreement thresholds Member's voting activities Comments
I 90% N/A
II 80% N/A I have voted on 0 out of 0 referenda in which I was eligible to vote. There were no valid referenda I was eligible to vote on
III 70% 100%
IV 60% 90%
V 50% 80%
VI 40% 70%
Status
Decision14d
Confirmation
1hr
Attempts
0
Tally
100%Aye
0%Nay
Aye3
Nay0
  • 10.00%
  • 0.0%

    Threshold

  • 0.0%
Bare Aye1
Max Voters11
Check how referenda works here.
Call
Metadata
Timeline3
Curves
Comments