+4 -4

shared/challenges_markdown/one/part_two.md

reviewed

··· 5 5 did's that can be used. [did:plc and did:web](https://atproto.com/specs/did#blessed-did-methods) with each one having a 6 6 slightly different way to find the did document. 7 7 8 8 - # plc 8 8 + ## plc 9 9 10 10 The PLC, or Public Ledger of Credentials, is a type of did host by Bluesky PBC currently, with plans to move to 11 11 an [independent ··· 19 19 `https://plc.directory/did:plc:vc7f4oafdgxsihk4cry2xpze`. To find the rotation keys or previous revsions you can 20 20 append `/log` to the url, `https://plc.directory/did:plc:vc7f4oafdgxsihk4cry2xpze/log` 21 21 22 22 - # did:web 22 22 + ## did:web 23 23 24 24 With `did:web` the domain of the did is the authority of the did doc, and you can find it via 25 25 `https://{did:web}/.well-known/did.json`. 26 26 An example would be the `did:web:didd.uk` with it's did doc found at https://didd.uk/.well-known/did.json. There are no 27 27 rotation keys since the proof is in the control of the domain and exposing the doc at the url. 28 28 29 29 - # The doc 29 29 + ## The doc 30 30 31 31 The did doc itself is much the same for both did types. It holds important information like. The user's handle, the 32 32 signing key (verificationMethod with the users did), and the PDS url (the `#atproto_pds` service). Can read more about ··· 64 64 65 65 ``` 66 66 67 67 - To complete this challenge. Enter your did's `publicKeyMultibase` from your did doc into the text box below. 67 67 + To complete this challenge. Enter your did's `publicKeyMultibase` from your did doc into the text box below.

+1 -1

web/src/main.rs

reviewed

··· 74 74 // Scope::Known(KnownScope::TransitionGeneric), 75 75 //This looks like it HAS to have the full collection name, before i want to say it worked with wildcard 76 76 //Gives full CRUD to the codes.advent.* collection 77 77 - Scope::Unknown("repo:codes.advent.test".to_string()), 77 77 + // Scope::Unknown("repo:codes.advent.test".to_string()), 78 78 ] 79 79 } 80 80