Geyser registry for subgraph indexing #24
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brandoniles
reviewed
Dec 3, 2024
Member
brandoniles
left a comment
brandoniles
left a comment
There was a problem hiding this comment.
Looks simple enough.
Since there's no way to query a list of geysers, to use it you need to already have been monitoring offchain for the events. What use case do you have in mind for onchain storage if users are already off chain?
Member
Author
|
We need a on-chain factory or registry for the subgraph to automatically start to index new geysers. If not we'll have to redeploy and re-index the subgraph every time we create a new geyser. |
brandoniles
approved these changes
Dec 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Simple on-chain registry to keep track of active geysers