#dusk $DUSK @Dusk
The cost of swapping chains for institutions: gas is the small end, rebuilding is the big end
The cost for an institution to swap to a new chain has never been in gas.
Audit reports, compliance processes, legal interpretations, and system integrations that are already running—everything is grown in the EVM ecosystem.
Swapping chains means redoing all of that.
Dusk co-founder Hein Dauven put it plainly in an official long-form piece:
No institution, venue, or builder wants every component to start from scratch.
DuskEVM’s mainnet is on the way. The official wording is: mainnet is coming.
This week’s testnet just launched. Solidity, Hardhat, and standard EVM wallets are in by the original team,
so the developers’ door is already open. This is when institutions finally can figure out the true cost today.
Dusk’s approach is to build the chain for regulated financial institutions:
when needed, privacy; selective disclosure as required; access control; and settlement finality,
with workflows that can map onto the MiFID II and DLT pilot framework.
DuskEVM is the entry point this path leaves for institutions.
Licensed institutions are already moving in.
Dutch exchange NPEX builds an dApp directly on DuskEVM. This exchange holds three licenses—MTF, Broker, and ECSP—
and reuses the existing standardized tools in the market for both front-end and back-end.
21X also plans to integrate DuskEVM into its supported chain.
The two firms are betting on both the licensing route and the product roadmap—the goal is for the entire workflow to pass review and actually be deployable.
The supporting tooling is also being upgraded:
Dusk Connect integrates wallets, Dusk Wallet provides the first-party workflows,
Dusk Forge does contract development, so native development doesn’t require starting from scratch.
If you want to get closer to the protocol layer, there’s also the DuskVM path via Rust/WASM.
Compatibility is just the entry.
The reason institutions will ultimately stay is beyond the entry:
Hedger adds auditable privacy to EVM applications, with settlement on a deterministic foundation.
Every step that regulated finance needs must stand up to scrutiny.
When institutions choose a chain, the账 must start with rebuilding costs.
The entry is already open—but before the mainnet goes live, will more licensed institutions join the lineup?
The cost of swapping chains for institutions: gas is the small end, rebuilding is the big end
The cost for an institution to swap to a new chain has never been in gas.
Audit reports, compliance processes, legal interpretations, and system integrations that are already running—everything is grown in the EVM ecosystem.
Swapping chains means redoing all of that.
Dusk co-founder Hein Dauven put it plainly in an official long-form piece:
No institution, venue, or builder wants every component to start from scratch.
DuskEVM’s mainnet is on the way. The official wording is: mainnet is coming.
This week’s testnet just launched. Solidity, Hardhat, and standard EVM wallets are in by the original team,
so the developers’ door is already open. This is when institutions finally can figure out the true cost today.
Dusk’s approach is to build the chain for regulated financial institutions:
when needed, privacy; selective disclosure as required; access control; and settlement finality,
with workflows that can map onto the MiFID II and DLT pilot framework.
DuskEVM is the entry point this path leaves for institutions.
Licensed institutions are already moving in.
Dutch exchange NPEX builds an dApp directly on DuskEVM. This exchange holds three licenses—MTF, Broker, and ECSP—
and reuses the existing standardized tools in the market for both front-end and back-end.
21X also plans to integrate DuskEVM into its supported chain.
The two firms are betting on both the licensing route and the product roadmap—the goal is for the entire workflow to pass review and actually be deployable.
The supporting tooling is also being upgraded:
Dusk Connect integrates wallets, Dusk Wallet provides the first-party workflows,
Dusk Forge does contract development, so native development doesn’t require starting from scratch.
If you want to get closer to the protocol layer, there’s also the DuskVM path via Rust/WASM.
Compatibility is just the entry.
The reason institutions will ultimately stay is beyond the entry:
Hedger adds auditable privacy to EVM applications, with settlement on a deterministic foundation.
Every step that regulated finance needs must stand up to scrutiny.
When institutions choose a chain, the账 must start with rebuilding costs.
The entry is already open—but before the mainnet goes live, will more licensed institutions join the lineup?