---
# System prepended metadata

title: 'FIP Proposal: Ethereum State on Filecoin'

---

# FIP Proposal: Ethereum State on Filecoin

Filecoin has the potential to store state from other blockchains. With [EIP-4444](https://eips.ethereum.org/EIPS/eip-4444) on the horizon, we propose a method to use Filecoin to store historical Ethereum state. This enables novel use cases of Filecoin as a Layer 0, while simultaneously laying the groundwork for an IPFS-powered Ethereum light client.

## High-level ideas

- Store Ethereum state on Filecoin
    - Ethereum state is bridged to IPFS as the hot layer
    - Historical state is archived to Filecoin as the cold layer
- Access Ethereum state from the FVM. 
    - Rolling up Ethereum state onto Filecoin as the layer 0.
    - Enables cross-chain, trustless bridges from the FVM.
    - New methods for token swapping, metadata sharing, cross-chain state sharing.
- Access Ethereum state from IPFS.
    - IPFS plugin provides a decentralized Ethereum RPC.
    - Fetch and validate any piece of state in a distributed way.
    - Decentralized, historical archive data.

## Milestones

- Support for Ethereum IPLD codecs included in IPFS & Filecoin clients
- Tools for bridging and creating storage deals for historical state
- Support for adding an Ethereum RPC to IPFS via plugin
- In browser Ethereum light clients powered by IPFS

## Current Questions

- Can we access IPLD objects that we store on Filecoin from the FVM?
- Can we access data stored in a deal from the FVM?
- Can the FVM create or update storage deals?

## Prior Work

https://github.com/vulcanize/go-codec-dageth
https://github.com/valist-io/leo

## Authors

@nasdf
@awantoch
@jiyuu-jin
