|
| 1 | +--- |
| 2 | +title: Unannounced channels |
| 3 | + |
| 4 | +## Optional. An entry will be added to the topics index for each alias |
| 5 | +aliases: |
| 6 | + - Private channels |
| 7 | + |
| 8 | +## Required. At least one category to which this topic belongs. See |
| 9 | +## schema for options |
| 10 | +categories: |
| 11 | + - Lightning Network |
| 12 | + |
| 13 | +## Required. Use Markdown formatting. Only one paragraph. No links allowed. |
| 14 | +## Should be less than 500 characters |
| 15 | +excerpt: > |
| 16 | + **Unannounced channels** are LN channels that are not advertised to |
| 17 | + the network for use in routing. |
| 18 | +
|
| 19 | +## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed. |
| 20 | +extended_summary: | |
| 21 | + Most unannounced channels are believed to belong to users that simply |
| 22 | + don't intend to route payments, such as users of mobile clients that |
| 23 | + aren't always online to route payments. |
| 24 | +
|
| 25 | + Unannounced channels channels are sometimes called **private |
| 26 | + channels** but this is [discouraged][unpublished channels delenda est] |
| 27 | + by some experts because, if the channels aren't used for routing, then |
| 28 | + the publicly known counterparty of an unannounced channel knows that |
| 29 | + any payment to or from that channel either started or ended with that |
| 30 | + channel. |
| 31 | +
|
| 32 | + [unpublished channels delenda est]: https://lists.linuxfoundation.org/pipermail/lightning-dev/2019-December/002408.html |
| 33 | +
|
| 34 | +## Optional. Produces a Markdown link with either "[title][]" or |
| 35 | +## "[title](link)" |
| 36 | +#primary_sources: |
| 37 | +# - title: Test |
| 38 | +# - title: Example |
| 39 | +# link: https://example.com |
| 40 | + |
| 41 | +## Optional. Each entry requires "title", "url", and "date". May also use "feature: |
| 42 | +## true" to bold entry |
| 43 | +optech_mentions: |
| 44 | + - title: "LND #1944 tweaks `sendtoroute` RPC to allow routing via private channels" |
| 45 | + url: /en/newsletters/2018/11/13/#lnd-1944 |
| 46 | + date: 2018-11-13 |
| 47 | + |
| 48 | + - title: "C-Lightning #2230 adds a `private` flag to the `listpeers` RPC" |
| 49 | + url: /en/newsletters/2019/01/15/#c-lightning-2230 |
| 50 | + date: 2019-01-15 |
| 51 | + |
| 52 | + - title: "C-Lightning #2234 adds route hints for private channels to `invoice` RPC" |
| 53 | + url: /en/newsletters/2019/01/22/#c-lightning-2234 |
| 54 | + date: 2019-01-22 |
| 55 | + |
| 56 | + - title: "Talk about LN topology and lack of public info about unannounced channels" |
| 57 | + url: /en/newsletters/2019/09/18/#lightning-network-topology |
| 58 | + date: 2019-09-18 |
| 59 | + |
| 60 | + - title: "C-Lightning #3351 enhances `invoice` RPC for private channels" |
| 61 | + url: /en/newsletters/2020/01/08/#c-lightning-3351 |
| 62 | + date: 2020-01-08 |
| 63 | + |
| 64 | + - title: "Eclair #1283 allows multipath payments to traverse unannounced channels" |
| 65 | + url: /en/newsletters/2020/01/22/#eclair-1283 |
| 66 | + date: 2020-01-22 |
| 67 | + |
| 68 | + - title: "Breaking the link between UTXOs and unannounced channels" |
| 69 | + url: /en/newsletters/2020/01/29/#breaking-the-link-between-utxos-and-unannounced-channels |
| 70 | + date: 2020-01-29 |
| 71 | + |
| 72 | + - title: "C-Lightning #3600 adds blinded paths to improve unannounced channel privacy" |
| 73 | + url: /en/newsletters/2020/04/08/#c-lightning-3600 |
| 74 | + date: 2020-04-08 |
| 75 | + |
| 76 | + - title: "C-Lighting #3623 improves unannounced channel privacy when routing payments" |
| 77 | + url: /en/newsletters/2020/04/22/#c-lightning-3623 |
| 78 | + date: 2020-04-22 |
| 79 | + |
| 80 | +## Optional. Same format as "primary_sources" above |
| 81 | +# see_also: |
| 82 | +# - title: |
| 83 | +# link: |
| 84 | +--- |
0 commit comments