feat(reserve-analysis): add burn/refund holder table generator - #63
Open
thalescb wants to merge 1 commit into
Open
feat(reserve-analysis): add burn/refund holder table generator#63thalescb wants to merge 1 commit into
thalescb wants to merge 1 commit into
Conversation
Generates the candidate table (current G$ held, G$ acquired, USD paid, remark) used for the burn/refund review. Current-held is a live balanceOf via public RPC. Acquired/USD paid fetch from Dune query 8656320 via Dune's REST API (same pattern as projects/dashboard-scripts), with a manual CSV export or a hardcoded snapshot as fallbacks. Auto-tags remarks from wallet-outflow-trace-out.json when present.
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
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.
Generates the burn/refund candidate table (current G$ held, G$ acquired, USD paid, remark) used in the ongoing reserve incident review.
Validated: fallback path runs end-to-end against live RPC. Dune API request/response handling (both the quick-fetch and the execute-and-poll paths) verified against mocked responses matching Dune's documented API shape; a live run with a real API key is the next step.