Proposal: Korean TTA Blockchain Reliability Verification of the Canton Private Synchronizer#419
Open
johnyangk wants to merge 7 commits into
Open
Proposal: Korean TTA Blockchain Reliability Verification of the Canton Private Synchronizer#419johnyangk wants to merge 7 commits into
johnyangk wants to merge 7 commits into
Conversation
…anton Private Synchronizer Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
SIG labels auto-detected and applied: If this is incorrect, you can ask the reviewers to update the labels. |
|
Champion identified Canton Foundation The committee will verify this champion during review. |
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
johnyangk
requested review from
hythloda,
isegall-da,
stas-sbi,
tkatrichenko and
waynecollier-da
…tiality policy) The open-source surface is reframed around the TTA-verified Canton deployment configuration and stack (self-built deployment / configuration scripts, host tuning, pinned Canton runtime, and benchmark/test harnesses). This reflects TTA's confidentiality policy: the submission package, the evaluation checklist, the guideline-to-test-item mapping, the detailed test contents, and the result report are TTA-confidential and are not published. The test harness is publishable only subject to consultation with TTA. The BRV result and headline verified metrics are publicly citable subject to prior consultation with TTA. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Squashes the WIP refinements into one commit on top of the initial scope-narrowing: - Milestone 2 deliverables trimmed to the two checkable artifacts (the TTA-issued BRV result and the published verified deployment configuration and stack); the recognition/adoption bullet (already informational in Acceptance Criteria) is removed. - Portability/mapping documentation removed entirely as a published artifact; the APAC-blueprint value prop rests on the runnable verified stack and the post-mortem. - Milestone 1 restructured: deliverable 1 is a plain acknowledgement that the BRV engagement is starting (no scope detail, so it stays publishable under the NDA); the reference-deployment outline returns without the NCSC guideline-scope clause; phase-1 mechanics no longer publish a guideline-scope statement. - Cryptographic-conformance review dropped as a deliverable; the crypto-gap risk stays with a pre-submission-check mitigation. - Wording polish: phase 2 -> "Evaluation submission preparation"; Strategy 2 -> "live production deployment". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Squashes the latest WIP refinements: - Milestone 1 acknowledgement is now TTA confirmation verifiable by the Tech & Ops Committee under NDA, rather than a "publicly verifiable" letter TTA may not permit us to publish. - Acceptance Criteria for M1 and M2 are bullet lists instead of single paragraphs. - M1 no longer calls the deployment stack "verified" before verification (it is the stack "to be verified"); the M1 repo focus line drops "verified" too. - Redundant "(publicly verifiable)" removed from the M1/M2 deliverable lines (verifiability is stated in Acceptance Criteria). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Development Fund Proposal Submission
Proposal file:
/proposals/2026-06-Nodeinfra-korea-tta-brv.md
Impact
Korean securities firms will make their first DLT choice ahead of the January 2027 STO deadline. That choice locks in their tokenization infrastructure for decades, and selection is defaulting toward Hyperledger Besu and Fabric.
This credential is what puts Canton in front of them before that default hardens. The Canton Foundation can verify (under NDA) that a Korean financial authority has confirmed the importance of this credential.
Summary
This proposal funds taking the Canton private synchronizer through Korea's TTA Blockchain Reliability Verification (BRV), timed ahead of the Korean STO law's January 2027 effective date. Success would make Canton the first non-Korean DLT — and the first privacy-preserving sub-net architecture — to hold the credential. Korean financial-infrastructure operators rely on that credential to evaluate a permissioned chain.
The BRV result attaches to the Canton private synchronizer software itself, so every ecosystem participant inherits it. We open-source the TTA-verified Canton deployment configuration and stack under Apache 2.0: the self-built deployment / configuration scripts, host tuning, pinned Canton runtime, the benchmark harness, the test harness (subject to consultation with TTA), and the post-mortem. Together they form a reusable, runnable blueprint for analogous APAC verification regimes.
Total request: 2,200,000 CC (~$330,000 USD at the $0.15/CC reference rate) across two milestones.
Checklist
/proposals/Notes for Reviewers
Eligible funding category: This proposal fits two categories.
SIG alignment:
Champion: Canton Foundation.
Public-good framing: The grant funds a credential that attaches to the Canton private synchronizer software, not to Nodeinfra or any single operator, plus an open-sourced (Apache 2.0) TTA-verified Canton deployment configuration and stack reusable across APAC (the verified, runnable substrate; TTA-confidential evaluation material is excluded). Nodeinfra's own commercial work is funded separately and fenced into the proposal's Out of Scope section. That work covers the STO issuance platform, securities-firm BD, and the law-firm legal-education engagement. It appears in the Growth and Adoption section only as evidence that the credential drives real adoption.
Acceptance criteria are objectively verifiable: Both milestone gates are independently checkable without grantee attestation. M1 is a public TTA engagement/scope acknowledgement; M2 is a publicly verifiable TTA-issued BRV result plus the published Apache 2.0 verified Canton deployment configuration and stack. Because the BRV result is binary, Milestone 2 payment is conditioned on the credential itself rather than on downstream adoption.
Adoption accountability: Adoption indicators are tracked as informational (not payment gates, since they lag issuance and sit with third parties), with a committed public adoption-tracking report in the repo at 6 and 12 months post-issuance.
Timing: The Korean STO law's January 2027 effective date is hard, and infrastructure-operator selection runs 6–12 months ahead of it. The 5-month delivery window is matched to that schedule, placing Canton in the selection pool before decisions are locked.