> ## Documentation Index
> Fetch the complete documentation index at: https://phylaxsystems-docs-project-incidents.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Incidents

> View incidents prevented by the Credible Layer

Incidents show when transactions were dropped because they violated assertions protecting contracts. This happens when a transaction that interacted with an assertion-protected contract was dropped by the [Enforcer](/credible/glossary#assertion-enforcer) because it caused an assertion to revert.

<Note>
  For the end-to-end flow, see the incident lifecycle diagram in
  [Architecture Overview](/credible/architecture-overview#incident-lifecycle-public-view).
</Note>

## How Incidents Are Grouped

An incident represents the invalidation of an assertion over a one-hour time period. Multiple dropped transactions can belong to the same incident if they violate the same assertion within that window.

**Why group transactions into incidents?**

* An attacker may craft multiple transactions that all violate the same assertion—these represent the same logical attack
* One hour is a reasonable estimate for how long an attack attempt might last
* After one hour without violations, a new invalidation likely indicates a different attack and creates a new incident

This grouping ensures you receive meaningful alerts without being spammed by repeated notifications for the same security event.

<Note>
  This is our initial approach to incident grouping and may be refined based on user feedback.
</Note>

## Project Incidents (Manager View)

<Check>Project incidents are visible only to the project manager and live inside the project dashboard.</Check>

Non-owners see project events, not incidents.

### Access and Navigation

* Open a project and select the **Incidents** tab.
* Route: `/projects/{project_id}/incidents`

<Frame caption="Project view header with the Incidents tab selected (screenshot placeholder)">
  <img src="https://mintcdn.com/phylaxsystems-docs-project-incidents/eyA1dTF0njiU7Xo-/images/incidents_project.png?fit=max&auto=format&n=eyA1dTF0njiU7Xo-&q=85&s=70c2d0deea41ff8c1d52cc6596ca5b2e" alt="Incidents Tab" width="5234" height="3054" data-path="images/incidents_project.png" />
</Frame>

### Incidents

The incidents list shows recent incidents for the project, ordered by most recent.

Each row includes:

* **Timestamp**
* **Contract Affected**
* **Assertion Triggered**
* **Invalid Transactions** count
* **Environment** (staging or production)

Click a row to open the incident detail view.

<Frame caption="Project incidents list view">
  <img src="https://mintcdn.com/phylaxsystems-docs-project-incidents/eyA1dTF0njiU7Xo-/images/incident_overview.png?fit=max&auto=format&n=eyA1dTF0njiU7Xo-&q=85&s=252a02389af30598f6e1ed543018125a" alt="Incident Overview" width="5234" height="3054" data-path="images/incident_overview.png" />
</Frame>

### Incident Detail and Invalidating Transactions

The incident detail page summarizes the incident and lists invalidating transactions.
It includes:

* **Incident detail card** with date, contract affected, assertion triggered, assertion group, invalid transaction count, and environment
* **Critical warning banner** if any invalidating transaction landed on-chain
* **Invalid Transactions** list with expandable rows and action buttons

Each invalidating transaction includes:

* Transaction hash, to/from, value, calldata, and block number (if available)
* **Open Debug View** to inspect the trace
* **Copy Data as JSON** to export the transaction

<Frame caption="Incident detail with invalidating transactions">
  <img src="https://mintcdn.com/phylaxsystems-docs-project-incidents/eyA1dTF0njiU7Xo-/images/incident_tx_details.png?fit=max&auto=format&n=eyA1dTF0njiU7Xo-&q=85&s=717dea93ec192a0b4e330a8a1c7b2a1f" alt="Incident details" width="5234" height="3054" data-path="images/incident_tx_details.png" />
</Frame>

### Debug Trace View

The debug trace view opens from an invalidating transaction.

* Route: `/projects/{project_id}/trace/{incident_id}/{transaction_id}`
* **Transaction Attributes** panel with copy-all action
* **Execution Context** panel (block environment + previous transactions)
* **Transaction Trace** panel with status: pending, in progress, completed, failed, or skipped

<Frame caption="Debug trace start">
  <img src="https://mintcdn.com/phylaxsystems-docs-project-incidents/eyA1dTF0njiU7Xo-/images/incident_trace.png?fit=max&auto=format&n=eyA1dTF0njiU7Xo-&q=85&s=d5b68a533abf9fc899f3a9273edbc692" alt="Incident trace 1" width="5234" height="3054" data-path="images/incident_trace.png" />
</Frame>

<Frame caption="Debug trace cont.">
  <img src="https://mintcdn.com/phylaxsystems-docs-project-incidents/eyA1dTF0njiU7Xo-/images/incident_trace_2.png?fit=max&auto=format&n=eyA1dTF0njiU7Xo-&q=85&s=235fd58e9fd8bb93a72f605ff7874e02" alt="Incident trace 1" width="5234" height="3054" data-path="images/incident_trace_2.png" />
</Frame>

### Real-Time Updates and Alerts

When a project manager is viewing the incidents list, new incidents stream into the list in real time.
You can also set up external alerts via webhooks:

* **Slack Integration**: Configure Slack webhooks to receive incident notifications
* **PagerDuty Integration**: Configure PagerDuty webhooks to receive incident notifications

See [Integrations](/credible/dapp-integrations) for setup instructions.

## Public Transparency Incidents

The Transparency dashboard includes a public incidents list with limited metadata for visibility.
Detailed transaction and trace views are only available to project managers.

## Use Cases

* Monitor when assertions prevent violations for your projects
* Understand attack patterns and attempted exploits targeting your protocol
* Add or refine assertions based on incident data

<Warning>
  Incident viewing is read-only. You cannot modify or delete incident records.
</Warning>

## Next Steps

<CardGroup cols={2}>
  <Card title="dApp Overview" icon="info" href="/credible/dapp-overview">
    Learn more about the dApp
  </Card>

  <Card title="Transparency Dashboard" icon="search" href="/credible/dapp-transparency-dashboard">
    Browse projects and assertions
  </Card>

  <Card title="Writing Assertions" icon="code" href="/credible/write-first-assertion">
    Learn how to write effective assertions
  </Card>

  <Card title="Architecture" icon="gears" href="/credible/architecture-overview">
    Understand how assertion validation works
  </Card>
</CardGroup>
