Today was... hectic. TLDR of the issue: If the logic the sequencer runs (in a very efficient way) isnt 100% equivalent to the Cairo Starknet claims to prove , the prover is there to prevent any deviation from the guaraneed logic (and force reorg). An edge case in a transaction today caused such a discrepency. This edge case is now fixed ofc. TLDR of lessons learned: too soon to give a certain answer. Many people took part today in debugging and restoring operations asap, but we will all ask ourselevs what we can learn here, and conduct asap an internal reflection process to brainstorm on prevention and mitigation action items going forward Feel free to ask whatever though! Including now, when the situation is fresh. The builders and I are here to answer any question. Transperancy matters to us.