Repository navigation
Single source of truth for the mesh release (v0.2.0, pinned at 8a290d8). The JerithChain node repo stays untagged by design — the chain is deployed from its own main.
What's in it
- Public bootstrap live at https://p2p.jerithai.com (signed advertise/pings, Cloudflare Tunnel, no open ports)
- Live JerithChain escrow contract:
POST /stake/lock,/stake/unlock,GET /stake, Ed25519-signed/stake/slash - Core wiring: per-process escrow (wallet auto-create, idempotent marker, unlock on shutdown), ledger synced to
GET /stakeevery tick jerith stake status|lock|unlockCLI- Mesh fallback chat: consecutive-duplicate history compaction on the QUIC wire (verified wire-level)
- Dev tooling: one-command two-node E2E (
scripts/dev-e2e.sh), Rust ≥ 1.85 enforced
Verification
- Workspace tests green (170),
scripts/dev-e2e.shgreen, CLI smoke-tested on scratch homes - Deployed binary verified on the tunnel:
/health, signed peer advertise,/stake/*token-gated (401s)
Install & verify (sign-off build)
| Asset | What it is |
|---|---|
jerith-mesh-v0.2.0.tar.gz |
Source archive generated from the tag (git archive v0.2.0) |
jerith-linux-x86_64 |
Release binary built in a clean worktree checked out exactly at v0.2.0 — same build profile as the binary deployed on p2p.jerithai.com (lto = thin) |
SHA256SUMS |
sha256 of both artifacts |
Operator verification:
sha256sum -c SHA256SUMSCI on this tag lineage is green: cargo test --workspace on Ubuntu and macOS plus the two-node live E2E. macOS operators: build from the source archive with Rust ≥ 1.85.