Dennis Verstappen
2025-09-02

Avalanche Indexing with The Neighborhood

Avalanche is home to a growing set of high-performance L1s, each optimized for its own community and use case. This design opens the door to faster innovation but also creates a challenge: how can builders and product teams access clean, reliable data across all these L1s without maintaining custom infrastructure for each one?

The Indexing Company built The Neighborhood, a distributed compute network for high-performance indexing. The Neighborhood can onboard any Avalanche L1 into its network and provide pipelines that span multiple L1s at once. This makes it possible to stream real-time activity from several chains into a single schema, while also running complete historical backfills from genesis.

Solving the Indexing Problem on Avalanche

Today, many teams rely on brittle systems like subgraphs or centralized APIs. These approaches come with rigid schemas, long reindexing times, and high infrastructure costs. They are especially limiting in a multi-chain ecosystem like Avalanche, where each L1 may introduce its own set of contracts and events.

The Neighborhood removes these bottlenecks. By ingesting raw block data directly from Avalanche RPCs, it lets developers apply programmable transformations in JavaScript and stream structured output into any database, warehouse, or webhook. The result is flexible, chain-aware pipelines that can handle multiple L1s side by side.

Examples of Avalanche Data You Can Index

Here are some of the datasets teams can build pipelines for today:

Token transfers: Track ERC20 and stablecoin movements such as AVAX, USDC, and USDT across several Avalanche L1s.
DEX activity: Capture swaps and liquidity events from protocols including Dexalot, Blackhole, LFJ, and Uniswap deployments.
Lending and borrowing: Stream deposits, borrows, repayments, and liquidations from Avalanche-native money markets.
NFT activity: Index NFT transfers, mints, and marketplace events to power dashboards or wallets.
Wallet-level analytics: Monitor balances, positions, and historical activity for specific addresses.
Custom contracts: Add your own L1 contracts and decode events specific to your application.

By combining these pipelines, developers can merge data from multiple Avalanche L1s into a single dataset—removing the complexity of stitching together siloed sources.

Benefits for Builders

Programmable pipelines

Developers define what gets indexed, from specific contracts to wallet sets. Pipelines can be adjusted on the fly without costly reindexing.

Real-time and historical coverage

Support for both sub-second data streams and full historical backfills ensures complete datasets for analytics, compliance, and research.

Local indexing options

Neighborhood nodes can run close to Avalanche validators or inside your own infrastructure, delivering lower latency and giving teams full control over reliability and security.

Cost and efficiency

The distributed design of The Neighborhood processes Avalanche workloads more efficiently than centralized cloud systems, reducing costs for data-heavy use cases like DeFi analytics or AI model training.

Why This Matters for Avalanche

Avalanche’s multi-L1 ecosystem is only going to grow. Without robust indexing, developers risk spending more time maintaining ETL pipelines than building products. The Neighborhood provides a unified data layer that adapts as new L1s launch, allowing product managers to ship faster, CTOs to cut costs, and data engineers to focus on insights instead of infrastructure.

Getting Started

The Neighborhood already supports Avalanche and its expanding family of L1s. Developers can define pipelines through our console and APIs, stream data into Postgres, BigQuery, Kafka, or webhooks, and build analytics that span multiple chains. For teams building on Avalanche, The Neighborhood makes it possible to go from raw chain data to production-ready pipelines—whether you’re indexing a single L1 or unifying activity across the entire Avalanche ecosystem.