daomasons / gs-voting-envio

Envio Blank Template

Please refer to the documentation website for a thorough guide on all Envio indexer features

gs-voting-envio's Issues

gs-envio

Create an Envio Indexer for all of Grant Ships

Why

• Faster
• Easier to iterate with
• Easier to debug
• More flexible
• Can add more features and hooks
• Multichain
• Easier to maintain

What

break into tickets as issues in the gs-envio repo once created.

• Create Envio repo, Scaffold (Do not autogenerate), and push code to repo
• Port over config.yaml
• Handlers for Allo, Registry
• Handlers fro GameManager Factory
• Handlers for GameManager
• Sunset gs-voting-envio and combine schema, config, handlers, and utils into new repo
• Sunset references to gs-envio in app
• Fix TXContext so that it only queries a single envio indexer

Key Changes

• Floating Game Manager Address
  • We do not index a single Game Manager. Instead the factory will be the source of truth
• ID rework
  • Unique ID for all game managers. I should be able to plug in a game-manager address into an env-variable and load an entirely new round
  • Unique ID Scoping for all Ships. These ships should be scoped to the round and should not display in other rounds
  • Unique ID Scoping for all Grants
  • Unique ID Scoping for all Feed Items
  • Unique ID Scoping for all items in the dashboards.
  • Everything should be 'game-round' specific besides Project profiles, which should easily port from one round to the other (so long as they are on the same chain)
• Scoped changes should be capable of presenting a 'historical view' of the app.
• Feed items create a link, so we users can click the item and view it in the app.
• Profile members should be able to see their projects in 'My Projects'

Related Tickets:

• DAOmasons/grant-ships-app#107
• DAOmasons/grant-ships-app#34
• DAOmasons/grant-ships-app#94
• DAOmasons/grantships-subgraph#3