WalletWasabi VS Avalonia

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.

You might also want to look at AvaloniaUI[0] for a cross platform .NET GUI library. It is similar to WPF but much nicer to work with.

[0] https://github.com/AvaloniaUI/Avalonia

Production user here. There's no money gotchas. They're above reproach. In fact, I've received considerable free support from their devs on GitHub Issues [1].

The Avalonia business model is based on selling XPF, which runs WPF (Windows-only) apps on other platforms. That's very interesting to big corps with existing codebases.

See my comment [2]

[1] https://github.com/AvaloniaUI/Avalonia/issues

[2] https://news.ycombinator.com/item?id=39246988#39249128

Yes, but the portable GUI frameworks by Microsoft themselves are generally not very good, and they tend to be abandoned after a couple of years.

Avalonia is developed outside of the Microsoft corporate madness and seems to be slowly becoming the defacto cross-platform framework because it is expected to last a bit longer than a manager's attention span: https://avaloniaui.net/

Not my comment, but relevant here "The problem with compiling Skia to WASM is you'll lose any benefits of hardware graphics acceleration on the device."

(From https://github.com/AvaloniaUI/Avalonia/discussions/6831#disc... )

It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.

Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.

[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup

[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)

For desktop, Avalonia, hands down.

https://avaloniaui.net/

Open source, powered by Skia, backed by JetBrains, and quite battle-tested at this point for small to medium-sized apps. In theory perfectly capable for enterprise as well, since it's basically a spiritual successor to WPF, which has been an industry standard for about 15 years.

They're diving into mobile and WASM well, but that's more of a recent effort and I haven't tested that yet.