> For the complete documentation index, see [llms.txt](https://dualguard.gitbook.io/dualguard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dualguard.gitbook.io/dualguard/security-reviews/protocol-teams/protocol-involvement-during-the-audit-process.md).

# Protocol Involvement During the Audit Process

#### Protocol involvement during the audit process

DualGuard audits run best when the protocol team stays available during the review window. Auditors will ask about expected behavior, permissions, integrations, and edge cases. Clear, timely answers reduce ambiguity and improve review quality.<br>

**Communication during an security review contest**

At the start of a contest, the protocol team joins a shared channel for auditor Q\&A. Participation is not required, but active teams usually get more accurate reports and fewer avoidable misunderstandings.<br>

During the contest, findings move through DualGuard’s review workflow. Reports may be assessed and validated while the contest is still active. To protect the process, submission visibility stays limited during the contest window. Protocol teams should also avoid sharing exploit details or partial findings publicly until review and disclosure are coordinated.

After the contest ends, the protocol receives the validated findings, severity assessments, and remediation guidance. Fix verification follows once patches are ready.

**Expectations for protocol teams**

Protocol teams should plan to stay reachable during audit weeks for questions and clarifications. They should also move quickly on remediation and fix verification after findings are confirmed.