#dusk $DUSK
Today I was digging into @Dusk_Foundation 's DuskEVM live testnet to better understand it. To be honest, At First glance it seemed pretty straightforward..... DApps can be deployed on Dusk using familiar Ethereum tools like Solidity and Hardhat. That means the barrier to entry for Ethereum developers to enter the new ecosystem is greatly reduced.
But if you go a little deeper, the matter is more interesting. However, here is where I noticed one thing. @Dusk_Foundation is not only providing EVM compatibility here, it is also trying to bring privacy and regulated finance into the same architecture. Through the Hedger module, transaction amount, balance and business logic can be kept secret, while the necesary verification is possible using Homomorphic Encryption and Zero-Knowledge Proof. But the thing is, jackfruit on the tree and oil on the mustache, that's not the case.
But yes, what worries me the most is the trade-off here - but I could be wrong in this logic. It may seem that restrained language means security. But the reality is a little different. Due to Ethereum's account-based EVM architecture, Hedger cannot provide complete anonymity. That is, even if financial data is hidden, account-level interactions are not completely anonymous. Another thing is that the more sophisticated the privacy layer, the higher the computation cost and latency can be. In addition, there is the issue of cross-layer security when bridging from @Dusk_Foundation to DuskEVM.
Yes, Of Course, there is another question.
Compliance and auditability are undoubtedly important for regulated finance. But will permissionless DeFi users find such a privacy model sufficiently independent?
Really, here, for me, is the real test of DuskEVM.
As attractive as it is to keep privacy and compliance together, this balance is perhaps the most difficult part🤔
Today I was digging into @Dusk_Foundation 's DuskEVM live testnet to better understand it. To be honest, At First glance it seemed pretty straightforward..... DApps can be deployed on Dusk using familiar Ethereum tools like Solidity and Hardhat. That means the barrier to entry for Ethereum developers to enter the new ecosystem is greatly reduced.
But if you go a little deeper, the matter is more interesting. However, here is where I noticed one thing. @Dusk_Foundation is not only providing EVM compatibility here, it is also trying to bring privacy and regulated finance into the same architecture. Through the Hedger module, transaction amount, balance and business logic can be kept secret, while the necesary verification is possible using Homomorphic Encryption and Zero-Knowledge Proof. But the thing is, jackfruit on the tree and oil on the mustache, that's not the case.
But yes, what worries me the most is the trade-off here - but I could be wrong in this logic. It may seem that restrained language means security. But the reality is a little different. Due to Ethereum's account-based EVM architecture, Hedger cannot provide complete anonymity. That is, even if financial data is hidden, account-level interactions are not completely anonymous. Another thing is that the more sophisticated the privacy layer, the higher the computation cost and latency can be. In addition, there is the issue of cross-layer security when bridging from @Dusk_Foundation to DuskEVM.
Yes, Of Course, there is another question.
Compliance and auditability are undoubtedly important for regulated finance. But will permissionless DeFi users find such a privacy model sufficiently independent?
Really, here, for me, is the real test of DuskEVM.
As attractive as it is to keep privacy and compliance together, this balance is perhaps the most difficult part🤔