📢 Gate Square Exclusive: #PUBLIC Creative Contest# Is Now Live!
Join Gate Launchpool Round 297 — PublicAI (PUBLIC) and share your post on Gate Square for a chance to win from a 4,000 $PUBLIC prize pool
🎨 Event Period
Aug 18, 2025, 10:00 – Aug 22, 2025, 16:00 (UTC)
📌 How to Participate
Post original content on Gate Square related to PublicAI (PUBLIC) or the ongoing Launchpool event
Content must be at least 100 words (analysis, tutorials, creative graphics, reviews, etc.)
Add hashtag: #PUBLIC Creative Contest#
Include screenshots of your Launchpool participation (e.g., staking record, reward
Vitalik: No one has yet clearly defined which transactions should be on L1 and which should be on L2.
Odaily Planet Daily News Vitalik said: "So far, our scaling solution can be understood as hybrid L1 + L2, but I think no one has clearly defined which transactions should be on L1, which transactions should be on L2, and the answer 'put everything on L2' is hard to accept, because: *It is easy to lose the position of ETH as a medium of exchange, store of value, etc. If you are worried that L2 will steal users from L1 and not give back to L1, this problem will be more serious in a situation where L1 is doing almost nothing. *Cross-chain operations still require L1. If an L2 encounters issues, users still need a way to move to another L2 themselves. Therefore, there are some use cases that are difficult to avoid L1. 'Putting everything on L1' is also a difficult answer to accept, because: *If L1 supports a large number of transactions, it is prone to centralization, that is, using technologies such as ZK-EVM, etc. *The demand for on-chain transactions in the world is infinite, no matter how high the TPS of L1 is, there is always an application that needs 10 times more TPS.