<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Nov 1, 2015 at 6:46 PM, Tier Nolan via bitcoin-dev <span dir="ltr"><<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>For guidelines<br><br></div><div>* Transaction version numbers will be increased, if possible<br></div><div>* Transactions with unknown/large version numbers are unsafe to use with locktime<br></div><div>* Reasonable notice is given that the change is being contemplated<br></div><div>* Non-opt-in changes will only be to protect the integrity of the network<br><br>Locked transaction that can be validated without excessive load on the network should be safe to use, even if non-standard.<br></div><div><br></div><div>An OP_CAT script that requires TBs of RAM to validate crosses the threshold of reasonableness. <br></div><div></div></blockquote></div><br>I like those guidelines, although I'm sure there may be lots of arguing over what fits under "protects the integrity of the network" or what constitutes "reasonable notice" (publish a BIP at least 30 days before rolling out a change? 60 days? a year?)</div><div class="gmail_extra"><div><br></div>-- <br><div class="gmail_signature">--<br>Gavin Andresen<br></div><div class="gmail_signature"><br></div>
</div></div>