#dusk $ACE $BTW $DUSK @Dusk
i keep thinking if my DUSK is already private inside Phoenix, then using that same value with a smart contract should just be more Phoenix.
like okay. encrypted Phoenix notes already hid the transfer side. sender, receiver, amount not sitting there publicly. so if that DUSK now needs to do something inside Rusk, why should the privacy shape have to change at all?
except apparently that is where Zilch starts mattering.
Phoenix already knows how to move DUSK through encrypted notes without turning the sender, receiver and amount into the public shape im used to.
but a smart contract isnt just another receiver.
and thats the bit i kept flattening.
encrypted Phoenix notes solve the private value side. once that DUSK needs to interact with Rusk, Zilch has to carry the private contract side instead of treating Rusk like one more Phoenix receiver.
so wait.
same private DUSK, but not the same job anymore?
Phoenix got the DUSK there privately, but that still isnt the same thing as giving Rusk a private interaction it can actually work with. thats the extra shape Zilch is solving.
which feels kind of backwards because i kept treating privacy like one wrapper around the DUSK.
except apparently the handoff matters too. Phoenix can keep the DUSK private while it moves, Zilch still has to keep the interaction private when that value reaches Rusk.
and i think thats what i was missing. i kept expecting the encrypted Phoenix notes to somehow be enough all the way into Rusk.
apparently getting the DUSK there privately and using it there privately are two different problems.
i keep thinking if my DUSK is already private inside Phoenix, then using that same value with a smart contract should just be more Phoenix.
like okay. encrypted Phoenix notes already hid the transfer side. sender, receiver, amount not sitting there publicly. so if that DUSK now needs to do something inside Rusk, why should the privacy shape have to change at all?
except apparently that is where Zilch starts mattering.
Phoenix already knows how to move DUSK through encrypted notes without turning the sender, receiver and amount into the public shape im used to.
but a smart contract isnt just another receiver.
and thats the bit i kept flattening.
encrypted Phoenix notes solve the private value side. once that DUSK needs to interact with Rusk, Zilch has to carry the private contract side instead of treating Rusk like one more Phoenix receiver.
so wait.
same private DUSK, but not the same job anymore?
Phoenix got the DUSK there privately, but that still isnt the same thing as giving Rusk a private interaction it can actually work with. thats the extra shape Zilch is solving.
which feels kind of backwards because i kept treating privacy like one wrapper around the DUSK.
except apparently the handoff matters too. Phoenix can keep the DUSK private while it moves, Zilch still has to keep the interaction private when that value reaches Rusk.
and i think thats what i was missing. i kept expecting the encrypted Phoenix notes to somehow be enough all the way into Rusk.
apparently getting the DUSK there privately and using it there privately are two different problems.
