Index contract data with Goldsky

You want a managed indexing pipeline (subgraph-compatible or a direct data mirror) against Lumia contract data.

Who this is for: developers who want indexed contract data without running their own Graph Node. Prerequisites: a deployed, verified contract on Lumia; Networks & Endpoints.

Confirm chain support directly with Goldsky before building a pipeline against it.

Steps (confirm network support before deploying)

1

Install Goldsky's CLI and authenticate

Consult Goldsky's own current published docs for the package name, version, and login command, since that's their product, not Lumia's. Authenticating requires a Goldsky account and API key.

2

Confirm Lumia is a supported chain in Goldsky's platform

3

Deploy your subgraph manifest, if you have one

If you already have a subgraph manifest (see /build/indexers/thegraph), Goldsky's subgraph-hosting deploy step may apply. Consult Goldsky's own docs for the exact deploy command and its arguments.

4

Or configure a direct-mirror pipeline

For a direct-mirror pipeline (raw contract events/decoded logs into a database or webhook) instead of a subgraph, consult Goldsky's own docs for the pipeline definition format and how to point it at a Lumia source.

Verify it worked

Check the pipeline/subgraph status in the Goldsky dashboard, then query it for an entity or row you know exists on-chain (cross-check against the explorer) and confirm it matches.

Troubleshooting

Lumia not selectable as a source chain

This is expected until Lumia's chain registration with Goldsky is confirmed; ask Goldsky support directly.

Pipeline shows synced but data looks incomplete

Check the configured start block against when your contract was actually deployed.