Tokens and Assets

The console's token surface spans two areas. Tokenize is where an operator launches tokens and works the on-chain contract: supply, roles, access, and signing. Digital Assets is where the workspace manages an asset's data: metadata, cap table, documents, provenance, and corporate actions. A guided wizard deploys a token and the relayer pays for the deploy.

What this area covers

The Tokenize area lists the tokens this workspace has deployed and is the entry to deploying a new one. It also hosts the building blocks for real-world assets: authorities and asset schemas. The data that describes a tokenized asset (metadata, cap table, documents, provenance, corporate actions) lives in the Digital Assets area, on the asset's own page. For the concepts behind all of this, see the XKOVA TAMS overview.

Deploy a token

The create token wizard is a guided form that ends in a relayer paid deploy. There is no in-browser wallet ceremony for the deploy itself; the XKOVA Relayer submits it and pays gas. The wizard moves through a few steps, then a progress view that polls until the token is active.

Step	What you provide
Basics	The token name and symbol.
Admin Safe	An existing Safe that will hold the admin, minter, and pauser roles. The platform does not create the Safe; you point at a deployed one, typically a treasury vault.
Access	Optional on chain transfer gating: none, an allowlist, or a denylist.
Review	Confirm the configuration and submit.

After you submit, the progress view tracks the deploy until the token reaches an active status and its on chain address is available, or it reports a failed status with a reason.

Token standards

Tokens follow the gasless meta transaction model so holders can act without holding native gas. The engine supports a fungible standard for digital dollars and non-fungible and multi-token standards for assets and collections. For the differences, see Token Standards and Deploy and Mint.

Manage access and policy

Once deployed, a token's transfer access is governed by allow and deny lists, roles, mint-cap policies, and a pause control. The console exposes these so an operator can change who may hold a token and who may mint or burn it. For the model, see Access and Policy.

Real-world assets and schemas

For tokenized real-world assets, the engine separates the asset's data from its code. You publish an asset schema (the shape of the metadata) and then bind a token to it, so the data is config not code and immutable fields stay immutable by system design. From the console you can build or upload a schema, publish it, bind a token, and edit a token's fields within the rules the schema sets. The concepts are in Real-World Assets, with cap tables, distributions, corporate actions, provenance, and holder eligibility covered in their own pages in the XKOVA TAMS section.

Related

For the full surface, see the XKOVA TAMS overview. For the exact operations, see the operations list or the interactive reference.