Project · identity
hcdeepid
- How you run it
- not recorded
- Holochain version
- 0.6.1
- Activity
- maintained
- Checked
- 29 October 2026
What is hcdeepid and what is it for?
hcdeepid is a reusable piece of Holochain code that keeps a person's profile, avatar and permissions consistent when they sign in from more than one device. Instead of treating each device's key as a separate identity, it anchors the shared identity to an ID issued by an existing login system, such as a Django or OAuth backend.
hcdeepid was separated out of the account zome of NFB Den, a project where authors and publishers agree publishing contracts. That contract work needed to know which real-world person had agreed to a deal rather than which device happened to sign, and the identity problem underneath it kept turning up on its own, so it was pulled out as a reusable part.
In Holochain, every device or browser a person uses gets its own key. If an app ties profiles and permissions straight to those keys, one person signing in on two devices looks like two different people. hcdeepid instead treats an ID from an existing login system as the source of truth, and stores the parts that should be shared — which avatar is current, how the profile is found — against that ID, while each device still keeps its own keys and history.
It is meant to be pulled into an existing Holochain workspace as a path dependency rather than run on its own; the maintainer describes it as an early extraction that is not yet published as a standalone crate. The repository explains the pattern and the install steps at github.com/Nuruddindev/hc_deepid.
How to get it
As a library
- Add the repository to your Holochain workspace as a git submodule under vendor/hc_deepid (git submodule add https://github.com/<you>/hc_deepid vendor/hc_deepid), or copy it in if you do not need to track upstream changes.
- Point your workspace Cargo.toml dependency entries at vendor/hc_deepid/zomes/coordinator/account and vendor/hc_deepid/zomes/integrity/account.
- Register the account and account_integrity zomes in your DNA.
Source: https://raw.githubusercontent.com/Nuruddindev/hc_deepid/main/README.md
Questions people ask
- Is hcdeepid a standalone app I install, or a component I add to a project?
- It is a component. The README says it is meant to be pulled into an existing workspace as a path dependency, that it is not a scaffolding template you invoke with hc scaffold --template, and that it is not yet published as a standalone crate. source
- How does it relate to Holochain's DeepKey?
- The README treats them as answering different questions: DeepKey tracks whether a given key is currently valid, revoked or replaced, while hcdeepid is described as resolving many device keys back to one durable identity issued by an external authority. The README describes them as complementary rather than competing. source
- Does hcdeepid require a Django backend?
- Django is the case the project was extracted from, not a requirement — the shared state is anchored to an external identity ID. The README lists a Django-side adapter (holodjango_deepid) as in progress, with adapters for other stacks such as JavaScript and PHP listed as planned. source
From 2 public sources, checked 23 September 2026.
Try hcdeepid
- Code on GitHubOpen on GitHub ↗Last change 25 July 2026.
- ReleaseNo GitHub release recorded.
- The project's own files do not say how it is run.
Details & sources
- Source
- Nuruddindev/hc_deepid
Evidence
- Last change
- api.github.com/repos/Nuruddindev/hc_deepidlisted by a third party · seen since 20 October 2026 · github.repository@1
- Activity
- api.github.com/repos/Nuruddindev/hc_deepidlisted by a third party · seen since 24 October 2026 · liveness@1
Compatibility
- hdk
- 0.6.1 · Cargo.toml @ b6fc764
- hdi
- 0.7.1 · Cargo.toml @ b6fc764
- holochain-client
- —
- happ.yaml
- absent
- web-happ.yaml
- absent