#dusk @Dusk $AKE
i keep getting stuck on this idea that privacy on Dusk is not really something Phoenix adds after $DUSK already moved
because that was how i was reading it
Moonlight brain basically. public balance moves, sender and receiver exist in the clear, then somehow Phoenix comes later and hides whatever was already sitting there publicly
nice clean mental model
except Phoenix keeps wrecking it
Fine.
Phoenix does not start from a public DUSK balance and cover it later. it starts from encrypted notes, shielded outputs, hidden relationships
a Dusk Phoenix spend can consume encrypted notes, leave nullifiers behind, make new shielded outputs
without first turning that note history into a Moonlight-style account trail for everybody to inspect
the Transfer Contract can still sit underneath DUSK movement. the proof says the spend was valid. the note history still doesnt have to open up
which is honestly where my half asleep brain keeps getting stuck
because if DuskDS can settle the spend, and the Phoenix nullifier is enough to stop that note being spent again, why would the rest of the note history ever need to become public
what exactly am i calling the ledger here
DuskDS?
the Phoenix note set?
the public settlement residue?
all of it somehow?
i think i had this backwards
maybe Phoenix isnt hiding a public financial history at all on Dusk foundation
maybe that public version just never existed underneath it @Dusk_Foundation
#Dusk $EDEN
i keep getting stuck on this idea that privacy on Dusk is not really something Phoenix adds after $DUSK already moved
because that was how i was reading it
Moonlight brain basically. public balance moves, sender and receiver exist in the clear, then somehow Phoenix comes later and hides whatever was already sitting there publicly
nice clean mental model
except Phoenix keeps wrecking it
Fine.
Phoenix does not start from a public DUSK balance and cover it later. it starts from encrypted notes, shielded outputs, hidden relationships
a Dusk Phoenix spend can consume encrypted notes, leave nullifiers behind, make new shielded outputs
without first turning that note history into a Moonlight-style account trail for everybody to inspect
the Transfer Contract can still sit underneath DUSK movement. the proof says the spend was valid. the note history still doesnt have to open up
which is honestly where my half asleep brain keeps getting stuck
because if DuskDS can settle the spend, and the Phoenix nullifier is enough to stop that note being spent again, why would the rest of the note history ever need to become public
what exactly am i calling the ledger here
DuskDS?
the Phoenix note set?
the public settlement residue?
all of it somehow?
i think i had this backwards
maybe Phoenix isnt hiding a public financial history at all on Dusk foundation
maybe that public version just never existed underneath it @Dusk_Foundation
#Dusk $EDEN