@COLDCARD Q has a strange UX downgrade from Mk4
When I consolidate UTXO, Mk4 specifically says that the receive address is mine, but that Q does not indicate that the address belongs to this same wallet.
@npub12ctj...c5ky please fix it you can!
@DETERMINISTIC OPTIMISM 🌞 pretty please
Login to reply
Replies (13)
did you use sparrow wallet 2.3.0 to generate PSBT ?


X (formerly Twitter)
Andrej Virgovic (@AVirgovic) on X
@RotorDriven @COLDCARDwallet @nvk The issue is with sparrow, it no longer adds BIP32 paths to PSBT if you copy from own address list (only change o...
I use sparrow, but in this instance I was connected w USBC (no internal batteries to hand)
Sparrow rightly said “Consolidating…” but “Don’t trust. Verify.” So I was disappointed that the Coldcard Q lost this feature of the Mk4.
does not matter how you were connected, there is a BUG in sparrow 2.3.0 which causes this behavior. Sparrow already fixed the bug, but haven't released it yet (should be out next week or so).
Downgrade your sparrow, as mentioned in the twitter post, or wait for new release.
Q didn't "loose" anything & same thing would happen to you if you use Mk4 with sparrow 2.3.0
Or check out @Bitcoin Safe
Very nice. Thank you for the info.
I’ve quit Twitter, so now I’m out of the loop, I guess.
Not going back!
I’ll check it out.
First glance:
- sync my wallet levels across…
WTF? Big nope.
cross-post:
The issue is with sparrow, it no longer adds BIP32 paths to PSBT if you copy from own address list (only change output has properly populated BIP32 paths). Coldcard cannot know if it's own address without it.
to fix downgrade sparrow to 2.2.3
I'd give it a try - it's a great wallet!
Hell no, terrible idea!!!!
I’ll look at it, but I’m super happy with Sparrow wallet, this one bug notwithstanding.
Presumably a future version would address this?
Or I could consolidate into change addresses to work around this, right?
It's opt in.
Fair enough. 👍