graphprotocol / graphprotocol/indexer

Feat: support specifying more Gateways to indexer config

Open
#837 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
262
Forks
148
No merged PRs in 30d

Description

As work towards launching more gateways in the near future is ongoing we will need to either:

  • document how indexers are expected to accept receipts from multiple gateway - in the event an indexer is expected to run multiple indexer stacks for each gateway they accept receipts from

  • update indexer-agent cli option --collect-receipts-endpoint or --gateway-endpoint to support multiple endpoints

  • update indexer-service cli option --client-signer-address to support passing multiple gateway addresses

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the CLI definitions for indexer-agent's --collect-receipts-endpoint and --gateway-endpoint, plus indexer-service's --client-signer-address. Determine with maintainers which of the three alternatives is intended, then trace how the selected value reaches gateway and receipt configuration. Done means the chosen multi-gateway behavior is implemented and documented with coverage for multiple endpoints or addresses.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.