A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | https://github.com/filecoin-project/notary-governance/issues/46 | ||||||||||||||
2 | |||||||||||||||
3 | Verifier Leveling Rubric | ||||||||||||||
4 | Category | L1 | L2 | L3 | L4 | L5 | |||||||||
5 | Long Term Network Alignment = Max(Time Commitment, Stake Exposure) | 0 | |||||||||||||
6 | Time Commitment | Substantial, sustained contributions to Filecoin over 6 mos (as a miner, developer, or active community organizer) | Substantial, sustained contributions to Filecoin over 1 year (as a miner, developer, or engaged community member) | Substantial, sustained contributions to Filecoin over 2 years (as a miner, developer, or engaged community member) | Substantial, sustained contributions to Filecoin over 3 years (as a miner, developer, or engaged community member) | Substantial, sustained contributions to Filecoin over 4 years (as a miner, developer, or engaged community member) | . | 0 | // Just shy of 6 mos | ||||||
7 | Stake Exposure | 100k tokens at stake | 500k tokens at stake | 1MM tokens at stake | 5MM tokens at stake | 10MM tokens at stake | . | 0 | |||||||
8 | Industry Reputation = Max(In-protocol Reputation, In-protocol Security, Organization Reputation, Individual Reputation) | . | 2 | ||||||||||||
9 | In-protocol Reputation | Reputable leader in Filecoin Ecosystem for >6 mos yr (contributions to the Filecoin protocol and/or spec), actively supporting, and cultivating the success of other members in the Filecoin ecosystem | Reputable leader in Filecoin Ecosystem for 2 yr (contributions to the Filecoin protocol and/or spec), actively supporting, and cultivating the success of other members in the Filecoin ecosystem | Reputable leader in Filecoin Ecosystem for 3 yr (contributions to the Filecoin protocol and/or spec), actively supporting, and cultivating the success of other members in the Filecoin ecosystem | Reputable leader in Filecoin Ecosystem for 4 yr (contributions to the Filecoin protocol and/or spec), actively supporting, and cultivating the success of other members in the Filecoin ecosystem | Reputable leader in Filecoin Ecosystem for 4+ yr (contributions to the Filecoin protocol and/or spec), actively supporting, and cultivating the success of other members in the Filecoin ecosystem | . | 0 | // Just shy of 6 mos | ||||||
10 | In-protocol security | Contributions in identifying, responsibly disclosing, and fixing multiple low security vulnerabilities in protocols or services in the Filecoin community | Sustained contributions identifying, responsibly disclosing, and fixing multiple medium protocol or service vulnerabilities, in the Filecoin community | Sustained contributions identifying, responsibly disclosing, and fixing high/critical protocol or service vulnerabilities, in the Filecoin community | Sustained contributions identifying, responsibly disclosing, and fixing multiple high/critical protocol or service vulnerabilities, in the Filecoin community | L4 Requirements | . | 0 | |||||||
11 | Organization Reputation | Community Members | Reputable entities in Filecoin-adjacent communities with substantially adopted services / products (e.g. Supranational, Pinata, Infura) | Major organizations in Web3 (e.g. Polychain, Consensys) | Major organizations in Web2 and Web3 (e.g. Ethereum Foundation, Vimeo) | Household names / Publicly traded Institutions (e.g. Andreseen Horowitz, Netflix) | . | 1 | |||||||
12 | Individual Reputation | Has access to 2+ social media accounts which individually have audiences > 500 where they will post publicly about their status as a notary if approved | Has access to 2+ social media accounts which individually have audiences > 1000 where they will post publicly about their status as a notary if approved | Has access to 2+ social media accounts which individually have audiences > 10000 where they will post publicly about their status as a notary if approved | - | - | 2 | // Based on LinkedIn, if two or more of your officers post a message announcing your selection as a Notary (meeting the specified criteria) you'd meet this requirement! | |||||||
13 | Diversity and Decentralization = .3*Use Case Diversity + .7*Geographic Distribution | . | 5 | ||||||||||||
14 | Geographic Distribution | Highly represented geography (>=4 existing or >=30% global DataCap has been allocated to the Region) | Highly represented geography (3 existing or 20-30% global DataCap has been allocated to the Region) | Somewhat represented geography (2 existing OR 10-20% global DataCap has been allocated to the Region) | Under-represented geography (1 existing Notary OR <10% global DataCap has been allocated to the Region)) | Unrepresented geography | . | 5 | |||||||
15 | Use Case Diversity | Highly represented use case (4 or more existing) | Highly represented geography (3 existing) | Somewhat represented usecase (2 existing) | Under-represented usecase (1 existing) | Unrepresented usecase | . | 5 | |||||||
16 | . | ||||||||||||||
17 | Allocation Ranking | . | 2 | ||||||||||||
18 | L1=Eligible up to 10TB | L2=Eligible up to 100TB | L3=Eligible up to 1PB | L4=Eligible up to 10PB | L5=Eligible up to 50PB | . | |||||||||
19 | Weighted Notary Leveling (see cell) | . | 2 | ||||||||||||
20 | Weighted Notary Leveling | Floor(.3*Long term network alignment + .4* Industry Reputation + .3*Diversity and Decentralization) | Floor(.3*Long term network alignment + .4* Industry Reputation + .3*Diversity and Decentralization) | Floor(.3*Long term network alignment + .4* Industry Reputation + .3*Diversity and Decentralization) | Floor(.3*Long term network alignment + .4* Industry Reputation + .3*Diversity and Decentralization) | Floor(.3*Long term network alignment + .4* Industry Reputation + .3*Diversity and Decentralization) | . | 2 | |||||||
21 | Concreteness of Allocation Plan =FLOOR(0.333*Allocation Strategy+0.333*Client Due Diligence+0.333*Bookkeeping Plan) | 3 | |||||||||||||
22 | Allocation Strategy | Minimal specificity in allocation strategy but demonstrates how allocation will reflect the Principles. | - | Moderate specificity in allocation strategy in alignment with the Principles. | - | Detailed plan, including tooling, to successfully allocate DataCap in a way that reflects the goals and values of the Principles. | . | 3 | // In a subsequent application specificity on the actual rubric you will / did use would bump this up! | ||||||
23 | Client Due Diligence | Minimal due diligence protecting against abuse and vetting clients. | - | Base due diligence protecting against abuse and vetting clients. | - | Robust due diligence for protecting against abuse and vetting clients. | . | 5 | |||||||
24 | Bookkeeping Plan | Minimal bookkeeping plan to document DataCap allocation decision and ready to provide justification when challenged or dispute. | Base bookkeeping plan to document DataCap allocation decision and ready to provide justification when challenged or dispute. | Detailed bookkeeping plan, with tooling, to document DataCap allocation decision and ready to provide justification when challenged or dispute. | Detailed bookkeeping plan, with tooling and defined audit processes, to document DataCap allocation decision and ready to provide justification when challenged or dispute. | L4 Requirements | . | 3 | // Scored assuming you'll use the same framework as the Filecoin Foundation! | ||||||
25 | Track Record | . | 1 | ||||||||||||
26 | Past Allocation | No previous track record. | Successful allocation <100TB of DataCap with no consistent pattern of impropriety*. Justifications and audit trail can be produced when challenged. | Successful allocation of 100TB of DataCap with no consistent pattern of impropriety*. Convincing justifications and audit trail can be produced when challenged. | Successful allocation of 1PB of DataCap with no consistent pattern of impropriety*. Convincing justifications and audit trail can be produced when challenged. | Successful allocation of 10PB of DataCap with no consistent pattern of impropriety*. Convincing justifications and audit trail can be produced when challenged. | . | 1 | |||||||
27 | Scale of Allocation | 3 | |||||||||||||
28 | Volume of Data | Volume of DataCap Requested = <10TB | Volume of DataCap Requested = 10-100TB | Volume of DataCap Requested = 100TB- 1PB | Volume of DataCap Requested = 1-10PB | Volume of DataCap Requested = 10PB+ | . | 3 | |||||||
29 | . | ||||||||||||||
30 | Final Allocation Amount =MIN(ROUND(0.5*Track Record + 0.3*Weighted Notary Leveling + 0.2*Concretness of Allocation Plan), Scale of Allocation) | . | 2 | ||||||||||||
31 | Unrounded Score (for tiebreaking only) | 1.7 | |||||||||||||
32 | |||||||||||||||
33 | |||||||||||||||
34 | |||||||||||||||
35 | |||||||||||||||
36 | |||||||||||||||
37 | |||||||||||||||
38 | |||||||||||||||
39 | |||||||||||||||
40 | |||||||||||||||
41 | |||||||||||||||
42 | |||||||||||||||
43 | |||||||||||||||
44 | |||||||||||||||
45 | |||||||||||||||
46 | |||||||||||||||
47 | |||||||||||||||
48 | |||||||||||||||
49 | |||||||||||||||
50 | |||||||||||||||
51 | |||||||||||||||
52 | |||||||||||||||
53 | |||||||||||||||
54 | |||||||||||||||
55 | |||||||||||||||
56 | |||||||||||||||
57 | |||||||||||||||
58 | |||||||||||||||
59 | |||||||||||||||
60 | |||||||||||||||
61 | |||||||||||||||
62 | |||||||||||||||
63 | |||||||||||||||
64 | |||||||||||||||
65 | |||||||||||||||
66 | |||||||||||||||
67 | |||||||||||||||
68 | |||||||||||||||
69 | |||||||||||||||
70 | |||||||||||||||
71 | |||||||||||||||
72 | |||||||||||||||
73 | |||||||||||||||
74 | |||||||||||||||
75 | |||||||||||||||
76 | |||||||||||||||
77 | |||||||||||||||
78 | |||||||||||||||
79 | |||||||||||||||
80 | |||||||||||||||
81 | |||||||||||||||
82 | |||||||||||||||
83 | |||||||||||||||
84 | |||||||||||||||
85 | |||||||||||||||
86 | |||||||||||||||
87 | |||||||||||||||
88 | |||||||||||||||
89 | |||||||||||||||
90 | |||||||||||||||
91 | |||||||||||||||
92 | |||||||||||||||
93 | |||||||||||||||
94 | |||||||||||||||
95 | |||||||||||||||
96 | |||||||||||||||
97 | |||||||||||||||
98 | |||||||||||||||
99 | |||||||||||||||
100 |