Main Topics Discussed
- Filip's emotional response to NPM and favor of alternative names.
- Introduction to the Bannyverse deploy scripts.
- Highlight of the complexity and components involved in the Bannyverse deploy script.
- The uniqueness of Bannyverse project and its multi-chain deployment.
- Unit tests for Juicebox V4 by NoWonder.
- Nouns proposal update by Matthew.
- General comments on governance and proposals.
Filip's Emotional Response to NPM and Favor of Alternative Names
The meeting kicked off with a light-hearted discussion on Filip's aversion to working with NPM packages and a preference for alternative names like "Twine" or "Hemplick" over "yarn."
Introduction to the Bannyverse Deploy Scripts
Jango introduced the deploy script for the Bannyverse project, highlighting its significance in tying together various components – NFTs, 721 hooks, buyback delegates, and more under a collective called the Bannyverse. Jango then proceeded to share his screen to walk the participants through the Banny contract and deploy script details.
Complexity and Components in the Bannyverse Deploy Script
The deploy scripts are comprehensive, set to incorporate elements like the 721 token URI resolver, multiple stages of configuration, and integration of numerous instantiated contracts like Croptop and Revnets. Jango detailed configuring different aspects including terminals, Revnet stages, buyback hooks, and NFT tiers, emphasizing the script’s extensive nature and systematic approach to launching the Bannyverse project.
Uniqueness of Bannyverse Project and its Multichain Deployment
Participants noted the Bannyverse project's uniqueness, particularly in its attention to detail and the ability to swap outfits on NFTs, highlighting the project's forthcoming deployment across multiple chains. Jango expressed excitement for the project’s potential to showcase the capabilities of Juicebox through Bannyverse's complex but tractable deployment process.
Unit Tests for Juicebox V4 by NoWonder
NoWonder shared updates on working on unit tests for Juicebox V4. Jango emphasized the importance of this foundational and somewhat thankless background work in enabling higher levels of abstraction within the project. The conversation highlighted the protocols and support structures necessary for maintaining project integrity.
Nouns Proposal Update by Matthew
Matthew presented updates on a Nouns proposal intended to support a project directly from the Nouns DAO treasury. However, due to a malformed execution resulting from a bug in the governance front end, the proposal has to be submitted and voted on again. Matthew remains optimistic about the eventual support and broader implications for DAO collaborations.
General Comments on Governance and Proposals
The discussion touched on experiences with on-chain governance, highlighting challenges and learnings that could benefit both current and future proposals. A focus on leveraging major DAO treasuries and employing strategic approaches to secure funding was emphasized as a promising avenue for project support.
In summary, the meeting featured an engaging mix of discussions around the intricacies of deploying the Bannyverse project, the foundational work of unit testing for ongoing development, experiences with on-chain governance, and strategic outreach to DAO treasuries for funding. The participants showed a combination of technical depth, project enthusiasm, and strategic foresight in approaching the challenges and opportunities presented.