Skip to content
This repository has been archived by the owner on Jul 14, 2023. It is now read-only.

Member Request #1

Closed
wants to merge 2 commits into from
Closed

Member Request #1

wants to merge 2 commits into from

Conversation

tugytur
Copy link

@tugytur tugytur commented Sep 26, 2022

Rank range:

I believe that I should be in the rank range of 2-3.

Earliest reference:

paritytech/polkadot#5168

auxiliary component:

Build sub 5-minute failover solution for validators. https://parasnaps.io/

Comment:

I come from the Infrastructure/Validator side. I'm experienced in running validators since NPoS was enabled.
But there are no public contributions/activity from my side until last year when I co-founded a company that focuses on the Dotsama ecosystem.

@rrtti
Copy link
Contributor

rrtti commented Sep 27, 2022

Hi @tugytur!

Ranks higher than I Dan come with a minimum time period since I Dan as well as additional specific requirements per rank. To attain the level of I Dan please review section 6.2 of the Manifesto and see the requirements there:

The Candidate should have made three clear demonstrations of protocol expertise. Possible examples of this may be: identifying and fixing a non-trivial protocol issue; being available and playing a crucial operational role for a network fix; proposing a reasonable and non-trivial protocol innovation; or doing a valuable, innovative and insightful refactoring or alteration.

Also

  • Primarily designed and implemented a minor or auxiliary component.
  • Should be able to list all key goals/principles/tenets of project philosophy and how these relate to technology

Please provide specific details on the three clear demonstrations of Polkadot protocol expertise, and the Polkadot core component you primarily designed and implemented. Furthermore please provide details on the proportion of your time given over to developing Polkadot core protocol (as described in Manifesto section 2.4 and in particular not any incidental or application-specific code) since the point at which these requirements were fulfilled.

Furthermore, Manifesto sections 6.3, 6.4, 6.5 and 6.6 all state that a time period of 12 months should generally be expected to have elapsed since attaining the prior rank, leading to a reasonable minimum period of 1 year since fulfilling I Dan requirements for attaining II Dan, 2 years since fulfilling I Dan requirements for attaining III Dan and so on.

Finally, for a rank higher and I Dan, please ensure that all requirements set out in the Manifesto for that rank and any prior ranks have been met and are clearly demonstrated. Please note that for III Dan and higher, a high degree of availability for the network must have been demonstrated.

@tugytur
Copy link
Author

tugytur commented Sep 28, 2022

Hi @rrtti ,

Thanks for the feedback.
After your input and further consideration, if then I Dan would be the appropriate fit.

By having expertise in Infrastructure and running validators my contributions come from debugging, being available to provide details on issues, feature request and building solutions to help other validator operators.

Due to the nature of running validators I'm constantly available and my activity is mainly focused in the validator related matrix channels.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants