From: Ross Nicoll <jrn@jrn•me.uk>
To: bitcoin-development <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] Re-enabling simple tx replacement
Date: Sun, 04 Jan 2015 14:43:05 +0000 [thread overview]
Message-ID: <54A95179.2070200@jrn.me.uk> (raw)
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
next reply other threads:[~2015-01-04 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 14:43 Ross Nicoll [this message]
2015-01-04 17:04 ` Gregory Maxwell
2015-01-04 17:22 ` Ross Nicoll
2015-01-04 17:35 ` Gregory Maxwell
2015-01-04 17:44 ` Gregory Maxwell
2015-01-04 17:47 ` Peter Todd
2015-01-04 18:11 ` Ross Nicoll
2015-01-04 18:31 ` Gregory Maxwell
2015-01-04 23:06 ` Jorge Timón
2015-01-04 17:45 ` Ross Nicoll
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54A95179.2070200@jrn.me.uk \
--to=jrn@jrn$(echo .)me.uk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox