Must Read it blog
نشر
SilverFalconX
·
--
#dusk $AKE $ACE
The Dusk foundation's Phoenix viewing key looks harmless right up until I stop thinking of it as "view access."
That label is doing a lot of work.
Issuer grants it for one reporting job. Auditor needs to reconcile a Dusk Phoenix transfer, maybe verify amount, maybe counterparties. Fine. DuskDS already settled state change, Phoenix kept note data shielded from everyone else, and selective disclosure opens enough of that mess to make the report possible.
Except the key does not care why it was handed over.
Thats part that keeps scraping at me.
I'd been treating audit request and the viewing authority like they had the same lifecycle. Took me a second.
They don't.
The report ends. Phoenix viewing authority can still exist.
And now Dusk's infra split gets uglier. Public observers still cannot reconstruct the shielded transfer graph. Good. That was the point.
But the auditor holding the viewing key may still be able to read whatever slice of Phoenix state that authority exposes after the original reporting job is already dead.
The PDF gets signed off.
The Dusk viewing authority does not magically expire with it.
Then legal asks what was disclosed? Compliance asks whether the same key can be reused? Custody asks who still has it?
Nobody cares about DuskDS finality anymore. That finished ages ago.
live problem is one Phoenix viewing authority hanging around after its reason for existing already disappeared.
Very tidy permission lifecycle.
I caught myself thinking revocation fixes it on Dusk foundation.
Then, no.
key can stop working later. Whatever Phoenix data already landed in the auditor's reconciliation file does not climb back into shielded note because someone changed permission afterward.
Dusk can close the next authorized view.
It cannot make the previous one un-happen.
That's why viewing key bothers me more than the transfer.
Phoenix notes stayed private from everyone else.
audit ended.
Who still has Phoenix viewing authority?
And what, exactly, did @Dusk already let them see? . coin ..
#Dusk $DUSK
The Dusk foundation's Phoenix viewing key looks harmless right up until I stop thinking of it as "view access."
That label is doing a lot of work.
Issuer grants it for one reporting job. Auditor needs to reconcile a Dusk Phoenix transfer, maybe verify amount, maybe counterparties. Fine. DuskDS already settled state change, Phoenix kept note data shielded from everyone else, and selective disclosure opens enough of that mess to make the report possible.
Except the key does not care why it was handed over.
Thats part that keeps scraping at me.
I'd been treating audit request and the viewing authority like they had the same lifecycle. Took me a second.
They don't.
The report ends. Phoenix viewing authority can still exist.
And now Dusk's infra split gets uglier. Public observers still cannot reconstruct the shielded transfer graph. Good. That was the point.
But the auditor holding the viewing key may still be able to read whatever slice of Phoenix state that authority exposes after the original reporting job is already dead.
The PDF gets signed off.
The Dusk viewing authority does not magically expire with it.
Then legal asks what was disclosed? Compliance asks whether the same key can be reused? Custody asks who still has it?
Nobody cares about DuskDS finality anymore. That finished ages ago.
live problem is one Phoenix viewing authority hanging around after its reason for existing already disappeared.
Very tidy permission lifecycle.
I caught myself thinking revocation fixes it on Dusk foundation.
Then, no.
key can stop working later. Whatever Phoenix data already landed in the auditor's reconciliation file does not climb back into shielded note because someone changed permission afterward.
Dusk can close the next authorized view.
It cannot make the previous one un-happen.
That's why viewing key bothers me more than the transfer.
Phoenix notes stayed private from everyone else.
audit ended.
Who still has Phoenix viewing authority?
And what, exactly, did @Dusk already let them see? . coin ..
#Dusk $DUSK
إخلاء مسؤولية: يتضمن آراء جهات خارجية. لا تُعدّ نصيحة. يُمكن استخدام Binance AI دون أي ضمان. اطلع على الشروط والأحكام.