kryptovero / kryptovero.github.io Goto Github PK

The problem of calculating FIFO is probably better modelled using double entry bookkeeping?

Here's one reference:
https://www.accountingcoach.com/inventory-and-cost-of-goods-sold/explanation/4

There are cryptocurrencies, which distribute rewards to cryptocurrency owners. For example, the proof-of-stake cryptocurrency Algorand rewards its holders cryptocurrency based on the amount of ALGO staked.

Currently, there is no support for cryptocurrency rewards in kryptovero.fi.

Takes several minutes to render. Probably need to switch to a component that uses a virtual list and only renders the components that are visible at a time.

Thanks for creating this! Looks really promising.

I just tried with a CSV file i got from Coinbase Pro. For some reason the amount of tax (veron määrä) is always shown as zero or as "epäluku":

Every row in the UI shows as either zero or as epäluku. Any idea what goes wrong?

The CSV file has 76 rows.

Does the tax office need to know the calculations behind the taxable gains? Which format would be the best? How does one attach the information when doing taxes? Need to call tax office and ask.

It's common to move crypto between exchanges/wallets. Since it costs crypto as gas/transaction fees, it should be representable with this tool.

Now we're using the Javascript native floating point numbers for calculations, and they should not be used for calculating monetary values because they cannot represent all necessary values (losing precision at some places, like the infamous .2 + .1)

Non-fungible tokens can be "minted" using crypto (usually ETH). This should be supported in the tool.

When adding a new transaction that has zero from & to values, the application goes into an infinite loop and crashes.

Google Chrome, Version 98.0.4758.102 (Official Build) (x86_64)

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'split') at Object.GetFormatterParts (_app-dac2e74ea2002737914d.js:1:228416) at Object.GetIANATimeZoneDateTimeParts (_app-dac2e74ea2002737914d.js:1:227298) at Object.GetIANATimeZoneOffsetNanoseconds (_app-dac2e74ea2002737914d.js:1:225834) at e.value (_app-dac2e74ea2002737914d.js:1:258333) at Object.he [as Call] (_app-dac2e74ea2002737914d.js:1:123933) at Object.GetOffsetNanosecondsFor (_app-dac2e74ea2002737914d.js:1:217892) at Object.BuiltinTimeZoneGetPlainDateTimeFor (_app-dac2e74ea2002737914d.js:1:218297) at Object.TemporalInstantToString (_app-dac2e74ea2002737914d.js:1:220538) at new e (_app-dac2e74ea2002737914d.js:1:268178) at Qo (_app-dac2e74ea2002737914d.js:1:313893)

Should the amount of profit be rounded (in Euros) for each row, or only for the resulting sum?

How should we handle importing CSVs from different sources? As there are PRs working on support for e.g. Binance and regular Coinbase, this is a relevant topic.

Possible solutions:

• UI for choosing where to import from
• Automatic detection based on CSV column names

The domain kryptovero (dot) fi is not pointing to this project anymore - README.md should be updated to reflect that.

It seems that Coinbase Pro and Coinbase have different kind of reports. Now kryptovero.fi supports importing only Coinbase Pro reports. Implementing an importer for normal Coinbase should be straightforward.

This project now uses PlainDate, which does not include any notion of time (only date). However the order of transactions is significant and with traders that have more volume there may be some differences if there are multiple transactions during the same day.