## **Mint and Burn Assets**

Minting and burning assets is a common operation in blockchain applications. In the Cardano ecosystem, minting and burning are achieved through Native Scripts and Plutus Scripts.

In the code snippet, you will find `txBuilder`, which is an instance of `MeshTxBuilder`, a powerful low-level APIs that allows you to build transactions. Learn how to initialize [MeshTxBuilder](https://meshjs.dev/apis/txbuilder/basics#initializeTxbuilder).

Mint and Burn Assets

## **Minting with One Signature**

In this section, we will see how to mint native assets with a `MeshTxBuilder`. For minting assets with smart contract, visit [``MeshTxBuilder`` - Smart Contract - Minting Assets with Smart Contract.](https://meshjs.dev/apis/txbuilder/smart-contract#plutusminting)

Firstly, we need to define the `forgingScript` with `ForgeScript`. We use the first wallet address as the "minting address" (you can use other addresses).

`const changeAddress = await wallet.getChangeAddress();
const forgingScript = ForgeScript.withOneSignature(changeAddress);`

Then, we define the metadata.


`const demoAssetMetadata = {
  name: "Mesh Token",
  image: "ipfs://QmRzicpReutwCkM6aotuKjErFCUD213DpwPq6ByuzMJaua",
  mediaType: "image/jpg",
  description: "This NFT was minted by Mesh (https://meshjs.dev/).",
};
const policyId = resolveScriptHash(forgingScript);
const tokenName = "MeshToken";
const tokenNameHex = stringToHex(tokenName);
const metadata = { [policyId]: { [tokenName]: { ...demoAssetMetadata } } };`

Finally, we create a transaction and mint the asset with the lower level APIs.


`const unsignedTx = await txBuilder
  .txIn(utxo.input.txHash, utxo.input.outputIndex)
  .mint("1", policyId, tokenName)
  .mintingScript(forgingScript)
  .changeAddress(changeAddress)
  .complete();`



Minting with One Signature

## **Minting Multiple Assets**

Minting multiple assets with a single transaction is a common operation in blockchain applications. Like minting single assets, you can mint multiple assets by calling `mint`() and `mintingScript` multiple times.

`const metadata = {};
metadata[policyId] = {};
for (let i = 1; i < 3; i++) {
  const tokenName = `MeshToken${i}`;
  const tokenNameHex = stringToHex(tokenName);
  metadata[policyId][tokenName] = {
    ...demoAssetMetadata,
    name: tokenName,
  };
  txBuilder.mint("1", policyId, tokenNameHex);
  txBuilder.mintingScript(forgingScript);
}`

You appending the metadata into one object and pass it to metadataValue() method.

`txBuilder
  .metadataValue(721, metadata)
  .changeAddress(changeAddress)
  .selectUtxosFrom(utxos);

const unsignedTx = await txBuilder.complete();
const signedTx = await wallet.signTx(unsignedTx);
const txHash = await wallet.submitTx(signedTx);`


Minting Multiple Assets

## **Burning assets**

Like minting assets, we need to define the forgingScript with ForgeScript. We use the first wallet address as the "minting address". Note that, assets can only be burned by its minting address.

`const usedAddress = await wallet.getUsedAddresses();
const address = usedAddress[0];
const forgingScript = ForgeScript.withOneSignature(address);`

Then, we resolve the policy ID and hex of token name, setting set 

txBuilder.mint("-1", policyId, tokenNameHex)

`const policyId = resolveScriptHash(forgingScript);
const tokenNameHex = stringToHex("MeshToken");`


Finally, we create a transaction and burn the asset with the lower level APIs.

`const unsignedTx = await txBuilder
  .mint("-1", policyId, tokenNameHex)
  .mintingScript(forgingScript)
  .changeAddress(changeAddress)
  .selectUtxosFrom(utxos)
  `.complete();``




Burning assets

## **Minting Assets with Native Script**

The above minting and burning one signature are indeed the mint and burn with native script examples. Here we would explain the logic you need to know for native script minting.

With `MeshTxBuilder`, you just need .`mint`() and provide script to mint or burn native script tokens:

`txBuilder
  .mint("1", policyId, tokenNameHex)
  .mintingScript(forgingScript)`

On top on these 2 core logics, you can attach metadata if needed with .metadataValue(), and construct the transaction as needed.

Minting Assets with Native Script

## **Minting Assets with Plutus Script**

Minting Plutus tokens with MeshTxBuilder starts with anyone of the below script version indicators:

`.mintPlutusScriptV1()
.mintPlutusScriptV2()
.mintPlutusScriptV3()`

Followed by specifying the minting information:

`.mint(quantity: string, policy: string, name: string)`

Similar to unlocking assets, minting or burning Plutus tokens require providing redeemer and scripts. However, no datum information is needed in minting or burning.

**Script of the token**

The actual script can be either provided by transaction builder or referenced from an UTxO onchain.

(i) Reference script

`.mintTxInReference(txHash: string, txIndex: number)`

(ii) Supplying script

`.mintingScript(scriptCbor: string)`

**Redeemer of the mint**

Redeemer can be provided in different `data types`. If your MeshTxBuilder does not include an `evaluator` instance, you can also provide your budget for the unlock with this redeemer endpoint

`.mintRedeemerValue(redeemer: Data | object | string, type: "Mesh" | "CBOR" | "JSON", exUnits?: Budget)`



Minting Assets with Plutus Script

## **Minting Assets with CIP-68 Metadata standard**

Minting CIP-68 tokens with MeshTxBuilder means 2 consecutive sets of minting APIs. The first is to mint the 100 token, and the second is the mint the 222 tokens:

`txBuilder
  .mintPlutusScriptV2()
  .mint("1", policyId, CIP68_100(tokenNameHex))
  .mintingScript(scriptCode)
  .mintRedeemerValue(mConStr0([]))
  .mintPlutusScriptV2()
  .mint("1", policyId, CIP68_222(tokenNameHex))
  .mintingScript(scriptCode)
  .mintRedeemerValue(mConStr0([]))`

A side note, Mesh also provides the utility function of `CIP68_100(tokenNameHex: string)` and`CIP68_222(tokenNameHex: string)` to help easily construct the token names as needed. So you dont have to memorize the prefix bytes to correctly mint the CIP68-compliant tokens.

Minting Assets with CIP-68 Metadata standard

## **Minting Royalty Token**

Royalty tokens is a special type of token that allows the creator to collect a royalty fee, this proposed standard will allow for uniform royalties' distributions across the secondary market space. Read [CIP-27](https://cips.cardano.org/cips/cip27/) for more information.

The implementation of royalty tokens is very simple, minting a token with **777** label, with "rate" and "addr" in the metadata.

Here is the example of the metadata:


`const assetMetadata = {
  rate: '0.2',
  addr: 'addr_test1vpvx0sacufuypa2k4sngk7q40zc5c4npl337uusdh64kv0c7e4cxr'
};`

Minting Royalty Token

Minting and burning assets with Native Script and Plutus Script



Mint and Burn Assets

Course Details

Level

Ratings

Modules

Lessons

Holder $WORK Price

Contact Us

Documentation

Navigation