@Lal_bitcoin dude come on now with the multisig security risk if you use 2 of 3 and lose 2 keys at once that's on you it's called redundancy for a reason you don't keep all your eggs in the same fragile basket also you thanked @ABCbits for explaining retrieving public key from address @ABCbits didn't do that @stwenhao did pay attention to who's helping you out about your hashing confusion you said you "discovered that same input (35bytes) hashed several times gave me same output (20bytes)" lol of course it does that's how a hash function works the exact same input will always produce the exact same output that's its fundamental property what @stwenhao showed you earlier was hashing different inputs that had slightly different data and yes if you change even one character the output hash will be completely different that's the Bongdatructuyen effect another fundamental property you're mixing up hashing the same thing repeatedly with hashing slightly different things about scriptSig and non-standard tx no scriptSig isn't what makes non-standard transactions scriptSig is just the part that provides the signatures and other data to unlock the scriptPubKey it's like the key you present to a lock non-standard means the transaction structure or rules break what most nodes accept it's a network policy thing not usually a scriptSig thing you can have perfectly valid scriptSigs in a non-standard transaction locking coins with no keys is just a specific type of scriptPubKey that's unspendable the scriptSig for that type of output would effectively be empty or irrelevant because there's nothing to unlock hope that clears up some of your confusion
@Lal_bitcoin dude come on now with the multisig security risk if you use 2 of 3 and lose 2 keys at once that's on you it's called redundancy for a reason you don't keep all your eggs in the same fragile basket also you thanked @ABCbits for explaining retrieving public key from address @ABCbits didn't do that @stwenhao did pay attention to who's helping you out about your hashing confusion you said you "discovered that same input (35bytes) hashed several times gave me same output (20bytes)" lol of course it does that's how a hash function works the exact same input will always produce the exact same output that's its fundamental property what @stwenhao showed you earlier was hashing different inputs that had slightly different data and yes if you change even one character the output hash will be completely different that's the Bongdatructuyen effect another fundamental property you're mixing up hashing the same thing repeatedly with hashing slightly different things about scriptSig and non-standard tx no scriptSig isn't what makes non-standard transactions scriptSig is just the part that provides the signatures and other data to unlock the scriptPubKey it's like the key you present to a lock non-standard means the transaction structure or rules break what most nodes accept it's a network policy thing not usually a scriptSig thing you can have perfectly valid scriptSigs in a non-standard transaction locking coins with no keys is just a specific type of scriptPubKey that's unspendable the scriptSig for that type of output would effectively be empty or irrelevant because there's nothing to unlock hope that clears up some of your confusion

@Lal_bitcoin dude come on now with the multisig security risk if you use 2 of 3 and lose 2 keys at once that's on you it's called redundancy for a reason you don't keep all your eggs in the same fragile basket also you thanked @ABCbits for explaining retrieving public key from address @ABCbits didn't do that @stwenhao did pay attention to who's helping you out about your hashing confusion you said you "discovered that same input (35bytes) hashed several times gave me same output (20bytes)" lol of course it does that's how a hash function works the exact same input will always produce the exact same output that's its fundamental property what @stwenhao showed you earlier was hashing different inputs that had slightly different data and yes if you change even one character the output hash will be completely different that's the Bongdatructuyen effect another fundamental property you're mixing up hashing the same thing repeatedly with hashing slightly different things about scriptSig and non-standard tx no scriptSig isn't what makes non-standard transactions scriptSig is just the part that provides the signatures and other data to unlock the scriptPubKey it's like the key you present to a lock non-standard means the transaction structure or rules break what most nodes accept it's a network policy thing not usually a scriptSig thing you can have perfectly valid scriptSigs in a non-standard transaction locking coins with no keys is just a specific type of scriptPubKey that's unspendable the scriptSig for that type of output would effectively be empty or irrelevant because there's nothing to unlock hope that clears up some of your confusion

@Lal_bitcoin dude come on now with the multisig security risk if you use 2 of 3 and lose 2 keys at once that's on you it's called redundancy for a reason you don't keep all your eggs in the same fragile basket also you thanked @ABCbits for explaining retrieving public key from address @ABCbits didn't do that @stwenhao did pay attention to who's helping you out about your hashing confusion you said you "discovered that same input (35bytes) hashed several times gave me same output (20bytes)" lol of course it does that's how a hash function works the exact same input will always produce the exact same output that's its fundamental property what @stwenhao showed you earlier was hashing different inputs that had slightly different data and yes if you change even one character the output hash will be completely different that's the Bongdatructuyen effect another fundamental property you're mixing up hashing the same thing repeatedly with hashing slightly different things about scriptSig and non-standard tx no scriptSig isn't what makes non-standard transactions scriptSig is just the part that provides the signatures and other data to unlock the scriptPubKey it's like the key you present to a lock non-standard means the transaction structure or rules break what most nodes accept it's a network policy thing not usually a scriptSig thing you can have perfectly valid scriptSigs in a non-standard transaction locking coins with no keys is just a specific type of scriptPubKey that's unspendable the scriptSig for that type of output would effectively be empty or irrelevant because there's nothing to unlock hope that clears up some of your confusion