Scout in 60 seconds
Describe what matters onchain. Scout checks whether it can monitor it, and tells you if anything is missing.
1. Describe what you want watched
Write the activity and conditions you care about in your own words.
2. Scout understands the request
Scout separates the activity, chain, tokens, wallets and conditions. Understanding a request does not mean it can run yet.
3. Scout checks what it needs
It checks which blockchain data and monitoring tools are needed, using its current capability registry.
4. If information is missing, Scout asks
A useful question helps confirm your intended scope. Scout keeps your requested conditions intact.
5. If a capability is unavailable, Scout tells you
You can see what is available and exactly which part is missing. The Watch stays inactive.
6. Scout builds and verifies the Watch
When the required capabilities are available, Scout prepares the data and tests the monitoring rules. A plan alone cannot activate a Watch.
7. Once ready, Scout monitors live activity
Scout follows finalized chain activity and records matches. Your configured delivery settings determine where alerts are sent.
What Scout can monitor now
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.
- Intent Resolver
- WatchProgram
- Capability Planner
- Data Adapter / Substreams
- Normalized Events
- Generic Runtime
- Investigation
- Decision
- Delivery
Watch details retain the capability plan, selected packages, modules, pipeline strategy, verification and historical evidence. General arbitrary pipeline generation is not currently implemented.