The Future of State, Part 1: OOPSIE - A new type of Snap Sync-based wallet/lightclient

[CPerezz]

@MicahZoltu

If the full state for USDC token is GBs though, then selective balances would make more sense.

Indeed is more than 1GB. You can see that in 2024 it was already 1GB in How to Raise the Gas Limit, Part 1: State Growth - Paradigm (see Figure 2). On top of that you also should account that most revival mechanisms require proofs to revive expired data.
So if you want Oopsie to be useful, you also need to store all intermediate nodes from the root of USDC contract until the root.

This is further explored in The Future of State, Part 2: Beyond The Myth of Partial Statefulness & The Reality Of ZKEVMs - #4 by MicahZoltu where we get numbers of the data needed in order to serve proofs for a particular contract. (TLDR, it’s arround 10GBs).

@MicahZoltu

While I know no one listens to me when I shout this into the wind, events (aka “logs”) should not be used for long term storage. They should be used to notify chain followers of interesting things that occurred in a block. A light client that is following head can utilize events for this trustlessly without an RPC server.

As per this, I agree we can do better. Nevertheless, it doesn’t fix or address the core issues of Oopsie within the situation where Ethereum is going to be in a couple years.