On Wed, Oct 5, 2011 at 8:31 AM, Michael Grønager <grona...@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. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
