How do you send 10 sats on chain?

Asking for a friend.

This is what they've been working on for years and will continue for years to come .

https://lightning.engineering/posts/2023-10-18-taproot-assets-v0.3/

It's still the difference between trusted vs fully custodial by a single actor. And as a fedimint module, this is a service they will be doing on behalf of users anyways. Not meant for an additional third party.

As you should be 🫡

We have recently disabled the ability to zap nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 wallet users from Mutiny. You may still pay their invoices or LN addresses normally but a big problem we were seeing was force closed channels due to stuck payments to Zeus due to their work arounds with locked payments. Which harm both the user experience and other lightning nodes on the network.

Since nostr users are mostly unaware if they're zapping Zeus users or not, we are taking this step proactively to protect users from having a 10 sat zap costing them serious on chain channel closing (and reopening) fees.

The approach we are working on for solving lightning addresses on mobile wallets is a fedimint hybrid approach where the sats end up at a federation if you are offline but get swept to your self custodial channel when you come online. Payments will settle instantly with the federation and it won't lock up unnecessary HTLCs on the network.

Ideally we get the ability to do offline receives normally on LN but that future is looking really grim with LND's continued priorities on shitcoins instead of features, and offline receives depends on a network wide upgrade.

We petition Zeus to move to a more responsible node implementation like LDK unless their plan is to add shitcoins or break LN further.

Should be fixed when we deploy tomorrow. It was lists that were screwing it up.

Confirmed I'm seeing it with your npub for some reason. We opened up an issue on it: https://github.com/MutinyWallet/mutiny-web/issues/710

Is that happening right now for you?

Please let us know! We only know when users tell us.

We have released a few updates over the last week and yesterday to cut down on channel closes and increase payment reliability. Let us know if these improve or not!

If you open it yourself then you pay the fee. If the LSP opens it for you then they have to charge you for the free. Right now that is 40k sats because the fee rates are high but soon it'll be dynamic.

There are probably 7 but 2 didn't go through. Talk to your client or person that set up the zap split.

You probably zapped someone with zap splits turned on.

Should be fixed now. Let us know if not.

Yes, turn on JavaScript JIT in your browser settings. https://github.com/MutinyWallet/mutiny-web/wiki/Browser-Compatibility#known-issues-include

The default configs would prevent small payments going out if they were much lower than the potential on chain fee. So we removed that limitation.

The mutiny relay does work with NWC but I'm not sure if we have full NWC response support. We'll probably migrate to a full strfry instance at some point.

👀👀👀

nostr:nevent1qqsr93nq9glm34df2wmhxy3ad3taupkn4wm5nsg6w3ny6dvu7vlkpjcpzpmhxue69uhkummnw3ezuamfdejsygx8aknxpf4usfc9xr5zkjnhz2kdaghrrhq22mude926cqy7lktuscpsgqqqqqqsfz02lf

Yes this seems encryption related. We're going to work on a fix today. If you needed it immediately, restoring from seed words and not setting a passcode should work.

We've released a new version earlier this evening to help with smaller payments that were not going through. Let us know if things have not improved on the latest version.