I wrote in mid-December about Detangling DeFi with Beancount, a plain-text accounting software that I really love.
Unfortunately, Hive, especially Hive Engine, is such a vibrant buzz of transactions that unless I take steps to limit my activity and exposure to the market, I'll continue to have a hundred or more transactions to log each day, just from Hive!
Doing that, even with Org-mode capture templates helping assist with data entry, isn't really feasible, and trying for these past couple days slowed everything else I was working on down to a crawl. Some things, like spread farming, became impossibly slow.
I don't really need a lot of the nuance that the Beancount ledger was giving me, so I'm comfortable, if a bit grumpy, about letting it go - at least for now.
But the difficulties of documentation on Hive have serious implications for the platform. Knowing the cost basis of an asset like HIVE or a sidechain token like BBH, when you earned or bought it, is important for filing taxes, or just, understanding your revenue in a holistic sense. It's a problem that will have to be solved, in order for HIVE as an ecosystem to make use of the liquidity now flowing into it because of futures markets.
Personally, not having to worry about Beancount will leave me free to spend more time cultivating the "content farm" part of my Org-mode records, which is where I plan, research, outline, and draft the stuff I'm posting to Hive and other places.
And, with the stability of housing, I might find myself getting back into programming. I hear there's already a Python library for interacting with Hive…
Of course, all this will change once spring gets here and things thaw. Then, it'll be time to focus on recording and sharing documentation from all the foraging and other stuff I'll hopefully be getting up to!
