@itinance
Yeah the standard convention is to have a separate smart contract for each collection. That's what I've been noticing across all marketplaces.
Thank you for your answer I'm going to implement it as soon as I get home and see if this helps me as well.
Update: the latest standard is here.
You have to implement the contractURI method that returns a URI that OpenSea can use to fetch contract metadata.
The expected JSON looks like this:
{
"name": "OpenSea Creatures",
"description": "OpenSea Creatures are adorable aquatic beings primarily for demonstrating what can be done using the OpenSea platform. Adopt one today to try out all the OpenSea buying, selling, and bidding feature set.",
"image": "/image.png",
"external_link": "",
"seller_fee_basis_points": 100, # Indicates a 1% seller fee.
"fee_recipient": "0xA97F337c39cccE66adfeCB2BF99C1DdC54C2D721" # Where seller fees will be paid to.
}