From: Greg Sanders <gsanders87@gmail.com>
To: Police Terror <PoliceTerror@dyne.org>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Transaction Replacement by Fee
Date: Thu, 12 Jan 2017 09:13:23 -0500 [thread overview]
Message-ID: <CAB3F3DtJ3Hq5saz7fVd95bhi+Y84m6U1GuduHOGyXuhVwRaWeg@mail.gmail.com> (raw)
In-Reply-To: <2ac49fb0-ff79-5cb9-7b92-14ec791ecc45@dyne.org>
[-- Attachment #1: Type: text/plain, Size: 845 bytes --]
BIP125 is the standard way to signal:
https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki
Should explain everything you need.
On Thu, Jan 12, 2017 at 9:02 AM, Police Terror via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello,
>
> Where can I find the rules on transaction replacement?
>
> For instance what are the valid ranges for the sequence values in
> transaction inputs? Normally I set this value to MAX_UINT32, and the
> locktime to 0.
>
> Can I change the outputs? Can I add more inputs to pay a higher fee?
>
> Just looking for clarity on this aspect of Bitcoin. Any resources would
> be much appreciated.
>
> Thanks.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1504 bytes --]
next prev parent reply other threads:[~2017-01-12 14:13 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 [this message]
2017-01-12 19:58 ` Peter Todd
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=CAB3F3DtJ3Hq5saz7fVd95bhi+Y84m6U1GuduHOGyXuhVwRaWeg@mail.gmail.com \
--to=gsanders87@gmail.com \
--cc=PoliceTerror@dyne.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/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