From: Peter Todd <pete@petertodd.org>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: bitcoin-development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Re-enabling simple tx replacement
Date: Sun, 4 Jan 2015 12:47:36 -0500 [thread overview]
Message-ID: <20150104174736.GA17628@savin.petertodd.org> (raw)
In-Reply-To: <CAAS2fgROnDRbzNubLa588mXRJR4jwEBotvQi5bFm5dnNQxiwTA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Sun, Jan 04, 2015 at 05:44:59PM +0000, Gregory Maxwell wrote:
> On Sun, Jan 4, 2015 at 5:35 PM, Gregory Maxwell <gmaxwell@gmail.com> wrote:
> > Can you send me the actual raw transaction (that site doesn't appear
> > have a way to get it, only some cooked json output; which doesn't
> > include the sequence number).
>
> Nevermind, I guess. I think I figured out your problem: The behaviour
> on testnet is busted because the non-mempooling is enforced by
> IsStandardTx which is bypassed in testnet. We should enforce that
> elsewhere.
>
> This isn't the case on the real network.
Yup.
I have a pull-req open to fix this:
https://github.com/bitcoin/bitcoin/pull/5521
--
'peter'[:-1]@petertodd.org
00000000000000000237ec84e4b02efbdf3bcbf62308c873da802caedd12432f
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 650 bytes --]
next prev parent reply other threads:[~2015-01-04 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 14:43 [Bitcoin-development] Re-enabling simple tx replacement Ross Nicoll
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 [this message]
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=20150104174736.GA17628@savin.petertodd.org \
--to=pete@petertodd.org \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@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