Skip to content

Mint packages NFTs

This guide describes how to use the Olas Protocol web app to mint software packages NFTs in the Olas Protocol. You can mint three types of packages: AI agents, Agent blueprints and Components.

How packages are minted

To mint a package (also referred to as unit) in the protocol, it must have been published into a remote IPFS registry. Read how to publish packages with the Open Autonomy framework.

Minting a software package involves creating a metadata file that contains the package data and a pointer to the IPFS where the package is published. The Olas Protocol web app will automatically create and publish the metadata file on the IPFS registry, based on the package/unit information provided by the user in an online form. Then, it will interact with the protocol smart contracts to complete minting the package on-chain.

Upon completing the minting process, you will have an NFT representing your package in the Olas Protocol. See the figure below.

Package minting

Components and Agent Blueprints are minted on ETH mainnet only, and then used as "foreign" IDs in AI Agents on any chosen network, since off-chain agent instances read from any chain and unpack configurations and codes following IPFS hashes. Minted NFTs offer an on-chain representation of the relationship between different software packages by mirroring their dependency relations. This helps the protocol Tokenomics to compute appropriate incentives, for example, based on how often a component is referenced.

Package dependencies represented on-chain

Requirements

In order to mint a software package as an NFT, you must ensure that you have:

  • An address associated to either

  • a crypto wallet (e.g., Metamask or

  • a multisig contract (like Safe) which allows to connect via Wallet Connect.

    In either case, the address must have funds for the chain that you wish to mint the package NFT.

  • The hash of the package that you want to mint on-chain, and which must have been published into a remote registry.

  • An NFT image URL. This image will be used to represent the minted NFT for the package on marketplaces such as OpenSea. You can use this sample image URL for testing purposes.

Mint a component

Connect your wallet to the Olas Protocol web app, open the components section and press the Mint button. Fill in the data of your component:

Mint component screenshot

  1. Owner Address. The wallet address of the component owner (starting with 0x...). It does not need to be the address of the connected wallet.

  2. Generate IPFS hash of the metadata file. Press the Generate Hash & File button and fill in the following data:

    • Name. The name of the component.
    • Description. A description of the component.
    • Version. The component version, in the format, <major>.<minor>.<patch>.
    • Package hash. The remote registry package hash starting with bafybei... obtained when the component was published in the remote registry.
    • NFT Image URL. An URL pointing to an image. You can use this sample image URL for testing purposes.

    By pressing the Save File & Generate Hash button, a metadata file with this information will be automatically generated and uploaded to the remote registry. You will notice that the hash will be populated in the component online form.

  3. Dependencies. Comma-separated list of component IDs which the component requires. You can find the IDs by browsing the components section.

Press the Submit button. Your wallet will ask you to approve the transaction. Once the transaction is settled, you should see a message indicating that the component NFT has been minted successfully.

Mint an agent blueprint

Connect your wallet to the Olas Protocol web app, open the agent blueprints section and press the Add Agent Blueprint button. Fill in the data of your agent blueprint:

Mint agent blueprint screenshot

  1. Owner Address. The wallet address of the agent blueprint owner (starting with 0x...). It does not need to be the address of the connected wallet.

  2. Generate IPFS hash of the metadata file. Press the Generate Hash & File button and fill in the following data:

    • Name. The name of the agent blueprint.
    • Description. A description of the blueprint.
    • Version. The blueprint version, in the format, <major>.<minor>.<patch>.
    • Package hash. The remote registry package hash starting with bafybei... obtained when the blueprint was published in the remote registry.
    • NFT Image URL. An URL pointing to an image. You can use this sample image URL for testing purposes.

    By pressing the Save File & Generate Hash button, a metadata file with this information will be automatically generated and uploaded to the remote registry. You will notice that the hash will be populated in the agent blueprint online form.

  3. Dependencies. Comma-separated list of component IDs which the agent blueprint requires. You can find the IDs by browsing the components section. At least one component must be specified here. If you're unsure which component to specify, write 1 as default.

Press the Submit button. Your wallet will ask you to approve the transaction. Once the transaction is settled, you should see a message indicating that the agent blueprint NFT has been minted successfully.

Mint an AI agent

Connect your wallet to the Olas Protocol web app, open the AI agents section and press the Add AI Agent button. Fill in the data of your AI agent:

Mint AI Agent screenshot

  1. Owner Address. The wallet address of the AI agent owner (starting with 0x...). It does not need to be the address of the connected wallet.

  2. Generate IPFS hash of the metadata file. Press the Generate Hash & File button and fill in the following data:

    • Name. The name of the AI agent.
    • Description. A description of the AI agent.
    • Version. The AI agent version, in the format, <major>.<minor>.<patch>.
    • Package hash. The remote registry package hash starting with bafybei... obtained when the AI agent was published in the remote registry.
    • NFT Image URL. An URL pointing to an image. You can use this sample image URL for testing purposes.

    By pressing the Save File & Generate Hash button, a metadata file with this information will be automatically generated and uploaded to the remote registry. You will notice that the hash will be populated in the AI agent online form.

  3. Agent Blueprints. Comma-separated list of agent blueprint IDs which the AI agent requires. You can find the IDs by browsing the agent blueprints section.

  4. No. of slots to Agent Blueprints. Specify the number of agent instances for each agent blueprint ID listed above.

  5. Cost of agent instance bond. Specify (in Wei units) what is the bond per each agent instance joining the AI agent. If you are using it for testing purposes, we suggest that you use a small value (e.g., 1000000000000000 GörliWei = 0.001 GörliETH).

  6. Threshold. Specify the threshold of agent instances required to sign.

Press the Submit button. Your wallet will ask you to approve the transaction. Once the transaction is settled, you should see a message indicating that the AI agent NFT has been minted successfully. You should also see that the AI agent is in Pre-Registration state.

Once the AI agent NFT has been minted, you can manage the life cycle of the AI agent.