How do I run Omni-ID?

The repository documents two routes: run the bundled web client against a local conductor using the steps in docs/RUNNING_LOCALLY.md, or pack a .webhapp and open it in the Holochain Launcher, which serves the interface locally and handles the conductor connection and zome-call signing.

What stops someone from faking a reputation score?

A rating has to reference an interaction record that was counter-signed by both participants, and the reputation zome loads that record and rejects the claim when the proof does not hold. The project's status notes record a passing test for rejecting a rating with fake evidence.

Is there a mobile app?

Not yet. docs/ANDROID.md is a roadmap for wrapping the same web-hApp for Android, and for desktop, with Tauri 2 and the p2p-shipyard plugin so a conductor runs on the device; it describes a large, still-maturing toolchain rather than a finished build.

Project · identity and reputation

Omni-ID

Name: Omni-ID
Author: Polymorph225

a tool for identity and reputationSovereign identity & cross-platform reputation protocol on Holochain

Explore this project All projects

How you run it: not recorded
Holochain version: 0.6.1
Activity: maintained
Checked: 29 October 2026

What is Omni-ID and what is it for?

Omni-ID is a Holochain project for identity and reputation, where people keep their own profile data and build a trust score out of interactions that both sides sign. It exists so that trust between people can be recorded and checked without a central service deciding who is credible.

Omni-ID is a project for sovereign identity and reputation on Holochain. Its documentation states the aim plainly: a person holds their own identity data, and a reputation score is built from interactions that both sides sign, with no central server deciding who is trustworthy. The design splits a trust system into three parts — who you are, what happened between two people, and what others say about it — and implements each as a separate zome inside one DNA.

The working idea is proof before opinion. Two people who have dealt with each other counter-sign a record of that interaction, and only then can either of them rate it; a rating that cannot point at such a record is rejected, so a score cannot be manufactured from invented reviews. Ratings are weighted by how credible the rater is and fade over time, which the project's design notes describe as raising the cost of creating many identities to inflate a score.

The project's own status notes say this full path — profile, two-agent interaction, rating and aggregated score — is exercised by its test suite, including a case where a rating backed by fake evidence is turned down. To try it, docs/RUNNING_LOCALLY.md walks through building the app, starting a local conductor and connecting the bundled web client to create a profile and read a score; docs/ARCHITECTURE.md explains the zome design and how a score is computed.

How to get it

In a browser

Enter the development shell and build the app bundle: nix develop, then npm install and npm run build:happ, which produces workdir/omni-id.happ.
Start a local conductor with the app installed (hc sandbox generate, then run), attach an app interface on a port and issue an authentication token over the admin interface.
Run the web client from the ui/ directory and connect it using the app WebSocket URL, the token, and the admin WebSocket URL, then open the Profile tab and create a profile.

Source: https://github.com/Polymorph225/omni-id/blob/main/docs/RUNNING_LOCALLY.md

Through the Holo Web Conductor

Build the web-hApp with npm run build:webhapp, which packs the app and UI into workdir/omni-id.webhapp.
Open that bundle in the Holochain Launcher, which serves the UI locally, starts the conductor and handles zome-call signing.
No URL or token entry is needed in this setup: the client detects the Launcher environment and connects automatically.

Source: https://github.com/Polymorph225/omni-id/blob/main/docs/RUNNING_LOCALLY.md

Questions people ask

How do I run Omni-ID?: The repository documents two routes: run the bundled web client against a local conductor using the steps in docs/RUNNING_LOCALLY.md, or pack a .webhapp and open it in the Holochain Launcher, which serves the interface locally and handles the conductor connection and zome-call signing. source
What stops someone from faking a reputation score?: A rating has to reference an interaction record that was counter-signed by both participants, and the reputation zome loads that record and rejects the claim when the proof does not hold. The project's status notes record a passing test for rejecting a rating with fake evidence. source
Is there a mobile app?: Not yet. docs/ANDROID.md is a roadmap for wrapping the same web-hApp for Android, and for desktop, with Tauri 2 and the p2p-shipyard plugin so a conductor runs on the device; it describes a large, still-maturing toolchain rather than a finished build. source

From 4 public sources, checked 23 September 2026.

Try Omni-ID

Code on GitHubOpen on GitHub ↗Last change 19 June 2026.
ReleaseNo GitHub release recorded.
The project's own files do not say how it is run.

Details & sources

Source: Polymorph225/omni-id

Evidence

Last change: api.github.com/repos/Polymorph225/omni-idlisted by a third party · seen since 20 October 2026 · github.repository@1
Activity: api.github.com/repos/Polymorph225/omni-idlisted by a third party · seen since 20 October 2026 · liveness@1

Compatibility

hdk: 0.6.1 · Cargo.toml @ ab1bd04
hdi: 0.7.1 · Cargo.toml @ ab1bd04
holochain-client: 0.20.0 · ui/package.json @ ab1bd04
happ.yaml: present · workdir/happ.yaml @ ab1bd04
web-happ.yaml: present · workdir/web-happ.yaml @ ab1bd04

Do you maintain Omni-ID?Add your name to this project’s page.

Claim this page