From alex.bosworth at gmail.com  Mon Dec 18 05:20:35 2017
From: alex.bosworth at gmail.com (Alex Bosworth)
Date: Sun, 17 Dec 2017 21:20:35 -0800
Subject: [Lightning-dev] Comments on BOLT#11
In-Reply-To: <87k1xm4ico.fsf@rustcorp.com.au>
References: <CAMpN3mL0mQdDhfDB+pnNm3f-mX_7N8i6R+fEkin26H4iJE4g0Q@mail.gmail.com>
	<87zi6ou4kt.fsf@rustcorp.com.au>
	<CAMpN3mJ-1XeWyX3Xm_uyGzzSbeHO=PC__0nCQxRfbayAck4NyA@mail.gmail.com>
	<874losfrjw.fsf@rustcorp.com.au>
	<CAMpN3m+Zu_Qq5Y7iEBk6BmwPiinB4=_LrvxTyo-zUvk01hPnoQ@mail.gmail.com>
	<87k1xm4ico.fsf@rustcorp.com.au>
Message-ID: <CAFLuHNEP1+5cAx5+WWhumhQTUqkf7zzc8JgVLw=yT=nVnycJ4g@mail.gmail.com>

htlc.me storing data in the description is just an artifact of the
original lnd API which didn't include that data in the payment request

On Sat, Dec 16, 2017 at 10:51 AM, Rusty Russell <rusty at rustcorp.com.au> wrote:
> Jonathan Underwood <junderwood at bitcoinbank.co.jp> writes:
>> iirc they are using the description as a way to join the user data and the
>> payment hash on their end.
>
> But the description isn't used when I send a payment.  All they get is
> the payment_hash.
>
>> htlc me is one node but separates its balance into user accounts that exist
>> outside lightning. I think the identifier is used so when their backend
>> checks the payment request status, the user info is right there in their
>> local lnd RPC response rather than having to store their own database
>> separately.
>
> Ah, that's understandable, but it seems like a wrong API.
>
> c-lightning doesn't store the description in the database at all: each
> invoice uses a label which the invoice creator specifies.  Unlike a
> description, this must be unique.  It's not exposed to customers at all.
>
> Cheers,
> Rusty.
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev



-- 
Sent from my iPhone