# Documentation

## Documentation

- [Welcome to Coverage!](https://docs.coveragelabs.io/welcome-to-coverage.md): Blockchain security is a high-stakes game where one exploit can result in billions of losses. Our mission is to make Web3 safer by proactively uncovering vulnerabilities and fortifying defenses.
- [Request Form](https://docs.coveragelabs.io/methodology/request-form.md): This is the starting point through which all engagements begin when a client submits a request for a quote.
- [Scope of Work](https://docs.coveragelabs.io/methodology/scope-of-work.md): The scoping process is essential for accurately allocating resources, setting realistic timelines, and defining clear deliverables for the engagement.
- [Rates](https://docs.coveragelabs.io/methodology/rates.md): This section details the base weekly rates for security reviews and fuzzing campaigns, determined by the agreed-upon number of engineers and the duration of the engagement.
- [Statement of Work](https://docs.coveragelabs.io/methodology/statement-of-work.md): The Statement of Work outlines the key terms of the agreement between the client and Coverage, ensuring both parties are aligned.
- [Communication](https://docs.coveragelabs.io/methodology/communication.md): This section outlines how communication is handled during our engagements, including the frequency and channels we'll use to ensure smooth and effective collaboration.
- [Security Review](https://docs.coveragelabs.io/services/security-review.md)
- [Context & Cleanup](https://docs.coveragelabs.io/services/security-review/context-and-cleanup.md): During this phase, we dive deep into your codebase to understand its intricacies, establish context, and eliminate known anti-patterns.
- [Manual Review](https://docs.coveragelabs.io/services/security-review/manual-review.md): During this phase, the codebase is reviewed to identify potential edge cases, design flaws, and attack vectors, while ensuring the business logic aligns with the project's technical specifications.
- [Quality Assurance](https://docs.coveragelabs.io/services/security-review/quality-assurance.md): During this phase, we document the capabilities of privileged actors within the protocol and assess the maturity of the codebase across multiple categories, highlighting areas for improvement.
- [Fix Review](https://docs.coveragelabs.io/services/security-review/fix-review.md): During this phase, the mitigations implemented for previously identified vulnerabilities are reviewed. The goal is to verify that the fixes are correctly applied and do not introduce new issues.
- [Final Report](https://docs.coveragelabs.io/services/security-review/final-report.md): During this phase, we generate a report that summarizes all findings, fixes, and recommendations, marking the end of the engagement
- [Fuzzing Campaign](https://docs.coveragelabs.io/services/fuzzing-campaign.md)
- [Invariant Development](https://docs.coveragelabs.io/services/fuzzing-campaign/invariant-development.md): The foundation of an effective fuzzing campaign lies in precisely defining the invariants—the unshakable truths of your protocol.
- [Implementation](https://docs.coveragelabs.io/services/fuzzing-campaign/implementation.md): During this phase we implement a stateful fuzzing test suite with Echidna, translating system properties into enforceable rules to verify correct code behavior.
- [Tests & Integration](https://docs.coveragelabs.io/services/fuzzing-campaign/tests-and-integration.md): We run a 48-hour fuzzing campaign to extensively test all protocol invariants. The test suite is then integrated into your CI/CD, triggering short fuzzing campaigns on every commit.
- [Fix Review](https://docs.coveragelabs.io/services/fuzzing-campaign/fix-review.md): During this phase, the mitigations implemented for previously identified vulnerabilities are reviewed. The goal is to verify that the fixes are correctly applied and do not introduce new issues.
- [Final Report](https://docs.coveragelabs.io/services/fuzzing-campaign/final-report.md): During this phase, we generate a report that summarizes all findings, invariants, runs and recommendations, marking the end of the engagement
- [Media Kit](https://docs.coveragelabs.io/resources/media-kit.md)


---

# 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, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on a page URL with the `ask` query parameter:
```
GET https://docs.coveragelabs.io/welcome-to-coverage.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.