Skip to main content

​
GPG signed messages

The Monad Foundation announcements to node operators will be GPG signed. Once the Monad Foundation sends a message via official node operators channels (Discord, Email, Slack, Telegram), node operators can independently verify the authenticity of the message by verifying the GPG signatures. Each message will contain:
  • announcement.txt - the readable announcement (example)
  • announcement.sig - the combined signatures from 2+ authorized signers (example)
The readable announcement will contain:
  • an unique index (e.g. MF Announcement #0)
  • an UTC creation timestamp in the ISO 8601 format (e.g. Created: 2026-08-08T08:08:08Z)
  • the actual message content
The signature file will contain the combined PGP signatures from 2+ authorized signers. The messages will be sent/posted after the creation timestamp, the index will be incremental and each message will include signatures from at least two authorized signers. Their public keys can be found in the official repository, while their full primary-key fingerprints can be found in the official documentation. More information can be found in the official repository.

​
Channels

Subscribe to the following channels to receive Monad Foundation announcements:

​
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.
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.
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.