The day I went to the bank to take care of a few things, I grabbed a ticket number. There were around twenty people ahead of me. I sat there and waited, and happened to have a DUSK document on my phone, so I opened it. Day after day, what the bank counters do is basically two things: keep records and protect confidentiality. But with the blockchain ledger, the books are public by nature.
While I was queuing that day, it suddenly clicked for me—if finance is going to move onto the chain, the first hurdle is privacy.
$BTC
While I was waiting, I went through the document and found that it breaks these two matters into separate modules to address them differently. XSC aligns with the standards of securities regulators. Confidential smart contract execution stays local. Verification only requires proof, and it also supports selective disclosure to authorized parties.
I weighed the design in my mind. It’s essentially taking the power to decide “who can see what” back off the chain and handing it to the owner of the transaction. Consensus runs on Succinct Attestation, aiming for block production on the order of about 10 seconds; under ideal conditions, it can be even lower. Once finalized, it’s finality—no need to wait for it to “change its mind.” The DuskEVM execution layer is about 2 seconds. Overall, it’s already a modular structure, with DuskDS handling settlement, and DuskVM and DuskEVM handling execution.
$ETH
When the counter called my number, I still had half a page left to read. I closed my phone to handle my business, but in my mind I was still thinking about that last half page. For a chain like DUSK—built for finance—privacy isn’t an optional add-on feature. It’s the very first thing every step of its design is solving.
I said that sentence after standing on the steps outside the bank for a bit and speaking it in one go.
#dusk $DUSK @Dusk
While I was queuing that day, it suddenly clicked for me—if finance is going to move onto the chain, the first hurdle is privacy.
$BTC
While I was waiting, I went through the document and found that it breaks these two matters into separate modules to address them differently. XSC aligns with the standards of securities regulators. Confidential smart contract execution stays local. Verification only requires proof, and it also supports selective disclosure to authorized parties.
I weighed the design in my mind. It’s essentially taking the power to decide “who can see what” back off the chain and handing it to the owner of the transaction. Consensus runs on Succinct Attestation, aiming for block production on the order of about 10 seconds; under ideal conditions, it can be even lower. Once finalized, it’s finality—no need to wait for it to “change its mind.” The DuskEVM execution layer is about 2 seconds. Overall, it’s already a modular structure, with DuskDS handling settlement, and DuskVM and DuskEVM handling execution.
$ETH
When the counter called my number, I still had half a page left to read. I closed my phone to handle my business, but in my mind I was still thinking about that last half page. For a chain like DUSK—built for finance—privacy isn’t an optional add-on feature. It’s the very first thing every step of its design is solving.
I said that sentence after standing on the steps outside the bank for a bit and speaking it in one go.
#dusk $DUSK @Dusk