First, we need to set up a one-time minting policy by minting an oracle token. This oracle token is essential as it holds the current state and index of the NFTs, acting as a reference for the minting sequence.

We need to provide 2 parameters to setup the oracle, the price of the NFT in lovelace and the collection name. The collection name is used when initializing MeshPlutusNFTContract which is used to derive the script CBOR. The price of the NFT in lovelace is used in setupOracle() function which will be added into the oracle token.

The setupOracle() function will return a transaction CBOR and aparamUtxo. The paramUtxowill be used in the minting transaction of the NFT, so it is important to store it. Here is an example of the paramUtxo:

The transaction CBOR can be signed and submitted using the following code:

This NFT minting script enables users to mint NFTs with an automatically incremented index, which increases by one for each newly minted NFT.

To facilitate this process, you must provide the paramUtxo that contains the output index and transaction hash of the NFT minting policy.

The mintPlutusNFT() function mints an NFT with asset metadata, which is a JSON object containing the NFT metadata. You can use the getOracleData() function to fetch the oracle data, which includes the current NFT index. This index will be helpful if you need to define the NFT name and its metadata. Here is an example of the how we can define the asset metadata:

The mintPlutusNFT() function will return a transaction object that can be signed and submitted using the following code:

Getting the oracle data is essential to fetch the current NFT index.

To facilitate this process, you must provide the paramUtxo that contains the output index and transaction hash of the NFT minting policy.

The getOracleData() function will return the current oracle data.