Scout documentation

What is a capability?

A capability is something Scout knows how to observe or evaluate.

Data capabilities

These provide blockchain activity, such as reading a protocol’s swaps. Support can differ between protocol versions and chains.

Monitoring capabilities

These evaluate conditions, such as counting unique wallets in 10 minutes. A monitoring tool also needs compatible data and verification of the full Watch.

Historical capabilities

These check earlier blockchain activity, such as whether a wallet used a protocol before. Unknown history is never treated as proof that no activity happened.

What the labels mean

Ready means tested against real chain data. Available means the data or tool is installed but each Watch still needs verification. Limited means only part of the capability works. Not available yet means Scout cannot currently provide it.

Different versions, different activity

Uniswap currently has Scout’s deepest protocol support. V3 and V4 appear separately because they expose different activity. Use the live list below to see the exact scope and limitations. ERC-20 transfer support is also listed by chain and token.

What Scout can monitor now

Loading capabilities
Technical details

Internally, Scout represents the request as a typed WatchProgram and validates every required capability before activation. The Capability Planner separates data acquisition from the generic runtime. Availability is not proof of whole-program acceptance or live stream health.

  1. Intent Resolver
  2. WatchProgram
  3. Capability Planner
  4. Data Adapter / Substreams
  5. Normalized Events
  6. Generic Runtime
  7. Investigation
  8. Decision
  9. Delivery

Watch details retain the capability plan, selected packages, modules, pipeline strategy, verification and historical evidence. General arbitrary pipeline generation is not currently implemented.

Build a Watch →