is anybody working on recurring payments with bitcoin yet ? #AskNostr
Mutinyβs got that
fr ?
Yeah to pay for mutiny plus. I think itβs just NWC that can auto approve payments monthly https://image.nostr.build/094e15c748a21092121ed5f7b9eb65091e47972c67925789acd1184114939465.jpg
So once the external service requests their monthly payment, itβs auto approved if you have it authorized and automatically pays the invoice ? π & is this a Mutiny + feature or free tier
Well the mutiny plus subscription is the only one currently doing that but yeah. Setting up NWC is free Iβm pretty sure
Thank you Harv π really appreciate it!!
You mean like LN
nah like patreon for example, authorize once n never again
I don't think I'd keep sats in that account...ever... Imagine you forget to cancel a subscription, and your sats are gone anyways.... π¬
I mean thatβs just poor management on your end, but recurring payments is needed for a lot of different services..
Agreed. There needs to be an easy way to manage my subscription wallet, cold wallet, and LN wallet all in one place....
Nostr wallet connect is already a thing no?
yes but I only use it to send one tap zaps, how can I do recurring payments with a one time authorization using NWC ? I genuinely do not know how
DIY write a script or even cornychat.com has V4V in settings you can set sats/hr or other value to auto invoice and pay at the rate you configure Alby even does it.
I guess what I was looking for was a wallet that had this feature for the non devs nostr:note1d2dp2lw3fguu2266uvf5nqwnn49qqs6jlydustw5cn4ftkam4q7s9f73mt
You can also use oaknode on Umbrel, but you need your own lightning channel.
Check out the backstage pass on highlighter.com
π
NWC allows that. NIP88 does that.
fr ? LN or on-chain ?
LN π
I was running a DVM with that for 2 months. Subscribe with NWC string, pay daily, weekly or monthly via NWC. Cancel via DVM or by revoking the NWC string.
π ok thatβs prettty siiick guess i need to study up more on NWC
I will bring the DVM back to try it out. I just removed it because I made the DVM free π
I think alby is working on that
π
In July, yes. Recurring and "streaming" payments on livestreams and patreon-style Creator monetization. This month's Peerhub v9 release is just the basic nostr integration tho, then zaps, then the above. Poco a poco as we say here :)
Is there any docs so I can read more ?
Yep, but right now the docs are all centered around the hive blockchain and fediverse, known currently as "hive-tube". This v9 release is a total rebrand though to "Peerhub" with a different repo on npmjs, new website and everything. So around the 15th of this month I will be posting all the new links here on nostr, hive, mastodon, twatter etc and I hope to get onto a couple podcasts to talk about all this more and why getting networks talking to each other is so important.
Because of its architecture it is somewhat difficult since the custody and therefore the sovereignty of the money belongs to each individual. A smart contract could work, but the incentive to pay for a service is that you can unsubscribe whenever you want. Ultimately, recurring payments are now controlled by the individual, there is no such thing as a bank draft in Bitcoin, or at least as far as I know!
thanks!!
Alby has that. I donβt remember how I did it but I have it set to send 21 sats to two different developers each day
prob NWC thatβs what everyone has been telling me so far
That sounds familiar. Tbh, I should probably log back in just to check on things π
https://blog.mutinywallet.com/solving-subscriptions-on-bitcoin-one-zap-at-a-time/
@OpenSecret gib this man a raise!! Thank you sm Marks! π
Check out BIP 352 - silent payments. You can share a single code and each payment made to it is to a new address. Great for privacy and also more convenient. https://github.com/bitcoin/bips/blob/master/bip-0352.mediawiki
Awesome! Thank you!!
zapplepay.com
Any service wanting recurring payment should support NWC. Then you'd connect that app (with alby, mutiny, boardwalk cash etc), specifying amount for monthly budget and creating connection string to use. Each subscription should have its own connection string to support per app/service revocation.