Comparison
Weave & Hypercore.
Hypercore (the data primitive behind Holepunch and Pear) is the closest tech relative to Weave's Trace — both are append-only, signed, replication-friendly logs. The differences are language, scope, and audience.
| Dimension | Hypercore | Weave |
|---|---|---|
| Primary language | JavaScript / Node + Bare runtime | Rust workspace |
| Append-only log | Hypercore | Trace |
| Filesystem | Hyperdrive | Locus (Trace-backed) |
| Discovery | Hyperswarm DHT | weave-dht |
| Streams | NoiseSecretStream | weave-secret-stream |
| Application protocol | Keet, custom Pear apps | WOVEN (signed events) + custom |
| Scope | P2P apps + runtime + delivery | 8 composable primitives in one workspace |
| Agent surfaces | Not a stated goal | /llms.txt, /llms-full.txt, /skill.md, /.well-known/agent.json |
| License | MIT / Apache-2.0 | MIT |
Pick Hypercore
Pick Hypercore if you want to ship JS-native P2P apps on the Pear runtime, or build directly on hypercore-protocol with libp2p-style Node tooling.
docs.pears.com →Pick Weave
Pick Weave if you want a Rust workspace, agent-readable surfaces by default, and the matching log + view + drive + transport + app layers as one stack.
All primitives →Where they meet, where they diverge.
- Both are off-chain, peer-to-peer, append-only-log designs.
- Hypercore lives at one layer (the data structure). Weave bundles the matching layers — log, view, drive, convergence, transport, application — into one Rust workspace.
- Hypercore optimizes for the JS-native, Bare-runtime, mobile-first vision (Holepunch / Pear). Weave optimizes for Rust services and agent fabrics.