Hey everyone,
Following up on my last post, the tax tool update is officially live. I transitioned the parsing logic entirely to the frontend.

The tool now processes large accounts with massive transaction histories quickly and reliably. You will also see a new progress indicator during the data retrieval phase, so you know exactly where the process stands. As discussed previously, the tool now exclusively outputs to CSV.
Test it out and let me know how it handles your account data.
As always,
Michael Garcia a.k.a. TheCrazyGM
good luck
Very useful also for standard reporting, and not only for tax purposes.
What is your view on sticking to VEST? Couldn't it be more useful if you convert it to HP? As VEST is more of an internal token, it is not very intuitive to everyone to track its value...
!PIMP & !LUV
Wasn't any reason in general. Was made with no feedback, but you are correct. I'll try to put in patch here soon.
Just realized how difficult it would be for accurate accounting purposes. The vest to hp formula changes per block, it would take thousands of api calls to figure out the historical vest->hp value. I could easily implement what the vest to hp is "at this moment" but for history not so easy.
In the past I once contemplated building a historical vest to hp table! I feel like something more practical could be used, and convert to hp at the time of report generation. What's the tax man going to do, build a table? 🤣
!PIMP
Thanks for spending some time on this tool in february, before it becomes a huge deal for people. This is a great example of a tool that has massively improved by iterative development processes.
!PIMP
!PAKX
!PIZZA
View or trade
PAKXtokens.Use !PAKX command if you hold enough balance to call for a @pakx vote on worthy posts! More details available on PAKX Blog.
Frontend parsing cuts load time way down for big accounts. Nice work.
$PIZZA slices delivered:
@ecoinstant(1/20) tipped @thecrazygm
Please vote for pizza.witness!