> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monad.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Announcements

## Channels

Subscribe to the following channels to receive Monad Foundation announcements:

| Channel  | Link                                                                 |
| -------- | -------------------------------------------------------------------- |
| Email    | Delivered to the address associated with your validator registration |
| Discord  | [#mainnet-validator-announcements](https://discord.gg/monaddev)      |
| Telegram | [Node Announcements](https://t.me/MonadNodeAnnouncements)            |

## Severity System

In order to provide a standardized framework for network-related communications, the Monad Foundation uses the following color-coded categories to preface announcements. These categories are directly attributed to level of severity, recommended action, and timeframe.

<Info>
  Ecosystem participants can use this framework to set up alerts (e.g. PagerDuty) for "CODE RED" in email subjects or social channels, further assisting in the dissemination of time-critical information.
</Info>

Announcements may be reclassified as more information becomes available. In an emergency, the Foundation may use any available communication channel regardless of the classification below.

### Green 🟢

**Subject contains "CODE GREEN"** — informational, no action required.

Examples:

* Optional upgrades
* Validator info updates
* Social coordination messaging
* Non-critical additions to the operations layer

### Orange 🟠

**Subject contains "CODE ORANGE"** — action recommended within 24–48 hours.

Examples:

* Upcoming non-emergency upgrades

Communication will be shared over email, Discord, and the Telegram Node Announcements channel.

### Red 🔴

**Subject contains "CODE RED"** — action recommended immediately upon receiving communication.

Examples:

* Critical emergency upgrades
* Chain halts
* Staking protocol compromises

Communication channels depend on the nature of the incident:

* **Resetricted rollout** (emergency and sensitive, e.g. security vulnerability) — to minimize the risk of exploitation before a patch is widely deployed, communication may initially be shared **exclusively over email** to known validators.
* **Unrestricted rollout** (emergency but not sensitive, e.g. emergency upgrade affecting chain liveness) — communication will generally be shared over email, Discord, and the Telegram Node Announcements channel.