Sozu currently shows 43.2M DUSK in TVL and roughly 24.07% APR on its live site.
Then I noticed something about how that route is funded.
Dusk gives users two native transaction models. Moonlight is public and account based. Phoenix is shielded and designed for confidential transfers using zero knowledge proofs.
Sozu, a staking pool built through Dusk’s stake abstraction system, currently uses public contract calls in Dusk Wallet.
Phoenix funded Sozu staking is explicitly out of scope in the current wallet implementation.
That is not a failure of @Dusk Foundation’s privacy design.
Dusk deliberately supports both transparent and shielded transaction models, while Sozu gives users a simpler way to stake without operating their own provisioner infrastructure.
But 43.2M DUSK already sitting in Sozu makes the distinction worth watching.
Privacy can be native at the protocol layer without automatically carrying into every application built above it.
The current wallet flow is a clear example the shielded path exists on Dusk but this staking route currently uses the public one.
So the metric I would watch next is not TVL alone.
It is whether staking behavior changes if Phoenix funded Sozu actions become supported too.
If privacy is native to $DUSK should wallet native applications merely make it available where supported, or preserve it by default?
#dusk
Then I noticed something about how that route is funded.
Dusk gives users two native transaction models. Moonlight is public and account based. Phoenix is shielded and designed for confidential transfers using zero knowledge proofs.
Sozu, a staking pool built through Dusk’s stake abstraction system, currently uses public contract calls in Dusk Wallet.
Phoenix funded Sozu staking is explicitly out of scope in the current wallet implementation.
That is not a failure of @Dusk Foundation’s privacy design.
Dusk deliberately supports both transparent and shielded transaction models, while Sozu gives users a simpler way to stake without operating their own provisioner infrastructure.
But 43.2M DUSK already sitting in Sozu makes the distinction worth watching.
Privacy can be native at the protocol layer without automatically carrying into every application built above it.
The current wallet flow is a clear example the shielded path exists on Dusk but this staking route currently uses the public one.
So the metric I would watch next is not TVL alone.
It is whether staking behavior changes if Phoenix funded Sozu actions become supported too.
If privacy is native to $DUSK should wallet native applications merely make it available where supported, or preserve it by default?
#dusk
