This repository was archived by the owner on Jul 14, 2023. It is now read-only.
Member request #57
Open
Member request #57
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bkchr
approved these changes
Nov 11, 2022
jacogr
approved these changes
Nov 12, 2022
andresilva
approved these changes
Mar 20, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am eskimor and have been working on Parachain Consensus for the last two
years. Given this time period I am applying for the III Dan: Fellow.
Major code contributions:
My first subsystem, was a rewrite of availability-distribution to make it
request/response based and thus efficient enough for production networks:
paritytech/polkadot#2423
That work was based on previously introducing request/response protocols into
Polkadot:
paritytech/polkadot#2352
paritytech/polkadot#2263
I then ported further subsystem to more efficient request/response protocols:
paritytech/polkadot#2621
paritytech/polkadot#2640
Also statement-distribution needed some boost to deal with large statements
(e.g. runtime upgrades) properly:
paritytech/polkadot#2803
paritytech/polkadot#2984
Later I started focusing on disputes and designed and implemented large parts of
our current dispute system:
paritytech/polkadot#3158
paritytech/polkadot#3282
paritytech/polkadot#4134
paritytech/polkadot#5323
paritytech/polkadot#5785
paritytech/polkadot#5894
Educational
Major contributions to the implementer's guide, in particular to the dispute
system, which were very well received. I also participated at the Polkadot
Academy as a lector. As a team lead I constantly mentor team members in
chat, calls, PR reviews and forum.