<div dir="ltr">On Wed, May 13, 2015 at 1:27 PM, Tier Nolan <span dir="ltr"><<a href="mailto:tier.nolan@gmail.com" target="_blank">tier.nolan@gmail.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>After more thought, I think I came up with a clearer description of the recursive version.<br><br>The simple definition is that the hash for the new signature opcode should simply assume that the normalized txid system was used since the beginning. All txids in the entire blockchain should be replaced with the "correct" values.<br><br>This requires a full re-index of the blockchain. You can't work out
what the TXID-N of a transaction is without knowning the TXID-N of its
parents, in order to do the replacement.<br><br>The non-recursive version can only handle refunds one level deep.<br></div></div></blockquote><div><br></div><div>This was what I was suggesting all along, sorry if I wasn't clear.<br><br>-- <br></div><div>Pieter<br> <br></div></div></div></div>