القائمة
Naming conventions for tags, releases, and SPKGs in the substreams-evm monorepo. Use when creating releases, tagging versions, or publishing packages.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Instructions for building, packing, and distributing Substreams packages (.spkg) in the substreams-evm monorepo. Use when building crates, running `substreams pack`, or copying .spkg files.
Expert knowledge for consuming Substreams data in applications. Use when building sinks, real-time data pipelines, or integrating Substreams outputs into Go, JavaScript, Python, or Rust applications.
Expert knowledge for testing Substreams applications. Covers unit testing, integration testing, performance testing, and FireCode tools usage.
Expert knowledge for developing, building, and debugging Substreams projects on any blockchain. Use when working with substreams.yaml manifests, Rust modules, protobuf schemas, or blockchain data processing.
Expert knowledge for building SQL database sinks from Substreams. Covers database changes (CDC), relational mappings, PostgreSQL, ClickHouse, and materialized views.
| name | release-conventions |
| description | Naming conventions for tags, releases, and SPKGs in the substreams-evm monorepo. Use when creating releases, tagging versions, or publishing packages. |
| license | Apache-2.0 |
| compatibility | {"platforms":["claude-code","cursor","vscode","windsurf"]} |
| metadata | {"version":"1.0.0","author":"Pinax Network","documentation":"https://github.com/pinax-network/substreams-evm"} |
Naming conventions and release workflow for Pinax substreams-* monorepos.
https://github.com/pinax-network/substreams-<chain>/releases/download/<chain>-<type>-v<version>/<chain>-clickhouse-<type>-v<version>.spkg
Examples:
https://github.com/pinax-network/substreams-evm/releases/download/evm-contracts-v0.4.0/evm-clickhouse-contracts-v0.4.0.spkghttps://github.com/pinax-network/substreams-evm/releases/download/evm-balances-v0.3.3/evm-clickhouse-balances-v0.3.3.spkghttps://github.com/pinax-network/substreams-svm/releases/download/svm-dex-v0.2.5/svm-clickhouse-dex-v0.2.5.spkg<chain>-<type>-v<version>
Examples: evm-contracts-v0.4.0, evm-dex-v0.4.0, svm-dex-v0.2.5
<chain>-<type> v<version>
Examples: evm-contracts v0.4.0, evm-dex v0.4.0
Each crate produces up to 3 SPKGs. All share the same version number.
| Type | Pattern | Example |
|---|---|---|
| Base DB module | <chain>-<type>-v<version>.spkg | evm-contracts-v0.4.0.spkg |
| ClickHouse sink | <chain>-clickhouse-<type>-v<version>.spkg | evm-clickhouse-contracts-v0.4.0.spkg |
| PostgreSQL sink | <chain>-postgres-<type>-v<version>.spkg | evm-postgres-contracts-v0.4.0.spkg |
Key: Chain prefix comes first, then engine (
clickhouse/postgres), then type.
| Type | Pattern | Example |
|---|---|---|
| Base DB module | <chain>_<type> | evm_contracts |
| ClickHouse sink | <chain>_clickhouse_<type> | evm_clickhouse_contracts |
| PostgreSQL sink | <chain>_postgres_<type> | evm_postgres_contracts |
SPKGs must be placed in two locations:
./spkg/ folder in the repo (so downstream modules can import them)substreams.yaml files (base, clickhouse, postgres)substreams.yaml to reference the new base spkg versioncargo build --target wasm32-unknown-unknown --release -p <crate>substreams pack in the base, clickhouse, and postgres directories./spkg/ (with correct naming) and remove old versionsgit tag -a <chain>-<type>-v<version> -m "<chain>-<type> v<version>"All 3 SPKGs for a given crate (base, clickhouse, postgres) must share the same version.
evm-<type>/ # DB module (contains everything)
├── substreams.yaml # Base DB module
├── src/lib.rs
├── Cargo.toml
├── clickhouse/
│ ├── substreams.yaml # ClickHouse sink (imports base spkg)
│ ├── schema.sql
│ └── Makefile
└── postgres/
├── substreams.yaml # PostgreSQL sink (imports base spkg)
├── schema.sql
└── Makefile