My biggest objection to the new eCash implementations atop of Bitcoin is that they carry *both* self custody risk and second-party custody risk
Lose your eCash wallet or backups, money gone
eCash issuer (bank) decides to run away with actual Bitcoin, also money gone
Gimme haha đȘ
1. Take monkey over
2. Return empty
3. Take tiger over
4. Return with monkey
5. Take banana over
6. Return empty
7. Take monkey over, done
(Dumb qn) How does that work for sending the right payment amount? If you send an ecash it has a fixed amount right, so do you get a new one back as change?
Or when initially paying the LN invoice do you get a ton of worth-one-request ecash tokens back?
Any Advancing Bitcoin-ers going to the Real Bedford game today?
(Tagging #[0] because the pirates đŽââ ïž donât seem to be on Nostr (yet))
âŠwhich pretty-much by definition means Bitcoin is not a security
The SEC will đ
Argh, why is setting up LUKS+btrfs such a pain in the ass on Debian but a breeze on Fedora!
Anyone got a good guide for doing it? Seems like youâve got to manually poke around in the shell or jump around the installer to get it to play ball đ«
Want to play with #[0] on a spare machine, but IMHO disk encryption is a must and btrfs snapshots make backups easy
If you want shitcoiners to be interested you need a new pointless token to pump đ
They genuinely seem to lose interest quickly if thereâs not a âhow do I get rich quickâ angle
I donât think thatâs true, I successfully swept the funds I had in BWâs custodial Lightning yesterday (a whopping 35 sats đ)
You have to remember to account for a fee, so I had 35 sats but invoiced myself 34, paying a 1sat fee. Annoyingly you can only guess what the fee will actually be and try again if you guessed too low, but 1sat is common.
Potentially theyâve got some channels that need rebalancing before they work properly again, given their flows will now be mostly outbound
Coinbase have been shitcoiners and smoothbrain big-blockers for a while now đ
We got her fam. đ€
Get your questions ready and join us for a live discussion with Mandibles author Lionel Shriver this Friday at 11 ET / 1600 UTC.
twitch: https://twitch.tv/citadeldispatch
youtube: https://youtube.com/@citadeldispatch
bitcointv: https://bitcointv.com/w/nYGx7Eg3C3jWACS2JMbKAf
matrix chat: https://citadeldispatch.com/chat

My only demand is she must try to orange pill her colleagues at the Spectator đ
Point of Sale UI? (Think itâs great to have in Breez)
Ah actually the higher-end Optiplex Micros (5000 series) do have two M.2 slots for SSDs and still have one SATA, though theyâre a bit more expensive
Yes, one SATA port and one M.2 internally. Ideally youâd want matching (like two M.2 drives) but itâll still work fine in btrfs/RAID
Proof of steak (đ«đ· Edition)

Iâd also be interested if the thing weâve âdiscoveredâ about segwit and taproot after the fact (inscriptionsâŠ) have changed attitudes against âcool but very complicated so few understandâ changes in core
IMO it should continuously get harder and harder to change core, to the point that only changes that avoid catastrophic badness can get in (I mean Consensus, Standardness, not QT UI fixes)
Current FUD from MSM about how âsmall number of devs can just change the codeâ and presumably they think weâll all upgrade⊠but would be good to have a solid discussion on why thatâs not the case, and what core devs can do easily via whatâs very hard for them to do without consensus
Very similarly specâd Dell Optiplex micros also available and work great đ€
Donât treat DMs as particularly secure, theyâre pretty simple an donât have many of the good properties that existing E2EE messaging alternatives like Telegram/Signal/WhatsApp have (ratcheting keys, key exchange between two parties, etc.)
You leak your nsec and all your past DMs are readable and youâre easily impersonated. Also everyone can just see who youâre messaging and when, even if they canât read it (because the DMs are jus events published to your relays like normal posts)


