List view

• Indexer Experience

  Work to improve the user experience across the `indexer` repository

  No due date

  •10/32 issues closed
  31% complete22 open10 closed

• Contributor Experience

  Work to improve the contributor experience across the `indexer` repository

  No due date

  •2/8 issues closed
  25% complete6 open2 closed

• Multi-network optimizations

  Post-mvp features and enhancements to the multi-network support.

  Overdue by 1 year(s)

  •

  Due by August 31, 2023

  •6/10 issues closed
  60% complete4 open6 closed

• Multiple Chain Operation

  To support smooth subgraph deployment migrations from the L1 network to the L2 network the `indexer-agent` will need to be able to operate for both an L1 and L2 indexer accounts but use a single, shared graph-node backend. #### Open Questions - Do we need to any changes to indexer-service? Might not need to make changes; there will need to be an indexer-service running for each network. - Do we want to support an arbitrary number of uniquely uniform networks, or do we want to be specific about L1/L2 chain pairs?

  No due date

  •4/4 issues closed
  100% complete0 open4 closed