pull down to refresh

0 sats \ 0 replies \ @stackingharder OP 5h \ on: Day 3: Lightswap - Every Pixel Is a Choice. builders
First 100 on the newsletter get beta access. If you care enough to read this, grab your spot: www.lightswap.com
I like the idea of changing the display unit depending on the amount, but layering on other units such as kilo mega centi feels like over-engineering… cool for us nerds but for anyone else it may seem too much
Agreed, 50,900,000 does look silly. Never really been a sat guy tbh but I see the need for it.
₿0.509 feels right to me — if someone has around $1,000 in bitcoin that’s about ₿0.01, which still looks reasonable.
I think giving users a choice between sats and bitcoin makes sense, or making the UI contextual based on balance. For example, default to sats for $50, but switch to bitcoin around $1,000 — with a brief explanation to the user.
I just mocked this one up now.
I've been following the recent debate on sats vs bitcoin UI... I don't have a strong opinion on it yet but I'm working on it.
Which of these makes most sense to you?
BTW: Day 1 is here: #1142435
Here's Day 2: #1195166
We love multisig but for v1 we’re laser focused on single sig.
Yes you’ll be able to import wallets using descriptors. We don’t have .dat files on the roadmap but we’ll add it to our future features voting board so people can tell us what they want to see.
Great question and one we’re constantly thinking about.
Where you trust Lightswap:
The app itself (and future updates) aren’t malicious.
The UI shows you the correct addresses and amounts — and you verify them in Lightswap’s confirmation screen and on your hardware signer’s trusted display before approving.
Our backend that parses your text intent isn’t exfiltrating sensitive info - although we don’t have any private information- we don’t ask for or know your name, personal details, or keys — just the natural-language request.
Failure cases we think about:
- Compromised device or malware
- Malicious/supply-chain app update
- UX mistakes (e.g. skipping checks in-app or on your signer and approving blindly)
These are the same classes of risks you already have with, say, a Kraken or Cash App client or a hardware wallet. We mitigate with Secure Enclave storage (or equivalent), clear verification prompts, seeing or storing as little information as possible, open-sourcing our code and aft some point we’ll explore reproducible builds so anyone can verify what the binary does.
As you said, you can always verify deposit/withdrawal addresses independently on your hardware signer or exchange, and that’s encouraged. Our aim is to keep the trust surface as narrow as possible.
No system is perfectly trustless but we want users to understand exactly where trust is required and to minimize it wherever possible. Questions like this help us get there.
What’s one thing you’d like me to share over the next 21 days? Design sketches? Security model? Behind-the-scenes of building?
Thanks @bitcoingecko! We can’t wait to show it to you next month ⚡️⚡️⚡️
Thanks @Stackernerd! If you haven’t already please sign up to our waitlist so we can be an early user when we launch.