Been poking around DuskEVM the last few days, chain ID 745, testnet RPC responding clean at rpc.testnet.evm.dusk.network... and then I went looking for how devs would actually get funds onto it. Turns out the bridge has been sitting paused since August 16, after the team caught suspicious activity on a wallet used for bridge ops. #dusk $DUSK @Dusk
Here's the thing that stuck with me. The incident notice itself says the bridge stays closed until they've got "a confirmed plan and timeline for reopening bridge services and resuming the DuskEVM launch." Not a separate note, not a footnote — the EVM rollout is literally chained to the bridge reopening. So the whole "bring Solidity devs in" pitch is currently gated behind a security review that has no announced end date.
Kind of a funny gap between the two narratives running in parallel right now. One is "deploy with Hardhat, familiar tooling, come build" — testnet's live, docs are clean, chain ID checks out fine. The other is "please don't send funds to the old bridge address, contact support if you did." Devs testing locally don't feel it yet. Anyone actually trying to move capital in does.
Makes me wonder less about the EVM tech itself and more about whether "developer access" even means anything before the money can move.