It is still weird, because I did not even know about this SIGHASH_NONE option until now. I did not even see it during transaction procedure.
Your signature does show that it's Sighash None (0x02).Code:
"txinwitness": ["c5f44fbc794750b099b08bf97ede5cd72f6f382f02bd9ae16d5885a2fde1f0e07c668a4ae3fe340954b30622f971dbca2209d3b3a7ee78984ca0b97a559cb63002"],
If you didn't intentionally selected the option; this may be a case of keyboard tab and arrow keys "accident".
You see, when that drop-down menu is highlighted by the tab key tab, pressing down button (e.g.: when navigating via keyboard) will select the next option which is SigHash None.
-snip-
It is still weird, because I did not even know about this SIGHASH_NONE option until now. I did not even see it during transaction procedure.
why would sparrow wallet use sighash_none? that's just like submitting a blank check to anyone to fill in their name... It is still weird, because I did not even know about this SIGHASH_NONE option until now. I did not even see it during transaction procedure.
i thought sparrow wallet was supposed to be a good wallet but if it's doing that kind of thing then i'm not so sure anymore.So there shouldn't be any issue unless the user experimented on the option.
But there should be warnings in other Sighash flags than just "Recommended" in Sighash All option.
Screenshot:
