TL;DR: Collectively mint a short video tutorial explaining how to deploy a Zora drop as a NounsDAO
As a contributor to Public Assembly, one of my primary goals is to provide context and education for tools like Nouns Builder. There are no existing tutorials that demonstrate ways to creatively onboard and engage Nouns Builder communities.
This proposal will trigger the creation of an open edition, made via Nouns protocol, deployed collectively by Public Assembly. This NFT will initially be deployed without the relevant metadata nor the appropriate sales configuration. Following the initial deployment, I’ll personally update the NFT’s metadata and sales configuration. Part of this tutorial will include the demonstration of this process, hence why I’m proposing things in this manner.
Details:
A 5-7 minute video, minted as an open edition, via Nouns protocol on behalf of Public Assembly
I (valcoholics.eth) will serve as the collection’s initial administrator. After the collection’s metadata and sales configuration have been updated, I’ll transfer administrative permissions to Public Assembly.
I proposed this onchain in an effort to create a public learning experience. I’d also like to set a precedent for the encouragement of curiosity and collective thinking via proposals.
Why don’t I make a request for funds from the Treasury:
At the moment, the ability to vote to mint educational assets alone is providing enormous and immediate value to Public Assembly.
this is an amazing breakdown thank u for this. imo this is def the level of detail we want on proposals, will be a great template for future ones. btw i think the treasury address is this instead 0x8330E78222619FD26A9FBCbEbAeb21339838bD30 (think the one u listed is the PA token address)
TL;DR: Collectively mint a short video tutorial explaining how to deploy a Zora drop as a NounsDAO
As a contributor to Public Assembly, one of my primary goals is to provide context and education for tools like Nouns Builder. There are no existing tutorials that demonstrate ways to creatively onboard and engage Nouns Builder communities.
This proposal will trigger the creation of an open edition, made via create.zora.co, deployed collectively by Public Assembly. This NFT will initially be deployed without the relevant metadata nor the appropriate sales configuration. Following the initial deployment, I’ll personally update the NFT’s metadata and sales configuration. Part of this tutorial will include the demonstration of this process, hence why I’m proposing things in this manner.
Details:
A 5-7 minute video, minted as an open edition, via create.zora.co on behalf of Public Assembly
I (valcoholics.eth) will serve as the collection’s initial administrator. After the collection’s metadata and sales configuration have been updated, I’ll transfer administrative permissions to Public Assembly.
I proposed this onchain in an effort to create a public learning experience. I’d also like to set a precedent for the encouragement of curiosity and collective thinking via proposals.
This is my annoying edit, feel like it clarifies some things and also just makes it more concise. I know I started to creep a lot into my own personal language, so feel free to do with this whatever you wish.
I initially used this outline from Gitcoin to see where I could be more detailed in my proposal descriptions, while also crossreferencing the nouns discourse for how people talk about video proposals
“made via create.zora.co” is not actually correct, not sure if it matters tho? the contract is actually getting deployed thru the nouns protocol as a proposal, but well be using the create front end to modify the metadata + salesConfig after the deploy goes thru
Correction, I was used to seeing the data in the event logs but I think the Zora version of nouns protocol does not display it like this, If you change the display output from hex code to text you are able to see the transcribe message
