Appreciate these comments and want to bring up a few additional points.
@ceresstation I really like the additional considerations you outline for us around worldbuilding, authenticity, principles and expansiveness/lore.
With regard to the why for each name - it was originally asked that people who write in names also give their reasoning, which we still are missing for quite a number of names in the brainstorm (I too am at fault for this and will work on getting some whyâs in there) - so I encourage everyone to contribute to the âwhyâ section of the Notion brainstorm.
Since these protocols are being named as part of our immediate Gitcoin ecosystem - essentially, our âportfolio,â - attributes of each name would ideally align with our brand characteristics - hence why it was important to discuss these prior to naming:
- Knowledgeable not pretentious
- Relatable not casual
- Dynamic not brash
- Intentional not chaotic
- Generous not overbearing
- Open not reckless
- Optimistic not naive
- Delightful not silly
To @owockiâs point, I think itâs important to recognize we our brand name that is separate from our protocol names (unlike some of the aforementioned web3 brands, like Optimism and Juicebox, whose protocol and brand names are shared.)
Iâd encourage us to think about how these all fit together, how the protocols share our brand values and personality traits, but also embody their own, which were also shared as part of the brand positioning work:
Grants Protocol:
- Informative not overkill
- Flexible not confusing
- Effective not overpromising
- Intuitive not lazy
- Practical not boring
Project Protocol:
- Structured not rigid
- Functional not cold
- Adaptable not wishy washy
- Intuitive not lazy
- Practical not boring
I think a lot of the points raised here come down to brand and product positioning, so I encourage everyone to think about these names in that context.
Nowhere in the above do we specifically highlight technical or natural - but they are softly alluded to throughout the traits.
Additionally, visual elements will complement these names - the most recent work can be found in the Community Call takeover presentation here, which also brings to life these traits visually and gives a sense of how we might do the same with the protocols.
Lastly, I personally dont have the context around the naming process for Passport, but there does seem to be alignment around keeping the name. That said, without that context I donât know if I can justify holding ourselves to names that best fit. Plus, these protocols while modular can also stand alone. While we donât want Passport to feel like the one that doesnât belong, I donât know if we need to be beholden to the style.
Really enjoying these comments and looking forward to more feedback!