[Fix] Surface RWA Oracle price staleness in the web app (Stellar)

[FabianSanchezD]

Description

The RWA Oracle supports staleness configuration and returns price data that can be stale. The frontend uses the oracle for token prices and lending/borrowing (e.g. useTokenPrice.ts, lending flows). Currently the UI may not indicate when a price is stale or when actions might be restricted due to staleness. This issue is to use the oracle’s staleness/resolution information and surface it in the Stellar flows so users are informed and, if desired, actions can be gated when prices are too old.

Requirements

• Use the RWA Oracle’s price response (e.g. timestamp, resolution, or staleness info from SEP-40) in the web app when fetching prices for Stellar (e.g. in useTokenPrice and wherever oracle prices are displayed or used for lending/borrowing).
• Expose staleness (or “last updated”) in the UI where Stellar RWA prices are shown (e.g. dashboard, asset detail, lend/borrow forms).
  Optionally: disable or warn before high-impact actions (e.g. borrow, collateral change) when the relevant oracle price is stale, or document why not.

Acceptance criteria

[ ] Stellar token price hooks/services expose whether the current price is stale (or last-updated time) based on oracle data.
[ ] At least one main user-facing screen (e.g. dashboard, asset detail, or lend/borrow) shows staleness or “last updated” for Stellar RWA prices.
[ ] No change to EVM flows; scope is Stellar-only.

Expected files to change/structure

• apps/web-app/src/hooks/useTokenPrice.ts (or equivalent) to parse and return staleness/last-updated from the oracle response.
• Components that display Stellar RWA prices (e.g. in features/stocks, features/lending, features/borrowing) updated to show staleness or last-updated.
• Optional: shared type/constant for “stale threshold” aligned with oracle config.

[AfroTechBoss]

@AfroTechBoss has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello, I would love to take this issue off your plate
ETA - 12-24 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AfroTechBoss to this issue.

[Emmy123222]

@Emmy123222 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

can i work on this ??

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emmy123222 to this issue.

[Hallab7]

@Hallab7 has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

i would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hallab7 to this issue.

[drips-wave]

Congratulations, @AfroTechBoss! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @AfroTechBoss: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