The information you provide to the generate method outlines what the signature can be used for.
The quantity, to, and metadata fields are required, while the rest are optional.
receiverAddress
The wallet address that can use this signature to mint tokens.
This is to prevent another wallet from intercepting the signature and using it to mint tokens for themselves.
Must be a string.
metadata
The metadata of the NFT to mint.
Must be an NFTMetadata struct
containing metadata that conforms to
the metadata standards.
The metadata is uploaded and pinned to IPFS before
the NFT(s) are minted.
quantity
The number of tokens this signature can be used to mint.
Must be an int.
GenerateFromTokenId
Generate a signature that can be used to mint additional supply of an existing NFT in the contract.
This is the same as generate but it allows you to specify the tokenId of the NFT you want to mint additional supply for, rather than
providing the metadata of a new NFT.
The typical pattern is the admin generates a signature, and the user uses it to mint the tokens, under the conditions specified in the signature.
Verify
Verify that a payload is correctly signed.
This allows you to provide a payload, and prove that it was valid and was generated
by a wallet with permission to generate signatures.
If a payload is not valid, the mint/mintBatch functions will fail,
but you can use this function to verify that the payload is valid before attempting to mint the tokens
if you want to show a more user-friendly error message.