I had a Dusk page open while checking a wallet notification, and I caught myself wondering what I’d actually need to know before building a financial app there.
My tea had gone completely cold, and there was this tiny crack in the corner of my phone screen that kept catching my eye. 😭
@Dusk
At first, I thought the answer would just be “learn XSC and start building.” I was probably making it too simple.
If I’m developing a financial application on Dusk, I’d need to understand more than the contract language. The whole point is that confidential smart contracts are part of the network’s design, so privacy isn’t something I can casually add at the end and forget about.
That changes how I’d think about the application from the beginning.
What information should stay hidden? What still needs to be verifiable? How does the contract behave when real users start interacting with it? And, honestly, what happens when the application gets complicated?
$DUSK
I initially checked a few surface-level details and thought I had the picture. Then I realized I was looking at the wrong thing.
The interesting part isn’t simply whether developers can build on Dusk.
It’s whether they can build something useful while working with the privacy assumptions that make Dusk different in the first place.
I’m still curious what the first annoying problem would be that a developer actually hits once the prototype stops being a prototype. 👀#dusk
My tea had gone completely cold, and there was this tiny crack in the corner of my phone screen that kept catching my eye. 😭
@Dusk
At first, I thought the answer would just be “learn XSC and start building.” I was probably making it too simple.
If I’m developing a financial application on Dusk, I’d need to understand more than the contract language. The whole point is that confidential smart contracts are part of the network’s design, so privacy isn’t something I can casually add at the end and forget about.
That changes how I’d think about the application from the beginning.
What information should stay hidden? What still needs to be verifiable? How does the contract behave when real users start interacting with it? And, honestly, what happens when the application gets complicated?
$DUSK
I initially checked a few surface-level details and thought I had the picture. Then I realized I was looking at the wrong thing.
The interesting part isn’t simply whether developers can build on Dusk.
It’s whether they can build something useful while working with the privacy assumptions that make Dusk different in the first place.
I’m still curious what the first annoying problem would be that a developer actually hits once the prototype stops being a prototype. 👀#dusk