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

# Certifier

Within the tokenization engine framework, the certifier assumes a vital role, empowered to invoke the certify function, which holds the capability to extend or supersede the ongoing certification period. By default, a new certification will uphold or extend the existing expiry date, although the certifier possesses the flexibility to specify an alternative date, which may be either shorter or even past the current timeframe, through an additional parameter.

As part of their certification duties, certifiers are expected to provide supplementary data, referencing an audit report that substantiates and justifies their certification decision. The audit process typically follows a structured sequence:

* Firstly, the certifier executes a script, extracting auditable information from the blockchain logs, encompassing all connections and disconnections. This data serves as the foundation for subsequent evaluation.
* Secondly, a real-world audit of the off-chain assets ensues, meticulously aligning them against the extracted information. This rigorous assessment culminates in a comprehensive audit report, capturing the findings and outcomes.
* Finally, the certifier publishes the audit report on-chain, utilizing the certify function, thereby validating the certification and cementing the integrity of the system. It is important to note that parallel audits can be conducted simultaneously by multiple certifiers, allowing for independent assessments without any interference between respective logs, except in cases where a forced expiry override is implemented.

If, at any point, the certification expires, a system-wide freeze ensues, affecting all participants, barring handlers. This freeze encompasses the prohibition of connecting and disconnecting assets, as well as the imposition of restrictions on all administrative actions. The handlers, however, retain their privileges and remain operational.

Typically, a certifier solely assumes the role of a certifier. This impartial stance is paramount, ensuring that they are perceived as "arms-length" participants, engendering trust in their ability to maintain objectivity and impartiality. To preserve this integrity, it is advisable for an impartial entity not to hold assets or possess privileged roles, as such circumstances could be perceived as conflicts of interest.

\ <br>