When royalties encoded on-chain are ignored: what to do first
When royalties encoded on-chain are ignored, the priority is evidence, not confrontation. Capture the contract address, the missed transaction hash, and the payer's identity before anything else. A missed on-chain payment triggers the same contractual deadlines as a missed bank transfer, regardless of how the payment was coded.
This situation sits inside tokenised rights, where the ledger is treated as evidence, not as the right itself. Where the on-chain trail is inconclusive, we say so directly rather than build a claim on a gap — see When there is nothing to establish, we say so. What follows sets out the order of steps and who ultimately decides.
The basis
Two EU instruments frame the technical layer without replacing the underlying contract. Regulation (EU) 2023/1114 (MiCA) sets authorisation and conduct requirements for crypto-asset service providers and issuers, but it regulates the platform, not the royalty clause itself. Regulation (EU) 2023/1113 (TFR) requires information to accompany transfers of crypto-assets, which is why a transaction hash can often be matched to an identified counterpart.
Neither instrument creates the royalty obligation. The smart contract's terms and the underlying licence do that. If the platform routing the payment is authorised under MiCA, its compliance contact is a fixed point you can address; if it is not, the notice goes to the paying party directly.
What changes in practice
The practical effect is timing. If the royalty clause sets a payment window, that window does not pause because the transaction sits unconfirmed or disputed on-chain. Silence from the payer is functionally identical to a missed invoice: it starts the clock for late payment and, eventually, for termination of the licence granting the right to mint or resell.
A second effect concerns proof. On-chain data is durable, but durability is not the same as clarity. A hash confirms that something moved; it does not confirm what the parties agreed the movement meant. That gap is closed by the licence text, not by the ledger.
| Item | Why it matters |
|---|---|
| Contract address | Identifies the instrument the royalty clause is attached to |
| Transaction hash of the missed payment | Fixes the date the obligation fell due |
| Wallet address of the payer | Anchors the counterpart before any name is attached to it |
| Counterpart identity, where available | Required to address a notice that has legal effect |
| The royalty clause itself | States the trigger, the rate, and the payment window |
What to do, in order
- Export the full on-chain record — contract address, wallet addresses involved, and every transaction hash tied to the royalty stream. Your operations team can do this before counsel is involved.
- Match each hash against the counterpart's declared identity, using the transfer information required under Regulation (EU) 2023/1113 (TFR) where the paying platform is subject to it.
- Locate the royalty clause in the underlying licence or issuance terms and identify the exact trigger for payment — sale, resale, or a recurring interval.
- Send a written notice to the paying party, referencing the specific missed transaction and the clause it breaches. Counsel drafts this once the ledger export is ready.
- If the paying party is a crypto-asset service provider authorised under Regulation (EU) 2023/1114 (MiCA), address the notice to its registered compliance contact, not to a general support address.
- Set a short response deadline in the notice itself, and record the date it was sent.
Who decides
Who decides depends on the licence's dispute clause. Where the licence names a court or an arbitral forum, that forum decides, based on the on-chain record, the licence text, and the notice sent. Absent a chosen forum, the courts of the paying party's domicile typically take the claim, applying the law the licence itself designates.
The evidence weighed is rarely the code itself. It is the combination of the transaction record, the clause it is measured against, and the notice that put the payer on formal warning.
If your situation differs
If the payer disputes the amount rather than the fact of payment, the notice becomes a demand for reconciliation, not a breach letter, and the evidence step above still comes first.
If the same platform is also facing redemption requests from token holders, the two situations are usually handled separately, since royalty and redemption clauses rarely share a trigger — see When holders demand redemption in practice.
If the payer stopped responding entirely rather than disputing anything, the next step is establishing whether it can pay at all, which this page does not do.
What this page does not cover
This page does not establish who legally owns the underlying asset, nor does it verify a debtor's solvency. Those are separate questions answered by dedicated reports, not by a situational guide.
Where the dispute turns on asset ownership in Poland, our report states what the registries actually show — see Asset in Poland and its limits.
Where the dispute turns on whether the non-paying counterpart can pay at all, the equivalent report on the debtor side applies — see Debtor report poland.
This page also does not interpret the smart contract's code. A technical audit of the contract sits outside legal advice and outside this text.
Checked
Checked against Regulation (EU) 2023/1114 (MiCA) and Regulation (EU) 2023/1113 (TFR). No national implementing act is cited here because the underlying obligation sits in the licence, not in statute.
Related situations
A related but distinct problem arises when the right itself was pledged before the royalty stopped — see When a right is pledged on-chain: what to do. The evidence step is similar; the priority of claims is not.
Frequently asked questions
What is the first step when royalties encoded on-chain are ignored?
Preserve the on-chain record first: contract address, the missed transaction hash, and the payer's identity. Confrontation before evidence usually weakens the eventual notice.
Which deadline is already running?
The payment window set in the royalty clause runs from the trigger event, not from when you notice the payment is missing. A dispute over the coding does not pause it.
Who decides, and on what evidence?
The forum named in the licence's dispute clause decides, or the courts of the payer's domicile where none is named. The evidence is the transaction record, the clause, and the notice sent.
If you are dealing with royalties encoded on-chain that have stopped, we can review the licence and the ledger together and tell you, plainly, what the evidence currently supports.