What You Can Build Today

Eighteen Months and a Million Dollars: Part 9

Excerpts from the Arkhai Whitepaper

Key Takeaways

• The original whitepaper was completed in summer 2024; the public product surface has evolved since then
• Settlement primitive: Alkahest (escrow + arbitration) plus developer SDKs
• Alkahest expresses peer-to-peer agreements as Statements, validators/arbiters, and escrowed value
• Git Commit Marketplace: pay the first commit that passes your tests
• Agentic RAG: provenance-first RAG pipelines for scientific work
• Generalized marketplace protocol: at publication, this was described as soon to be released; SCM was released later

Historical context — March 2026 pre-SCM-release snapshot

“Today,” “right now,” and availability statements in this post refer to March 2, 2026. SCM was released later, and the broader compute-and-energy and arbitrary-constraint negotiation language below remains research direction rather than current SCM behavior. Current SCM VM rounds vary scalar price while non-price VM terms remain fixed or validated. See Arkhai Compute and the current SCM source for current boundaries.

Eighteen months and a million dollars

The whitepaper was a thesis about machine-native markets. The last eighteen months have been about turning one part of that thesis into something real: settlement in open environments.

A bit changed in the process (but surprisingly, not much!). Some ideas stayed as research. Some became experiments. Many became concrete interfaces you can use today.

Below are the application surfaces the post described as existing at its March 2026 publication date, written in the same format: what it is, who it's for, and what you get.

Application 1: Escrow and arbitration (Alkahest)

Alkahest is Arkhai's open-source escrow and arbitration system for peer-to-peer agreements. You describe what should happen, under which conditions, and who decides when those conditions hold. Escrow enforces the outcome.

At the interface level, this is a small set of primitives:

• Statements to represent obligations
• Validators/Arbiters to evaluate conditions (and escalate when necessary)
• Escrow obligations to hold and release value

Who this is for:

• Anyone building marketplaces, bounties, or escrowed services
• Teams that need conditional payment in open environments (not just trusted counterparties)
• Protocol designers who want a reusable settlement layer instead of bespoke per-app escrow

What you get:

• A programmable escrow interface you can reuse across deal types
• Dispute resolution and recursive escalation when automation runs out
• Composable conditions (boolean logic over on-chain and off-chain signals)

Application 2: Markets for shipped code (Git Commit Marketplace)

Git Commit Marketplace turns commits into tradeable units of work: escrow funds, define verification (tests), and pay the first commit that satisfies the objective.

Who this is for:

• Open source maintainers funding specific changes
• Teams that want outcome-based contracting instead of hourly workflows
• Organizations that want transparent pricing for discrete engineering tasks

What you get:

• Faster, more legible procurement of software work
• Automated verification as the oracle for payment
• Settlement that doesn't require trusting the counterparty

Application 3: Provenance-first research RAG (Agentic RAG)

Agentic RAG is an open-source approach to retrieval-augmented generation for scientific and technical work, focused on reproducibility and provenance rather than chatbot answers.

Who this is for:

• Researchers and labs building literature maps and research assistants
• Teams that need traceable, reproducible retrieval pipelines
• Organizations building internal knowledge systems that must be auditable

What you get:

• RAG pipelines that preserve provenance from source → chunk → embedding → retrieval → output
• A system designed for inspection and iteration, not black-box responses
• A way to turn retrieval into a first-class, reusable artifact

Application 4: Compute and energy markets driven by cybernetic agents

At publication, this section described a pre-release direction for generalized compute-and-energy markets: autonomous agents negotiating over cycles and watts under constraints such as latency, carbon, and reliability. Current SCM implements a narrower compute path whose VM rounds vary scalar price while resource, duration, provisioning, and non-amount escrow terms stay fixed or validated. Energy markets and arbitrary-constraint negotiation remain direction, not current SCM behavior.

Who this is for:

• Compute and energy providers exploring market-based allocation
• Data center operators looking to maximize their ROI on compute and energy infrastructure
• Compute purchasers looking for the best deals given their requirements
• DePIN and infrastructure teams that need programmable settlement primitives
• Builders who want to participate in shaping the threat model and mechanism choices early

What you get:

• A path to agent-mediated resource allocation built on a concrete settlement layer
• Early integration points: settle deals with escrow/arbitration, then iterate on matching and optimization

Getting started

Pick one surface and build one small loop end-to-end:

• Alkahest (escrow + arbitration): Model your deal as a Statement. Decide what evidence releases funds, and who arbitrates when evidence is ambiguous. Start with one validator and one outcome, then add complexity.
• Git Commit Marketplace: Choose an objective (a failing test, a benchmark, a feature flag). Escrow funds. Pay the first passing commit. Start with deterministic checks, then expand to richer verification.
• Agentic RAG: Make provenance a first-class output. Persist source references, chunk IDs, and retrieval traces so results can be audited and reproduced.
• March 2026 generalized-market direction: The post proposed defining deal formats and constraints such as latency, carbon, and reliability, then iterating on negotiation and matching above Alkahest. This was not current SCM behavior.

---

For current compute infrastructure and limitations, explore Arkhai Compute or inspect the SCM source.