Mark Engelberg (@mark_engelberg) profile picture

Always prefers the alternate ending in the special features. @mark_engelberg@techhub.social [email protected]

Joined April 2015
Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)Photo by Mark Engelberg (@mark_engelberg)
Replying to @Fidelity
@Fidelity claims that @Strategy failed to pay the $STRC dividend at the end of September. True or false?
1
1
129
It would be helpful if other @Fidelity customers with $STRC could check their statements for the dividend. Assuming @Strategy paid it, would be nice to know if @Fidelity screwed it up with just me or all their customers.
3
105
Just tried #chatgpt #astra. Even on light reasoning, I burned through my usage in a few minutes. How is anyone getting anything done with this model?
1
1
252
Today we remember Tim Curry, best known for his performance in Earth 2.
135
I've run into a weird quirk with buzz.xyz caused by agents not really knowing their own identity. I sent a message that looked like "@agenta do this coding task and tag @agentb when you're done to code review". Both agents thought message was for them!
1
2
139
agenta understands that it is the one who is supposed to be doing the coding, and is getting annoyed when it finds the other branch written by agentb, and gripes about having to spend time consolidating the branches so as not to waste the work done by agentb. I can sympathize.
1
18
It gets funnier. To try to avoid this happening again, next time I just communicated with agenta. agenta remembering the prior instruction responded, "I'll code that and then tag agentb". The mere mention of agentb made b think it was the one who was supposed to code the task.
18
Replying to @Bitkey
@Bitkey is a great choice for those who are non-technical or intimidated by self-custody. But serious bitcoiners should be using tor and/or private electrum server. Bitkey can't use tor and private server is only possible after leaking linked addresses and ip to public server.
1
190
@Trezor is my top recommendation for those with a modicum of technical know-how, as it supports tor, private servers, split seeds, any number of passphrases, SD card encryption of seed, and a bunch of other security features, with a strong track record.
1
1
96
If you want to access privacy cryptocurrencies like @monero, that would be another reason to choose a wallet like @trezor with broader cryptocurrency support.
1
41
Whatever you choose, never store your hardware wallet or seed at your house. Consider secure locations like safes at geographically distributed banks (safes are one of the few things banks are still good for!)
25
Mark Engelberg retweeted
The single biggest point of failure in self custody isn't the hardware, it's the seed phrase on paper or metal. Bitkey skips it with multisig built in. Two of three keys, split across your phone, the device, and Block, no seed to generate, write down, or lose. No seed, nothing to compromise. Use code SIMPLY for 10% off.
18
10
1
131
16,228
Anyone on Coldcard needs to switch. My recommendations: the hardware wallet whose security I trust the most is @Trezor. But for many people, safely storing a seed/passphrase is the weak link. For those people I recommend @Bitkey as it is robust against that kind of user error.
1
2
191
To Bitcoin community leaders worldwide: Please message your Telegram, Signal, Discord, Nostr groups: anyone who created a recovery phrase on a Coldcard should migrate: fresh seed, generated on a new device. If your community needs hardware wallets, get in touch. We're expediting onboarding and shipments for local communities: help.blockstream.com/local#r…
2
21
125
6,726
Canceled @claudeai today. Had an issue with the desktop app and got stonewalled by the cust support bot, which was completely ignorant about the app yet refused to relay my message to humans. The weakness of the bot and lack of connection to people signifies claude's problems.
1
3
168
Lyn is a master of cool and collected logical analysis. I love every single one of her responses to the vitriolic frenzied bip110ers.
I’ve read the bip. I’m sure you are aware of the motte-and-bailey fallacy, but for those who are not I’ll explain it here. It’s a debating style where you assert an aggressive position, and then fall back to a somewhat more defensible position when the aggressive one isn’t working, and purposely conflate the two or switch back and forth when convenient. Many leaders of this movement, and by association their followers, have been saying that Bitcoin is under major attack by spam, that it is vulnerable to illegal images, that bitcoin will fail without this fork, that nodes will become unwieldy, or that this fork is absolutely going to happen. That in aggregate is the aggressive position, the bailey. And keep in mind this is path dependent; it emerged from the filter movement that spent years trying to stop spam. I know people who have received death threats for not supporting this fork. You should see my inbox or notifications of people talking about how this is the most existential thing in bitcoin, or that it’ll stop spam or csam and preserve bitcoin as money. That’s what many people assert. And when I say, “well no, it doesn’t do that, I don’t consider this an emergency, and even if it was an emergency I wouldn’t view this as anywhere near being a solution for the emergency, but I’m open to discussions on spam management for the longer run.” Then people respond by saying “look at the bip, it’s so mild, it admits how limited it is for spam, it’s not really about spam, etc” That’s the semi-defensible position to fall back to, the motte. But then great, it’s not an emergency. In fact, the reason I have not written about the bip on my main timeline or in an article (either for or against), is because I read it and it hasn’t reached my top ten things to focus on. By default I don’t support forks under a year old unless I consider them true emergencies, so that they have time for proper review. But for those who want to try for a contested fork, I support their right to do so. 👍
1
436
Mark Engelberg retweeted
They just closed my @Wise bank account because I'm into Bitcoin. And now, I am banned from ever opening an account with them. Great. This is why the banking system is rigged. I knew it was a huge red flag opening the account in the first place, they have over 10 countries they didn't let you interract with. SMH, this is why Bitcoin is important.
240
165
43
1,582
200,553
A question for the community: Where can I find an online course for learning/mastering ZK STARKs? Several years ago, I took @danboneh's cryptography coursera course, so am looking for something of similar quality. Want to fully understand the principles and get practice building.
1
1
286
Mark Engelberg retweeted
Spending on @Liquid_BTC is going near-instant. 0-conf brings safe-to-act-on transfers, now in public beta with a full release around the corner. And with the issuance cap removed, issuers can mint stablecoins and other Issued Assets at real-world scale. The full Liquid roadmap is in our Q2 update. blog.blockstream.com/blockst…
2
9
46
9,841
Chat. We're so back. The algorithm is finally showing us real Bitcoiners again… so we’re giving 5 Jade Plus devices to the timeline. Winners drawn Friday July 17 at 12 PM Eastern. To enter: 1. Follow @BlockstreamJade 2. RT this post
102
288
12
294
14,337