I think it's true that most of my proposal can be achieved by writing
such things in human-readable form in the description field. Mostly,
the only thing my proposal does is to put things into a machine-
readable form; this may aid in automated processing and maybe a better
UI experience.
Maybe
Good morning CJP,
It seems to me, naively, that we can encode the description "the obligation in
the invoice whose hash is is nullified", whose meaning then is promoted to
"if payment happens, payee has an obligation to ensure that the obligation in
the invoice whose hash is is nullified",
Right now, the only defined semantics of the description field in
BOLT11 is that it SHOULD be "a complete description of the purpose of
the payment". I think this is a bit vague; maybe this is deliberate?
Anyway, you may also think of a BOLT11 payment request as an option
contract. If the payment
