From: ZmnSCPxj <ZmnSCPxj@protonmail.com>
To: Erik Aronesty <erik@q32.com>
Cc: Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>,
lightning-dev <lightning-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Scaling Lightning With Simple Covenants
Date: Tue, 19 Sep 2023 07:44:48 +0000 [thread overview]
Message-ID: <An4gUD9oSgMzt9dGWj7ZhCZ73fWNcQ_c9dya0X0OILJFGijykRNtWc4HClKJ0QGsQjKiL2-Oak7syh_4XngCNFJEVJDhKeEy11nedSpXbpI=@protonmail.com> (raw)
In-Reply-To: <CAJowKgL+sW_rtO+zaoe=ztia9SfQXCeZ0YnAsmox1O3r3kAAwQ@mail.gmail.com>
Good morning Erik,
> > replacing CTV usage with Musig2
>
>
> this changes the trust model to a federated one vs trustless and also increases the on-chain footprint of failure, correct?
As I understand it, no.
MuSig and MuSig2 are n-of-n signing algorithms.
The implied usage is that all entities `A_i` for all `i` and `B` dedicated LN node are in the n-of-n set.
The argument that 2-of-2 channels are non-custodial and trust-minimized extends to n-of-n for all n.
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2023-09-19 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 18:54 [bitcoin-dev] Scaling Lightning With Simple Covenants jlspc
2023-09-11 0:56 ` [bitcoin-dev] [Lightning-dev] " Anthony Towns
2023-09-17 0:52 ` jlspc
2023-11-15 19:59 ` jlspc
2023-09-11 2:13 ` [bitcoin-dev] " Rusty Russell
2023-09-17 0:56 ` jlspc
2023-09-11 5:27 ` Antoine Riard
2023-09-17 0:59 ` jlspc
2023-09-26 16:42 ` Antoine Riard
2023-10-06 16:26 ` jlspc
2023-09-17 11:32 ` Erik Aronesty
2023-09-19 7:44 ` ZmnSCPxj [this message]
2023-09-18 4:14 ` ZmnSCPxj
2023-09-28 15:56 ` jlspc
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='An4gUD9oSgMzt9dGWj7ZhCZ73fWNcQ_c9dya0X0OILJFGijykRNtWc4HClKJ0QGsQjKiL2-Oak7syh_4XngCNFJEVJDhKeEy11nedSpXbpI=@protonmail.com' \
--to=zmnscpxj@protonmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=erik@q32.com \
--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