When we mint your NFT, it is minted against your own personal private key, which we generate when a provider creates a wallet for you. After transfering your key to your own ownership (which we highly recommend you do), you can log into OpenSea using that private key to confirm ownership over the NFT that we minted.
Yes! While we highlight the OpenSea integration throughout these docs, any marketplace that supports ERC-1155s on Polygon and the Ethereum Mainnet will work with a WrapDapp NFT.
Polygon is a layer 2 network which prioritizes speed and volume of transactions over decentralization. While Polygon is decentralized, it's mechanisms for settling transactions do not require the same level of "agreement" by individual nodes in the network as is required in a proof of work network like Ethereum's Mainnet. The result is far cheaper and quicker minting, as well as cheaper gas fees in general.
Some will argue that NFTs not on Ethereum's mainnet don't hold their value as well. Furthermore, Polygon isn't support by all marketplaces currently.
If you can afford minting on the Ethereum mainnet, we recommend this over Polygon.
The short answer is "it depends".
When you minted your NFT, if you chose to send your artwork and metadata files to IPFS, then your NFT is considered final and can no longer be updated.
If you chose to mint the NFT while keeping the artwork and metadata files on WrapDapp's local servers, then you can still make changes.
We recommend minting against WrapDapp's server until you are 100% satified with the state of your NFT.
Much like Ethereum's blockchain is immutible, so it is with IPFS as well. Therefore if you choose to send your NFT's artwork and metadata file to IPFS instead of using WrapDapp's local servers, the data associated with the NFT cannot be changed ever again.
If you choose not to send to IPFS, which we recommend doing until you are 100% satisfied with the NFT's contents, you can still make changes to the art and metadata file.
Essentially, using IPFS when minting creates finality for your song's NFT.
WrapDapp mints using a standard ERC-1155 contract on both Polygon and Ethereum's Mainnet.
Mumbai: 0xb36292f2fd4933f9676f15979bf951a080ac5526
Polygon Mainnet: Coming soon
Goerli: 0x73405A2d1AA3ddCEcc09d40Ae80f1E8511ce7CD1
Mainnet: Coming soon
If you recently sent your NFT data to IPFS, please give it some time. If you continue to experience slow response times after 24 hours, please contact us for additional support.
The process of batch minting NFTs involves first creating the songs within the
WrapDapp platform, either via TSV import or individually. Once you have created
your songs and have the song IDs, you can make a request to the POST/user/{userId}/nft/batch endpoint
to initiate the minting process.
Note that, as is evidenced by the batch minting endpoint, you can only mint in batches to a single wallet (ie user ID) for any given batch request.
Please see the input model from the API documentation for information on how to create the API request.