ambassador

senior_ambassador

head_ambassador

Please ensure that there is clear evidence that voting activity reaches the Manifesto-specified thresholds.

Not clear from the evidence which of the contributions are rank IV level ("valuable individual contributions to the (r)evolution of the protocol should have been demonstrated through broad architectural work together with novel designs").

Also, an in-person interview is generally required for all promotions to rank III or greater.



[@Gav](16SDAKg9N6kKAbhgDyxBXdHEwpwHUHs2CNEiLNGeZV55qHna-collectives) 

I would hope that for architectural work and novel designs these contributions can be considered:

Time Disputes: https://github.com/paritytech/polkadot-sdk/issues/742#issuecomment-1691884835 : The ability to mitigate nondeterminism issues on the protocol level.

I also played a role in the new disabling strategy: https://github.com/paritytech/polkadot-sdk/issues/784#issuecomment-1691886382 - although the major breakthrough here came from Overkillus.

The design for on-demand cumulus integration, can also be considered a novel design: https://github.com/paritytech/polkadot-sdk/issues/1487

Currently still evolving, a more resilient collator protocol: https://github.com/orgs/paritytech/projects/36/views/1?pane=issue&itemId=30536363 where I intend to make parts of it general purpose for hardening of other protocols as well.

I originally posted my evidence [here](https://github.com/polkadot-fellows/Evidences/pull/22/files). You can also find it [on IPFS](https://cloudflare-ipfs.com/ipfs/bafybeidqygovx57tn6hv45i6o6e3ggopffwngxpcr3wxywzshe4usabe5a) (might be slow to load).

Thank you for your consideration!

toRank

Executed

Submitted

DecisionStarted

DecisionDepositPlaced

ConfirmStarted

Confirmed

promote_to_iv_dan

Promote eskimor to rank IV

# Evidence-0001: Promotion to Rank IV

|                  |                  |
| ---------------- | ---------------- |
| **Report Date**  | 2024/06/07       |
| **Submitted by** | Robert Klotzner  |

## Member details

- Polkadot address: `12pRzYaysQz6Tr1e78sRmu9FGB8gu8yTek9x6xwVFFAwXTM8`

- Current rank: 3
- Date of initial induction: 2023/07/16
- Date of last report: N/A
- Area(s) of Expertise/Interest: `Parachains Consensus`

## Reporting period

- Start date: 2023/07/17
- End date: 2024/06/07

## Evidence

Examples of architectural and design work I participated in as required for rank 4:

- [on-demand cumulus integration](https://github.com/paritytech/polkadot-sdk/issues/1487)
- [more resilient collator protocol](https://github.com/orgs/paritytech/projects/36/views/1?pane=issue&itemId=30536363)
- [New disabling strategy](https://github.com/paritytech/polkadot-sdk/issues/784#issuecomment-1691886382)
- [New price controller for Agile Coretime](https://github.com/paritytech/polkadot-sdk/pull/4521)
- [time-disputes](https://github.com/paritytech/polkadot-sdk/issues/742#issuecomment-1691884835),
  a bit older but I believe interesting as it can fully solve security issues with
  indeterminism in a sharded network.

Other contributions:

- on-demand parachains. Most recent [here](https://github.com/paritytech/polkadot-sdk/pull/3190).
- Agile Coretime. Recent example [here](https://github.com/paritytech/polkadot-sdk/pull/1694).

[PR List](https://github.com/paritytech/polkadot-sdk/pulls?q=is%3Apr+author%3Aeskimor+is%3Aclosed)
[Reviews](https://github.com/paritytech/polkadot-sdk/pulls?q=is%3Apr+reviewed-by%3Aeskimor+)


### Blog Posts and Talks

- Talk: Protocol Berg, comparing parachain consensus to optimistic rollups: https://www.youtube.com/watch?v=O9QZveTdW5I
- Blog Post: Node Strategy [here](https://www.parity.io/blog/polkadot-node-strategy), originally posted on [grill](https://grillapp.net/12935/98722).
- Blog Post: [Core Time Pricing Explained](https://grillapp.net/12935/agile-coretime-pricing-explained-166522?ref=12935)



Evidence-0001: Promotion to Rank IV

members

proficient_members

fellows

architects

architects_adept

grand_architects

masters

masters_constant

grand_masters

retain_at_i_dan

retain_at_ii_dan

retain_at_iii_dan

retain_at_iv_dan

retain_at_v_dan

retain_at_vi_dan

promote_to_i_dan

promote_to_ii_dan

promote_to_iii_dan

promote_to_v_dan

promote_to_vi_dan

fast_promote_to_i_dan

fast_promote_to_ii_dan

fast_promote_to_iii_dan

Origin aggregated through weighted votes of those with rank 1 or above; `Success` is 1. Aka the "voice" of all Members.

Origin aggregated through weighted votes of those with rank 2 or above; `Success` is 2. Aka the "voice" of members at least II Dan

Origin aggregated through weighted votes of those with rank 3 or above; `Success` is 3. Aka the "voice" of all Fellows

Origin aggregated through weighted votes of those with rank 4 or above; `Success` is 4. Aka the "voice" of members at least IV Dan

Origin aggregated through weighted votes of those with rank 5 or above; `Success` is 5. Aka the "voice" of members at least V Dan

Origin aggregated through weighted votes of those with rank 6 or above; `Success` is 6. Aka the "voice" of members at least VI Dan

Origin aggregated through weighted votes of those with rank 7 or above; `Success` is 7. Aka the "voice" of all Masters

Origin aggregated through weighted votes of those with rank 8 or above; `Success` is 8. Aka the "voice" of members at least VIII Dan

Origin aggregated through weighted votes of those with rank 9 or above; `Success` is 9. Aka the "voice" of members at least IX Dan

Origin aggregated through weighted votes of those with rank 3 or above when voting on a fortnight-long track; `Success` is 1

Origin aggregated through weighted votes of those with rank 4 or above when voting on a fortnight-long track; `Success` is 2

Origin aggregated through weighted votes of those with rank 5 or above when voting on a fortnight-long track; `Success` is 3

Origin aggregated through weighted votes of those with rank 6 or above when voting on a fortnight-long track; `Success` is 4

Origin aggregated through weighted votes of those with rank 7 or above when voting on a fortnight-long track; `Success` is 5

Origin aggregated through weighted votes of those with rank 8 or above when voting on a fortnight-long track; `Success` is 6

Origin aggregated through weighted votes of those with rank 3 or above when voting on a month-long track; `Success` is 1

Origin aggregated through weighted votes of those with rank 4 or above when voting on a month-long track; `Success` is 2

Origin aggregated through weighted votes of those with rank 5 or above when voting on a month-long track; `Success` is 3

Origin aggregated through weighted votes of those with rank 6 or above when voting on a month-long track; `Success` is 4

Origin aggregated through weighted votes of those with rank 7 or above when voting on a month-long track; `Success` is 5

Origin aggregated through weighted votes of those with rank 8 or above when voting on a month-long track; `Success` is 6

Origin aggregated through weighted votes of those with rank 3 or above when voting on a 30 day long track; `Success` is 1.

Origin aggregated through weighted votes of those with rank 4 or above when voting on a 30 day long track; `Success` is 2.

Origin aggregated through weighted votes of those with rank 5 or above when voting on a 30 day long track; `Success` is 3.


Report Date	2024/06/07
Submitted by	Robert Klotzner