In this week's edition of Auditor's Take, @FormallyJon breaks down the specific sequencing bug that recently drained Future Protocol. The core of the issue involved just three standard operations: a transfer, a sync call, and a burn. When these commands are executed in the proper sequence, everything operates exactly as intended and nothing unusual occurs. However, simply triggering those exact same steps in an incorrect order caused $4.6M to be emptied from the pool.