YubiKey-Guide VS WalletWasabi

Instead, most people generate keypair(s) on an airgapped machine and write them to two Yubikeys. Or write subkeys to a single Yubikey and keep a backup in encrypted form. See https://github.com/drduh/YubiKey-Guide

I'd recommend using the Yubikey as a GPG smartcard[1]. The private key stays on the Yubikey. I also use it for ssh. But make sure you have a backup key or two, just in case the primary Yubikey gives out. FIDO2 and all other regular Yubikey functionality still works with it.

[1]: https://github.com/drduh/YubiKey-Guide

The excellent guide by drduh should be mentioned here: https://github.com/drduh/YubiKey-Guide — I've been using this approach for years to store my OpenPGP keys on Yubikeys and use them for SSH.

I don't generate my keys on devices. That lets me be flexible and keep backups, as well as use the same keys on multiple physical devices. Using a single yubikey is a bad idea, as you're bound to eventually lose it or break it. Hasn't happened to me yet in 5 years, but I expect it to happen.

I followed this guide to generate a master key and three subkey.

See https://github.com/drduh/YubiKey-Guide . Also google for OpenPGP card specifications, they will answer your question

Regarding GPG/SSH keys, there is a great howto: https://github.com/drduh/YubiKey-Guide

I'd be lying if I said I understood all of that. I'm definitely going to do some research ahaha. Someone else on this post sentence this like which they said was very good guide. https://github.com/drduh/YubiKey-Guide

When storing the key on a Yubikey, however, all you need is just the PIN in order to use the key. It can contain numbers, letters, symbols, etc. and can be quite long, so you can treat it as a passphrase for all intents and purposes. There are actually two PIN codes: one regular one, for a read access, and another administrative one, for write access for when you want to modify the gpg applet settings or the key on the Yubikey. There is also a limit to how many times in a row you can enter pins incorrectly, after which the gpg applet gets locked and the only thing you can do is reset it, erasing the PGP keys. See https://github.com/drduh/YubiKey-Guide for more information.

Try follow this guide from DrDuh https://github.com/drduh/YubiKey-Guide/blob/master/README.md

When I use a search engine to find wasabi wallet, the top result is https://wasabiwallet.app/ However, on github, it says the offical site is https://wasabiwallet.io

Finally, fork Wasabi Wallet, remove what you don't need and add what you do: https://github.com/zkSNACKs/WalletWasabi

This is the list of supported operating systems https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi.Documentation/WasabiCompatibility.md

For the record, this feature has been implemented already, but not released. I hope it'll make it to the next one: https://github.com/zkSNACKs/WalletWasabi/pull/10976

GitHub Discussion: https://github.com/zkSNACKs/WalletWasabi/discussions/10965

Hola. Te dejo el link al GitHub de la billetera Bitcoin 100% escrita en C# (front y back), 100% open source, en la que laburo como dev C# hace 1 año y medio aprox.

The Wasabi Wallet for Bitcoin Core, for example, manages this process almost unnoticed by the user in the background for an additional fee. The problem with this is that the system is a centralized single point of failure. State intervention cannot be ruled out. In addition, Wasabi excludes certain coins that are blacklisted, or whose origin is questionable, in order to "protect its users."

You can check its development activity on GitHub https://github.com/zkSNACKs/WalletWasabi/ if you care about that.

Not your key, not your coins. Go Non-custodial if you must. I use Wasabi Wallet mainly for the privacy.