Skip to content

fix(juice): align positionV2 query with renamed stablecoinAddress field#3875

Merged
davidleomay merged 1 commit into
developfrom
fix/juice-positionv2-stablecoin-address
Jun 12, 2026
Merged

fix(juice): align positionV2 query with renamed stablecoinAddress field#3875
davidleomay merged 1 commit into
developfrom
fix/juice-positionv2-stablecoin-address

Conversation

@davidleomay

Copy link
Copy Markdown
Member

Problem

JuiceService.processLogInfo fails every cycle with GRAPHQL_VALIDATION_FAILED: the positionV2 query requests the field jusd, which the juicedollar ponder schema renamed to stablecoinAddress when it was generalized for multi-stablecoin support. Verified via introspection against both deployed ponders (jdm + jdt): no jusd field, stablecoinAddress present, all other queried fields unchanged.

Fix

Rename the field in the graph query and JuicePositionGraphDto. The public JuicePositionDto keeps its jusd key (address of the stablecoin contract), so API consumers are unaffected.

Verification

  • Introspected both ponder schemas: stablecoinAddress confirmed
  • ~4 errors/40min on dfxdev disappear once deployed

The juicedollar ponder schema generalized the position's stablecoin
contract field from jusd to stablecoinAddress (multi-stablecoin support),
so getPositionV2s failed with GRAPHQL_VALIDATION_FAILED on every
processLogInfo cycle. The public JuicePositionDto keeps the jusd key, only
the graph query and graph DTO are renamed.
@davidleomay davidleomay merged commit bd3c4b5 into develop Jun 12, 2026
7 checks passed
@davidleomay davidleomay deleted the fix/juice-positionv2-stablecoin-address branch June 12, 2026 09:50
davidleomay added a commit that referenced this pull request Jun 12, 2026
Second schema rename in the generalized juicedollar ponder (after
stablecoinAddress, #3875): the equity entity jUICE is now poolShare,
same fields (id, profits, loss, reserve) and still keyed by the
stablecoin address, verified against both deployed ponders.
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.

2 participants