# Managing hooks For similar reasons as the asset registry, the Aera client is responsible for managing the hooks contract. This currently entails maintaining the target sighash allowlist which governs the type of contracts and operations on those contracts that the gurdian can submit for execution It's critical that the client independently evaluates the correctness of any calldata sent to the hooks contract. Adding an target sighash pair is a sensitive operation that could needlessly empower the guardian. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.aera.finance/v2-archive/guides/treasury/managing-hooks.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.