From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Y7mOh-0000S6-Vw for bitcoin-development@lists.sourceforge.net; Sun, 04 Jan 2015 14:43:16 +0000 X-ACL-Warn: Received: from s3.neomailbox.net ([178.209.62.157]) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Y7mOe-0007xT-QC for bitcoin-development@lists.sourceforge.net; Sun, 04 Jan 2015 14:43:15 +0000 Message-ID: <54A95179.2070200@jrn.me.uk> Date: Sun, 04 Jan 2015 14:43:05 +0000 From: Ross Nicoll User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: bitcoin-development Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1Y7mOe-0007xT-QC Subject: [Bitcoin-development] Re-enabling simple tx replacement 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: Sun, 04 Jan 2015 14:43:16 -0000 Dear all, I've been looking at atomic cross-chain trading ( https://en.bitcoin.it/wiki/Atomic_cross-chain_trading ) between the Bitcoin and Dogecoin blockchains, and have a mostly functional prototype. However as it stands if the refund transaction is relayed before the actual spend transaction, it "blocks" the legitimate spend transaction from being accepted into the memory pool. I'd like to enable TX replacement in the case where all conflicting transactions are not final, and the replacement is final. While yes, this still leaves scope for "unpaid for" bandwidth, hopefully being able to do a single replacement isn't a major issue. For those wanting background on this, https://github.com/bitcoin/bitcoin/pull/2516 may be useful reading. I've drafted a patch for this https://github.com/rnicoll/bitcoin/commit/e668d36607f008990ccaac7275e463a6efdd9b5a but have not yet raised a PR, as historically this has lead to a lot of discussion in Github which is better suited to this mailing list. I'm therefore looking for feedback while I continue testing that patch, and any comments would be welcomed. Ross