From: Jeff Garzik <jgarzik@bitpay•com>
To: Aaron Voisine <voisine@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Self-dependency transaction question...
Date: Sun, 13 Jul 2014 22:51:50 -0400 [thread overview]
Message-ID: <CAJHLa0OOBK8+eiU5jGaaicVzi9L5bY6W1XyfY2Mcv1C1DBCA0A@mail.gmail.com> (raw)
In-Reply-To: <CACq0ZD6Mo0uVMM8HU3VrYORQgme7z084B45Cap8GYVwi-xs6vA@mail.gmail.com>
On Sun, Jul 13, 2014 at 10:25 PM, Aaron Voisine <voisine@gmail•com> wrote:
> I believe tx have to be ordered sequentially within a block. Also
> since a tx is referenced by it's hash, it's practically impossible to
> make a self referential tx.
Correct. A TX will not reference a later TX in the same block (or itself).
This would be a good invalid-block test to add to the test suite. Any
volunteers?
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-07-14 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 23:32 Richard Moore
2014-07-14 2:25 ` Aaron Voisine
2014-07-14 2:51 ` Jeff Garzik [this message]
2014-07-14 11:18 ` Mike Hearn
2014-07-15 13:56 ` Paul Lyon
2014-07-14 20:51 ` Matt Whitlock
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=CAJHLa0OOBK8+eiU5jGaaicVzi9L5bY6W1XyfY2Mcv1C1DBCA0A@mail.gmail.com \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=voisine@gmail$(echo .)com \
/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