> For the complete documentation index, see [llms.txt](https://docs.42.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.42.space/for-developers/interactive-blocks.md).

# Frequently Ask Questions

Common FAQ.

### Security

<details>

<summary><strong>Has 42 been audited?</strong></summary>

The 42 protocol has undergone security reviews and audits by independent third-party auditors (refer to [Audits](https://docs.42.space/security/markdown.md)). Identified issues have been addressed prior to deployment, and the team continues to improve the codebase as the protocol evolves.

That said, no smart-contract system can be considered entirely risk-free. Users should always assess their own risk tolerance and participate responsibly.

</details>

<details>

<summary><strong>What risks should users be aware of?</strong></summary>

42 is a non-custodial, smart-contract-based protocol. Participation involves interacting directly with on-chain code, which carries inherent risks, including but not limited to:

* **Smart contract vulnerabilities:** unforeseen bugs or edge cases may exist despite audits and testing.
* **Oracle and resolution risk:** markets resolve strictly according to predefined rules and data sources; unexpected oracle behavior or data anomalies may impact outcomes.
* **Economic and market risk:** prices and payouts depend on participant behavior, timing, and capital distribution.
* **Protocol integrations:** where 42 interfaces with external infrastructure (e.g. oracles, settlement layers), failures or exploits in those systems may affect the protocol.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.42.space/for-developers/interactive-blocks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
