How Dusk Approaches Digital Securities
Spent some time this week trying to trace how much of Dusk’s on-chain activity actually touches the NPEX securities side versus just base-layer protocol noise, and ran into a wall worth mentioning.
Checked The DUDE (duskexplorer.com), an independent Dusk explorer, on a recent 24h window: 252 total transactions, 89 of them contract calls — roughly 35% of network activity is smart-contract interaction rather than plain transfers or staking. That’s a meaningful share for a chain this size. But the explorer doesn’t label which contracts these calls hit. There’s no dApp tag, no “NPEX” flag, nothing distinguishing a Zedger securities call from a reward-withdraw or generic contract deploy.
So the public data confirms real contract usage is happening — but not what kind. The €200-300M NPEX tokenization figure comes entirely from press releases and partner statements, not from anything I could independently trace to specific on-chain contract addresses.
What surprised me: for a project whose whole pitch is auditable, compliant securities settlement, the retail-facing explorer tooling doesn’t make that activity legible at all. Maybe that’s intentional given the privacy design, maybe it’s just early tooling.
Has anyone actually traced a Zedger or NPEX-linked contract address directly?
The tool isn’t available right now, so here’s the same table in text:
@Dusk_Foundation $DUSK #dusk
Spent some time this week trying to trace how much of Dusk’s on-chain activity actually touches the NPEX securities side versus just base-layer protocol noise, and ran into a wall worth mentioning.
Checked The DUDE (duskexplorer.com), an independent Dusk explorer, on a recent 24h window: 252 total transactions, 89 of them contract calls — roughly 35% of network activity is smart-contract interaction rather than plain transfers or staking. That’s a meaningful share for a chain this size. But the explorer doesn’t label which contracts these calls hit. There’s no dApp tag, no “NPEX” flag, nothing distinguishing a Zedger securities call from a reward-withdraw or generic contract deploy.
So the public data confirms real contract usage is happening — but not what kind. The €200-300M NPEX tokenization figure comes entirely from press releases and partner statements, not from anything I could independently trace to specific on-chain contract addresses.
What surprised me: for a project whose whole pitch is auditable, compliant securities settlement, the retail-facing explorer tooling doesn’t make that activity legible at all. Maybe that’s intentional given the privacy design, maybe it’s just early tooling.
Has anyone actually traced a Zedger or NPEX-linked contract address directly?
The tool isn’t available right now, so here’s the same table in text:
@Dusk_Foundation $DUSK #dusk