Token management overview

Qustody Token Management exposes structured endpoints to manage QRC token lifecycles end-to-end: configure, deploy, mint, burn, transfer, govern roles, pause, freeze, and apply compliance-aware controls. Every privileged operation runs through the existing Qustody approval policy engine, is signed with post-quantum signatures, and is recorded in the audit log.

​

Two paths

Qustody supports two ways to work with tokens. Pick the path that fits your team.

​

Path A — Managed Token API

The default path for most teams. Qustody abstracts the QRC standards and exposes typed endpoints that map to common operations.

• Structured request/response schemas per standard
• Approval policy enforcement out of the box
• Idempotency keys, webhooks, and audit-log integration
• Fewer moving pieces — no Solidity tooling required

Use this path when you are happy with one of the supported QRC standards and want operational velocity. → Managed Token API reference

​

Path B — Advanced RPC + bytecode

For teams that need a custom contract or behaviour beyond the managed API.

• Compile your own Solidity, generate ABI + bytecode
• Submit deployment and contract-call transactions directly through Qustody (or through Quantum Chain RPC)
• Reuse the same approval-policy and post-quantum-signing flow

Use this path when you need custom logic, an extra extension, or compatibility with an existing on-chain contract. → Advanced RPC and bytecode

​

What you can do

​

How a token operation flows

Every token operation reuses the existing transaction state machine: See the full token operation lifecycle for deploy and mint/burn diagrams.

​

Where to next