Who: @nicholas - nnnicholas.eth
Proposal date:
September 20, 2021
(prior version proposed on Discord September 14, 2021)
IPFS
https://gateway.pinata.cloud/ipfs/QmeWBRvq4ukANJfP4we1bEQiXFrvL7xQSJpFJCCF7948Me
What responsibilities have you assumed on the community’s behalf thus far?
In the ~3 weeks since I began working with Juicebox, I've contributed in a number of ways:
-
I've dived into governance, getting to know the team and how the protocol works and contributing to governance planning, such as my contributions to the BANNY governance voting incentivisation scheme and testing Coordinape.
-
I'm designing and leading the NFTMKT v1 implementation with Jango's help, and I am planning NFTMKT v2 and beyond (see https://www.notion.so/juiceboxdao/Specification-bf833fd203154476b998345514c668c9)
-
I'm using my network to help recruit for roles we need filled, such as the recent #analytics recruiting push. I've also used my network to attempt to staff up CanuDAO, in an effort to both strengthen that team and help their bot writing
-
I am recording and documenting meetings where possible, such as the #Analytics Graph Deep Dive and our call with Dragonfly Capital. See:
-
I'm contributing to the Notion, Discord structure, and Github Docs, for example:
Gitbook Welcome page and Contract Addresses
-
I'm proactively doing research into JBX token holders to learn who are our biggest contributors. I have begun making connections with these large stakeholders, such as Dragonfly Capital, who made the single largest transaction to JBX treasury. I used Nansen to find trace their wallet to the VC firm, then organized a meeting with Tom Schmidt, General Partner. This meeting was attended by our other largest contributors Dexer, Yoni, and TerraBellus, who each spoke up during the call — an interesting and unexpected outcome.
-
Through private and semi-private conversations, I've built bridges with other DAO and teams building influential DAO tools. I'm gently encouraging these folks to consider permissionless composable integrations with Juice. I've already spoken with leaders at Mirror and PartyDAO, Gitcoin, and SZNS.
-
I'm deeply embedded in Shark, workshopping NFTMKT features with Sharks developing derivatives projects.
-
Perhaps most importantly, Juicebox is one of the very few projects that I have and will continue to associate myself with publicly. I am comfortable attaching my reputation to this project on Twitter and when encouraging new people to become juicers, because i love what Juicebox is doing.
What responsibilities do you plan on assuming on the community’s behalf going forward?
- I will complete NFTMKT v1 and continue subsequent iteration on that project.
- I am taking on a larger role in governance design and communications projects.
- I'm looking forward to spreading the word about Juicebox on Twitter, Spaces, blogs, podcasts, and more when we are ready for that kind of exposure. I have several Spaces and blog posts in mind already, including a series on daotools.
- I think I'm at my best when solving needs I identify as we go, so I expect a large part of my contribution will be addressing specific needs that arise and become apparent over time.
Proposed Reserved JBX allocation
35% Reserved JBX:
- JBX DAO: 30%
- Jango: 24%
- Peri: 24%
- Exekias: 7%
- Nicholas: 7%
- CanuDAO: 4%
- WAGMI: 4%
What else do you foresee needing from the community for you to best manage this responsibility.
I foresee needing dev support from the dev team. Initially, I anticipate requiring help from Jango, Peri, and Exekias to take the NFTMKT from semi-functional prototype to production code. The two main parts of this are the solidity implementation and testing, and the JS Library that will enable projects to create front-ends easily. I would also appreciate help staying on track with that project over time.
I think I can learn a lot from Jango about piercing indecision navigating the dao fog of war despite uncertainty and lack of prior art on many matters.
I would appreciate hearing more from Unicornio on governance as we navigate governance formalization and org growth.
I can achieve the most collaborating with Zeugh to implement fast process iteration and improvement in the Discord. The same applies for contributions to 9birdy9's and Zeugh's efforts on governance process.
What does success look like for someone taking on these responsibilities?
- Continue to hone in on focus areas: governance and logistical process design, targeted recruiting and communications efforts, and improving the protocol and product experience.
- Continue to take on various tasks that deliver value to the DAO and enable teammates to move faster and build better software and relationships.
- Personal goal: Grow to be a confident Web3 developer through the NFTMKT project so that I can contribute to the dev team as a full fledged builder. Explore the outer wilds and bring home what I have seen.
Under what criteria might it make sense for the community to reassess this reserved token allocation to you?
If I fail to deliver the NFTMKT in a timely manner and/or if my various contributions on other fronts decelerates to the point that other contributors do not feel I am adding the same level of value as when this proposal was adopted, it will make sense to reassess and decrease my reserved tokenallocation.
If I ship the NFTMKT and/or continue to contribute in significant positive ways, it will make sense to consider increasing my reserved token allocation.