hubert (@notrickfox) header
hubert (@notrickfox) profile picture

2021 New York Times bestselling author

southern part of heaven
Joined March 2022
Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)Photo by hubert (@notrickfox)
My own recent prepping upgrades: Got 2 hard drives and downloaded the top 10 abliterated and open models. Getting a starlink mini for communications. The basics are food, water, medicine, electricity, weapons, money, and transportation. For myself that’s a few weeks of food, water, and electricity to run a laptop and phone. 6 months of medicine. A little cash and gold. A few handguns and ammo. And an off-road vehicle. That isn’t to restart civilization or survive a nuclear winter, it’s to be comfortable for a couple weeks while I assess and relocate in a crisis. My mental model for prepping is that no matter how bad the crisis, there will be safe and calm parts of the world. Get to those. If the entire world is apocalyptic? Well, it’s been a good run. Not hedging that.
1
79
I think it will be obvious in retrospect that OpenAI hasn't released any models because they have been and are currently assisting with a national security situation. Below, I gather the fact pattern and make some guesses. (a 🧵):
53
who cares about treason? hire him back!
Over the past week, I’ve been overwhelmed by the love and support of friends, industry colleagues, and people I've never met. Thank you to everyone who has shown kindness to my family and me. It means the world to me. I came to the United States 53 years ago, and becoming an American citizen is one of the greatest gifts and proudest moments of my life. NVIDIA has been my life’s work. Building it into the company it is today alongside my colleagues has been a privilege and an honor. Nowhere but in America could a company like NVIDIA be possible. I love our country, and I love NVIDIA. I did not live up to the standards expected of everyone at NVIDIA, and I have made serious mistakes in my personal life. I created problems for the Board that I deeply regret. I own my mistakes completely, and I am committed to cooperating with the Board’s independent investigation. Since my departure, I’ve seen an outpouring of calls from NVIDIA’s employees, investors, business partners, and customers for me to return as CEO. Many continue to reach out to me directly as the company navigates complex technology, market, competitive, and geopolitical dynamics. NVIDIA is a once-in-a-generation company. If the Board of Directors decides that my return is in the best interest of our shareholders, our employees, the company, and America, I would be honored to answer these calls and return as CEO. Thank you again to everyone who has shared their good wishes. I am profoundly humbled by your support. To my family: I love you, and I will spend the rest of my life being worthy of yours. Jensen
43
ok Ari
The NSA's internal communications network is down, no comment or statement yet from the NSA.
1
79
Replying to @notthreadguy
Schwab down at market open for scheduled maintenance
3
1
63
3,099
Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail. At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum: * Signatures * STARKs * Merkle branches * FHE computation * ... Really the first two are the most important. Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this. 8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims": "pubkey P has signed message M" "program X run on data D has output Y" "p(X) = Y for some polynomial P whose hash is H" and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is: (i) hashes of inputs and outputs (~64-96 bytes per claim) (ii) a single STARK proof per tick These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type. Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part. The core distinction is: *what is the underlying object that the user is creating?* In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: ethresear.ch/t/sphincs-minus… If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else. In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for: * Any signature scheme (including eg. lattice-based ones if you like those) * A multisig that hides its internal logic * Privacy protocols * Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other Basically, it's a free for all, in the same way the EVM is a free for all. But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts. LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: vitalik.eth.limo/general/202… ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas. The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256) LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems. But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later. So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS. firefly.social/post/x/212092…
279
192
76
1,465
257,235
where i’m from we call that a proper roundtrip
1
66
hubert retweeted
tap the first pic then swipe quickly on the preview row at the bottom
25
28
7
336
14,459
Kind of major, started at approx 3:15pm Boston Center, New York Center, Chicago Center, New York Approach have all lost numerous frequencies. All facilities are in ATC Alert. Some sectors in New York Center are unable any traffic currently. Numerous— I mean NUMEROUS frequencies across the NAS have / are currently failing as we speak.
1
237
hubert retweeted
19
27
9
319
10,543
LOCK HIM UP
Replying to @DavidSacks
David, as AI czar, which parts of the story were you aware of? If Alice was sharing notes with Beijing (whether she was labeled a “spy”) how does that affect your thinking? Are you confident NVIDIA Blackwell GPUs weren’t used to train the Chinese models? I’m seeing decent tech forensics suggesting $5b+ worth likely were. So then the question is just was NVIDIA (and yourself as AI czar) aware and criming? Or unaware but guilty of gross negligence in oversight? Or innocent mistake? @DavidSacks
67
hubert retweeted
INSIGHT: Ethereum research group Ethlabs proposes pulling quantum resistance forward to 2027, a year ahead of the current target, by removing faster block times from the Hegotá upgrade and prioritizing post-quantum cryptography amid rising AI-driven security risks.
61
69
25
604
127,037
Replying to @ashleevance
he bought huggingface and shut down the scam instead of complying
1
14
2,213
hubert retweeted
I previously said that code I posted on GitHub at lalalune/pumpfun-source was open source.  It wasn’t.  The code doesn’t belong to me, and I never had the right to release it, license it, or give anyone permission to use it.  Also, the “Copyright (c) 2026 Shaw” license and similar licenses in the repo weren’t real and don’t give anyone any rights to the code.  Don’t rely on those licenses, or anything I said, as permission to use, copy, fork, modify, build on, distribute, or otherwise do anything with the code.  You should not distribute or try to reverse engineer the pumpfun code.  It is protected by copyright.
76
4
15
210
57,375
had to read this headline twice
75
The sad thing about the Jensen Huang thing is he lost the one thing he can never get again which is a partner you're confident loves you for who you are Once you have resources, you can never rebuy or find that kind of peace and love again
67
212
17
3,357
41,737
so jensen’s wiener is sending us to war
75
hubert retweeted
When researchers analyzed how Pegasus spyware infected iPhones without the user tapping anything, they found something wild. The attackers sent an iMessage with a fake GIF that targeted Apple's image decompression engine. The decompression math was so flexible that the exploit chained arithmetic operations together to construct a literal, functioning software CPU using over 70,000 segment commands that defined logical bit operations (AND, OR, XOR, XNOR, etc.) entirely inside the image parser. This created a small computer architecture with registers, a full 64-bit adder, and a comparator, running raw code before the phone even buzzed with a notification
118
931
176
10,730
772,051