Cover photo

The EFS Devnet is Live

Come kick the tires... but not too hard!

If Ethereum is becoming a world computer, it needs better ways to organize information. EFS is an attempt to make information on Ethereum more structured, navigable, and usable.

Today is April 19, Bicycle Day, which feels like a fitting time to take a new decentralized architecture for a spin. The EFS Devnet alpha is now live.

This is a public testing environment for the EFS protocol and client end-to-end. It is live enough to use, but early enough to break. For now, the devnet runs on a pinned Sepolia fork rather than public Sepolia, because the system is still changing quickly. Connect a wallet and it will be auto-funded on first contact, so you do not need to worry about gas costs or finding a faucet.

In other words, this is a low-friction way to start exploring EFS before the shape of the system hardens.

Try it here

https://app.efs.eth.limo (https://app.efs.eth.link works too)

What you can do today

The interface is still basic, but right now you can already:

  • upload files to the devnet

  • browse parts of the EFS client and explorer

  • inspect tagged and seeded content paths

  • test early social/file workflows

  • break things and tell me what feels wrong

Data onchain by default

One of the most distinctive features of this alpha is that files go onchain by default. This alpha is not just about interface testing - it is about exploring the limits of what native Ethereum storage can actually support. The intended launch architecture uses IPFS as the main file transport, alongside Arweave, but for now, you get an onchain-first experience.

Important caveats

This is a playground, not a permanent home for important data. If you do not mind sharp edges, I would love for you to try it.

Please assume:

  • devnet files will be deleted weekly

  • things may crash

  • things may change at any time

  • parts of the architecture are still evolving

  • some explorer views and seeded content are still under active iteration

Why release now

I would rather get EFS into people's hands early than wait for a false sense of completeness.

The architecture is solidifying, but it isn't fully there yet. Getting real usage and real feedback right now will shape the product, the architecture, and the user experience much more effectively than keeping it private for another few weeks.

Feedback wanted

The best time to get feedback is before the shape of the system hardens. I would love for you to try the system with free devnet gas and report what feels broken or confusing.

I am especially interested in:

  • bugs and crashes

  • confusing UX

  • what feels intuitive

  • what doesn't make sense yet

  • what you expected to be able to do next

Best places to send feedback:

A bigger story post unpacking the full vision is coming later, along with a presentation on May 8. But for now, this is the beginning, not the finished form.