This is the first transaction you need to setup the contract.

This transaction mints the one-time minting policy (a NFT) for the contract.

It will be attached with the datum which serves as the single source of truth for the contract oracle.

Note: You must save the paramUtxo for future transactions.

This transaction send the NFT to a oracle contract locking the datum, which serves as the single source of truth for the contract oracle with data integrity.

This is the second transaction you need to setup the contract.

Note: You must provide the paramUtxo from the mintOneTimeMintingPolicy transaction.

This are the next transactions you need to setup the contract. You need to run once for each script, and you would likely have to run one after the previous one is confirmed.

This transaction sends the reference scripts to the blockchain for later transactions, boosting efficiency and avoid exceeding 16kb of transaction size limits enforced by protocol parameter.

Note: You must provide the paramUtxo from the mintOneTimeMintingPolicy transaction.

Note: You must save txHash (after signed and submitted) forContentRegistry, ContentRefToken, OwnershipRegistry,OwnershipRefToken transactions for future transactions.

This is the next transaction you need to setup the contract after completing all the `sendRefScriptOnchain` transactions.

This transaction creates one content registry. Each registry should comes in pair with one ownership registry and each pair of registry serves around 50 records of content ownership. The application can be scaled indefinitely according to the number of parallelization needed and volumes of content expected to be managed.

Note: You must provide the paramUtxo from the mintOneTimeMintingPolicy transaction.

Note: You must provide the txHash forContentRegistry, ContentRefToken, OwnershipRegistry,OwnershipRefToken transactions.

This is the last transaction you need to setup the contract after completing all the `sendRefScriptOnchain` transactions.

This transaction creates one content registry. Each registry should comes in pair with one content registry and each pair of registry serves around 50 records of content ownership. The application can be scaled indefinitely according to the number of parallelization needed and volumes of content expected to be managed.

Note: You must provide the paramUtxo from the mintOneTimeMintingPolicy transaction.

Note: You must provide the txHash forContentRegistry, ContentRefToken, OwnershipRegistry,OwnershipRefToken transactions.

Getting the oracle data is essential to fetch the current state of the registry.

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.

For example:

This transaction mints a token that users can use to create content.

Note that you can actually use any tokens for createContent(), this mintUserToken() function is just helpful if you want to mint a token specifically for this purpose.

Note that you signTx with true to mint the token to enable partial signing.

This transaction creates a content attached to the registry reference by a token. You can use any token for ownerAssetHex and the contentHashHex is a string to identify the content.

Note: You must provide the paramUtxo from the mintOneTimeMintingPolicy transaction.

Note: You must provide the txHash forContentRegistry, ContentRefToken, OwnershipRegistry,OwnershipRefToken transactions.

This transaction fetches the content data from the registry.