BitBox (and other wallets?) can't be connected via EPS to a Bitcoin Core node #298
Description
Hello,
Yesterday, I tried to help a bitcoiner about connecting its BitBox02 hardware wallet in Sparrow, which was connected to his Bitcoin Node through an Electrum Personal Server (+ TOR).
It didn't work, so we simplified things: no TOR, and no EPS. It also works: tx were synchronising, etc.
However, when we tried again to launch EPS, Sparrow couldn't connect and find tx.
We also tried to export the EPS file in order to modify the config.ini file, but it didn't work:
"Cannot invoke "com.sparrowwallet.drongo.ExtendedKey.toString(com.sparrowwallet.drongo.ExtendedKey$Header)" beacause the return value of ..."
With the BitBox02, there were only a deposit and a postmix accounts (no badbank and no premix). I do think that's why there was this error: 'cause there isn't any inter-deposit-notification-address to export.
That's why, i think, the EPS couldn't load tx.
Am i wrong?
Does all hardware wallets have the same problem? 'cause i gonna connect with a multisig some jade / trezor / seedsigner / coldcard..
I do admit i'm a bit confused, considering this: https://bitbox.swiss/blog/peek-into-bitcoin-internals-using-sparrow-wallet-with-your-bitbox02/
It seems they achieved to connect their BitBox02 to an EPS; by not using a proxy and not adding the postmix account.
Thanks for your time.
Configuration:
- sparrow 1.7.9
- bitcoin core v25.0.0
- bitbox02