🔥I was stunned by the report I saw on Ars Technica:
An analysis by security companies CloudSEK and Hudson Rock shows that the LiteLLM supply-chain attack in March affected more than 2,500 companies worldwide, even though the malicious packages were only online for about 40 minutes. The amount of leaked data reached the scale of around 195TB. Names like NVIDIA, AWS, and Samsung are all involved.
That makes me worry for big institutions—if even the keys of these top tech companies can be scraped away so quickly, what kind of risk would institutions face if their holdings, trade amounts, and counterparties are all put on public chains?
This is also why regulated assets have been calling for “on-chain” for so long, yet real implementation hasn’t come that fast. Public-chain transparency is fine for ordinary transactions, but for people doing real finance, once information is made public, it’s essentially like revealing your cards to everyone.
So I went back over the materials related to @Dusk , because that’s exactly what solves these problems.
At its core, DuskEVM is an EVM-compatible layer within the Dusk technology stack. Developers can continue writing contracts in Solidity, deploying with Hardhat and Foundry, and the wallet/RPC setup basically doesn’t need to change. Gas is paid with $DUSK , and final settlement lands on DuskDS. For those already used to Ethereum tooling, the barrier drops dramatically.
What made me pause a bit longer is Hedger.
It’s a privacy module built specifically for #dusk and the EVM. Its core relies on homomorphic encryption and zero-knowledge proofs. Homomorphic encryption allows computation to be performed directly on encrypted data. Zero-knowledge proofs, meanwhile, allow one to prove that a transaction is valid without revealing the specific numbers. The result is that balances and transfer amounts can be hidden from the outside world, so institutions don’t have to worry about their holdings being watched by the entire network. At the same time, the authorized regulator can still perform necessary review through the proof path.
I even looked up what on earth homomorphic encryption is, and found that it can actually operate directly on encrypted data. For institutions, its practicality is far higher than pure anonymity. This design puts privacy and auditability into the same workflow.
DuskEVM brings in the familiar developer experience, while Hedger fills in compliance-grade privacy protection. Together, they give institutions a much more realistic choice.
When even big-factory keys can be scraped away in 40 minutes, regulated finance needs controllable privacy more than anything.
An analysis by security companies CloudSEK and Hudson Rock shows that the LiteLLM supply-chain attack in March affected more than 2,500 companies worldwide, even though the malicious packages were only online for about 40 minutes. The amount of leaked data reached the scale of around 195TB. Names like NVIDIA, AWS, and Samsung are all involved.
That makes me worry for big institutions—if even the keys of these top tech companies can be scraped away so quickly, what kind of risk would institutions face if their holdings, trade amounts, and counterparties are all put on public chains?
This is also why regulated assets have been calling for “on-chain” for so long, yet real implementation hasn’t come that fast. Public-chain transparency is fine for ordinary transactions, but for people doing real finance, once information is made public, it’s essentially like revealing your cards to everyone.
So I went back over the materials related to @Dusk , because that’s exactly what solves these problems.
At its core, DuskEVM is an EVM-compatible layer within the Dusk technology stack. Developers can continue writing contracts in Solidity, deploying with Hardhat and Foundry, and the wallet/RPC setup basically doesn’t need to change. Gas is paid with $DUSK , and final settlement lands on DuskDS. For those already used to Ethereum tooling, the barrier drops dramatically.
What made me pause a bit longer is Hedger.
It’s a privacy module built specifically for #dusk and the EVM. Its core relies on homomorphic encryption and zero-knowledge proofs. Homomorphic encryption allows computation to be performed directly on encrypted data. Zero-knowledge proofs, meanwhile, allow one to prove that a transaction is valid without revealing the specific numbers. The result is that balances and transfer amounts can be hidden from the outside world, so institutions don’t have to worry about their holdings being watched by the entire network. At the same time, the authorized regulator can still perform necessary review through the proof path.
I even looked up what on earth homomorphic encryption is, and found that it can actually operate directly on encrypted data. For institutions, its practicality is far higher than pure anonymity. This design puts privacy and auditability into the same workflow.
DuskEVM brings in the familiar developer experience, while Hedger fills in compliance-grade privacy protection. Together, they give institutions a much more realistic choice.
When even big-factory keys can be scraped away in 40 minutes, regulated finance needs controllable privacy more than anything.