Skip to main content
The Cosmos Tokenization Suite (CTS) does not replace the bank’s existing core. Instead, CTS contains a digital ledger that stores and tracks tokenized deposits alongside the core. The core ledger stays authoritative. CTS manages tokenization and reconciliation between the two ledgers.

​
The two ledgers

Everything in CTS follows from there being two ledgers that must agree. The core ledger is the bank’s existing system of record, whether Fiserv, Jack Henry, or another platform. It continues to hold the deposit and remains the system from which the bank reports and audits. The digital ledger is created by CTS alongside the core. It holds the tokenized representation of those deposits and gives the bank reach into custody services, other networks, and counterparty banks. Ledger sync is the bidirectional process that keeps the two ledgers in agreement. A tokenized deposit is only meaningful while every digital-ledger token has a corresponding deposit on the core. See Reconciliation.

​
Interfaces

​
Why the policy and logs interface exists

Without the policy and logs interface, compliance, risk, and policy would require reimplementation inside the tokenization layer. Instead, they remain in the systems the bank already operates, with audit records returned to those systems.

​
Choosing the digital ledger

The bank chooses what the digital ledger runs on:
  • The Cosmos EVM ledger, which is the recommended path and the fastest to deploy
  • The bank’s own ledger, which is fully supported where the bank has an existing chain or a requirement to operate its own
See Digital Ledger Support.

​
Deployment

Two deployment models are supported, and the bank makes the choice during setup. On-premises deployment runs CTS inside the bank’s own production environment and under the bank’s own controls. Cloud deployment is managed by Cosmos Labs. The bank interacts with a cloud deployment through an API instead of operating it. The components communicate over standard protocols and are independently deployable. A production deployment can therefore split them across hosts or clusters. The deployment model is an operational choice: both models run the same components.

Talk to us about deployment

Deployment models are scoped per bank. Contact sales@cosmoslabs.io to discuss which model fits your environment and controls.
See Getting Started for its place in setup.