Every Kubermint engagement runs on the same production platform: public EVM chains or permissioned networks, compliance logic in the token contract, and an operator console that a compliance officer can run. You do not license it; it is how we deliver the service.
The standard determines what controls the issuer has. We choose by instrument, venue and regulator, and explain the trade-offs in the structure paper.
| Standard | What it is | When we use it |
|---|---|---|
| ERC-7943 (uRWA) | A universal real-world asset interface layered over ERC-20, ERC-721 or ERC-1155: whitelisting, freeze, forced transfer and transfer validation in one interface | Our default for regulated instruments. The Kubermint production platform implements it across all three base standards with a live operator console. |
| ERC-3643 | Permissioned token with an on-chain identity registry and modular compliance rules | Issuers whose venue or custodian requires it, or who want the identity registry pattern |
| ERC-1400 / 1410 | Security token with partitions (tranches) and document management | Multi-class instruments and structures with lock-up tranches |
| ERC-1155 | Multi-token contract; many classes in one contract | Carbon credits (project, vintage and methodology as classes), fund series, receivable pools |
| ERC-4626 | Tokenized vault standard for yield-bearing positions | Fund and credit strategies where the token represents a share of a pool |
| ERC-20 | Plain fungible token | Only for unrestricted assets such as some commodity receipts, and only where the regulator agrees |
Ethereum mainnet, Polygon, Arbitrum, Base and Avalanche. Chosen by custody support, settlement currency availability and gas economics for the expected transaction pattern.
Hyperledger Besu and other private EVM deployments where the regulator or the institution requires a closed network. Same contracts, same console.
Integrations with institutional custodians and MPC wallet infrastructure for the issuer's treasury and for investors who do not hold their own keys. Policy engines enforce approval thresholds on every issuer transaction.
KYC, KYB, sanctions and accreditation via specialist providers, with results written to the whitelist. Reusable verification across issuances on the same platform.
Price feeds for commodities and stablecoins, proof of reserve attestations for vaulted assets, and registry data for carbon. Signed valuation uploads for illiquid assets.
Fiat through partner banks and payment providers; regulated stablecoins where the jurisdiction permits. Delivery versus payment on issuance and secondary transfers.
Every issuer action runs through the console: onboarding approvals, minting against verified subscriptions, whitelist maintenance, freezes, forced transfers, distributions, corporate actions and reporting. Each action has a maker and a checker, a reason field and an immutable log entry. The console is what makes the platform operable by a compliance officer without developer support.
It is live today on Kubermint deployments and is the same software we operate for every plan and can transfer in house under the Enterprise plan.
We can share the interface specification, console walkthrough and a sample audit report under NDA.