lrx.sh
License and Right eXchange

Protocol · v3.4.0

Where digital licenses become first-class citizens of the network.

A quietly authoritative registry for declaring, exchanging, and verifying rights — typeset for clarity, engineered for portability.

Read on

§ 01 · Purpose

A trusted intermediary, written as code.

lrx.sh provides the foundational substrate for exchanging digital licenses and rights. We sit at the seam between legal language and machine execution, turning the careful prose of agreements into verifiable, portable, signed objects that travel with the assets they govern.

Every license becomes a first-class digital artifact — immutable in its terms, transparent in its provenance, addressable across any system that speaks the protocol. No bespoke contracts. No siloed registries. No ambiguous handshakes between counterparties.

RFC-LRX-2026 · open specification · community governed

§ 02 · The Exchange

Publish terms, discover terms, settle in a single transaction.

Rights holders publish license terms through a declarative schema. Consumers discover, evaluate, and acquire rights through a unified interface. The exchange handles the inconvenient complexity — jurisdiction mapping, term normalization, compliance verification — so that integration looks like a function call.

Each settlement produces a cryptographically signed receipt that doubles as both proof of acquisition and a machine-readable grant. No intermediaries collecting tolls in the middle. No ambiguity about what was agreed. No friction between intent and effect.

License Grant · grant.sh
lrx grant \
  --holder   "org:acme-corp" \
  --asset    "pkg:widget@2.0" \
  --terms    "commercial-use,redistribution" \
  --duration "perpetual" \
  --sign

§ 03 · Architecture

Three quiet layers, each doing one thing well.

lrx.sh is built on three principles: immutability of terms, transparency of provenance, and portability of grants. The architecture reflects these values at every layer — and only at every layer. Nothing is sprinkled in for marketing.

  1. 01

    Registry Layer

    A distributed ledger of license definitions, each addressed by a content hash. Terms cannot be altered after publication — only superseded by new versions with explicit migration paths and signed deprecations.

  2. 02

    Exchange Layer

    The matching engine that connects rights holders with consumers. Supports bulk operations, conditional grants, and time-bounded trial licenses with automatic expiration. Settlement is atomic; receipts are signed at the point of agreement.

  3. 03

    Verification Layer

    Runtime verification of license grants against application contexts. Embeddable as a library, deployable as a sidecar, or queryable as a service — all returning the same answer for the same inputs.

§ 04 · For Rights Holders

Define your terms once, distribute them everywhere.

lrx.sh translates human-readable license language into machine-enforceable policy. Monitor usage, manage grants, and receive compensation through a single interface that respects the substance of intellectual property without drowning you in tabs and modals.

Our tooling integrates directly into the workflows you already keep — CI/CD pipelines, package registries, content management systems, billing infrastructure. Publishing a license is as simple as committing a file and signing the commit.

License Definition · commercial-standard.yml
name: "Commercial Standard"
version: 3
permissions:
  - commercial-use
  - modification
  - distribution
conditions:
  - attribution
  - notice-preservation
limitations:
  - liability
  - warranty

§ 05 · For Consumers

Discover exactly the rights you need — and prove you have them.

Search by permission type, jurisdiction, asset category, or compliance requirement. lrx.sh surfaces compatible licenses from across the exchange, ranks them by fit, and handles acquisition in a single transaction that leaves you with a receipt your build system can read.

Integrate verification into your release pipeline to ensure compliance at every artifact boundary. The SDK checks license grants against your dependency tree and flags conflicts before they become legal exposure.

SDK distributions: npm · pip · cargo · go · maven

§ 06 · Open Standard

Infrastructure for rights should be as open as the rights themselves.

The lrx protocol is a free, versioned specification. Backward compatibility is enforced by the governance process; extensions are namespaced; new versions ship with reference implementations and conformance suites. Interoperability is not a feature — it is the foundation.

Any system that implements the protocol can participate in the exchange without permission, intermediation, or vendor lock-in. The reward for adoption is access to the network; the cost is conformance to the spec.

LRX

Trusted infrastructure for the exchange of digital rights and licenses.

spec/2026-r4 · signed · reproducible