Costume: Stephen and Lipsi are Alice and Bob, your favore asymmetric cryptography example characters https://nostrcheck.me/media/public/nostrcheck.me_2762973159025785401698455669.webp
Bob can’t afford shoes because he’s been the victim of too many cyber attacks
Costume: Justin is generic 50s greaser guy. https://nostrcheck.me/media/public/nostrcheck.me_1722755223637749381698454425.webp https://nostrcheck.me/media/public/nostrcheck.me_1789011319232365161698454432.webp
Is that a Coldcard in there?
Elon is turning X into the WeChat of the West.
The EU is planning to roll our their CBDC.
All within the next year.
The time to push Lightning to its limits is now. nostr:note1zvp2aymnzsw5jy6yzql0x64qv0nctk3rx0vvrvjhz0ad6jv5jadspc98ud
Might name my bar the Taproot Taproom
Nope, unfortunately not. But contrary to popular believe you can still find good souvlaki in the US
Just had a fantastic souvlaki. AMA
Invoice won’t get generated
Nope still 10k for an open
Would sacrifice the fee percentage to be higher then. Would have to be at least 25% then
Thinking about tweaking our fee structure for ZEUS PAY:
A
Min amt: 10
10-1,000 sats: 20%
> 1,000 sats: 200 sats
B
Min amt: 20
20-2,500 sats: 10%
> 2,500 sats: 250 sats
Note that with these lower fees, you’d almost certainly need a channel from OLYMPUS to be able to redeem payments on the low end.
Whatcha think nostriches? A, B, or are both still too high for you to consider using for zaps?
No promises, but would love to get some feedback.
If you have the technical chops you may even want to do a trusted funding channel. You will save on onchain fees too.
It is an advanced set up though. Not recommended unless you can get your hands dirty
It’s going to evolve over time but the challenge is ensuring that we earn enough in sats on the payment to route the payment to you.
Maybe the fees get lower at the low end but then you’d almost certainly have to use ZEUS PAY in conjunction with an inbound OLYMPUS channel
Yes. It would give you security benefits to not expose your whole Lightning stash to your phone.
Check out our docs on how to do so: https://docs.zeusln.app/category/embedded-node
Sorry. Need a channel to redeem or need to get sent 50k+ in one go to trigger a chan open from OLYMPUS
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.
Very cool. Congrats on the launch 🚀
Invites sent! Thanks for playing.
Making our final tweaks to ZEUS v0.8.0-beta1. Thinking of tweaking our default Nostr relay list for ZEUS PAY users.
Here's the current list:
wss://relay.damus.io
wss://nostr.wine
wss://nostr.lnproxy.org
Who should we add? Who should we remove? Why?
ATTENTION ZEUS v0.8.0 iOS ALPHA TESTERS
A new TestFlight link is available for testers on our alpha portal web page.
However, due to our new developer account, all settings and configured wallets and remote nodes will be lost when upgrading to ZEUS v0.8.0-alpha61 (build 61).
If you're using the new embedded node, it's recommended you close your channels and wait for them to settle before proceeding. Before joining the new TestFlight you should also uninstall your old instance of ZEUS, and remove the old TestFlight instance from your TestFlight app.
If you are using ZEUS PAY, you will be able to access your old account as long as you use the same seed phrase. If you enter in any handle on the create account screen and hit submit, your old account will be restored.
If you experience issues redeeming ZEUS PAY payments, you may have to resubmit your payment hashes to the service. You can trigger this by changing your Nostr key under 'Change Nostr keys'. We suggest changing to a random one, submitting, then reverting back to your actual key and submitting again.
Want to hang on to your existing channels for now? If you're on build 60, you will be free to continue using it for the next 89 days. The tradeoff is that you will not be able to receive any software updates or receive ZEUS PAY notifications.
We apologize for the inconvenience. This was a necessary step to take as set up our new company and was unfortunately unavoidable. We hope this is the last of our growing pains as proceed to take ZEUS to the next stage in its evolution.
Android users are unaffected.
Yes
What do you have against Scooby Doo?
You’re gonna feel like an asshole when all the people you onboarded onto custodial wallets get rugged or worse.
Knock it off.
Hi nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 just checking in. Are hue still mad at us? 😔
Hope you’re day is amazing. ☀️😁
Haha it’s ok. I’m just giving everyone a hard time
They’re up for grabs again
Interesting! So your node does a HOLDhtlc and sits on it until she comes back online? That’s cool AF 
Precisely
I had noticed after the splicing update fees were getting higher on Phoenix wallet, so I finally got around to testing a couple new options.
---
First up is Mutiny wallet, I'm really liking it! The Android APK is working well now if you happen to be on that OS.
I tested sending lightning payments up to 1M, using Alby, WoS, and Zeus with Olympus LSP as receiving wallets. They all worked. Fees were reasonable, ranging from 11-25 sats for the 1M sat transfers.
---
I also set up the Zeus integrated lightning node, Olympus. I like the Zeus interface, I use it as a front end for Alby on my phone.
Zeus had trouble sending larger payments. I wasn't able to send over 250K in my tests today, once again testing with WoS, Alby, and Mutiny as receiving wallets. Fees were a bit higher as well, 84 sats consistently for a 250K transfer.
---
nostr:npub1mutnyacc9uc4t5mmxvpprwsauj5p2qxq95v4a9j0jxl8wnkfvuyque23vg and nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 are still in beta, so your mileage may vary, here be dragons, etc. Both are much better in respect to fees than Phoenix is currently. I have decently large channels open in both now, so I will be able to continue testing more in the future. I can't wait to see what they build going forward!
#lightning #bitcoin
Try enabling Express Graph Sync in Embedded Node settings to boost your chance of payment success.
Routing is done client side so you need to get the LN graph either through P2P or Express Graph Sync
vim is a bolt12 maximalist
Zeus v0.7.6-beta2 is now available for testing.
## New in this build
- Bug fix: iOS FaceID login loop
- Bug fix: Core Lightning: display multiple channels per peer + update msat fields
## v0.7.6 Highlights
- Notes: add ability to leave notes on transactions, payments, and invoices
- POS: associate existing payments with open orders + hide open orders
- Fiat exchange rates: add ability to choose between Zeus and Yadio as source
- Bug fix: LNDHub: balance refresh
- Bug fix: Compatibility issues with CLN 23.05
Full release notes: https://github.com/ZeusLN/zeus/releases/tag/v0.7.6-beta2
## External links
PGP Key: https://zeusln.app/PGP.txt
### Android
Universal APK https://zeusln.app/zeus-v0.7.6-beta2-universal.apk
arm64-v8a APK https://zeusln.app/zeus-v0.7.6-beta2-arm64-v8a.apk
Manifest https://zeusln.app/manifest-v0.7.6-beta2.txt
Manifest Signature https://zeusln.app/manifest-v0.7.6-beta2.txt.sig
### iOS
TestFlight https://testflight.apple.com/join/gpVFzEHN
#[0] appreciate you going out of your way to acknowledge and address the privacy issue with Zaps and adding a private option. Looking forward to it being integrated on all clients cc #[1] #[2]