#dusk @Dusk $BTW $DUSK
The holder-report row is what keeps getting under my skin on Dusk.
Not Zedger transfer.
That part already cleared.
DuskVM executed it. DuskDS finalized it. Phoenix already has newer Phoenix holder evidence sitting behind shielded state.
Fine.
Then issuer holder-report checkpoint is still one step behind.
Thats the annoying part.
Issuer ops pulls the Dusk holder extract. row is old. Rusk already has finalized Zedger move. RUES can surface it. Nobody notices until the selective-disclosure request is already being prepared.
My eyes keep going back to issuer extract. Looks current enough. Then Rusk shows Dusk Zedger move finalized beyond the holder-report checkpoint.
Nothing broke.
checkpoint is just late enough to contaminate the next corporate-action run.
Auditor opens Dusk issuer extract and asks for Phoenix holder evidence behind that row.
row is stale.
Phoenix has already moved on.
Now Phoenix viewing key is being asked to prove a holder row that sits behind the current DuskDS finalized height.
Nice.
On Dusk, DuskDS can already be final while Phoenix keeps new holder evidence shielded. Rusk has the finalized Zedger history. RUES can surface the move. None of that forces the issuer’s holder-report checkpoint to advance before the next selective-disclosure request is built.
So DuskDS can be current while the issuer is still asking Phoenix to prove yesterday’s holder row.
Then corporate-action snapshot starts from that stale extract.
The Dusk payout file inherits the stale row and the Phoenix audit view gets built around it.
And suddenly Phoenix holder evidence and issuer report are not describing the same DuskDS finalized height anymore.
Thats where I keep getting stuck.
Valid Phoenix proof.
Valid issuer row.
Different DuskDS height.
Dusk Zedger move is already in finalized DuskDS history.
The holder-report checkpoint still isn’t there.
Which one does issuer actually act on?
@Dusk_Foundation DuskDS finalized height? Current.
Issuer holder row? Already behind.
#Dusk
The holder-report row is what keeps getting under my skin on Dusk.
Not Zedger transfer.
That part already cleared.
DuskVM executed it. DuskDS finalized it. Phoenix already has newer Phoenix holder evidence sitting behind shielded state.
Fine.
Then issuer holder-report checkpoint is still one step behind.
Thats the annoying part.
Issuer ops pulls the Dusk holder extract. row is old. Rusk already has finalized Zedger move. RUES can surface it. Nobody notices until the selective-disclosure request is already being prepared.
My eyes keep going back to issuer extract. Looks current enough. Then Rusk shows Dusk Zedger move finalized beyond the holder-report checkpoint.
Nothing broke.
checkpoint is just late enough to contaminate the next corporate-action run.
Auditor opens Dusk issuer extract and asks for Phoenix holder evidence behind that row.
row is stale.
Phoenix has already moved on.
Now Phoenix viewing key is being asked to prove a holder row that sits behind the current DuskDS finalized height.
Nice.
On Dusk, DuskDS can already be final while Phoenix keeps new holder evidence shielded. Rusk has the finalized Zedger history. RUES can surface the move. None of that forces the issuer’s holder-report checkpoint to advance before the next selective-disclosure request is built.
So DuskDS can be current while the issuer is still asking Phoenix to prove yesterday’s holder row.
Then corporate-action snapshot starts from that stale extract.
The Dusk payout file inherits the stale row and the Phoenix audit view gets built around it.
And suddenly Phoenix holder evidence and issuer report are not describing the same DuskDS finalized height anymore.
Thats where I keep getting stuck.
Valid Phoenix proof.
Valid issuer row.
Different DuskDS height.
Dusk Zedger move is already in finalized DuskDS history.
The holder-report checkpoint still isn’t there.
Which one does issuer actually act on?
@Dusk_Foundation DuskDS finalized height? Current.
Issuer holder row? Already behind.
#Dusk