Jump to content

Questioning the ledger to list up historic buys


kanaas

Recommended Posts

I made some important XRP buys during the years 2014 and 2015, mainly on the old RippleTrade, later also on Gatehub.
Our Belgian taxes only apply tax to huge private capital gains if these are not obtained through (intensive) trading. For the latter, taxes are very huge.
My problem (and I guess others too), to avoid very heavy taxes (about 40%), is that I will have to prove when I bought the XRP and that I made only very limited or no trading at all.

Question: is there a tool somewhere (that can be used by our taxation) that can look up and list all the purchases and sales that were made on a specific account?

If not, I might be prepared to pay for a creation of such.

Link to comment
Share on other sites

You could look up the transaction history of your account(s) via one or several calls to https://ripple.com/build/rippled-apis/#account-tx

The results probably still need some interpretation, I personally use ledger-cli (or related tools like Beancount) for that.

3 minutes ago, kanaas said:

If not, I might be prepared to pay for a creation of such.

In theory the DataAPI should be enough, in practice they seem to miss a lot of data and in general be slightly on the unreliable/buggy side of things.

Link to comment
Share on other sites

1 hour ago, Sukrim said:

In theory the DataAPI should be enough, in practice they seem to miss a lot of data and in general be slightly on the unreliable/buggy side of things.

We are working on that! Things have already improved tremendously, and we'll get any remaining wrinkles ironed out.

Link to comment
Share on other sites

1 minute ago, nikb said:

We are working on that! Things have already improved tremendously, and we'll get any remaining wrinkles ironed out.

Great to hear. Looking at the commits though...? https://github.com/ripple/rippled-historical-database/commits/develop

The 2 open PRs are about removing a feature and adding address/gateway names (unanswered for months now). Issues on Github are an issue by themselves...

As far as I see, there is zero(!) validation of data that this project ingests, it sompletely trusts the rippled server(s) to quickly serve reliable data. I hope you are feeding the data API servers from an internal cluster and not from s2.ripple.com. Anyways, good to know that you are taking a look at the project and are committed to improving it. Please also take the community into account and let them help you.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...