# Token Factory

Token Factory is the contract used for Summon Exports from a metaverse. It is an ERC-1155 that spawns its individual ID tokens as standalone ERC-20s instead of internal accounting, acting as their parent. Transactions made on the individual ER-C20s trigger and log appropriate events in the parent contract and vice-versa. These tokens combine the advantages of the fungible/non-fungible worlds. This means exported assets are both NFTs (therefore supported by NFT marketplaces) and regular ERC-20 tokens (supported by DEXs, CEXs, etc.), depending on which contract we manage them from. The only disadvantages are: slightly higher gas cost, allowances have to be made on the parent/children separately, and introducing the decimal concept to ERC-1155 because it has to match with the underlying ERC-20’s.

![Fig. 6. Multiverse Asset Factory](https://3181322212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHoSxDEX74aEigEDYbles%2Fuploads%2Fc0DbjfoMigljZguptIIK%2Ftokenfactory.drawio.png?alt=media\&token=6b80c32b-863f-4da8-a569-381efea4bb5e)

All the summoned (minted) tokens are made by the factory from all the integrated Metaverses. We believe we made a quite generic standard that caters for all fungible and non-fungible needs. A Metaverse can only mint an ERC20, or looked at from the parent, an ERC1155 with a specific ID it was permissioned for. Obviously, the oracles of the Willy Wonka Metaverse should not have access to the minting of Minecraft Gold Tokens and vice-versa.
