#dusk $DUSK @Dusk Reading the core components page, one line stopped me cold: “DuskDS is not a name for the complete Dusk network.”
Dusk $DUSK #dusk @Duskfoundation keeps settlement deliberately narrow. DuskDS only handles consensus, finality, data availability, and the two transaction models—Moonlight public accounts, Phoenix shielded UTXOs. The Transfer contract is the single entry for both and for gas. Execution branches on top: DuskVM runs native Rust/WASM on L1, DuskEVM settles through the same foundation.
What changed for me was the incentive. Expanding the base layer would have been easier and more familiar. Freezing settlement instead forces every market workflow to inherit the same deterministic finality and dual privacy options. That is specialized financial infrastructure, not another general chain.
Next check: the actual ratio of native DuskVM calls versus DuskEVM batches posting commitments and blobs back to DuskDS.
Dusk $DUSK #dusk @Duskfoundation keeps settlement deliberately narrow. DuskDS only handles consensus, finality, data availability, and the two transaction models—Moonlight public accounts, Phoenix shielded UTXOs. The Transfer contract is the single entry for both and for gas. Execution branches on top: DuskVM runs native Rust/WASM on L1, DuskEVM settles through the same foundation.
What changed for me was the incentive. Expanding the base layer would have been easier and more familiar. Freezing settlement instead forces every market workflow to inherit the same deterministic finality and dual privacy options. That is specialized financial infrastructure, not another general chain.
Next check: the actual ratio of native DuskVM calls versus DuskEVM batches posting commitments and blobs back to DuskDS.