Watchtower
What Watchtower monitors, which events it can watch, and who can use it.
Watchtower is the AGENTEX monitoring agent. A monitor pins one Watchtower version and scans consecutive windows of blocks on one EVM network for the events you declare. Every event it reports carries evidence and explicit coverage, just like a research report.
Use Watchtower when you need to know when something happens, such as a large transfer, a new approval or an ownership change, rather than the state of a contract at one moment.
Networks and accounts#
| Networks watched | Ethereum, Base and Robinhood Chain |
| Paid in | ETH on Robinhood Chain, prepaid from your AGENTEX balance |
| Accounts | EVM accounts only |
Solana is not monitored by Watchtower.
What it can watch#
A monitor has one to eight rules. The current Watchtower version (0.3.0) offers:
| Rule | Fires on |
|---|---|
| Token transfers | ERC-20 Transfer events from one token, optionally filtered by sender, recipient and a minimum amount. |
| Approvals by an owner | ERC-20 Approval events by one owner on one token, optionally for one spender. |
| Proxy or ownership change | Upgraded, AdminChanged, BeaconUpgraded and OwnershipTransferred emitted by a contract. |
| Wallet token movements | ERC-20 transfers into or out of one wallet across one to eight named tokens, with an optional minimum. |
| Pool swaps and liquidity | Swap, Mint and Burn on one Uniswap V2-compatible, Uniswap V3-compatible or Aerodrome pool, with optional minimum amounts. |
| Governance and timelock | OpenZeppelin Governor and TimelockController events (proposals created, queued, executed or cancelled; operations scheduled and executed; delay changes) and Compound timelock events. |
| Roles and pause | AccessControl RoleGranted, RoleRevoked and RoleAdminChanged (well-known roles are named) and Pausable Paused and Unpaused. |
Every event is re-checked locally against the exact event layout before it is reported; provider filters are never trusted on their own.
What it cannot watch#
Watching liquidity thresholds, any interaction with a wallet or contract, and native ETH transfers needs pool, transaction or trace indexes that are not connected. Watchtower refuses those rules with an explicit reason instead of reporting a quiet window.
How a window works#
Each window scans a bounded range of blocks up to the latest block confirmed by the network, for every rule. The report states its coverage:
| Coverage | Meaning |
|---|---|
| Complete | Every rule was read through the end of the window. No events means no matching log was returned for those filters. |
| Partial | The window's log cap was reached. Only whole blocks before the cap are examined; later blocks are listed as unknown and scanned again. |
| Unavailable | A provider error, rate limit or reorganisation stopped the scan. The window makes no claim about activity and is retried. |
If the chain reorganises after a window, the affected events are retracted and the window is scanned again. Blocks are never skipped silently.
Next: Create a monitor.