Just finished a new zora minting module + metadata renderer combo for the PA Onchain repo. here is the github repo, and here is a figma that breaks down the architecture + contract interactions required to set this up (included an example)
tldr : custom minting module + metadata renderer that are tied together and let you set the tokenURI of a token upon mint, without needing to define collection wide token metadata upon contract deployment (what zora currently does for editions + drops)
potential use cases : scrapbooking, archiving, instances where you want to collect user generated data from a front end and mint it, creator owned “1 of 1 album” minting contract in similar vein of the old zora minting contract, etc
I very much like this. I get really tripped up on basic stuff like deploying, passing the right args etc. so even just having examples of deploy scripts is nice.
To go through the setupDropsContract step (from onchain readme).
Deploy Zora Drop Contract (only available on Mainnet/Goerli atm), and pass in address of TokenUriMetadataRenderer for Metadata Renderer, and abi.encoded value of contractURI + wildcardAddress for Renderer Init
See screenshot below for how to use abi.hashex.org to create encoded init value for Zora Drop init:
What would some of the user generated data be, and other instances where this combo can be used? Not fully grasping the situational use when you say scrapbooking, archiving and etc. Wondering if you can provide a situational metaphor/explanation