Thanks @koob! I'm personally VERY excited about this feature :D . It's been our dream to enable E2EE collaborative custody for everyone since day 1 of Nunchuk. Now it's gotten to the point where the UX is highly reliable and seamless.

Look forward to seeing how people use it.

Hey guys! Hugo from nunchuk.io here. Congrats on this!

Do you support two-round signing / MuSig2 protocol?

We have added support for Schnorr + MuSig2 recently to Nunchuk (https://nunchuk.io/blog/taproot-multisig). Would be cool to have Satochip integrated in Nunchuk and get MuSig2 working with a hardware signing device.

If you're interested, shoot me an email hugo@nunchuk.io !

Thank you!

You're welcome!

It's still very early days (this is a beta release), plus the rest of the ecosystem hasn't added support for Taproot yet. In terms of hardware signing devices, only Ledger and Coinkite currently have experimental firmware for Taproot. So I'd say give it some time to mature. If you want to try it out, put a very small amount of fund in it.

Multisig is great, and UX is quickly improving!

Checkout Taproot-based multisig wallets, which we just launched a few hours ago on Nunchuk (currently a beta feature): https://nunchuk.io/blog/taproot-multisig

It leverages Schnorr signatures and MuSig2 protocol to enhance privacy (i.e. Taproot multisig transactions look indistinguishable from singlesig transactions on-chain) and lower transaction fees.

X thread: https://x.com/nunchuk_io/status/1871632189752008780

Thanks for sharing @Rsync25!

Congrats!! Glad I could help.

You're welcome!

Here's another good resource: https://learnmeabitcoin.com/technical/keys/hd-wallets/extended-keys/

You enter the XPRV (which is short for "Extended private key"), encoded in base58 format. It's the same encoding used for XPUB ("Extended public key").

I suggest spending some time on https://iancoleman.io/bip39/ to get a better understanding of keys and encodings. Try generating a few keys. WARNING: Only use the site for learning; don't use it to generate keys for a real wallet!

The XPRV for the master key is labeled "BIP32 root key". XPRV strings have the prefix "xprv".

It's Keys tab > Add key > Add software key > Recover existing key > Recover key via XPRV

Love to hear it, and you're welcome! :)

Hey! What version of Nunchuk are you using? Android or iOS?

We've officially switched to testnet4 since a couple of releases ago.

Based on handling support tickets for several years: the #1 reason people lock themselves out of their wallets is forgotten passphrases.

(Which was one of the main reasons I wrote this essay: https://hugonguyen.medium.com/passphrases-are-not-the-solution-for-bitcoin-custody-4f967a339b1b)

For multisig wallets, it's pretty standard practice now that you must absolutely back up the wallet configuration file (BSMS or Output Descriptors format). Eliminate most of the issues you listed.

Cool and thanks! Our goal is to continue making self-custody easier and more accessible. It's crucial IMHO, especially with the rise of ETFs and governments looking to make self-custody illegal or cost-prohibitive—to effectively close the exit door as the fiat system runs its course.

That link between users and coders is super important. I don’t spend time writing code anymore, but I was an engineer for 10+ years—from working close to bare metal (i.e., firmware & embedded programming on CDMA/GSM chipsets) to front-end consumer applications—so I completely understand what you mean.

For better or worse, devs tend to live in their own world, often lacking empathy for end users. It happens at all levels of the hardware + software stack.

(It’s probably the same autistic tendencies that make certain people exceptionally good at coding, but at the same time, it’s their Achilles' heel.)

This disconnect is so prevalent in tech that a company like Apple can come in and create a trillion-dollar business just by being insanely focused on user experience at all levels of the hardware + software stack. It’s mind-blowing.

I think we’re witnessing the same phenomenon in Bitcoin. A lot of devs like to tinker with cool things, but barely have experience dealing with end users on a day-to-day basis. Most devs hate doing that; they just want to code. As a result, a lot of projects in Bitcoin so far are cool AF from an engineering perspective, but not sustainable long-term because they don't actually solve a real problem for end users. I hope that changes as Bitcoin matures. Voices like yours are important in bringing about that change. Cheers!

P.S. Would love to hear your feedback on Nunchuk when you have a chance.

You said you weren't trained in coding, but one thing that crosses my mind when reading your post, is that you'd probably make a great engineer! I think that fanatical attention to detail would help a lot.

Thanks for sharing your story.

Very interesting insight. Thanks for sharing @kojisan!

Fair point.

OP didn't say if it was a local or remote setup.

If it's a local setup, your wallet can only be operational while staying within the LAN. Some people might be fine with not having your wallet accessible on-the-go. Most users will probably find that too limiting, though.

Another big benefit of using Electrum server is authenticated connection.

Bitcoin Core, otoh, was never designed to be a backend. Connecting to bitcoind directly uses RPC, which is not secure.