Eugene [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2019-01-02 to 2020-05-17
💬 Posted a total of 3 messages
📚 Participated in the following categories: Lightning-dev
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-09 13:00:15

- reply

📅 Original date posted:2020-05-17
📝 Original message:
Hello,
I found a way for one client to initiate a payment from the other by using spontaneous keysend payments:
1. Payee sends keysend payment of negligible amount (1 sat?)
2. Payer accepts keysend and verifies that it comes from a trusted node
3. Payer makes a keysend payment of required amount back to Payee
4. Payee accepts payment
Step two should probably be implemented by a custom plugin that checks incoming keysend messages and pays valid ones back.
The flow above is basically uses keysend to send an invoice to Payer to be paid. I wonder if there's an other way to send an invoice through LN by Payer's node public key?
Cheers,
Eugene
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, 15 May 2020 01:13, Eugene via Lightning-dev <lightning-dev at lists.linuxfoundation.org> wrote:
> Hello, list,
>
> I haven't closely following the Lightning Network's state of affairs since late 2018 and I wondering, is it possible to support the following use-case with LN:
>
> 1. A user subscribes to the service by opening a channel with it
> 2. User sets his LN node to "trust" invoices that come from said service
> 3. On subscription renewal, service sends an invoice to the client's LN node
> 4. Since the client's node is "trusting" service's node, it pays invoice straight away
>
> User, of course, may cancel the subscription at any time by removing service's LN node public key from the list of "trusted". Or the user can set a limit on the amount and the frequency of payments that would be accepted from the trusted node.
>
> For that matter, the questions are:
>
> 1. Is it possible to send invoices just by LN means? (Should we use TLVs?)
> 2. Is it possible to enable automatic machine-to-machine payments? As in the example above, by accepting invoices from "trusted" nodes.
>
> Best regards,
> Eugene
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20200517/dae3f0a5/attachment.html>

2023-06-09 13:00:15

- reply

📅 Original date posted:2020-05-14
📝 Original message:
Hello, list,
I haven't closely following the Lightning Network's state of affairs since late 2018 and I wondering, is it possible to support the following use-case with LN:
1. A user subscribes to the service by opening a channel with it
2. User sets his LN node to "trust" invoices that come from said service
3. On subscription renewal, service sends an invoice to the client's LN node
4. Since the client's node is "trusting" service's node, it pays invoice straight away
User, of course, may cancel the subscription at any time by removing service's LN node public key from the list of "trusted". Or the user can set a limit on the amount and the frequency of payments that would be accepted from the trusted node.
For that matter, the questions are:
1. Is it possible to send invoices just by LN means? (Should we use TLVs?)
2. Is it possible to enable automatic machine-to-machine payments? As in the example above, by accepting invoices from "trusted" nodes.
Best regards,
Eugene
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20200514/781455c6/attachment.html>

2023-06-09 12:53:49

- reply

📅 Original date posted:2019-01-02
📝 Original message:
Hi,
how about using of Chernoff Faces to identify node’s public key? Since humans are best fit to recognize small changes in faces and to remember them.
To achieve avalanche effect from changing a private key to produce much different face, one can just plug node’s public key into a cryptographic hash function and then plug a result into Chernoff Face generator, thus making a public key change very easy to notice.
Вкл вс, дек. 23, 2018 в 21:49, Pavol Rusnak via Lightning-dev <lightning-dev at lists.linuxfoundation.org> написал(а):
> Hi all!
>
> Currently, when I perform a payment via QR code, I usually check the
> payee node id (public key) in the send dialog. However, this is a rather
> long hex value, so for example Eclair app shows just the beginning and
> the end of the value.
>
> Idea: Can we show an identicon (for example https://jdenticon.com/) of
> payee node id (= public key) next to the QR code, so user can visually
> quickly check whether the recipient is correct?
>
> We'd need to add this to UI of all Lightning user-facing wallets to make
> sense, though.
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20190102/628c7c2e/attachment.html>