This repository has been archived by the owner on Jul 14, 2023. It is now read-only.
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've been working on the Parachains consensus team (aka Parachains-core) since mid 2020, but my early ecosystem contributions were to https:/paritytech/parity-common which contained core crates shared between Ethereum (called
parity
at the time) and Substrate clients and dates back to early 2019, that I've been maintaining since then. As a student of the guide, I've designed and implemented validator discovery used by collators and validators, grid topology for optimized networking, disputes rewards and slashing mechanism, introduced Prometheus metrics to Polkadot, implemented several subsystems and reviewed most of them.Some notable PRs:
uint
to match the performance of GMP in the worst cases)Besides PRs, I've reviewed numerous PRs (incl. finding issues in Grand Architect's code), spent countless hours investigating and fixing issues on testnets, participated in technical discussions, interviewing, onboarding new people and knowledge sharing.
Given the above, I'd apply to either Dan 4 or 3 at your discretion.