From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z60R8-0003tL-7Z for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 17:50:42 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com designates 209.85.214.181 as permitted sender) client-ip=209.85.214.181; envelope-from=jgarzik@bitpay.com; helo=mail-ob0-f181.google.com; Received: from mail-ob0-f181.google.com ([209.85.214.181]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z60R7-0002oB-AT for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 17:50:42 +0000 Received: by obctg8 with SMTP id tg8so79207906obc.3 for ; Fri, 19 Jun 2015 10:50:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=MGRCL1ArlZbJktX3zYnDgUqYaQr4iqwYsELIYCvwVoQ=; b=Tc3ivZtB60yUxSRTwO5uF6B1uv97odwnjHnnVUVw8/eIN/2YNpcFtyzIJtW8S2uL98 EeLeNcuihHc7+GyIGtbJu9pW5FRu0SUbHqRDak2E7rmQGZ5Rxlcz5om0IpKXtAtHwSd6 K1d2OwJ7UHmcJm/hL+b02jkeMoYcJ/L56cQDKrWCCbGpxGbhJfLIH55558ZdtRelH4gu ypyMi44MXhFZYViwPlXP75dzpzbxjU8TbQifW+zKe/U56I/h9+wuE8YoG39px6hBVsLL X4p/KPR12KSIYyRU/KQBw83MftwSpjUG4yQYazBZfQ7dbZu6WVgt2ORL2ShX+f/lM1AI x00Q== X-Gm-Message-State: ALoCoQn0yAptVrHEloJogDxykmbXp7/lXiA7Rp14YafPS+GeJAL+h5GoUm6tV97cgwbx+SCTvlsU X-Received: by 10.202.55.7 with SMTP id e7mr13793181oia.56.1434736235899; Fri, 19 Jun 2015 10:50:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.108.149 with HTTP; Fri, 19 Jun 2015 10:50:15 -0700 (PDT) In-Reply-To: References: <20150619103959.GA32315@savin.petertodd.org> <04CE3756-B032-464C-8FBD-7ACDD1A3197D@gmail.com> <812d8353e66637ec182da31bc0a9aac1@riseup.net> <1727885.UUNByX4Jyd@crushinator> <15ea02cb53046dbe363d5d4876becb6d@riseup.net> From: Jeff Garzik Date: Fri, 19 Jun 2015 10:50:15 -0700 Message-ID: To: Justus Ranvier Content-Type: multipart/alternative; boundary=001a113cea26b005f90518e28f8a X-Spam-Score: -0.4 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.2 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1Z60R7-0002oB-AT Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2015 17:50:42 -0000 --001a113cea26b005f90518e28f8a Content-Type: text/plain; charset=UTF-8 On Fri, Jun 19, 2015 at 10:48 AM, wrote: > On 2015-06-19 17:40, Jeff Garzik wrote: > >> Making multiple incompatible versions of a spend is a -requirement- of >> various refund contract protocols. >> > > Is there not a dedicated field in a transaction (nSequence) for express > purpose of indicating when a protocol like this is in use? > No. You cannot know which is the 'right' or wrong transaction. One tx has obvious nSequence adjustments, the other - the refund transaction - may not. -- Jeff Garzik Bitcoin core developer and open source evangelist BitPay, Inc. https://bitpay.com/ --001a113cea26b005f90518e28f8a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Fri, Jun 19, 2015 at 10:48 AM, <<= a href=3D"mailto:justusranvier@riseup.net" target=3D"_blank">justusranvier@= riseup.net> wrote:
On 2015-06= -19 17:40, Jeff Garzik wrote:
Making multiple incompatible versions of a spend is a -requirement- of
various refund contract protocols.

 Is there not a dedicated field in a transaction (nSequence) for express pur= pose of indicating when a protocol like this is in use?

No.=C2=A0 You cannot know which is the 'right' or = wrong transaction.=C2=A0 One tx has obvious nSequence adjustments, the othe= r - the refund transaction - may not.

--
Jeff Garzik
Bitcoin core developer and open s= ource evangelist
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0https://bitpay.com/
--001a113cea26b005f90518e28f8a--