a timeless @kelvin classic 

https://kelvinfichter.com/pages/thoughts/hybrid-rollups/

I actually have an idea on how to do a hybrid zk/op roll up.

It uses the underlying principle of this post I wrote: https://ethresear.ch/t/lookup-singularity-via-mmr/18704
…

lore @optimism | ex: @coinbase & crypto twitter | views are my own | oncha↑n summer 

Working on building zkTLS infra/products. A ruthless empiricist.

http://opacity.network

Advisor @ EV3 Ventures

Ignore the MMR part. So we’re just precomputing a lookup table and use it as a public input into the circuit.

We have a ZKP + a list of assumptions.

If the ZKP is incorrect, something in the table must be wrong. Submitting a fraud proof a table entry is a lot simpler than bisecting the execution trace.

Ethereum Researcher. OP Labs, prev. EF, working on #Ethereum scaling R&D. 🦇🔊 .oO🔴

Thanks!

Ive thought this through.

Even the MMR approach with an EigenLayer AVS would be more simple than the current approach. You just tune the amount staked to adjust security level.

tagging in people who can speak euler in case interested 

@tynes @kelvin @proto

If we verkleize sooner rather than later can we just avoid this mess entirely?

Lookup tables seem like a neat hack to optimize broken designs, but it seems like if we're totally reformatting the state space anyway in a year or two we can take advantage of that.

Why rely on fraud proofs when we can just disable fraud?