On Mon, Nov 04, 2013 at 01:16:49PM -0500, Peter Todd wrote: > You'll want to put some "reasonable" limit on actual path lengths, just > pick something like 32 levels; if applications pick their UUIDs honestly > a collision will be very unlikely. You can also make the allowed paths > block specific by defining them as H(uuid | nonce), with nonce as an
This could be H(uuid | nLockTime) Coinbase transactions still have a nLockTime, and while it's generally left at zero it can be any value valid for a transaction in the block. -- 'peter'[:-1]@petertodd.org 00000000000000086d6d5b17d979d44a24a68bcf92eb9aea18351e4f6bc485b6
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
