From 32ec5d0bb7f81e972b40804f5748a62847978cfa Mon Sep 17 00:00:00 2001 From: anon <109770337+lnproxy@users.noreply.github.com> Date: Sun, 9 Jul 2023 13:23:03 -0400 Subject: [PATCH] restore readme --- README.md | 42 +++++++++++++++++++++++++++++------------- 1 file changed, 29 insertions(+), 13 deletions(-) diff --git a/README.md b/README.md index e6c8bc0..87968df 100644 --- a/README.md +++ b/README.md @@ -1,16 +1,32 @@ -### Hi there šŸ‘‹ +# lnproxy - +## Why + +Lightning network invoices reveal the destination of payments. + +- Users who operate public Lightning Network nodes reveal the identity of their node + with every Lightning invoice they generate. + With lnproxy, these users can obfuscate the destination of their payment from their custodian. + +- Users of custodial Lightning wallets reveal the destination + of every Lightning invoice they pay to their custodians. + With lnproxy, these users can obfuscate the identity of their Lightning nodes + from their transaction counterparties. + +## How + +Proxy invoices are hodl invoices. +When an lnproxy relay accepts an htlc for the proxy invoice, +it immediately pays the original invoice +and uses the revealed preimage to settle the proxy invoice. +This ensures that you don't need to trust lnproxy relays +with your payments.