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-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_--