Smart contract and licence alignment: stages and deadlines

Smart contract and licence alignment runs through four stages: mapping licence clauses to contract logic, drafting a gap list, testing the patched functions, and locking the reviewed version against the licence text it matches. Each stage ends with a written sign-off. Skipping a sign-off does not stop deployment, but it removes the record you would need if a dispute follows.

This procedure sits inside the wider work on tokenised rights and digital objects, and the reports built on top of it start from a stricter premise: When there is nothing to establish, we say so. That distinction matters here too. Alignment work brings a contract into line with a licence that already exists; it does not create a right that was never recorded anywhere.

What changes if the code and the licence diverge

A licence sets out who may transfer, sub-licence, or terminate a right, and under what conditions. A smart contract encodes only what its functions actually do. When the two drift apart, the contract may allow a transfer the licence forbids, or block a termination the licence permits. The gap is invisible until someone tries to exercise the right the contract does not support.

The practical effect is timing risk, not a change in the underlying right. A misaligned contract does not cancel the licence. It delays the moment a party can act on it, and it shifts the burden of proof onto whoever claims the contract reflects the licence correctly.

Steps to bring the code and the licence into line

1. List every clause with a contractual trigger. The legal team pulls the current licence text and marks transfer, royalty, termination, and sub-licensing clauses before any code review starts.
2. Match each clause to a contract function. The technical lead checks the deployed code against the list and marks any clause with no matching function as a gap.
3. Route the gap list for confirmation. The list goes to the licensor, not to the platform operating the contract. If the issuer and the platform are the same party or affiliated, confirmation follows a different path — see The issuer and the platform are related token issuance.
4. Patch the functions that do not match. The development team rewrites only the flagged functions, keeping the rest of the contract untouched to limit the scope of re-testing.
5. Test every clause trigger at least once. The test set has to exercise transfer, royalty, and termination paths individually, not just the happy path of a single transaction.
6. Lock the reviewed version. The commit hash of the patched contract is recorded together with the exact licence version it matches, dated and signed off by both teams.

Who decides and by when

The licensor confirms the gap list, and no other party can substitute for that step. A licensor with in-house counsel typically responds within a few working days of receiving the list. Where the licensor has no internal legal function, the response usually takes longer, and the delay sits with the licensee, not with the platform.

Typical branches

If the licence has a fixed term and the contract has none coded into it, the contract needs an explicit expiry function before deployment, not a side agreement to remember the date manually.

If the platform hosting the contract also issues the underlying token, the confirmation step in stage three does not run as an arm's-length exchange. It runs as an internal review, and the written record of that review becomes the only evidence of independent sign-off.

If the counterpart does not respond to the gap list within the agreed window, the licensee has two options: pause deployment until confirmation arrives, or deploy against the licensee's own reading of the licence and accept that any dispute later starts from that unilateral reading.

What this page does not cover

This page describes the procedure, not the underlying licence terms themselves, and not how a tokenised right is first recorded. It does not set a fixed number of days for any stage, because that depends on the complexity of the licence and the number of parties who need to sign off. It does not cover valuation or dispute resolution once a gap has already caused a loss.

Sources and limit

Where the same misalignment surfaces after a right has already been pledged, the cost of getting it wrong is described separately: Asset report before a right is pledged. Where the trigger is a sale of the claim rather than a pledge, the first practical step differs: Debtor report before selling the claim.

This page sets out a procedure and names no statute, regulation, or article. The acts governing crypto-asset markets and fund transfer information sit in a separate layer of this site, tied to jurisdiction, and are not cited here because a procedural page of this kind cannot carry a national citation that has not been checked against the relevant national register. The steps above reflect standing practice, checked internally in 2025, not a legal requirement with a fixed deadline.

Related reading

For the recordal step that usually precedes this alignment work, see How on-chain and off-chain recordal tokenised rights runs in.

FAQ

How long does smart contract and licence alignment take in practice?
A single licence with a short clause list can be aligned in a few working weeks. A licence covering multiple rights, or requiring sign-off from several affiliated parties, regularly takes longer, mainly because the confirmation stage depends on the licensor's own response time.

Which documents are needed to start?
The current licence text, the repository holding the deployed contract code, any prior audit report on that code, and a list of the people authorised to sign off on the licensor's side.

What happens if the other side does not respond?
The gap list should state a response window when it is sent. If that window passes without a reply, the licensee either holds deployment until confirmation arrives or proceeds on its own reading of the licence, in which case the record of that decision becomes central if a dispute follows.

— Aleks Vaher, AURELIS