From: Mike Hearn <mike@plan99.net>
To: Richard Moore <me@ricmoo.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Self-dependency transaction question...
Date: Mon, 14 Jul 2014 13:18:22 +0200 [thread overview]
Message-ID: <CANEZrP3RfYRoiwg_f9K0sf=vvpY=Wx78Q97Qp8uosK1GPV9QRg@mail.gmail.com> (raw)
In-Reply-To: <35E6FF51-F9C4-4973-8489-B364E7C27C14@ricmoo.com>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Conceptually all transactions in the block chain lie on a single timeline.
The fact that we quantise that timeline into blocks is in many ways neither
here nor there - it's still a strict line.
What *can* happen and you must be aware of is duplicated transactions.
Satoshi sort of assumed this could never happen because everything is hash
based, but forgot that duplicating coinbases is possible and at one point
this did happen. It was banned by a rule change afterwards but you still
must be able to process the older parts of the chain that have this. There
is a BIP that covers the new rule.
[-- Attachment #2: Type: text/html, Size: 748 bytes --]
next prev parent reply other threads:[~2014-07-14 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-13 23:32 [Bitcoin-development] Self-dependency transaction question Richard Moore
2014-07-14 2:25 ` Aaron Voisine
2014-07-14 2:51 ` Jeff Garzik
2014-07-14 11:18 ` Mike Hearn [this message]
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='CANEZrP3RfYRoiwg_f9K0sf=vvpY=Wx78Q97Qp8uosK1GPV9QRg@mail.gmail.com' \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=me@ricmoo.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