Minting fundamentals
What actually happens when you mint?
Minting creates token units or an identified item under a contract’s rules. Understanding that record makes the rest of the process easier to evaluate.
The core idea
Minting creates a record under a set of rules
In a token contract, minting increases the recorded supply by creating new units or a new identified item. The contract decides who can mint, how much can be created, and which conditions must be met. The network processes the transaction and records the resulting state.
For a fungible token, minting typically adds units to an account’s balance and increases total supply. For an NFT, it typically assigns a new token identifier to an owner. Some designs create supply during deployment; others allow later minting. The exact behavior depends on the contract.
Read the action
Three actions that are easy to mix up
| Action | What changes | Question to ask |
|---|---|---|
| Deploy | A contract is published on a network. | Which rules and administrative powers does it contain? |
| Mint | New units or an identified item are created under the contract. | Who receives them, and what limits apply? |
| Transfer | An existing balance or item changes owner. | Which asset and recipient are involved? |
Where does the artwork live?
An NFT often points to metadata, which in turn points to an image, audio file, video, or other media. Some projects keep data directly on-chain. Others use web hosting or content-addressed storage. These choices affect cost, availability, and the ability to change a file.
A content identifier can help detect when referenced content changes. It does not make a file available forever without storage and distribution. Likewise, an ordinary web URL may continue to exist while its contents change. Ask both what a reference identifies and who keeps the underlying content accessible.
The Soundwaves / Photon study separates the source audio, preview image, metadata, and token record so that each responsibility is visible.
What the record can tell you
Fees, confirmation, and finality
Executing a transaction can require a network fee, separate from any mint price. The amount and fee model depend on the network and the work the transaction performs. A failed transaction may still consume a fee for computation already performed.
A submitted transaction is not necessarily confirmed, and confirmation is not identical to finality. Check its status on the intended network and understand that network’s settlement behavior. A test network is useful for learning, but its fees, congestion, and operating conditions do not predict a production deployment.
Choose what you want to create
Start with interchangeable units or follow the separate guide for individually identified works.