You are viewing a single comment's thread from:

RE: HiveBit.io Beta - Export Your Hive Transaction History In Seconds & Import/Sync to Tax & Portfolio Svcs (Koinly, CoinTracker & more)

in HiveHustlers4 years ago

Powering up/down really had me confused on how to handle them. For now I've ignored both of them, but on powerdowns to your own account, I was triggering events. I think it would be more accurate to make it so that if any account powers down to you (withdrawl routes) it should trigger an event since you are receiving liquid funds.

How are you handling VESTs received? I was thinking of getting the historical pricing of them somehow and use the equivalent HIVE value at first, but the more I think on it, the more I feel like ignoring that would be best, since it'd get captured by the powerdown amount and no need to work out historical vests pricing.

Sort:  

I'm counting all powered up HIVE. When there is a power-down that exceed the powered up HIVE, I create a deposit with the remaining HIVE. Powering up HIVE and powering the same amount is not a tax event, only when I power down more hive then powered up, I have created a tax event. The powered down HIVE, which was not powered up before, is then a staking reward (Could be author, curation, witness or staking reward, but I few all as staking reward regarding tax).

Receiving HIVE through a withdrawal route is the same as a normal transfer.

I do not consider VESTS, as they do not have a price. Only when the get accessible by the tax payer through a power down, a tax event is created. So meaning when I receive an author reward as hive power, I only have to pay taxes, when I more power down as I have powered up.

Hope this makes sense.

That makes sense. Smart way to do it as well. Thanks for sharing your ideas.