> 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/handler.md).

# Handler

Handlers in the tokenization engine ecosystem have a pivotal role as the sole accounts responsible for sending and receiving ERC1155 NFTs and ERC20 tokens during a system freeze caused by certification lapses.

The appointment of a handler is not always immediate, but when obstacles arise during the audit process, the certifier must provide a remediation plan for the handler to restore system integrity promptly.

Handlers can be either Externally Owned Accounts (EOA) or smart contracts, with the latter offering higher trustworthiness but the former being more practical in time-sensitive situations.

In certain cases, a handler may also assume the roles of a connector and/or a disconnector, resolving inconsistencies between on-chain and off-chain assets for a synchronized ecosystem.

After successful repair and certification, it is crucial to revoke or renounce the handler role, emphasizing its temporary nature and ensuring a well-regulated operational environment.