Avatar
OpenSecret
df173277182f3155d37b330211ba1de4a81500c02d195e964f91be774ec96708
OpenSecret is the Confidential Backend for your app. Enable user-level encryption by default to protect your users and yourself. Check out the first app, Maple AI - Confidential AI Chat: https://trymaple.ai
Replying to Avatar Michael

nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll How can we use nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg hosted on nostr:npub126ntw5mnermmj0znhjhgdk8lh2af72sm8qfzq48umdlnhaj9kuns3le9ll on Android? I keep getting "failed to load Mutiny" after adding the same websocket proxy and storage onion url as on the web app.

You're putting an onion URL in the settings? That shouldn't work. Needs an IP address or domain name .

That option allows you to open to any node on the network.

In the "on chain swap" screen, the default is to open the channel yourself with the LSP.

Support the team! It's available for testing for our Mutiny+ users.

We love to see lots of new users try out the wallet and ask questions! We took some time out to answer some of the common questions. It's a different experience dealing with self-custodial Lightning and we hope to address as many pain points as possible.

Let us know if you have any that we might have missed!

https://blog.mutinywallet.com/mutiny-wallet-faq/

Replying to Avatar Settebello

Geez.

Are we at the “And then, they fight each other”?

After teaming up on nostr:npub1hcwcj72tlyk7thtyc8nq763vwrq5p2avnyeyrrlwxrzuvdl7j3usj4h9rq , nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 and nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg are at each other’s throat.

Seems like they see it as a space to conquer.

You guys gotta be careful, your greed and lack of humility will encourage people to fuck off and start their own node.

Whoes going the first hypocrite to answer that they are encouraging self custody? We all know that if we do, you guys are out of business.

I don’t want to be harsh but I’m getting fed up of this feud. nostr:note1vnl6fls3jshkg75nnfnaq40zjjg6h29zdnx4vsdk4phsxu0hxlxsxlq8gp

lol lighten up

Okay great, that was it then. We need to fix it so that the reserve takes into consideration the chain fees. You were the one that opened the channel from your on chain funds, correct? This limitation happens in reverse if the LSP is the one that opened the channel to you. So no fee limit on your end, but less receiving capacity due to channel reserves on the LSP side.

Okay this is typically an indication there might be something else going on here. If you can submit logs to the GitHub link in our bio, we can take a look.

Another thing to try other than that is try topping it up a bit more and seeing if payments send out again? This could be related to additional reserves needed for higher on chain fees.

How much balance do you have available by chance? It might be on our end though, we might need to balance liquidity.

nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg what is the inbound liquidity allowance on each channel open?

If the channel opens from an incoming payment, it's an extra 100k of inbound. There's no extra inbound if you're the one to swap from on chain to lightning.

More than likely what you're seeing on the sending wallet is more of a payment timeout issue. You do have to keep mutiny open for the payment to be received. Are you closing/minimizing it?

Replying to Avatar GHOST

nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg when I send sats to mutiny why does the sending wallet give me a error / failed message but the transaction completes just fine on the mutiny side?

Ask the wallet you're sending from why they gave you an error.