#dusk $DUSK @Dusk
I was reading through @Dusk_Foundation docs assuming privacy was basically a baseline feature across the whole network, since thats the headline pitch Than I got to the DuskEVM page and had to stop for a second.
DuskEVM is actually a pretty solid piece of the setup
You get normal Solidity tooling, Foundry, Hardhat, ethers, all of it, while settlement and data availability still run through DuskDS underneath So builders coming from Ethereum don't have to relearn everything just to plug into @Dusk_Foundation .
But heres what got me On the Dusk L1 side, privacy is built in through Phoenix, shielded transfers with selective disclosure when its needed DuskEVM, from what the docs describe, is a standard transparent EVM execution environment, and assets move between the two through a bridge🌉
So what happens to that privacy once something crosses over into DuskEVM?
Does it carry through in some form, or does moving into that environment mean the activity is now just as visible as it would be on any other EVM chain?
The docs say EVM apps can reach Dusk L1 privacy oriented workflows as integrations require, but they dont really lay out what that looks like in practice once you're actually inside DuskEVM
Not saying this is a gap or a problem, I just can't stop thinking about it now that I noticed it If @Dusk_Foundation 's whole pitch is regulated finance needing both privacy and disclosure control, the behavior at that specific crossing point seems like it matters a lot
Anyone building on DuskEVM have a clearer picture of this than I do?
@dusk #dusk $DUSK