Minting
Minting is the creation of new tokens on a blockchain by calling the function of a smart contract that issues them — a stablecoin issuer minting a million tokens against a million dollars received, a fund tokenising shares, a protocol issuing its governance token. Burning is the reverse: tokens destroyed on redemption. For a regulated issuer the mint-and-burn cycle is how supply matches reserves, and the controls over who may mint, on what evidence, are what an auditor examines.
- Also known as
- Token minting, Mint and burn, Token issuance, Coin minting
- Used at
- stablecoin issuance and redemption, tokenised funds and securities, e-money tokens under MiCA, protocol and governance tokens, NFTs, and loyalty and in-game tokens
- Binding
- for stablecoins and e-money tokens, MiCA and the US GENIUS Act require that tokens be issued only against reserves received and redeemed at par, with reserve reporting and attestation; securities law governs the issuance of tokenised securities; the smart contract's access controls and the issuer's operational controls over minting are part of the authorisation
- Typical mechanics
- an authorised address (the issuer's, usually behind a multi-signature or hardware-key arrangement) calls the mint function with an amount and a recipient; the contract increases the total supply and credits the recipient; events are emitted and the supply is visible on-chain; burning reduces supply when tokens are redeemed; an "unlimited mint" flaw or a compromised key is the catastrophic failure
- Typical controls
- dual authorisation for every mint, reconciliation of on-chain supply to reserve balances daily, caps per transaction and per day, monitoring of the total supply against the reserve ledger, and a pause function
- Parties
- the issuer's treasury and operations teams, the key holders, the reserve custodian and auditor, the exchanges that request mints, the regulator, and the users whose tokens' value depends on supply matching reserves
How minting works in practice
An exchange wires $10 million to a stablecoin issuer's reserve account. The issuer's operations team confirms receipt against the bank statement; two authorised officers approve a mint of 10 million tokens to the exchange's wallet through a multi-signature transaction; the contract executes; total supply rises by 10 million; the daily reconciliation shows supply of 5.21 billion against reserves of $5.21 billion. A month later the exchange redeems 4 million: it sends tokens to the issuer's redemption address, the issuer burns them, and wires $4 million. The supply and the reserves move together, and the monthly attestation confirms they matched on every reporting date. A fund tokenisation works the same way with shares instead of dollars.
The failure modes are the reason for the controls. An unlimited-mint bug lets an attacker create tokens from nothing and sell them — several DeFi tokens have been drained this way. A compromised minting key does the same with the issuer's own contract. An operational failure — minting against a wire that bounces — leaves unbacked tokens in circulation. For a regulated issuer, minting is the point where its balance sheet meets its code, and the controls around it are what the regulator's authorisation examined; for an acquirer of an issuer or a tokenisation platform, the minting records, the key-management arrangements and the reconciliation history are the operational diligence.
Example
An e-money token issuer under MiCA processes 400 mints and 350 burns a month for authorised participants. Its controls: mints require a confirmed reserve receipt, two officers' approval on a hardware multi-signature, and an amount within the daily cap; supply is reconciled to reserves every hour and any variance above 0.01% triggers a pause; keys are held by four officers in two jurisdictions. In its second year an acquirer's diligence samples 60 mints, traces each to a reserve receipt and two approvals, reads the hourly reconciliation logs for twelve months (three variances, all resolved within an hour, all documented), and reviews the key ceremony records. The acquirer's report: the minting control environment is the reason the reserve attestations can be trusted.
Common mistakes
- A mint function callable by one key. - Minting before the reserve receipt is confirmed. - No reconciliation of supply to reserves on a schedule that would catch an error quickly. - Contracts with no cap and no pause. - Diligence that reads the attestation and not the minting records behind it.