Was deep in the DuskDS / DuskVM / DuskEVM breakdown for the CreatorPad task on Dusk ($DUSK , #dusk , @Dusk ) when something small stopped me — the site's own product stack still tags DuskEVM as "Testnet." Not old news either. Checked it again today, Aug 18, three days after their Aug 15 piece on SME tokenization went live on the blog.
Here's the thing that stuck: the architecture explainer reads like three layers humming together right now. In practice only DuskDS, the native ZK settlement layer, carries the "Live" tag. DuskEVM and Hedger — the parts that actually let regular Solidity devs touch this thing — are still testnet. So the privacy-native side is already earning its keep (210M+ DUSK staked, ~10s finality on the live counter) while the EVM path everyone cites as "the onboarding ramp" is… still a promise with a status badge attached.
Kept scrolling back up thinking I'd misread the labels. Hadn't.
Makes sense as a sequencing choice — get the compliant settlement rail proven with institutions first, bring the EVM crowd in once it's boring and stable. But it does mean "three components working together" is more roadmap than current state.
Who's actually building on this today versus who's just bookmarking docs for later?
@Dusk
#dusk
$DUSK
Here's the thing that stuck: the architecture explainer reads like three layers humming together right now. In practice only DuskDS, the native ZK settlement layer, carries the "Live" tag. DuskEVM and Hedger — the parts that actually let regular Solidity devs touch this thing — are still testnet. So the privacy-native side is already earning its keep (210M+ DUSK staked, ~10s finality on the live counter) while the EVM path everyone cites as "the onboarding ramp" is… still a promise with a status badge attached.
Kept scrolling back up thinking I'd misread the labels. Hadn't.
Makes sense as a sequencing choice — get the compliant settlement rail proven with institutions first, bring the EVM crowd in once it's boring and stable. But it does mean "three components working together" is more roadmap than current state.
Who's actually building on this today versus who's just bookmarking docs for later?
@Dusk
#dusk
$DUSK
