#dusk @Dusk I spent some time looking through the developments around Dusk and what caught my attention is that the project seems to be moving beyond the usual "privacy blockchain" idea.
The part I find more interesting is DuskEVM. Since it provides an EVM environment developers already familiar with Solidity can build on Dusk without having to completely change the way they approach smart contracts.
The bigger question for me is what happens when privacy becomes part of those applications.
That is where Hedger becomes interesting. The idea is to keep transaction information confidential while still allowing the system to produce proofs that can be reviewed when necessary. For applications that difference could matter a lot. Institutions usually cannot put every balance, position or transaction detail into a public environment but they still need a way to demonstrate that activity follows the required rules.
So I’m looking at Dusk less from the perspective of "how private's it?". More from the perspective of how usable is that privacy for regulated finance?
There is still a lot I want to understand about the security assumptions, selective disclosure and how governance handles changes to these privacy mechanisms.
If Dusk is trying to connect financial infrastructure with, on-chain markets I think these details may ultimately matter more than the headline features.
Which part would you examine first: DuskEVM, Hedger’s privacy design or the governance and compliance layer?
@Dusk_Foundation Foundation #dusk $DUSK @Dusk
The part I find more interesting is DuskEVM. Since it provides an EVM environment developers already familiar with Solidity can build on Dusk without having to completely change the way they approach smart contracts.
The bigger question for me is what happens when privacy becomes part of those applications.
That is where Hedger becomes interesting. The idea is to keep transaction information confidential while still allowing the system to produce proofs that can be reviewed when necessary. For applications that difference could matter a lot. Institutions usually cannot put every balance, position or transaction detail into a public environment but they still need a way to demonstrate that activity follows the required rules.
So I’m looking at Dusk less from the perspective of "how private's it?". More from the perspective of how usable is that privacy for regulated finance?
There is still a lot I want to understand about the security assumptions, selective disclosure and how governance handles changes to these privacy mechanisms.
If Dusk is trying to connect financial infrastructure with, on-chain markets I think these details may ultimately matter more than the headline features.
Which part would you examine first: DuskEVM, Hedger’s privacy design or the governance and compliance layer?
@Dusk_Foundation Foundation #dusk $DUSK @Dusk