I was looking at DuskEVM today and one thing made more sense to me than the usual “EVM-compatible” description.
Dusk has separated execution from settlement.
DuskEVM is the EVM execution layer, where developers can use Solidity and familiar EVM tools. DuskDS sits underneath it as the settlement and data-availability layer. So the two aren't doing the same job.
Then there is Hedger.
According to the Dusk documentation, Hedger runs on DuskEVM and is designed for EVM-first applications that need confidential flows. Dusk describes its approach around privacy, selective disclosure and verifiable execution rather than simply making everything public or everything private.
That distinction is important for financial applications.
A transaction can involve information that shouldn't necessarily be visible to everyone, while the system can still need rules around who is allowed to see certain information.
That's the part of Dusk I find worth following. The project isn't treating privacy as the only goal. Its architecture is trying to give builders different tools depending on what an application actually needs: DuskEVM for EVM development, DuskVM for direct L1 execution, and DuskDS for settlement and data availability.
I'm more interested in seeing how builders use these pieces than repeating another generic “privacy blockchain” description.
#dusk $DUSK @Dusk
Dusk has separated execution from settlement.
DuskEVM is the EVM execution layer, where developers can use Solidity and familiar EVM tools. DuskDS sits underneath it as the settlement and data-availability layer. So the two aren't doing the same job.
Then there is Hedger.
According to the Dusk documentation, Hedger runs on DuskEVM and is designed for EVM-first applications that need confidential flows. Dusk describes its approach around privacy, selective disclosure and verifiable execution rather than simply making everything public or everything private.
That distinction is important for financial applications.
A transaction can involve information that shouldn't necessarily be visible to everyone, while the system can still need rules around who is allowed to see certain information.
That's the part of Dusk I find worth following. The project isn't treating privacy as the only goal. Its architecture is trying to give builders different tools depending on what an application actually needs: DuskEVM for EVM development, DuskVM for direct L1 execution, and DuskDS for settlement and data availability.
I'm more interested in seeing how builders use these pieces than repeating another generic “privacy blockchain” description.
#dusk $DUSK @Dusk