Could be the bip21 QR code or could be due to the taproot addresses we generate. Not everyone has supported sending to them. Phoenix probably doesn't use taproot.

Have you opened the wallet again while it processes? It might be connected or the response might not have made it through.

PSA if you're testing Fedimint in Mutiny, the next release will change storage and will feature encrypted remote storage for ecash recovery.

This will break current ecash storage, get your Fedimint sats off soon. Lightning unaffected.

Thanks for testing!

https://github.com/MutinyWallet/mutiny-node/pull/970

It does. We do not have raw socket support yet.

A new mutiny update for start9 should have hit their store yesterday. Check again.

Sending on Mutiny just got a lot more social: you can now search your contacts (and global nostr users) when sending! There's a lot that changed in this release so let us know what you think.

Expect to see more like this in the future!

https://m.primal.net/HXYW.mp4

nostr:npub1u8lnhlw5usp3t9vmpz60ejpyt649z33hu82wc2hpv6m5xdqmuxhs46turz , start9 needs an update. Multiple reports of this.

Awesome to see!

It should have been fixed recently. Is it up to date?

Awesome to see!

nostr:nevent1qqszegfpmhw7vk6a0xvmykmyedyeljen6uu6vexnplgk4jujlhfjnsgpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqkhv2lm4dvr0jtw76fqtkqfzwudmuh2hu3z2cfpa5nts37q822xsqvzqqqqqqyl9u6ql

Maybe this month or next.

New version of Mutiny (v0.5.1) just released which improves a lot of functionality with Fedimint. Thank you to all the testers so far!

Now that Fedimint v0.2.1 is officially released, you may spin one up and start testing yourself too. https://x.com/fedimint/status/1742680076221612148?s=20

If you file an issue on our GitHub with your logs, we can take a look at what happened.

Do you know if it's actually completed? Do you switch between multiple devices? Typically happens because of that. No easy way to get rid of it beyond restoring the wallet so it wipes the metadata.

Chrome or Firefox work the best.

Yup! Just like the wallet does today via self custodial.

Not yet. Requires a federation invite code and we're using that right now for private testing. Though anyone can spin up a federation and send out invite codes to their federation. We expect that to happen more in the coming weeks and months.

Not heard of this happening. Do you still have plenty of outbound?

Ending the year off strong!

Over the last few months, we've been preparing our wallet for Fedimint integrations. Today marks the first release with Fedimint support ready for alpha testing!

Fedimint is software for managing federated custodian funds. It's similar to the trust model of Liquid but better privacy and without a blockchain involved. It also has first-class support for Lightning.

The way we've gone about the integration is to seamlessly smooth over the edges that exist in self-custodial Lightning. Our hybrid approach will use a configured Federation when needed. Otherwise, it uses self-custodial Lightning if it exists for the user. This helps things like channel reserves, channel minimums, high chain fees to get started, etc.

You may add a Federation alongside your existing wallet or start with one without needing to open channels or pay on-chain costs. We recommend keeping the value low since this is a very early release, and there are some known features that we still need to develop.

It should feel and act like the same Mutiny Wallet with some caveats around backups for now.

A massive shoutout to the Fedimint team for their recent v0.2 release. It's still early for them and us, so all testing and feedback is welcomed! This does rely on having a federation invite code. We suspect that, over the next few weeks and months, more mainnet federations will pop up. There is not a default one built into the wallet.

We should also have Lightning Address support in a few weeks that works through federations. Kody has already started that work, and it seems promising: https://github.com/Kodylow/hermes

Also, there's beginning work on supporting the Lightning Service Provider Specification, which will eventually allow more plug-and-play support for any LSP to power Mutiny. This will be huge for more advanced node runners as the spec matures. Huge shoutout to John Cantrell for that work.

A lot of core infrastructure has been built into this release. Let us know if there are any problems; it should be identical to previous versions if you do not configure a Fedimint or different LSP.

Expect much more to come soon. Happy new year!

Typically it says that if you had pending payments for about a day or two and you never came back online to finish in time. Yes, you'll have to pay the fee again since that's the cost for opening a channel on chain.