Register did:julia - #748
Open
fizpawiz wants to merge 1 commit into
Open
Conversation
fizpawiz
requested review from
KDean-Dolphin,
MizukiSonoko,
Steffytan,
adam-burns,
ajile-in,
apuchitnis,
gatemezing,
genaris,
msporny,
ottomorac,
rajivrajani,
stenreijers,
swcurran and
wip-abramson
as code owners
August 26, 2026 20:37
🤖 AI Preliminary Specification ReviewThis is an advisory, automated review of the DID Method specification(s) referenced in this pull request, checked against the registration checklist. It does not replace review by the registry editors.
|
| Item | Level | Status | Notes | |
|---|---|---|---|---|
| ✅ | M1. Specification reachable and is a DID Method spec | MUST | pass | |
| ✅ | M2. DID Method Syntax is defined | MUST | pass | |
| ✅ | M3. CRUD operations are defined | MUST | pass | |
| ✅ | M4. Security Considerations present and substantive | MUST | pass | |
| ✅ | M5. Privacy Considerations present and substantive | MUST | pass | |
| ✅ | M6. Method name indicative and non-generic | MUST | pass | |
| ✅ | M7. No unreasonable harms | MUST | pass | |
| ✅ | M8. Human-readable description | MUST | pass | |
| ✅ | S1. contactEmail present | OPTIONAL | pass | |
| ✅ | S2. verifiableDataRegistry present | OPTIONAL | pass | |
| ✅ | S3. IP posture clear | SHOULD | pass |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR registers
did:julia, a DID method rooted in Chia blockchain singletons.Specification: https://github.com/julia-social/did-julia/blob/v1.0.0/spec/did-julia.md
A
did:juliaidentifier is the base58 encoding of a Chia singleton launcher ID. The launcher ID commits to the DID's original BLS12-381 authentication key, so a DID's full key history is verifiable from genesis and signatures stay verifiable across key rotation. Current DID state — authentication configuration, custodians, recovery configuration, and credential revocation — is read from the chain by any Chia node, with no issuer or provider on the verification path.The specification is self-contained and covers method syntax (§5), CRUD operations (§7), DID Documents (§8), the Verifiable Credentials 2.0 mapping (§9), Security Considerations (§10), and Privacy Considerations (§11).
One capability is specified and not yet implemented, and is flagged as such in the specification (§7.2, §12): the publication path that writes DID Document contents to Chia DataLayer and resolves them for readers. The DID singleton's document-pointer mechanism is shipped, and a
did:juliaDID is usable without a DID Document lookup, as the only required element of a DID Document is the DID value itself.On-chain reference implementation (Chialisp, Apache 2.0): https://github.com/julia-social/julia_did_chialisp
Reference resolver (Python, Apache 2.0, in the specification repository): https://github.com/julia-social/did-julia