📅 Original date posted:2011-10-27
🗒️ Summary of this message: Green addresses could be implemented as a second signature in the scriptSig, but it triggers a size limit issue.
📝 Original message:Am Mo, 24.10.2011, 16:55, schrieb Gavin Andresen:
> Green addresses could be implemented as a second signature in the
> scriptSig. You'd have to hack your bitcoin client, but you could
> generate a transaction that had <greensig> <sig> <pubKey> ... as the
> input instead of <sig> <pubKey>.
>
> The <greensig> will be ignored by old clients. The transactions is
> still considered 'standard'. But you could teach bitcoin to look for
> <greensig> signatures in wallet transactions...
I played around with this a little bit and managed to generate such
transactions. However, I ran into the problem that IsStandard() also
checks that the size of scriptSig is not above 200. Adding an extra
signature there triggers this limit. I guess there is no way around
that?
Regards,
Jan
Jan Vornberger [ARCHIVE] /
npub147…tnsv4
2023-06-07 02:35:04
in reply to nevent1q…fltj
Author Public Key
npub147edljttlezv8m5dugzg4ka8cg3073j3t2hq4h8ncxaz9sm5swuq4tnsv4Seen on
wss://relay.nostr.bandPublished at
2023-06-07 02:35:04Event JSON
{
"id": "5635cdd07384b9b35c8b6f0ca97d7079bc739ff253d78dc516a73e904c89f6e1",
"pubkey": "afb2dfc96bfe44c3ee8de2048adba7c222ff46515aae0adcf3c1ba22c37483b8",
"created_at": 1686105304,
"kind": 1,
"tags": [
[
"e",
"30f32a4839f3515f22b5206d3110e202b851ce295fc65c5314c19fc43658750b",
"",
"root"
],
[
"e",
"060ed1cbb19d3f9a785e546ce9060f3a3143111b92e9878fa7720025780a7fae",
"",
"reply"
],
[
"p",
"3415c93783a275488e5c6b38892170eaef07d76147cfa1af131b95577b903df7"
]
],
"content": "📅 Original date posted:2011-10-27\n🗒️ Summary of this message: Green addresses could be implemented as a second signature in the scriptSig, but it triggers a size limit issue.\n📝 Original message:Am Mo, 24.10.2011, 16:55, schrieb Gavin Andresen:\n\u003e Green addresses could be implemented as a second signature in the\n\u003e scriptSig. You'd have to hack your bitcoin client, but you could\n\u003e generate a transaction that had \u003cgreensig\u003e \u003csig\u003e \u003cpubKey\u003e ... as the\n\u003e input instead of \u003csig\u003e \u003cpubKey\u003e.\n\u003e\n\u003e The \u003cgreensig\u003e will be ignored by old clients. The transactions is\n\u003e still considered 'standard'. But you could teach bitcoin to look for\n\u003e \u003cgreensig\u003e signatures in wallet transactions...\n\nI played around with this a little bit and managed to generate such\ntransactions. However, I ran into the problem that IsStandard() also\nchecks that the size of scriptSig is not above 200. Adding an extra\nsignature there triggers this limit. I guess there is no way around\nthat?\n\nRegards,\nJan",
"sig": "0bc0037231f5efc5ca7eaf4dfc5e492dd6082a667aee71e92934edc15417226f539fbe925f1a54411cfdc56d5a596325a34b5ff492e2a1ee38935ff85bd24084"
}