Alex Hook (@alexhooketh) profile picture

Built, audited, and led several blockchain protocols to production. Looking for what's next via @untronfi @daimo_com @getclave

Joined July 2020
Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)Photo by Alex Hook (@alexhooketh)
Looking for a job. DeFi protocols built by me are processing thousands of dollars every day. Audit firms have struggled hard and tend to find nothing in my code. Things I build just work. You know a few blogs that referenced my research, too. Portfolio below. DMs open.
14
15
3
195
21,008
OpenAI bars some formal verification work behind KYC-ed Daybreak Blue closed proprietary LLMs are literally Hitler
1
133
The next programming language for AI agents is English
github.com/medovina/natural_… wow! natural language lean, see its worthwhile to check out recent lean projects.
1
131
— People are creating and switching to AI-friendly forks of our product en masse, as it takes us over a year to get one more chip supported, and half the hardware is still not working properly — So we're going to finally adopt AI and fill the support matrix, right? Right?... —:
Asahi Linux is moving everything from the MIT licence to GPLv2-or-later. Asahi is the volunteer project that reverse-engineers Apple Silicon Macs so they can run Linux. In today's Linux 7.3 progress report, developer James Calligeros explains why: people have been using the permissive licence to take the team's work. "In some extreme cases, in-development feature code was being lifted straight out of our personal forks and published without attribution or lazily rewritten with LLM assistance to obfuscate its origin." The report points to WINE, which switched from MIT to LGPL in 2002 for the same reason: "Those who do not learn from history are doomed to repeat it." The same report brings real wins too. M3 Macs now install without the EXPERT flag, Thunderbolt support (USB3 and networking for now) is shipping to users, and the team got GTA IV and Fallout: New Vegas running outside the muvm VM using Google's per-process page size patches.
108
Alex Hook retweeted
3 predictions: 1) In < 2 years most code will be written in Lean4 or equivalent 2) The final binary will be faster than Rust or C 3) Compiler architecture will change, with builtin intelligence and drastically more aggressive optimizations
30
14
6
378
20,539
Alex Hook retweeted
x86 formal verification is coming! The (first?) published machine-checked proof of a security property for the end-to-end execution of a Linux process running an x86 binary statically linked against glibc. And we believe it scales! A joint research project with @zellic_io 🧵👇
43
171
39
1,337
142,466
Superlogical Rex is exceptional. AI-assisted software built by people with actual taste is the future Can't wait to try out the iPadOS version when it's live. It has all chances to replace my MacBook for SWE work
4
11
250
Dune's trial email: "continues on Free after. nothing is charged." Dune on day 15: tries to charge me $4k (four thousand dollars), twice thank god for an empty card
1
9
392
Dune right after: threatens to block my account if the payment doesn't go through
1
4
93
@grok does this constitute fraud
1
2
75
Alex Hook retweeted
Formal verification is inevitable
5
2
15
861
Small announcement: ✅ formal-git As an experiment, over the last 2 months we've modelled ~30% of Git in Lean 4, making heavy use of coding agents, and proved >8000 theorems of varying usefulness about the implementation. In the process of doing this we've uncovered >100 potential defects in Git v2.55, at least two of which may constitute security vulnerabilities. We've also built a DRT (differential random testing) harness and the biggest corpus of relevant pinned differential test cases for Git implementations with >10k unique tests at the moment. We've used the test cases to test our own small internal implementation of Git in TypeScript. The next step will be to differentially test all notable public Git implementations against this corpus of tests to help improve their correctness and security 🫡 We'll be reaching out to library maintainers in due course. If you have a Git implementation you'd like us to help you test, please reach out and let me know. We'll open-source all this eventually, after potential security issues that were uncovered are responsibly disclosed and fixed.
39
66
10
551
25,523
M4 Pro progress: 🔊 all 6 speakers with Apple's tuning + headphone jack + mics 🔌 USB3 5 Gbps on all 3 USB-C ports 📷 webcam 🎞️ AV1 hardware decode, 4K60 in Firefox 💤 lid suspend 🐧 Linux 7.3 All PRs up at github.com/aurora-silicon/li…, should be in Omarchy soon
Got Linux GPU acceleration working on an Apple M4 Pro Shoutout to @AuroraSilicon and @tiredkebab for some of their work.
24
34
7
574
25,901
If we assume Grok Bot is a form of Cursor (which is fair in a lot of ways!), then they actually managed to win back a lot of their old users who switched to Codex / Claude Code last year! Using Cursor from its early days to late last year I was frankly sure they'd just die out
1
2
164
I shared a phishing email I've received earlier with Grok @bot, and it autonomously nuked absolutely everything about the scheme with abuse reports. The domain is now dead too Not the best time to live in for scammers
5
137
.@cursor_ai could someone in Cursor's support team escalate my issue to a human, please? Cursor's AI support bot is some of the dumbest I've had to chat with in my whole life My Cursor account seems to have been barred from making payments, and all my cards are being declined :|
1
2
148
4:20
Replying to @alexhooketh
at 200-300 tok/s it could probably be my main daily driver, but you're not getting this performance with local hardware — yet? we're this close to feasible local AI
4
157
Introducing Safe Rollup. Ethereum-anchored, operator-controlled. Safe as in Safe multisig, not safe funds. Safe Rollup gives institutions the credibility of Ethereum and the control of a database. Live on Sepolia today. saferollup.fyi
34
31
32
283
49,003
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable. Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread. Instead, the correct solution is... EIP-8288 maximalism. If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation. This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.
Replying to @lex_node
> we could still ultimately do Lattice stuff for accounts, wallets, etc. through a precompile if it is proved to be AI-secure The ideal route to support everyone's cryptography is imo through 8288. You make whatever signature you want locally, then STARK it, and then it gets included through the stark aggregator machine. Don't need any calldata onchain. Ethereum can then never add a new precompile again.
457
284
104
2,018
419,897
I remember how P-256's unknown seed was quite a popular argument against EIP-7951 among critics. Thankfully it was a nothingburger!
3
194