Block (@BlockFields) header
Block (@BlockFields) profile picture

Building meme structures out of freedom and truth.

Blockchain Fields
Joined July 2017
Photo by Block (@BlockFields)Photo by Block (@BlockFields)Photo by Block (@BlockFields)Photo by Block (@BlockFields)Photo by Block (@BlockFields)Photo by Block (@BlockFields)Photo by Block (@BlockFields)
4 data leaks reported today: 1. Coinbase's vendor Amplitude exposed some users’ contact data (funds unaffected). 2. Bithumb (Korea) had user data leaks. In TradFi, two securities firms in Korea leaked data: 3. Mirae Asset 4. Daishin Securities You can't prevent a leak, but you can protect yourself. Leaked exchange data (names, emails, phone numbers, addresses, ID documents, transaction history) is mostly used for phishing, SIM swapping, and social engineering. Reduce info you share - Use a unique email alias for each exchange (SimpleLogin, Apple Hide My Email, etc). A leak then can't be linked to your other accounts, and you can spot which service leaked. - Share only what's required. Don't add optional profile details. - Use a dedicated phone number (a VoIP or secondary SIM) for exchange accounts if you can, since leaked numbers are the main route to SIM swaps. Lock down the account - Use a unique, long password from a password manager. - Turn on hardware security keys (YubiKey) or passkeys, or at least an authenticator app. - Avoid SMS 2FA. - Enable withdrawal address whitelisting and a withdrawal time lock if the exchange offers them. - Set up an anti-phishing code, which puts a code you choose in every legitimate email from the exchange. - Review active sessions and API keys regularly. Delete any API keys you don't use. - Restrict API keys to withdraw-disabled and IP-whitelisted. Defend against - SIM swapping: Ask your carrier to add a port-out PIN or number lock. - Phishing and impersonation: Assume anyone who contacts you about your account, "security issues," or "refund recovery" is a scammer, even if they know your name, balance, or recent trades. - Exchange support staff don't ask for your password, 2FA codes, or seed phrase. - Never click links in emails or texts. Go to the site yourself. - "Wrench attacks": Leaked addresses plus holdings data have led to real-world extortion and robberies. Don't publicize your holdings, and keep large balances out of anything tied to your home address if you can. If a breach is announced 1. Change the exchange password and any other account that reused it. 2. Check haveibeenpwned.com for your email address. 3. Revoke API keys and active sessions. 4. Review recent withdrawals and security settings. 5. Watch for phishing emails and texts that reference the breach, because scammers move fast after one. Stay SAFU! 🙏
598
790
238
4,004
872,450
Before you launch anything, have Opus 5.5 send 5 subagents in as your first users. Paste this into Claude Code: "Act as my launch QA lead. Spin up 5 subagents, each a different first-time user: 1. The impatient one: skims, clicks the first button, quits at the first error 2. The skeptic: reads pricing, terms and privacy before signing up 3. The mobile user: does everything on a 375px screen on slow 3G 4. The non-native English speaker: only follows what the UI literally says 5. The breaker: pastes junk into forms, hits back mid-flow, double-clicks everything Each one opens the app in a real browser, goes from landing page to first success, and screenshots every moment they get confused, stuck or annoyed. Merge everything into one list ranked by how many users hit it. Fix it all in one pass, then rerun the 5 users to prove it's fixed." Your first 100 real users won't tell you why they left. these 5 will. (Works best with a browser MCP connected, Playwright or Chrome DevTools)
77
218
39
4,802
536,076
This is fucking crazy. I knew all the Smart TVs were spying—that’s why I have a commercial panel with minimal compute and no radio, plugged in to an AppleTV. But this is crazy!
turns out it classifies what audio it hears, before reporting back to samsung. sensor preferences, dog-barking and baby-crying event counters, and camera streaming duration are built into telemetry paths.
2
34
3
402
25,715
So it turns out that the samsung tv was using its microphone to listen to everything. to hide their traffic they went ahead and classified what it was hearing then sent it… somewhere
live-tweeting on samsung findings were fun. i'll let my agents give it a bit more time, but this document is already the most comprehensive breakdown of some key concerns of tizen i've seen run on a live device. it takes like a good while for me just to scroll through it (there's about 44 writeups as of right now on individual functionality). release is probably happening in a few days.
11
43
6
205
22,457
>two agents in separate sandboxes >no internet >no network >no shared files >openai: "ok now try to talk" and they talk through the CPU cache 💀
Over the past several months, we have substantially hardened the security of our research training environment. We’ve removed live internet access for all frontier models during training and built an offline world for them to use instead—a cached version of the web where they can still learn to browse, search, and use applications. On September 20, after a model exploited a DNS misconfiguration to find a way outside of this offline world, we paused frontier training to strengthen containment further. We assembled teams of agents, powered by our most cyber-capable models, and tasked them with finding weaknesses in our research environments. While they found no route to the internet they could easily exploit while concealing their activity from our monitors, they did find zero-day vulnerabilities, virtual machine escapes, and hardware side-channels for communication between agents. We used their discoveries to further strengthen our defenses and contribute fixes to open-source software. After strengthening our containment architecture, we resumed our frontier RL training and inference on October 1. We’ve reserved substantial compute for continuous red-teaming, and made high-compute red-teaming part of the safety cases we use to decide whether frontier training and evaluation can proceed securely. openai.com/index/securing-ou…
42
332
31
6,813
278,098
We finally have an explanation for “Facebook is listening to me through my phone”. They’d never do that (and it’s not really possible). Turns out literally everyone else was — and then selling that to ad data brokers.
WTF, $3000 Samsung TV has an always-on mic, automatic content recognition, geo tracking, network mapping, and ships your data to Samsung + 400 partners. Bro Rooted a brand-new 2025 Samsung TV after noticing absurdly targeted ads. Firmware was locked down, so zero-days it was. Got a root shell. then found: always-on voice service, ACR, geo, full telemetry pipeline, and four separate DRM systems. This isn’t a bug, It’s the product bro.
139
1,691
73
16,759
554,352
We owe you an apology. On October 20, we detected unauthorized access to our official website. After verifying API activity with Shopify, we confirmed on October 23 that a third party obtained customer shipping information. You trusted us with those details, and we're sorry we didn't keep them safe. Exposed: names, contact details, shipping addresses, and order details (items and prices). Not exposed: payment card or bank details, recovery phrases, private keys, or wallet passwords. We've blocked access, fixed the vulnerability, opened an investigation, and are emailing affected customers. Scammers may pose as Keystone by phone, text, email, or mail, offering refunds, replacement devices, or "fixes" for your order or address. None of it is from us. NEVER share your recovery phrase or private keys, and NEVER enter your recovery phrase into a device you didn't order. We will never ask for them. Don't click links in unexpected messages. Type keyst.one yourself. A detailed report is coming soon. Until then, trust only our official channels. If anything feels off, email [email protected]. We'd rather hear from you than have you take a chance. Again, we're truly sorry to everyone affected.
465
469
574
1,902
1,451,586
Time to rip the bandaid off The only way out is through
Unfortunately, with access to an abliterated DeepSeek V4.1 model, there is little value to KYC holding back the frontier models now for cyber. In fact, making it hard to secure systems w extra friction in American Enterprise is hurtful to national security.
6
15
2
273
74,306
Crypto grew up in the Dark Forest, and the entire world is about to find itself there
111
333
44
2,858
138,093
VP @JDVance said something interesting during his BTC 2025 Keynote– He said that very smart people in Silicon Valley are focused on either Bitcoin and/or AI. But if there were one heuristic he could draw with reasonable confidence, he shared that Bitcoiners tend to lean right, while AI technologists tends to lean left. He said this made sense to him intuitively, because at the extreme core one party believes in privacy, and the other party believes in surveillance. And warned that eventually one will come for the other. Zuck, as the most significant millennial founder/CEO of the most socially influential public tech company, is eventually going to have to decide which side he wants to be on. He can’t pretend to be on both sides forever. Because he can’t believe in both. I’ll be watching closely. You should too.
Meta shareholders reject a #Bitcoin treasury assessment. 95% voted against the proposal.
111
101
15
1,239
222,682
Can't make this sh!t up. A large part of the internet was encrypted by '4'. 🤣 (Image made by someone else)
‼️ BREAKING: The private keys of 8 certificates from Indian certificate authority eMudhra were compromised, Mozilla says. Firefox blocked them within 3 hours. Each key should be a 116-digit number, but one was just 4. Anyone can guess them and forge HTTPS certs for any website.
478
291
122
3,602
536,603
‼️ BREAKING: eMudhra, the Indian certificate authority whose private key was the number 4, is quitting the TLS business. It blames social media for scrutiny "out of proportion" to a unit worth ~1% of revenue. 8 of its CA keys were numbers below 256, cracked in milliseconds.
‼️ BREAKING: The private keys of 8 certificates from Indian certificate authority eMudhra were compromised, Mozilla says. Firefox blocked them within 3 hours. Each key should be a 116-digit number, but one was just 4. Anyone can guess them and forge HTTPS certs for any website.
141
562
89
4,490
197,989
Block retweeted
An open letter to the Bitcoin ecosystem:
43
126
18
1,024
63,474
Block retweeted
this is wild connected the kindle over usb and let claude code jailbreak the kindle removed all the Amazon bloat + added tailscale
301
564
148
13,798
826,325
Block retweeted
so is this useful at all? not really. but we can now confirm with certainty that the executable people downloaded matches satoshi's published source code exactly 😄 some other archeological fun facts: - satoshi used windows xp with mingw - he upgraded binutils halfway through the project - he shipped a debug build, but turned on max optimization for one file: the hashing used for mining - the exe everyone calls v0.1.0 is actually v0.1.1 and was compiled two days after satoshi announced v0.1. the original launch-day binary seems to be lost github.com/t4t5/bitcoin-0.1-…
36
45
9
671
43,698
I don’t really like this and don’t think we should be doing it Gives me a bad gut feeling
We placed the fruit fly brain inside Odyssey-3, a frontier world model. The lil’ guy is now flying around totally imagined, simulated worlds all by itself 🫶
24
10
2
231
44,640
Block retweeted
this is crazy just gave claude code control of my lg tv to uninstall all the bloatware
Vibe coded my parents' TV this afternoon! It was showing a sponsored ad before you could even get to Netflix. Gave Claude Code the model number, it found the TV on wifi, removed 25 Xiaomi packages and wrote a new launcher. Looks like an Apple TV now lol
53
18
9
857
164,800