on Injective

In this guide, you'll learn how to initialize a Injective-based Substreams project within the Dev Container.

If you prefer to begin locally within your terminal rather than through the Dev Container (VS Code required), refer to the Substreams CLI installation guide.

Prerequisites

• Docker and VS Code installed and up-to-date.

• Visit the Getting Started Guide to initialize your Dev Container.

Step 1: Initialize Your Injective Substreams Project

1. Open the Dev Container and follow the on-screen steps to initialize your project.

2. Running substreams init will give you the option to choose between three Injective project options. Select the one that best fits your requirements:

   • Injective EVM: Navigate to the substreams init EVM path to access Injective-specific EVM data. Supports Extended Blocks.

   • Injective-minimal: Creates a simple Substreams that extracts raw Injective block data and generates corresponding Rust code. This path will start you with the full raw block, you can navigate to the substreams.yaml (the manifest) to modify the input.

   • Injective-events: Creates a Substreams that extracts Injective events using the cached Injective Foundational Module, filtered by one or more smart contract addresses. This includes type wasm events.

Tip: Have the start block of your transaction or specific events ready.

Step 2: Visualize the Data

1. Run substreams auth to create your account and generate an authentication token (JWT), then pass this token back as input.

2. Now you can freely use the substreams gui to visualize and iterate on your extracted data.

Step 2.5: (Optionally) Transform the Data

Within the generated directories, modify your Substreams modules to include additional filters, aggregations, and transformations, then update the manifest accordingly. To learn more about this, visit the How-to-Guides.

Step 3: Load the Data

To make your Substreams queryable (as opposed to direct streaming), you can automatically generate a SQL sink.

SQL

1. Run substreams codegen sql and choose from either ClickHouse or Postgres to initialize the sink, producing the necessary files.

2. Run substreams build build the Substreams:SQL sink.

3. Run substreams-sink-sql to sink the data into your selected SQL DB.

Note: Run help to better navigate the development environment and check the health of containers.

Additional Resources

You may find these additional resources helpful for developing your first Injective application.

Dev Container Reference

The Dev Container Reference helps you navigate the container and its common errors.

CLI Reference

The CLI reference lets you explore all the tools available in the Substreams CLI.

Substreams Components Reference

The Components Reference dives deeper into navigating the substreams.yaml.