Skip to content

fix: recalibrate financeLogPairIds toScrypt CHF#3351

Merged
TaprootFreak merged 1 commit intodevelopfrom
fix/recalibrate-scrypt-chf-pair-ids
Mar 5, 2026
Merged

fix: recalibrate financeLogPairIds toScrypt CHF#3351
TaprootFreak merged 1 commit intodevelopfrom
fix/recalibrate-scrypt-chf-pair-ids

Conversation

@TaprootFreak
Copy link
Copy Markdown
Collaborator

Summary

  • Recalibrate financeLogPairIds.toScrypt.chf to eliminate 40k CHF phantom pending on Yapeal/CHF (Asset 404)
  • BankTx 190079 (40k CHF) has no matching ExchangeTx deposit at Scrypt due to a manual entry, causing a 1:1 mapping shift
  • Sets bankTxId = 190080 and exchangeTxId = 123646 so unfiltered Sender = Receiver = 1'370'000 CHF → toScrypt = 0

Test plan

  • Run migration on staging
  • Verify via ./scripts/db-debug.sh --balance that toScrypt on Yapeal/CHF is 0
  • Check that no other pair IDs are affected

BankTx 190079 (40k CHF) has no matching ExchangeTx deposit at Scrypt
due to a manual entry, shifting the 1:1 mapping. In unfiltered mode
23 senders (40k) vs 22 receivers (40k) causes +40k CHF phantom pending
on Yapeal/CHF (Asset 404).

Set toScrypt.chf pair IDs to a balanced starting point:
- bankTxId: 186482 → 190080
- exchangeTxId: 116514 → 123646

After recalibration: Sender = Receiver = 1'370'000 CHF → toScrypt = 0
@TaprootFreak TaprootFreak marked this pull request as ready for review March 4, 2026 18:33
@TaprootFreak TaprootFreak merged commit df0fae3 into develop Mar 5, 2026
8 checks passed
@TaprootFreak TaprootFreak deleted the fix/recalibrate-scrypt-chf-pair-ids branch March 5, 2026 13:14
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