Follow the instructions and samples from this guide to get you started minting NFTs.


# Glossary Definitions

Asset – is a structure that represents a Cardano native token. The data structure is based on the
Cardano metadata standards, with extended properties. These extended properties are used exclusively by Bakrypt and indicate minting methodologies within the API. The Assets API creates assets.

Attachment - You can upload files and create attachments through the Files API. These files are
uploaded into a CDN and later pinned into IPFS. This structure holds the IPFS information required
when making assets.

Collection – is a foreign key to link different assets under the same policy, and it's created in a
single request as a "list of assets" using the Assets API. Each Transaction has a limit for the metadata size, which is 8 kb, set by the network. The Collection will be split into chunks of sub-collections if the total size of the collection metadata is more than 8 kb. The sub-collections are
processed in separate Transactions once the full payment for the Collection is received. The system automatically completes this process, and only one payment is required from the payor.

Deposit address – is a payment address generated by Bakrypt to process the Transaction. The
payment address is the wallet receiving the ADA tokens from the payor. Bakrypt will use the funds
in this wallet to generate and register Cardano Native Tokens. The system will return any change
to the issuer's address and any tokens found in the Transaction or UTXO.
Consider this sensitive data information and should only be shown to the legitimate owner of
the minted assets

Issuer Address – is set as the payor of the Transaction and is chosen from the first UTXO found in
the list of UTXOs from the deposit address. The first wallet that transfers funds to
the deposit address will retrieve all tokens and the change from the deposit. This value can be set when creating the Asset if the user has enough permissions.

Transaction - is a data structure that holds the metadata and information related to the minting
process, like the deposit address, minting costs, convenience fees, the issuer's wallet address, and
minting status. Each mint request will generate a Transaction, and therefore it will be linked to an
Asset or a Collection of assets. All transactions can be retrieved and managed using the
Transactions API. The API also provides nested endpoints used to retry or refund the
Transaction manually if necessary. Non-Confirmed Transactions will be automatically refunded and
canceled after 24 hours of activity.

Auto Processing - Assets can be minted on-demand or automatically. This attribute is ON by
default and ensures that all requests return an estimated cost and deposit address to process the
Transaction, otherwise, the transaction will be set to "authorized" for minting.