On Fri, Apr 26, 2024 at 4:49 PM Simon Michael <[email protected]> wrote:
> On 2024-03-19 08:37, Eric Altendorf wrote: > > Hmm, i guess my example doesn't include any account transfers. > > > > My understanding is cost bases are attached to lots which are tracked in > > accounts. So if you have 100 ETH in account A and 100 ETH in account B, > > and you sell or transfer from Account A, it will FIFO the lots in > > Account A and ignore the lots in Account B. > > > Hi Eric, I was just looking at > > https://github.com/ericaltendorf/magicbeans/blob/master/data/magicbeans_example.pdf > , I must say it's rather lovely and as you say, practical for showing eg > to an auditor. > > To be clear, if someone tracks lots in subaccounts and manually > preserves all costs when assets are moved around, magicbeans will > probably still be able to produce reasonably accurate reports ? > Probably. A big part of the issue I ran into was scale. Both on the farming ("mining") side as well as on the trading side, there were tons of small transactions. If you include the spam-dust (billionths of a cent that were sent to my address on a regular basis) I had a truly obscene number of transactions and lots. Even if you filter those, I had many thousands because of some stupid pooling protocol issues and bad illiquid execution on an exchange. So anything "manual" was simply untenable for me. I wanted a fully automated pipeline, kind of like an old school "make" script, that would gather everything, apply my cleanups and tweaks, and reconcile it all. I just kept adjusting the tweaks and cleanups until I handled all the mess, but then at least it's reproducible, and if i want to change something (e.g. lot selection, or I get some new info that was missing before) i can update and rerun the whole thing. it's not the normal beancount way, but it felt most safe to me. FWIW, magicbeans has basically two components: one, which is what I just described, a set of importer tools that I found useful, which produces a beancount file. The second is the report generation, which takes a beancount file as input. If you produce a beancount file by other means but containing the needed info, you should still be able use the second half of the tool to generate the reports. > > -- > You received this message because you are subscribed to the Google Groups > "Beancount" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beancount/15103496-1e3e-4b80-8aa9-855443acd2ad%40joyful.com > . > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/CAFXPr0uocD8sUsNUxc6uLevGhBoZoz-NgcnGM%2BTuHUB2hcc%2BQg%40mail.gmail.com.
