Smart contract and licence alignment: documents to prepare
A smart contract can only encode what already exists in writing. Before any code is deployed, the licence terms it is meant to mirror must be inventoried, matched to specific contract functions, and signed off by someone with authority to approve the mapping. This page lists the documents that stage requires, the order they come in, and the point after which the mapping is no longer reversible.
This alignment step is one procedure inside a wider set of tokenised-rights work. It does not replace an assessment of what a given engagement can and cannot cover; that boundary is set out separately in What we do not do, and why the line.
Documents to prepare
The list below is the minimum set. Larger licences with multiple rights holders or cross-border scope tend to add side letters and amendment records to the same structure, not a different one.
| Document | Purpose | Who prepares it |
|---|---|---|
| Underlying licence agreement, current signed version | Defines scope, exclusivity, territory and term the contract must mirror | Whoever holds the executed copy, licensor or licensee |
| Rights inventory | Lists every right and permitted use separately so each maps to one contract function | Licensee's counsel or in-house team |
| Term sheet for the on-chain representation | States which licence fields become on-chain parameters and which stay off-chain | Joint drafting, technical and legal side together |
| Amendment or waiver record | Captures side letters or informal adjustments that change the written licence | Whoever holds the correspondence |
| Internal sign-off memo | Records who approved the mapping before deployment | Authorised signatory on the licensee's side |
| Pre-deployment checklist | Confirms the contract has been tested against every clause in the rights inventory | Technical lead, countersigned by counsel |
Where the licence concerns a reserve-backed token, this alignment step assumes the reserve itself has already been checked. The separate procedure for that verification is covered in Reserve evidence and attestation.
Stages and typical timing
- Inventory and matching. Every licence clause is read against the planned contract functions. This is usually the longest stage, because ambiguity in the licence text surfaces here, not later.
- Term sheet drafting. Technical and legal sides agree which fields become on-chain parameters and which remain off-chain records.
- Internal review. Counsel checks the term sheet against the rights inventory line by line.
- Sign-off. An authorised signatory approves the mapping in writing, before any code is written against it.
- Test deployment. The contract runs on a non-production network against sample data.
- Production deployment. This is the point of no return, described below.
Duration varies with the number of rights in the inventory and the number of parties who must sign off. A single-licensor arrangement with a short rights list moves through the first four stages in days. A licence with several sub-licensees or territorial splits adds review rounds at stage three.
Who decides
No court or regulator approves this mapping. The decision sits with whoever holds signing authority on the licensee's side, usually a director, compliance officer or a named authorised signatory under the entity's own internal rules. Their sign-off memo is the record that the mapping was checked before deployment, and it is the document most often requested later if a dispute arises over what the contract was supposed to encode.
Point of no return
Production deployment is the stage that cannot be undone by internal process alone. Once the contract is live and third parties begin to rely on it, correcting a mismatch between the licence and the code usually means a new contract version, a migration, or a negotiated fix with every counterparty affected. The pre-deployment checklist exists specifically to catch mismatches before this stage, not after it.
Forks
If the licence is exclusive, the rights inventory needs an explicit negative list: what the licensee is barred from sub-licensing, not only what it may do. An exclusive grant that is under-specified on-chain risks looking like a non-exclusive one to any third party reading the contract.
If the licence spans more than one jurisdiction, the term sheet should record which jurisdiction's version of the text governs each on-chain field, since licence wording can differ slightly between local versions of the same agreement.
If the licensor does not respond to a request to confirm scope before deployment, the safer route is to pause the mapping rather than encode an assumption. A contract deployed on an unconfirmed reading of the licence is harder to correct than a delayed deployment.
Sources and limits
This page describes procedure only. It does not classify the token, the licence or either party under any specific regulatory regime, and it is not a substitute for that classification. Jurisdiction-specific findings of that kind are recorded separately, with their own dates and their own limits, for example in Asset in Czechia and its limits or Debtor report ireland.
This page also does not cover tax treatment of the licence fee, insolvency priority of the licensed right, or how a court would read the smart contract against the licence if the two disagree after deployment. Those are separate questions with separate procedures.
Reviewed: 4 March 2025. This page contains no citation to a specific statute, regulation or directive, by design: it sets out sequence, documents and decision-makers, not legal classification.
Related reading
The recordal side of the same alignment work, on-chain against off-chain, is covered separately in How on-chain and off-chain recordal tokenised rights documents to.
FAQ
How long does smart contract and licence alignment take in practice?
For a single licence with a short rights list, the first four stages, inventory through sign-off, typically run over days rather than weeks. Additional sub-licensees, territorial splits or unresponsive counterparties extend the review stage, which is usually where the delay sits.
Which documents are needed to start?
At minimum: the current signed licence agreement and a rights inventory that lists each right separately. Everything else in the table above, the term sheet, amendment record, sign-off memo and checklist, is produced during the process rather than needed on day one.
What happens if the other side does not respond?
The mapping should not proceed on an unconfirmed assumption about scope. The usual response is to pause deployment, escalate the request internally, and rely on whatever notice or response period the licence itself sets out, rather than encode a guess into the contract.
Next step
If the underlying position depends on a licence that was refused or narrowed by a regulator, the alignment work described here comes after that question is settled. See When an appeal deadline follows a refusal: what it costs to be wrong before starting the mapping.