BuilderDAO

Builder

One thing I could never find the answer to is why rollups use less on-chain space than normal native L1 txs?

Whatever the reason, couldn’t L1 also do that?

Not sure I get that: if it is compressed, you can pass around smaller blocks, which means you can do more, everything else being equal.

the way it was explained to me a long time ago was that they basically "outsource" computation needed to execute tx in different storage locations and return it in compressed/byte size data. 

you can compress your data on an L1 but its pointless because you still exerted energy to do that

https://material.work


prev: https://persistence.wtf / https://nouns.build

I’m asking a much narrower question than simply how rollups work

its basically a way to compute things offchain and then update L1 later in one batch instead of doing all the work on L1. eventually there are plans to enshrine this in the protocol in the case of eth but the market is currently battling it out for the best implementation