Controlled issuance and redemption
Evaluate approved-recipient issuance, policy epochs, transfer restrictions, frozen-holder handling, redemption-related burns, controller-supply updates, and Audit evidence.
KCC20 Regulated · Issuer evaluation workspace
Policy-aware digital assets on Kaspa.
KCC20 Regulated gives stablecoin, wrapped-asset, and controlled-token issuers a guided environment for rulebook governance, Registry-linked issuance, policy-controlled transfers, lawful-control demonstrations, supply accounting, and consolidated Audit evidence.
Built for issuers that must govern how an asset moves.
KCC20 Regulated is designed around the operating problems that appear after token creation: who may receive the asset, how policy changes are published, how controls are authorized, how supply is reconciled, and how evidence is assembled for review.
Policy-aware circulation
Model issuance tied to an external custody or deposit decision, governed circulation, withdrawal or redemption burns, and final supply reconciliation.
Institutional and business assets
Explore tokenized deposits, permissioned settlement assets, institutional credits, membership value, loyalty programs, and other policy-controlled instruments.
Six apps. One connected issuer workflow.
The regulated workspace organizes the full lifecycle into focused tabs so policy design, token operations, controls, and evidence remain understandable.
1
Overview
See wallet readiness, policy state, Registry status, regulated token selection, and the next required step.
2
Rulebook Lab
Create and update allowlists, blacklists, frozen holders, policy epochs, normalized rulebooks, and rulebook roots.
3
Deploy
Create a regulated KCC20 token with zero initial supply and bind its profile to the policy Registry reference.
4
Issue
Authorize and issue supply to an eligible recipient, then review tracked holdings, metadata, and controller supply.
5
Controls
Evaluate Freeze, Unfreeze, Registry-authorized Seizure, Forced Burn, and controller-supply reconciliation.
6
Audit
Review chronological evidence, filters, chain integrity, source coverage, pending actions, and exportable Testnet reports.
From rulebook to reconciled evidence.
The workspace treats issuance as one stage in a governed lifecycle rather than the finish line.
Define policyEligibility, restrictions, freezes, and lawful-control rules.
Publish RegistryCommit the current policy epoch and rulebook root.
Deploy tokenCreate the zero-supply regulated token profile.
Authorize issueApprove the amount and eligible recipient.
DistributeTransfer through policy-aware wallet checks.
Apply controlsFreeze, unfreeze, seize, or force burn when authorized.
Reconcile supplyAlign controller supply and tracked holder records.
Review AuditInspect evidence, chain integrity, sources, and outcomes.
How the regulated flow can support issuer operating models.
The examples below show how external issuer decisions can connect to the KCC20 Regulated lifecycle. Banking, custody, reserve, attestation, and deposit-verification systems remain issuer-specific production integrations.
Governed issue, circulation, redemption, and supply accounting
An issuer can bind approved reserve or issuance decisions to policy-aware token operations and preserve evidence across the lifecycle.
- Reserve or issuance approval
- Operator issue authorization
- Regulated issue to an eligible wallet
- Policy-controlled circulation
- Redemption request and token removal
- Controller-supply reconciliation and Audit review
External custody decisions connected to controlled token circulation
A wrapped-asset operator can use external custody or lock verification to authorize issue, then govern circulation and withdrawal-related burns.
- External asset custody or lock
- Verified issuance authorization
- Wrapped-token issue
- Policy-controlled circulation
- Withdrawal or redemption burn
- External release and reconciled token supply
External banking, custody, reserve-attestation, oracle, and deposit-verification connections are production integrations defined for each issuer. They are not implied by the Testnet demonstration.
Clear responsibilities across policy, wallet, node, and settlement.
KCC20 Regulated separates policy administration from wallet custody while keeping the operating evidence connected.
Compliance Node
Authors, normalizes, publishes, and administratively tracks rulebooks, Registry state, policy epochs, and operator decisions.
Compliance Wallet
Evaluates policy, plans transactions, verifies Registry references, tracks regulated records, reconciles supply, and projects Audit evidence.
OMA browser wallet
Holds wallet credentials locally and presents intentional review, unlock, signing, and submission steps to the user or operator.
Signatures, UTXO settlement, transaction lineage, covenant identity, and on-chain state remain anchored to Kaspa.
Transfer planning can evaluate current rulebook state before the operator signs and submits a token action.
Policy, Registry, issue, transfer, control, burn, and controller-supply evidence can be reviewed in one user-scoped journal.
Production boundary
Testnet evaluation is the beginning of the operating model—not regulatory approval.
Current availability is Testnet-10 issuer evaluation. A production launch requires dedicated infrastructure, approved governance, documented operating procedures, recovery and Audit planning, customer-specific external integrations, and a separate commercial agreement.
- Not legal certification: Testnet access does not determine whether an asset, issuer, operator, or business model satisfies any specific law or regulation.
- Not reserve attestation: Reserve custody, banking, proof-of-reserves, oracle feeds, and external asset verification are outside the demonstration unless separately integrated.
- Not shared production infrastructure: Mainnet operation requires a dedicated Compliance Wallet and Compliance Node environment with approved operator access and recovery procedures.
Design the operating model before issuing the asset.
Use KCC20 Regulated to evaluate the policy, token, controls, accounting, and Audit lifecycle for your stablecoin, wrapped asset, or controlled-token program.