Degen L3 downtime and reorganization, what happened?
- 王林Original
- 2024-06-04 12:05:241151browse
Written by: Proof of Track
Compiled by: Peng Sun, Foresight News
May 13, 04:15:29 Beijing time, L3 chain Degen Chain experienced an outage and stopped producing blocks for more than 24 hours. The outage caused community concern.
Degen Chain is an ultra-low-cost L3 chain launched by DAO infrastructure service provider Syndicate on March 28. Early yesterday morning, Rollup service provider Conduit tweeted that Degen would stop publishing Batches at 03:00 on April 11 after making custom configuration changes. According to Syndicate co-creator Will Paper on Warpcast, the block number affected by this outage is 15043908, which occurred around 17:15:45 on May 11, Beijing time. Currently, the Degen node is resynchronized from the genesis block. According to Conduit’s estimation, it will be completed at approximately 21:00 Beijing time tonight.
It was precisely because of the custom configuration change that the Degen Chain reorganized 500,000 blocks during the outage. So, what exactly happened to Degen Chain?
First of all, Degen Chain is L3 built using Arbitrum Orbit, Base (for settlement) and AnyTrust (for DA). The Gas token of Degen Chain is DEGEN. I agree very much with what penumbra team Henry said, "There is no L3, only L1 and L2." To me, Degen Chain is just "L2 on L2."
Next let’s talk about L3 block reorganization. First, why does block reorganization occur in L3? As L2BEAT researcher donnoh.eth pointed out, there are three situations, namely:
- The batch issued by the sequencer on L2 is inconsistent with the soft confirmation;
- L2 due to its own reasons Reorganization;
- L1 reorganization leads to L2 reorganization.
The first reason is more common and is the most likely reason for this reorganization.
In addition, we also need to think about some other questions, such as:
- Why should we believe that the managed sorter is honest?
- How to solve the reorganization problem when L2 and L3 are actually decentralized?
- What if Raas goes wrong?
- What if L1 or L2 goes wrong?
Of course, we still need Conduit’s post-mortem analysis on what exactly happened with the custom configuration changes.
The above is the detailed content of Degen L3 downtime and reorganization, what happened?. For more information, please follow other related articles on the PHP Chinese website!