I like blocks | @ethereum Protocol Fellow | Prev: @OlenaProtocol @SumeroApp

Decentralized
Joined May 2009
krisoshea.eth retweeted
Finally summarized what I've been sending to friends in DMs
235
569
262
6,107
793,296
It’s crazy how quickly the main deciding factor for me to use a given product/service has become can my agents easily read/write to and from that product/service and interoperate with other products/services that also allow access to my agents. There’s even categories of products/services that I’ve always wanted to use but they created too much friction to set up and use regularly that I never bothered. That is fully solved by agents now too. Take @AwakenTax and @getAkiflow for example. I’ve used @KoinlyOfficial for the past few years but now I’ll be immediately switching to solutions like Awaken that allow me to connect all my context and agents to the software directly. Then take Akiflow, it’s this brilliant productivity tool, but the main issue with it (and many productivity tools) is most of the time you end up saving gets spent on actually setting it up and maintaining it to fit your life, this is now fully solved by ambient always on agents that understand my life and my context. Very excited to see what this unlocks over the coming years. I don’t think enough people realise how much of an impact minimising these friction points will have on onboarding new users to existing products/services once agents become the unlock.
78
krisoshea.eth retweeted
Back in 2021 I interviewed at Vercel and I failed badly. I couldn’t implement a debounce function and was stuck for like 30 minutes. It was pretty embarrassing. 10 months later (2022) I interviewed again and got the job. Don’t give up!
108
207
74
6,271
729,407
krisoshea.eth retweeted
spent the last year building systems to run my life because I took on a lot of responsibilities all at once and started juggling too many balls. from 50+ angel investments and managing all of that, to my work at World, my personal life, health, travel, fitness, family, friendships, interests, hobbies, learning, and so much more. I've been very quiet compared to 2 years ago. I am finally getting back on my feet because I've been building a context management system that combined with ai agents is starting to take off a lot of weight off my shoulders. I am in SF for three weeks to lock in and work on world stuff and also shipping the oss version of my context management system. At world I've also mostly switched to building AI systems to scale the foundation and help the TFH (labs) team do the same. If you're building personal or company agentic systems and building/scaling processes hit me up. Really looking forward to launching all the tools I've been building over the last few months. I am working on making them robust and useable for people other than myself right now. the goal is to do for context / life management what openclaw/hermes did for personal agents, i feel like it's the main thing missing from all of these agents and no startup, lab or oss project really does it well. Another topic I'm really into are ontologies, which is the general version of context management. The two best players in this space are Palantir and Databricks. Here are some links to learn more: palantir.com/platforms/found… - palantir.com/docs/foundry/on… and databricks.com/product/platf…. The latter ontology project is a more ambitious version of my personal context management system and will take me longer to build, but I hope to launch a really barebones version of it and work on it in the open. I've had tens of conversations with developers at companies I'm friends with about how they design internal agentic systems and this is one of their biggest pain points. We need to have open source ontology engines, together with connectors, visualization libraries and lots of surrounding tooling in order to make agents truly useful at scale, so if you're interested in this as well, hit me up! with the publication of the tools I'm building I'll also publish a long form article on dcbuilder.dev/blog about all of the things I've been working, so see you there.
30
7
3
250
17,230
krisoshea.eth retweeted
I started writing smart contracts in 2018, and one thing always bothered me: why did running my own RPC mean running a full node, or an archive node if I wanted historical state? My app only cared about my contracts, a few dependencies and some ERC20s. Why did I need to keep up with everything everyone else was doing on Ethereum just to serve those reads? The annoying part was keeping that smaller set of state up to date. Reading a value at one block was doable, but knowing what changed in the next block meant executing it or asking a node that had. A transaction could reach my contract through several other contracts, so just filtering transactions by their destination wasn’t enough. I mostly forgot about it. RPC providers got reliable enough for what I needed, and I had other things to build. I still didn’t love the setup, but it stopped being something I spent time thinking about. Then over the weekend, I was looking through Glamsterdam’s EIPs and realized block-level access lists might make this practical. BALs include the state changes made during a block, including the new values, and the block commits to that list. So once you have the initial state you care about, you can follow its changes without re-executing every transaction. So I started vibe coding it. It’s called skim. You tell it which accounts and storage slots you care about, or let it discover the state your simulations read. It fetches the initial values from Ethereum’s P2P network through SNAP, checks their Merkle proofs, and keeps them updated using BALs. Your eth_calls then run locally. If a call needs something it hasn’t fetched, it gets that from peers too, just with more latency. No upstream RPC provider for those reads. It can also keep historical versions of the state you’re tracking. That was another thing I wanted: being able to query my app’s past state without keeping everyone else’s history. It exposes a JSON-RPC interface, so existing tools can use it for the methods it supports. It still receives full payloads and BALs. The state it maintains is selective, not everything it downloads. There’s also a consensus light-client implementation now, but that path isn’t active on Sepolia yet because the required Gloas light-client data isn’t being served by the peers tested so far. For now, the head is still trusted. It’s still an experiment, and I’m working through correctness bugs and longer-running tests. I’m not presenting it as a production node replacement. But it’s pretty satisfying to finally build something around a complaint I’ve had since 2018. I wanted a small client that knows the parts of Ethereum my app actually uses, and that’s what I’m trying to make. github.com/leekt/skim
43
47
7
511
29,894
krisoshea.eth retweeted
Replying to @tempo
@tempo's tooling stack is giving me a million different ideas for my own security stack XD
2
9
98
5,349
krisoshea.eth retweeted
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.
5,958
6,264
2,293
25,549
6,657,381
Solar by @paradigm is a Solidity compiler we've been quietly building which will eliminate unsafe Solidity - we have started finally being able to produce more gas optimized assembly free code than the legendary @optimizoor Solady
24
30
7
320
34,012
krisoshea.eth retweeted
Elon gives me money, Elon takes my money. The circle of life.
693
491
123
20,172
721,695
krisoshea.eth retweeted
local entrepreneur
We've been in business for 22 years and we LOVE our customers. Look who swung by on Sunday! Local entrepreneur Palmer Lucky !! He has been a loyal customer of our little flower stand for many years. His favorite bouquet is Spring Mist. We feel so LUCKY ;) to have people like him to keep our NB community thriving. Just remember shoes next time Palmer ;)
20
21
1,539
164,725
krisoshea.eth retweeted
we will finally kill "stack too deep" the next @ethereum update brings both: 1) the ability to deploy larger contracts 2) lets compilers fix "stack too deep" eth dev is going to rip in Q4
46
88
30
507
87,893
krisoshea.eth retweeted
1/4 ePBS is headlining the upcoming glamsterdam hardfork, so I wrote a short(ish) article, titled "ePBS, distilled", highlighting what it looks like in its final form and how I believe the MEV markets will evolve once it goes live.
9
22
1
101
5,448
krisoshea.eth retweeted
ZisK v1.1.0-alpha release 🚀 Ethereum proven in real time on 4x5090 GPUs with a p99 of 9.62s. All providing 128-bit provable security, powered by Poseidon1, and post-quantum secure. This release pushes the prover further and fixes bugs, without trading soundness for benchmarks. Release notes: github.com/0xPolygonHermez/z…
17
36
17
229
52,522
krisoshea.eth retweeted
Never give up
Stripe reportedly buys OpenRouter for $7 Billion. I think their orchestration is easy to replicate and switch from. And there's very little moat. But atm, OpenRouter has the userbase, valuable dataset, + momentum. What's your take... Yay or Nay for the payments firm?
50
84
15
2,654
600,103
krisoshea.eth retweeted
Goodbye, Poseidon! An epic 8-year, 8-figure rabbit hole in post-quantum cryptography reaches its dream conclusion. The Ethereum Foundation is abandoning Poseidon for L1, pivoting to SHA or BLAKE. This milestone unlocks ultimate security for lean Ethereum and foreshadows a golden era of hash-based cryptography. Since 2018, the Ethereum Foundation has invested in magic cryptographic bricks, so-called "SNARK-friendly hashes". In 2019, Poseidon was born. It held strong and became the dominant SNARK-friendly hash, securing billions via zkrollups and zkVMs. In a stunning reversal, breakthrough SNARK designs show that SNARK-friendly hashes aren't necessary after all. Off-the-shelf traditional hash functions like SHA2 and BLAKE2s can now match Poseidon in a SNARK. In hindsight the key was not SNARK-friendly hashes, but hash-friendly SNARKs. The secret is doing maths over the smallest prime number: 2. So-called "binary fields" natively speak the language of bits, aligning with the boolean operations inside traditional hashes. This is a stark departure from "prime fields", where awkward large-prime arithmetic makes bit manipulation painfully expensive. We're talking sci-fi cryptography. 1M traditional hash calls proven per second, on a laptop. Just 100x overhead vs native CPU boolean compute. Nobody predicted such performance, not even the handful of binary-field visionaries. Hat tip to the research geniuses: Jim and Ben with Binius in 2023; Ron, Benedikt and William with Flock in June. With SHA2, the lean aesthetic of minimal assumptions reaches its climax. The EF's principled stance on pure hash-based cryptography has aged like fine wine. We now enjoy foundations the world can trust for decades and centuries, foundations worthy of the dream of an internet of value. Speed of deployment is a secondary win. There's no longer a need to wait years for Poseidon cryptanalysis to bake. Emile and Thomas from the EF post-quantum team are moving at breakneck speed with binary fields. The strawmap now points to a production-grade leanVM in 2027, with CL, DL, EL deployments in 2028. As AI becomes exceptional at cryptanalysis, the contrarian bet to avoid riskier structures like lattices and isogenies is visibly paying off. The past weeks have been brutal. Lattice-based "HAWK" and isogeny-based "SQIsign", both signature schemes in NIST's Round 3, have suffered blows. Sources I trust say more blood is coming. On AI, the open autoresearch trend kicked off by ECDSA[.]fail is spreading fast, with amazing outcomes from zk[.]golf and SNARK[.]fast. Days ago SNARK[.]fast crossed 1.8M BLAKE3/sec proven on an M3 Max. Stay tuned for fresh autoresearch challenges dropping tomorrow. Also tomorrow: Ethproofs call #10, dedicated to binary fields. Possibly the most noteworthy Ethproofs call yet. Experts leading the charge will present the future of hash-based SNARKs at 2pm UTC. What an incredible time to be alive. To witness history, DM me for a calendar invite :) Today I can confidently claim that hash-based cryptography has won out for blockchain post-quantum signatures. SNARK succinctness compresses arbitrarily many signatures into one small proof per block. SNARK flexibility yields k-of-n threshold signatures, complex multisigs, and more. Ultimate security. Uncompromising performance. Full programmability. Believe in something. Believe in hashes.
163
356
149
2,037
480,314
krisoshea.eth retweeted
The world has identified verifiable AI as a missing civilization-scale primitive. The core technical obstacle, practical zero-knowledge proofs, was considered impossible. We solved it. Today, we are launching @attestable, the AI Integrity Company, and announcing a $20M seed round led by @jaminball at @AltimeterCap and @YonatanMandelba at @TLV_Partners , with participation from @HalcyonFutures, Cerca Partners, @Weiner_Lia at Netz, @nickymontanaa at Zero Knowledge Ventures, @assaf_rappaport, Asaf Ezra, Nadir Izrael, Jon Coller, Eyal Manor, @OmerPerchik.
86
93
34
794
1,045,922
Crypto financial infrastructure has been operating under extreme paranoia that 24/7 bots are trying to hack it, by virtue of it being accessible by anyone, open source, and largely immutable. Some successfully, others not. Since February, everyone serious in crypto has been running 24/7 agents against their code, either themselves or by employing 3p red teamers who are basically prompting for them with some extra tricks / known exploit databases etc (which are also public). We have been operating an internal tool for this as well, called Cyclops, you can find it doing work in our repos @tempo. The rest of the world is about to experience this, and everybody will need to introduce 24/7 agents to defend themselves. The new meta will be that there'll be a minimum $ defense token spend that you'll need to release any kind of software. Hopefully, open models will make that minimum $ cost low enough that this doesn't raise the barrier to entry to production-grade software.
37
36
10
510
41,874
krisoshea.eth retweeted
life after you stop reviewing your coworker's slop PRs and just merge that shit
122
665
92
15,247
1,243,857