|
Title: 42 character Sigscript. Post by: cyptomania on March 17, 2020, 12:52:03 AM Hi Guys thanks for all your answers over the years,I have a question that's not really important but I can't find the answer.
Every so often when I check my transactions I run across a small Sigscript,it's short at only 42 characters long instead of the usual long ones,what is this ? I don't see how any public key info or any thing else can be in there. Thanks for probably a stupid question but I'm trying to learn,please explain if you can,thanks. Title: Re: 42 character Sigscript. Post by: pooya87 on March 17, 2020, 04:41:11 AM you should post the transaction that you had in mind for a more accurate answer, it could be a non-standard script. but 42 hexadecimal characters or 21 bytes seems is very close to the 22 bytes redeem script of spending a P2SH-P2WPKH output which is 0x0014{20_byte_hash}. does the transaction have any witnesses at the same index as the input signature you are looking at?
example: https://github.com/bitcoin/bips/blob/master/bip-0143.mediawiki#p2sh-p2wpkh nVersion: 01000000 Title: Re: 42 character Sigscript. Post by: cyptomania on March 17, 2020, 11:15:53 PM Hi,this is what it looks like,I don't know how the info needed can be kept in this short thing,curious,hope someone knows.It says it's a Base58(P2SH) at Blockchian.com running the wallet number,I've never seen this configuration.
}, "script_asm" : "001470eb5212b558chj10b31f0849ef88ecf17097ac1", "script_hex" : "16001470eb5212b558chj10b31f0849ef88ecf17097ac1", "witness" : [ "30450221009931f96895b6ff7a486044095f8e09cc2bfb220e54bac67a2909e2e2f49e262b02201 7a4a5b34731cca29616d5013cf02ebbb096613dfd201b30b62a74a5d526b8f601", "0238288b60e8c50785809a69517ae3ca2fe3e407cac8b5868c5fb3803c233dfbcc" Title: Re: 42 character Sigscript. Post by: pooya87 on March 18, 2020, 03:39:08 AM Hi,this is what it looks like,I don't know how the info needed can be kept in this short thing,curious,hope someone knows.It says it's a Base58(P2SH) at Blockchian.com running the wallet number,I've never seen this configuration. it is because this is a special script form for pay to script hash pubscripts that was introduced back in 2017 as a part of Segregated Witness soft-fork. it is like a workaround to use SegWit while stay backward compatible since the address format is the same as before (base58 starting with 3). the actual script is the "script_hex" part since the 0x16 push byte is a part of it and this whole thing is a redeem script and is accompanied by the signature placed in the witness part. Title: Re: 42 character Sigscript. Post by: nc50lc on March 18, 2020, 05:32:35 AM "script_asm" : "001470eb5212b558chj10b31f0849ef88ecf17097ac1", May I ask? There's no "42 character" string in that scriptSig;"script_hex" : "16001470eb5212b558chj10b31f0849ef88ecf17097ac1", Did you just added the invalid characters "hj" in the middle of the 'script_hex' and 'script_asm' that made them 44 and 46 characters? If you remove 'h' and 'j', the pubkeyHash160 will be 19bytes that's impossible to happen. Where did you get those strings? Can you share the actual transaction or P2SH address like pooya suggested in post#2? |