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

Subgraph Implementation - for Bot #17

Open
Briggs20 opened this issue Oct 25, 2022 · 2 comments
Open

Subgraph Implementation - for Bot #17

Briggs20 opened this issue Oct 25, 2022 · 2 comments
Assignees
Labels
Feature new functionality

Comments

@Briggs20
Copy link

Briggs20 commented Oct 25, 2022

  • Explore the subgraph
  • Setup local subgraph node targeted for Apothem network with the help of Zack
  • Develop subgraph that returns the positions at risk
  • Make changes in bot to fetch the positions from graph instead from chain.
@Briggs20 Briggs20 changed the title Subgraph Implementation Subgraph Implementation - for Bot Oct 28, 2022
@Briggs20 Briggs20 added this to the KERMADEC Release milestone Oct 28, 2022
@Tarunshrma
Copy link
Contributor

Tarunshrma commented Oct 28, 2022

  • Explore the subgraph
  • Setup local subgraph node targeted for Apothem network with the help of Zack
  • Develop subgraph that returns the positions at risk
  • Make changes in bot to fetch the positions from graph instead from chain.

@Tarunshrma
Copy link
Contributor

Tarunshrma commented Oct 31, 2022

Tested the subgraph, it is working as expected, however there is a problem that need to be addressed:

Bot listen event and query to graph node even before it is fully synced to latest block that leads to inconsistent data. I have tried it with hosted node. I may need to implement that polling approach to make sure graph node is fully synced upto target block before making a query.

Putting this task on HOLD to resume #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature new functionality
Projects
None yet
Development

No branches or pull requests

2 participants