How can I get OpenSea to lazy mint with a custom contract I built?
In other words, how do I get OpenSea to communicate with my custom contract during the sale of a lazy minted token?
I don’t want the lazy minted token to show up on the OpenSea smart contract. I want it to live on my custom contract after purchase.
Related
I'm working on a project to create an NFTs marketplace.
When an NFT is listed, the owner can transfer that NFT to another wallet and the listing would still be there.
This raises a few problems:
When the NFT is returned to the original, the listing is up again and bots can snipe the NFT if the listing is below the floor price.
Buyers can still call the function but the transaction will be reverted, buyers would receive no NFT and lose the gas fee.
Apparently, Opensea is fighting this problem using front-end solution. CMIIW.
You can see more below:
https://opensea.io/blog/safety-security/important-updates-for-listing-and-delisting-your-nfts/
https://support.opensea.io/hc/en-us/articles/4415742560403-What-is-an-inactive-listing-
Are there any other ways for the smart contracts to recognize the NFT being transferred out of the wallet and make the listing invalid, only using smart contracts?
How can I list Rarible Lazy Minted off-chain tokens on OpenSea?
I am Lazy Minting tokens on Rarible that go to a custom smart contract during the sale. Before the sale, the tokens are stored off-chain but still listed on Rarible. How do I get these off-chain tokens to also be listed on OpenSea?
In other words, I need to list off-chain lazy minted tokens on Rarible and OpenSea that mint to a custom smart contract at sale.
I'm trying to build an NFT marketplace. So I wanted to create an ERC1155 smart contract to allow content creators to put their art into the smart contract. I'm using OpenZeppelins wizard as a base but I found some weirdness on the mint function. It's allowing only the owner of the contract to mint:
It's made me suspicious about my actions. Should I disallow users to mint to create items on my contract?
I can't speak for the wizard authors why they decided on some specific approach.
However it's an established practice that when an artist or any other authorized person publishes an NFT collection, they don't want other people to contribute to this specific collection and change the overall meaning of it. For example, if you have a collection of NFTs representing pictures of dogs, you might not want other people to create NFTs representing pictures of cats in the same collection. Or any other unrelated pictures for that matter.
If you want to allow minting tokens in the collection by anyone, you can remove the onlyOwner modifier from the mint functions As well as the Ownable extension of MyTokens contract and its import, assuming you don't use the Ownable features elsewhere in your contract.
I actually need a very simple smart contract using the following functions "transferfrom" and "approve".
I just need a smart contract that will be able to request approval to spend a token ( example -- bake ) from a wallet if the user calls the "approve" function.
It will also be able to withdraw the particular token from the user's wallet to the "address to" set by the contract's onwer, if the onwer calls the "transferfrom" function.
There's a design limitation of the ERC20 standard that disallows approval through a contract in between.
The user always needs to invoke the approve() function on the token contract directly - not through your contract.
I just start to learn solidity and I've finished a couple courses and I want some help to create my first working smart contract.
The smart contract I want to build will buy and sell tokens on the pancakeswap platform from a smart contract; it like my smart contract will start interacting with a pancakeswap contract to execute some trades, doing the same stuff as I'm using their website.
Any help will be appreciated
I have tried to add the interfaces I need to start the interaction between my contract and pancakeswap router contract to use the function