i see $AKE and $TUT but then i see notification about Dusk.
i keep thinking the weird part of Dusk is not even that Phoenix hides a shielded DUSK transfer.
it’s that Phoenix and Moonlight almost disagree on what “spending DUSK” even means.
same native DUSK. same DuskDS. but one spend leaves behind evidence the other side doesn’t even think in.
Moonlight feels normal enough when you’re half awake. Moonlight account. public DUSK balance. sequential nonce. spend again, nonce moves again. okay fine. my brain knows this shape.
then Phoenix basically says forget the account balance for a second.
you have encrypted notes.
and a Dusk Phoenix spend isn’t really “subtract this amount from my account.” it consumes Phoenix notes, creates new outputs, leaves nullifiers behind so DuskDS knows those inputs cannot come alive twice.
so what am i actually calling a spend here?
same DUSK moving... but is DuskDS even remembering the same kind of event?
Moonlight keeps asking about an account and an account+nonce spending ID.
Phoenix keeps asking whether this note already died through its nullifier.
“same DUSK. different evidence.”
and somehow both still have to become valid DUSK movement through the Transfer Contract, which honestly makes it weirder not cleaner.
because if one side remembers account order and the other remembers dead notes... what exactly does “public versus private” explain?
idk. suddenly that phrase feels way too neat.
Dusk Phoenix didn’t just put darkness over Moonlight accounting
“privacy changed the bookkeeping.”
maybe that’s what was bothering me.
DuskDS has to remember a different kind of evidence once that DUSK moves.
#dusk $DUSK @Dusk
i keep thinking the weird part of Dusk is not even that Phoenix hides a shielded DUSK transfer.
it’s that Phoenix and Moonlight almost disagree on what “spending DUSK” even means.
same native DUSK. same DuskDS. but one spend leaves behind evidence the other side doesn’t even think in.
Moonlight feels normal enough when you’re half awake. Moonlight account. public DUSK balance. sequential nonce. spend again, nonce moves again. okay fine. my brain knows this shape.
then Phoenix basically says forget the account balance for a second.
you have encrypted notes.
and a Dusk Phoenix spend isn’t really “subtract this amount from my account.” it consumes Phoenix notes, creates new outputs, leaves nullifiers behind so DuskDS knows those inputs cannot come alive twice.
so what am i actually calling a spend here?
same DUSK moving... but is DuskDS even remembering the same kind of event?
Moonlight keeps asking about an account and an account+nonce spending ID.
Phoenix keeps asking whether this note already died through its nullifier.
“same DUSK. different evidence.”
and somehow both still have to become valid DUSK movement through the Transfer Contract, which honestly makes it weirder not cleaner.
because if one side remembers account order and the other remembers dead notes... what exactly does “public versus private” explain?
idk. suddenly that phrase feels way too neat.
Dusk Phoenix didn’t just put darkness over Moonlight accounting
“privacy changed the bookkeeping.”
maybe that’s what was bothering me.
DuskDS has to remember a different kind of evidence once that DUSK moves.
#dusk $DUSK @Dusk
