Replying to Avatar Matt Corallo

Not sure which numbers you’re referring to, but I think I agree with the *need*, just strongly disagree with the idea that we have any great solutions. From where I sit, the ideas for scaling using covenants often don’t provide all that much scale, and almost always make other tradeoffs.

IMHO one of the more compelling ideas is timeout trees (which sadly was proposed after people had kinda given up on CTV). But it makes a huge tradeoff - if you get screwed it costs you 10-20x more to FC than Lightning. Worse, an operator can create a “ghetto” of poor users and screw them all to steal from them. *but* it gets you great optimistic-case scaling!

Most things end up looking like that, and it leaves me pretty unexcited…except that the research is moving at a clip! I’m excited to see what the research comes up with, in the mean time I’m still building lightning.
Avatar
fiatjaf 1y ago

By the way, do we really any prospects of creating a trustless decentralized L2 on Bitcoin ever? Isn't it true that Ethereum has had all the ability to make any covenants they want for years and after so much time trying to find a scalable solution the best they got was zk rollups that centralize everything in the hands of a company and require a ton of space anyway that has to be acknowledged by the chain consensus?

In other words, even if we had all the opcodes we wanted by magic we would still be just as bad at scaling as Ethereum is currently?

Reply to this note

Please Login to reply.

Discussion

Avatar
Matt Corallo 1y ago

Yea, I mean the ETH zkRollups are super centralized but to some extent that’s a consequence of these things being hard to build so they need an “escape valve” in practice. There’s not a lot of motivation to remove that but I assume it’ll get removed eventually…. just may be a while.

I do think it’s somewhat informative that ETH only built *rollups*, which certainly don’t have a huge scalability multiple themselves (doubly so for payments, though it’s important to note ETH is trying to scale computation, not payments).