📅 Original date posted:2015-11-02
📝 Original message:On Sun, Nov 1, 2015 at 6:46 PM, Tier Nolan via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> For guidelines
>
> * Transaction version numbers will be increased, if possible
> * Transactions with unknown/large version numbers are unsafe to use with
> locktime
> * Reasonable notice is given that the change is being contemplated
> * Non-opt-in changes will only be to protect the integrity of the network
>
> Locked transaction that can be validated without excessive load on the
> network should be safe to use, even if non-standard.
>
> An OP_CAT script that requires TBs of RAM to validate crosses the
> threshold of reasonableness.
>
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?)
--
--
Gavin Andresen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151102/193dffef/attachment.html>;
Gavin Andresen [ARCHIVE] /
npub1s4…d44kw
2023-06-07 17:44:02
in reply to nevent1q…wzag
Author Public Key
npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kwPublished at
2023-06-07 17:44:02Event JSON
{
"id": "81fb73a497fbd51fafe31cb9f2600473c3c0612bb12439b17e6f6427c788d1aa",
"pubkey": "857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4",
"created_at": 1686159842,
"kind": 1,
"tags": [
[
"e",
"6fa3af2048f82399a81c9ef5aa9a6d88ff6b14b545801828e83f0dab2f1294d8",
"",
"root"
],
[
"e",
"d71208ffb986bec90f228dac64d70c54ae9da45a4ac5e453417239f03e46850b",
"",
"reply"
],
[
"p",
"b2b39b6f2c86908d3da9f500193abd5757b21cac328f838800a48c4d557c10dd"
]
],
"content": "📅 Original date posted:2015-11-02\n📝 Original message:On Sun, Nov 1, 2015 at 6:46 PM, Tier Nolan via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e For guidelines\n\u003e\n\u003e * Transaction version numbers will be increased, if possible\n\u003e * Transactions with unknown/large version numbers are unsafe to use with\n\u003e locktime\n\u003e * Reasonable notice is given that the change is being contemplated\n\u003e * Non-opt-in changes will only be to protect the integrity of the network\n\u003e\n\u003e Locked transaction that can be validated without excessive load on the\n\u003e network should be safe to use, even if non-standard.\n\u003e\n\u003e An OP_CAT script that requires TBs of RAM to validate crosses the\n\u003e threshold of reasonableness.\n\u003e\n\nI like those guidelines, although I'm sure there may be lots of arguing\nover what fits under \"protects the integrity of the network\" or what\nconstitutes \"reasonable notice\" (publish a BIP at least 30 days before\nrolling out a change? 60 days? a year?)\n\n-- \n--\nGavin Andresen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20151102/193dffef/attachment.html\u003e",
"sig": "87bedad045adfc87c6add420d079eb94faae96c06cdf0d4182fa75c3f60af4267e08f5ba6f783c866ecf65f208e9d818b4e1515fb0dcabfdff5e9493aa51e684"
}