listingRecord
that contains the information of the Listing
they have curated. Curators can "remove" a Listing by burning their listingRecordsgetListings()
view call on a given Curator.sol proxy, or by using NFT indexers to gather data on all curationReciepts
that have been minted from a given curation contractListing
struct found in ICurator.sollistingRecord
NFTs minted to a curator's wallet. Allows for easy tracking via NFT indexers (like the ZORA APIListings
by burning their non-transferable listingRecords
CuratorSkeletonNFT.sol
Each curation contract is its own ERC721 collection. This allows for clear contract ownership, listings as individual tokens that are minted out of the contract, and composability with NFT indexersCurator.sol
Base implementaion for curation contracts generated from CuratorFactory.sol. Inherits from CuratorSkeletonNFT, and manages all of the curation related functionality CuratorFactory.sol
Gas-optimized factory contract allowing you to easily + for a low gas transaction to create your own curation contract. DefaultMetadataRenderer
A flexible metadata renderer architecture that allows for centralised and IPFS metadata group roots to be rendered.SVGMetadataRenderer
Onchain renderer for curation contracts that encodes information related to a specific listingyarn install
git submodule init && git submodule update
yarn build
All curation contracts are wholly owned by their creator and allow for extensibility with rendering and minting
All curation listing tokens minted to curators are non-transferable, but allow for the curator to burn the token so as to remove it from the onchain listing and their wallet
The metadata renderer abstraction allows these drops contracts to power a variety of onchain powered projects