summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Carman <benthecarman@live.com>2021-06-28 10:55:30 +0000
committerbitcoindev <bitcoindev@gnusha.org>2021-06-28 10:55:33 +0000
commit8cc261918b17cb1f28c0e6e6faa3e727698cf746 (patch)
tree7d251a4b093a3c1b6c072e3872caea2765ecfb81
parent9f9c05ff10c4830bfc419a7ca80a1c79ec74f8d8 (diff)
downloadpi-bitcoindev-8cc261918b17cb1f28c0e6e6faa3e727698cf746.tar.gz
pi-bitcoindev-8cc261918b17cb1f28c0e6e6faa3e727698cf746.zip
Re: [bitcoin-dev] BIP proposal: Anti-fee-sniping protection with nSequence in taproot transactions to improve privacy for off-chain protocols
-rw-r--r--2f/e3a2800bfb9b2bc2d34c452058b7a4476e0459194
1 files changed, 194 insertions, 0 deletions
diff --git a/2f/e3a2800bfb9b2bc2d34c452058b7a4476e0459 b/2f/e3a2800bfb9b2bc2d34c452058b7a4476e0459
new file mode 100644
index 000000000..f3c197aab
--- /dev/null
+++ b/2f/e3a2800bfb9b2bc2d34c452058b7a4476e0459
@@ -0,0 +1,194 @@
+Return-Path: <benthecarman@live.com>
+Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137])
+ by lists.linuxfoundation.org (Postfix) with ESMTP id 69B85C000E
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Mon, 28 Jun 2021 10:55:33 +0000 (UTC)
+Received: from localhost (localhost [127.0.0.1])
+ by smtp4.osuosl.org (Postfix) with ESMTP id 57F4D4031C
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Mon, 28 Jun 2021 10:55:33 +0000 (UTC)
+X-Virus-Scanned: amavisd-new at osuosl.org
+X-Spam-Flag: NO
+X-Spam-Score: -2.101
+X-Spam-Level:
+X-Spam-Status: No, score=-2.101 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,
+ HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
+ RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
+ autolearn=ham autolearn_force=no
+Authentication-Results: smtp4.osuosl.org (amavisd-new);
+ dkim=pass (2048-bit key) header.d=live.com
+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 SHdu8TOfC89F
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Mon, 28 Jun 2021 10:55:32 +0000 (UTC)
+X-Greylist: whitelisted by SQLgrey-1.8.0
+Received: from NAM12-BN8-obe.outbound.protection.outlook.com
+ (mail-bn8nam12olkn2090.outbound.protection.outlook.com [40.92.21.90])
+ by smtp4.osuosl.org (Postfix) with ESMTPS id 37A054031B
+ for <bitcoin-dev@lists.linuxfoundation.org>;
+ Mon, 28 Jun 2021 10:55:32 +0000 (UTC)
+ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
+ b=CyiZH0VAzjHi9BkKFJG7bukTWsPWX1vHWBdyvDvsguR17uGbYzJmba8QgKwP6dbrvnsN1TwLDbwT3qDxfRY19jJxBzWTkqkzi4zazqzvIgad7Qp+1vkK+7pX9kxl096wl7Edy2tTNgWSfOMvs009pdIca51o5uPwexatEKi889qw+Y9vVWzhtWlUJVJMTlZgaideOoVslymTlaEQkvS6AiFA3cLACUVjm1nBTdCXAFc1NBYh9WEyjUj9SKqKKQLwwQ9BOMwzmeFBsBeIdDl9sZqX07bzO4RTVBsRKzXmOv0TH+XaRp/A2TiIHhrsFMnN5Vf9mmn+k/SeXlfcTv+G6Q==
+ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
+ s=arcselector9901;
+ h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
+ bh=yf12Zy8TE67EGRM5+oU9YLzWruyH53FIRSemaAFUcXE=;
+ b=MXbbhk8obG405NMuE3P2rED9rdzQ7lODzvGMxQQtNNFhAQAWluOnYzSsYmE7I3RlTU1E7McztB+4Pqa5rwwdgc9ME58fjKZ37MNXtuzja5syaOzcSZhOKSA3TLLRddJECraWYxH4Rautz6PVuaVPbR7tTtJAGBDtKCpnGXYfmkXPo5PEr8xSHNslH0iCugqS7+gDiYjVOyuhgiqJUwmHtl0llEVuOozvBvUXsdIHhKH9v6bRstRR3j3pOZvovKunKIDxu/aOCtLutVyqdJn3q2Bsv/Xv5SjXtLm1evpeFAUQT06JrwNGT1plJiTcEkmh4olscNNTwrC9AdG/izV+Jw==
+ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=none; dmarc=none;
+ dkim=none; arc=none
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=live.com; s=selector1;
+ h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
+ bh=yf12Zy8TE67EGRM5+oU9YLzWruyH53FIRSemaAFUcXE=;
+ b=PurIB5RrYKu/C//+NiE+RUE2r/V24NQVILiQsUyzJ3/DN2QtIz47qp7rVEFL4N3Gcm0WoPoOMcJ/bovyu8hbx1cyzny9Kl9mGUBTFu97wx2KiV8zXfvoDQI4MGMO27nmEjEjudtUDeC7hejiMrVNf9lHU+XuYuH0PbuplimZ++3jXt0sBC2OJDVaIj34D+g2bTFwPpYBb+JQmm5xUEDSCi4k+XhMI60eLztKGC70Qbg2amxw68NdsGHlk/EmCbvuNo3Vl1AljrNxdcCnqWRSdPErQ9ZUOAMU+L7HSEg53qZjk6OPuBURrzEFCZn1xhROi6+JfDKRXVLuQlR9ctVcKw==
+Received: from MW2NAM12FT034.eop-nam12.prod.protection.outlook.com
+ (2a01:111:e400:fc65::4d) by
+ MW2NAM12HT105.eop-nam12.prod.protection.outlook.com (2a01:111:e400:fc65::139)
+ with Microsoft SMTP Server (version=TLS1_2,
+ cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4287.8; Mon, 28 Jun
+ 2021 10:55:30 +0000
+Received: from SJ0PR10MB4719.namprd10.prod.outlook.com
+ (2a01:111:e400:fc65::4c) by MW2NAM12FT034.mail.protection.outlook.com
+ (2a01:111:e400:fc65::182) with Microsoft SMTP Server (version=TLS1_2,
+ cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4287.8 via Frontend
+ Transport; Mon, 28 Jun 2021 10:55:30 +0000
+Received: from SJ0PR10MB4719.namprd10.prod.outlook.com
+ ([fe80::a05c:77:88c0:471f]) by SJ0PR10MB4719.namprd10.prod.outlook.com
+ ([fe80::a05c:77:88c0:471f%2]) with mapi id 15.20.4264.026; Mon, 28 Jun 2021
+ 10:55:30 +0000
+From: Ben Carman <benthecarman@live.com>
+To: "bitcoin-dev@lists.linuxfoundation.org"
+ <bitcoin-dev@lists.linuxfoundation.org>
+Thread-Topic: BIP proposal: Anti-fee-sniping protection with nSequence in
+ taproot transactions to improve privacy for off-chain protocols
+Thread-Index: AQHXbAwczrbLrg1n2Ey1kEZihRiJxw==
+Date: Mon, 28 Jun 2021 10:55:30 +0000
+Message-ID: <SJ0PR10MB4719291762199CECE5798AF1A1039@SJ0PR10MB4719.namprd10.prod.outlook.com>
+References: <mailman.96927.1623334755.32591.bitcoin-dev@lists.linuxfoundation.org>
+In-Reply-To: <mailman.96927.1623334755.32591.bitcoin-dev@lists.linuxfoundation.org>
+Accept-Language: en-US
+Content-Language: en-US
+X-MS-Has-Attach:
+X-MS-TNEF-Correlator:
+x-incomingtopheadermarker: OriginalChecksum:B99DD11BF30A51531BF74A797557D2970053F1A7FEF619456022B56CA8812161;
+ UpperCasedChecksum:11556712E750F125B9833B3C0090ECDC90A9F69C88B8CD0607B39DECB089E327;
+ SizeAsReceived:7171; Count:44
+x-ms-exchange-messagesentrepresentingtype: 1
+x-tmn: [+XIGx69mlS+BcYgKOYWwoO+nDg00Gh7q]
+x-ms-publictraffictype: Email
+x-incomingheadercount: 44
+x-eopattributedmessage: 0
+x-ms-office365-filtering-correlation-id: 42ffd33e-94a0-4812-ede9-08d93a233f14
+x-ms-traffictypediagnostic: MW2NAM12HT105:
+x-microsoft-antispam: BCL:0;
+x-microsoft-antispam-message-info: iH6+E9Xf8/onuuWM1SXEG1oyu6muYmtlnb9EdvD5cFInRPCH28U2rTk2E/k75S5zgX8xfpEsZUP2m6Elkj1UixFQ1dhWv84i4qC5DCyMqUCA/GcP5kfd9lPNOA2zFhcPbs4nqghpNFYykFPstdffOBoahchazNRJrw96eI4nPQ+l4uCd3Y+ShbgcVUfd6CxoGvEMn2tmP1ii3mH5M5DaSNxK6nKJPcEiisv2nme8xIme9Nm+m3bmuBI3RA2uC0+fpUtlolO5FHDXmkU9Wjk5/8URSO79bJW+VK9lfW00tslegJGi2iektDnEXmCYMz0I62EC24Eu3vHXTU6XH2sVfwNz/DLjshUoShWibBy9FmFtR8BphIEoR5M62msJEjFXm9/2Tus0UXIgl0LmoHadAw9fd60UzpZcNRNsvs61cgfFRZ8L8venAOBZZhwuAsEx
+x-ms-exchange-antispam-messagedata: Nb0RXzM9AaA+BFpk3vcxn7MOw+BjXwUeOJqB3zj3HlMwi5MEVEEE3YbhJhn+QKXz6cDdPZeC3uUInxuXfflpY0vWIe4w3LODW1xUANoaT2Fn2PnizU+sqpu6RNIVU5RxmXG3eiJWfaljUg7+10akKw==
+x-ms-exchange-transport-forked: True
+Content-Type: multipart/alternative;
+ boundary="_000_SJ0PR10MB4719291762199CECE5798AF1A1039SJ0PR10MB4719namp_"
+MIME-Version: 1.0
+X-OriginatorOrg: live.com
+X-MS-Exchange-CrossTenant-AuthAs: Anonymous
+X-MS-Exchange-CrossTenant-AuthSource: MW2NAM12FT034.eop-nam12.prod.protection.outlook.com
+X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
+X-MS-Exchange-CrossTenant-Network-Message-Id: 42ffd33e-94a0-4812-ede9-08d93a233f14
+X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Jun 2021 10:55:30.5730 (UTC)
+X-MS-Exchange-CrossTenant-fromentityheader: Internet
+X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
+X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
+X-MS-Exchange-Transport-CrossTenantHeadersStamped: MW2NAM12HT105
+X-Mailman-Approved-At: Mon, 28 Jun 2021 10:57:35 +0000
+Subject: Re: [bitcoin-dev] BIP proposal: Anti-fee-sniping protection with
+ nSequence in taproot transactions to improve privacy for off-chain
+ protocols
+X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
+X-Mailman-Version: 2.1.15
+Precedence: list
+List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
+List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
+List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
+List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
+List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
+List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
+ <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
+X-List-Received-Date: Mon, 28 Jun 2021 10:55:33 -0000
+
+--_000_SJ0PR10MB4719291762199CECE5798AF1A1039SJ0PR10MB4719namp_
+Content-Type: text/plain; charset="Windows-1252"
+Content-Transfer-Encoding: quoted-printable
+
+> If nSequence is set it should apply only to the first input of the
+transaction, if it has multiple inputs.
+
+This could have complications with DLCs and dual funded lightning. In both =
+protocols the ordering of the inputs is not know until both parties have re=
+vealed all of their inputs, and during the reveal the nSequence is given. =
+If we want DLCs and dual funded lightning to be compatible it would be bett=
+er to have it define it as =93at least one of the inputs of the transaction=
+=94 instead of =93it should apply only to the first input of the transactio=
+n=94
+
+benthecarman
+
+
+--_000_SJ0PR10MB4719291762199CECE5798AF1A1039SJ0PR10MB4719namp_
+Content-Type: text/html; charset="Windows-1252"
+Content-Transfer-Encoding: quoted-printable
+
+<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
+hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
+fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
+<head>
+<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
+252">
+<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
+<style><!--
+/* Font Definitions */
+@font-face
+ {font-family:"Cambria Math";
+ panose-1:2 4 5 3 5 4 6 3 2 4;}
+@font-face
+ {font-family:Calibri;
+ panose-1:2 15 5 2 2 2 4 3 2 4;}
+/* Style Definitions */
+p.MsoNormal, li.MsoNormal, div.MsoNormal
+ {margin:0in;
+ font-size:11.0pt;
+ font-family:"Calibri",sans-serif;}
+.MsoChpDefault
+ {mso-style-type:export-only;}
+@page WordSection1
+ {size:8.5in 11.0in;
+ margin:1.0in 1.0in 1.0in 1.0in;}
+div.WordSection1
+ {page:WordSection1;}
+--></style>
+</head>
+<body lang=3D"EN-US" link=3D"blue" vlink=3D"#954F72" style=3D"word-wrap:bre=
+ak-word">
+<div class=3D"WordSection1">
+<p class=3D"MsoNormal">&gt; If nSequence is set it should apply only to the=
+ first input of the<br>
+transaction, if it has multiple inputs.<o:p></o:p></p>
+<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
+<p class=3D"MsoNormal">This could have complications with DLCs and dual fun=
+ded lightning. In both protocols the ordering of the inputs is not know unt=
+il both parties have revealed all of their inputs, and during the reveal th=
+e nSequence is given.&nbsp; If we want
+ DLCs and dual funded lightning to be compatible it would be better to have=
+ it define it as =93at least one of the inputs of the transaction=94 instea=
+d of =93it should apply only to the first input of the transaction=94<o:p><=
+/o:p></p>
+<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
+<p class=3D"MsoNormal">benthecarman<br>
+<br>
+</p>
+</div>
+</body>
+</html>
+
+--_000_SJ0PR10MB4719291762199CECE5798AF1A1039SJ0PR10MB4719namp_--
+