substreams

This bot follows StreamingFast's agentic Substreams workflow: the substreams.dev registry, the streamingfast/substreams-skills packs, and thegraph.market Portal API for usage and hosted sinks.

StreamingFast substreams-skills v1.6.0 is the skill pack to follow (11 packs: core chains, convert, sinks, testing, thegraph-market-api). Clone or read https://github.com/streamingfast/substreams-skills rather than relying on a local workspace copy.

Each user authenticates themselves: run substreams auth against The Graph Market to mint their own data-plane JWT. Never copy, print, or ship another user's token or .substreams.env. Graph Market keys can cap concurrent streams, so serialize live substreams run jobs. Polygon's canonical Substreams network id is matic (polygon as an endpoint name may also work).

If available, The Graph subgraph registry and subgraph GraphQL connectors can be used alongside Substreams. They are custom MCP connections and are not bundled with this template.

Use this for cross-cutting Substreams development: manifests, module graphs (map/store/index), protobuf, performance, and debugging. For EVM decoding use substreams-ethereum; for Solana use substreams-solana; for SQL sinks use substreams-sql.

Use this when building EVM Substreams: ABI codegen, event decoding, ERC-20/721/1155, Uniswap/DEX pools, topic0, Solidity, or any EVM chain (Polygon, Arbitrum, Base, BSC, Optimism). Always decode logs into typed protobuf objects, one message type per event.

Use this when building Solana Substreams: walk_instructions, program/account filters, SPL Token, Anchor discriminators, IDL parsing, Raydium, or Pump.fun. Always decode instructions into typed protobuf objects, one message type per instruction.

Use this when working with Bitcoin Substreams, UTXO model, transaction parsing, address extraction, or Esplora API compatibility.

Use this when migrating a subgraph (The Graph) or a Solana program/contract into a Substreams module pipeline.

Use this when building SQL database sinks from Substreams: PostgreSQL vs ClickHouse, Database Changes vs From-proto, primary keys, delta updates, and schema evolution.

Use this when building custom Substreams sinks or integrating Substreams output into Go, JavaScript, Python, or Rust applications.

Use this when the user wants to run a Substreams sink themselves on their own infra: Postgres, ClickHouse, files, PubSub, or webhook. For StreamingFast-hosted sinks use substreams-hosted-sink.

Use this when the user wants StreamingFast to host a Substreams sink via the Portal API HostedService (Postgres or ClickHouse). Before any first deploy, stop and offer a substreams run output-quality check.

Use this when testing Substreams: unit tests with substreams::testing (map!, clock), real block fixtures via firecore, CLI integration (substreams run, --test-file), performance checks, or CI.

Use this to authenticate to The Graph Market (StreamingFast Portal) and call billing, usage, live-load, and hosted-deployment APIs. Covers device-code login, plan/usage questions, sink status, deploy, scale, and undeploy.