keep falling asleep with hardware components and frostsnap prototypes in my pockets
"irresponsibly all-in" doesn't have the same ring as irresponsibly long, but best to not use leverage
2024 shitcoins: imagine we took the continuum limit of high stakes coin flipping and added a funny name
they were so real for this
Signed addresses / list of known payees?
we want to do this
This node has been used in the creation and testing of the satsale app in 2021, making a mess of the env trying to learn docker.
And more recently in creation of the nolooking app, where nostr:npub1yevrvtp3xl42sq06usztudhleq8pdfsugw5frgaqg6lvfdewfx9q6zqrkl + I opened many lightning channels in single transactions, some failing in weird states during development
Only hardware failure has been the sd card. That took a while to fix because "solutions" that assert your harddrive is corrupted are big storage propaganda
It's a rpi4, only actual hardware failure so far has been the SD card
My tortured umbrel node is almost done resyncing.
Going to check the force close damage and finally put it out of it's misery 
Yep! Lightning support for LND, Core Lightning, and LNDHub.
Lightning address works for LND and Core LN (branch awaiting review). You just need a domain name and somewhere to host satsale. Zaps soon™
i want us all to have self-custody lightning addresses and zaps
https://github.com/SatSale/SatSale/issues/135
This is what a SatSale config looks like
Release time!
In our biggest update yet, we've completely redesigned the home screen, added a nostr-based profile setup walkthrough, and have finished our initial fedimint integrations by adding a federation discovery & recommendations!
Most lightning wallets these days are what we call "invoice-oriented." We want to go back to the basics to solve what people are really trying to do: paying a person. We've added a new wallet creation flow to make the wallet about you!
The new version of Mutiny now allows you to create a new nostr profile, or import a nostr private key from an existing profile. From there, you can now DM other mutiny & nostr users to send or request money directly from the app. No more copy / pasting invoices!
To double down on social, we've redesigned our home screen to put people first. We now include a row of recent profiles for quick access. We also now have tabs on the home screen for looking at your payment activity, your friend's zap activity on nostr, and your payment requests.
Next up, better fedimint support!
Mutiny has had beta support for the fedimint protocol for a couple of months now. Instead of opening a lightning channel on your first receive, with a minimum of 100k sats, you can get started on a fedimint with just a few sats.
This new update adds a way to discover available fedimints to join. Naturally, the discovery process is powered by an open protocol built on nostr. You can see who recommends a federation, and add it with one click.
You'll automatically receive funds to that fedimint, as long as the amount is smaller than 200,000 sats, and you'll automatically spend out of that fedimint, with a fallback to your regular lightning balance. You can also swap from fedimint to your lightning balance at any time.
Coming up shortly after this release, we'll be adding federated lightning addresses that lock incoming payments to your key, which you may redeem at any point by coming back online. We'll be rolling this out to Mutiny+ users first, stay tuned!
Let us know what you think! We're excited about this new direction and need feedback to help us continue driving forward.
https://blog.mutinywallet.com/mutiny-new-design-people-oriented/
what's her npub?
ive seen extremely fucked posts on nostr twice now, you're going to want *some* localized censorship
i only occasionally listen to podcasts but damn does Citadel Dispatch keep producing insanely high signal episodes that i simply must watch
if only you knew how good things really are
wtf did i miss
GM
goals, what did you post
The ecash-zaps conversation is something new, I don't know if there's been more discussion about it, but afaik it's something that's happening live. Maybe nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg can tell us a bit more.
But I think the p2pk option and locking to a public key makes sense for this use case because it makes the process non-interactive for the receiving user and yet I imagine you can know the value of the nut. This way the clients could account for that value, because we assume that the nut can only be used by that user and no other user can spend it, so clients can account for that and display it like the current zaps.
Encrypting it is a valid option, but requires user interaction to decrypt it and then add a step to make the nut/value public(?). I think p2pk would be more suitable for this use case.
Zaps are already interactive with zap receipts, but it would be nice if they weren't
https://github.com/nostr-protocol/nips/blob/master/57.md#appendix-e-zap-receipt-event
there are no men on Nostr