Lei Yang

But, you know, we just want to build apps because it's such a pain in the ass to get all the infrastructure ready for an app chain.

Think about on-ramping, off-ramping, bridging.

security, getting the servers, paying for the servers, thinking about gas tokens, and all sorts of stuff, right?

So RPC, for example, I think each individual ticket is not a big effort, but combined,

You cannot imagine how much time and energy we have to burn on just getting all those infrastructure projects and infrastructures lined up for a chain.

So I think building on a monolithic chain also saves that headache from app founders.

And then I think composability or asynchronous composability or cross-chain transfers, however you want to call it,

I think there are fundamental limits.

Light clients are not there still.

So without light clients for layer ones, it's, I would say, almost impossible for people to build fully trustless, fully decentralized cross-chain transfers.

And I think that's a big headache.

So just technical wise, I don't think you can get as seamless or as secure of an application if you just build an app chain.

So yeah.

Yeah.

And I guess finally the brand, the distribution channels, a monolithic chain might have, it's more like people banding together into some sort of a nation or some sort of a, like a,

federal, federated states, some sort like that.

I think these are the main benefits, I think, to build on a chain.

But of course, I think some applications that does not, there are, of course, applications that do not care about or do not care a lot about, say, the cost of upkeeping the infrastructure.

They have their own distribution.

Yes, and I would say, yes, it's probably more beneficial for them to build an app chain just because they control the entire app stack, sorry, the entire tech stack.