thank you, I'd be interested in learning more about it. going to search for 
content and also would appreciate to receive the shared links.

b...@bben.us schrieb am Samstag, 10. April 2021 um 17:04:58 UTC+2:

> There were several recent threads on this subject that go into more 
> details. I'm on mobile or I'd give you a link.
>
> On Sat, Apr 10, 2021, 07:24 david e <in...@davidebner.de> wrote:
>
>> I see, thanks!
>>
>> bl...@furius.ca schrieb am Samstag, 10. April 2021 um 16:19:50 UTC+2:
>>
>>> It doesn't do that for you.
>>> It can book against the existing lots (e.g. with FIFO) but on 
>>> the opening side (WalletB) it won't know to fill in the corresponding 
>>> average cost basis.
>>> If you do this a lot, you'll have to automate with a script.
>>>
>>> I think eventually some features need to be built for users of DA but I 
>>> don't know what they all should be yet, and I don't use the stuff much 
>>> myself, I have some, but I don't spend any. Crypto's a bit of a headache if 
>>> you use them as dual purpose to spend or transfer and as speculation. If 
>>> tracking really matters to you, I think you'll make your life easier if you 
>>> separate those two worlds.
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Apr 10, 2021 at 10:00 AM david e <in...@davidebner.de> wrote:
>>>
>>>> I am adding my crypto tx history manually to my bean-file and am 
>>>> wondering about how to send from one wallet to another by respecting the 
>>>> cost basis.
>>>>
>>>> example:
>>>>
>>>> 2020-01-01 * "send eth from wallet a to b"
>>>> Assets:Crypto:WalletA   -1.00 ETH {} ;bean fetches cost basis
>>>> Assets:Crypto:WalletB    1.00 ETH {} ;how to match them here?
>>>>
>>>> when I run bean-report myfile.bean print, I can then see that 1.00 ETH 
>>>> from WalletA contains several Lots that now have to be transferred to 
>>>> Wallet B (as this isn't a taxable event I want to keep the cost basis).
>>>>
>>>> is there a way to hand the exact amount over either as an average or 
>>>> with the Lots as is?
>>>>
>>>> thanks lot
>>>>
>>>> -- 
>>>> 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 beancount+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/beancount/274e7cac-cd45-45e3-aaaa-2f77732f2405n%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/beancount/274e7cac-cd45-45e3-aaaa-2f77732f2405n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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 beancount+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beancount/19b2c568-214e-498b-8578-a026b12c4496n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beancount/19b2c568-214e-498b-8578-a026b12c4496n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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 beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/ee013b55-ce0d-4d44-89b8-d0ebc505cbf0n%40googlegroups.com.

Reply via email to