Revoked

UCAN revocation is achieved via a Certificate Revocation List expressed as a grow-only prefix trie. It must contain both the revoked UCAN, and be signed by a DID in the proof chain above the target UCAN.
This lives at /revoke/*. For a UCAN to be valid, a validator must construct a proof of non-inclusion, in addition to the UCAN's internal structural checks. A revocation claim contains the following information:
1
data RevocationClaim = RevocationClaim
2
  -- Links
3
  { revoke   :: HardLink UCAN -- UCAN to revoke
4
  , resolved :: HardLink UCAN -- Resolved revoked UCAN
5
  -- Metadata
6
  , revoker  :: DID       -- DID in proof chain
7
  , sig      :: Base64Url -- signRSA(didPK, revokedCID)
8
  }
9
  
10
type RevocationTable = Map (CidOf UCAN) RevocationClaim
Copied!
The revoke and resolved may be the same. We rely on the content addressed hard links to de-deuplcate storage if they're identical. If the original revoked UCAN is Merkle compressed, dereference at least the parts that include the revoker's DID through to the genesis DID.
​

Append

Next - File System

Unlisted

Last modified 1yr ago

Export as PDF

Copy link