docs: modernize + LLM.md + cross-links (one-way SDK model)
This commit is contained in:
z
@@ -1,12 +1,86 @@
|
||||
<p align="center"><img src=".github/hero.svg" alt="net" width="880"></p>
|
||||
<p align="center"><img src=".github/hero.svg" alt="Hanzo Net" width="880"></p>
|
||||
|
||||
# hanzonet/network — archived
|
||||
# Hanzo Net
|
||||
|
||||
> **This monorepo has been split into 36 focused repositories** under the
|
||||
> [`hanzonet`](https://github.com/hanzonet) GitHub organization. Each crate
|
||||
> now lives in its own repo with its own CI and ship cadence.
|
||||
**Run your own distributed AI cluster — in Rust, across every device you own.**
|
||||
|
||||
## Where each crate lives now
|
||||
Hanzo Net turns the machines you already have — iPhone, iPad, Mac, an NVIDIA box,
|
||||
a Raspberry Pi — into one private, peer-to-peer AI cluster. Models, agents, tools,
|
||||
and inference run on your hardware, meshed together over libp2p, with post-quantum
|
||||
identity and on-chain settlement built in. No datacenter, no proxy, no lock-in.
|
||||
|
||||
This repository is the **canonical Rust workspace** behind Hanzo Net: a set of
|
||||
focused crates that compose into a self-hostable node.
|
||||
|
||||
<p>
|
||||
<img src="https://img.shields.io/badge/license-MIT-black" alt="MIT">
|
||||
<img src="https://img.shields.io/badge/rust-2021-black" alt="Rust 2021">
|
||||
<img src="https://img.shields.io/badge/crates-36-black" alt="36 crates">
|
||||
<img src="https://img.shields.io/badge/post--quantum-native-black" alt="Post-quantum native">
|
||||
</p>
|
||||
|
||||
## Why Hanzo Net
|
||||
|
||||
- **Your hardware, your cluster.** Pool everyday devices into one inference fabric —
|
||||
each node contributes compute, storage, and models.
|
||||
- **Peer-to-peer by design.** libp2p mesh with a relayer for NAT traversal; no
|
||||
central coordinator to trust or pay.
|
||||
- **Agents, tools, and MCP on-device.** A full agentic runtime — job queue, tool
|
||||
runner, and Model Context Protocol — executes locally and safely.
|
||||
- **Post-quantum from the identity up.** ML-KEM, ML-DSA, and SLH-DSA underpin node
|
||||
identity, messaging, and attestation.
|
||||
- **On-chain settlement.** An embedded L2 (Quasar BFT, EVM with AI precompiles)
|
||||
meters and settles heterogeneous compute.
|
||||
- **Zen models, natively.** Serve the Zen model family — Hanzo's own architecture —
|
||||
alongside your local weights.
|
||||
|
||||
## Quickstart
|
||||
|
||||
Build the whole workspace from source:
|
||||
|
||||
```bash
|
||||
git clone https://github.com/hanzoai/net
|
||||
cd net
|
||||
cargo build --release
|
||||
cargo test
|
||||
```
|
||||
|
||||
Or depend on an individual crate from crates.io:
|
||||
|
||||
```toml
|
||||
[dependencies]
|
||||
hanzo-vm = "1.1"
|
||||
hanzo-runtime = "1.1"
|
||||
# crates whose name collides with the consumer SDK ship under a hanzonet-* package:
|
||||
hanzo-pqc = { version = "1.1", package = "hanzonet-pqc" }
|
||||
```
|
||||
|
||||
The Rust library name is always `hanzo_*`, so `use hanzo_vm::…;` works regardless of
|
||||
which package on crates.io served the crate.
|
||||
|
||||
A running node exposes a local HTTP API under `/v1` for models, jobs, and tools.
|
||||
|
||||
## Architecture
|
||||
|
||||
Hanzo Net is composed, not monolithic. The core pieces:
|
||||
|
||||
| Layer | Crates | What it does |
|
||||
|-------|--------|--------------|
|
||||
| **Networking** | `hanzo-libp2p`, `hanzo-libp2p-relayer`, `hanzo-messages` | Peer-to-peer mesh, relaying, and typed node messaging. |
|
||||
| **Identity & crypto** | `hanzo-identity`, `hanzo-did`, `hanzo-pqc`, `hanzo-zap` | Post-quantum node identity, DIDs, and authorization. |
|
||||
| **Runtime & inference** | `hanzo-runtime`, `hanzo-wasm`, `hanzo-wasm-runtime`, `hanzo-embed`, `hanzo-models`, `hanzo-model-discovery` | On-device model execution, WASM sandboxing, embeddings, and model discovery. |
|
||||
| **Agents & tools** | `hanzo-agentic`, `hanzo-tools`, `hanzo-tools-runner`, `hanzo-runner`, `hanzo-mcp`, `hanzo-jobs`, `hanzo-job-queue-manager` | Agentic orchestration, safe tool execution, and the Model Context Protocol. |
|
||||
| **Data & state** | `hanzo-database`, `hanzo-db-sqlite`, `hanzo-fs`, `hanzo-api`, `hanzo-http-api` | Storage, filesystem, and the local `/v1` HTTP surface. |
|
||||
| **Cluster economics** | `hanzo-compute`, `hanzo-machine`, `hanzo-mining`, `hanzo-hmm`, `hanzo-brain` | Compute accounting, VM lifecycle, and Hamiltonian market-maker pricing for heterogeneous hardware. |
|
||||
| **On-chain settlement** | `hanzo-consensus`, `hanzo-vm`, `hanzo-l2` | Quasar BFT consensus, an EVM with PQ / Quasar / AI-inference precompiles, and an L2 bridge on Lux Network. |
|
||||
|
||||
### All crates
|
||||
|
||||
Every workspace member is also published to crates.io and mirrored as a standalone
|
||||
repository for focused issues and CI.
|
||||
|
||||
<details>
|
||||
<summary><strong>36 crates → standalone repos</strong></summary>
|
||||
|
||||
| Crate (crates.io) | Repo |
|
||||
|--------------------------|-------------------------------------------------------------|
|
||||
@@ -47,27 +121,34 @@
|
||||
| `hanzo-wasm-runtime` | [`hanzonet/wasm-runtime`](https://github.com/hanzonet/wasm-runtime) |
|
||||
| `hanzo-zap` | [`hanzonet/zap`](https://github.com/hanzonet/zap) |
|
||||
|
||||
</details>
|
||||
|
||||
## Naming convention
|
||||
|
||||
- **`hanzonet-*`** = network-internal implementations of names that collide with
|
||||
the consumer SDK in [`hanzoai/rust-sdk`](https://github.com/hanzoai/rust-sdk).
|
||||
Crates: `hanzonet-pqc`, `hanzonet-did`, `hanzonet-config`, `hanzonet-mcp`.
|
||||
the consumer SDK in [`hanzo-rs/sdk`](https://github.com/hanzo-rs/sdk). Crates:
|
||||
`hanzonet-pqc`, `hanzonet-did`, `hanzonet-config`, `hanzonet-mcp`. Import them
|
||||
under their original name via a package rename:
|
||||
|
||||
To use them with their original import name:
|
||||
```toml
|
||||
hanzo-pqc = { version = "1.1.21", package = "hanzonet-pqc" }
|
||||
hanzo-pqc = { version = "1.1", package = "hanzonet-pqc" }
|
||||
```
|
||||
|
||||
- **`hanzo-*`** = everything else. The Rust library name is always `hanzo_*`,
|
||||
so `use hanzo_vm::...` works regardless of which package on crates.io
|
||||
served the crate.
|
||||
- **`hanzo-*`** = everything else. The Rust library name is always `hanzo_*`, so
|
||||
`use hanzo_vm::…;` works regardless of which package on crates.io served the crate.
|
||||
|
||||
## Why split?
|
||||
## Contributing
|
||||
|
||||
One repo per focused concern. Each repo has its own CI, its own ship cadence,
|
||||
its own issues, and a clear scope. Easier to grep, easier to depend on,
|
||||
easier to evolve independently.
|
||||
One repo per focused concern, one workspace to build them together. Each crate has
|
||||
a clear scope and its own tests. `cargo test` from the root runs the full suite;
|
||||
`cargo test -p <crate>` targets one.
|
||||
|
||||
## License
|
||||
|
||||
MIT.
|
||||
MIT © Hanzo AI, Inc. See [LICENSE](LICENSE).
|
||||
|
||||
## Hanzo — the Open AI Cloud
|
||||
|
||||
Open source · every language · on-chain settlement. [hanzo.ai](https://hanzo.ai) · [docs.hanzo.ai](https://docs.hanzo.ai)
|
||||
|
||||
**SDKs in every language** — [Python](https://github.com/hanzoai/python-sdk) (flagship) · [TypeScript](https://github.com/hanzo-js/sdk) · [Go](https://github.com/hanzo-go/sdk) · [Rust](https://github.com/hanzo-rs/sdk) · [C++](https://github.com/hanzo-cpp/sdk) · [Swift](https://github.com/hanzo-swift/sdk) · [Kotlin](https://github.com/hanzo-kt/sdk) · [umbrella](https://github.com/hanzoai/sdk)
|
||||
|
||||
Reference in New Issue
Block a user