Noticed something odd while mapping out Dusk’s two execution environments: DuskVM (native Rust/WASM, where the privacy-preserving transfers live) and DuskEVM (Solidity, EVM-tooling). Official copy from the Dusk-Chainlink partnership post says NPEX’s tokenized securities are “issued on DuskEVM” — but Dusk’s own product page still tags DuskEVM’s status as “Testnet,” while a separate Blockscout instance labeled “DuskEVM Mainnet Explorer” is already indexed and live. Two official sources, two different maturity claims for the same layer.
Dug into GitHub to sort it out. The clearest recent signal I found: dusk-network/duskevm-genesis (the repo holding DuskEVM’s genesis block and rollup config) shows a commit dated Aug 8 — active engineering on the exact layer in question, just outside a tight 7-day window but the freshest dated artifact I could pin down.
Data shows: regulated asset issuance is explicitly routed to the EVM-compatible layer, not the native privacy layer, while status labeling across Dusk’s own properties is inconsistent. Interpretation: could be simple lag in updating marketing copy, or it reflects a genuinely staged rollout where compliance-grade assets move first and native privacy features follow.
What I couldn’t confirm: actual DuskEVM mainnet transaction counts — the explorer blocks automated fetches, so I’m going on secondary references, not raw data.
Anyone pulled live tx volume off explorer.evm.dusk.network directly?
If someone with direct access to the DuskEVM Blockscout API can pull recent tx counts, that would resolve the testnet-vs-mainnet ambiguity a lot faster than I could from search alone.
@Dusk_Foundation $DUSK #dusk
Dug into GitHub to sort it out. The clearest recent signal I found: dusk-network/duskevm-genesis (the repo holding DuskEVM’s genesis block and rollup config) shows a commit dated Aug 8 — active engineering on the exact layer in question, just outside a tight 7-day window but the freshest dated artifact I could pin down.
Data shows: regulated asset issuance is explicitly routed to the EVM-compatible layer, not the native privacy layer, while status labeling across Dusk’s own properties is inconsistent. Interpretation: could be simple lag in updating marketing copy, or it reflects a genuinely staged rollout where compliance-grade assets move first and native privacy features follow.
What I couldn’t confirm: actual DuskEVM mainnet transaction counts — the explorer blocks automated fetches, so I’m going on secondary references, not raw data.
Anyone pulled live tx volume off explorer.evm.dusk.network directly?
If someone with direct access to the DuskEVM Blockscout API can pull recent tx counts, that would resolve the testnet-vs-mainnet ambiguity a lot faster than I could from search alone.
@Dusk_Foundation $DUSK #dusk