Launch an L2 or L3 in a few clicks, no code required. Ask questions about rollups in /conduit

Degen Chain Downtime from last week – below is the key sequence of events with timestamps and blocks numbered.  This Wednesday is the ETA  of @conduit's post-mortem analysis. Currently there are reports of lost funds between points (1) and (4) below.

gm. It has been nearly 11 days since Degen L3 stopped operating normally at block 14.5M. This is an open letter to @conduit and @syndicate to release a post-mortem (or if the problem isn’t dead yet, a mid-mortem / vivisection).

How Some Funds Were Lost During the Degen Chain Outage

In this thread, I'll share an example of how some DEGEN funds were lost due to the outage and how, in some cases, funds may still be recovered.

🧵⬇️

Other informative threads on the topic:

(1) @hlau – https://warpcast.com/hlau/0x650bfa24
(2) @tempetechie.eth – https://warpcast.com/tempetechie.eth/0x1ffaac38
(3) @proxystudio.eth – https://warpcast.com/proxystudio.eth/0x5fb17519

Making DeFi accessible to everyone - building @starta | FID 675

Here is the published post-mortem: https://conduitxyz.notion.site/External-Degen-and-Proof-of-Play-Incident-Post-Mortem-0b47c88868034e51924b00e712ca1ddb

Conduit is investigating an issue with the Degen L3 sequencer.

We will share more updates here when we have them.

Finally, a second recent event, on May 18, caused a much shorter Degen Chain downtime of ~30-60m. So far no known / reported significant incidents as a result. It's not yet known whether this 2nd event is linked to / caused by the 1st.

Finally, a second recent event, on May 18, caused a much shorter Degen Chain downtime of ~30-60m. So far no known / reported significant incidents as a result. It's not yet known whether this 2nd event is linked to / caused by the 1st.

https://warpcast.com/conduit/0x27ee2086

(2) "the reorg started from" (after this point "reorg" branch shows on block explorer):
2024-05-11 20:16:09 UTC, 1715458569
Block 14828327, 0xe24327

(3) "reorg trigger":
2024-05-12 20:18:00 UTC, 1715545080
Block 15044080, 0xe58df0

(4) "RPC Down":
2024-05-12 21:42:00 UTC, 1715550120
Block 15044149, 0xe58e35

(5) "RPC Up (bug/misconfig mistake):
2024-05-12 22:38:00 UTC, 1715553480
Block 15044150, 0xe58e36

(6) "RPC Down (bug/misconfig mistake revert):
2024-05-12 23:48:00 UTC, 1715557680
Block 15044182, 0xe58e56

(7) "RPC Up":
2024-05-15 04:15:00 UTC, 1715746500
Block 15053321, 0xe5b209

(8/8) "Conduit's snapshot is from...":
2024-05-16 13:03:06 UTC, 1715864586
Block 15523559, 0xecdee7

(1) "post resync, the network reorged again, so we have now realized this is safe"
2024-05-09 18:17:19 UTC, 1715278639
Block 14500000, 0xdd40a0