Incident Response

RAX Protocol includes monitoring and alerting mechanisms designed to surface abnormal conditions and potential incidents.

This page describes how RAX responds to detected incidents and how users should interpret and act on related signals.


What Constitutes an Incident

An incident may include, but is not limited to:

  • Severe liquidity stress

  • Rapid increases in Risk Scores

  • Persistent high-severity alerts

  • Widespread anomalies across protocols or chains

  • Data integrity or infrastructure disruptions

Incidents may originate from market conditions, external protocols, or underlying infrastructure.


Detection and Notification

RAX detects incidents through a combination of:

  • Real-time monitoring

  • Risk threshold breaches

  • Anomaly detection

  • Model confidence degradation

When an incident is detected, alerts are generated according to configured severity levels and notification settings.


RAX System Response

Upon detecting an incident, RAX may:

  • Increase alert frequency

  • Highlight affected assets, protocols, or chains

  • Reduce model confidence where appropriate

  • Apply more conservative assumptions in simulations

  • Restrict or caution allocation suggestions

These responses are designed to surface risk clearly rather than obscure it.


User Responsibilities During an Incident

During elevated risk conditions, users are expected to:

  • Review alerts and supporting metrics

  • Avoid increasing exposure without analysis

  • Reassess risk constraints and strategy profiles

  • Use simulations to evaluate downside scenarios

  • Apply independent judgment and caution

RAX does not automatically execute protective actions unless explicitly configured to do so.


Communication and Transparency

Significant incidents affecting system-wide behavior may be communicated through:

  • In-app notifications

  • Documentation updates

  • Public communication channels

Transparency is prioritized to ensure users understand system behavior and limitations during incidents.


Limitations

Incident detection does not guarantee prevention of losses.

RAX may not detect all incidents in advance, particularly those involving novel or unprecedented conditions.


Summary

Incident response within RAX focuses on visibility, transparency, and user awareness.

By surfacing abnormal conditions and adjusting system behavior conservatively, RAX supports more informed decision-making during periods of stress.

Last updated