iirc they are using the description as a way to join the user data and the payment hash on their end.
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. 2017年12月16日(土) 8:31 Rusty Russell <[email protected]>: > Jonathan Underwood <[email protected]> writes: > > Additional comment: we should make a requirement to hide text in the > > description under certain conditions. > > > > ie. "A reader MUST hide information surrounded by curly brackets {} > > including > > the brackets themselves from the UI, and only make the information > avaiable > > internally." > > > > I think a lot of people will want to include extra data in their payment > > requests' description. > > > > I think HTLC.ME uses it and maybe bitrefill? (correct me if I'm wrong.) > > OK, HTLC.ME (cool site!) uses a description of: > > {"generic_id":"ada00363-50b6-4281-82dd-d274393439f1"} > > Which I really don't understand. This field is literally only to > display to the user, for them to validate it's what they wanted. The > recipient never gets it back. > > If I knew who ran HTLC.ME, I'd ask them to fix it: they should have a > description entry field in their "Request Payment" form. It could > default to "Test payment ada00363-50b6-4281-82dd-d274393439f1", but > they're in spec violation at the moment. > > > Perhaps adding an "extra data" tag? > > Easy to do, if I knew why they wanted it. > > Thanks! > Rusty. > -- ----------------- Jonathan Underwood ビットバンク社 チーフビットコインオフィサー ----------------- 暗号化したメッセージをお送りの方は下記の公開鍵をご利用下さい。 指紋: 0xCE5EA9476DE7D3E45EBC3FDAD998682F3590FEA3
_______________________________________________ Lightning-dev mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
