You are viewing a single comment's thread:
RE: Update Live: Frontend Parsing for the HiveTools Tax Tool
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
0.00048787 BEE
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.