The 280 transfers caught my eye, but I ended up paying more attention to everything around them.
I went through the latest Dusk Hyperlane sign off work and the testing so far looks solid. The latest clean repro passed the contract builds, VM tests, transaction tests and Hyperlane agent checks. Then the high volume soak ran 7 cycles, with 20 EVM to Dusk and 20 Dusk to EVM transfers in each cycle. That came to 280 total transfers over 7,282 seconds before the 120 minute test window ended.
What I found more important was the production checklist sitting beside those results. Production signer custody is still being decided. There is also an open decision around pending escrow recovery, how long the soak should run, and how the CI and reproducibility setup should work. Those are easy to overlook when the headline number is a successful test, but they are the things I would want to understand before real liquidity is involved.
The signer question is especially hard to ignore after what happened with the old Dusk to EVM bridge in January. An attacker gained access to the bridge signing wallet, stole DUSK from it, and moved part of the stolen funds through the bridge to BNB Smart Chain. Dusk was clear that the incident was a bridge wallet compromise, not a Dusk consensus or protocol exploit. The bridge was later redesigned with stronger separation between signing, event handling and fund release, along with tighter balance and recovery controls.
So I’m not looking at the 280 transfers as either a green light or a red flag. They show that the system is being tested seriously. What matters to me now is how the system is supposed to behave when something goes wrong, who controls the sensitive parts, and how recovery is handled.
That’s what I’d want settled before treating Dusk Hyperlane as infrastructure for meaningful liquidity.
$DUSK @Dusk #dusk
I went through the latest Dusk Hyperlane sign off work and the testing so far looks solid. The latest clean repro passed the contract builds, VM tests, transaction tests and Hyperlane agent checks. Then the high volume soak ran 7 cycles, with 20 EVM to Dusk and 20 Dusk to EVM transfers in each cycle. That came to 280 total transfers over 7,282 seconds before the 120 minute test window ended.
What I found more important was the production checklist sitting beside those results. Production signer custody is still being decided. There is also an open decision around pending escrow recovery, how long the soak should run, and how the CI and reproducibility setup should work. Those are easy to overlook when the headline number is a successful test, but they are the things I would want to understand before real liquidity is involved.
The signer question is especially hard to ignore after what happened with the old Dusk to EVM bridge in January. An attacker gained access to the bridge signing wallet, stole DUSK from it, and moved part of the stolen funds through the bridge to BNB Smart Chain. Dusk was clear that the incident was a bridge wallet compromise, not a Dusk consensus or protocol exploit. The bridge was later redesigned with stronger separation between signing, event handling and fund release, along with tighter balance and recovery controls.
So I’m not looking at the 280 transfers as either a green light or a red flag. They show that the system is being tested seriously. What matters to me now is how the system is supposed to behave when something goes wrong, who controls the sensitive parts, and how recovery is handled.
That’s what I’d want settled before treating Dusk Hyperlane as infrastructure for meaningful liquidity.
$DUSK @Dusk #dusk
