#creatorpad $SIGN
SIGN
0.03495
-0.96%
نشر
--
Just found something in the sign protocol docs that i haven't seen anyone discuss publicly, and it's sitting uncomfortably in my head.
The schema struct in sign protocol has a field called revocable. it's a boolean — either attestations built on a given schema can be revoked, or they cannot. that design choice gets made at schema creation time, by the schema registrant. and crucially, once a schema is registered on-chain, the revocable field is fixed. you can't retroactively make a non-revocable schema revocable. that decision is permanent.
Now think about what @signofficial is positioning sign for: national digital ID systems, government credentials, CBDC infrastructure. credential revocation is not an edge case in those contexts. it's a core operational requirement. a passport can be cancelled. a license can be suspended. a benefit eligibility attestation can expire. if a government department or a contractor sets revocable: false when registering a schema — even by mistake, even as a temporary deployment choice — every attestation made under that schema cannot be withdrawn. ever.
The docs describe a workaround: you can issue a new corrective attestation that references the flawed one via linkedAttestationId. that mechanism works for flagging error, but it doesn't delete the original. the incorrect credential still exists on-chain. a verifier reading the raw schema gets the original attestation before the correction unless it explicitly queries for linked revocations.
The whitepaper describes the system as sovereign infrastructure. $SIGN powers the governance layer. but the revocable design means governance begins at schema creation, not after the fact. for governments that are early in deployment, that's the window where permanent decisions are most likely to be made without full awareness of their permanence 🤔
@SignOfficial #SignDigitalSovereignInfra
{future}(SIGNUSDT)
The schema struct in sign protocol has a field called revocable. it's a boolean — either attestations built on a given schema can be revoked, or they cannot. that design choice gets made at schema creation time, by the schema registrant. and crucially, once a schema is registered on-chain, the revocable field is fixed. you can't retroactively make a non-revocable schema revocable. that decision is permanent.
Now think about what @signofficial is positioning sign for: national digital ID systems, government credentials, CBDC infrastructure. credential revocation is not an edge case in those contexts. it's a core operational requirement. a passport can be cancelled. a license can be suspended. a benefit eligibility attestation can expire. if a government department or a contractor sets revocable: false when registering a schema — even by mistake, even as a temporary deployment choice — every attestation made under that schema cannot be withdrawn. ever.
The docs describe a workaround: you can issue a new corrective attestation that references the flawed one via linkedAttestationId. that mechanism works for flagging error, but it doesn't delete the original. the incorrect credential still exists on-chain. a verifier reading the raw schema gets the original attestation before the correction unless it explicitly queries for linked revocations.
The whitepaper describes the system as sovereign infrastructure. $SIGN powers the governance layer. but the revocable design means governance begins at schema creation, not after the fact. for governments that are early in deployment, that's the window where permanent decisions are most likely to be made without full awareness of their permanence 🤔
@SignOfficial #SignDigitalSovereignInfra
{future}(SIGNUSDT)
إخلاء المسؤولية: تتضمن آراء أطراف خارجية. ليست نصيحةً مالية. يُمكن أن تحتوي على مُحتوى مُمول. اطلع على الشروط والأحكام.