I was under the impression the nostr event that tells Mutiny to zap gets sent immediately (and then Primal shows it was sent). But the next time you open Mutiny (unless it’s still running in the background, or running on another device), all of those payments actually get sent out (automatically, not needing to approve each one). Maybe I’m mistaken. Will have to test it out again.

Without adding a federation, zaps don’t send until you return back to the Mutiny wallet. If you’re using a federation, do zaps send automatically (assuming they’re below your auto-approve budget)? Or is the case of needing to go back to the Mutiny app for them to send still how it works?

This post was hard to get back to. Any idea why this post wouldn’t be showing up in search? I tried searching for Phoenixd, LNbits, Docker, all with no luck.

My first question was ‘what are the fees’. Leaving this here to save others a click: https://phoenix.acinq.co/server/auto-liquidity

Seems reasonable for someone wanting an easy to set up, ‘set it and forget it’ type solution.

This makes you feel less comfortable with VPN use at an AirBnB or a coffee shop though.

Thanks for the great guides!

Haven’t tried this one yet, but here is a way to get a lightning address that points to your Phoenix server: https://github.com/AngusP/phoenixd-lnurl

Doesn’t seem like the raw data contains any info on Bitplay’s node unless I’m missing something: { "human_readable_part": { "prefix": "lnbc", "amount": 2500000 }, "data": { "time_stamp": 1710758579, "tags": [ { "type": "p", "length": 52, "description": "payment_hash", "value": "6f89c5b8af9dd7be2643cf364516c581cb703dddba1a4bafb5ff60497aacc72b" }, { "type": "d", "length": 16, "description": "description", "value": "Betplay.io" }, { "type": "c", "length": 2, "description": "min_final_cltv_expiry", "value": 80 }, { "type": "x", "length": 5, "description": "expiry", "value": 1209600 }, { "type": "s", "length": 52, "description": "payment_secret", "value": "4654fadf20713cc0f8d662f11e8045559c7d7684c633efe90ef5339416bab32f" }, { "type": "9", "length": 4, "description": "feature_bits", "value": "00100100001000000000" } ], "signature": { "r": "3cc2d99567edb942bf7b15004b7630fe9839d7c00e2fef33b561f2247bdf7e7e", "s": "257abcb4f2266612719a9e0b64e1956082a720032cca3fc3696e06a7ab246721", "recovery_flag": 0 }, "signing_data": "6c6e62633235750cbf0356610d1be2716e2be775ef8990f3cd9145b16072dc0f776e8692ebed7fd8125eab31cac1a082132ba383630bc9734b7e002140c02849d40201a232a7d6f90389e607c6b31788f4022aace3ebb426319f7f4877a99ca0b5d599781404242000" }, "checksum": "ya06qv" }

Yea, and other incoming payments were working fine into the other wallets I tried. Good thought though.

Hmm another interesting theory. I’m pretty sure it has been like this since before WOS closed up shop for the US though.

I haven’t. I’ll have to do some digging. Find a way to get information out of a deposit invoice to learn more.

Interesting. I wonder what the reason for that would be over just allowing withdrawals to any lightning invoice if that’s the case. Thanks for the info.

Solid theory. Would be nice for their error messages to be more descriptive, but seems like a good explanation.

A good reason to find a way to make it work with another wallet if possible

Mentioning in this pop up that the fee will be calculated on the next page would be useful info. I remember being a bit confused by this my first time through before realizing it was calculated on the next page.

What is the difference between "data plus" vs "no number" plans? They seem to have the same description on the ‘buy’ page.

Update: it works for me in the browser, but not my PWA instance. Adding wallet connections can also be pain sometimes with the PWA, as the app I'm linking wants to take me back to Mutiny in the browser, not back to the PWA. Maybe I should just move back to the browser instead of the PWA. That would be as simple as making sure my PWA isn't open in the background, then going to app.mutinywallet.com, and restoring with my seed words, correct?