From: Alan Reiner <etotheipi@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Trusted identities
Date: Thu, 26 Apr 2012 14:00:59 -0400 [thread overview]
Message-ID: <4F998D5B.9070708@gmail.com> (raw)
In-Reply-To: <20120426173000.GB16099@savin.lan>
[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]
On 04/26/2012 01:30 PM, Peter Todd wrote:
>
>> More difficulty shortens the safe time we can transact large volumes in,
>> which is good for the network.
>>
>> I'm not sure of the current implementation of replacement transactions, can
>> anyone on the core team speak to this? Can I replace transactions, or is
>> that part of the spec unimplemented or deprecated right now?
> My understanding is it's completely disabled.
Went on a scavenger hunt with Gavin a couple weeks concerning tx
replacement. The conclusion was that if,
(1) Transaction has lock-time in the future AND
(2) Transaction has non-maximum sequence number
Then the transaction will both propagate and be accepted into nodes'
memory pools, but will not go into any block until locktime expires. If
the lock-time is in the past OR sequence number on all TxIns is
0xffffffff, then it will be immediately valid and included in the
blockchain.
But the actual "replacement" mechanism is disabled. Therefore, the
nodes accept the tx as if it's replaceable, but don't allow it to be
replaced. This means that it is effectively replaceable *once*, but
only if you inject a final transaction into the blockchain. You can't
broadcast a final version of the same tx, because it will conflict with
the non-final one sitting in all the other nodes' memory pools. You
need a miner to agree to remove the non-final tx from their memory pool
and specifically include your replacement.
-Alan
[-- Attachment #2: Type: text/html, Size: 2059 bytes --]
next prev parent reply other threads:[~2012-04-26 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 15:49 Peter Todd
2012-04-26 17:11 ` Peter Vessenes
2012-04-26 17:30 ` Peter Todd
2012-04-26 18:00 ` Alan Reiner [this message]
2012-04-26 17:59 ` Amir Taaki
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=4F998D5B.9070708@gmail.com \
--to=etotheipi@gmail$(echo .)com \
--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