Documentation

Alert Preferences

Customize how and when you receive notifications

Back to Documentation

Alert Preferences give you fine-grained control over every aspect of how ChainRaven notifies you — from which channels receive which alerts, to how severe an event needs to be before you hear about it.

Accessing Alert Preferences

  1. Click your profile icon in the top-right corner
  2. Select Profile Settings
  3. Click the Alert Preferences tab

Each alert type has its own expandable section. Click on an alert type to expand its settings.

Settings for Each Alert Type

Enable / Disable

The main toggle at the top of each section turns monitoring on or off for that alert type entirely. When disabled, ChainRaven won't detect or send notifications for that event type.

Notification Channels

Choose where to receive alerts. You can enable multiple channels to receive the same alert in multiple places simultaneously.

ChannelNotes
EmailEnabled by default for all users
TelegramRequires setup first — see Telegram Setup
DiscordRequires setup first — see Discord Setup
WebhookPer-alert-type, custom endpoint — see Webhook Setup

Severity Configuration

For Large Transfers, you can choose between two modes:

  • Simple Mode — one severity level for all large transfer alerts
  • Range Mode — define different severity levels based on how much the threshold is exceeded:
Excess Over ThresholdAssigned Severity
1×–2×Low
2×–5×Medium
5×–10×High
10×+Critical

For all other alert types, select the severity level assigned to all alerts of that type. Most users keep the defaults (High for ownership/admin changes, Critical for proxy upgrades).

Minimum Severity to Send

This filter controls which alerts actually get sent to you, regardless of what's detected:

SettingEffect
LowReceive all alerts
MediumSkip Low severity alerts
HighOnly receive High and Critical alerts
CriticalOnly receive Critical alerts

Tip: On contracts with high activity, setting a higher minimum severity can significantly reduce notification noise without missing anything important.

Cooldown Period

Prevents notification overload by setting a minimum time between repeated alerts of the same type on the same contract.

ValueDuration
0No cooldown (receive every alert)
90015 minutes
36001 hour (default)
8640024 hours

Max Retry Attempts

If an alert fails to send (e.g., a webhook timeout or temporary Telegram outage), ChainRaven will retry automatically.

  • Range: 1–5 attempts
  • Default: 3 attempts

Per-Alert-Type Webhooks

Unlike Email, Telegram, and Discord which are global settings, webhooks can be configured separately for each alert type. This allows advanced routing:

  • Send Large Transfer alerts to a financial monitoring system
  • Send Critical alerts (Ownership/Proxy/Admin) to a security incident channel
  • Use different webhook secrets for different alert types for added security

Configure webhooks in the expanded section for each alert type.

Saving Your Changes

Important: Changes are not saved automatically.

After making changes:

  1. Click the Save Changes button
  2. Wait for the green confirmation message

To undo unsaved changes, click Discard Changes.

Tips

  • Start with defaults — the default settings work well for most users and can be refined over time
  • Adjust cooldowns by risk — use shorter cooldowns for Critical events, longer for Low severity
  • Test your integrations — after connecting Telegram, Discord, or a webhook, send a test alert to verify everything works before relying on it

Next Steps