Good morning Jose,
>
> I wish they could ;-)
> Not all machines sell products. Some sell services: Arcade machines, Toll
> booths, etc., are examples of machines that provide a service instead of a
> physical product, where not having to replentish invoices ever is desirable.
I imagine even a
DISCLAIMER:
These next two messages come out of order. One was scrubbed by the list (html),
the other I sent inadvertently only in private to ZmnSCPxj.
I repost them here for completeness of the thread.
My excuses.
Hello ZmnSCPxj,
> Is
Good morning Jose,
> > I still have a few doubts however on how the scheme you propose would
> > handle these concerns:
> > a) Price changes: With the piggybacking scheme I propose, the vending
> > machine (or toll both, or whatever) doesn't set the price of the item or
> > service. It only
Good morning Jose,
> Anyway, my point here is that it is actually desirable having both standards
> and modified wallets, to radically increase usability, which will be needed
> if we want to have widespread adoption of LN payments.
This is badly undesirable.
We should have standard wallets
Hello ZmnSCPxj,
Is this the same problem that is solved by: https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-November/001579.html ?
It essentially is; but I guess there will be other use cases where it may be interesting to transmit some information encoded within the
Good morning JOSE,
> An offline device (say a vending machine) shares a secret S1 with an online
> LN Node.
Is this the same problem that is solved by:
https://lists.linuxfoundation.org/pipermail/lightning-dev/2018-November/001579.html
?
I believe the solution presented at the summit is
Hi, I'd like to share an idea to piggyback information within the
payment_preimage. (The intended use case is for offline payments, but I suppose
there could be more).
AFIK the Bolt documentation doesn't have any provision for a scheme like this,
but I am am still trying to digest all the Bolt
