On-Chain Alert Builder
No-code alert designer: compose up to 4 conditions (metric × operator × threshold) joined by AND/OR on 6 flagship metrics (MVRV, Puell, NUPL, Reserve Risk, Trinity Composite, Market Cycle Phase). 10-year backtest + sensitivity indicator + localStorage persistence. Live monitoring and notifications are not yet available.
What is it?
The On-Chain Alert Builder is a no-code tool to design, test and save custom alert rules on key on-chain metrics (MVRV, Puell Multiple, NUPL, Reserve Risk, Trinity Composite Score, Market Cycle Phase). Users assemble up to 4 conditions (metric + operator + threshold) joined by AND/OR, name their rule and save it in their browser (localStorage). A backtest button replays 10 years of history to measure trigger frequency and sensitivity.
How to read
The interface presents as a visual rule builder with blocks to assemble. Each block represents a condition (metric + operator + threshold). Blocks are connected by AND or OR. The 'Backtest (10y)' button measures how many times the rule would have fired historically. A sensitivity indicator (green/amber/red) summarises whether the rule is healthy (1-5 triggers per 4-year cycle), too sensitive (>5) or too restrictive (<1).
Key zones
The most useful alerts combine indicators from different categories: a valuation indicator (MVRV, NUPL) + a cycle indicator (Pi Cycle, Mayer) + a sentiment indicator (reserve risk, STH-SOPR). Triple confirmation drastically reduces false positives. Default thresholds proposed by the tool are calibrated on each metric's historical extremes, offering a reliable starting point for customisation.
What to observe
Test your alerts on historical data (backtest) before activating them. The tool includes a simulator that replays the last 10 years of data and shows when your alerts would have triggered. If an alert fires more than 5 times per year, thresholds are probably too sensitive. If it never fires in 10 years, thresholds may be too restrictive. Aim for 1-3 triggers per cycle for a quality indicator.
Historical context
On-chain alert systems were historically reserved for institutions using professional APIs (>$500/month). Trinity's no-code approach democratises this capability by allowing any user to build alerts as sophisticated as those of quantitative desks, without writing a single line of code. The idea is inspired by automation tools like Zapier, applied to on-chain analysis.
Expert notes
this phase delivers the designer + backtest entirely client-side (rules persist in browser localStorage). Live continuous monitoring with email / PWA push notifications is not yet available. Beware of overfitting: building an alert that perfectly captures the last 3 tops does not guarantee it will capture the next - the historical sample is tiny. Aim for 1-3 triggers per cycle for a quality indicator rather than an ultra-precise rule.
Common mistakes to avoid
Creating dozens of alerts with different thresholds 'to miss nothing' is counterproductive - it creates noise and alert fatigue. Fewer, better-calibrated alerts are always worth more than excess. Also, a triggered alert is NOT an indication for immediate action - it is an invitation to deepen analysis. The best analysts use alerts to know when to look, not when to act.
Programmatic access
REST API
curl -sS \
'https://api.trinityinsights.io/api/v1/onchain/metrics/on-chain-alert-builder/data?timeframe=90d' \
-H 'X-API-Key: $TRINITY_API_KEY'MCP server
{
"tool": "get_chart_value",
"metric_id": "on-chain-alert-builder",
"timeframe": "1y"
}Required tier: performance. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.
Related metrics
Institutional disclaimer
Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.