Security token ledgerBuild proposal

A security token ledger built to the rules

Issue and manage tokenized real-world assets such as real estate and bonds on a ledger that meets the legal requirements. We supply issuance control, MPC key management and reconciliation proofs — and, if needed, build the shared consortium ledger as well. Securities firms and issuer account managers can prepare for the KSD suitability review in step with the enforcement date.

Across all productsWe prove the facts without exposing the data

Regulatory timeline

Pre-announcement
2026.10.02
Comment deadline
2026.11.11
Enforcement
2027.02.04

First in scope: private MMFs and private placement bonds (per press reports). Dates follow the pre-announcement and may change.

Track record

  • Bank of Korea CBDC pilot (2022)
  • Samsung SDS Stablecoin platform backend (2025)
  • Gyeonggi Province Stablecoin adoption study (2026)
Company & technology →

STO ledger requirements and how we meet them

What ZKRYPTO covers for each requirement in the draft security token rules.

RequirementWhat ZKRYPTO coversFeature
3+ independent consensus participantsA blockchain where KSD and each participant run their own nodeDistributed nodesShared ledger (for new builds)
2+ account management institutionsAdd participants and manage permissions through configurationShared ledger (for new builds)
KSD distributed-ledger suitability reviewReview materials and KSD integrationKSD integration
Total issuance controlRegular proof that total issuance equals total investor holdingsReconciliation proof
Issuance and redemption controlIssue only after 2+ approvals (multi-approval, MPC signing), with approval records keptIssuance control · key management

If you join a consortium platform, we connect issuance control and KSD integration to that ledger. Requirement wording will be updated after legal review and the final notice.

How we compare with building in-house or joining a platform

The three usual ways a securities firm gets a security token ledger, compared with ZKRYPTO.

CriteriaIn-house build (SI)Join a shared platformBuild on open-source ledgerZKRYPTO
CostHigh upfront build costVolume-based feesPricing not publicNo license fee; mostly development laborBuild fee or license fee
Data ownershipSecurities firmUsable within the platform's scopeSecurities firmSecurities firmDeployed at your site
CustomizationFully customStandard features onlyBuild it yourselfConfiguration plus extensions
Reconciliation proofKSD total-supply linkInternal book reconciliation built separatelyKSD total-supply linkKSD total-supply linkInternal book reconciliation built separatelyRegular proof that internal books match the ledger
Approvals & key managementDesigned separatelyWhatever the platform providesHSM or MPC purchased separatelyMulti-approval and MPC signing included

KSD joins every security token ledger as the total-supply node. On top of that, ZKRYPTO proves that the firm's internal books match the distributed ledger. Based on industry reports as of October 2026; actual terms vary by project.

Ledger structure and issuance approval

Participants each keep a copy of the ledger and run it together, reconciling totals against KSD records.

Ledger structure

Consensus node 1Consensus node 2Consensus node 33+ independent consensus participantsSecurity token ledgerEach participant keeps a copyAccount manager ASecurities firmAccount manager BSecurities firm or issuerKSDRegistration & total supplySupply reconciliation2+ account managers
  1. Consensus participants3+ independent institutions
  2. Security token ledgerEach participant keeps a copy
  3. Account managersSecurities firms & issuers, 2+
  4. KSDRegistration & total-supply reconciliation

Issuance approval

  1. RequestIssuance officer
  2. 2+ approvalsPer approval policy
  3. Split-key signingMPC
  4. Ledger recordNew ledger or shared platform
  5. Supply proofHoldings add up

No one can issue alone, and every approval is recorded

What's included

Issuance control and KSD integration on top of the core (key management and reconciliation proofs). Add the shared ledger when you need it.

Specific to this product

KSD integration

Connects to KSD registration and total-supply control

Included

Issuance control

Token issuance, redemption and admin console

Included

Keys & approvals

Keys split across parties and signed jointly (MPC, zkWallet)

Included

Reconciliation proof

Proves total issuance equals investor holdings (zero-knowledge, zkPoRL)

Add-on · available in pilot

Shared ledger

A blockchain run jointly by KSD and participants (ZKRYPTON)

Optional add-on

Private transfers

Institutions can't see each other's holdings or trades (zkTransfer, recommended for phase 2)

Who it's for

Securities firms

Run security token accounts and issuance as an account management institution

Issuer account managers

Issuers who want to manage investor accounts for their own tokens

System integrators

Bundle the ledger and proof features into your projects under license

Getting started

Timeline
About 5 months (depending on scope)
What we need from you
A link to your existing account books, and at least two participating account managers
Pricing
Pilot (4–6 weeks) → pilot fee deducted from the build fee when you signFull pricing is split into license, build and operating fees. Amounts are quoted during consultation once the scope is confirmed.

Frequently asked questions

We already use another blockchain. Is that a problem?

No. Issuance control, key management and reconciliation proofs connect to the chain you already use. Whether to switch ledgers is decided together during consultation.

How does the KSD suitability review work?

The review is taken by your organization. During the build, ZKRYPTO provides the review materials and the KSD integration.

How is this different from an open-source ledger?

With an open-source ledger you have to build internal reconciliation proofs, issuance approvals and key management yourself. ZKRYPTO includes both, so there is less audit and review material to prepare separately.

Has it been externally audited?

An external security audit of the proof and issuance code is being prepared. Results will be published when complete and added to the evaluation pack.

Set your build scope before enforcement

We'll review the gaps between your current systems and the requirements map together.

Add a trust layer to your existing services.

Stablecoins & digital assets, public trust infrastructure, research collaboration — live demos available at demo.zkrypto.com.