You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've been reading your work. I'm developing a similar marketplace with auction, and I have all the code in a single contract. I'm looking for a way to split it, but I don't know which is the right way.
I have seen that in your implementation you use the ERC721URIStorage contract... why did you use this approach?
And I would ask you, what do you think is the approach that I should use?
in principle I tried to implement inheritance of contracts, I understand how to separate them, but I don't know how to link them in migrations.
Best regards
The text was updated successfully, but these errors were encountered:
We have implemented ERC721URIStorage because it comes with a map (tokenID -> tokenURI) to store URL of NFT metadata (name, description, image) which we use in our frontend. Essentially you can use ERC721 contract and implement this map yourself if you need to store this URL on the blockchain.
If your NFT token in auction and market place are unrelated you can separate them and deploy both the contracts separately. Now you have two contract address to work with - one for auction place and one for market place.
Hi, I've been reading your work. I'm developing a similar marketplace with auction, and I have all the code in a single contract. I'm looking for a way to split it, but I don't know which is the right way.
I have seen that in your implementation you use the ERC721URIStorage contract... why did you use this approach?
And I would ask you, what do you think is the approach that I should use?
in principle I tried to implement inheritance of contracts, I understand how to separate them, but I don't know how to link them in migrations.
Best regards
The text was updated successfully, but these errors were encountered: