Manage token-level claim topic schemes in the DALP Console

View the resolved claim topic scheme chain for a token in the DALP Console and add or remove token-specific schemes from the claim-topics tab.

A topic scheme defines the data shape behind a claim topic: the typed signature an issuer's claim must match for identity and compliance checks to count it. Most assets inherit the topic schemes they need from the system and the global registry. Use this guide when one asset needs a claim topic the shared registries do not provide, and you want to register that scheme on the token itself.

The claim-topics tab shows the full set of schemes that apply to a token, resolved across three tiers, and lets a governance operator add or remove the token's own schemes without touching the shared registries every other asset depends on.

When to use this

An asset requires a verification claim that no system or global topic scheme describes.
You want to confirm which topic schemes an asset already inherits before changing its compliance configuration.
You need to review a conflict where two registries in the chain define the same topic with different data shapes.

To manage topics for every asset in a system rather than one token, add a verification topic at the system level instead. To choose which issuers may sign claims, see configure trusted issuers.

Prerequisites

The governance role on the token. Without it the claim-topics tab is read-only and the add control is hidden.
A signing wallet ready for wallet verification. Adding or removing a token scheme submits an on-chain transaction.
For adding a scheme: the token must have its own topic scheme registry. A token without one still shows its inherited schemes, but token-level management stays unavailable.

How the scheme chain resolves

DALP resolves the schemes for a token through a chain of registries, in order: the token's own registry, then the system registry, then the global registry. The claim-topics tab lists every scheme in that resolved chain and tags each row with its source.

Source	What it means	Manage it
Token	Registered on this token's own registry.	Add and remove here.
Inherited, system	Provided by the active system registry and shared by every asset.	Manage at the system level with verification topics.
Inherited, global	Provided by the shared global directory.	Manage in the global directory.

Inherited rows are read-only on this tab. They appear so you can see the full claim vocabulary an asset already carries before you add to it.

Each row shows the scheme name, the topic name and numeric topic ID, the claim signature, and its source. The signature is the typed shape the claim data must follow, expressed as ABI types.

Open the claim-topics tab

Open the token information page

In the Console sidebar, open the token you want to manage and go to its information page.

Open the claim-topics page from the Trust Registry tile

Select the Trust Registry tile, then open the topic schemes page. It opens as a full detail page with its own breadcrumb. The table lists the resolved token, system, and global schemes for the asset.

The trusted issuers for this asset live on a sibling page reached from the same Trust Registry tile. Topic schemes define the claim data shapes; trusted issuers decide whose claims for those topics count.

Add a token-level topic scheme

Add a scheme when this asset needs a claim topic the system and global registries do not provide. The new scheme applies to this token only.

Start the add flow

Select Add topic scheme. The control is available only with the governance role and only when the token has its own topic scheme registry.

Name the scheme and define its signature

Enter a human-readable name for the scheme. Then build the claim signature one field at a time, choosing each field's type and an optional name. The fields you list become the topic's typed signature, in order. The field builder is the same one that defines a system verification topic, so you describe the claim data by its types rather than typing raw ABI.

Review and confirm

The confirmation step summarizes the name and the derived signature. Confirm, then complete wallet verification. The platform submits the registration through the transaction queue.

After you submit, the tab shows a notice that the change may take a moment to appear while the network confirms it. Once it settles, the new scheme appears as a Token row and can be removed from the same tab.

Remove a token-level topic scheme

Remove a scheme this asset no longer needs. Only token-level schemes can be removed; inherited system and global rows have no remove control.

Find the Token row for the scheme and open its menu from the … button at the end of the row. Inherited rows show "Inherited, read-only" instead of a menu.

Confirm the removal

Select Remove topic scheme, then confirm in the dialog and complete wallet verification. Removing the token-level scheme does not affect the system and global schemes the token still inherits.

Before removing a scheme, confirm that no compliance rule on the asset still depends on the claim topic it defines.

When the token has no registry

A token without its own topic scheme registry cannot hold token-level schemes. The tab still lists the schemes it inherits from the system and global registries, and a notice explains that token-level management is unavailable. The inherited schemes stay in force and read-only.

Manage the same schemes through the API

The claim-topics tab and the token topic schemes API act on the same registries. Use the API to read the resolved chain or to add and remove token-level schemes from an integration or a script. For the underlying wallet, identity, claim-topic, and issuer model, see Claims and identity.

Manage token claim topics