Feature: Replace Floating-Point Monetary Storage

[3m1n3nc3]

Description

Replace binary floating-point money fields with exact asset units and explicit asset identity.

File Location

learnault-api/prisma/schema.prisma, monetary utilities, migrations, and affected tests

Design Reference

API Roadmap Phase 0: Replace Floating-Point Monetary Storage.

Dependencies

• Status: Blocked
• Blocked by: Feature: Repair Clean Install and Prisma Generation #67 (Repair Clean Install and Prisma Generation) — done
• Blocks: API Phase 1 wallet schema and later rewards/payouts

Tasks

• Inventory all persisted and calculated amounts using Float or JavaScript number
• Choose integer stroops/asset units or exact decimals and rounding rules
• Persist asset code, issuer, network, and decimals where required
• Create checked forward migration and rollback notes
• Prevent implicit number coercion in serializers and arithmetic
• Test conversion, rounding, overflow, and boundaries

Acceptance Criteria

• No persisted monetary amount uses binary floating point
• Asset and unit are explicit
• Unsafe legacy conversion fails visibly
• Migration and arithmetic tests pass

Verification Evidence

• Attach schema diff, migration dry-run, and exact-arithmetic tests

Difficulty

Advanced

[senmalong]

Hello,

I’d be excited to take this on. I have experience building on Celo and working with Solidity, TypeScript, Rust, Soroban, and Cairo.

I understand the importance of clean contracts, smooth UX, tests, and clear documentation. I can deliver a solid solution within 24 hours of assignment.

Ready to start whenever assigned

[Muhammadjazuli]

I’d like to take this on. I’m comfortable with TypeScript/Node.js and database-backed APIs, and this is an area where getting the foundation right matters before the wallet and payout work builds on it.

I’ll audit the existing monetary fields and calculations, replace unsafe floating-point handling with exact units, and make the asset identity explicit. I’ll also cover the migration carefully, including legacy values that cannot be converted safely, and add tests around conversion, rounding, overflow, and boundary cases.

I’ll include the schema diff, migration dry-run, and exact-arithmetic test results in the PR.

[limxiy]

IHi,
Can I work on this issue? I have experience building Node.js/TypeScript APIs with Various integration systems including prisma, so I’m comfortable working across the schema, migration, and application logic involved here.

I’ll start by tracing where monetary values are stored and calculated, then move them to exact units with the asset information needed to interpret them correctly. I’ll be careful with the legacy migration and make unsafe conversions fail rather than silently changing values.

I’ll also add the conversion and boundary tests and include the migration/schema verification.

[grantfox-oss]

🦊 GrantFox — @Muhammadjazuli has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #123)
2. Your PR will be reviewed by the learnault maintainers

Good luck! Track your progress on GrantFox.