You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't tried out whether saving account statements covering overlapping time ranges causes problems
However, the transaction ID of other exchanges doesn't appear to be used yet. Do you think it's beneficial to use it for detecting "duplicate" transactions?
The text was updated successfully, but these errors were encountered:
I haven't tried out whether saving account statements covering overlapping time ranges causes problems
However, the transaction ID of other exchanges doesn't appear to be used yet. Do you think it's beneficial to use it for detecting "duplicate" transactions?
Why not. If we want to implement it. We should add a function which is called after the readin and does checks like this and other (e.g. do the buy/sell positions match?)
#127 matches identical operations together. It raises an error, when identical operations exist in two different files (duplicate!?). In the branch, identical transactions in the same file will be merged together without a warning.
I don't think that this is a huge issue, because account statements should be gathered directly from the exchange and added to CoinTaxman without any custom changes.
I haven't tried out whether saving account statements covering overlapping time ranges causes problems
However, the transaction ID of other exchanges doesn't appear to be used yet. Do you think it's beneficial to use it for detecting "duplicate" transactions?
The text was updated successfully, but these errors were encountered: