> For the complete documentation index, see [llms.txt](https://s0x.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://s0x.gitbook.io/docs/primary-issuance/roles-and-permissions/connector.md).

# Connector

Connectors play a crucial role in bridging the gap between off-chain stocks and their on-chain tokenized counterparts within the tokenization engine framework. These connectors facilitate the creation of matching ERC1155 NFTs and ERC20 tokens through a single connect function embedded in the contract.

When utilizing the connect function, connectors specify the amount of ERC1155 and ERC20 tokens to be minted, along with relevant data that serves as input for audit reports reviewed by certifiers. Typically, this data takes the form of an IPFS hash, enabling efficient retrieval and processing by scripts rather than including detailed audit information directly.

For instance, imagine a scenario where a connector aims to bring stocks on-chain for tokenization. The accompanying data provided during the tokenization process would include essential details to that stock. However, for the purpose of minting the ERC1155 and ERC20 tokens, the pertinent information would focus primarily on the quantity of shares to be tokenized, their corresponding identifiers, and any additional attributes necessary for accurate representation.

It is important to note that while connectors often encompass both connection and disconnection functionalities, allowing for seamless tokenization and potential unwinding processes, such dual capability is not obligatory within the tokenization engine ecosystem.