Repository navigation
[MEDIUM] — CSV donation export hardcodes "USD Equivalent" = 0.00; downstream consumers may trust the column for tax / accounting workflows #15
Description
Activity
Hi maintainer, I would love to work on this issue. I have studied the details of the issue description and I understood the requirements. I shall deliver with qualitative feedback and promptly.
🦊 GrantFox — @iyanumajekodunmi756 has been assigned to this issue as part of the Official Campaign campaign!
Next steps:
- Open a Pull Request referencing this issue (e.g.,
Closes #15) - Your PR will be reviewed by the OrbitChainLabs maintainers
Good luck! Track your progress on GrantFox.
- Open a Pull Request referencing this issue (e.g.,
🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!
@iyanumajekodunmi756's PR #29 was approved and merged by @Alqku.
🏆 @iyanumajekodunmi756: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (83 total points). Track your full progress on GrantFox.
👏 Great work, @iyanumajekodunmi756! Keep contributing to OrbitChainLabs.
Severity: Medium
Type: Bug
Scope: Donations, Users
Labels:
bug,security,help wantedDescription
Both the synchronous and asynchronous export paths emit a hardcoded
0.00USD equivalent:UsersService.exportUserDonationsAsCSV(src/users/users.service.ts, line ~415).ExportProcessor.handleDonationExport(src/users/export.processor.ts, line ~58).The comment in each location acknowledges this is a placeholder ("USD equivalent: fetched from price cache in production").
Two failure modes persist today:
0.00value and may trust it.Recommendation
Quote: pending./order_booksnapshots, CoinGecko, or a self-hosted oracle service) and cache quotes with TTL by asset.README.mdso external integrators are not surprised.