Open jbrauck-unchained opened 4 months ago
Marking this as a feature request (aka "enhancement"). This is expected behavior though agreed it's undesirable. Would be a nice enhancement to auto parse any sigs as well. It should be pretty easy for someone new to the code base to resolve so marked it as a good first issue. I'm happy to try and help get someone started if they have specific questions for implementation.
@bucko13 i want to work on this issue
I will work on this issue
Hello @bucko13 sir , I exported the unsigned PSBT tx formed from my 1 of 2 multisig wallet ,but i was unable to sign the inputs using the corresponding private key, because the PSBT inputs had unknown pubkeys and not the ones i used to generate my wallet.... now am not sure how this could happen, since am using the the private key for the one of the two pub keys used to form the wallet.
Any help would be appreciated.
Weird, looking back at my original post, I see that one PSBT has tpubs and one has xpubs usually denoting that one came from a testnet setup vs mainnet. Maybe thats what is happening with yours too?
If you have the PSBT that caused this unknown pubkeys output, I would love to take a look.
then i tried to create a psbt , that is :
cHNidP8BAH0BAAAAAfBVf0MThVaxH7C0XqYRyMrMAchLllWPS+RkZx1MXvcMAQAAAAD/////AugDAAAAAAAAFgAUyMQ/mwniqt6z/B0gDaBCRDv9O5C/3AAAAAAAACIAIFi8ff8Kynu80ErnCuv6iKq8PqrFwsw8PTNLNivhi85CAAAAAE8BBDWHzwAAAAAAAAAAAAbnFiQRLc0Zibl6B4FfoFGuVNqdN/X70cW3b0Z+sGEzA15pjlg7JJXFaNQ/gZDjH+WmnnNtPI06pq/uQ3Fbd44ZFAAAAAAwAACAAQAAgAAAAIACAACATwEENYfPAAAAAAAAAAAAGAyZhhVjbNh1qnDHHPpre/VwGHpW2MbQVOYLZE0T6dMCPkdA0LpjniiWPzR2FXt88vt8b99CVPlwmc+GcLUF6lkUAAAAADAAAIABAACAAAAAgAIAAIAAAQDNAgAAAAABAYM+fMYv5fHY3K5O6HI22uet4X3odKoUFWYBQYgczgAoAQAAAAD9////AvBDBqIAAAAAIlEgfzOwrjt/CaDo2mbJ2cSDFzLzDGz41yCucKpPaEOUIzhW4QAAAAAAACIAIB6X/s1scoJULEWaPLDHMfV+scJ/sbkNA/PBPOHf958tAUBbl7vP5+tOyx9SnVQ49h6HJrXWmNnZVFQuXvQLh/42PKPcP2uAidWRbwSHS/ziMgz5cv21AP1Q48ueg9gKIg0BjUs/AAEBK1bhAAAAAAAAIgAgHpf+zWxyglQsRZo8sMcx9X6xwn+xuQ0D88E84d/3ny0BBUdRIQLJfcP0QgQC4BoROYQxG/ShuN43bKwL3Prxs6yB8TQzxyEDEGrzx/NkFanZZ+TNBiJ1gS6j5AnGpt94jXXkbobDPwFSriIGAsl9w/RCBALgGhE5hDEb9KG43jdsrAvc+vGzrIHxNDPHHAAAAAAwAACAAQAAgAAAAIACAACAAAAAAAAAAAAiBgMQavPH82QVqdln5M0GInWBLqPkCcam33iNdeRuhsM/ARwAAAAAMAAAgAEAAIAAAACAAgAAgAAAAAAAAAAAAAAA
I was able to solve the issue i was facing by exporting the psbt in sparrow and signing through a hardware wallet , seedsigner. Thank you for your time.
I'll work on fixing the import sigs.
My progress so far :
Same transaction in :
Sparrow: 0200000001039a8f1b25d0075e6b587f3eadcefedcc55236f8930016507368322874f8c42c0100000000fdffffff019745000000000000160014c8c43f9b09e2aadeb3fc1d200da042443bfd3b90b04d3f00
Caravan:
0100000001039a8f1b25d0075e6b587f3eadcefedcc55236f8930016507368322874f8c42c0100000000ffffffff019745000000000000160014c8c43f9b09e2aadeb3fc1d200da042443bfd3b9000000000
(There's a discrepancy in the version , sequence and lock time) So the same signatures that were done in sparrow , gets invalidated in caravan. Next step to resolve this.
Recreation steps:
This definitely feels like a bug, let me know if I am wrong.
Unsigned PSBT
Partially signed PSBT