#dusk $DUSK @Dusk I usually try to read a protocol twice before I decide what I actually think about it.
With Dusk, I went in thinking the main story was pretty straightforward: privacy for financial applications.
Then I started looking at the XSC standard and confidential smart contracts, and I got a little less sure.
What caught my attention wasn’t simply the idea of hiding financial data. It was the awkward question underneath it: if some information is private, how do you still make sure the important parts can be verified?
That feels like the harder problem.
Because in finance, privacy can’t just mean “nobody sees anything.” There still has to be some way for rules to be followed and for people to have confidence in what happened.
I’m still thinking about that.
Maybe I’m missing something in the docs, but I find this tension more interesting than the privacy label itself.
Where do you draw the line between keeping information confidential and keeping the system verifiable?
That’s the part I want to look at more closely.
$BOS
$CAP
With Dusk, I went in thinking the main story was pretty straightforward: privacy for financial applications.
Then I started looking at the XSC standard and confidential smart contracts, and I got a little less sure.
What caught my attention wasn’t simply the idea of hiding financial data. It was the awkward question underneath it: if some information is private, how do you still make sure the important parts can be verified?
That feels like the harder problem.
Because in finance, privacy can’t just mean “nobody sees anything.” There still has to be some way for rules to be followed and for people to have confidence in what happened.
I’m still thinking about that.
Maybe I’m missing something in the docs, but I find this tension more interesting than the privacy label itself.
Where do you draw the line between keeping information confidential and keeping the system verifiable?
That’s the part I want to look at more closely.
$BOS
$CAP