@@ -12,6 +12,10 @@ should be able to answer, without decoding contract data:
1212An alert links to the exact case whose transition triggered it, not just the
1313PINGME landing page.
1414
15+ The heading keeps the compact ` sequencer · case status ` form. The body states
16+ the event, full sequencer address, relevant slot, epoch or round, UTC
17+ observation time, and reason provenance without repeating explanatory prose.
18+
1519## Claims allowed at each stage
1620
1721| Stage | What the alert may claim |
@@ -35,29 +39,32 @@ action” and “predicted payload address.”
3539L1 votes contain no offense type. Alerts may attach a reason only as separately
3640labelled node evidence matched by address and exact target epoch or slot:
3741
38- > Candidate 2,000 AZTEC slash becomes executable in 2d 4h. This node observed
39- > inactivity in target epoch 123.
42+ > Event: Quorum reached for a 2,000 AZTEC slash
43+ >
44+ > Epoch: 123
45+ >
46+ > Reason: Inactivity (node evidence)
4047
4148They must not say:
4249
4350> L1 confirmed a 2,000 AZTEC inactivity slash.
4451
4552If several local offenses match the same L1 action, list them rather than
46- choosing one. If no evidence matches, say “reason unknown on L1.” An approximate
47- timestamp match is insufficient.
53+ choosing one. If no evidence matches, say ` Reason: Not encoded on L1` . An
54+ approximate timestamp match is insufficient.
4855
4956## Required context
5057
5158Every alert includes:
5259
5360- watched sequencer address;
54- - case stage and previous stage ;
55- - exact slot, epoch, target epoch, or slashing round as applicable;
56- - source ( ` this Aztec node ` , ` Sentinel ` , or ` Ethereum L1 ` ) ;
57- - source observation time; current freshness is shown when the case opens ;
61+ - current case status in the heading ;
62+ - exact slot, epoch, or slashing round as applicable;
63+ - UTC observation time ;
64+ - reason and its node-evidence provenance, or that no reason is encoded on L1 ;
5865- actual AZTEC amount or candidate AZTEC amount, explicitly distinguished;
5966- the next transition and countdown, when deterministic; and
60- - the exact slashveto.me case URL.
67+ - for Telegram, the exact slashveto.me case URL.
6168
6269Stage-specific evidence is:
6370
@@ -70,9 +77,9 @@ Stage-specific evidence is:
7077| Execution / slash | transaction, round, deployed payload, requested action, canonical ` Slashed ` amount, and post-slash/ejection state when known |
7178| Reorg / correction | orphaned block or transaction and the case state that replaced it |
7279
73- Telegram may add Dashtec links for affected sequencers and Etherscan links for
74- the exact network transaction, block, or predicted/deployed address . Web Push
75- opens the same exact case.
80+ Telegram includes the exact case link, a Dashtec sequencer link, and an
81+ Etherscan transaction link when a transaction hash exists . Web Push contains no
82+ links in its copy and opens the exact case when selected .
7683
7784## Alert transitions and noise control
7885
@@ -81,7 +88,8 @@ Alert on meaningful path changes, not every poll:
8188- first missed duty in an epoch;
8289- newly qualifying inactive epoch or changed streak progress;
8390- offense registration or safe withdrawal;
84- - first L1 mention and relevant vote/penalty threshold crossings;
91+ - first L1 vote and slash quorum; intermediate ballot counts update the case
92+ without sending alerts;
8593- candidate addition, removal, amount change, or address change;
8694- round close, execution start, veto, materially changed pause protection, or
8795 expiry;
0 commit comments