From rusty at rustcorp.com.au  Sat Dec 16 18:51:03 2017
From: rusty at rustcorp.com.au (Rusty Russell)
Date: Sun, 17 Dec 2017 05:21:03 +1030
Subject: [Lightning-dev] Comments on BOLT#11
In-Reply-To: <CAMpN3m+Zu_Qq5Y7iEBk6BmwPiinB4=_LrvxTyo-zUvk01hPnoQ@mail.gmail.com>
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>
Message-ID: <87k1xm4ico.fsf@rustcorp.com.au>

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.