Dusk Own Bridge Notice Ties DuskEVM Launch To A Review With No End Date
went back and read Dusk's official bridge incident notice in full instead of just the headline. One sentence near the bottom stood out:
they'll share updates once "the review is complete, and we have a confirmed plan and timeline for reopening bridge services and resuming the DuskEVM launch."
read that twice. DuskEVM launch isn't described as its own independent milestone. It's explicitly tied to the bridge review finishing first. Two separate pieces of infrastructure, wallet security and an entire execution layer rollout, bundled into one dependency chain, with no date attached to either.
the notice itself is handled well otherwise, clear timeline of what was detected, what got paused, what got hardened. No user funds affected, they say. Fine. But that one line means DuskEVM's mainnet timeline was never actually independent, it was always contingent on a security review with an open-ended finish line.
anyone tracking DuskEVM as its own roadmap item was, by Dusk's own wording, actually tracking a bridge investigation with an EVM launch attached to the end of it.
Makes me wonder how many people repeating a DuskEVM launch timeline realize it was never really Dusk's call alone to make, it was always downstream of when that review closes.
#dusk $DUSK @Dusk
went back and read Dusk's official bridge incident notice in full instead of just the headline. One sentence near the bottom stood out:
they'll share updates once "the review is complete, and we have a confirmed plan and timeline for reopening bridge services and resuming the DuskEVM launch."
read that twice. DuskEVM launch isn't described as its own independent milestone. It's explicitly tied to the bridge review finishing first. Two separate pieces of infrastructure, wallet security and an entire execution layer rollout, bundled into one dependency chain, with no date attached to either.
the notice itself is handled well otherwise, clear timeline of what was detected, what got paused, what got hardened. No user funds affected, they say. Fine. But that one line means DuskEVM's mainnet timeline was never actually independent, it was always contingent on a security review with an open-ended finish line.
anyone tracking DuskEVM as its own roadmap item was, by Dusk's own wording, actually tracking a bridge investigation with an EVM launch attached to the end of it.
Makes me wonder how many people repeating a DuskEVM launch timeline realize it was never really Dusk's call alone to make, it was always downstream of when that review closes.
#dusk $DUSK @Dusk