#dusk $DUSK @Dusk $APR
i keep thinking Moonlight and Phoenix should almost feel like two different kinds of DUSK
because Moonlight is easy for my brain
Moonlight account. public DUSK balance. Moonlight sender there, receiver there, transfer amount there, sequential nonce moving forward
normal enough
then Phoenix is like no actually forget that whole shape
DUSK lives through encrypted Phoenix notes. spending means consuming those notes, leaving Phoenix nullifiers behind, making new shielded outputs. no Moonlight public account state sitting there for everyone to follow
fine
except both still end up at the same Transfer Contract
and thats where my brain starts doing the morning thing
because what exactly is the Transfer Contract treating as the same here
Moonlight brings account-based DUSK
Phoenix brings note-based DUSK
one side changes a public DUSK balance
the other consumes shielded notes and leaves nullifiers so the same DUSK cant quietly move twice
same native DUSK apparently. same DuskDS settlement underneath it
but Moonlight is still moving a balance and nonce while Phoenix is burning through notes and leaving nullifiers behind
i think i was still assuming privacy only changed visibility
maybe thats the part i had wrong
Phoenix isnt taking Moonlight DUSK and making it private
the DUSK was already living as notes before the Transfer Contract ever had to make sense of the spend
same DUSK
one Moonlight account
one Phoenix note set
and somehow DuskDS still has to settle both without pretending they were ever the same shape @Dusk_Foundation
#Dusk $AKE
i keep thinking Moonlight and Phoenix should almost feel like two different kinds of DUSK
because Moonlight is easy for my brain
Moonlight account. public DUSK balance. Moonlight sender there, receiver there, transfer amount there, sequential nonce moving forward
normal enough
then Phoenix is like no actually forget that whole shape
DUSK lives through encrypted Phoenix notes. spending means consuming those notes, leaving Phoenix nullifiers behind, making new shielded outputs. no Moonlight public account state sitting there for everyone to follow
fine
except both still end up at the same Transfer Contract
and thats where my brain starts doing the morning thing
because what exactly is the Transfer Contract treating as the same here
Moonlight brings account-based DUSK
Phoenix brings note-based DUSK
one side changes a public DUSK balance
the other consumes shielded notes and leaves nullifiers so the same DUSK cant quietly move twice
same native DUSK apparently. same DuskDS settlement underneath it
but Moonlight is still moving a balance and nonce while Phoenix is burning through notes and leaving nullifiers behind
i think i was still assuming privacy only changed visibility
maybe thats the part i had wrong
Phoenix isnt taking Moonlight DUSK and making it private
the DUSK was already living as notes before the Transfer Contract ever had to make sense of the spend
same DUSK
one Moonlight account
one Phoenix note set
and somehow DuskDS still has to settle both without pretending they were ever the same shape @Dusk_Foundation
#Dusk $AKE