I'm trying to sign a message with a specific Native SegWit (P2WPKH, bc1...) address on my Coldcard, fully air-gapped via microSD only (no USB/NFC/etc).
When I use Sign Text File (under Advanced/Tools & File Management) Coldcard always signs with the key at m/44'/0'/0'/0/0 (the first Legacy (1...) address) regardless of which wallet format is loaded. This is confirmed by the on-screen message Coldcard displays before signing.
My funded address is a Native SegWit bc1... address and I need the signature to correspond to that specific address for an audit proof of ownership requirement.
Is there a way to direct Coldcard's Sign Text File to sign with a specific address or derivation path? Is there an alternative air-gapped message signing flow (microSD only) that produces a signature verifiable against a specific bc1... address? Is this behaviour documented anywhere?
fyi, running Coldcard Mk4 firmware 5.5.0, Electrum 4.7.0.
Update: I found a workable solution using Sparrow Wallet instead of Electrum. Sparrow's airgapped signing flow (Sign by File / Load Signed File) creates an intermediate file that specifies the exact derivation path and script type, which Coldcard uses to sign with the correct bc1... address. A solution with electrum would still be useful, both to me and maybe others.
[link] [comments]
You can get bonuses upto $100 FREE BONUS when you:
π° Install these recommended apps:
π² SocialGood - 100% Crypto Back on Everyday Shopping
π² xPortal - The DeFi For The Next Billion
π² CryptoTab Browser - Lightweight, fast, and ready to mine!
π° Register on these recommended exchanges:
π‘ Binanceπ‘ Bitfinexπ‘ Bitmartπ‘ Bittrexπ‘ Bitget
π‘ CoinExπ‘ Crypto.comπ‘ Gate.ioπ‘ Huobiπ‘ Kucoin.
Comments