Cool. Signed a tx the hard way* via the Unchained UI.

* download the psbt

* in Sparrow: File -> Open Transaction -> File

* finalize the tx and do the normal @npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl QR-based signing

* File -> Save PSBT -> As Base 64

* upload signature to Unchained

---

*(note that this approach is kind of dumb; I could have just constructed the entire tx in Sparrow, signed, and broadcast it from there without going through the Unchained UI at all. BUT... in the case where I need them to sign w/their key, I would have to go through their UI so it's good to know the steps!)

nostr:note10hl70ujr5jhkxcn2v4yg42qrc25ephw4cwm3vy7c64zvd53tupys87wd5y

Reply to this note

Please Login to reply.

Discussion

does seedsigner keep the private key in memory or does it write it to the sd card?

It keeps it in memory until it is depowered. Then you have to reload the seed. Nothing is on SD card- in fact you can remove the card once it has booted.

nice. i remember seeing this "attack" and was curious about the default seedsigner software behavior https://twitter.com/emzy/status/1632750430139678720

Shows the importance of verifying your software downloads. And the latest software which allows your SD card to be remove negates this attack vector.

Shows the importance of verifying your software downloads. And the latest software which allows your SD card to be remove negates this attack vector.

Cool! Out of curiosity, what made you choose Unchained over other providers such as Casa or Nunchuck?

Unchained:

* Bitcoin only

* I've met a number of Unchained folks (MANY of whom are @npub17tyke9lkgxd98ruyeul6wt3pj3s9uxzgp9hxu5tsenjmweue6sqq4y3mgl maxis!) and consider a bunch of them friends. They are all hard-core Bitcoiners and super-focused on improving self-custody as much as possible.

* Will be moving my self-directed bitcoin IRA over to their service (better match for me vs Swan's IRA product).

* Pricing model: free for basic 2-of-3; $20 each time you need Unchained to co-sign for you (should only be needed in an emergency/catastrophe).

Casa:

* not Bitcoin only. I have a ton of respect for Lopp but since there are various competing services in the market, it's nice that I can choose accordingly.

* Pricing model: Annual fee ($100-200?)

* Fewer personal connections there.

* Overall I just know less about them, to be honest.

Nunchuk:

* Hadn't even occurred to me. Their collaborative custody service is brand new, yes? I would need to see a longer track record before committing any of my stack that way (see below).

* Their early product releases were broken in unacceptable ways (e.g. my cosigner on iOS signed a tx but the app in Android never--to this day--showed the signature as complete. Possibly a problem with which UX flow I used, but still shouldn't be possible to screw that up. Their app has ONE JOB and the early release I tried failed. A subsequent release worked better but was still plagued with some really bad UI/UX decisions: hiding crucial info, not indicating pending txs/balance changes, etc). I love the idea of their app but it'll be a while before I'd feel comfortable deeply integrating any of my multisig setups / cosigners in their ecosystem.

Coming soon (~Oct?): Swan:

* Will def give their service a try when it's available. I want multiple multisigs storing bits of my stack w/different collaborative custody services.

* Bitcoin only

* I have more personal connections to Swan.

* I've worked on and worked closely with the Specter Desktop team, which is now under the Swan umbrella and I'd guess will be the main interface for Swan's collaborative custody service.

Thanks a lot for this response Keith! 🙌

Keith Am I supposed to be able to know how to make my own vault from your sharing? The cold card script mods, the derivation path, or ARE YOU SHARING and SOON will give the Well intentioned Simpleton- A Dummy template to follow (like the brilliant, clear, SeedSigner directions). I am patiently begging 😀.

Yes, when I get the chance I'll write up steps!