Skip to content

Commit fa1f6cc

Browse files
authored
Update README.md
1 parent fc53cb4 commit fa1f6cc

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

resolver/README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,8 @@ To resolve a `did:cel` identifier, a resolver MUST perform the following steps:
1818
2. Extract `didDocument` from the create event.
1919
3. The `didDocument.id` and `didDocument.assertionMethod.controller` fields MUST exactly match the `did:cel` which is being resolved.
2020
4. Recreate `initialDidDocument` by removing the `id` and `assertionMethod.controller` fields from the `didDocument`
21-
5. Perform `multihash(sha3-256(JCS(initialDidDocument)))`. The result value MUST exactly match the `initialDidDocumentHash` extracted from the DID.
21+
5. Compute `multihash(sha3-256(JCS(initialDidDocument)))`. The result value MUST exactly match the `initialDidDocumentHash` extracted from the DID.
22+
6. Verify create event integrity
2223
5. Verify Integrity: Iterate through subsequent events ($E_n \dots E_0$), in reverse chronological order, starting with the newest entry, allowing previous verification to be reused if already cached or computed as needed. For each event, verify that:
2324
- For $E_n$ where $n \gt 1$, the `previousEventHash` MUST match the `sha3-256` hash of the previous event's document hash.
2425
- The event is signed by a key authorized in the state established by the previous event.

0 commit comments

Comments
 (0)