Ad hominem would be dismissing the case for ECash because it is made retards, that's not what I have done... I have said there is simply no case for ECash.
Maybe spend more time on vocabulary and less time on ways you can sign useless strings over to yourself.
A channel per device is wasteful, it'll be too low volume to be sustainable and will get closed
For kids, share a family node over Nostr with lightning.pub and ShockWallet
The privacy properties are a hoax too
nostr:nevent1qqswv5j3kj8c9qtc4a8m8lkxqxmvegpl28s9ppxdephzt24f9c8vk8cpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7q3qyxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96sxpqqqqqqznvkw34
Circle-jerk signatures all you want, Bitcoin is the only goal post
Bitcoin in has metadata, Bitcoin out has metadata, if you don't trust a custodian with that then no crypto-wanking can help you
I don't care about any crypto nonsense, it's not interesting, it's completely useless in any trusted or custodial context... total distraction for tinkerers that can't stick to a long term vision like real Bitcoin
Some people are retarded.
Is an LSP trusted if you pay it out-of-band in hopes they open a channel in return? Absolutely.
Fortunately, LSP is just a made-up term by some company, that is now reselling blockstream cloud nodes. Coincidence? LSP's aren't a real thing in the protocol, you don't need one... you can just open a channel like you would make any other chain transaction.
Whataboutism doesn't address the fact that circle-jerk-coins don't improve anything... just mindless cope for pedantic fetishists that were too dense to bother understanding the profundities of Bitcoin.
Lightning doesn't have to be perfect for ECashers to be complete morons, but that said it does scale sufficiently and trust is optional.
Whatabout Lightning all day if you want, it won't change the fact that ECash doesn't improve anything. Just another retarded custodial shitcoin that skates by on privacy virtue signaling by the same retards that think they're private behind Tor and their CIA run VPN.
The privacy properties are a hoax too
nostr:nevent1qqswv5j3kj8c9qtc4a8m8lkxqxmvegpl28s9ppxdephzt24f9c8vk8cpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7q3qyxp7j36cfqws7yj0hkfu2mx25308u4zua6ud22zglxp98ayhh96sxpqqqqqqznvkw34
Relays are no different than any other hosting service in terms of incentives, they're a CDN for notes.
Some hosting services cater to illegal content, like seedbox services for torrents.
Others, like business tier S3 with a terms of service, do not.
The only difference vs. traditional hosts is that Nostr uses keys/signatures so that data is verifiable and therefore can be easily distributed across redundant hosts (exactly what torrents do by using redundant trackers with hashes to ID files).
Unlike torrents though, there's a reputational lever available in Nostr because of author keys. This will allow it to become more email-like, where servers generally drop everything that doesn't pass some checks.
Email and traditional file hosting is enured to legacy DNS/IP4 limitations, and therefore not as simple to have provider redundancy, which makes service offerings less commoditized than is possible with Nostr relays.
So, while Nostr is an improvement over legacy hosting services in terms of censorship-resistance, there's no magic that makes it a different animal in terms of incentives or how it evolves service hygiene.
I'm pleased to announce that we've finally opened the pull request for NIP-68, Lightning Debit Requests.
These ad-hoc debit requests, when combined with NIP-69 offers, provide a more intuitive, secure, and scalable successor to NWC that actually leverages Nostr for identity of Apps and Services.
Pairing an app is now as simple as entering a Lightning-enabled NIP-05 address and clicking Approve or Deny in your wallet.
The implementation is live in ShockWallet's PWA and Android build with iOS coming later this week.
A temporarily forked nostr-tools is also available for ease of integration.
Check out this UX sample: https://m.primal.net/LPAk.mp4
Both nostr-tools and strfry have less stars than the NIPs, that's the inversion to watch for, because they are what provide actual utility
Specs are meaningless without implementations, particularly nostr specs where they're generalized json and websocket schemas that are indistinguishable from every other app on the Internet
Yea and I actually recall someone making the point it should have been binary
Ultimately it's the implementations that make the rules, the idea of bouncing signed data off webservers is as old as the web itself... Nostr just made it simple for midwits to understand so they could feel like contributors... that came at the cost of a larp army obsessed with retarded specs, not implementing shit that actually works
Nostr can only succeed if there's a broadly useful SDK, which imo has to have commercial motives
That's how we use it in ShockWallet, but it makes NWC redundant, the lightning address bridge server uses it to get the invoice from the node
Example implemented here:
GitHub.com/shocknet/bridgelet
I believe that's a limitation of their node software not nwc itself, we so things differently with lightning.pub so each user wallet can have there own or multiple nip69 offers/lightning addresses
Under notifications there will be a reminder to back up credentials once you receive sats, click this it will take you to auth... otherwise there should be an auth link in the hamburger menu
You're not the first to point out this is unintuitive... trying to design something cleaner...
Nostr is literally websockets and json, things that make up the web already.
Relays are just databases, things that make up applications already.
Just because you don't know how to scale them doesn't make them not scalable, and as far as I know there's only one developer actually working on scaling it @Doug Hoyte
Scale will come quickly ones its made a priority.
Relays are no different than postgres in a traditional stack, they "relay" data across time in (conjunction with middleware)
Ditto is right because it introduces proper middleware rather than clients speaking equivalent to SQL directly, and relegates the relay back to its core database functionality.
The mastodon influence im not a fan of, but it's directionally correct to have application middleware between clients and the database (relay)
IP filters will eventually block new people as well, those using popular VPN's, ISP level IP4 gateways, Tor exit relays, college campuses, the list goes on... attackers can unfortunately get their hands on IPs just as easily as they can generate new keys
Soft forms of WoT via invite links or PoW seem more promising
Yea thats fine for short-term rate-limiting defense against DoS, but doing anything reputational with IP's beyond that will hurt new users even worse in the long run
Tiering works well in many environments, for example you can still allow new users with no friction but also impose a basic rate limit (or kind restrictions), with upgrades to those permissions achievable either via a PoW flow, WoT-invite flow, or just good behavior heuristics over time
Architecturally very similar to what we do with ShockWallet and Lightning.Pub so it's nice to have the validation, and honestly I always kinda felt browser extensions / WebLN were retarded 🤣
I'm fairness that's only because it's trash engineering that doesn't work, and is only being propped up by a few salaried devs funded with opaque objectives.
Live for testing on ShockWallet and demo.nip69.dev
nostr:nevent1qqs02hng960kaf2kertxg5qtxu8u9eng87s798xa3z4rfn0qtkkx5rcpz9mhxue69uhkummnw3ezuamfdejj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqzc3ad03
If you have an old laptop you can dedicate to throwing linux on (or $5/mo for a VPS), you can set up a Lightning.Pub by pasting one line of code
That'll will set up a Lightning node that allows you to connect ShockWallet to it over Nostr, it also provides for inviting friends/family etc to share in your liquidity
Pub will give each user a noffer string, and the wallet will use it to get a shockwallet.app lightning address
Lightning.Pub instructions on Github: https://github.com/shocknet/Lightning.Pub
There's comparison to Bolt12 in the PR comments, Nostr-native offers feature better performance, portability, web-friendliness, and privacy than Bolt12 offers
There's comparison to Bolt12 in the PR comments, Nostr-native offers feature better performance, portability, web-friendliness, and privacy than Bolt12 offers
Privacy focused products generally spread through virtue signaling, not substance... Unless you really know what you're doing, privacy tools are just honeypots
All these shitfork proposals enable externalized consensus to pervert the incentive structure
They're funded and astroturfed by the same cabal that uses shitcoins to muddle the industry.
Open just a couple channels for your own/family use to save yourself chain fees, don't expect to earn routing fees and go overboard. Routing isn't for casuals.
In that case I would recommend reading and watching anything written or presented by Alex Bosworth over the last 5 years
Good starting point, https://www.youtube.com/watch?v=HlPIB6jt6ww
Cashu/ECash is a bad design choice for this usecase imo, it makes tradeoffs incompatible with fluid mass-adoptable UX because its just layering the management of a new shitcoin as opposed to direct RPC access
Save for enterprise-scale environments, Pub isn't any less private either as it uses ephemeral keys that are blind children not tied to a given identity. A user could have one or many, rotate them, etc. Also with friends/family nodes nodes the anonymity set is so low that becomes the common limiting factor... whitelisting keys would also negate any privacy benefits
If however you are already running a mint, it could conceivably serve as a backend for Pub... while we built on a single implementation to focus on security (LND) we did so in a way that adapters should be relatively simply to implement
Most of the benefits come from it being always-on 24x7 but it won't hurt if it goes down from time to time
It'll run on Windows/Mac too but would be a manual installation
I personally recommend an old laptop with clean *buntu install, the built-in battery makes it much less likely the node gets corrupted. Since it uses neutrino a 4GB of RAM clunker with ~20GB of free disk should be adequate (would suggest an SSD at least though)
If you're the node operator then its self-custodial, with the option to add custodial guests. The goal is to let people who prefer a custodial solution keep that as close as possible. Most people share a house/fridge/car with people already, and they'll share a node / channel too.
There's no benefit in Cashu as it's the same scenario with either... if you run your own mint then its self custody, else it's custodial.
ECash is worse UX because there's fragile gateway and settlement layer between it and real Lightning payments, and on the client side you're reintroducing bearer shitcoins thus making the worst combination of trade-offs: a custodial solution that still requires key management.
It's not that Pub is more private, it's just not less, the overall point is that you shouldn't use either for privacy as both are limited by the nodes anonset. Since a node operator has countless ways to deanonymize activity, you simply shouldn't use a custodian you don't trust and ECash doesn't make a custodian you don't trust anymore trustworthy. ECash's privacy benefits would only come at bank or government level scale which is even more dangerous because of how much oversight those mints would have into the flows of the Lightning network... this is why it's so important we make custodians small... ECash is for governments not families.
Huge milestone ⚡️🎉
1-line deployment of Lightning.Pub, a Nostr-powered Lightning Node
In this demo I set up a node, from scratch, in 2 minutes with a connection to a management dashboard as admin, and then connect another user with guest link... completely over Nostr with no tricky networking or sluggish Tor
https://m.primal.net/JcEi.mp4
Thanks!
Wallet is the client and has a node manager built in yes, the Nostr RPC comes from the lightning.pub repo, if you look at the methods there on GitHub you can see all the calls we make over Nostr... It's just like a regular http API, but we built a proto generator that takes the API and spits it out as Nostr interface code
We also recently PRd NIP69 to enable static payment codes over nostr without the full interface, debits coming next in a companion nip
Oddbean new post about login | logout
Notes by shocknet_justin | export