Building fully on-chain orderbook infrastructure for EVM

I mean, even if the nodes were to “execute” the blobspace data, I don’t think it will add a lot of overheads to the consensus layer, at least theoretically.

I haven’t been following up on this subject for a while so I might be wrong, so please advise.

Hey @vitalik.eth I have a question regarding the L1 gas policies.

If we can have cheap blobspaces, why can’t we just lower the gas costs of computations in general?

Asking this because, as far as I know, networking overheads are much significant than computation overhead in decentralized scaling.

For a long time, the Ethereum ecosystem has been content to develop applications for a relatively small bubble, and high fees were a good reason why we could not go further. Today, no longer. And so, we no longer have an excuse.

We no longer have an excuse to not have orderbooks on-chain.

AMM was just a compromise we made due to the high gas fee environment.

I agree — and here’s a great example of what we should be building when we no longer have such an excuse.

I agree — and here’s a great example of what we should be building when we no longer have such an excuse.

https://ethresear.ch/t/enabling-on-chain-order-matching-for-order-book-dexs-revisited-segmented-segment-trees-and-octopus-heaps-explained/15180

Kevin

@0xvinsohn