Checked in on @Dusk 's bridge status again this week and it's still closed. Same message as before, security review ongoing, no confirmed reopening date yet. At this point that's the more interesting data point than the incident itself.
$DUSK 's core chain never stopped, that part was clear early. What's less clear is how "temporary" a pause like this actually is when it's tied to a bigger launch, DuskEVM in this case. The team explicitly linked the bridge reopening to getting that launch right too, so the timeline isn't just about patching a wallet, it's about not rushing two things at once.
I went in expecting a quick patch-and-reopen story. Instead I'm watching a team choose to sit in the uncomfortable middle, publicly, for longer than most projects would tolerate.
Not sure yet if that's discipline or just how long these reviews genuinely take. Guess that's the thing you can't verify from the outside.
#dusk
$DUSK 's core chain never stopped, that part was clear early. What's less clear is how "temporary" a pause like this actually is when it's tied to a bigger launch, DuskEVM in this case. The team explicitly linked the bridge reopening to getting that launch right too, so the timeline isn't just about patching a wallet, it's about not rushing two things at once.
I went in expecting a quick patch-and-reopen story. Instead I'm watching a team choose to sit in the uncomfortable middle, publicly, for longer than most projects would tolerate.
Not sure yet if that's discipline or just how long these reviews genuinely take. Guess that's the thing you can't verify from the outside.
#dusk
