🚀I find myself looping back to a single awkward DUSK question while thinking about confidential execution:
If a transaction has 1 public input and 5 private ones, what exactly is a wallet supposed to simulate before signing?
On a normal EVM path, simulation works because the wallet can inspect enough state to estimate the outcome. DUSK changes that assumption.
🛡️When inputs, permissions, participant data and proofs are partially hidden, the wallet may not have the full picture of what determines the transaction result.
And this goes beyond UX.
An indexer showing 500 addresses doesn't necessarily mean 500 real participants. One institutional contract could represent thousands of investors, while hundreds of addresses could still belong to one entity.
Batching creates another trade-off.
If 1 operation fails inside a 1,000-transfer confidential batch, DUSK must balance failure isolation against additional proof and accounting complexity.
⚡So perhaps the bigger scaling question isn't just transaction throughput.
It’s whether DUSK can make private state predictable enough for wallets, institutions and observers without compromising confidentiality.
Does privacy strengthen the network, or does it also create a new challenge around measuring what’s actually happening underneath?🥺
@Dusk #dusk $DUSK
If a transaction has 1 public input and 5 private ones, what exactly is a wallet supposed to simulate before signing?
On a normal EVM path, simulation works because the wallet can inspect enough state to estimate the outcome. DUSK changes that assumption.
🛡️When inputs, permissions, participant data and proofs are partially hidden, the wallet may not have the full picture of what determines the transaction result.
And this goes beyond UX.
An indexer showing 500 addresses doesn't necessarily mean 500 real participants. One institutional contract could represent thousands of investors, while hundreds of addresses could still belong to one entity.
Batching creates another trade-off.
If 1 operation fails inside a 1,000-transfer confidential batch, DUSK must balance failure isolation against additional proof and accounting complexity.
⚡So perhaps the bigger scaling question isn't just transaction throughput.
It’s whether DUSK can make private state predictable enough for wallets, institutions and observers without compromising confidentiality.
Does privacy strengthen the network, or does it also create a new challenge around measuring what’s actually happening underneath?🥺
@Dusk #dusk $DUSK