CHLOM™ Licensing Master Technical Document

Version 1.0 — Issued by CrownThrive, LLC “Issuance, Terms, Transfers, and the Roadmap for Tokenized Licensing in the Decentralized Licensing & Compliance Layer.”

Audience: Product architects, licensing engineers, compliance leads, LEX market designers, validator operators, integrators, and Help Center editors curating the CHLOM Licensing category. Scope: Canonical reference for what CHLOM Licensing is, how it’s modeled and encoded, how it works in production, and which 30+ follow‑on docs to read next.

0 · How to Use this Master Doc (Help Center Index)

  • Start here for the big picture and concrete build paths for license issuance, amendments, sublicensing, renewal, and transfer.
  • Each section ends with “What to read next” cross‑links into the Licensing category.
  • Code examples are illustrative; the authoritative source is the runtime repository, LEX specs, and governance records.

1 · System Overview

CHLOM™ Licensing defines how rights and obligations are issued, amended, enforced, transferred, renewed, revoked, and optionally fractionalized. Licenses are represented as chain‑native NFTs bound to:

  • Terms (CID) — canonical legal/commercial terms at issuance time;
  • KPI Profile — measurable performance commitments;
  • Royalty Model — graph of recipients and weights;
  • Compliance Pack — jurisdictional rules and disclosures;
  • Constraints — transfer/sublicense rules, ROFR/ROFO, regional scope, and expiry.

Licensing logic is deterministic in pallets; attestations are provided by oracles; enforcement is governed by DLA and DAO.

1.1 High‑Level Architecture

+--------------------------+      +--------------------+      +---------------------------+
|  Business Apps & Consoles|<---->|  API Gateway / WS  |<---->| Reference Chain (Runtime) |
|  (Issuer, LEX, Ops)      |      |  (REST/WS/RPC)     |      | FRAME Pallets             |
+--------------------------+      +--------------------+      +---------------------------+
                                                                | licensing / kpi / royalty |
+--------------------------+      +--------------------+        | dla / lex / gov / oracle  |
|  Data & Analytics        |<---->|  Indexers          |        | attest / sustainability   |
|  (Dashboards, BI)        |      |  (SubQuery/Squid)  |        | treasury / staking ...    |
+--------------------------+      +--------------------+        +---------------------------+

+--------------------------+      +--------------------+
|  Oracles & Off‑chain     |<---->|  OCWs + Gateways   |
|  (KYC, IoT, POS, ESG)    |      |  (signed feeds)    |
+--------------------------+      +--------------------+

1.2 Consensus & Accounts

