What does Substreams do for Scout?
Substreams gives Scout fast access to structured blockchain activity. Scout can reuse existing Substreams packages instead of writing a new indexer for every Watch.
- Your request
- Scout understands it
- Data source
- Monitoring rules
- Verified live Watch
Historical processing
Substreams can process historical block ranges in parallel. Scout uses earlier activity to test the data before activation. Testing a range does not prove complete wallet history.
Live streaming
The same data pipeline can continue toward new finalized blocks. Scout saves its position so monitoring can recover after an interruption.
Reusable packages
A package describes reusable blockchain data processing. Scout checks whether its output provides the activity and fields your Watch needs.
Why Scout verifies it
A package name cannot prove that its data is correct for your request. Scout checks output against independent evidence and keeps a Watch inactive if verification fails.
Scout supplies the monitoring logic
Substreams supplies activity. Scout applies your conditions, checks relevant history, records findings and delivers alerts.
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.
Packages may include protobuf output types and compiled WASM modules. Scout inspects those artifacts and verifies field semantics before trusting their output.