The register, the compliance engine, investor communications, dividends, voting, corporate actions, insolvency and a verifiable NAV feed. Built as four services and a set of lifecycle applications, so a new event type is an application on the same rails rather than a new platform.
Who may do what: register investors, add wallets, send notices, request transfers, reserve exchange slots, sign routine NAV updates. Granted per issuance or platform-wide, revocable, logged.
The investor register as a transfer agent keeps it, with a privacy-safe twist: identity documents are stored as hashes, duplicates are refused or flagged, KYC and accreditation carry expiry dates, and one investor can hold several wallets.
Every movement of units is validated: receiver KYC, hold periods, holder caps overall and per country, blocked countries, accreditation, flow-back blocks between regions, lock-ups, freezes, and a blanket suspension during insolvency. Rejections carry the reason.
Every investor-facing event produces a stored, hash-stamped message: transfers, dividends, votes, actions, insolvency steps. The record is the evidence that the investor was told.
| Event | Flow | Controls |
|---|---|---|
| Transfers and trading | Peer to peer, exchange-executed by API, pooled-wallet slot reservations, forced transfer and reissuance for court orders or lost wallets | Compliance check on every movement; forced transfers need two approvers |
| Dividends | Declare, approve, allocate pro rata with withholding by country, pay; undeliverable amounts held for withdrawal | Four eyes on declaration; withholding table maintained by Kubermint |
| Voting | Options, quorum and threshold; ballots weighted by units at close; results broadcast | Only holders vote; ballots changeable until close |
| Corporate actions | Redemption and buyback offers, maturity, splits and consolidations, lock-ups, notices | Approved before execution; holders notified |
| Insolvency | Declaration, suspension and freeze, automatic claims, administrator admits, pro-rata recovery, burn | Two-person declaration; administrator is a named organization |
| NAV oracle | Chained, signed NAV records; root key for material changes, derivative key for routine ones; stale-data refresh; public verification endpoint | Root signing needs two approvers; verifier pinpoints tampering |
A licensed venue integrates through an API rather than a bespoke build: check eligibility before quoting, register a customer it has verified together with the customer's wallet, settle a matched trade wallet to wallet, and reserve investor slots for pooled-wallet trading. Each call runs the issuance's compliance rules; the venue never has to interpret them.
Every event above runs from one issuer console with an investor portal on the other side. We will walk you through it with your own asset.