Framework is chain‑agnostic; the reference chain uses:

  • Consensus: BABE (block production) + GRANDPA (finality).
  • Staking: NPoS (
  • Accounts: SS58, sr25519/ed25519; multisig via

What to read next: Doc 01 — Licensing Conceptual Model; Doc 02 — Network & Keys Handbook.

2 · Core Protocols (Functional Specs)

2.1 Licensing Protocol (LP)

Tokenizes rights/obligations as License NFTs (using pallet_nfts or pallet_uniques). Each license carries: jurisdiction, scope, royalty formula, KPI thresholds, escrow rules, transfer constraints, expiry/renewal window, and compliance pack binding.

Extrinsics (examples):

  • licensing.mint(class_id, metadata, terms_hash)
  • licensing.attachKpi(item_id, kpi_profile_id)
  • licensing.bindPack(item_id, pack_id)
  • licensing.amend(item_id, terms_hash)
  • licensing.sublicense(item_id, percent, buyer, constraints)
  • licensing.transfer(item_id, to)
  • licensing.renew(item_id, window)
  • licensing.revoke(item_id, cause)

Storage: (class_id, item_id); TermsCID; KpiProfileId; PackId; RoyaltyModelId; Constraints; Expiry; Flags (frozen, escrowed, disputed).

2.2 Terms & Amendments Protocol (TAP)

Canonical terms tracked via IPFS/Arweave CID; amendments recorded as incrementing versions with diff hashes; optional multi‑sig sign‑off.

  • terms.register(terms_hash, metadata)
  • terms.link(item_id, terms_hash)

2.3 Sublicensing Protocol (SLP)

Deterministic carve‑outs by bps, geography, or channel; respects parent constraints; cascades royalties and KPIs.

2.4 Renewal & Expiration Protocol (REP)

Auto‑notifications pre‑expiry; proof of cure windows for breaches before renewal; grace periods per policy.

What to read next: Doc 03 — Licensing Protocol Spec; Doc 04 — Terms & Amendments Spec; Doc 05 — Sublicensing Spec; Doc 06 — Renewal & Expiration Spec.

3 · Runtime Pallets (FRAME)

PalletPurposeKey StorageKey ExtrinsicsEvents/Errors
pallet_chlom_licensingMint/amend/transfer/sublicenseLicenses, TermsCID, Constraints, Expirymint, amend, transfer, sublicense, renew, expire, revokeLicenseMinted, Revoked
pallet_chlom_kpiKPI thresholds & reportsThresholds, Reportsset_thresholds, report, flagKpiBreached
pallet_chlom_royaltyRoyalty graph & payoutsSplits, Accrualsroute, settleRoyaltySettled
pallet_chlom_lexExchange for License NFTsOrders, Escrowslist, buy, partialSell, cancelTradeSettled
pallet_chlom_dlaDisputes & sanctionsCases, SanctionsopenCase, applySanction, resolveSanctionApplied
pallet_oracle_gatewayCompliance/pricing oraclesFeeds, SigsregisterFeed, attestAttested
pallet_attestationsEvidence registryProofssubmitProofProofRecorded
pallet_chlom_govGovernance hooksWeights, RolessetWeight, assignRoleGovWeightChanged
pallet_reputationIssuer/operator scoresScoresupdateScoreReputationUpdated
pallet_sustainabilityImpact ledger & offsetsImpacts, RoutesrecordImpact, routeOffsetImpactRecorded

What to read next: Doc 07 — Pallet Design Deep Dives (Licensing Set).

4 · Data Model & Schemas

  • License:
  • TermsVersion:
  • Sublicense:
  • Renewal:

What to read next: Doc 08 — Runtime Storage & Schemas (Licensing).

5 · Protocol Flows (Sequence Specs)

5.1 License Lifecycle

Apply → KYC/KYB (oracle) → Mint License NFT → Operate (emit KPI/royalty events) → Comply (auto checks) → Amend/Transfer/ Sublicense → Renew/Expire/ Revoke.

5.2 Royalty Settlement

Transaction → royalty.route() compute splits → accrual buckets → settle() by era/threshold → emit receipts.

5.3 LEX Trade

list() → escrow → policy gates (ROFR/pack restrictions) → buy() → atomic swap; partial equity via partialSell(%) when enabled.

What to read next: Doc 09 — Sequence Diagrams & State Machines.

6 · Governance & DAO Mechanics

DAO owns policy parameters: default constraints, renewal grace, breach curves, sanction ladders, sublicensing caps, fee schedules. Council fast‑track for freezes; post‑hoc referendum ratification; scheduler for phased policy rollouts.

What to read next: Doc 10 — Governance Parameters & Processes (Licensing).

7 · Token Model (Runtime View)

  • CHM (governance): stake, vote, validator rewards; reputation‑weighted policy influence.
  • CHLOM (utility): fees for mint/transfer/sublicense/renewal; escrow & dispute fees; buyback/burn hooks; bonds for high‑risk issuances.

What to read next: Doc 11 — Token Implementation & Fee Model (Licensing).

8 · Oracles & Off‑Chain Workers

KYC/KYB, sanctions, IoT occupancy, POS revenue, sustainability receipts. OCWs batch KPI reports, renewal notices, grace‑period checks, and signed attestations.

What to read next: Doc 12 — Oracle Gateway & OCW Patterns (Licensing).

9 · Indexing & Analytics

Index license states (active, frozen, expired), amendments, sublicenses, ROFR/transfer attempts, DLA cases, royalty settlements. Dashboards: renewal calendars, breach heatmaps, constraint violations, issuer reputation.

What to read next: Doc 13 — Indexing Blueprints; Doc 14 — Observability & Telemetry.

10 · Security, Privacy, and Compliance

Threats: forged terms, stale KPIs, MEV around LEX, oracle spoofing, replayed renewals. Controls: multi‑sig issuance, versioned terms, ZK proofs for sensitive KPIs, property tests, non‑reentrant escrows, circuit breakers, time‑locks for policy changes, CI gates.

What to read next: Doc 15 — Security Standards & Threat Model; Doc 16 — Privacy/ZK Patterns.

11 · Sustainability & Impact Hooks

Each issuance/renewal can route 1% (scaling to 5%) to Stripe Climate; EcoDrive campaigns rotate by territory; recordImpact(kind, amount, ref) logs impact tied to licensing volume.

What to read next: Doc 17 — Sustainability Module & API.

12 · Developer Environment & Tooling

12.1 Prereqs

Rust stable + nightly; wasm32-unknown-unknown; Substrate node template; subkey; Docker; Polkadot‑JS Apps.

12.2 Build & Run (Reference Chain)

rustup target add wasm32-unknown-unknown
cargo build -p node --release
./target/release/chlom-node --dev

12.3 Testing

Unit/integration tests; try-runtime; proptest and fuzzing; scenario tests for amendments, renewals, sublicenses, DLA freezes.

What to read next: Doc 18 — Local Dev & Testing Guide.

13 · Deployment Topologies

DevNet (faucet, mock oracles); TestNet (permissioned oracles; chaos tests); MainNet (oracle SLAs; governed policy updates; snapshots/backups; incident response SOPs).

What to read next: Doc 19 — Networks & Chain Specs; Doc 20 — Upgrade Playbook (Forkless Upgrades).

14 · SDKs & API Surfaces

TypeScript SDK (high‑level wrappers), Rust client (indexers/oracles), JSON‑RPC (standard + licensing_*).

Example:

await api.tx.chlomLicensing.mint(classId, termsCid, scope)
  .signAndSend(account)

What to read next: Doc 21 — TS SDK Reference; Doc 22 — Custom JSON‑RPC Extensions.

15 · Royalty Graph & Licensing Interplay

License binds to a RoyaltyModelId; route/settle honors sublicensing cascades; escrow holds during disputes; Merkle receipts for audits; dust rounding policy disclosed in terms.

What to read next: Doc 23 — Royalty Engine Spec (Licensing Interop).

16 · KPI Catalogue & Measurement (Licensing Context)

Vertical metric packs (suites: occupancy; media: completion; commerce: repeat purchase). Thresholds map to sanctions and renewal eligibility; ZK‑eligible metric set for privacy‑sensitive verticals.

What to read next: Doc 24 — KPI Library & Policies.

17 · LEX Market Microstructure (Licensing)

Order types (fixed/Dutch/sealed‑bid); reserve prices; on‑chain escrow; oracle‑gated transfers per jurisdiction; commit‑reveal for high‑value auctions; automatic enforcement of constraints and ROFR.

What to read next: Doc 25 — LEX Market Design (Licensing Edition).

18 · DLA Case Management (Licensing)

Disputes: forged terms, KPI fraud, constrained transfers, renewal manipulation. Lifecycle with evidence chains, sanctions (freeze, revoke, fines), appeals, and public redaction policy.

What to read next: Doc 26 — DLA Casebook & Sanction Matrix.

19 · Cross‑Chain & Bridging (Licensing Tokens)

XCM for license movement; bridge allowlist; jurisdiction constraints; rate limits; circuit breakers for mass transfers; mapping tables for foreign asset IDs.

What to read next: Doc 27 — Cross‑Chain Strategy (Licensing Tokens).

20 · Compliance Packs by Jurisdiction (Licensing)

Pluggable rule packs for sector and region; mapping tables; version calendars; conflict‑of‑law fallbacks; localized disclosures and consent artifacts.

What to read next: Doc 28 — Regional Compliance Packs (Licensing).

21 · Operational Runbooks (Licensing Registrar & Governance)

Registrar ops (issuance QA, term versioning, renewal calendars, ROFR service levels). Governance ops (policy updates, change control, incident response).

What to read next: Doc 29 — Registrar/Validator Runbook (SRE); Doc 30 — Governance Ops Manual.

22 · Contribution, Versioning, and SLA

Semantic versions; migration notes; state version bumps; deprecation policy; documentation SLAs; change approval via governance; audit trails for term updates.

What to read next: Doc 31 — Contributing & Release Process.

23 · Full Documentation Roadmap (30+ Items)

  • Licensing Conceptual Model
  • Network & Keys Handbook (SS58, Sessions, Staking)
  • Licensing Protocol Spec
  • Terms & Amendments Spec
  • Sublicensing Spec
  • Renewal & Expiration Spec
  • Pallet Design Deep Dives (Licensing Set)
  • Runtime Storage & Schemas (Licensing)
  • Sequence Diagrams & State Machines (Licensing)
  • Governance Parameters & Processes (Licensing)
  • Token Implementation & Fee Model (Licensing)
  • Oracle Gateway & OCW Patterns (Licensing)
  • Indexing Blueprints (SubQuery/Subsquid)
  • Observability & Telemetry (Prometheus/Otel)
  • Security Standards & Threat Model
  • Privacy & ZK Patterns
  • Sustainability Module & API
  • Local Dev & Testing Guide
  • Networks & Chain Specs
  • Upgrade Playbook (Forkless Upgrades)
  • TypeScript SDK Reference
  • Custom JSON‑RPC Extensions
  • Royalty Engine Spec (Licensing Interop)
  • KPI Library & Policies
  • LEX Market Design (Licensing Edition)
  • DLA Casebook & Sanction Matrix
  • Cross‑Chain Strategy (Licensing Tokens)
  • Regional Compliance Packs (Licensing)
  • Registrar/Validator Runbook (SRE)
  • Governance Ops Manual
  • Disaster Recovery & Backups
  • Performance & Benchmarking (Weights)

24 · Final Notes for Help Center Editors

  • Keep this master current with each runtime and governance release.
  • Every new module/upgrade must link back to this index and add a child doc entry.
  • Cross‑check examples against the repository CI snapshot before publishing.

Appendix A — Example Types (Rust)

pub struct License { pub class_id: u32, pub item_id: u128, pub owner: AccountId32, pub jurisdiction: Vec<u8>, pub scope: Vec<u8>, pub royalty_model_id: u32, pub kpi_profile_id: u32, pub pack_id: u32, pub constraints: BoundedVec<Vec<u8>, ConstU32<16>>, pub terms_cid: Vec<u8>, pub expiry: u64, pub flags: u32 }
pub struct TermsVersion { pub terms_hash: Vec<u8>, pub version: u32, pub metadata: Vec<u8>, pub signed_by: BoundedVec<AccountId32, ConstU32<16>>, pub created_at: u64 }

Appendix B — Example TS SDK Call

await api.tx.chlomLicensing.mint(classId, termsCid, scope)
  .signAndSend(account, ({ status, events }) => { /* ... */ })

Disclaimer: Technical documentation; not legal advice. Always align deployments with applicable laws and CHLOM Governance decisions.

Was this article helpful?