Do I need a Holochain conductor to run AInonymous?

Yes. The documented path starts a Holochain conductor with a loopback-only admin WebSocket, installs the project's two hApp bundles, and then starts the daemon; a conductor connection failure is treated as fatal rather than falling back to another discovery method.

Does AInonymous hide who is talking to whom?

No. The project's own security documentation states that pseudonymous agent keys do not provide network anonymity, that relay and endpoint metadata such as timing and transfer sizes can still be observed, and that no mixnet, onion routing or zero-knowledge inference protocol is implemented.

Can anyone join a network?

Joining behaviour depends on the mode. A private network requires a signed admission credential supplied at installation that binds the agent to a network ID, while the public-network admission mechanism is documented as not implemented, which the maintainers give as the reason public mode remains development-only.

Project · inference-network

AInonymous

Name: AInonymous
Author: Geoking2104

a network for distributed AI inferenceDecentralized LLM inference network — Holochain P2P + QUIC + Gemma 4

Explore this project All projects

How you run it: not recorded
Holochain version: 0.7.0
Activity: active
Checked: 29 October 2026

What is AInonymous and what is it for?

AInonymous is an experimental peer-to-peer network for running large language model inference across several machines without a central database in the control path. Holochain records and validates the coordination state — membership, each node's declared capabilities and the scheduling of work — while model and inference traffic travels directly between peers over QUIC.

AInonymous explores how a group of machines can share large language model inference work without putting a single central service in the control path. Its design separates three jobs: Holochain carries the records that coordinate the network, a direct transport carries the heavy inference traffic, and an optional SD-WAN adapter can supply network topology and link-health signals. The maintainers describe it as alpha research software for development and controlled private pilots.

In human terms, the question the project asks is: if several people each have a machine that can run part of a model, how does anyone know who is available and who is who? AInonymous answers with entries authored by each participating agent — a node publishes what it can compute, which models it has loaded, and the public key it will use for direct connections — and the inference data itself moves over those direct connections rather than through the shared record store.

One documented use is a private pilot network: before an agent may join, an operator issues a signed admission credential that binds that agent to a specific network ID, and the app checks it at installation. The repository's docs/ARCHITECTURE.md and docs/SECURITY.md describe the design and its stated limits.

How to get it

Desktop app

Install the pinned toolchain the project requires: a recent Rust toolchain with the wasm32-unknown-unknown target, Holochain and hc from the 0.7.0 family, and the Lair keystore. On x86_64 Linux or WSL2 the repository's setup script installs the pinned release assets after verifying their published SHA-256 digests.
Pack both hApps with the pinned hc release — manifest validation and bundle formats are version-sensitive, so an older hc is not supported.
Start a Holochain conductor with a fresh data root and a loopback-only admin WebSocket, then install the ainonymous-core and hybridnode hApp bundles. The documented local configuration uses app ports 8889 and 8891 with admin on 8888.
For a private network, generate a PrivateNetworkProof for the target agent and network ID and supply it through role settings when installing the app; a matching private bootstrap mode and bootstrap URL are also required.
Start the daemon. Conductor connection failures are fatal by design — the runtime does not silently fall back to static discovery.

Source: https://github.com/Geoking2104/AInonymous

Questions people ask

Do I need a Holochain conductor to run AInonymous?: Yes. The documented path starts a Holochain conductor with a loopback-only admin WebSocket, installs the project's two hApp bundles, and then starts the daemon; a conductor connection failure is treated as fatal rather than falling back to another discovery method. source
Does AInonymous hide who is talking to whom?: No. The project's own security documentation states that pseudonymous agent keys do not provide network anonymity, that relay and endpoint metadata such as timing and transfer sizes can still be observed, and that no mixnet, onion routing or zero-knowledge inference protocol is implemented. source
Can anyone join a network?: Joining behaviour depends on the mode. A private network requires a signed admission credential supplied at installation that binds the agent to a network ID, while the public-network admission mechanism is documented as not implemented, which the maintainers give as the reason public mode remains development-only. source

From 3 public sources, checked 23 September 2026.

Try AInonymous

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

Details & sources

Source: Geoking2104/AInonymous

Evidence

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

Compatibility

hdk: 0.7.0 · dnas/ainonymous-core/dnas/agent-registry/zomes/coordinator/Cargo.toml @ d554b72
hdi: 0.8.0 · dnas/ainonymous-core/dnas/agent-registry/zomes/integrity/Cargo.toml @ d554b72
holochain-client: —
happ.yaml: present · dnas/ainonymous-core/happ.yaml @ d554b72
web-happ.yaml: absent

Do you maintain AInonymous?Add your name to this project’s page.

Claim this page