Skip to content

fix: build the testnet indexer with testnet provider metadata - #123

Merged
aminsammara merged 1 commit into
mainfrom
amin/indexer-testnet-provider-metadata
Oct 26, 2026
Merged

aminsammara merged 1 commit into
mainfrom
amin/indexer-testnet-provider-metadata

Conversation

@aminsammara

Copy link
Copy Markdown
Collaborator

Problem

Providers added under providers-testnet/ (e.g. TestInc, provider 50) don't show up on the testnet staking dashboard.

The single-instance indexer deploy (#87) always runs yarn bootstrap, which aggregates the mainnet providers/ directory, even when ENV=testnet. The testnet indexer therefore serves mainnet provider names against testnet provider ids:

$ curl -s https://api.testnet.stake.aztec.network/api/providers/50 | jq -r .name
Staker Space        # mainnet provider 50; on testnet, 50 is TestInc

Fix

Run yarn bootstrap-testnet when ENV=testnet. This is the switch atp-indexer/bootstrap.sh already makes on the ECS deploy path. Prod is unchanged.

Testing

  • Locally, yarn bootstrap-testnet aggregates the 5 files in providers-testnet/, with provider 50 as TestInc.
  • The workflow YAML parses.

After merge

Redeploy the testnet indexer (Deploy Indexer, environment testnet). The metadata is baked into the image at build time.

The single-instance deploy (#87) always ran `yarn bootstrap`, which aggregates the mainnet providers/
directory, even when ENV is testnet. So the testnet indexer serves mainnet provider names against
testnet provider ids: provider 50 shows as "Staker Space" instead of TestInc, and the providers in
providers-testnet/ never appear on the testnet dashboard.

Run `yarn bootstrap-testnet` for testnet, the same switch bootstrap.sh's ECS deploy path already makes.
The testnet indexer has to be redeployed to pick this up.
@aminsammara
aminsammara requested a review from a team as a code owner October 23, 2026 09:34
@aminsammara
aminsammara merged commit 823537d into main Oct 26, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant