Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gs-envio #6

Open
8 tasks done
jordanlesich opened this issue Jul 9, 2024 · 0 comments
Open
8 tasks done

gs-envio #6

jordanlesich opened this issue Jul 9, 2024 · 0 comments
Assignees

Comments

@jordanlesich
Copy link
Contributor

jordanlesich commented Jul 9, 2024

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:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant