HODLXXI

A Bitcoin-native research framework for long-term coordination

HODLXXI explores how cryptographic identity, time-locked commitments, and voluntary participation can support cooperation without central authority.

There is no token.
No promised returns.
No central operator.

This is not a product.
This is not a service.
This is an open research framework.

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.

What This Is

HODLXXI is an applied research effort exploring constraint-based coordination over long human time horizons.

Core Components

  • Bitcoin time primitives (OP_CHECKLOCKTIMEVERIFY, descriptors)
  • Cryptographic identity (public key authentication)
  • Repeated-game incentives (iterated Prisoner's Dilemma)
  • Explicit exit and forkability (no lock-in)

The goal is not optimization. The goal is constraint-based coordination that preserves agency and allows exit.

Research Status Threat Model & Failure Modes Technical Architecture

Transparency First

Every assumption is documented. Every limitation is explicit. Every failure mode is acknowledged.

Open Assumptions

All design decisions are documented with rationale. We state what we believe and why. We invite critique and alternative interpretations.

Explicit Limits

We document what the system cannot do. We list failure modes upfront. We acknowledge uncertainty.

Designed for Fork

The system is designed to remain inspectable, forkable, and functional without its original authors.

No Authority

No single entity controls the protocol. No privileged keys exist. Exit is always possible.

Explicit Limits Ethics & Invariants Governance License (MIT)

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.