> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://ensforge.com/api/mcp` to find what you need.

# Upgrade to 0.3

Version 0.3.0 adds indexer-backed discovery to Core, SDK, and React. Existing on-chain reads and
writes do not need to move to the indexer. Upgrade your installed ensforge packages together;
there is no required action-call rewrite for applications that do not use the new discovery APIs.

## Keep indexed and on-chain reads distinct

Use the indexer for lists, search, relationships, and history. Keep on-chain actions for current
record values and transaction confirmation. An indexer can lag behind a successful write.

Core's indexer actions are available through `@ensforge/core/indexer`; SDK applications use the
`sdk.indexer` group. The transport and generated operations ship with ensforge, so you do not need
to install a GraphQL client just to use these actions.

See [getIndexerStatus](/sdk/api/indexer/get-indexer-status) before relying on a source, and inspect
the source status returned by discovery actions when results are partial or unavailable.

## Handle pagination and source configuration

Treat returned cursors as opaque values and pass them back with the same query parameters. Avoid
constructing cursors from offsets or mixing them between filters, sources, or deployments.

If you override indexer endpoints, check their schema and authentication configuration. A valid
RPC URL is not an indexer endpoint. Use the built-in source configuration when it matches your
deployment rather than retaining a copied staging URL indefinitely.

## Wagmi compatibility

This release supports Wagmi 2.19 and 3.x, including applications using RainbowKit. Keep your chosen
Wagmi version compatible with the rest of your wallet UI dependencies; upgrading ensforge does
not require changing that UI stack.

Version 0.3.1 only changes repository metadata and release provenance. There are no additional
application migration steps for that patch.