Use historic BTC rate for expense items; allow BTC as currency #226
Reference in New Issue
Block a user
Delete Branch "feature/currencies"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fetches historic rates when adding expense items where the date is not the current day (still using current rate otherwise). The API for this is just JSON objects posted to a public category in our
kosmos@kosmos.orguser's remoteStorage account (implementation for that following separately).Also allows to add expense items with BTC as currency, which forgoes the currency conversions.
Both for transparency and accurate implementation, there is now also an additional sats amount stored with each line item in the expense list for every expense, no matter if it's EUR, USD, or BTC.
closes #225
Edit: I just realized that for the
amountSatsto be included in the IPFS docs, it needs to be added to the kredits JS library first. Added an issue for it.I just used this PR to submit the latest reimbursement, which spans a few months. The historic rates in storage go back to August 1, 2024 as of now (but can be extended if necessary).
Here's the corresponding PR for publishing the exchange rates every midnight (UTC):
kosmos/chef#581
This is all ready to merge, with the dependencies already merged and deployed...