📅 Original date posted:2012-02-01
📝 Original message:Op 1 feb. 2012 10:48 schreef "Andy Parkins" <andyparkins at gmail.com> het
volgende:
>
> On 2012 January 31 Tuesday, Luke-Jr wrote:
>
> > Both BIP 16 and 17 are backward compatible enough that people can
continue
> > to use the old clients with each other. An upgrade is only required to
> > send to (or create/receive on) the new 3...-form addresses. That being
>
> Is that true? (I'm happy to be called wrong)
>
> It doesn't seem like it to me. The new transaction types will be
rejected by
> old clients won't they? They don't pass IsStandard().
IsStandard() is for accepting transactions into the memory pool.
Non-standard transactions are verified just fine when they are in the block
chain.
BIP16/17 both create transactions that, when interpreted as old scripts,
are valid. The only change to the protocol is that previously-valid
transactions become invalid. As long as a supermajority of miners enforce
the new rules, everyone can happily keep using their old bitcoin client.
They won't create the new transaction type, and don't accept them as
payment, but they will accept the new block chain.
If we do a breaking change to the protocol - such as adding a new
transaction type - ALL users must upgrade. Those who don't will see a fork
of the chain from before the first new-style transaction. That is not the
case now.
--
Pieter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20120201/a20b0ba6/attachment.html>;
Pieter Wuille [ARCHIVE] /
npub1tj…jtl6r
2023-06-07 03:02:41
in reply to nevent1q…qhqh
Author Public Key
npub1tjephawh7fdf6358jufuh5eyxwauzrjqa7qn50pglee4tayc2ntqcjtl6rSeen on
wss://relay.noswhere.comPublished at
2023-06-07 03:02:41Event JSON
{
"id": "bb44e673ef50bfd9ba3c8654a77ad12e43ea7e1cdf41c7fe454641d2e264dd50",
"pubkey": "5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6",
"created_at": 1686106961,
"kind": 1,
"tags": [
[
"e",
"c92e2a87aa2d3c7365eadb419b42aac76742888a43a9dd185e4a98ca6fda909f",
"",
"root"
],
[
"e",
"45d4fc9a550d7db10d610a250be2690c8055d1db7ede034019be826263e236ac",
"",
"reply"
],
[
"p",
"99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59"
]
],
"content": "📅 Original date posted:2012-02-01\n📝 Original message:Op 1 feb. 2012 10:48 schreef \"Andy Parkins\" \u003candyparkins at gmail.com\u003e het\nvolgende:\n\u003e\n\u003e On 2012 January 31 Tuesday, Luke-Jr wrote:\n\u003e\n\u003e \u003e Both BIP 16 and 17 are backward compatible enough that people can\ncontinue\n\u003e \u003e to use the old clients with each other. An upgrade is only required to\n\u003e \u003e send to (or create/receive on) the new 3...-form addresses. That being\n\u003e\n\u003e Is that true? (I'm happy to be called wrong)\n\u003e\n\u003e It doesn't seem like it to me. The new transaction types will be\nrejected by\n\u003e old clients won't they? They don't pass IsStandard().\n\nIsStandard() is for accepting transactions into the memory pool.\nNon-standard transactions are verified just fine when they are in the block\nchain.\n\nBIP16/17 both create transactions that, when interpreted as old scripts,\nare valid. The only change to the protocol is that previously-valid\ntransactions become invalid. As long as a supermajority of miners enforce\nthe new rules, everyone can happily keep using their old bitcoin client.\nThey won't create the new transaction type, and don't accept them as\npayment, but they will accept the new block chain.\n\nIf we do a breaking change to the protocol - such as adding a new\ntransaction type - ALL users must upgrade. Those who don't will see a fork\nof the chain from before the first new-style transaction. That is not the\ncase now.\n\n-- \nPieter\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20120201/a20b0ba6/attachment.html\u003e",
"sig": "0e0e901823df24e54625e5891a160bcf0f0249e8ad06b8f84c70454d68051f2b562dabe9ae6bf801b8059593b8b379bed487477e908934268a8677b70cbe231f"
}