Bitcoin, privacy, and FOSS. Run your own node. Avoid KYC. Take self custody. Learn to spend. Build a signing device.
Self-Custody
Joined April 2022
- Tweets4.5K
- Following3.5K
- Followers5.2K
- Likes10.4K
Pinned Tweet
BITCOIN DIY SIGNING DEVICE THREAD
Here I'll keep track of the various complete DIY signing devices and their relevant repositories which contain essential info for acquiring parts, assembling, and flashing.
Bitcoin privacy tools @SamouraiWallet and @SparrowWallet have been added to "The Hitchhiker's Guide to Online Anonymity".
anonymousplanet.org/guide.ht…
Did I dream this or did I read *somewhere* that the @SamouraiWallet Android app will support a "mix to xpub" feature sometime in the future?
Kyle Linkinbio retweeted
From the preamble of the GNU GPL: "[T]he GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. [...]" u.fsf.org/3kz
ALT Logo of "GPLv3." Says, "Free as in freedom" underneath.
So far the theme in 2023 is that trusted third parties having custody of your bitcoin is okay as long as you don't keep too much with them.
Absolutely pathetic.
Criticize @strike or @jackmallers and you get hit with a number of "Mallerisms" from the fanboys:
- regulatory moat
- small step
- superior payments rail
- network adoption
- game theory
The only Bitcoin "adoption" that matters is by those who can and will resist state controls.
If you're interested in learning about practical uses of BIP85, check this out. That's what caused me to begin writing this, and I found it to be extremely useful for making cold @SamouraiWallet seeds that can be selectively imported for private spending.
This quoted post is unavailable.
Custodial and institutional usage of Bitcoin is not adoption. They are unable to resist state controls.
Celebrating an increase of these two as adoption shows how little thought is put into what Bitcoin is.
Time to talk about secure elements again. Because a SE is a chip that's specifically made to handle keys, and because we can't publicly review and *verify* the code that handles the keys, we're forced to *trust* that they're secure. What happened to "don't trust, verify"?
It would be even better to see some sort of public intention to work with @tropicsquare. Doing so would at least signal that a HWW manufacturer acknowledges the issue with closed source SEs and how they're used in Bitcoin.