John Saigle (@johnsaigle) profile picture

working on blockchain security @ asymmetric research "Perilous to us all are the devices of an art deeper than we possess ourselves."

Joined June 2017
Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)Photo by John Saigle (@johnsaigle)
"The most load-bearing question, then, is the morality of the one who wields the ring."
This is not the correct takeaway from Lord of the Rings
20
209
4
2,645
53,858
John Saigle retweeted
show this video to anybody that is an old school programmer that hates AI this is one of the best videos I’ve seen all month.
1,141
6,562
1,356
47,573
4,387,933
I unfortunately can't take seriously the big AI devrels on Twitter. Popular software factory repos just don't compute for me as cred for "How to use AI". The people I trust the most are people focused on correctness whose bottom is on the line. Kernel/Inference folks, TigerBeetle, our own Tempo team etc. Basically systems folks. I believe that 90% of application layer advice out there is garbage and actively distracting you.
43
48
6
665
32,481
John Saigle retweeted
GrapheneOS code quality has greatly increased due to using frontier models for code review and bug finding. Our port of the Pixel 10 drivers from Linux 6.6 (QPR1) / 6.12 (QPR2) to Linux 6.18 went incredibly smoothly because we were able to find most of the issues in advance.
6
41
5
1,269
34,052
There’s no excuse for new software not to be logical, not to be deterministic. Investing in owning your testing, to be DST-first, and to accelerate the local development velocity of your team, is probably the best technical decision you can make.
We are actively rewriting software w/ TigerStyle & DST at Tempo. This is the role I am the most excited to hire right now. Please reach out. Need someone extremely AI pilled who also gets that "correct software" is the prerequisite to hillclimbing for performance.
9
18
4
360
12,914
It’s refreshing to have access to, and be able to work with, a team of incredibly passionate and skilled (not to mention human) engineers, who want to break the code, and find bugs as much as you do. To be clear, machines (like the VOPR and LLMs) are great at exhaustively enumerating bugs, but these things are defense-in-depth: The principle is that you should always be adding layers, but never replace one layer with another. For example, don’t replace human review with LLM review, but rather add another layer as defense-in-depth. (The LLM should only be a canary, if it finds anything, you know your other layers failed, and you fix them and invest in them). At the end of the day, the most valuable software in the world is not valuable because of the “time” it took you to create, but because of the “quality” and value you added.
Apparently you're not allowed to do Deterministic Simulation Testing with GPT 6 Astra
9
10
1
119
4,201
John Saigle retweeted
Crypto grew up in the Dark Forest, and the entire world is about to find itself there
111
334
44
2,843
139,306
John Saigle retweeted
Crypto’s irony is that it usually is attacked first and mocked for its operational failures Yet the competition ends up looted more aggressively later by the same actors (🇰🇵) and reluctantly adopts the security solutions that wouldn’t exist without crypto being attacked first
SCOOP: Major U.S. banks are detecting unauthorized third-party AI agents inside customer accounts, including some attempting to take actions that appear to be independent of user instructions, sources told Axios. The findings have alarmed banking executives, who are racing to restrict access to their systems as AI moves at a velocity faster than financial institutions can respond, multiple industry and bank executives told Axios. Several banks are now preparing for worst-case and even “day after” scenarios, including how to rapidly secure or restore customer accounts if things go wrong, the people said. Several bank executives told Axios they're struggling to distinguish between human users and AI agents. One executive said banks also struggle to determine whether agents are authorized by customers or potentially operating without their permission, more akin to rogue agent behavior. Read my latest for Axios here: axios.com/2026/10/22/ai-agen…
21
36
4
243
25,545
John Saigle retweeted
There are literally zero moats left unless you go to the portfolio tab on our website those are the only companies with moats
29
42
5
1,152
54,911
So many people discovering that the whole Internet is dry tinder and the only thing keeping it from burning is the fact that teenagers haven’t found the matches yet.
10
38
5
253
11,810
John Saigle retweeted
iOS 16 on redmi note 12
10
642
11
8,056
96,235
John Saigle retweeted
Replying to @thorstenball
I don’t think we want probabilistic guarantees of memory safety which require inference to imperfectly check. We likely want a deterministic, fast, sound algorithm you can run locally —which is what the rust compiler mostly gives us today.
1
1
9
419
John Saigle retweeted
Public service announcement: there is a lot more to security than finding software vulnerabilities. 🫡
29
35
10
305
16,622
John Saigle retweeted
opening a repo and seeing a .DS_Store file is infinite aura loss
37
112
9
5,990
419,072
John Saigle retweeted
"Today, most tools use put Developer Experience first —remember all the 'easy-to-use' javascript frameworks, then Performance, then Safety; TigerStyle does the opposite order" youtu.be/qIhAc9Qw_1c?si=2330…
3
15
1
59
3,383
John Saigle retweeted
This Immunefi Allstar just found a max critical that earned him a $50,000 bounty. Congrats @0jovi0! One critical can change everything. Find yours: immunefi.com/bug-bounty/
13
11
4
211
19,001
John Saigle retweeted
Mandatory reading. gruhn.me/blog/2026-08-03/
37
146
39
907
87,194
Replying to @ori_pomerantz
I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.
567
1,975
900
18,854
5,142,297