That One Guy in Crypto (@treycrypto) header
That One Guy in Crypto (@treycrypto) profile picture

♕Just a DeFi Farmer enjoying Life ♘Travel, Crypto, & AI #bitcoin #eth #sol 👾maxi of all things crypto. follow the data & find the truth.

Your Moms House
Joined March 2014
Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)Photo by That One Guy in Crypto (@treycrypto)
That One Guy in Crypto retweeted
Congrats on your failure. Most people dont even try.
281
1,693
126
14,422
305,485
That One Guy in Crypto retweeted
Mechazilla catches Starship! Congratulations to the entire SpaceX team on this incredible achievement!
6,795
27,369
9,113
141,283
17,610,733
That One Guy in Crypto retweeted
"I avoid bad luck by being patient" - Jay Gould
38
104
11
1,401
55,738
That One Guy in Crypto retweeted
POD UP: The Besties React to the Midterm Massacre -- Full Postmortem on the 2026 Midterms -- Looking Ahead: How to Save Trump 2.0? -- Market Reaction: $4T Wipeout, Data Center Fears, AI Ban Potential -- Science Corner: Exponential Time Hypothesis Solved (0:00) Bestie intros! (3:37) Midterms postmortem: What led to a generational GOP collapse? (32:26) How can Trump salvage his presidency? (53:13) Market reaction: Data center fears, $4T in market cap wiped, AI ban potential (1:24:21) Science Corner: OpenAI solves the Exponential Time Hypothesis
200
82
60
1,037
1,346,885
That One Guy in Crypto retweeted
Some walk with you for a while… Others stay in your sky forever…
725
8,574
990
56,934
16,263,558
That One Guy in Crypto retweeted
Real life, baby
19,172
96,099
45,749
772,982
99,533,959
That One Guy in Crypto retweeted
Choosing where to build is a big decision. You're putting your time and your reputation behind it. To everyone who chose Robinhood Chain in these first 100 days: thank you. I'm glad we get to build this together.
1,036
441
266
5,206
472,613
That One Guy in Crypto retweeted
California Governor Poll (Hilton internal) 🟦 Xavier Becerra: 45.7% 🟥 Steve Hilton: 40.1% ⬜️ Not sure: 14.1% Undecideds forced to choose leaned 72.5% Becerra, 27.5% Hilton. —— David Wolfson | 10/1-2 | 1,020 LV nypost.com/2026/10/04/us-new…
59
52
19
362
92,173
That One Guy in Crypto retweeted
Just wanna thank god in advance for the generational run we about to go on.
33
72
17
401
23,298
That One Guy in Crypto retweeted
When you look back, you’ll wish you’d just done the long-term version of everything.
846
7,189
633
55,011
2,995,877
That One Guy in Crypto retweeted
This onchain engine runs on memes & RWAs & vibes.
574
292
180
2,596
327,549
That One Guy in Crypto retweeted
Going to be more humble this time around because God has a funny way of taking things away when you get cocky.
115
302
29
3,883
131,790
That One Guy in Crypto retweeted
Our latest research paper explores the growing connection between AI and digital assets and explains why broad AI adoption may drive new demand, utility and applications across the digital asset economy. blackrock.com/us/individual/…
758
1,980
1,259
8,340
4,169,821
That One Guy in Crypto retweeted
AI doomers say if we build AI we might die. But they have it backwards: 165,000+ people already die every day. Cancer, heart disease, illnesses, car crashes. AI is helping us solve these. Slowing progress doesn't keep us safer, it guarantees more preventable deaths.
406
385
65
3,547
174,868
That One Guy in Crypto retweeted
timeline. ticker. trade.
1,785
2,151
1,608
14,718
6,101,098
That One Guy in Crypto retweeted
robinhood chain summer is multiseasonal
354
144
59
1,803
190,936
That One Guy in Crypto retweeted
manifesting an onchain autumn for all of us 🍂
426
197
88
2,176
205,219
That One Guy in Crypto retweeted
Today more than anything LONG 🇺🇸 Every public company will have a leading stock based community on LONG. Stock by stock.
Tokenization is coming to America. Thanks to the SEC’s leadership, Americans can start to reap the benefits of tokenization: instant settlement, 24/7 trading, fractionalization by default and more. It’s a good day for US innovation.
82
70
30
671
99,661
That One Guy in Crypto retweeted
AI will prove your code is correct
It's an increasingly common take that AI hacking means cybersecurity is doomed. I disagree. I think cybersecurity is naturally defense-favoring once people get their shit together. And anyone who continues to hold cryptocurrency (including me, ~90% of my net worth) is implicitly making that bet. Here's why I am making that bet. First, the oversimplified punchy one-line statement: If AI can prove Navier-Stokes and FLT, then AI can prove the statement "this program is secure" as a mathematical theorem. Even if the program is very complicated. Now, the nuance: (See also: vitalik.eth.limo/general/202… ) The word "secure" is hiding all kinds of skeletons in the closet in terms of what it actually means. What does it mean for Signal (the encrypted messenger) to be "secure"? The most basic definition you might think of is: no one who doesn't hold the recipient's secret key can read the contents of the message. But: * Did you remember to include _other_ critical forms of security? Can the adversary forge messages? Can the attacker prevent messages from reaching the recipient? Can they cause your client to crash by sending malformed messages? * Have you made sure that your model of the adversary includes attackers that interfere with the protocol actively and not just passively? And attackers that interfere by replaying messages to you or the recipient that either of you sent over the wire at any point earlier? * What if the adversary hacked (or _is_) the Signal server? * How did you learn which public key belongs to the recipient in the first place? What if that process was tampered with? * What if your device gets hacked at some point in the past or future - is your message still safe then? * What if your key leaks because of a bug in your operating system? Or because you got a bugged version of the Signal client? Or what if the database is corrupted? * Or the libraries, interpreter or compiler of the programming language you wrote it in? * What if your key leaks because tiny perturbations in perceptible signals generated by the hardware leak mathematical relationships that can extract the key a few hundredths of a bit at a time? * Are you hiding the *size* of the payload? Does that matter? * You're definitely not hiding the identity of the sender and the recipient, and the exact time each message was sent (think: not just time-of-day, but also time deltas between one message and the next). Is that not enough to deduce a lot of important facts about what relationships you have, and what *kinds* of conversations you are having? So ... even definitions can be over a thousand lines of code, and need deep careful thought to figure them out. Working on making definitions more human-readable is of extreme importance - it's perhaps the only "high-level language" that matters right now. But even still, even despite all of the above, for security-critical components, the definition is a much smaller attack surface than the implementation. Verifying that the definition is adequate is a much more tractable task than scanning over the code directly - and can become even more tractable with better tooling. Definitions are also _additive_: if two groups have two different definitions A and B, then, well, you can just prove that the program satisfies both A and B. Code is not additive in this way: if a program is A + B, a bug in A _or_ B can sink the whole thing. Definitions are additive. And if you can't satisfy A and B at the same time, you've isolated the most important philosophical issue for your project to spend its next few weeks grappling with. Sometimes, definitions are not much smaller than the implementation - UI components might be one example. But for many of the most critical components - message-passing protocols, sandboxes, cryptography like SNARKs and FHE - the asymmetry is real. Historically, a large class of failures with this approach have come from people only verifying a small portion of their code, that they self-declared to be the security-critical portion, and ignoring the rest - and it turns out that something in the rest of the code is security-critical too. This was reasonable back when verification was difficult and scarce. The solution today: sorry, you have to verify over literally your entire program, including database, networking, any caching layers, everything. Modern AI can do it. So it's not about "the good guys find all the vulnerabilities before the bad guys do" - that could maybe work too, after all a finite program only has a finite number of vulns, but it's riskier - it's specifically an asymmetric strategy of making code that is much more resilient in the first place. This is the kind of direction that Ethereum is going in for the next few years. There is no future for blockchains - especially blockchains with scalability and privacy - without doing this. We need to make software actually secure. And we have already made a lot of progress.
409
147
88
2,492
445,595
That One Guy in Crypto retweeted
The future is more likely AIs fighting AIs (on behalf of humans) than AI fighting humanity.
906
987
311
12,692
587,725