public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Greg Sanders <gsanders87@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transaction Replacement by Fee
Date: Thu, 12 Jan 2017 14:58:30 -0500	[thread overview]
Message-ID: <20170112195830.GA5663@savin.petertodd.org> (raw)
In-Reply-To: <CAB3F3DtJ3Hq5saz7fVd95bhi+Y84m6U1GuduHOGyXuhVwRaWeg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

On Thu, Jan 12, 2017 at 09:13:23AM -0500, Greg Sanders via bitcoin-dev wrote:
> BIP125 is the standard way to signal:
> https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
> 
> Should explain everything you need.

Additionally some miners mine full replace-by-fee, which has no limitations on
nSequence. My implementation (for v0.13.2) is here:

    https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.13.2

and is identical to Bitcoin Core modulo the nSequence stuff being removed, and
a special service bit added to allow full-rbf nodes to preferentially peer with
each other to make sure replacement transactions get propagated.

In practice full-RBF works fairly well, so while it's even faster to use the
nSequence signalling specified in BIP-125, doing so is not mandatory so long as
you can et your replacement transaction to a full-RBF node.

-- 
https://petertodd.org 'peter'[:-1]@petertodd.org

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2017-01-12 19:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 14:02 [bitcoin-dev] Transaction Replacement by Fee Police Terror
2017-01-12 14:13 ` Greg Sanders
2017-01-12 19:58   ` Peter Todd [this message]
2017-01-28 18:34     ` Andrew

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=20170112195830.GA5663@savin.petertodd.org \
    --to=pete@petertodd.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=gsanders87@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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