Oh man, guys: the hoops I just jumped through to send a UTXO consolidation transaction to myself using my hardware wallet (seedsigner). I don’t normally transact and probably made this way harder on myself than needed.
I stack each paycheck, normally using cashapp. With fees ripping (at least, until now that I'm writing this at 822,443), I decided it was time to consolidate. I was withdrawing to a watch-only address in blue wallet and wanted to make sure I didn’t OVER-overpay on fees, so I decided to recover with a desktop UI. I went with Nunchuk since it seemed simple after a btcsessions session (shoutout). Except my laptop’s f*&^#$@ webcam can’t read the QR code. Whatever… I’ll enter the xpub by hand... and, there it is. No big deal. When the transaction is built, and I unsuccessfully sign with my device, I try to export to blue wallet and scan the PSBT with my phone. When I’m ready to broadcast, I get:
Cannot read property ‘broadcast-tx’ of undefined
???
Anyone who posts in the blue wallet telegram group just gets bombarded by scammers, so I try to broadcast using my node, but bitcoin-cli can’t parse the json. Because f-you, that’s why. So I’ve got this transaction hex just sitting here. Okay, I’ll try one more time recovering the wallet on MOBILE nunchuk. Except I’m on an older version of seedsigner that can’t export to nunchuk via QR. Download new image, verify, re-flash… and I’m back in with the new seedsigner version. Building, signing, and broadcasting the transaction from here is a breeze. I even got confirmed in the next block! …guess I overpaid.
b@@lean /
npub14l…5ul9j
2023-12-22 21:50:39
Author Public Key
npub14lmpajydchx0060recje8fmtye6svavnvxtx9z4qludz4wasj25qz5ul9jPublished at
2023-12-22 21:50:39Event JSON
{
"id": "ae647f16e1198902d7a588c8e1ad41107c412c485ea44d9e90a411f21341775f",
"pubkey": "aff61ec88dc5ccf7e9e3ce2593a76b26750675936196628aa0ff1a2abbb092a8",
"created_at": 1703278239,
"kind": 1,
"tags": [],
"content": "Oh man, guys: the hoops I just jumped through to send a UTXO consolidation transaction to myself using my hardware wallet (seedsigner). I don’t normally transact and probably made this way harder on myself than needed.\n\nI stack each paycheck, normally using cashapp. With fees ripping (at least, until now that I'm writing this at 822,443), I decided it was time to consolidate. I was withdrawing to a watch-only address in blue wallet and wanted to make sure I didn’t OVER-overpay on fees, so I decided to recover with a desktop UI. I went with Nunchuk since it seemed simple after a btcsessions session (shoutout). Except my laptop’s f*\u0026^#$@ webcam can’t read the QR code. Whatever… I’ll enter the xpub by hand... and, there it is. No big deal. When the transaction is built, and I unsuccessfully sign with my device, I try to export to blue wallet and scan the PSBT with my phone. When I’m ready to broadcast, I get:\n\nCannot read property ‘broadcast-tx’ of undefined\n\n???\n\nAnyone who posts in the blue wallet telegram group just gets bombarded by scammers, so I try to broadcast using my node, but bitcoin-cli can’t parse the json. Because f-you, that’s why. So I’ve got this transaction hex just sitting here. Okay, I’ll try one more time recovering the wallet on MOBILE nunchuk. Except I’m on an older version of seedsigner that can’t export to nunchuk via QR. Download new image, verify, re-flash… and I’m back in with the new seedsigner version. Building, signing, and broadcasting the transaction from here is a breeze. I even got confirmed in the next block! …guess I overpaid.",
"sig": "c257252b34249ca973d56a9fab612c23732994cfc20c8615344fd238e2ca50ed755317f3d5d1ead41e5952169dfa31ba297521d2eb655adcc1d661e2e7b12c52"
}