From: "Michael Grønager" <gronager@ceptacle•com>
To: Gregory Maxwell <gmaxwell@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] vtxPrev
Date: Wed, 5 Oct 2011 15:44:08 +0200 [thread overview]
Message-ID: <03BEA6AD-7EF2-41D0-91A3-D943A7B2964D@ceptacle.com> (raw)
In-Reply-To: <CAAS2fgRiM9SFGVtYU1GJM8U0z8aMecc3Ng9wM4SNWkE5_MKPwQ@mail.gmail.com>
Oups - I was reading the code wrongly - going through AddSupportingTransactions carefully again...
The vtxPrev contains a list of the supporting confirmations up to 3 confirmations back. So it is only of relevance (and only gets filled) if you accept coins that are less than 3 confirmations old. In this case you would like to resend the depending transactions to the network in case of chain splits.
This makes much more sense, but also, it is only of relevance when you accept newly earned coins. And it will only be of relevance for half an hour or so.
Cheers,
Michael
On 05/10/2011, at 14:50, Gregory Maxwell wrote:
> On Wed, Oct 5, 2011 at 8:31 AM, Michael Grønager <gronager@ceptacle•com> wrote:
>> The vtxPrev stores 3 transactions back, but as transactions need 7 block to maturity and respendability isn't it overkill - I mean it is highly unlikely that a transaction gets invalid after 7 confirmations and
>
> They don't need 7 blocks to maturity and respendability. The software
> will attempt to use older inputs when available but if not it will use
> what it has. It's also prone to respending its own outputs quickly
> because it reasonably trusts that it won't doublespend its own
> transactions.
>
> And, yes, if there is a deep split then its possible that inputs might
> have been spent differently in the new split. But it's not especially
> likely. Retransmitting one of your own txn's parents if its dropped
> but not yet impossible sounds prudent to me.
Michael Gronager, PhD
Owner Ceptacle / NDGF Director, NORDUnet A/S
Jens Juels Gade 33
2100 Copenhagen E
Mobile: +45 31 62 14 01
E-mail: gronager@ceptacle•com
prev parent reply other threads:[~2011-10-05 13:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 12:31 Michael Grønager
2011-10-05 12:50 ` Gregory Maxwell
2011-10-05 13:44 ` Michael Grønager [this message]
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=03BEA6AD-7EF2-41D0-91A3-D943A7B2964D@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gmaxwell@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