pull down to refresh
Been waiting for someone to try this for ages. Kudos to OpenNoms. Confirms what I instinctively felt — more transparency needed on the points of failure, and more honesty ont be trade-offs.
Either: Lightspark actively funds and fosters a much healthier and well-distributed, neutral Spark operator base (lol yeah right)
Or: only ever keep a few sats in Spark wallets, like paper cash in a real wallet — you might lose it for real real.
Not exactly world-class scalable.
Much better, much more developed product: https://conduit.mobile/en
This is terrific! I am aware of the other phoenixd dashboards but none had quite got the UI right from my PoV. I started to vibe code the exact same thing, with NodeJS.
Great work! Please keep it up. With LN Address and NWC support, plus Ansible scripts for ease of set up (configure domain with Cloudflare API + nginx/caddy setup), this gets towards what I’m working on and becomes a super viable competitor to WoS and Lexe, but with cleaner UI and non-custodial capabilities.
Also recommend that users are able to read their seed.dat in app for easy back up.
Keep it up!
I read a lot of finger pointing and blaming others but very little introspection. TLDR we are a way off users being able to mass adopt.
OP by their own admission runs an Umbrel and is a Linux user. By default, this is an advanced user, deep down the rabbit hole and with the tools needed to enjoy bitcoin to its fullest (lightning + lightning address).
The reality is, though, that this is hard to set up and nothing that someone today is used to when they compare to their current financial setup: open bank account (because they want and need one), then download app and log in. Often this is the same process, now.
Custodial services can replicate this, and hence dominate (Cash App, Coinbase, Strike), but non-custodial still presents many UX hurdles.
Increasingly, with time, I am observing that a lot of this responsibility sits with developers’ choices of what they expose to the user and the language they use to describe what is happening. It’s technically bamboozling to someone trying to adopt.
And that’s before we get into Lightning liquidity and whether or not to use Cashu, Spark or Ark to mitigate the downsides.
How the hell does anyone type that bitcoin ascii symbol, anyway?
And the dunking on LNURL really discredits this post. A group of bitcoiners willfully rejected something that found market fit because they’re not fans, and then promoting the same thing but worse.
There’s much of the “gist of the idea” to agree with here, but it’s still impractical.
Indeed this guide is very good. Some elements could be clearer but we have AI now.
I see two main advantages, even if not running a routing node:
1/ speed goes up noticeably versus a tor only node.
2/ if you open even just a couple of public channels, payment reliability jumps considerably.
As others have said, but in overly complicated ways, this is very achievable and you can do it. The first time you set it up might feel unclear but you’ll get it quickly.
Rent a VPS — any VPS. Ideally you pay for that VPS with Lightning. Check out https://bitcoin-vps.com/
Install Wireguard, fail2ban and ufw.
Setup Wireguard tunnel between node host and VPS. Open port 9735 on both sides. VPS side if you’re not familiar with IP tables etc, you’ll need to use chatGPT, but it all lives in the Wireguard config (wg0.conf)
Once tunnel works, edit LND Conf to broadcast VPS IP.
Done.
I don’t understand why, when he had Bitcoin and the terminal accepted bitcoin, the payment had to be made in arbitrary stablecoin. Square and Cash App did the hard work of removing the dollar. Where is there demand for what David is demoing?
I felt sorry for the Design guy who David gives 30 seconds of airtime before wanting you back on his ego.
About time flags were raised. Marcus is duplicitous.