Back to Common Questions

Common Questions / Pipelines and databases

What is a Hosted Store?

Updated

A Hosted Store is a managed, organization-scoped, block-aware key/value store that StreamingFast runs for you on The Graph Market. You put data in, and any Substreams module (or any gRPC client) reads it back at a specific block height, in sync with the stream. You operate no service and write no reorg handling.

It joins Hosted Sinks under Hosted Services. It is in beta.

How does it work?

A Hosted Store is a key → value map with blockchain semantics:

  • Keys are raw bytes: a string, an address, a hash, or a composite key.
  • Values are protobuf messages you define, tagged with their type (google.protobuf.Any).
  • Reads from a module happen at the block being processed, so lookups stay consistent during backfills.

The store versions data by block, so a lookup during a historical run returns what was true at that block, not only the latest value. Only your organization can access it.

How do I fill it?

Substreams feedRemote feed
SourceA Substreams package writing key/value entries from chain dataYour own service, pushing over gRPC
Best forData derived from the chain (token metadata, pool registries)Off-chain or application-owned data (prices, allowlists)
ReorgsHandled, because Substreams is the sourceData you push is treated as final

With a remote feed you write entries with Feed.Set, delete with Feed.Delete, and flip the store live with Feed.SetReady.

What is it good for?

Whenever a module needs reference data that is not in the block it is processing: resolving token symbol and decimals, mapping an address to its owner or protocol, checking an allowlist, attaching an off-chain price to an on-chain event, or reading a value another package already computed. See how to look up reference data in a Substreams module.

Hosted Store or Hosted Sink?

They move data in opposite directions. A Hosted Sink writes Substreams output out to your Postgres or ClickHouse database. A Hosted Store holds data you look up from inside a running pipeline. If the consumer is a dashboard or app backend, you want a sink; if a module needs reference data, you want a store.


Frequently asked questions

Is it the same as a foundational store? A module consumes it as a foundational-store input in substreams.yaml, so the two terms refer to the same lookup mechanism in the manifest.

Is it production ready? It is in beta. Check the current status before depending on it for critical workloads.


Get an API key at thegraph.market.

Related: What are Hosted Sinks? · How do I look up reference data in a Substreams module? · What is Substreams?