Maybe you’re looking for more UI and UX flexibility than the embedded marketplace affords. We offer an SDK that allows you to create a marketplace using OpenSea’s infrastructure and building blocks, but with your layouts and design layered over the top. It’ll take more than three minutes, but the results will be well worth it.
Once you got a seaport initialized, allowing your sellers to create listings is straightforward:
Peruse our full documentation on . Skim our example app, the , for reference. And get inspired about the power of our SDK on . Their entire marketplace is built with our tooling! You can read about Mythereum’s development experience .
And if you get hung up at any point, drop by our server and let us know about it. We almost always respond within a few hours and usually, it’s within a few minutes. Little in this world brings us more satisfaction than learning about new projects using our tools. Even if you’re just considering it as a possibility, we’d be happy to chat with you about how we can help.
White-label
OpenSea also offers a white-label solution. If you own AAA IP that you think would match up well with the ecosystem, if you’ve got a successful game and you’re looking for a marketplace on a custom domain, or if you’re running your own and looking to spin up an instance of OpenSea on it to enable smooth, sophisticated exchange, send us an email at contact@opensea.io. We’d love to talk about the costs and benefits of an OpenSea white-label marketplace.
If a readymade, customizable marketplace with your brand on it sounds appealing, but your project is just getting started, then follow us on or Medium for more . We’re developing a quick, cheap, self-serve marketplace creator that will bring some of the power and convenience of Stripe to the world of crypto.
Why We’re Excited
We feel confident in saying that OpenSea provides a valuable service to the space: we build a crisp, safe, open marketplace so that dapp developers can invest their time in creating mesmerizing, addictive, innovative projects. For the first time, developers can deploy a digital asset and instantaneously give users a liquid marketplace for their items. We like to think that we add a little extra flow to the rising tide that’s lifting the NFT ship.
What else would you like to see in a marketplace? What other needs do you think we could meet? What tools would help you build a better experience for your users? Let us know on , message us on , or at us. Developer input is priceless and we’re always happy to chat!
To stay up to date on all things OpenSea, or follow us on Medium.
Appendix A: Handling Common Issues
Sometimes, issues crop up that can’t be solved by reading or . And sometimes . Anyway, here’s some information on diagnosing and fixing the most common issues, just in case:
1. I can’t access the storefront editor
By default, the storefront editor page () is accessible to the contract’s . If your contract doesn’t implement Ownable, or if it does but the owner address is not accessible (maybe it’s living exclusively on a server), or if it’s just not working, we can fix that manually. Send an email to support@opensea.io introducing yourself, providing the contract address, and providing the address that you’d like authorized to edit the storefront. We’ll confirm your ownership, then make the authorization.
2. My contract’s not accessible in the sidebar or the search bar
That’s the default state of all new contracts on OpenSea. We employ a concept that we call whitelisting. When a dapp gets whitelisted, it appears in the sidebar and becomes searchable in the main search bar.
Whitelisting is discretionary, but we use a few key metrics to inform the decision: the project’s community engagement on discord and , historical volume of sales on OpenSea, the project’s reach on twitter and other social media, the novelty of the tech, and the pace of development, among others. If you put together a brief report on your project, focusing on the metrics enumerated above, and send it to contact@opensea.io we’d be happy to review it.
3. I re-deployed my contract and now the names are all messed up
When you add the new contract with the same name as your previous contract, it will automatically have a new storefront with “V2” after the name (or “V3”, “V4”, etc.).
To update your smart contract, go to the storefront editor for each contract, rename the old contract to “ContractNameOld,” and rename the new contract to “ContractName.”
After you’ve updated your contract, you might want to get rid of the old one. We don’t have an interface for deleting old smart contracts from OpenSea, so you’ll need to contact us on . We’ll be sure to get it done as soon as possible!
4. My metadata isn’t displaying properly
We’ve noticed that this issue usually owes its origin to a few different causes:
The metadata isn’t available through tokenURI, but we have an API that you could hit.
Great! That works for us. Send an email to support@opensea.io with your contract address and your base API URL. We’ll need to be able to feed it a ID and get back a JSON formatted according to .
The metadata is available through tokenURI, but doesn’t appear at all on OpenSea.
This is can get a little trickier. If the links returned by tokenURI don’t 403 and the JSONs that they point to pass muster on a JSON validator, then ask the following questions: Is my contract compliant with ERC 721, including its ? Does my ’s image link work? Am I using exclusively display_type options? Do my attributes with a display_type of “number” have numbers for their values and not strings?
If you can answer “yes” to all of those questions and the metadata still won’t turn up, please contact us on , because we’ve got a true mystery on our hands. We love solving mysteries.
The metadata is served through IPFS and appears unreliably.
We find that sometimes IPFS links can be a little finicky. If the metadata shows up for some of your contract’s assets, but not all of them, please contact us on and we’ll run a remedial script.
Appendix B, The Speed Run: Setting up an OpenSea Storefront in Three Minutes or Less
Do you already have an ERC 721 compliant contract? Have you already minted some ? Do you have that’s accessible through your tokenURI function? Does your contract implement Ownable? If you can answer all those questions affirmatively, then you can get set up on OpenSea in the time it takes to make a bag of popcorn. Set the power to “high,” listen for 1–2 seconds between pops, and follow these steps:
1. Find one of your tokens on OpenSea
First, go to . Then append /YOUR_CONTRACT_ADDRESS/LOWEST_TOKEN_ID onto the URL. This will take you to the asset’s detail page and if OpenSea was previously unaware of your contract, it’ll have the side effect of adding it to our system.
2. Click the grey contract name below the token’s name
This will take you to the contract’s main page. Eventually, you’ll be able to see all your here. But don’t get distracted! We’ve got a deadline, after all.
3. Access the storefront editor
To access the storefront editor, Click the “••• More” button in the top right of the screen, then select “Edit Storefront.” This option is only available by default to the of the contract. If you don’t see it, just ping us on or send an email to support@opensea.io with your contract address and the address you’d like to authorize as an editor.
4. Set a developer fee
The storefront editor page is full of enticing options, but we’re trying to set records here, so stay focused! Skip past all the other fields, and go straight to “Add your seller fee (%).” Most developers that choose to set a fee go with 2.5%, but you can choose whatever you think will be best for your project.
Then, paste your ETH address into the field labeled “Your payout address.” Finally, click “Save” and record your time. That’s it! Congratulations, you’ve set up a storefront on OpenSea.
I made it through these steps at a leisurely pace in just over two minutes on an ornery local instance. your time at us if you can beat my record, then check out the “OpenSea Storefront” section above to finish your storefront setup.
Published at Wed, 27 Mar 2019 21:06:17 +0000
