📅 Original date posted:2014-02-24
📝 Original message:Regarding 80 bytes vs smaller: The objectives should be that if you are
determined to put some extra data in the blockchain, OP_RETURN should be
the superior alternative. if a user can include more data with less fees
using a multisig TX, then this will happen.
eventually dust-limit rules will not be the deciding factor here, since
i suspect block propagation times will have a stronger effect on
effective fees. therefore a slightly larger payload than the biggest
multisig TX is the right answer. - that would be >= 64x3 bytes = 192 bytes.
(this is my understanding of how large a 3-of-3 multisig tx can be, plus
1.5 bits encoded in the "n" parameter)
Andreas Petersson [ARCHIVE] /
npub10z…qsg9a
2023-06-07 15:13:57
in reply to nevent1q…ls5g
Author Public Key
npub10zyxjrelgpp85qc93pnt8e4yx0jsxm27sn9lsypkhlrttjpmjktqkqsg9aPublished at
2023-06-07 15:13:57Event JSON
{
"id": "a602993271e35f05c4e96d47f433a43526ab0b31050ab1707ac80b4722d8459b",
"pubkey": "7888690f3f40427a03058866b3e6a433e5036d5e84cbf81036bfc6b5c83b9596",
"created_at": 1686150837,
"kind": 1,
"tags": [
[
"e",
"1ef870aa2080d76066b16301e94316a8cf8557aa7768e48cc4c5664289bfd14e",
"",
"root"
],
[
"e",
"917feadf780a0b2330b7b424754ee715a8e11728dadc2d34d5caa71044ac48ca",
"",
"reply"
],
[
"p",
"1c61d995949cbfaf14f767784e166bde865c7b8783d7aa3bf0a1d014b70c0069"
]
],
"content": "📅 Original date posted:2014-02-24\n📝 Original message:Regarding 80 bytes vs smaller: The objectives should be that if you are\ndetermined to put some extra data in the blockchain, OP_RETURN should be\nthe superior alternative. if a user can include more data with less fees\nusing a multisig TX, then this will happen.\n\neventually dust-limit rules will not be the deciding factor here, since\ni suspect block propagation times will have a stronger effect on\neffective fees. therefore a slightly larger payload than the biggest\nmultisig TX is the right answer. - that would be \u003e= 64x3 bytes = 192 bytes.\n(this is my understanding of how large a 3-of-3 multisig tx can be, plus\n1.5 bits encoded in the \"n\" parameter)",
"sig": "75c66bd9f5716fa1ad6510610a06251a62310bcacf95e3398443eb4c7d6aaa2336e45ba70c4f962b7edf3f4a3c1bf11359d577af812860eb37c1568cd5f85fc1"
}