perp-fees: fix GMX Subsquid schema + edgeX depth level - #1622
Merged
Conversation
GMX: Subsquid removed positionFeeFactor field; query was 400ing on every tick. Remove the dropped field and its Go fallback. edgeX: depth endpoint only accepts level=15 or 200, not 100. The invalid level returned empty_orderbook on every tick.
Flotapponnier
added a commit
that referenced
this pull request
Jul 28, 2026
* perp-fees: delete gauges on asset_not_found (Lighter ghost metrics) (#1621) * perp-fees: delete gauges on asset_not_found to prevent ghost metrics * add mayan/squid/socket/across to provider registry and logo manifest * perp-fees: fix GMX subsquid schema + edgeX depth level (#1622) GMX: Subsquid removed positionFeeFactor field; query was 400ing on every tick. Remove the dropped field and its Go fallback. edgeX: depth endpoint only accepts level=15 or 200, not 100. The invalid level returned empty_orderbook on every tick.
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
1 participant
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.
Problems found
Two venues have been failing silently for an unknown number of days:
GMX v2 — Subsquid schema change
The Subsquid
gmx-synthetics-arbitrumsubgraph removed thepositionFeeFactorfield. Every tick logs:The query still requested
positionFeeFactorForNegativeImpact(which works) andpositionFeeFactoras a fallback (removed). GraphQL rejects the entire query if any field is invalid.Fix: remove
positionFeeFactorfrom the query and its Go fallback branch.edgeX — invalid depth level
The
getDepthendpoint only acceptslevel=15orlevel=200. The harness was requestinglevel=100, which returned:{"code":"INVALID_DEPTH_LEVEL","data":null}This parsed as
data:[]→empty_orderbookerror on every tick.Fix: switch to
level=200(200 levels, more depth than before).Verification
Both APIs tested live before this PR:
level=200→ SUCCESS with 80+ bid/ask levels for ETHpositionFeeFactorfield should return valid fee factorDeploy
After merging → main, rebuild and restart
perp-feeson VPS: