#signdigitalsovereigninfra $SIGN I spent way too long thinking revoke was broken.
Nothing failed.
Nothing reverted.
Nothing even looked wrong.
The credential was still there, still valid, like I had never called anything at all.
At first I thought I grabbed the wrong record.
So I ran it again. Same result.
Then I started checking everything one by one.
The attester matched.
The schema pointed somewhere else.
I tried revoking from the attester side again. Still nothing.
Then I switched and called it from the schema side.
That’s when it finally worked.
And honestly, that was the real surprise.
The one creating the credential wasn’t the one who could shut it off.
I tested another credential after that. Same pattern.
One side could issue.
The other side had the actual control.
From the outside, it looks like the issuer is in charge.
But under the hood, revocation lives somewhere else.
That changes the question for me.
It’s not just “can this be revoked?”
It’s “when something needs to be turned off quickly, who actually has the power to do it?”
@SignOfficial #SignDigitalSovereignInfra $SIGN
