From: ZmnSCPxj <ZmnSCPxj@protonmail•com>
To: ryan@breen•xyz
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Sentinel Chains: A Novel Two-Way Peg
Date: Wed, 30 Aug 2023 11:05:03 +0000 [thread overview]
Message-ID: <E9WH5C46HJT_uwLTnliTeZSZPrPwoKQs57muUxPVzaGWCWWriC4m2HGVoagR8dfvRBU_1qGtvlhojqIf_854em3_bJIR6DzAqAGHR6fW_nI=@protonmail.com> (raw)
In-Reply-To: <0D44C322-E2B4-4F80-A5D8-7D8304BDAE1A@breen.xyz>
Good morning Ryan,
> I appreciate your questions, ZmnSCPxj.
>
> I will answer your second question first: Mainchain nodes do not ever validate sidechain blocks. Sidechain nodes watch Bitcoin for invalid withdrawals, and publish signed attestations to a public broadcast network (such as Nostr) that a transaction is making an invalid withdrawal. These sidechain nodes are the so-called sentinels.
Let me reiterate my question:
Suppose I trust some sidechain node that is publishing such an attestation.
Then the sidechain node is hacked or otherwise wishes to disrupt the network for its own purposes.
And it attests that a valid sidechain withdrawal is actually invalid.
What happens then?
To the point, suppose that the attestation private key is somehow leaked or determined by a third party that has incentive to disrupt the mainchain network.
And it seems to me that this can be used to force some number of nodes to fork themselves off the network.
This is dangerous as nodes may be monitoring the blockchain for time-sensitive events, such as Lightning Network theft attempts.
Making "fork off bad miners!" a regular occurrence seems dangerous to me.
Regards,
ZmnSCPxj
next prev parent reply other threads:[~2023-08-30 11:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 2:02 ryan
2023-08-19 14:35 ` Ruben Somsen
2023-08-19 18:58 ` ryan
2023-08-21 22:32 ` Ruben Somsen
2023-08-28 13:48 ` ZmnSCPxj
2023-08-28 14:35 ` ryan
2023-08-30 11:05 ` ZmnSCPxj [this message]
2023-08-31 0:16 ` ZmnSCPxj
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='E9WH5C46HJT_uwLTnliTeZSZPrPwoKQs57muUxPVzaGWCWWriC4m2HGVoagR8dfvRBU_1qGtvlhojqIf_854em3_bJIR6DzAqAGHR6fW_nI=@protonmail.com' \
--to=zmnscpxj@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=ryan@breen$(echo .)xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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