Lots of reasons. Employees thanking each other with sats is taxable income (unless you're in the UAE or some such place). All taxable income needs a reporting trail, and, say in the case of Singapore, must be pegged to the SGD equivalent at the time of transaction for reporting. Basically tax departments (and internal accounting teams) can't deal well with blind tokens flying around left and right. And if you gate it at the app and node level (take down names) so you have that audit trail then you have to ask what the point of cashu is anymore, besides nifty tricks with programmatic strings. Another reason is that your system has to be defensible against threats like smurfing (look it up), and cashu is hard to defend against smurfing without making it not cashu anymore. It's like how many companies can't deal with AGPLv3 open source code since it can infect their proprietary code by accident and is seen as too dangerous to have in the codebase. And a bunch more reasons, including the fact that Cashu by nature triggers a bunch of licensing headaches that custodial lightning + NWC does not trigger. NWC is accidentally pretty well-engineered for regulatory approval