Send current exchange-rate requests without a device timestamp

[peachbits]

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Requirements

No visual changes to the GUI — this touches the exchange-rate request logic only — so the device-testing checklist below does not apply.

• Tested on iOS device
• Tested on Android device
• Tested on small-screen device (iPod Touch)
• Tested on large-screen device (tablet)

Description

Symptom: wallets render correct crypto balances but $0.00 fiat — the same signature as the Cardano report in the ticket.

Verbose exchange-rate logging from an affected device (4.50.2, Android) shows every current rate returning no rate while historical rates resolve:

rates query 0 result: 13 resolved, 16 no-rate:
  base_USD@2026-08-13T13:04:43.935Z, bitcoin_USD@…, monero_USD@…,
  cardano_USD@…, USD_USD@2026-08-13T13:04:43.935Z

The 16 no-rate pairs are exactly the current-timestamp ones; the cache then stores current: 0, so fiat = amount × 0 = $0.00.

Root cause: convertToRatesParams stamped "current" pairs with the device clock (new Date()). The rates server returns no rate for a timestamp more than ~2 minutes in the future, and this device's clock runs ~2 minutes fast (its log uploads show the device UTC ahead of the server date header), so every current request landed right on the server's future cutoff.

Replaying the device's verbatim request against rates3/rates4.edge.app/v3/rates confirmed it: past / now / +1m resolve; +2m and beyond return null. With isoDate omitted, the server uses its own clock and returns the latest rate.

Fix: omit isoDate for current pairs so the server timestamps them; historical pairs keep their explicit date. Immune to device clock skew, with no behavior change when the clock is correct. Adds a convertToRatesParams regression test (current → no isoDate; historical → date preserved).

Verified: tsc, eslint, and the ExchangeRateActions jest suite (6/6) pass.

---

Note

Medium Risk
Changes how all current rate queries are built for the rates server; incorrect behavior would affect fiat display app-wide, but the change is narrow and covered by a targeted test.

Overview
Fixes wallets showing correct crypto balances but $0.00 fiat when the device clock is slightly fast. Current rate pairs used to get isoDate from new Date() in convertToRatesParams; the rates server rejects timestamps too far in the future and returns no rate, so the cache stored current: 0.

convertToRatesParams now leaves isoDate undefined for pairs with no historical date (crypto and fiat), so the server timestamps with its own clock. Pairs with an explicit isoDate still send that date for historical lookups.

Also exports convertToRatesParams for tests and adds a regression test that current pairs omit isoDate on the wire while historical pairs keep it. CHANGELOG updated.

^{Reviewed by Cursor Bugbot for commit 1c64ca1. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1216779213469798