š
Original date posted:2019-05-01
š Original message:Good morning Aymeric,
Sent with ProtonMail Secure Email.
āāāāāāā Original Message āāāāāāā
On Tuesday, April 30, 2019 5:43 PM, Aymeric Vitte <vitteaymeric at gmail.com> wrote:
> I must badly explain my point (or just wondering things that do not
> exist finally), the question is indeed whether nodes will relay non
> usual transactions or not and how to know what they will accept or not:
>
> - my modified multisig 2 of 3: I did put OP_2 out of the usual redeem
> script, the redeem script still matches scriptpubkey and scriptsig will
> execute succesfully, that's a normal legacy P2SH or segwit P2WSH
>
> - bch segwit recovery: it's a p2sh transaction without any signature
> verification, as far as I remember there was a story that it could not
> propagate in the network (even taking the risk to be stolen) and that
> people had to contact a (honest) miner
>
> - sha bounties: same as above, p2sh transactions without signatures
>
> etc
>
> Will all of those transactions propagate normally? And then the rule is
> just that it matches the P2PKH, P2WPKH, P2SH, or P2WSH templates
> whatever scripts you put inside?
P2PKH and P2WPKH cannot have custom script.
However, yes, any custom script can be wrapped in P2SH and P2WSH and it will be propagated.
The P2SH/P2WSH hides the details of your custom script so cannot be filtered based on your custom script.
Do realize that once a claim on your modified x-of-3 is propagated your `redeemScript` is known and someone can attempt to RBF (or coordinate with a miner) with a modified `witness` stack or `scriptSig` to claim your UTXO.
(I do not know if `OP_CHECKMULTISIG` supports 0-of-3 but at least one of your signatories could make it a 1-of-3 and bribe a miner to get it claimed)
I cannot answer for BCH; arguably that is off-topic here.
The old SHA bounty transactions were propagated in the days before `isStandard` I think.
Either that or they were put in by miners.
An SHA bounty can still be propagated today if they are wrapped in a P2SH or P2WSH, but you have to publish the `redeemScript` yourself in some other method.
Or bribe a miner if the transaction is not time-sensitive (for an SHA bounty, unlikely to be time-sensitive).
Regards,
ZmnSCPxj
ZmnSCPxj [ARCHIVE] /
npub1g5ā¦3ms3l
2023-06-07 18:17:54
in reply to nevent1qā¦2n8t
Author Public Key
npub1g5zswf6y48f7fy90jf3tlcuwdmjn8znhzaa4vkmtxaeskca8hpss23ms3lPublished at
2023-06-07 18:17:54Event JSON
{
"id": "892cbbff5ad77ac4ce1c7fee0ff7cbaa53e3759c5ee9f9446f0a4662a9fa79c2",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686161874,
"kind": 1,
"tags": [
[
"e",
"ea519755e9d868d305da2e64274a4b5901d37623b95a6db53c067baa02945ea9",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "š
Original date posted:2019-05-01\nš Original message:Good morning Aymeric,\n\n\nSent with ProtonMail Secure Email.\n\nāāāāāāā Original Message āāāāāāā\nOn Tuesday, April 30, 2019 5:43 PM, Aymeric Vitte \u003cvitteaymeric at gmail.com\u003e wrote:\n\n\u003e I must badly explain my point (or just wondering things that do not\n\u003e exist finally), the question is indeed whether nodes will relay non\n\u003e usual transactions or not and how to know what they will accept or not:\n\u003e\n\u003e - my modified multisig 2 of 3: I did put OP_2 out of the usual redeem\n\u003e script, the redeem script still matches scriptpubkey and scriptsig will\n\u003e execute succesfully, that's a normal legacy P2SH or segwit P2WSH\n\u003e\n\u003e - bch segwit recovery: it's a p2sh transaction without any signature\n\u003e verification, as far as I remember there was a story that it could not\n\u003e propagate in the network (even taking the risk to be stolen) and that\n\u003e people had to contact a (honest) miner\n\u003e\n\u003e - sha bounties: same as above, p2sh transactions without signatures\n\u003e\n\u003e etc\n\u003e\n\u003e Will all of those transactions propagate normally? And then the rule is\n\u003e just that it matches the P2PKH, P2WPKH, P2SH, or P2WSH templates\n\u003e whatever scripts you put inside?\n\nP2PKH and P2WPKH cannot have custom script.\nHowever, yes, any custom script can be wrapped in P2SH and P2WSH and it will be propagated.\nThe P2SH/P2WSH hides the details of your custom script so cannot be filtered based on your custom script.\nDo realize that once a claim on your modified x-of-3 is propagated your `redeemScript` is known and someone can attempt to RBF (or coordinate with a miner) with a modified `witness` stack or `scriptSig` to claim your UTXO.\n(I do not know if `OP_CHECKMULTISIG` supports 0-of-3 but at least one of your signatories could make it a 1-of-3 and bribe a miner to get it claimed)\n\nI cannot answer for BCH; arguably that is off-topic here.\n\nThe old SHA bounty transactions were propagated in the days before `isStandard` I think.\nEither that or they were put in by miners.\nAn SHA bounty can still be propagated today if they are wrapped in a P2SH or P2WSH, but you have to publish the `redeemScript` yourself in some other method.\nOr bribe a miner if the transaction is not time-sensitive (for an SHA bounty, unlikely to be time-sensitive).\n\nRegards,\nZmnSCPxj",
"sig": "7a752c306686800aea7f6620b98770bfce238ae3cf3e8184485ee03a31b0b53399c383d5cfe6376bea70ba9446eab2b5099ca4f0d4751bb9aefd7d3dbd69b340"
}