Is .NET still suitable for WasabiWallet?

[Rot127]

Forwarded from #14212 (comment)

The issue linked above was about a segfault I encountered. It is likely due to some upstream bug in .NET.

On a higher level, I think the dependency on .NET is worth a discussion.

Do you think a framework which is written with memory unsafe languages, but is forced to use AI for development is still an acceptable choice for a privacy focused BTC wallet?

What stops an attacker with enough exits nodes to send malicious block data? Data to exploit bugs in the crypto library or some other component of .NET? Specifically for crypto stuff there seems to be closed without fix issues in .NET already.

Even if the wallet is compartmentalized away in a VM and if it is kept empty, an exploit would defeat the whole privacy aspect.

Of course there is no such thing as "simply rewriting" a wallet like Wasabi.
Still I wanted to open the discussion here out of interest.

Related:

https://github.com/orgs/WalletWasabi/discussions/8910
https://github.com/orgs/WalletWasabi/discussions/13796

[MarnixCroes]

If anybody can, they are welcome to do so of course.

It's just that Wasabi happens to be like this since forever and in current conditions and the very limited amount of contributors (who are mainly familiar with .NET / C#) there is no rewrite planned.

Anyone can do it, I think it would be great to have. If done well.