···11-//notes we are using the users multibase as the answer here. Explain how to find the did doc and what that key does
22-31Great job beating Part 1! Now onto Part 2.
4255-This will be submitting their public verification code from the did doc since each did doc will have one.
33+You now know how to find your did. But how to do you get things like the PDS url or the public signing key? These are
44+stored on something called a [did document](https://atproto.com/specs/did#did-documents). On atproto there are two valid
55+did's that can be used. [did:plc and did:web](https://atproto.com/specs/did#blessed-did-methods) with each one having a
66+slightly different way to find the did document.
6777-Each one has a unique way to find something called a [DID document](https://atproto.com/specs/did#did-documents). Your
88-did document holds various information about your identity. Things like where does your PDS live, the key that signs
99-your repo, handle, and more.
88+# plc
1091111-explain where to find the did document for each did
1010+The PLC, or Public Ledger of Credentials, is a type of did host by Bluesky PBC currently, with plans to move to
1111+an [independent
1212+entity](https://docs.bsky.app/blog/plc-directory-org). This allows users to sign up for an account on the atmosphere
1313+easily and without prerequisites. The PLC is the authority of the did doc with the popular one
1414+being [https://plc.directory](https://plc.directory/). Access to changing the did doc is by rotation keys which are
1515+either secp256k1 (“k256”) or NIST P-256 (“p256”) public `did:keys` which are set on creation of the did and changed when
1616+using a previous one to sign for the change. Can read more on that [here](https://web.plc.directory/spec/v0.1/did-plc).
12171313-# plc
1414-1515-talk about where to find the PLC
1818+To find the did doc for a `did:plc` you can make a simple web request to `https://plc.directory/{did}`, like
1919+`https://plc.directory/did:plc:vc7f4oafdgxsihk4cry2xpze`. To find the rotation keys or previous revsions you can
2020+append `/log` to the url, `https://plc.directory/did:plc:vc7f4oafdgxsihk4cry2xpze/log`
16211722# did:web
18231919-talk about how to find your did:web (altho you probably already know this)
2424+With `did:web` the domain of the did is the authority of the did doc, and you can find it via
2525+`https://{did:web}/.well-known/did.json`.
2626+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
2727+rotation keys since the proof is in the control of the domain and exposing the doc at the url.
20282121-Keeping it simple proof of concept, blah, blah will have a real one here another time. Add a new field `partTwo` to the
2222-record with the value `{{code}}`
2929+# The doc
23303131+The did doc itself is much the same for both did types. It holds important information like. The user's handle, the
3232+signing key (verificationMethod with the users did), and the PDS url (the `#atproto_pds` service). Can read more about
3333+the
3434+did doc [here](https://atproto.com/specs/did#did-documents).
24352525-[//]: # (<input type="file" id="part_one_input" placeholder="Enter your code here" />)3636+```json
3737+{
3838+ "@context": [
3939+ "https://www.w3.org/ns/did/v1",
4040+ "https://w3id.org/security/multikey/v1",
4141+ "https://w3id.org/security/suites/secp256k1-2019/v1"
4242+ ],
4343+ "id": "did:plc:vc7f4oafdgxsihk4cry2xpze",
4444+ "alsoKnownAs": [
4545+ "at://jcsalterego.bsky.social"
4646+ ],
4747+ "verificationMethod": [
4848+ {
4949+ "id": "did:plc:vc7f4oafdgxsihk4cry2xpze#atproto",
5050+ "type": "Multikey",
5151+ "controller": "did:plc:vc7f4oafdgxsihk4cry2xpze",
5252+ "publicKeyMultibase": "zQ3shTnCYJAav9LgJrRWt81qiW2uKArPQNiNP62igctKXCQh9"
5353+ }
5454+ ],
5555+ "service": [
5656+ {
5757+ "id": "#atproto_pds",
5858+ "type": "AtprotoPersonalDataServer",
5959+ "serviceEndpoint": "https://shiitake.us-east.host.bsky.network"
6060+ }
6161+ ]
6262+}
6363+6464+6565+```
6666+6767+To complete this challenge. Enter your did's `publicKeyMultibase` from your did doc into the text box below.