TLaaS (LEX) — Designing a License Schema: Fields, Rights, Expiry & Metadata

1. Purpose of the License Schema

A well‑structured license schema defines what rights are granted, for how long, and under what conditions. In TLaaS (LEX), this schema becomes the backbone of the marketplace protocol, ensuring clarity for issuers, holders, validators (via TLAAS), and arbitrators (via DAL).

2. Core Fields

Each tokenized license should include the following on‑chain fields:

  • License ID – Unique identifier linked to the NFT/SFT.
  • Issuer Address – Public key of the license creator.
  • Holder Address – Current owner’s public key.
  • Issued Date – Timestamp of creation.
  • Expiry Date – Timestamp of expiration.
  • Rights Granted – Machine‑readable list of permissions.
  • Restrictions – Conditions or limitations of use.
  • Jurisdiction – Applicable legal region(s).
  • Royalty Terms – Percentages and distribution logic.
  • Validation Hash – Reference to off‑chain/hashed agreement text.

3. Rights Definition

Rights should be codified in a standardized format to support automation and interoperability:

  • Usage Rights – Personal, commercial, resale, sublicensing.
  • Geographic Rights – Country or region‑specific usage.
  • Temporal Rights – Time‑bound or perpetual.
  • Modification Rights – Alteration, adaptation, or derivative works.

4. Expiry & Renewal Logic

  • Fixed Term – License expires on a set date; renewals require payment.
  • Rolling Term – Automatically extends upon recurring payment.
  • Conditional Renewal – Extends only if validator approval or compliance checks pass.
  • Grace Period – Optional extension window before revocation.

5. Metadata Standards

Metadata should follow a consistent JSON schema for on‑chain and off‑chain storage:

{
  "license_id": "12345",
  "issuer": "0x123...",
  "holder": "0x456...",
  "issued_date": "2025-08-08T00:00:00Z",
  "expiry_date": "2026-08-08T00:00:00Z",
  "rights": ["commercial", "resale"],
  "restrictions": ["no-derivatives"],
  "jurisdiction": "US",
  "royalty_terms": {"issuer": 40, "validators": 20},
  "validation_hash": "Qm...IPFSHash"
}

6. Integration Points

  • TLAAS (DLA): Validates license authenticity, expiry, and rights.
  • DAL: Resolves disputes regarding rights usage or term violations.
  • Smart Compliance: Ensures licenses meet regulatory and industry standards.

7. Benefits of a Standardized Schema

  • Interoperability across CHLOM protocols.
  • Reduced disputes through clear, machine‑readable terms.
  • Easier validation and automated enforcement.
  • Compatibility with external marketplaces and ecosystems.

Next Article: License Registry Smart Contract (LEX) — ERC‑721/1155 Implementation Guide

Was this article helpful?

TLaaS (LEX) — Deployment Scripts (Testnet & Mainnet): Environment Management
TLaaS (LEX) — Event‑Driven License Lifecycle Management