📅 Original date posted:2017-04-14
📝 Original message:On Fri, Apr 14, 2017 at 2:20 PM, Tom Zander via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> On Friday, 14 April 2017 09:56:31 CEST Gregory Maxwell via bitcoin-dev
> wrote:
>> Segwit was carefully engineered so that older unmodified miners could
>> continue operating _completely_ without interruption after segwit
>> activates.
>
>
>> They [Older nodes] can
>> upgrade to it [segwit] on their own schedule. The only risk
>> non-participating
>> miners take after segwit activation is that if someone else mines an
>> invalid block they would extend it,
>
> This is false,
>
> a segwit transaction to the miner you describe is an "everyone can spend"
> transaction, and as such a miner that does not validate the segregated area
> in a post-segwit world will be able to create blocks that will not validate
> for segwit miners by including a transaction that spends a SW tx.
>
> This would then lead to a chain-fork as the SW miners reject it and the non-
> SW miners continue to mine on it.
This is false,
Those "everyone can spend" transactions are prohibited from being
mined due to policy rules. The risk is only in regards to mining on
top of an invalid block that intentionally mined an invalid SW
transaction.
>
>
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
James Hilliard [ARCHIVE] /
npub10r…kgk2d
2023-06-07 18:00:04
in reply to nevent1q…ks04
Author Public Key
npub10r9d6edmnrljk59wsf06zqp494l3qtjpa3w245hy6t5euqxlzw2qdkgk2dSeen on
wss://relay.nostr.bandPublished at
2023-06-07 18:00:04Event JSON
{
"id": "98c2f8d7c9aaadf7c6ab39ccedaab485cfc16d28a48766b62712fbbadf83bd34",
"pubkey": "78cadd65bb98ff2b50ae825fa100352d7f102e41ec5caad2e4d2e99e00df1394",
"created_at": 1686160804,
"kind": 1,
"tags": [
[
"e",
"5d1e64c970da07b0178aa4b0869114a6c0b54023e99bc79f83d180601afc646b",
"",
"root"
],
[
"e",
"2bfc5ae3605ca6987aa339e46528166f0b9a7e55e2847813d10557c73b16db47",
"",
"reply"
],
[
"p",
"dcb947d818dbfd7cf0baf26c0d5eb606b5a32336c5483fb53e05146315833ca7"
]
],
"content": "📅 Original date posted:2017-04-14\n📝 Original message:On Fri, Apr 14, 2017 at 2:20 PM, Tom Zander via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e On Friday, 14 April 2017 09:56:31 CEST Gregory Maxwell via bitcoin-dev\n\u003e wrote:\n\u003e\u003e Segwit was carefully engineered so that older unmodified miners could\n\u003e\u003e continue operating _completely_ without interruption after segwit\n\u003e\u003e activates.\n\u003e\n\u003e\n\u003e\u003e They [Older nodes] can\n\u003e\u003e upgrade to it [segwit] on their own schedule. The only risk\n\u003e\u003e non-participating\n\u003e\u003e miners take after segwit activation is that if someone else mines an\n\u003e\u003e invalid block they would extend it,\n\u003e\n\u003e This is false,\n\u003e\n\u003e a segwit transaction to the miner you describe is an \"everyone can spend\"\n\u003e transaction, and as such a miner that does not validate the segregated area\n\u003e in a post-segwit world will be able to create blocks that will not validate\n\u003e for segwit miners by including a transaction that spends a SW tx.\n\u003e\n\u003e This would then lead to a chain-fork as the SW miners reject it and the non-\n\u003e SW miners continue to mine on it.\n\nThis is false,\n\nThose \"everyone can spend\" transactions are prohibited from being\nmined due to policy rules. The risk is only in regards to mining on\ntop of an invalid block that intentionally mined an invalid SW\ntransaction.\n\u003e\n\u003e\n\u003e --\n\u003e Tom Zander\n\u003e Blog: https://zander.github.io\n\u003e Vlog: https://vimeo.com/channels/tomscryptochannel\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "06d299694d9f45b2d795e7ee6aa8905e799d76552f96b5eaa085c631ae6a8dc8d63e116575a3752896100022dd968c0b21fe26b36d41281e778811801bbe39bc"
}