Joined May 2016
Kyle Jacobs | Root retweeted
Pixel art for DOS-AGE's title screen. Hand-sketched, hand-drawn by yours truly.
20
68
3
649
7,015
Kyle Jacobs | Root retweeted
me when people ask about the current state of AI:
130
669
85
5,108
353,512
Kyle Jacobs | Root retweeted
2
4
13
687
Kyle Jacobs | Root retweeted
the biggest risk managers and market makers asked us for historical tycho data for 10/10 analysis and now the data is public - you can see how sell depth within 1% falls from about $4M to about $0.7M for eth/usdc - at its lowest onchain spot price was $3,086, while Binance was $3,751 - gas spiked 350x as arbitrageurs tried to capture opportunities data clearly shows how speed and simulation throughput can give you an edge in such situations fynd is the only router that can handle these demands without breaking a sweat dm me if you're building a blazingly fast terminal and need one unified book of onchain liquidity or running liquidations
1
2
8
555
Kyle Jacobs | Root retweeted
Ok, spent Sunday trying something else fun. AVI (Videos) rendered entirely from the smart contract. Mint a block on @base ! block.graphics/ UI still getting some polish.
4
2
1
14
591
Kyle Jacobs | Root retweeted
GLM 5.3 Flash is now free in OpenCode
787
1,439
1,193
20,359
2,795,676
Kyle Jacobs | Root retweeted
New machine new me. This one is about 12,000$ and can run GLM-5.3-Flash and some 100 tok/s
112
69
17
1,688
95,086
opshnz cartel alphalpha
opshnz cartel alphalpha part 5: 1. Opshnz 💁🏻‍♀️ opshnz.com/ z whole opshz ecosystem catalogue 2. Lockstep 💁🏻‍♀️ delta-neutral strats /w fixed yield lockstep-gamma.vercel.app/ 3. Crypto Options Bot 💁🏻‍♀️ get quotes & analysis in grok bot x.ai/bot/16QaosA_qUfqSVDqA2Y…
7
174
Kyle Jacobs | Root retweeted
We were able to fine tune an open weight model (Qwen3.5-9B) on proprietary internal data at @coinbase, and it out performed frontier models, at much lower cost and speed, for a specialized task (fraud prevention in this case). I think we'll see more of this pattern inside companies. The frontier models are amazing generalists. But increasingly you'll see specialist models out perform on more narrow tasks, either working on teams, or by themselves. We're making it easy to fine tune models internally for our employees. We even have a skill for it in our internal harness that makes it easy to spin these up and start training them: "/fine-tune-and-serve-llm I want to fine-tune Qwen for payments risk review. help me get started" I imagine we'll have some backend services that could be replaced entirely by this new architecture.
618
794
543
9,513
1,599,790
I assume resilience, and adaptation, following any trauma. If it can be broken, it can be improved by same tech.
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
2
1
18
789
3Jane doing onchain credit scores. If you'd like to know yours, you can go to their site.
Introducing credit scores on @3janexyz x @cred_protocol Reputation can now be collateralized to generate higher yield within DeFi, permissionlessly and at scale, starting with undercollateralized promises on LCC
1
3
189
Kyle Jacobs | Root retweeted
AI is good at stuff. Attracts capital. Bonds sell off. Unemployment rises. Tax receipts down. Governments can’t pay debts. Bonds sell off more. Massive money printing to pay off debt. New world order.
BREAKING: 🇺🇸 US 30-year bond yield just hit 5.7% for the first time since 2002. Back then, inflation was only 1.2%, the Fed funds rate was 1.75%, and the stock market was already in a crash, about 40% below its peak. Today inflation is almost 3 times higher at 3.4%, and stock market is at all time high.
8
1
1
43
12,274
Kyle Jacobs | Root retweeted
🥪❌ MEV bots can't sandwich you if it's impossible to backrun you. Every sandwich attack relies on three things: ⒈ Frontrunning your trade, buying before you. ⒉ Pushing the price up with its own trade right before yours executes, so you buy at a worse price. ⒊ The bot selling its tokens back to the pool at that inflated price. On a standard AMM: The liquidity pool is symmetrical and bidirectional, meaning the same curve that sells tokens to the front-runner buys them back a moment later, after your trade has pushed the price up. The bot buys low - pushing the price up, forcing you to buy high - then sells high, keeping the difference. This is impossible to perform on @CarbonDeFixyz. 👉 Asymmetric liquidity: each strategy has a separate buy curve and sell curve, set by the maker at distinct price ranges. 👉 Unidirectional curves: each curve trades in one direction only. A sell curve sells. It doesn't automatically reverse and buy back. 👉 No profitable sell-back: tokens a bot buys from a maker's sell curve can't be dumped back into that curve at the inflated price. The only buyer is the maker's buy curve, at the lower price the maker chose. A bot can still try the front-run, but the back-run doesn't pay. And a sandwich without its second leg is just an expensive trade. #MEV #sorrynotsorrybots
3
5
14
2,409
Kyle Jacobs | Root retweeted
/deeper-roots
5
39
582
6,477
Kyle Jacobs | Root retweeted
Web crawlers /[•]\ #js x #css
1,065
8,591
942
69,524
3,265,937
Kyle Jacobs | Root retweeted
today we're releasing apex-flash-1, our first open-weights model for security research post-trained on real vulnerabilities we found and got paid for. we are also releasing the abliterated variant for researchers who want fewer refusals in their own authorized workflows. how we built it: cantina.security/apex-flash
91
170
59
1,513
294,598