#dusk $DUSK @Dusk
I was mid-task digging through Dusk's Phoenix specs and almost skimmed past the note structure...then noticed that transaction metadata such as fees and gas usage can remain visible outside the shielded value transfer.

That's the part that stuck.
The marketing lens is fully confidential transfers — sender information, transferred amount, and the specific notes involved are hidden from ordinary observers through zero-knowledge proofs, with the receiver retaining the relevant information.
But reading it slow, what Phoenix actually delivers is hidden value with public network metadata still hanging off the side.
Fees, gas consumption, and block timing remain observable.

Hold up — that's the opposite of what most privacy threads imply when they say shielded by default.
The assumption is everything disappears.

What actually happens is sensitive financial data hides inside the proof, while the network still sees that someone paid validators at a specific height. The privacy boundary isn't the transaction — it's what the protocol encrypts versus what remains visible for consensus.

Makes me wonder how many confidential transaction narratives quietly assume metadata exposure doesn't matter...

Meanwhile, $MUBARAK , $HEMI and $Tree are also on my radar as I keep digging into different sides of the market.