#dusk @Dusk $AIO $EDEN $DUSK
What keeps scratching at me on Dusk isn’t the Phoenix amount.
That part did disappear.
Its the explorer metadata row sitting beside the transfer like some nosy clerk who didn’t get the memo.
Sender hidden. Receiver hidden. Amount hidden. Phoenix note linkage shielded.
Good.
Then transaction still lands in Dusk chain history with public metadata around it.
Not the Phoenix amount.
The transaction around it.
And I can already see where people get lazy with that distinction.
Institution tells the client the transfer was confidential. Analyst opens the Dusk explorer later and still sees that a Phoenix transaction happened, roughly when it happened, maybe fee or transaction metadata the model leaves public.
No balance. No counterparties.
Still... something happened here.
I’d probably start lining timestamps up almost by reflex.
Treasury file says 14:03. Dusk explorer shows a Phoenix transaction around 14:03. Another one twenty minutes later.
Nothing proven.
But now somebody is building a story from the bits Dusk never claimed to hide.
On Dusk, Phoenix keeps the note economics shielded with zero-knowledge proofs while DuskDS still records the network event around that spend. The amount and note linkage can stay hidden even though the transaction timestamp and permitted metadata still enter public Dusk chain history.
That distinction gets uglier once the observer already knows something off-chain.
A redemption window.
A payroll batch.
An issuer distribution.
Now the Dusk explorer row becomes something an analyst can line up against those off-chain timestamps.
I’ve seen analysts work with less than that. One treasury timestamp, one Dusk explorer row... they’re already checking what lines up.
Very convenient.
Phoenix did its job. The note stayed shielded.
The Dusk metadata row stayed public anyway.
So how much can somebody infer before they ever need the amount?
@Dusk_Foundation
What keeps scratching at me on Dusk isn’t the Phoenix amount.
That part did disappear.
Its the explorer metadata row sitting beside the transfer like some nosy clerk who didn’t get the memo.
Sender hidden. Receiver hidden. Amount hidden. Phoenix note linkage shielded.
Good.
Then transaction still lands in Dusk chain history with public metadata around it.
Not the Phoenix amount.
The transaction around it.
And I can already see where people get lazy with that distinction.
Institution tells the client the transfer was confidential. Analyst opens the Dusk explorer later and still sees that a Phoenix transaction happened, roughly when it happened, maybe fee or transaction metadata the model leaves public.
No balance. No counterparties.
Still... something happened here.
I’d probably start lining timestamps up almost by reflex.
Treasury file says 14:03. Dusk explorer shows a Phoenix transaction around 14:03. Another one twenty minutes later.
Nothing proven.
But now somebody is building a story from the bits Dusk never claimed to hide.
On Dusk, Phoenix keeps the note economics shielded with zero-knowledge proofs while DuskDS still records the network event around that spend. The amount and note linkage can stay hidden even though the transaction timestamp and permitted metadata still enter public Dusk chain history.
That distinction gets uglier once the observer already knows something off-chain.
A redemption window.
A payroll batch.
An issuer distribution.
Now the Dusk explorer row becomes something an analyst can line up against those off-chain timestamps.
I’ve seen analysts work with less than that. One treasury timestamp, one Dusk explorer row... they’re already checking what lines up.
Very convenient.
Phoenix did its job. The note stayed shielded.
The Dusk metadata row stayed public anyway.
So how much can somebody infer before they ever need the amount?
@Dusk_Foundation