For the complete documentation index, see llms.txt. This page is also available as Markdown.

Frequently Ask Questions

Common FAQ.

Security

Has 42 been audited?

The 42 protocol has undergone security reviews and audits by independent third-party auditors (refer to Audits). 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.

What risks should users be aware of?

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.

Last updated