@salvatoshi
@ercwl
@brian_trollz
So I would say it's can actually be worth adding some pretty sophisticated L1 features to reduce the code burden of L2s and allow them to be reasonably simple.
Nothing is funnier than the retarded meme 'just do it on layer two' as if layer twos and what they can do are not COMPLETELY limited by what layer one can do.
When you see this argument, know you are engaging with a moron.
@Excellion
I consider CTV advocates at best naive, at worst saboteurs.
Complex features can be built on L2.
Scaling is not going to happen on the base layer. It happens on L2. The base layer will always fill up regardless of 'scaling' efforts.
@salvatoshi
@ercwl
@brian_trollz
Honestly I'm about 3x less confident in the "simplify L1 even at the expense of more complicated L2s" concept than I was five years ago. The challenge is that when you can trade off between L1 bug risk and L2 bug risk, it's not actually clear that the latter is better!
@salvatoshi
@ercwl
@brian_trollz
If you have an L1 consensus failure, stuff breaks core devs scramble for a day, but eventually things are alright again. With an L2 bug, people could permanently lose lots of money.
@VitalikButerin
@salvatoshi
@brian_trollz
What are your thoughts on OP_CAT to get us there? It’s super simple and allows us to verify merkle root hashes on the stack and run state machines which basically opens up for channel-free L2s (recursive covenants, plasmas, MATT which
@salvatoshi
likes).
@VitalikButerin
@salvatoshi
@ercwl
@brian_trollz
Introducing Facet: the affordable decentralized computation protocol.
Facet isn't a blockchain. It's a new way of looking at blockchains
And just by changing our perspective, it turns out that we can reduce Ethereum transaction costs by up to 99%
With FacetPort, you'll soon be…
@VitalikButerin
@salvatoshi
@ercwl
@brian_trollz
Vitalik, what are you talking about?
L1 is already congested enough, the less important data of L1 package it and place it into L2.
Isn't it possible to process more blockchain information faster?
@VitalikButerin
@salvatoshi
@ercwl
@brian_trollz
Would the enshrined zkEVM be an example of relieving L2 security risk?
If the circuits shared by L1/L2 zkEVMs have a bug and an L2 is attacked because of that, L1 is also attachable and hence an L1 fix (perhaps and a re-org)) can immediately step in to fix it.
@VitalikButerin
@salvatoshi
@ercwl
@brian_trollz
L1 cannot remain simplistic, if it is a burden to build on top of it. It is impossible to outsource everything to higher layers.
A protocol has to evolve as time goes on, and it is the best to enshrine various processes which can be thought as common goods. It is the most…
@VitalikButerin
@salvatoshi
@ercwl
@brian_trollz
The root problem of what you are describing is that rollups have on-chain non-deterministic behaviour. They write down state roots and other data derived from the rollup's social consensus.
That is a bridging problem. Rip it out. Scale up L2.