HI there!! need help please with setting royalties for my very first NFT on manifold,a collection is only 1 unique token .
Would setting royalties on contract level guarantee royalties would be paid for each secondary sale or should I apply the royalty on token level instead?
BEst,
xyz.lB
Please beware of external links. Support will only be handled on this forum.
Manifold employees will have a Manifold Team badge next to their name.
Before asking the Community for assistance, please search for existing topics before posting.
If you’re running into issues, please provide the following in order for us to help:
What is your wallet address?
A summary of the issue
What are you trying to do?
A screenshot of the issue/error with the console visibile. Instructions here: Manifold Help Center
Contract-level royalty is the default that applies to every token in that contract.
Token-level royalty overrides the contract default for that specific token only.
They don’t stack. If you set both, only the token-level one applies to that token.
On the royalties guarantee:
The royalty is published by your contract, but it’s the marketplace processing the sale that decides whether to honor it. This can be determined by the marketplace itself, collectors etc. Most major marketplaces made creator royalties optional in 2023, so a sale elsewhere may pay less/nothing.
OK I didn’t get a reply , maybe auction is not working on Manifold?
In that case I’d consider auctioning on opensea , where they have an enforce royalty button inside opensea studio , except it only works for ERC721-C , not sure why my Manifold NFT is showing as ERC-721. Can i convert the smart contract on manifold from ERC721 to ERC721-C ??
To clarify: royalties only apply to secondary sales, meaning resales between collectors after you have sold the piece. They are not deducted from your own auction. If you auction the 1/1 on Manifold you receive the full sale amount, we take no platform fee, and no royalty is taken on a sale by the creator.
You can create an auction from the List option in the Create Menu.
Your contract is a standard ERC-721 that publishes your royalty on-chain. ERC-721C is a separate standard that adds a transfer whitelist to the contract itself, so the contract refuses a transfer unless it goes through an approved marketplace. That is what OpenSea’s enforce earnings button relies on, which is why it only appears for 721-C collections, and it cannot be added to a contract that was not built with it.
Thanks Lyndo for the explanation , so ERC721 contracts have optional royalties . Does Manifold have the ability to create ERC721-C contract ? In other words can i redeploy a new contract to have a manifold ERC721-C that would guarantee royalties for secondary sales?
No, Manifold doesn’t support ERC721-C. For a number of reasons, but primarily because most creators are not aware of the side-effects with the modified standard which include marketplace lock-in for their tokens. If you want to deploy a collection that is restricted to marketplaces such as OpenSea, we’d advise that you use the OpenSea Drops platform.
Thanks ediep! Opensea stopped allowing direct glb that’s why I used Manifold.
I just check the auction page , is the price here the equivalent of a reserve price?
The photo on that page and the arweave and rarible links are buggy , I’d rather wait to have them fixe both before listing . . NOt sure why my rarible profile photo disappeared .
Hi ediep! I forgot to mention this sentence "The contract is being indexed on Manifold, please come back later” is found at the bottom of the contract page.
I was planning to start the auction today , 1st day for NFT.NYC where my submission was accepted but somehow not visible .But I really need to fix the issues above.Hope I can still make it🙏
The message at the bottom of your contract page is about indexing on Foundation section, not about your contract on Manifold. Foundation no longer exists and we’ll be removing that section. Shouldn’t block anything.
On the price field, it depends which listing type you pick. A listing is a fixed price. An auction makes that field the starting bid, and the clock starts on the first bid. A private listing is a fixed price for one wallet.
Your files are showing on Opensea/Manifold links - The blank image on the Studio page is just missing a preview because of the asset type. The image and the 3D file are both stored permanently on Arweave and load correctly. The metadata preview link is hitting an issue on Arweave’s gateway side that we’ll resolve.
On Arweave - Arweave stores your files permanently and the file was uploaded correctly. A gateway is a separate service that serves them over a normal web link, and it’s that gateway that is having issues. Your image and 3D file both load fine, and the metadata itself is intact and confirmed on the network.
It’s on the gateway operator’s side and we’ve flagged it, but it may not clear today. It doesn’t affect your token or your listing, so you don’t need to wait for it to clear.
On the Metamask issue. MetaMask builds that explorer link from whichever network is selected in your wallet. You have BNB Chain selected, so it sends you to BscScan with your Ethereum contract address pasted in. Nothing exists at that address on BNB Chain, which is why you see zero holders and zero supply.
Switch your wallet’s network to Ethereum, or search the contract on etherscan.io directly.
OK it was set to all networks , I deleted the nft from metamask ,tried to refresh metadata inside metamask after disconnecting all Dapp connections ,locking metamask and deleting all history /data from browser But the NFT didn’t show up in my wallet till I imported it manually is that normal? Shall I go ahead with listing ?
why do u think the rarible page is looking like this?? is there anything i can do on my part to fix it before I do the listing on Manifold?
It’s possible that Rarible is running to same Arweave issue - You can reach out to their support team if it’s something you want resolved before listing the the piece for auction.
Hi lyndo ! I am still waiting for Rarible to get baack to me . I would really appreciate if you do a manual media refresh to hopefully fix the page cannot be found arweave error ?
btw i am surprised the animation button on the official manifold page downloads automatically the glb without even buying it .
Like mentioned above - Arweave stores your files permanently and the file was uploaded correctly.
The Gateway is a separate service that serves them over a normal web link, and it’s that gateway that is having issues. Your image and 3D file both load fine, and the metadata itself is intact and confirmed on the network.
A manual refresh won’t resolve the issue with the Gateway. We’ll provide an update here as soon as we have one.
Please beware of external links. Support will only be handled on this forum.
