Started this course where a markets protocol should be judged first, the settlement layer.
Dusk runs Succinct Attestation, a proof-of-stake, committee-based consensus. The property that matters, deterministic finality, once a block is ratified its final, no user-facing reorgs in normal operation. Compare that to probabilistic chains where finality is a confidence curve, six confirmations, twelve, pick your comfort level.
Why does determinism matter so much for THIS chain specificaly? Becuase dusk targets regulated financial markets, and regulated settlement cannot be probabilistic. A securities trade thats "probably final" is not settled, its pending, and pending positions carry legal and capital obligations. Tradfi runs on the concept of settlement finality as a LEGAL fact, the moment ownership definitively transfers. A chain wanting to host real securities must produce that moment on demand, not asymptoticaly.
The design consequence worth noting, dusk seperates settlement from execution entirely. DuskDS handles consensus, finality and data availability, while execution happens above it, in duskvm or duskevm. The settlement layer stays simple and final, the application layers stay flexible.
What im uncertain about after day one, committee-based consensus concentrates block production into selected committees, and I want to understand how committee selection resists capture. Fifteen days to find out.
@Dusk_Foundation #dusk $DUSK
Dusk runs Succinct Attestation, a proof-of-stake, committee-based consensus. The property that matters, deterministic finality, once a block is ratified its final, no user-facing reorgs in normal operation. Compare that to probabilistic chains where finality is a confidence curve, six confirmations, twelve, pick your comfort level.
Why does determinism matter so much for THIS chain specificaly? Becuase dusk targets regulated financial markets, and regulated settlement cannot be probabilistic. A securities trade thats "probably final" is not settled, its pending, and pending positions carry legal and capital obligations. Tradfi runs on the concept of settlement finality as a LEGAL fact, the moment ownership definitively transfers. A chain wanting to host real securities must produce that moment on demand, not asymptoticaly.
The design consequence worth noting, dusk seperates settlement from execution entirely. DuskDS handles consensus, finality and data availability, while execution happens above it, in duskvm or duskevm. The settlement layer stays simple and final, the application layers stay flexible.
What im uncertain about after day one, committee-based consensus concentrates block production into selected committees, and I want to understand how committee selection resists capture. Fifteen days to find out.
@Dusk_Foundation #dusk $DUSK