Skip to content

For issuers: compliance by consensus

Live on testnet For issuers Simplifies the whitepaper, sections 1.4 and 1.5

Whatever power an issuer has over an asset is declared the moment the asset is created, visible to every holder, and impossible to extend afterwards.

Issuing takes one transaction

On Sequentia, an asset is not a contract someone deploys. It is a kind of output the chain understands from the start. Creating one takes a single transaction and about ten seconds, from the web wallet or from Sequentia Core.

What you decide at that moment is fixed for the life of the asset: its name, its ticker, how finely it divides, your internet domain, and whether it is supervised.

Your domain proves the name

Anyone can issue a token and call it “USDT”. What stops them fooling your customers is that a name is only shown when the owner of a website says the asset is theirs.

  1. When you issue, you write a short declaration: name, ticker, decimals, your domain, your public key.
  2. The asset’s id is computed from the issuance transaction and that declaration together. Change one character and you get a different id, which is a different asset.
  3. You publish a small file on your domain that names the asset id. Only whoever controls tether.to can put a file on tether.to.
  4. A registry checks all of it and marks the asset verified. Wallets then show the name.

The chain itself stores only the id. A name can never be added or corrected later, and a registry decides what a wallet displays, never what the chain accepts.

Step by step: Issue an asset.

Supervised assets

Some assets represent a claim the issuer is legally obliged to be able to arrest. A fiat-backed stablecoin is the obvious case. For these, an issuer can declare the asset supervised.

A supervised asset is one whose issuer can freeze the coins held at a given address, by a rule every node enforces.

What the issuer can do

  • Freeze an address. The issuer publishes a signed freeze record naming an address. From the next block, every node rejects any transaction spending coins of that asset held there. Nobody can move them, the issuer included.
  • Lift the freeze, with another signature.

What the issuer can never do

  • Spend a holder’s coins. Freezing stops a transfer; it never redirects one. No issuer key can move somebody else’s coins.
  • Mint with the freeze keys. Creating new units is a separate authority. A stolen freeze key cannot print money.
  • Change the terms. The supervision keys and options are part of the asset id. Altered terms give a different id: a different asset, holding no coins.
  • Hide it. The declaration sits in the issuance transaction. Any holder can check, before accepting the asset, exactly what its issuer will ever be able to do.

An unsupervised asset can never become supervised, and a supervised one can never be released. The only route is to issue a different asset.

Whitepaper 1.5Seizure and burning, and why supervised assets must be reissuable

Regulators sometimes ask for more than a freeze. Both further powers are derived from freezing, not added to it:

  • a permanent freeze is, economically, a burn;
  • a permanent freeze, plus issuing the same amount again to the address a court names, is a seizure.

This is why consensus refuses to grant supervision to an issuer whose asset cannot be reissued. It is also the freeze, burn and reissue cycle that large stablecoin issuers already run on other chains.

Whitepaper 1.5Two keys, so that a stolen key is an incident and not a catastrophe

A supervised asset names two public keys.

  • The operational key signs freezes and unfreezes. It is used often, so it is the one exposed to theft.
  • The recovery key signs only one thing: a record replacing a key. It lives in cold storage.

The operational key cannot replace either key, not even itself. A thief who obtains it can freeze holders and nothing more, and the issuer rotates the stolen key with the recovery key and the incident is closed.

Whitepaper 1.5What can and cannot be frozen

Two limits are deliberate, so that consensus never destroys value belonging to someone other than the frozen party.

Only spending is blocked. Paying into a frozen address stays legal. This is what makes it useful to freeze a known destination in advance: funds arrive already trapped.

Only single-owner addresses can be frozen. A shared script, such as a Lightning channel or a swap contract, is never frozen. Freezing one would trap an innocent counterparty’s whole balance, and in any contract racing a deadline it would hand the frozen party the timeout.

Supervised assets have been active on the testnet since block 94,600. Operator documentation: supervised-assets.md.

Why this is better than what exists

On most chains, an issuer’s control over a token is whatever its contract says, which few holders read and which is often upgradeable. On Liquid’s asset platform, control works through a trusted operator that co-signs every transfer and must stay online for the asset to move at all.

On Sequentia the power is narrow, declared and permanent, and a supervised asset is still a bearer asset: it moves between holders without asking anyone, pays fees, trades on the DEX and travels over Lightning like any other.

Three ways to enforce a policy

A power to freeze is enough for a stablecoin. A security may need more: only approved investors may hold it, transfers may be capped, tokens may vest. Sequentia offers three levels, and an issuer chooses per asset.

Supervised asset OpenAMP OpenDAMP
What it enforces Freeze and unfreeze of addresses Any rule a server can check: approved holders, categories, velocity limits, holder caps, lock-in, vesting, freezing, clawback Whitelist, blacklist, transfer limits, time windows
Who enforces it Every node, by consensus The issuer’s policy server, which co-signs each transfer Every node, through covenants
Server in the path of a transfer No Yes No
Holders Anyone Registered holders Holders the policy allows
Best for Stablecoins and other bearer assets Securities needing rich, changeable rules Regulated assets that must move without the issuer online

OpenAMP is an open-source, self-hostable equivalent of Blockstream’s AMP2. The asset id commits to the issuer’s policy key, so anyone can verify offline which key governs an asset. Every registration, rule change, freeze, approval, refusal and clawback goes into a public hash-chained log. A live instance runs on the testnet.

OpenDAMP moves enforcement from a server into the chain: the asset’s policy is checked by Simplicity covenants that every node runs.

SeqPal is a proof-of-concept service that walks an issuer through structuring, issuing and servicing a security token, with the enforcement level chosen per issuance.

Read further