On Tue, Aug 1, 2023 at 12:19 PM Eric Altendorf
wrote:
> On Sun, Jul 30, 2023 at 9:12 AM Martin Blais wrote:
>
>>
>> On Wed, Jul 19, 2023 at 9:10 AM Eric Altendorf
>> wrote:
>>
>>> FWIW I went ahead and wrote my importers to the Beangulp API. I'm
>>> developing them here if anyone wants to
On Sun, Jul 30, 2023 at 9:12 AM Martin Blais wrote:
>
> On Wed, Jul 19, 2023 at 9:10 AM Eric Altendorf
> wrote:
>
>> FWIW I went ahead and wrote my importers to the Beangulp API. I'm
>> developing them here if anyone wants to follow along, contribute, or
>> comment:
>>
On Wed, Jul 19, 2023 at 9:10 AM Eric Altendorf
wrote:
> FWIW I went ahead and wrote my importers to the Beangulp API. I'm
> developing them here if anyone wants to follow along, contribute, or
> comment:
> https://github.com/ericaltendorf/beancount-crypto-importers
>
> Currently covers
FWIW I went ahead and wrote my importers to the Beangulp API. I'm
developing them here if anyone wants to follow along, contribute, or
comment:
https://github.com/ericaltendorf/beancount-crypto-importers
Currently covers Coinbase, Coinbase Pro, and Gate.io.
For now I just have a dumb shell
On Tue, Jul 18, 2023 at 12:52 AM Eric Altendorf
wrote:
> Thanks for the quick reply!
>
> On Sun, Jul 16, 2023 at 8:58 PM Red S wrote:
>
>> I'd recommend exactly that as the first step---spitting out text files of
>> the write format, and using that with your workflow for a while. You'll
>>
I'd recommend exactly that as the first step---spitting out text files of
the write format, and using that with your workflow for a while. You'll
either find that sufficient, or truly understand the specific problems you
want to solve, and be able to pick the right framework with that
I have a few CSV files with basic transactions (basically sent and
received assets & amounts, plus commission cost). These are all I need to
process. It would be pretty easy for me to just translate them line by
line into Beancount format inputs, but I like to do things "the right
way". Problem
