From: Atomic Mr Nuclear <atomic-mr-nuclear@onionmail.org>
To: bitcoin-dev@lists.linuxfoundation.org,
lightning-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Nucleus: Capital-efficient multipeer Lightning payment channels
Date: Sun, 20 Aug 2023 14:25:07 +0000 [thread overview]
Message-ID: <1a7c7373-5511-d5f4-4aa9-8c19c3c0303d@onionmail.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 575 bytes --]
Dear community,
In the attachment you will find a new proposal for Lightning multipeer payment
channels which provides better capital efficiency (no inbound liquidity is
required) and liveness (up to half of peers may go offline and the channel can
continue to operate). It also doesn't rely on a penalty mechanism and doesn't
require the use of atomic swaps (HTLC, PTLC etc) and routed payments for scaling
(peers can directly join the multipeer channel instead of establishing a network
of channels locking in the liquidity).
----
Atomic Mr Nuclear
[-- Attachment #1.2: Type: text/html, Size: 594 bytes --]
[-- Attachment #2: Nucleus.pdf --]
[-- Type: application/pdf, Size: 322440 bytes --]
reply other threads:[~2023-08-20 14:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1a7c7373-5511-d5f4-4aa9-8c19c3c0303d@onionmail.org \
--to=atomic-mr-nuclear@onionmail.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=lightning-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox