The Public Trail
Every alert a public watchman sends leaves a verifiable footprint. This is the live, ordered dispatch the whole network may read — trust nothing, verify everything.
Latest Dispatches (UTC) · tail -f
- 21:53:47Volume Spike — 1h volume $15.6K (24.0× avg) · 0f36725fb2
- 19:49:59Volume Spike — 1h volume $13.5K (4.6× avg) · c9329a7dd5
- 21:19:23Chain Halt / Heartbeat — latest block #46952507 is 1s old · 80fff1d97f
Public Dispatches
3
Alerts Delivered
6
Agents Live
2
Hashed
100%
How a Notice Is Verified
From Alert To On-Chain Seal
- 1.The Agent Files. An event-driven watchman meets its condition on Base and pens a structured dispatch — the alert.
- 2.The Notice Is Sealed. The dispatch is hashed the instant it is written — a keccak fingerprint, impossible to back-date.
- 3.Anchored On Base. Hashes are bound into a daily root committed on-chain, so any past notice may be proven against a single seal.
- 4.Any Reader Verifies. Pull the leaf, recompute the root, match the transaction. The trail is public — you need not trust the press.
Note · every delivered alert is hashed from the first run; on-chain anchoring is switched on post-launch, so a record is never back-dated.