Hosting
The host address of a Collection can:
  1. 1.
    Create, for the Collection, new itemIds
  2. 2.
    Mint Items of the Collection’s itemIds in the Collection
  3. 3.
    Change the metadata of the Collection and / or its Items.
Who Can Host a Collection?
A Collection’s host can be either:
  1. 1.
    No one, i.e address(0).
  2. 2.
    An extension, cloned from the Extension factory.
In the first case, nobody can create new itemIds for the Collection, mint new Items of preexisting itemIds in the Collection, nor change the metadata of the Collection and / or its Items.
In the second case, the extension—that right now is the multiOperatorHostand the Native—can be used to govern the Collection with the granular permission system described below.
What Is the multiOperatorHost Extension?
The multiOperatorHost is a smart contract that, once linked to a Collection of Items, becomes the Collection’s host address. As the host address, it manages the Collection’s itemId creation logic, Item minting logic & metadata modifying logic, following the rules established by the Collection’s creator.
Extensions allow developers to granulate how their Item Collections operate. Especially when used in tandem with the other capabilities of the Item protocol, they help unlock the potential of what is the most sophisticated & first ever upgradeable, programmable and perfectly interoperable token standard.
How Does It Work?
As a Collection’s host address, a multiOperatorHost can designate permission to two Operator addresses to do these two general things:
  1. 1.
    Change the metadata of the Collection and / or its Items
  2. 2.
    Create new itemIds for the Collection and mint new Items of the Collection’s itemIds inside the Collection.
What is the Native Extension?
The Native is a smart contract that, once linked to a Collection of Items, becomes the Collection’s host address. As the host address, it manages the Collection’s itemId creation logic, Item minting logic, metadata modifying logic and finalization logic (if an Item is finalized, it can no longer be minted).
Even the Native Extension allows developers to granulate how their Item Collections operate, differently from the multiOperatorHost. Look at the following pages to learn more.
How Does It Work?
As a Collection’s host address, a Native can designate permission to an Operator address to do this thing:
  1. 1.
    Change the metadata of the Collection and / or its Items
While the host address of the Native Extension can:
  1. 1.
    Create new itemIds for the Collection and mint new Items of the Collection’s itemIds inside the Collection
  2. 2.
    Finalize Items, i.e. to make the token not more mintable and therefore to have a fixed supply.
Copy link