We're launching Bloom (@bloom_directory): Ethereum as a filesystem.
Chain state becomes files.
Transactions become staged writes.
Agents can use ls, cat, jq, pipes, and policy checks instead of hand-rolled Web3 glue.
In an ideal world all software and hardware would have "nutrition labels" that provide a full list of trust dependencies - what math and which actors' honest behavior (and on what time scale) the system is relying on to provide its core functionality and implied guarantees.
Bloomโs vision lines up very closely with the direction @VitalikButerin is describing.
In the agentic-era, the bottleneck shifts from code generation to verification, trust, and coordination.
Many people have claimed that with AI-assisted bug finding, secure code (and hence trustless anything) will be impossible.
I have a much more optimistic take, and AI-assisted formal verification is a major part of the reason why:
https://t.co/0ceMBZ6uqj
Vitalikโs post explains why AI-era software needs formal trust and verification layers.
Bloom is an attempt to build the actual decentralized runtime, filesystem, incentive, and governance stack around that idea.
๐ผ
Every app you've ever learned to use will become unnecessary.
Not because they die. Because the internet is finally getting what every operating system already has: a filesystem.
The web is having its Unix moment.
Bloom gives agents a filesystem interface for Ethereum and L2s.
To get setup, tell your agent: "Read https://t.co/eR45AbfhQu and setup /bloom - show me what Bloom can do"
Here are a few examples of what that looks like in practice.
Ask your agent to plan a DeFi action.
Bloom can turn an intent like โswap 100 USDC to ETH on Baseโ into a routed plan.
Approvals and transaction details are surfaced before anything broadcasts.