Pinned Tweet
SPV for Surplus Human Capital Mining:
Flash Organization: Flashmob w/ phase transition b/t open community & value-capturing temp constructs👷
Application Specific Task Force: ASIC of heterogeneous capital formation w/ a count-down timer🏴☠️
MicroDAO: microbrewery of DAOs🐄
There.Is.Now.Alternative⚡🤖 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…
There.Is.Now.Alternative⚡🤖 retweeted
Your pre-frontal cortex is the harness for the rest of your brain
Meta-cognition is like a self-improving harness – at San Francisco, CA
There.Is.Now.Alternative⚡🤖 retweeted
OH: “Everyone in AI inference thought they weren’t a honeypot… but then I showed them this”
There.Is.Now.Alternative⚡🤖 retweeted
I am leaving Cambridge after a few days spent for a workshop on fast finality, concurrent with other workshops on post-quantum crypto and formal verification. Quick takeaways
- Faster finality is coming, the research is mature, even as new ideas have come in during the week, the handoff to specifiers and implementers feels well underway. Next catalyst event will be at devcon in a few weeks, with core devs
- The performance numbers for post-quantum finality are improving massively, and this is the worst that they’ll ever be. This is significant, it means the penalty from moving to more complex crypto would not require, in my opinion, if the numbers hold up, a deep rearchitecting to move to PQ-secure consensus, in particular when it comes to incentives
- The biggest opportunity imo remains networking. Simulations and live experiments are exploring both the current pre-PQ setting, where networking is clearly the bottleneck, and the post-PQ setting, where compute remains the bottleneck. But with PQ compute numbers improving, I wouldn’t be surprised if once again networking becomes the bottleneck
All of this is making me extremely bullish that we’ll achieve PQ-secure and faster finality even faster.
Many thanks to @yannvon @benjaminion_xyz and @robsaltini for the workshop, and to @corcoranwill and @drakefjustin for hosting us in Cambridge!
AI is making Ethereum more ambitious.
You might have heard about the challenges that blockchains face in a post-AI world, and while security assumptions will surely be stress-tested in the coming months and years, there is another side to it. I believe AI will let us speedrun towards a world that's both more secure and feature-rich.
As we look towards Ethereum's first post-AI upgrade, Hegotá, the R&D community is asking itself what increasingly powerful tools could help us do differently:
> How far can we push both security and iteration speed?
> How much of the design space can we examine before committing to one?
> How easily can we test the interactions between complex features?
My recent formal verification work @ethlabs_org has given me some reasons to be optimistic about these, as work that would have previously not even been attempted is now being done by agents in days. In September, I posted about using formal verification as part of designing a new consensus protocol. This time, I want to tell you about formally verifying something already fully specified and in production: Ethereum's Fast Confirmation Rule (FCR).
If you are not familiar with FCR, it lets applications confirm Ethereum blocks in seconds, roughly 30x faster than waiting for finality, under additional assumptions (from waiting 13 minutes to 24 seconds!). It also further solidifies Ethereum L1's case as an asset hub and center of gravity for the onchain economy. FCR now has a safety proof in Lean, closely modeling the rule in the consensus specs, which is the source of truth for Ethereum's consensus clients.
Some takeaways:
> FCR is safe! Under its assumptions, confirmed blocks remain canonical. On top of the manual proofs from the paper, we now have Lean proofs of this for the actual spec, additional evidence for applications considering FCR!
> The bulk of the formal verification work took just a 4-5 days (check out the animation!), with agents working mostly unsupervised. We should be very ambitious about using this as a tool at scale.
> After verifying the current rule, it was easy to adapt the model to the upcoming Gloas changes. Immediately, this surfaced a subtle bug caused by changes to fork choice. The problem was in the spec itself and not a gap in the model. The safety proof would not go through, and the agents could precisely pinpoint what was causing it to fail. The bug is now fixed, and formal verification of the corrected protocol goes through.
Iteration is never quite over, even for "finished" features like FCR, because the protocol keeps evolving around them. A formal model lets us ensure that key properties keep holding throughout the evolution of the protocol. With these capabilities, Ethereum can and should keep upgrading faster, tightening fork timelines and exploring more ambitious features, while still raising the security bar.
This picture has been getting much clearer over the past few months, and the past week confirmed it for me, as @drakefjustin and @corcoranwill brought together 100+ Ethereum researchers, cryptographers and formal verification experts in Cambridge for six days of workshops on post-quantum cryptography, formal verification and fast finality. Beyond its own workshop, formal verification was the omnipresent star of the week: everyone is using Lean and doing amazing things with it! Piece by piece, Ethereum's technological core is being rebuilt for the post-AI age.
The excitement was palpable, the sense of optimism was pervasive, and every talk and conversation carried a level of ambition I'd never seen before. The Ethereum R&D machine is upgrading itself, and we will see the outcome of that on the network sooner than you think.
There.Is.Now.Alternative⚡🤖 retweeted
In July we open-sourced a dynamic graph of everything a child learns in primary school. 1,590 concepts, 3,221 dependencies.
Now we’re turning every concept into interactive experiments kids can play and learn from.
First one, age 7: heat and water.
Everything that used to be a boring textbook can now be an engaging experience, potentially tailored to every child.
Kids education just got a massive upgrade.
There.Is.Now.Alternative⚡🤖 retweeted
Sometimes a demo is simply to remind the world that your competition has no desire to dream -- and no ability to evolve.
There.Is.Now.Alternative⚡🤖 retweeted
Unreal. Satoshi prob chose secp256k1 instead of NSA's P-256 because of this mystery - its a lot easier to just trust the number 7 (coefficient in secp256k1) than the mysterious possibly backdoored monster coefficient in P-256
now we know where the monster came from! its benign!
Claude figured out the origin of the NIST curve parameters. Turns out to have been timestamps!
anthropic.com/research/ecdsa…
There.Is.Now.Alternative⚡🤖 retweeted
CLAUDE FOUND THE SEEDS
anthropic.com/research/ecdsa…
There.Is.Now.Alternative⚡🤖 retweeted
Wrapped zkAPI + Tor + extra cover traffic + local LLM prompt rewriting in an open-AI compatible daemon, and made a "paranoid mode" wrapper for my agent harness (pi):
Each conversation gets assigned a separate Tor circuit, your requests are masked with random cover traffic, zkAPI ensures you don't leak your identity through payments, and all prompts are locally rewritten (bring-your-own-local-model; I'm using qwen3.8-flash-next)
github.com/vbuterin/zkapi/tr…
My agent harness is wrapped with a bwrap sandbox (also experimenting with MicroVM) and wrapped again with torsocks, so everything it does goes through Tor.
Here's what me asking it to do a simple research task looks like.
It's getting quite usable! Though you definitely still pay quite a bit in increased latency, especially when starting a new conversation.
Also, Tor is far from optimal here for privacy; the cover traffic mechanism is okay against passive adversaries but much weaker if the LLM provider is colluding with the guard and actively manipulating timing. This kind of task really requires a more specialized mixnet, probably take the tradeoff of a higher bandwidth multiplier and built-in constant cover traffic.
Also also, much cheaper zkAPI deposit and withdraw gas costs are coming to mainnet soon.
There.Is.Now.Alternative⚡🤖 retweeted
People are not ready for how much of a one man army I am in the process of becoming. Bet on your cyborg friends, they’re the only hope against the centralization of AI.
In an industry that prides itself on "don't trust, verify", herd mentality is ironically prevalent.
May have to do with individuals self selection for tribalism.
There.Is.Now.Alternative⚡🤖 retweeted
Since leaving X, I decided to try a new challenge. Could I make a chicken sandwich No. 1 on the App Store?
Well, guess what.
I have spent over a year now thinking about and building coding factories every single day. We are now hours away from releasing Smithers 1.0.0 the most powerful framework for building and self hosting your own coding factory. Fully open source. And easily the dankest thing I have ever built.
1. I am available to give your team a presentation about Smithers
2. Are you interested in building your team’s coding factory? I am looking for design partners to be added to the first cohort of Smithers factory users
3. If you were an early Smithers 0.x.x adopter I would like to whitelist you for an exciting new application built on top of Smithers I am releasing alongside the new Smithers
There.Is.Now.Alternative⚡🤖 retweeted
no comments, no deps, no docs, no tests (except e2e ones), no PRs, very little CI, a lot of CD - this might be the uncomfortable future we're headed to
There.Is.Now.Alternative⚡🤖 retweeted
This is also what will happen to Ethereum - the pace of changes will be beyond human governance abilities and the chain will start behaving like an adaptive system with hierarchies defined by the value of signal and infrastructure shape in the given region.
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
There.Is.Now.Alternative⚡🤖 retweeted
“OpenAI in talks to buy Trail of Bits” 👀 theinformation.com/articles/…






























