Skip to content

perp-fees: ghost metric guard + GMX schema + edgeX level fix - #1623

Merged
Flotapponnier merged 2 commits into
mainfrom
hotfix/perp-fees-fixes-main
Jul 28, 2026
Merged

perp-fees: ghost metric guard + GMX schema + edgeX level fix#1623
Flotapponnier merged 2 commits into
mainfrom
hotfix/perp-fees-fixes-main

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Cherry-picks of #1621 + #1622 to main.

3 harness fixes found via full audit of all perp-fees venues:

  1. Ghost metric guard (perp-fees: delete gauges on asset_not_found (Lighter ghost metrics) #1621): asset_not_found now deletes gauge series instead of carrying the stale last value indefinitely. Defensive fix for future venue delistings.

  2. GMX Subsquid schema (perp-fees: fix GMX Subsquid schema + edgeX depth level #1622): Subsquid removed positionFeeFactor field — query was 400ing on every tick. Removed the dropped field; positionFeeFactorForNegativeImpact still valid.

  3. edgeX depth level (perp-fees: fix GMX Subsquid schema + edgeX depth level #1622): level=100 is invalid (API accepts 15 or 200 only) — every tick returned empty_orderbook. Switched to level=200.

After merge: rebuild perp-fees on VPS

ssh rescue@57.130.61.201 -p 8822
cd /opt/ocb && docker compose build perp-fees && docker compose up -d perp-fees

…1621)

* perp-fees: delete gauges on asset_not_found to prevent ghost metrics

* add mayan/squid/socket/across to provider registry and logo manifest
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
Flotapponnier merged commit 0dfbb02 into main Jul 28, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant