Rico on Nostr: π I'm in needs of help moving funds from an old single sig legacy address: I ...
π I'm in needs of help moving funds from an old single sig legacy address:
I exported my Coldcard's xpub to Bluewallet. Bluewallet derived an address from that xpub onto which I received funds. Unfortunately, Bluewallet gave me a legacy address and I didn't notice. I should've given it the zpub, I know better now.
Now I like to move that BTC but the first TX I made in Sparrow, which is watch-only, m/0'/0'/0' and correctly fingerprinted, watching legacy, sees the UTXO and scripts the psbt but the Coldcard refuses to sign saying "failure. my xfp not involved".
Alright, I created a second psbt with the original culprit Bluewallet but Coldcard doesn't like to sign this psbt either as "m/44' led to wrong pubkey for input#0" and this is where I need help rabbitholing.
This watch-only Bluewallet always has been on derivation path m/44'/0'/0'/0', I didn't interfere the xpub import to begin with, this is how it got the idea to give me a legacy address. How come even Bluewallets psbt isn't pleasing the Coldcard?
What does Coldcard need from me now?
Thank you π€
#bitcoin #helpstr
#m/fun'/for'/everyone'
Published at
2023-05-27 13:53:57Event JSON
{
"id": "6f2e1415407c9111c7da3e0276ae6b529f642b9a081ea4de4b3d5a60e5969792",
"pubkey": "fe403ee3a532c9cc893566cddd6043c872fa9261db240127d603d91c026391d9",
"created_at": 1685195637,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"bitcoin"
],
[
"t",
"helpstr"
],
[
"t",
"helpstr"
],
[
"t",
"m"
],
[
"t",
"m"
]
],
"content": "π I'm in needs of help moving funds from an old single sig legacy address:\nI exported my Coldcard's xpub to Bluewallet. Bluewallet derived an address from that xpub onto which I received funds. Unfortunately, Bluewallet gave me a legacy address and I didn't notice. I should've given it the zpub, I know better now. \n\nNow I like to move that BTC but the first TX I made in Sparrow, which is watch-only, m/0'/0'/0' and correctly fingerprinted, watching legacy, sees the UTXO and scripts the psbt but the Coldcard refuses to sign saying \"failure. my xfp not involved\". \n\nAlright, I created a second psbt with the original culprit Bluewallet but Coldcard doesn't like to sign this psbt either as \"m/44' led to wrong pubkey for input#0\" and this is where I need help rabbitholing.\n\nThis watch-only Bluewallet always has been on derivation path m/44'/0'/0'/0', I didn't interfere the xpub import to begin with, this is how it got the idea to give me a legacy address. How come even Bluewallets psbt isn't pleasing the Coldcard? \n\nWhat does Coldcard need from me now? \nThank you π€\n\n#bitcoin #helpstr\n#m/fun'/for'/everyone'",
"sig": "e2e459b90e6e308ec3374fff205c12dce352c100f07177d30d4d5ba3547c6b5332f23122ffaa225ac5a8f3ece21c2d3c7be894d75ad312b0dcfd1ee358aa7ee1"
}