If I had a time locked signed transaction where I threw away the key, this would potentially invalidate my transaction. What is the point of such a rule? On Wed, Apr 15, 2015 at 6:43 PM, s7r wrote: > Hi, > > Would it be wise to add a consensus rule like the one we have for blocks, > > (if > 75% from last 1000 blocks are version 'n' mark version 'n' as > standard for blocks and if > 95% from the last 1000 blocks are version > 'n' mark previous block versions as invalid) > > but for transaction versions? In simple terms, if > 75% from all the > transactions in the latest 1000 blocks are version 'n', mark all > previous transaction versions as non-standard and if > 95% from all the > transactions in the latest 1000 blocks are version 'n' mark all previous > transaction versions as invalid. > > At this moment, the standard in consensus is v1, but nothing is enforced > in the network related to transaction versions. > > Regarding BIP62, as it can be read here [0] it is said that it requires > v2 transactions. It is also said that transaction version 2 will be > skipped and jump directly to v3, for an even version for transactions > and blocks (?). Might as well add the rule for invalidating previous > transaction versions if the majority updates - could this break anything > or affect functionality in any way? > > BIP62 adds a newer transaction version which is optional and does not > mark previous v1 as non-standard or invalid. This means bitcoin core > will treat both v1 and v2/v3 transactions as standard and relay/mine > them with the same priority, regardless of the tx version? > > > Thanks. > > [0] > > https://bitcoin.stackexchange.com/questions/35904/how-much-of-bip-62-dealing-with-malleability-has-been-implemented > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live > exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- > event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >