On opt-in basis, keep track of DCA performance

[jorijn]

Someone opted the idea to let Bitcoin DCA report how your DCA strategy is performing. Ideally the app would write the transactions to some sort of database and when the user would request statistics, fetch the current price and show how much % the user has progressed.

[Sebastix]

There is already some sort of logging build into the app right? When you provide the tag (-t) argument to the buy command, the buy is attached to a tag (https://bitcoin-dca.readthedocs.io/en/latest/tagged-balance.html#tagged-balance). This info is written down in a JSON file in de application dir /var/storage/balance.db
My idea:

• Add enviroment variable (boolean) to enable logging all buy transactions (or call it a portfolio feature maybe)
• When enabled, a new record is written into a JSON with the amount of bought btc and the timestamp (and maybe also the price in fiat you paid otherwise you should get this price from a third party exchange)
• To check the performance overall, an interface (application) would be ideal which reads all the info from the json and a API request (for example coindesk or the exchange which is used for the buy) is used to get the current btc price. This interface/application could be fully client-side, so you can easily open this at anytime without any use of Docker.

[jorijn]

I like this idea. Yet, isn't SQLite better? Using JSON as a (growing) database isn't very efficient since the code has to parse the entire file every time a line should be added. This would also help in the event of a web interface as SQLite offers basic query functions like GROUP BY and SUM, offloading this logic to presumably more efficient (than PHP) native functions.

[Sebastix]

I agree using a SQLite database is better, but then we need a Docker container to run this database I think?
Another question arises to me, is it possible to query this database from the client / application (Javascript)? Make use of an library like https://github.com/sql-js/sql.js? Or perhaps using IndexedDB is an option? Don't have hands-on expierence with both.