Darkbloom vs Statewright

Darkbloom is a peer-to-peer AI inference network built on idle Apple Silicon machines. Built by the team at Eigen Labs, it routes model inference requests across a mesh of MacBooks, Mac Minis, and Mac Studios whose owners opt in as operators. Prompts are end-to-end encrypted so operators cannot read user data, and operators keep 100% of the inference fees they earn. The network exposes an OpenAI-compatible API endpoint, so swapping from OpenAI or Anthropic requires a single line change. It supports popular open-weight models (Llama, Mistral, Qwen families) and claims up to 70% cost reduction versus centralized cloud inference — because the underlying hardware already exists in people's homes and offices. This is the most technically credible attempt yet at decentralized AI inference using consumer hardware. The core insight is that Apple Silicon chips have exceptional performance-per-watt and are already sitting idle in millions of homes. If the network can hit meaningful scale, it could meaningfully undercut AWS/GCP inference pricing while keeping prompts private — a rare combination.

Statewright takes a provocative stance on AI agent reliability: instead of making models smarter, restrict what they can do. The framework lets you define explicit state machines that determine which tools an agent can access at each phase of a workflow. During planning, agents get read-only tools. During implementation, edit tools unlock. During validation, only test commands are available. The philosophy is captured in a single line from the README: "Agents are suggestions, states are laws." The core engine is written in Rust for deterministic, zero-LLM evaluation of state transitions. Plugin layers integrate with agents via MCP (Model Context Protocol), enforcing tool restrictions at the protocol level across most major platforms. The framework is Apache 2.0 for its core engine, with FSL licensing for extended features (converting to Apache 2.0 in 2029, self-hosting allowed for developers and teams now). The team published SWE-bench results showing models jumping from 2/10 to 10/10 success rates on five tasks when Statewright constraints were applied—a striking claim that has the HN crowd both skeptical and intrigued. This is genuinely novel territory: rather than prompt engineering or fine-tuning, it's architectural guardrails enforced at runtime. For production agent deployments where agents interacting with dangerous tools (databases, file systems, APIs) need hard constraints, this fills a real gap. 53 stars so far, but the HN traction suggests it's about to pop.