> For the complete documentation index, see [llms.txt](https://docs.obol.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.obol.org/next/advanced-and-troubleshooting/security.md).

# Security

- [Overview](https://docs.obol.org/next/advanced-and-troubleshooting/security/overview.md): An overview of Obol's security posture — official domains, completed audits, threat model references, and the bug bounty program.
- [Centralization Risks and Mitigation](https://docs.obol.org/next/advanced-and-troubleshooting/security/risks.md): Outlining potential centralization risks and their mitigations
- [Obol Bug Bounty Program](https://docs.obol.org/next/advanced-and-troubleshooting/security/bug-bounty.md): Obol's bug bounty program, scope, and reward structure for security researchers reporting vulnerabilities in our distributed validator software.
- [Smart Contract Audit](https://docs.obol.org/next/advanced-and-troubleshooting/security/smart-contract-audit.md): Public audit reports for the Obol Splits and Obol Validator Manager smart contracts.
- [Software Development at Obol](https://docs.obol.org/next/advanced-and-troubleshooting/security/ev-assessment.md): Ethereal Ventures' assessment of Obol's software development lifecycle and operational security practices, with the team's responses to each recommendation.
- [Charon Threat Model](https://docs.obol.org/next/advanced-and-troubleshooting/security/threat_model.md): A threat model for Charon as a distributed validator middleware — actors, attack surfaces, and the cryptographic and BFT properties that bound each risk.
- [Contacts](https://docs.obol.org/next/advanced-and-troubleshooting/security/contact.md): How to report a security incident or vulnerability to Obol, and where to find Obol's public security disclosures.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.obol.org/next/advanced-and-troubleshooting/security.md?ask=<question>
```

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.