-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(new format of csv) Unrecognized file type error #14
Comments
It should not be too hard to load this file type, but your example only contains a single example line so it does not provide a lot of information. In particular:
Finally, this appears to rather be a kind of position being held, given that there is a "LONG" and an "ExitPrice"? Is this just a future trade waiting to happen or does it actually map to a transaction? |
Hello, sorry for providing incomplete data.
It is a perpetual trade that has already been finished, hence the closed profit and loss being reported (p&l), so it is finished. Based on what I've seen on the Koinly support page, these trades should just be the p&l. Since they aren't actual transactions (ex: buying or selling btc), it is all just smart contracts. Thanks a lot for your help, I appreciate what your software offers against the SAAS alternatives. |
Alright, so that's going to be a little more tricky, since it means not only parsing a new CSV format but also adjusting the application in general support this new type of transaction. Still not that big of a deal though, we can uncomment "RealizedProfit" and "RealizedLoss" in |
This is quickly getting difficult, and I am not a experienced coder, this is out of my reach. |
I've made a bit of a start on this at #15. What is missing is:
|
I am using a not very well known DeX (apex omni, from bybit team), hopefully this is not a dealbreaker, I understand if we can't add the formatting for it.
The csv looks like this:
If somebody, or Bjorn himself, has the knowledge required to add this format of csv I would be very grateful, thanks a lot.
The text was updated successfully, but these errors were encountered: