💥 Gate Square Event: #Post0GWinUSDT# 💥
Post original content on Gate Square related to 0G or the ongoing campaigns (Earn, CandyDrop, or Contract Trading Competition) for a chance to share 200 USDT rewards!
📅 Event Period: Sept 25, 2025, 18:00 – Oct 2, 2025, 16:00 UTC
📌 Related Campaigns:
Earn: Enjoy stable earnings
👉 https://www.gate.com/announcements/article/47290
CandyDrop: Claim 0G rewards
👉 https://www.gate.com/announcements/article/47286
Contract Trading Competition: Trade to win prizes
👉 https://www.gate.com/announcements/article/47221
📌 How to Participate:
1️⃣ Post original cont
Vitalik: Fusaka is developing the core functionality PeerDAS, aimed at achieving real-time Blockchain access without the need to download complete data.
Golden Finance reports that Ethereum founder Vitalik Buterin stated on the X platform that security is the top priority for Fusaka. Its core feature PeerDAS is attempting something unprecedented: creating a real-time blockchain that does not require any single node to download all the data. The way PeerDAS works is that each Node only requests a small amount of "data chunks", probabilistically verifying that over 50% of the data chunks are available. If more than 50% of the data chunks are available, then theoretically the Node can download these data chunks and use erasure coding to recover the rest of the data. In the first version, the complete data of the block still needs to exist in one place, and there are two scenarios: (i) Initial Broadcasting: When data is published for the first time; (ii) Data Reconstruction: When the publisher has released data blocks between 50% and 100%. But these roles are all trustless: we only need one honest participant to perform these tasks, and even with 100 dishonest participants, the protocol will bypass them. Furthermore, different nodes can execute this task for different blocks. In the future, cell-level messaging and distributed block building will allow these two functions to be decentralized as well. These are all new technologies, and it is wise for the core developers to remain super cautious during testing, even though they have been working on this for many years. This is also why the initial number of blobs will increase conservatively and then become more aggressive over time. But this is the key to L2 scaling (and ultimately also the key to L1 scaling, once the L1 gas limit is high enough that we have to put L1 execution data into blobs).