[Frontend] Consolidate duplicate amount helpers in lib/amount.ts and utils/amount.ts

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

There are two parallel amount-formatting modules with overlapping function names but different signatures, and different parts of the app import from each. This is an active bug-magnet: a developer copying a call from one file to another can silently pass the wrong arguments.

Verified divergence

Both frontend/src/lib/amount.ts and frontend/src/utils/amount.ts export formatAmount, parseAmount, formatRate, hasValidPrecision, toStroops, fromStroops — but the signatures differ:

• lib/amount.ts: fromStroops(stroops) (1 arg), toStroops(value) (1 arg, assumes 7 decimals).
• utils/amount.ts: fromStroops(amount, decimals) (2 args), toStroops(amount, decimals) (2 args).

Import split (verified via grep):

• Import from @/lib/amount: app/activity/page.tsx, components/IncomingStreams.tsx, components/stream-creation/{AmountStep,StreamCreationWizard,ScheduleStep}.tsx, components/dashboard/ActivityHistory.tsx.
• Import from @/utils/amount: app/streams/[id]/page.tsx, app/streams/create/page.tsx, components/NotificationDropdown.tsx, components/stream-creation/TopUpModal.tsx.

utils/amount.ts is the richer one (token-decimals cache, async fetchTokenDecimals, validateAmountInput) and is the one covered by __tests__/utils.test.ts.

Acceptance criteria

• Pick one canonical module (suggest utils/amount.ts, since it's tested and fuller) and migrate all imports to it.
• Reconcile the differing fromStroops/toStroops arities at call sites.
• Remove the duplicate module (or re-export from it for back-compat).
• Tests and build pass.

Files to touch

• frontend/src/lib/amount.ts
• frontend/src/utils/amount.ts
• All importers listed above.

Out of scope

• Changing displayed precision/format behavior.

[itzabdoull]

@itzabdoull has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi team, can i work on this issues?

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

[silifatzoffun74-art]

@silifatzoffun74-art has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi Maintainer Can I work on this issue

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

[drips-wave]

Congratulations, @silifatzoffun74-art! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @silifatzoffun74-art: 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 awarded 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 🌊

[drips-wave]

This issue has been completed by @silifatzoffun74-art as part of the Stellar Wave Program's 5th Wave 🥳

😎 @silifatzoffun74-art: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.