Learn about the different types of alerts and how to configure them
ChainRaven monitors your smart contracts for four types of security-relevant events. This guide explains each alert type, why it matters, and what information is included in each notification.
| Alert Type | What It Detects | Default Severity |
|---|---|---|
| Large Transfer | Token transfers exceeding your configured threshold | Configurable |
| Ownership Transfer | Contract owner changed | High |
| Proxy Upgrade | Implementation address changed | Critical |
| Admin Change | Admin role transferred or revoked | High |
ChainRaven monitors Transfer events emitted by ERC-20 token contracts on your watchlist. When a single transfer exceeds your configured threshold, a Large Transfer alert is triggered.
You can configure thresholds three ways:
1,000,000 USDC)$500,000)1%)See Large Transfer Detection for full configuration details.
Large transfer alerts use multiplier-based severity relative to your configured threshold:
| Excess Over Threshold | Severity |
|---|---|
| 1×–2× | Low |
| 2×–5× | Medium |
| 5×–10× | High |
| 10×+ | Critical |
Detects when a contract emits the OwnershipTransferred event, indicating the contract owner has changed to a new address.
Tip: If you weren't expecting an ownership transfer on a contract you own or rely on, treat it as a potential security incident and investigate immediately.
Detects when a proxy contract's implementation is upgraded via the Upgraded event. This means the contract's logic has been replaced with a new implementation.
Note: If you receive a Proxy Upgrade alert, consider running an AI Contract Analysis on the new implementation address to understand what changed.
Detects AdminChanged events when the admin role is transferred to a different address. The admin role controls who can upgrade the proxy implementation.
ChainRaven uses four severity levels across all alert types:
| Level | Color | Meaning |
|---|---|---|
| Low | Blue | Informational — no immediate action needed |
| Medium | Yellow | Worth reviewing when convenient |
| High | Orange | Requires prompt attention |
| Critical | Red | Requires immediate investigation |
You can configure a minimum severity threshold in Alert Preferences to reduce notification noise on busy contracts.
Each monitored contract receives a health score from 0–100 based on recent event activity:
| Score | Status | Meaning |
|---|---|---|
| 0–30 | 🟢 Healthy | No concerning events detected |
| 31–70 | 🟡 Elevated | Some events detected — worth monitoring |
| 71–100 | 🔴 Critical | Multiple high-severity events — investigate immediately |
The score is recalculated continuously and considers the number and severity of events detected in the last 24 hours.