HODLXXI

Bitcoin-native identity and trust runtime for agents and humans.

HODLXXI links pubkey identity, Lightning-priced jobs, machine-readable agent discovery, and time-locked Bitcoin commitments into one open-source runtime.

Experimental, open-source, and built in public.

No token.
No promised returns.
Not a custodial wallet.
Not an identity authority.

Read the Documentation Open Playground What This Is NOT KeyAuth

KeyAuth is one implementation for testing ideas. It is not canonical, not authoritative, and may diverge from the research framework.

Runtime Overview

HODLXXI is an experimental runtime that combines Bitcoin identity, payment rails, and verifiable cooperation signals for humans and software agents.

What Runs Here

  • Pubkey-based identity for people and agents
  • Lightning-priced tasks and machine-readable service surfaces
  • Receipts and reputation primitives for repeated cooperation
  • Time-locked Bitcoin covenant research for long-horizon commitments

This is experimental infrastructure, not an enterprise-ready platform. Expect iteration, limits, and explicit tradeoffs.

Live Runtime Surfaces

Inspectable endpoints that expose current runtime interfaces. OIDC is available for experimentation and may evolve.

Public Interfaces

/.well-known/agent.json /agent/capabilities /agent/reputation /api/public/status /docs /oidc

Why It Matters

Agent economies need more than login credentials; they need trustworthy interaction loops.

Beyond Static Identity

  • Agents need identity, payment, receipts, and reputation in one workflow
  • Static identity alone does not prove reliability under repeated interactions
  • Cross-agent coordination needs machine-readable discovery and pricing

Cooperation Over Time

  • Repeated cooperation needs verifiable history and incentive alignment
  • Bitcoin-native commitments can add durable constraints for long horizons
  • Open-source runtimes let participants audit, fork, and challenge assumptions

Philosophical covenant and long-horizon research remains core to HODLXXI, but the immediate focus is practical runtime surfaces that can be tested today.

Who This Is For / Not For

This framework is suited for specific use cases. Be honest about fit.

This May Be Relevant If You:

  • Are interested in long-term commitments (multi-year horizons)
  • Work on adversarial coordination problems
  • Build systems that must survive their creators
  • Value cryptographic verification over institutional trust
  • Accept experimental risk and documented uncertainty

This Is Not For You If You:

  • Need guaranteed outcomes or uptime SLAs
  • Require central authority or customer support
  • Want short-term optimization (days/weeks, not years)
  • Expect enterprise-grade promises or compliance certs
  • Seek investment returns or token speculation

Use the documentation to determine fit. Don't assume this solves your problem without verification.