Skip to content

Correct the K-256 reference #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
toderash merged 1 commit into from
Apr 26, 2026
+1 −1
Merged

Correct the K-256 reference #60

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/implementing/repository.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Creating a PLC DID requires the creation of at least two cryptographic keys: a r

Repositories should generally control both of these keys, and allow a user to provide the public key for their own rotation key. In the PLC directory, "earlier" rotation keys can override "later" ones (i.e. those first in the list can override any key after it), so the user's rotation key should be placed first. This allows them to override any erroneous operations if needed.

Rotation keys must use ECDSA, with either a NIST P-256 (secp256r1/prime256v1) or NIST K-256 (secp256k1) key. We recommend the use of K-256, as most implementations using the PLC directory use it.
Rotation keys must use ECDSA, with either a K-256 (secp256k1) or NIST P-256 (secp256r1/prime256v1) key. We recommend the use of K-256, as most implementations using the PLC directory use it.

Note that keys must use the low-S form of the key, and must be encoded in compact (IEEE-P1363) form. This ensures keys are stored in canonical form, and prevents key confusion attacks.

Expand Down
Loading