#dusk $ACE $PORTAL $DUSK @Dusk
What keeps bothering me on Dusk foundation isn’t the Citadel license.
Not really.
It's the trusted License Provider list sitting one layer later on Dusk. Enough authority to make that license useless without touching license itself.
Fine.
Investor clears the off-chain check. License Provider signs the Citadel credential. Registered. ZK proof still verifies. Dusk Citadel session still looks fine.
Then the Dusk Service Provider removes that LP from its trusted list.
And thats where the clean state starts lying by omission.
Because the Citadel license did not fail.
The proof did not fail.
Service Provider just stopped accepting the License Provider that issued it.
I'd been treating "registered credential" like it should carry farther than that.
Too generous.
On Dusk I can't treat credential validity and Service Provider acceptance as one state. Citadel can keep proving the LP-signed license. Then the trusted-LP list gets another say when the next Dusk Service Provider action arrives.
Same credential.
Different answer.
Very calm little split.
The investor comes back with the same wallet, same license, same proof path. Session verifies. Then the next Dusk Service Provider action hits the current trusted-LP check.
Rejected.
Now the investor may need a fresh credential from an LP the Service Provider still accepts.
Old Citadel license?
Still verifying.
Nothing cryptographic broke.
Which is somehow more annoying.
I know where my eyes would go first. Back to the license, checking for a failure that isn’t there. lovely.
Nice use of time.
The Dusk state that matters now is the trusted-LP list.
List moves. Next Service Provider action dies. Citadel credential still intact.
So when did the license actually stop being useful?
When the credential failed?
Or when the Dusk Service Provider stopped trusting who signed it?.
@Dusk_Foundation #Dusk
What keeps bothering me on Dusk foundation isn’t the Citadel license.
Not really.
It's the trusted License Provider list sitting one layer later on Dusk. Enough authority to make that license useless without touching license itself.
Fine.
Investor clears the off-chain check. License Provider signs the Citadel credential. Registered. ZK proof still verifies. Dusk Citadel session still looks fine.
Then the Dusk Service Provider removes that LP from its trusted list.
And thats where the clean state starts lying by omission.
Because the Citadel license did not fail.
The proof did not fail.
Service Provider just stopped accepting the License Provider that issued it.
I'd been treating "registered credential" like it should carry farther than that.
Too generous.
On Dusk I can't treat credential validity and Service Provider acceptance as one state. Citadel can keep proving the LP-signed license. Then the trusted-LP list gets another say when the next Dusk Service Provider action arrives.
Same credential.
Different answer.
Very calm little split.
The investor comes back with the same wallet, same license, same proof path. Session verifies. Then the next Dusk Service Provider action hits the current trusted-LP check.
Rejected.
Now the investor may need a fresh credential from an LP the Service Provider still accepts.
Old Citadel license?
Still verifying.
Nothing cryptographic broke.
Which is somehow more annoying.
I know where my eyes would go first. Back to the license, checking for a failure that isn’t there. lovely.
Nice use of time.
The Dusk state that matters now is the trusted-LP list.
List moves. Next Service Provider action dies. Citadel credential still intact.
So when did the license actually stop being useful?
When the credential failed?
Or when the Dusk Service Provider stopped trusting who signed it?.
@Dusk_Foundation #Dusk