#dusk $DUSK Dusk caps blocks at 1MB.
That works out to roughly 250 Phoenix transactions per block , per Dusk's own engineering notes. Do the division and a single shielded transfer runs close to 4KB.
A plain UTXO transfer on a transparent chain sits under 500 bytes. The PLONK proof itself stays compact and constant-size, holding near half a kilobyte no matter how complex the circuit gets . So the extra weight isn't the proof. It's the notes, nullifiers, and commitments a shielded transfer has to carry so a spend can't be traced back to anyone.
Privacy is paid for in bytes, not compute.
I figured that was the whole scalability story until I went digging into DuskEVM. It runs on the OP Stack, executing EVM transactions while a batcher posts the transaction data back to DuskDS as blobs instead of to Ethereum . Smart on paper. Pull general contract execution off the privacy-native settlement layer, give it its own gas market, keep DuskDS lean.
Except those blobs still land on DuskDS's own block budget. Same finite bytes the shielded transfers already fight over. And right now, DuskEVM runs sequencer-only, with no public mempool
So the chokepoint didn't disappear. It relocated, and ordering got more centralized on the way there. DUSK is the native gas token across both the DuskDS and DuskEVM layers , so its real usage curve hinges on whether that shared byte budget holds once EVM traffic actually shows up at scale.
Does a modular privacy chain solve congestion by adding layers, or just move it somewhere harder to check?
#Dusk @Dusk
That works out to roughly 250 Phoenix transactions per block , per Dusk's own engineering notes. Do the division and a single shielded transfer runs close to 4KB.
A plain UTXO transfer on a transparent chain sits under 500 bytes. The PLONK proof itself stays compact and constant-size, holding near half a kilobyte no matter how complex the circuit gets . So the extra weight isn't the proof. It's the notes, nullifiers, and commitments a shielded transfer has to carry so a spend can't be traced back to anyone.
Privacy is paid for in bytes, not compute.
I figured that was the whole scalability story until I went digging into DuskEVM. It runs on the OP Stack, executing EVM transactions while a batcher posts the transaction data back to DuskDS as blobs instead of to Ethereum . Smart on paper. Pull general contract execution off the privacy-native settlement layer, give it its own gas market, keep DuskDS lean.
Except those blobs still land on DuskDS's own block budget. Same finite bytes the shielded transfers already fight over. And right now, DuskEVM runs sequencer-only, with no public mempool
So the chokepoint didn't disappear. It relocated, and ordering got more centralized on the way there. DUSK is the native gas token across both the DuskDS and DuskEVM layers , so its real usage curve hinges on whether that shared byte budget holds once EVM traffic actually shows up at scale.
Does a modular privacy chain solve congestion by adding layers, or just move it somewhere harder to check?
#Dusk @Dusk