📅 Original date posted:2018-11-21
📝 Original message:Anthony Towns via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org>
writes:
> Given this implementation, NOINPUT effectively implies ANYONECANPAY,
> I think. (I think that is also true of BIP 118's NOINPUT spec)
I mentioned this in my reply to Pieter, but this may not be true if we
remove the blanking of the `hashSequence` field. Anyonecanpay would
allow changing the number of inputs in an arbitrary fashion, while
`noinput` without the blanking would (in a weird roundabout way) still
commit to the number of inputs. Maybe we want to make that more explicit
by also hashing the number of inputs? But I can't think of a good
usecase for keeping that, with noinput.
Cheers,
Christian
Christian Decker [ARCHIVE] /
npub1wt…gtuyn
2023-06-07 18:15:16
in reply to nevent1q…0nq0
Author Public Key
npub1wtx5qvewc7pd6znlvwktq03mdld05mv3h5dkzfwd3dc30gdmsptsugtuynPublished at
2023-06-07 18:15:16Event JSON
{
"id": "aae6845216e0b6f0e24820d9301fb94f1e0ad65484f2f7ff341b788104f2952b",
"pubkey": "72cd40332ec782dd0a7f63acb03e3b6fdafa6d91bd1b6125cd8b7117a1bb8057",
"created_at": 1686161716,
"kind": 1,
"tags": [
[
"e",
"1bd7a781e2cfd166ff9a33b1bac5fde47a675384fad1a2f913ed308d62699fea",
"",
"root"
],
[
"e",
"3ec48bc41e1c64bd7f3a32b12d07f09b4d48109fdbd9a0136c8479a707153409",
"",
"reply"
],
[
"p",
"f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab"
]
],
"content": "📅 Original date posted:2018-11-21\n📝 Original message:Anthony Towns via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\nwrites:\n\u003e Given this implementation, NOINPUT effectively implies ANYONECANPAY,\n\u003e I think. (I think that is also true of BIP 118's NOINPUT spec)\n\nI mentioned this in my reply to Pieter, but this may not be true if we\nremove the blanking of the `hashSequence` field. Anyonecanpay would\nallow changing the number of inputs in an arbitrary fashion, while\n`noinput` without the blanking would (in a weird roundabout way) still\ncommit to the number of inputs. Maybe we want to make that more explicit\nby also hashing the number of inputs? But I can't think of a good\nusecase for keeping that, with noinput.\n\nCheers,\nChristian",
"sig": "2e78276c603d0bbcf9b3bd0ed406e86d68383633266e38c44270bffbcc8ff609568d9ad05e667c1b391bf84d7ff23212b81fe034e153aa00420cfed25b9d7b64"
}