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.

Sign up for GitHub

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

Jump to bottom

find changed v3 pools should be based on last sync #907

Open
franzns opened this issue Sep 6, 2024 · 0 comments
Open

find changed v3 pools should be based on last sync #907

franzns opened this issue Sep 6, 2024 · 0 comments
Assignees
@franzns

Comments

@franzns
Copy link
Collaborator

franzns commented Sep 6, 2024 •
edited
Loading

Currently to find the changed v3 pools we use the block number in dynamic data but it should use a dedicated entry in the PrismaLastBlockSyncedCategory table, similar to how COW and v2 pools are synced.
@franzns franzns closed this as completed Sep 6, 2024
@franzns franzns reopened this Sep 6, 2024
@franzns franzns changed the title find changed cow pools should be based on last sync find changed v3 pools should be based on last sync Sep 6, 2024
@franzns franzns self-assigned this Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@franzns franzns

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@franzns