Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 60EEFC0032 for ; Wed, 30 Aug 2023 11:05:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 2E01241BEE for ; Wed, 30 Aug 2023 11:05:25 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 2E01241BEE Authentication-Results: smtp4.osuosl.org; dkim=pass (2048-bit key) header.d=protonmail.com header.i=@protonmail.com header.a=rsa-sha256 header.s=protonmail3 header.b=Yz0xKEwK X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.599 X-Spam-Level: X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEfBoK2PebYw for ; Wed, 30 Aug 2023 11:05:24 +0000 (UTC) Received: from mail-4319.protonmail.ch (mail-4319.protonmail.ch [185.70.43.19]) by smtp4.osuosl.org (Postfix) with ESMTPS id CFB1C407D7 for ; Wed, 30 Aug 2023 11:05:23 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org CFB1C407D7 Date: Wed, 30 Aug 2023 11:05:03 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1693393521; x=1693652721; bh=FlGb2KUtxHpzsGuvdNh40edkYAtEamAp0J0Ye0EC3G0=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=Yz0xKEwKPoTcUlUDAeMtn3+94vmJ3qdXUJJF99e3AaA0RKUhdcKVqC3AdnVR50tQn TihQq8iQi4dGCuEEM8nd9K/LbTEF45iRSuMri14ubimY+HDWyiACnbB47FAbJKmbXv kC70+5J+Q41uZYgOSUra+xOvbWERL/Fj2OY/SmGkNN9rs5ly3J4nH6jSTk7hCxoZNx 5mYDSBAGttuStLnhALklcXVJm9rZ/28qAf9ixDGA3MeT2bFB4SZ1tmFHW4HeBY8omy j2e6ZltSJTKwd1zQ0MDf4B2gRQgKAK19HtJ3SAj6o++dJh0IaRUKnYHVfjcRBzmqa9 cUDAMgmORgyGA== To: ryan@breen.xyz From: ZmnSCPxj Message-ID: In-Reply-To: <0D44C322-E2B4-4F80-A5D8-7D8304BDAE1A@breen.xyz> References: <2BFA7EE8-2E0E-45A3-AC11-8E57F99EC775@breen.xyz> <2FylpMx7IsZBt3ILxEt9pVB0Kq03jZqTUeLnB2hWT5j8qiB4o6plW3gjhBXQ_7p4MwQ_npQUpZ64hQaR6UnLhMNCnk_jCv1XObmrJbjrVqg=@protonmail.com> <0D44C322-E2B4-4F80-A5D8-7D8304BDAE1A@breen.xyz> Feedback-ID: 2872618:user:proton MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Sentinel Chains: A Novel Two-Way Peg X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Aug 2023 11:05:25 -0000 Good morning Ryan, > I appreciate your questions, ZmnSCPxj. >=20 > I will answer your second question first: Mainchain nodes do not ever val= idate sidechain blocks. Sidechain nodes watch Bitcoin for invalid withdrawa= ls, 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 networ= k 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 ne= twork. And it seems to me that this can be used to force some number of nodes to f= ork themselves off the network. This is dangerous as nodes may be monitoring the blockchain for time-sensit= ive events, such as Lightning Network theft attempts. Making "fork off bad miners!" a regular occurrence seems dangerous to me. Regards, ZmnSCPxj