It's now the big yellow button at the top called "find an autozap page"
Yes, just the zapplepay nostr key for now. Wonder if there's at all a good delegated way to signal it's on behalf of someone else. Pablo might have something out soon related to this from the sounds of it.
Please. We've talked to a few that want to do this. I think with NWC extensions, we can do this.
Not possible yet unfortunately. There's a few challenges around it.
For anyone that needs it https://app.mutinywallet.com/settings/connections
You can put whatever you want, that's just a name for your reference.
Profile picture isn't showing up, but here.
https://www.zapplepay.com/autozap/npub1ftj3tmr44tdzs93e0hdgfnrrct9pu2e8haylzuatm2tkfwdaudds27pjju
Check your profile image. It is not loading in amethyst either right now.
Not at all. Auto approval has a check box in the wallet connections area.
Yes, this works for any device and wallet that has NWC including Alby.
We want to integrate it into mutiny more in the future but we wanted to demonstrate how anyone can use the NWC tech for different use cases. Check out the zapple pay autozaps page to see it in action. We think it is pretty accessible but let us know if not.
We've been thinking a lot about subscriptions at Mutiny and how others can take advantage of it.
Today, ZapplePay just shipped AutoZaps. It's like a decentralized Patreon: every npub gets their own page where people can set up recurring payments to them. https://www.zapplepay.com/autozap/
AutoZaps and ZapplePay use NWC (Nostr Wallet Connect) to communicate with supporting wallets such as Mutiny and Alby. Both wallets have budgeting features so you can auto-approve payment requests associated with a specific NWC string.
We built Mutiny+ using this same NWC tech. Bitcoin is a "push" system, so replicating fiat's "pull" payments in a self-sovereign way involves new ideas and standards. NWC keeps the user in control, and offers the convenience of autopay when you want it. https://blog.mutinywallet.com/solving-subscriptions-on-bitcoin-one-zap-at-a-time/
Check out AutoZaps and see what you think! We're looking to work with other services / products that want to offer NWC-based checkouts and subscriptions so hit us up if you'd like to chat.
You may have given up but we haven't.
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg getting a connection error for the relay - I can dm error log if helpful!
To the mutiny relay?
If a force close just occurred, it may take up to a day or two for the funds to become available.
That sounds more like when this would have occurred. We made a few fixes for that since then and some more on the way. Let us know if the funds don't sweep back. After the next few days.
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg I just realised my mutiny wallet had its channel closed but I don't see any funds, even on chain.
I have a channel id with the following reason:
Channel closed because of an exception: Peer's feerate much too high. Actual: 10979. Our expected upper limit: 6250
Where can I see the tx id to see what happened? Fees vs outputs etc.
Typically within a few days that'll get swept back to your wallet. That's a really high fee estimate that the wallet is protecting you from, but it should hopefully be fixed in a couple weeks from happening at all.
Most of the time it just takes a few days to sweep the funds back. If you open a ticket here with logs, we can take a look: https://github.com/MutinyWallet/mutiny-web/issues
Potential force close that needs time to sweep. Can open up a ticket here with logs and we can take a look: https://github.com/MutinyWallet/mutiny-web/issues
There's a pending PR with them as well. The problem comes down to SSL support with umbrel.