#dusk $ROBO $CYS $DUSK
Okay so, part of Dusk that keeps bothering me isn't Moonlight.
Not even Phoenix.
Its Transfer contract making both look like same settlement problem...until treasury tries to reconcile them.
Fine.
Moonlight settles through DuskDS and leaves public account state behind. Sender, recipient, amount.Treasury reads row, matches it, closes.
Then Phoenix lands through same Dusk settlement layer.
Different morning.
Encrypted note.Shielded amount.Proof. No equivalent public balance row for the reconciliation file.
I'd been treating same DuskDS finality like it should buy back office one reconciliation habit.
That was optimistic.
On Dusk Transfer contract can route both models into same settlement layer without flattening what each model exposes afterward. Lovely... Moonlight gives treasury account state. Phoenix can be fully finalized while amount still sits behind viewing authority and selective disclosure.
Same chain state.
Different mess desk can actually close against.
One line in treasury file closes from Dusk's Moonlight state.
Phoenix line stays open.
And then... right. Somebody needs viewing authority. Or an internal record tying the note to amount. Maybe selective disclosure for this transfer. Maybe. Depends what file actually needs.
DuskDS is not waiting.
Treasury is.
Very efficient. chain finished before spreadsheet did.
I've seen teams make mistake. One rail, one reconciliation habit. Sounds reasonable until Phoenix leaves one line waiting on a view.
On Dusk, DuskDS can finish both transfers and treasury still be holding two completely different bits to reconcile against. Moonlight gives it the public account trail. Phoenix leaves second line dependent on the note-side view.
Good.
I'd still check DuskDS twice before admitting chain isnt what left Phoenix line open.
Which is dumb, exactly how clean finality rows fool you.
Thats the bruise.
Same DuskDS finality.
Dusk foundation Moonlight line closed.
Phoenix still waiting on a view.
what exactly was "same settlement" on @Dusk_Foundation supposed to make same?
Okay so, part of Dusk that keeps bothering me isn't Moonlight.
Not even Phoenix.
Its Transfer contract making both look like same settlement problem...until treasury tries to reconcile them.
Fine.
Moonlight settles through DuskDS and leaves public account state behind. Sender, recipient, amount.Treasury reads row, matches it, closes.
Then Phoenix lands through same Dusk settlement layer.
Different morning.
Encrypted note.Shielded amount.Proof. No equivalent public balance row for the reconciliation file.
I'd been treating same DuskDS finality like it should buy back office one reconciliation habit.
That was optimistic.
On Dusk Transfer contract can route both models into same settlement layer without flattening what each model exposes afterward. Lovely... Moonlight gives treasury account state. Phoenix can be fully finalized while amount still sits behind viewing authority and selective disclosure.
Same chain state.
Different mess desk can actually close against.
One line in treasury file closes from Dusk's Moonlight state.
Phoenix line stays open.
And then... right. Somebody needs viewing authority. Or an internal record tying the note to amount. Maybe selective disclosure for this transfer. Maybe. Depends what file actually needs.
DuskDS is not waiting.
Treasury is.
Very efficient. chain finished before spreadsheet did.
I've seen teams make mistake. One rail, one reconciliation habit. Sounds reasonable until Phoenix leaves one line waiting on a view.
On Dusk, DuskDS can finish both transfers and treasury still be holding two completely different bits to reconcile against. Moonlight gives it the public account trail. Phoenix leaves second line dependent on the note-side view.
Good.
I'd still check DuskDS twice before admitting chain isnt what left Phoenix line open.
Which is dumb, exactly how clean finality rows fool you.
Thats the bruise.
Same DuskDS finality.
Dusk foundation Moonlight line closed.
Phoenix still waiting on a view.
what exactly was "same settlement" on @Dusk_Foundation supposed to make same?