Proposal: Korean TTA Blockchain Reliability Verification of the Canton Private Synchronizer
- Author: John Yang (Nodeinfra / Mirny Inc.)
- Status: Submitted
- Created: 2026-06-08
- Label: regulatory-compliance
- Champion: Teagan Buckley
Abstract
This proposal requests funding to take the Canton private synchronizer through Korea's TTA Blockchain Reliability Verification (BRV, 블록체인 신뢰성 검증) ahead of the new Korean STO law's January 2027 effective date. BRV is TTA's blockchain-specific reliability and security evaluation, and its evaluation framework is built on the National Cyber Security Center's 「국가ㆍ공공기관 도입을 위한 블록체인 암호기술 가이드라인」 (Blockchain Cryptographic Technology Guideline for Adoption by National & Public Institutions, 2020.12) — a permissioned-blockchain security standard co-authored by the National Intelligence Service, the Ministry of Science and ICT, the National Security Research Institute, and TTA. That guideline is the standard against which Korea's financial-infrastructure operators evaluate a permissioned chain, and BRV is the most credible blockchain-specific reliability credential available for chain eligibility.
Nodeinfra, a Korea-based Daml/Canton firm with prior blockchain-TTA experience, is already engaged with the Canton Foundation and two leading Korean financial groups to build STO issuance platforms on Canton (counterparties under strict NDA). Verification is what makes those platforms recognizable and productionizable in a market that does not yet distinguish Canton's permissioned-substrate option from public-chain alternatives. Critically, the BRV result attaches to the Canton private synchronizer software itself, not to Nodeinfra or any single operator — every ecosystem participant inherits the credential, which is what makes this a public good rather than a private commercial asset. All non-NDA artifacts will be open-sourced under Apache 2.0 as a reusable blueprint for analogous verification regimes in Japan, Taiwan, Hong Kong, and other APAC jurisdictions.
Motivation
Korean STO regulation is now law. The 「전자증권법」 (Electronic Securities Act) and 「자본시장법」 (Capital Markets Act) amendments passed the National Assembly on 2026-01-15 and take effect in January 2027. For the first time, distributed ledgers have legal status as the "electronic registration account book" (전자등록계좌부). This creates a hard, dated ~12-month window before STO issuance and trading can begin.
The market this opens is large and concrete. BCG projects Korean tokenized securities at KRW 119T (~USD 85B) by 2026, KRW 233T by 2028, and KRW 367T (~USD 265B) by 2030 — 14.5% of Korean GDP (BCG forecast, as reported in the Korean financial press, 2026). These figures are at the optimistic end of tokenization forecasts; the case for verification holds well below them. KDX (KRX-led) and NXT (Nextrade-led) consortia have already been selected by the FSC as preliminary OTC trading platform operators. Securities firms (Mirae, Shinhan, NH, KB, and others) are racing to lock in infrastructure choices now, well before the effective date.
By design, Korean regulation pushes this market onto private (permissioned) blockchains. The amended Electronic Securities Act preserves total-supply oversight and right-presumption rules that are structurally hard to square with public-chain issuance. The Canton private synchronizer is a strong structural fit: permissioned, privacy-preserving, deterministic finality.
The regime is also structurally two-layered, and this matters for who actually selects the chain. Settlement and registration infrastructure is operated by a small set of statutorily-recognized financial institutions: KSD (한국예탁결제원), FSI (금융보안원), KFTC (금융결제원), and additional public-interest financial bodies designated under the Electronic Securities Act framework. Securities firms, banks, and asset managers participate as application-layer counterparties on top of that infrastructure, not as operators of it. For a permissioned chain to fit the regime, its validator set has to sit at the infrastructure-operator layer. A BFT consensus distributed across three or more of these institutions is precisely the trust model Korean regulators expect from a private chain. Canton's private synchronizer with sub-net architecture maps onto this structure directly.
But fit is not recognition. The dominant private-blockchain infrastructures in Korea today are Hyperledger Besu and Hyperledger Fabric. Those are the defaults Korean regulators, securities firms, and systems integrators reach for when they think "permissioned blockchain." Canton, despite having a structurally superior private-synchronizer option for exactly this use case, is often mistakenly perceived as just another public-network altcoin. Educating regulators and the market that Canton's private synchronizer exists — and that it is the right substrate for Korean STO issuance — is itself a meaningful part of the work this grant funds.
Korean STO regulation does not strictly mandate any particular verification. But in a market with that level of misperception, TTA BRV is the most credible way to put Canton on equal institutional footing with the Besu / Fabric defaults — and the only path that tests the exact security properties the infrastructure operators care about. Its evaluation framework is built on the National Cyber Security Center's permissioned-blockchain cryptographic-technology guideline, co-authored by the NIS, MSIT, the National Security Research Institute, and TTA. That guideline is the reference the public-sector and quasi-public security and compliance teams at KSD, FSI, and KFTC apply when they assess a permissioned chain. The guideline targets exactly the architecture in question — permissioned blockchains adopted by national and public institutions — and sets out concrete requirements across cryptographic usage, account and key management, data-transmission security, consensus, ledger integrity, and smart contracts. Clearing BRV simultaneously surfaces the private synchronizer to the people choosing infrastructure and validates it against the precise reliability and security attributes that map onto STO issuance and oversight needs. The blockchain-specific nature of the credential is the point: it is direct evidence on consensus fault tolerance, key management, and ledger integrity, not a generic enterprise-software seal.
Demand for Canton on this substrate is not hypothetical. Nodeinfra, with the help of the Canton Foundation, is already engaged with two leading Korean financial groups to build STO issuance platforms on Canton (counterparties under strict NDA). But none of this can productionize until the chain itself is verified.
To date, no DLT has completed BRV with a privacy-preserving sub-net architecture, and no foreign chain has obtained it either. There are three reasons: the verification is specific to Korean regulations and the National Cyber Security Center guideline that underpins it; no other DLT structurally aligns with the amended Electronic Securities Act the way Canton does; and the STO regulatory framework itself was only finalized in January 2026. Canton would be the first. It enters the buildout window with a credential nobody else holds, just as Korean securities firms are choosing the substrate they will run STOs on for the next decade. The window for first-mover capture is open precisely because the rules just got drawn.
The strategic payoff extends well beyond Korea in two dimensions. First, ecosystem lock-in: Korean financial institutions onboard onto the private synchronizer now, while regulation requires permissioned substrates. When Korean regulation matures to permit cross-domain interop, those institutions are positioned to seamlessly extend onto the global Canton synchronizer and align with CC and the broader Canton economy. Same chain, same software, same trust model — only the synchronizer scope changes. Second, APAC blueprint: the open-sourced verification artifacts are intentionally structured to be portable, with mapping documents calling out Korea-specific versus reusable assumptions. Once the playbook exists, the marginal cost of clearing analogous verifications in Japan, Taiwan, Hong Kong, and other regulated APAC markets drops substantially.
Specification
1. Objective
Take the Canton private synchronizer through Korea's TTA BRV and publish all non-NDA artifacts (submission package, NCSC-guideline compliance mapping, deployment scripts, test harness, post-mortem) under Apache 2.0 as a reusable APAC blueprint.
The intended outcome: at the moment Korean STO infrastructure selection is happening (mid-2026 through January 2027), the Canton private synchronizer holds a credential that puts it in the institutional selection pool. The credential is recognizable to procurement, risk, and compliance teams at KSD, FSI, KFTC, and peer infrastructure operators, and to their counterparts at securities firms downstream. The credential attaches to the Canton software and is therefore inherited by every team building on the private synchronizer, and the engineering artifacts to clear analogous regimes elsewhere are publicly available under Apache 2.0.
2. Implementation Mechanics
Work breaks into three phases, each part of a single end-to-end verification cycle:
-
Scope confirmation with TTA. Engage TTA, confirm the BRV evaluation scope for the Canton private synchronizer, and publish a submission package outline mapped against the National Cyber Security Center guideline's compliance domains: cryptographic usage standards, account and key management, data-transmission security, consensus protocol, ledger, and smart contracts.
-
Submission package preparation. Build the reproducible verification environment (deployment scripts, NUMA-aware host configuration, Postgres backing, Canton 3.x runtime), the test harness covering the reliability and security criteria, and the documentation set required for TTA evaluation. Open the public GitHub repo for the open-source artifacts at this stage.
-
TTA evaluation cycle. Submit, respond to findings through the standard TTA evaluation cadence (~2-month formal evaluation, with potential gap-closing work between rounds), and shepherd the package through to an issued verification result.
Verification target — what TTA will verify about the Canton private synchronizer:
| Company / Developer | Platform / Solution | TTA Verification Type | Key Verified Metrics |
|---|
| Nodeinfra (Mirny Inc.) — for the Canton Foundation ecosystem | Canton Private Network | Blockchain Reliability Verification | Demonstrated TPS scalability; BFT fault tolerance and total-supply preservation; account and key-management security; smart-contract and source-code security; privacy-preserving sub-net architecture; node-role separation aligned with the amended Electronic Securities Act |
Supporting notes:
- Electronic Securities Act alignment: the verification maps directly onto the Act's structure. BFT fault tolerance and total-supply preservation under node faults map onto the Act's total-supply oversight and right-presumption rules; account and key management map onto the issuer, registrar, and account-management institution roles; ledger integrity maps onto right-presumption. The verification is a literal demonstration of regulatory fit, not a generic enterprise-software seal.
- NCSC guideline as the evaluation backbone: the guideline targets permissioned blockchains adopted by national and public institutions and sets out compliance requirements across cryptographic usage, account/key management, data-transmission security, consensus, ledger, and smart contracts. The Canton private synchronizer is assessed against those requirements directly.
- Privacy as differentiator: Canton's privacy-preserving sub-net architecture is the property no other Korean private-chain precedent has. The Korean STO market is converging on permissioned chains specifically because of the total-supply oversight and right-presumption rules. Canton is the only candidate whose privacy model is structurally aligned with them.
- Cryptographic-conformance work: the guideline recommends cryptographic algorithms from the Korea Cryptographic Module Validation Program (KCMVP) set, while also permitting standards-body algorithms (ISO/IEC, IETF, and equivalents). A concrete deliverable is a conformance review of Canton's cryptographic primitives against the guideline's KCMVP set and its standards-body allowance, documenting equivalence or surfacing any gap for upstream resolution.
- Throughput approach: Canton's throughput capacity has been independently demonstrated by Proof Group at ~100K TPS in a 12-hour lab benchmark on bare-metal infrastructure for a fellow Super Validator's use case. The benchmark ran on 10 machines with 4 synchronizers, 17 participants, and 824 cores on Canton 3.5.0, using Daml asset transfers with full interpretation, atomic settlement, and per-stakeholder encrypted view trees. For this grant, Nodeinfra will build a TTA-tailored evaluation environment and benchmark harness on top of the upstream Canton open-source performance benchmark suite — the same open-source tooling Proof Group's fork leveraged. The harness is purpose-built for performance and reliability reproducibility against the BRV criteria, and ships as a substantive engineering artifact in the open-source release.
Open-source surface (Apache 2.0):
- BRV submission package (redacted only where TTA or counterparties require NDA)
- NCSC-guideline compliance mapping for the Canton private synchronizer
- Deployment / configuration scripts for the verification environment
- Test harness used to satisfy TTA's evaluation checklist
- Post-mortem describing findings, fixes, and the engineering work required to pass
- Mapping documents calling out Korea-specific assumptions vs. portable artifacts (for APAC reuse)
The NDA carve-out plan — naming exactly what will and will not be open-sourced — is delivered at the start of Milestone 1 and is a precondition for Milestone 1 acceptance. The open-source surface is therefore defined and accepted before any payment, not promised afterward.
3. Validator Architecture
The Canton private synchronizer is intended to operate under a BFT validator set composed of Korea's statutorily-recognized financial infrastructure institutions. Expected core participants:
- KSD (Korea Securities Depository, 한국예탁결제원) — electronic registration anchor under the Electronic Securities Act
- FSI (Financial Security Institute, 금융보안원) — financial-sector cybersecurity authority
- KFTC (Korea Financial Telecommunications & Clearings Institute, 금융결제원) — interbank clearing infrastructure
Additional candidate validators may be drawn from public-interest financial bodies designated under the Electronic Securities Act and Capital Markets Act framework (e.g., KRX / Koscom, KSFC, BOK in roles relevant to wholesale settlement). Final composition is a regulatory and governance decision outside the scope of this grant; the verification work itself is validator-agnostic.
This validator architecture is a stronger institutional story than a securities-firm-operated chain. The three core institutions cover distinct verticals — depository, security, clearing — with no cross-ownership and no shared commercial counterparties, so commercially-motivated collusion against the BFT 51% rule is not a realistic compromise vector. Securities firms, banks, and asset managers transact on the network as application-layer participants, not as consensus operators. This preserves the same separation of duties the amended Electronic Securities Act establishes between issuer / registrar / account-management roles and infrastructure operators.
This is also where the case for BRV specifically (rather than lighter credentials) lives. The infrastructure-operator tier evaluates a permissioned chain against the National Cyber Security Center guideline, which BRV operationalizes; BRV is the blockchain-specific reliability credential that directly maps onto that guideline, where independent audits and ISO 27001 serve only as general supporting evidence. Whether BRV becomes a formal requirement is still being settled in the KSD-led standards work; as a recognized, blockchain-specific verification it is the credential most likely to be relied on in the technical-review process, and the one that puts Canton on equal footing with the Besu/Fabric defaults.
4. Architectural Alignment
The verification work validates existing Canton private synchronizer architecture; it does not modify protocol behavior. Specifically:
- The privacy sub-net model, BFT consensus, and deterministic finality being verified are upstream Canton properties; the verification asserts what already exists.
- Gap-closing engineering, if any, is configuration- and deployment-side (test harness, observability, deployment hardening, cryptographic-conformance documentation), not protocol-side.
- Any protocol-side gap surfaced by TTA evaluation will be raised upstream through standard Canton CIP / release processes, not as part of this grant deliverable.
- This work is directly aligned with the multi-synchronizer roadmap, demonstrating the Canton private synchronizer as a regulated production substrate in a major jurisdiction — strengthening the case for the same architecture across other jurisdictions.
5. Backward Compatibility
No backward compatibility impact. The verification work does not modify Canton protocol, ledger semantics, or existing integration surfaces. Existing deployments, applications, and dependent systems are unaffected.
Milestones and Deliverables
Milestone 1: Kickoff and TTA Engagement
- Estimated Delivery: 1–2 months after grant approval
- Focus: Confirm BRV evaluation scope with TTA against the NCSC guideline, publish submission package outline, open the public GitHub repo for open-source artifacts.
- Deliverables / Value Metrics:
- Written acknowledgement from TTA confirming engagement and scope (publicly verifiable)
- Public GitHub repository established under Apache 2.0
- Published submission package outline mapped against the NCSC guideline's compliance domains
- Published NDA carve-out plan naming what will and will not be open-sourced — delivered and accepted before Milestone 1 payment
Milestone 2: Blockchain Reliability Verification Issued
- Estimated Delivery: ~5 months after grant approval
- Focus: Submission, evaluation cycle response, gap-closing engineering, verification result issuance.
- Deliverables / Value Metrics:
- TTA-issued BRV result for the Canton private synchronizer (publicly verifiable)
- All non-NDA artifacts published to repo (submission package, NCSC-guideline compliance mapping, deployment scripts, test harness, post-mortem)
- Canton private synchronizer holds a recognized blockchain-reliability credential for Korean STO infrastructure selection at both the infrastructure-operator tier (KSD, FSI, KFTC, peer institutions) and downstream by securities firms
- Mapping documents identifying Korea-specific vs. portable assumptions, enabling reuse for analogous APAC verifications
Acceptance Criteria
The Tech & Ops Committee will evaluate completion based on:
- Milestone 1: Public, verifiable TTA acknowledgement letter; public repository established with submission package outline published and NDA carve-out plan delivered — the plan is a precondition for Milestone 1 payment; if the open-source surface is inadequate, grantor and grantee re-scope before payment.
- Milestone 2: TTA-issued BRV result publicly verifiable; all named non-NDA artifacts published under Apache 2.0; post-mortem published describing findings and engineering work.
- Ecosystem value indicators (informational, not gate; these are the adoption metrics defined in Growth and Adoption):
- Canton private synchronizer cited in RFPs, PoCs, or technical evaluations at KSD, FSI, KFTC, or peer infrastructure institutions designated under the Electronic Securities Act framework, or in downstream Korean securities-firm STO infrastructure selection processes.
- Open-source artifacts referenced by at least one team pursuing analogous verification in another jurisdiction (Japan, Taiwan, Hong Kong, or comparable) within 12 months of result issuance.
Note on artifact-style gates: the verification result is by nature binary — Canton either holds a passing BRV result or it doesn't. Without it, Canton enters infrastructure selection without the blockchain-specific credential its competitors will be measured against; with it, Canton is in the selection pool on equal footing. The Milestone 2 gate accordingly conditions payment on the credential itself rather than on downstream adoption. The 12-month ecosystem indicators are tracked separately as the lagged adoption outcomes the credential unlocks.
Scheduled adoption reporting: although these indicators do not gate payment, Nodeinfra commits to publishing a public adoption-tracking update in the GitHub repo at 6 and 12 months after BRV result issuance, reporting progress against the ecosystem value indicators above (operator-tier and securities-firm citations; cross-jurisdiction artifact reuse). This makes adoption accountable on a fixed schedule without conditioning grant payment on outcomes outside the grantee's control.
Funding
Total Funding Request: 2,200,000 CC (~$330,000 USD at the $0.15 / CC reference rate; funding is denominated and paid in CC — see Volatility Stipulation).
Payment Breakdown by Milestone
| Milestone | Payment on Acceptance |
|---|
| Milestone 1 — Kickoff and TTA Engagement | 374,000 CC |
| Milestone 2 — Blockchain Reliability Verification Issued | 1,826,000 CC |
| Total | 2,200,000 CC |
Indicative Line-Item Breakdown
The $330,000 / 2,200,000 CC ask decomposes approximately as follows:
| Line item | Headcount | Rate | Duration | USD | CC (@$0.15) |
|---|
| Blockchain engineers | 4 | ~$11K/mo loaded | 5 months | $220,000 | 1,466,000 CC |
| Security engineer | 1 | ~$12K/mo loaded | 5 months | $60,000 | 400,000 CC |
| Admin (partial allocation) | 1 | ~$2,000/mo | 5 months | $10,000 | 67,000 CC |
| Infrastructure (cloud) | — | — | 5 months | $25,000 | 167,000 CC |
| TTA evaluation fee | — | — | — | $15,000 | 100,000 CC |
| Total | | | | $330,000 | 2,200,000 CC |
Caveats:
- Rates shown reflect compensation for engineers with the specialized Canton / Daml and Korean TTA-process expertise this verification requires; actual compensation is set by Nodeinfra.
- Labor reflects partial grant-coverage of total team time; Nodeinfra commercial revenue (NaaS + active engagements) covers the remainder.
- BRV is a paid evaluation; the team budgets for the full evaluation fee. The figure shown is an estimate, confirmed against TTA's actual quote during Milestone 1 scope confirmation.
- Infrastructure is for the cloud-based verification environment over the 5-month evaluation cycle.
- If TTA's actual quote materially exceeds the estimate, the difference is absorbed from contingency in the labor line; Nodeinfra carries the residual.
Volatility Stipulation
Project duration is targeted at approximately 5 months. Should the project timeline extend beyond 5 months due to Committee-requested scope changes, any remaining milestones will be renegotiated to account for significant USD/CC price volatility.
External delays (e.g., TTA-side evaluation timeline) do not trigger renegotiation; the team accepts that volatility risk and reports transparently in monthly status updates.
Funding Rationale
- 374,000 CC at Milestone 1 (~17% of total) covers TTA evaluation fees, infrastructure costs for the verification environment (cloud), and a portion of the engineering resources required during the ~2-month evaluation preparation and submission cycle (test harness build, deployment hardening, documentation set). The kickoff payment is intentionally bounded — it sustains the team into the formal evaluation phase but is not a reward for "engagement"; the bulk of value is concentrated in the actual verification result.
- 1,826,000 CC at Milestone 2 (~83% of total) is conditioned on the deliverable that creates ecosystem value: a publicly-verifiable BRV result plus the full open-source artifact set. This recovers the remaining engineering and infrastructure expense (cloud) from the verification cycle. It also sustains Nodeinfra's runway as it continues its separate, commercial work onboarding leading Korean financial groups onto the now-verified Canton private synchronizer. That onboarding work itself is out of scope (see Out of Scope below).
- Why 1:5 weighting rather than 1:1: the verification result is binary. Either the Canton private synchronizer holds a passing BRV result or it doesn't. The committee is paying for that credential, not for incremental progress, and the funding structure reflects that.
Out of Scope
This grant does not fund:
- Productization of an STO issuance platform on top of the synchronizer
- Commercial / BD work with Korean securities firms (a separate Nodeinfra commercial workstream)
- Legal / regulatory education engagement with a Korean law firm (the compliance-opinion and briefing workstream described under Growth and Adoption — funded separately, not by this grant)
- TTA GS Class 1 certification (the general software-quality seal under the Software Promotion Act) — a useful complementary credential pursued separately as a potential follow-on, not part of this grant
- Re-verification or annual re-verification beyond initial issuance (repository maintenance itself continues under Nodeinfra's APAC practice — see Sustainability)
- Korean legal-entity setup or other corporate / regulatory infrastructure outside the verification itself
Licensing
All open-source artifacts produced under this grant — submission package, NCSC-guideline compliance mapping, deployment / configuration scripts, test harness, TTA-tailored benchmark harness, and post-mortem — will be released under the Apache License 2.0.
Sustainability
The BRV result is a standing, issued credential: once granted it requires no ongoing funding to remain valid for the infrastructure-selection window it targets.
Nodeinfra maintains the public Apache 2.0 repository — compliance mappings, test harness, deployment scripts, and benchmark harness — as a standing asset of its commercial APAC verification practice, so upkeep is self-funded beyond the grant rather than abandoned at close.
Any protocol-side gap surfaced after issuance is routed to upstream Canton maintainers through the standard CIP / release process, with Nodeinfra acting as the reporting party given its production operational experience.
Re-verification or annual renewal, if a future Korean rule requires it, is a separate engagement and is not funded here — see Out of Scope.
Co-Marketing
Upon verification result issuance, Nodeinfra will collaborate with the Canton Foundation on:
- Joint announcement of BRV in both English and Korean
- Technical blog documenting the verification process, NCSC-guideline compliance mapping, and reusable lessons for analogous verification regimes
- Korean-press outreach (전자신문, 보안뉴스, 한국경제, etc.) — Korean-language explainer positioning Canton in the STO infrastructure landscape, co-branded with Canton Foundation
- Ecosystem presentations at Korean blockchain / FinTech events and at Canton-related conferences
- Submission-package open-sourcing as marketing: the public Apache 2.0 artifact set itself is co-marketing material, showcasing Canton's verifiability to non-Korean APAC markets
Growth and Adoption
Adoption runs on two main strategies that reach the same downstream buyers from opposite directions, plus a third that extends the work across APAC. The shared obstacle all three overcome is the market's current misperception of Canton as "just another public-chain altcoin" rather than a permissioned STO substrate.
Strategy 1 — Top-down: operator-tier selection and blessing
The infrastructure-operator tier (KSD, FSI, KFTC, and peer institutions designated under the Electronic Securities Act framework) selects the chain first. The issued BRV result enters their procurement and technical-review workflows as a recognized blockchain-specific credential — the same credential their security and compliance teams apply against the NCSC guideline. Once an operator-tier institution selects and blesses the Canton private synchronizer, that decision cascades downward: securities firms, banks, and asset managers inherit the selection as application-layer participants without re-running chain-level diligence.
Strategy 2 — Bottom-up: Nodeinfra's STO platform and securities-firm pull
In parallel, Nodeinfra builds a full-stack Korean STO issuance platform on top of the TTA-verified Canton private synchronizer, serving as the first production adopter of the credential this grant produces. This platform is a separate, commercially-funded Nodeinfra workstream (see Out of Scope) — the grant funds the public credential, not the platform — but it provides concrete, near-term proof that verification converts into real issuance activity on Canton rather than remaining a paper credential. Nodeinfra leverages its two leading Korean financial-group engagements (counterparties under NDA) as launch customers, and its established relationships with top Korean securities firms to generate demand-side pull across the application layer.
The two strategies reinforce each other: securities firms are reached from above by an operator-blessed credential and from below by a working platform they can issue on today. Top-down supplies institutional legitimacy; bottom-up supplies a live reference deployment. Both meet at the securities-firm layer, where the bulk of STO issuance volume will sit.
Strategy 3 — Outward: APAC blueprint
The open-source Apache 2.0 artifacts are structured for portability, with mapping documents calling out Korea-specific versus reusable assumptions. Once the playbook exists, the marginal cost of clearing analogous verifications in Japan, Taiwan, Hong Kong, and other regulated APAC markets drops substantially, extending Canton's reach beyond Korea at zero additional ecosystem cost.
Regulatory & legal education (law-firm partner)
Cutting across both the top-down and bottom-up strategies, Nodeinfra will engage a Korean law firm with securities and digital-asset expertise to produce an independent legal compliance analysis: a written opinion mapping the Canton private synchronizer — and the BRV credential it carries — onto the Electronic Securities Act, the Capital Markets Act amendments, and the NCSC guideline. This addresses the core obstacle named above: regulators, KSD, and securities-firm risk committees need a neutral, third-party legal interpretation confirming that Canton's permissioned, privacy-preserving architecture satisfies the total-supply-oversight and right-presumption rules, not just a vendor's claim that it does. This legal engagement is a separate, complementary workstream funded outside this grant (see Out of Scope) — but Nodeinfra intends to publish the resulting analysis as a citable reference and use it as the basis for educational briefings to KSD, the FSC/FSS where appropriate, and downstream securities firms, delivered jointly with the Canton Foundation (see Co-Marketing).
Discovery and measurement
Discovery across all three strategies runs through the joint Canton Foundation announcement, Korean-press outreach, ecosystem presentations (see Co-Marketing), and the open-source artifact set as discoverable proof for evaluators outside Korea. Initial adoption is defined as the Canton private synchronizer cited in RFPs, PoCs, or technical evaluations at the operator tier or in downstream securities-firm selection within 12 months of issuance, and the artifacts referenced by at least one team pursuing analogous verification in another APAC jurisdiction. These indicators are tracked in Acceptance Criteria and reported publicly at 6 and 12 months post-issuance.
Rationale
Why BRV over alternative paths. Several alternatives could in principle deliver some of the same recognition; none deliver all of it.
- TTA GS Class 1 certification: more institutionally generic and less blockchain-specific than BRV. GS Class 1 is an ISO/IEC 25051-anchored software-quality seal that certifies general product quality across eight attributes, but it does not test the consensus fault tolerance, key management, and ledger-integrity properties the National Cyber Security Center guideline requires of a permissioned chain. It is a useful complementary credential and a sensible follow-on, but it is not the credential that answers the infrastructure operators' chain-security questions.
- Independent third-party audit (e.g., Big-4 or specialized blockchain auditor): produces a report but no standing against the NCSC guideline; cannot clear Korean infrastructure operators' procurement and security workflows, which require a recognized credential rather than a vendor-purchased opinion.
- Generic enterprise software credentials (ISO 27001, SOC 2): certify the operator's processes, not the chain product itself, and are non-Korean credentials with no hook into the Electronic Securities Act or the NCSC guideline. Useful complements; not a substitute.
- FSC regulatory-sandbox pilot: running an actual STO under the FSC sandbox is possible, but takes ~12 months minimum and operates under sandbox-set scope constraints. The result is one-off for the participating issuer, not a transferable credential other firms can rely on.
- Marketing / education campaign only: addresses the Canton-as-altcoin misperception but lacks an institutional anchor; securities-firm risk committees need a verifiable third-party signal to point to in their selection process.
BRV is the only path that simultaneously provides three things: a blockchain-specific evaluation against the NCSC guideline that underpins infrastructure-operator security review; the credential that public-sector and quasi-public procurement at KSD, FSI, KFTC, and peer infrastructure operators applies; and a transferable credential that downstream securities firms, banks, and asset managers inherit without separate re-engagement.
Why open-source over proprietary. The verification artifacts are 70%+ portable to other jurisdictions. Keeping them proprietary would protect Nodeinfra's incremental edge by a few quarters at most; releasing them under Apache 2.0 multiplies Canton's reach across APAC at zero marginal cost to the ecosystem. The APAC blueprint is, in many ways, the strongest part of this proposal — and it only exists if the artifacts are open.
Why now versus later. The Korean STO law's January 2027 effective date is hard. Infrastructure-operator selection at KSD, FSI, KFTC, and peer institutions runs ahead of downstream securities-firm onboarding by 6–12 months. The operators are sequencing decisions now, well before the law takes effect, because production rollouts take time. A chain verified in late 2027 is too late; a chain verified by Q4 2026 / early Q1 2027 is in the selection pool at the tier where the decision is actually made. The 5-month delivery window of this grant is matched to that timing.
Why Nodeinfra. Nodeinfra is one of the very few independent, vendor-agnostic teams in Korea with prior successful TTA verifications for blockchain infrastructure (via the Korean government's TIPS program). Most TTA blockchain experience lives inside Korean-built L1 vendors (Aergo, loopchain, etc.). Shepherding a non-Korean DLT through BRV is a fundamentally different exercise. The team's combination of TTA process experience, Korean financial counterparty relationships, and direct Canton operational experience is uniquely matched to it.
Timing and posture alternatives. (a) Wait for FSC subordinate regulations to name a specific credential — risk: misses the buildout window; the chains verified before the rules finalize will be the ones already selected. (b) Do nothing and let Canton win on technical merit — risk: addressed in Motivation; the misperception problem is real and won't self-correct in time.
Team
Nodeinfra (Mirny Inc.) — a Daml software development firm and Canton NaaS (Node-as-a-Service) provider based in Korea, currently operating 4 Canton nodes in production. Four blockchain engineers and one security engineer will be allocated full-time to this verification.
- Prior TTA verification experience — specifically for blockchain infrastructures. Nodeinfra has successfully completed TTA verifications for blockchain infrastructure as part of the Korean government's TIPS (Tech Incubator Program for Startups) program. TTA's blockchain-specific verification practice is recent. The number of teams that have shepherded a blockchain stack through evaluation end-to-end is small, and almost all of them are inside chains that own their own Korean-built L1s (Aergo, loopchain, etc.). Nodeinfra is one of the few independent / vendor-agnostic teams with this experience.
- Building Musubi Network — Canton-native infrastructure for FX trading and stablecoin settlement (including JPYSC, the SBI / Startale Japanese-yen stablecoin), demonstrating production Canton / Daml capabilities.
- Currently building two tokenization platforms for two leading Korean financial groups (counterparties under strict NDA).
- Direct operational experience with the Canton private synchronizer in production — covering the deployment, monitoring, and key-management posture that a BRV evaluation will scrutinize.
- Established working relationships with Korean financial counterparties at the application layer (securities firms, financial groups); infrastructure-operator engagement (KSD, FSI, KFTC, and peer institutions) initiated through this grant and the TTA verification process.
John Yang — CEO / Founder, Nodeinfra (Mirny Inc.) — johnyangk.github.io
- First author of papers at top systems / computer-science conferences (OSDI, USENIX ATC, EuroSys). Brings the systems-engineering depth required to map Canton's architecture onto the NCSC guideline's reliability and security requirements and to lead the evaluation-response cycle credibly.
Risks and Mitigations
- TTA finds a gap in upstream Canton (not our integration). Mitigation: internal pre-submission review using Nodeinfra's production-Canton operational experience to surface obvious gaps before formal submission; escalation path to upstream Canton maintainers documented at kickoff for anything we can't close ourselves.
- Cryptographic-conformance gap against the NCSC guideline. The guideline recommends KCMVP-validated algorithms while also permitting standards-body algorithms (ISO/IEC, IETF). Mitigation: an early conformance review of Canton's cryptographic primitives against both the KCMVP set and the standards-body allowance, documenting equivalence; any genuine gap is raised upstream through standard Canton processes rather than treated as a grant deliverable.
- NDA / confidentiality surface larger than expected. Mitigation: the carve-out plan naming the open-source surface is delivered and accepted before Milestone 1 payment; if the surface is inadequate, grantor and grantee re-scope before payment rather than after.
- Verification timeline slips beyond 5 months due to TTA-side delays. Mitigation: monthly public status updates in the GitHub repo; per Volatility Stipulation, external delays do not trigger renegotiation — the team accepts that volatility risk.
- TTA does not issue a passing verification result. Mitigation: Milestone 2 payment is conditioned on result issuance — if the result is not issued, Milestone 2 does not pay. Milestone 1 funds (already disbursed for kickoff infrastructure, submission preparation, and TTA fees) cover work performed and are non-refundable. In the event of non-issuance, Nodeinfra will publish a public post-mortem documenting the findings and any uncloseable gaps so future submitters can build on the work.
- Validator set composition differs from KSD / FSI / KFTC as named. Mitigation: Verification is validator-agnostic — the BRV result attaches to the Canton private synchronizer software, not to a specific validator roster, and not to Nodeinfra; any ecosystem team or institutional composition compliant with the Electronic Securities Act framework inherits it equally. Final validator selection is a regulatory and governance decision outside the grant's scope.
References
Standards & guideline basis
Legal & regulatory primary
Market sizing & analyst commentary
Press confirming private-chain consensus and securities-firm activity
English-language coverage
Precedent — prior private-chain TTA verifications in Korea
Canton private synchronizer would be the first non-Korean DLT, and the first privacy-preserving sub-net architecture, to complete TTA BRV.
| Company / Developer | Platform / Solution | TTA Verification Type | Key Verified Metrics |
|---|
| Beatoz | Beatoz Permissioned Network | Blockchain Reliability Verification | 17,700 TPS; stablecoin financial infrastructure; permissioned node stability |
| Heseg (헤세그) | Niktonet | Blockchain Reliability Verification | 3,000+ TPS on proprietary Tendermint-based PBFT+; enterprise data privacy and encryption compliance |
| Hana Financial TI | Hana Group Standard Blockchain Key Management Solution | Blockchain Reliability Verification | Zero-vulnerability architecture for financial networks and STOs; key lifecycle security, account node sandboxing, network fault tolerance |
| SK C&C | ChainZ (체인제트) | TTA V&V (Verification & Validation) | 4,480 TPS native coin; 1,850 TPS smart-contract token under heavy load |
| Coinplug (Metadium) | Metadium Enterprise Platform | TTA Security & Performance Test | 4,258 TPS transaction input; 50,000+ TPS query throughput (2020) |
For reference, prior GS Class 1 certifications of Korean private chains (the complementary software-quality track, pursued separately as a potential follow-on) include Blocko's Aergo Enterprise v2.0, ICONLOOP's loopchain Enterprise, Glosfer's HYCON EP, Leadpoint System's Innoblock, Lambda256's Luniverse, and SecureLink's EdgeChain-based CTTI cyber-threat-intelligence platform.
