Korean granted patent 10-2891022
Cryptocurrency trading-loss insurance management system
KR102891022B1
Application · 10-2024-0192348
- Filed
- Grant publication
STUPORE / FOUR PLATFORMS. ONE ECOSYSTEM.
Respond to incidents. Read the markets. Govern your agents. Build what comes next.
CHOOSE YOUR STARTING POINT ↓Bring incident evidence, eligibility checks, and reviewer decisions into a traceable resolution workflow.
Incident response & settlement oversight.
Research equities and crypto through sourced market snapshots, analyst theses, and personal watchlists.
Market intelligence & research.
Set an agent’s boundaries, route actions for approval, and examine receipts, incidents, and audit history.
Agent policies & accountable decisions.
Turn product context and research into reviewed ideas, structured build packets, and lessons from outcomes.
From first idea to new venture.
WHY CRYPTODAM · PATENTS & MARKET EVIDENCE
Designing investor protection since 2024. Recurring incidents show why it matters.
A sculpted brass dam crosses fine teal signal lines beside orderly evidence records, illustrating an intended observation, verification and review process.
CryptoDam — Crypto & Stablecoin Insurtech Insurance Platform
CryptoDam is building investor protection on patented technology, with clear protection terms, verifiable incident evidence, and accountable compensation processes. Our mission is to safeguard investors and help rebuild trust in crypto and stablecoin markets—in Korea and worldwide.
01 / DOCUMENTED FOUNDATION
The founder’s patent records describe a technical approach to risk assessment, premium calculation, multi-source trigger verification and compensation processes.
Korean granted patent 10-2891022
KR102891022B1
Application · 10-2024-0192348
Related international application published
WO2026135040A1
Application · PCT/KR2025/021564
A published international application, not a worldwide patent grant.
Patent records do not establish insurance authorization, government endorsement or currently available coverage.
The Korean grant and the related PCT application have distinct legal statuses. A PCT publication is not a worldwide patent grant. Patent records do not establish insurance authorization, government endorsement or currently available coverage.
How the PCT process works · WIPO (opens in a new tab)Inventor and original assignee in the publication: 김경진 (Kim Kyung Jin). Founder profile: Walt KJ Kim.
The documented technology addresses risk assessment, premium calculation, multi-source trigger verification, and compensation processes. Grant publication: November 24, 2025.
Filing date, grant-publication date, inventor/original assignee, and documented technical architecture.
Related international application identifying Kim Kyung Jin.
International publication WO2026135040A1. PCT is an international application procedure; national or regional offices decide patent grants.
Reviewed November 16, 2026: the Korean patent record links the PCT application; publication metadata was corroborated by a bibliographic mirror. The primary WO publication full text could not be retrieved in this review.
Original publication link; its full text could not be retrieved during this review.
Full source not retrieved in this review
The PCT application identifier, filing date, and linked international publication.
Bibliographic application/filing and publication identifiers/dates and applicant information.
The distinction between the PCT application procedure and national/regional patent grants.
First Korean filing
Korean grant publication
PCT international publication
IP milestones and market events share a timeline, not a causal connection. The March 2023 USDC episode is earlier historical context.
Historical context predating the first CryptoDam filing.
Korea’s user-protection rules commenced before the first patent filing on 20 December 2024.
10-2024-0192348 · Founder Kim Kyung Jin.
Korean granted patent 10-2891022.
PCT/KR2025/021564 · International application procedure.
WO2026135040A1 · Distinct from national/regional grants.
Followed by funding and phased service-restoration announcements.
Our interpretation of these cases guides development and pilot work. These objectives are CryptoDam’s analysis, not claims made by the cited sources or a promise to compensate any listed event.
Develop objective event timing, evidence of affected functions and predefined duration criteria for service interruptions.
Use multiple price sources and venue comparisons; distinguish a persistent price deviation from an issuer’s redemption failure.
Link verified issuance and redemption status to eligible exposure records and explicit product conditions in pilot workflows.
Connect evidence, decision ownership and review history, with appropriately funded protection arrangements where offered.
Market field notes
Reviewed cases illustrate different protection problems. Impacts, recovery and service availability are reported separately; these cases are not an exhaustive global incident census.
I01 Binance
A security incident was followed by company funding and phased withdrawal restoration.
Status as of
Company funding was reported complete; withdrawals reopened on 87 networks while phased restoration continued.
Binance reported approximately US$6.34 billion in affected assets after its October 29 security incident. Its November 12 announcement said company-funded coverage of the affected assets was complete.
Status as of
On November 14, Binance reported reopening withdrawals on 87 networks while phased restoration continued. Funding completion and full service availability are separate facts.
CryptoDam design objective: maintain distinct evidence and decision records for affected assets, financial coverage, and actual service availability.
Theft on or about October 29 and the government attribution.
October 29 occurrence and the affected-asset estimate.
Completion of affected-asset funding and phased withdrawal restoration; published November 12 and signed November 13.
Withdrawals reopened on 87 networks, with restoration continuing elsewhere.
Primary source · Source published
Supports: October 29 occurrence and the affected-asset estimate.
Content reviewed
Primary source · Source published
Signed
Supports: Completion of affected-asset funding and phased withdrawal restoration; published November 12 and signed November 13.
Content reviewed
Primary source · Source published
Supports: Withdrawals reopened on 87 networks, with restoration continuing elsewhere.
Content reviewed
Primary source · Source published
Supports: Theft on or about October 29 and the government attribution.
Content reviewed
Minting and redemption were suspended after a security incident.
Roughly eight hours of interruption or degradation; full system recovery took longer.
Bitcoin rewards were credited in error during an exchange promotion.
USDe/BNSOL/WBETH collateral prices diverged; BNSOL and WBETH are not dollar stablecoins.
Emergency maintenance restricted service for approximately 90 minutes.
Theft, compensation, affected assets and reserve exposure measure different things. They are never added into a combined loss total.
Read the complete incident and policy archive04 / THE KOREAN CONTEXT
Since 19 July 2024, covered Korean virtual asset providers must prepare for specified incident liabilities.
FSC implementation FAQ · 17 July 2024 (opens in a new tab)Aggregate insurance or mutual-aid limits and reserves must meet the applicable minimum for specified incident liabilities.
Since 19 July 2024, covered virtual asset service providers in Korea—including relevant exchanges and custodians—must make financial provision for liabilities arising from specified incidents such as hacking and computer-system failures. Permitted measures include insurance, mutual aid and reserves.
Article 8 requires covered providers to prepare for specified incident liabilities. The supervisory rule sets minimum aggregate insurance or mutual-aid limits and reserves according to customer assets and the applicable business category.
The greater of 5% of the prescribed value of customer virtual assets outside cold storage and ₩3 billion (30억원).
An aggregate resource requirement for the provider’s specified incident liabilities; it is not 5% plus ₩3 billion or a payout promise to each user.
The greater of that same 5% amount and ₩500 million (5억원).
Applies to qualifying providers whose customer services involve no exchange between virtual assets and money. This is an exception based on business activities, not firm size.
Insurance or mutual-aid limits and reserves may contribute to the aggregate. Deposits or trusts at qualifying institutions are conditional fallback measures under Article 10(1), when insurance/mutual aid and reserves are both unavailable or cannot by themselves meet the amount requirement.
The calculation totals month-end quantities outside cold storage multiplied by the prescribed preceding one-year average daily KRW conversion values at that month-end. Recalculate monthly and make required limit increases or additional funding by the 10th of the following month. Month-end and the 10th are calendar dates, not business days.
These requirements address the provider’s specified incident liabilities. They do not establish universal coverage of market losses or stablecoin depegs. Any future retail fixed-benefit product needs a separate product and authorization assessment.
Sources and applicable versions
The standard viewer did not expose the article body. Article 10 was reviewed in the official indexed text and its amounts, calculation and deadline were cross-checked against the FSC’s 17 July 2024 explanation.
The version effective 2 October 2026 was identified, but the standard viewer did not expose Article 27. The no-exchange-between-money-and-virtual-assets criterion was cross-checked against the FSC’s 22 March 2021 explanation of the finalized regulation.
Full source not retrieved in this review
Preserve prescribed transaction records for 15 years after the transaction relationship ends.
Article 9 requires prescribed transaction records to be retained for 15 years after the transaction relationship ends, supporting traceability and the checking and correction of errors.
The 15-year period begins when the transaction relationship ends. An incident report alone does not establish compliance with the statutory transaction-record requirements.
Sources and applicable versions
Reporting review examines the adequacy and actual operation of organizational, personnel, IT and internal controls.
Requirements strengthened from 20 August 2026 bring the adequacy and operation of organizational, personnel, IT and internal control arrangements into the VASP reporting review.
Apply the relevant transition provisions—including the amended reporting rules and treatment of specified pre-commencement grounds for already reported providers—when assessing an individual provider’s obligations. They are not a blanket exemption from internal-control requirements.
Sources and applicable versions
The supplementary Articles 1, 3, 4 and 5 of Act No. 21358, promulgated 19 February 2026, were also reviewed. Transitions cover amended reporting by existing providers and treatment of specified pre-commencement grounds; they do not establish a blanket internal-control exemption.
The announcement body and in-force Act were reviewed. The attached manual’s body could not be inspected, so separate final-manual issuance or application is not asserted.
Supervisory guidance, not a new Article 10 floor; 16 November is a follow-up to the same announcement. Status as of
In its 12 November 2026 announcement, the FSC said the Digital Asset Bill was still being prepared.
Content reviewed
On 12 November 2026, the FSC called for continuous monitoring and incident response, greater cold-storage protection, and sufficient insurance compensation limits and reserves.
Announced security measures and supervisory guidance; this release does not itself establish a new numerical Article 10 floor. The 16 November public summary follows this announcement, rather than constituting a separate enactment or incident.
CryptoDam interpretation: institutions need verifiable incident response and adequate compensation resources. The guidance neither requires nor endorses CryptoDam.
The FSC announced security and compensation-capacity measures and said the Digital Asset Bill was still being prepared.
An FSC public summary reiterated the 12 November security measures. It is a follow-up to the same policy announcement, not a separate law or incident.
Primary source · Source published
Supports: Monitoring and response, cold-storage protection, insurance limits and reserves, and the Digital Asset Bill then being prepared; not a newly enacted numerical supervisory floor.
Content reviewed
Primary source · Source published
Supports: Follow-up public summary of the 12 November security measures, reiterating continuous response, cold storage, insurance limits, reserves and incident-response measures.
Content reviewed
A passed target date establishes neither completed implementation nor a statutory mandate for every measure. Status as of
On 6 April 2026, the FSC announced review findings and a control-improvement programme covering continuous ledger/wallet reconciliation, automated verification and multiple approvals for manual transactions, stronger internal controls and planned self-regulatory implementation.
These are announced improvement measures and implementation plans. The announcement does not establish that every measure became a statutory mandate or was completed simply because a target date passed.
CryptoDam interpretation: protection workflows need verifiable records, clear decision ownership, and review history.
The FSC announced reconciliation, transaction-verification and approval-control improvements with planned self-regulatory and system implementation.
Primary source · Source published
Supports: Reconciliation, verification and multiple approvals for manual transactions, internal-control improvements and planned self-regulatory/system implementation; not evidence of completed implementation.
Content reviewed
Recurring incidents and Korea’s protection requirements reinforce the need for verifiable evidence and accountable compensation processes. CryptoDam is being developed to help exchanges, insurers and other institutions address that need—and help restore trust in crypto and stablecoins.
05 / A PROPOSED PATH
Proposed launch path
Start with a proposed enterprise pilot; evaluate insurer-issued protection after defining coverage, lawful distribution, claims responsibilities and customer protections.
Defined incident evidence and sample reports, within an agreed enterprise software pilot.
The insurer owns terms, pricing, underwriting, claims and payouts. CryptoDam supports evidence and workflow records.
Permitted distribution or scoped sandbox designation, with a separate VASP and AML assessment for stablecoin activities.
CryptoDam’s proposed launch begins with enterprise incident-evidence software. An insurer-issued protection product would follow once the parties establish the coverage terms, permitted distribution arrangements, claims responsibilities and customer protections.
01 · Enterprise software pilot
Begin with defined incident detection, timestamped evidence, event reconstruction and sample reports, within an agreed enterprise pilot scope. The proposed commercial model is a fixed software or pilot fee.
Assess the actual functions and contractual commitments. A fixed fee or “software” label is not a regulatory exemption.
02 · Insurer-led protection
Support an insurer-issued KRW product with evidence and workflow records. The insurer sets policy terms and pricing, underwrites the risk and retains responsibility for claims and payouts. Solicitation and regulated claims functions are performed by the insurer or other persons legally entitled to perform those functions.
Scope technical evidence and workflow support with the insurer. Coverage judgments, loss assessment, and insurance-money recommendations can engage regulated functions even if generated by software.
03 · Expanded distribution
Evaluate appropriate agency or brokerage registration, or a specifically designated regulatory sandbox where relevant. Review stablecoin trading, exchange, custody, transfer and intermediary features separately before activation.
Verify sandbox eligibility for the actual applicant entity. A designation provides specific permissions and relief within its stated scope.
Korean insurance law regulates the substance of paid risk protection. Insurance business requires FSC authorization; solicitation and related compensation must fit permitted roles. The insurer prepares product documentation and completes any required filings. Loss-adjustment responsibilities and permitted delegation must be settled before production use. A regulatory sandbox provides only the relief granted to the designated service. Stablecoin business activities require a separate VASP and AML assessment.
Relevant law and official sources
The announcement’s provider count and list are not presented as a current register. The actual activities and the provider’s reporting and acceptance requirements need separate assessment.
The cited version and articles were reviewed for this date. Article 127 requires advance filing in specified cases; assess the actual functions, permitted roles and delegation scope.
Check the actual applicant against the eligibility rules, including financial companies and Commercial Act companies with an office in Korea. Relief is limited to the designated service, scope, conditions and duration.
The supplementary Articles 1, 3, 4 and 5 of Act No. 21358, promulgated 19 February 2026, were also reviewed. Transitions cover amended reporting by existing providers and treatment of specified pre-commencement grounds; they do not establish a blanket internal-control exemption.
The announcement body and in-force Act were reviewed. The attached manual’s body could not be inspected, so separate final-manual issuance or application is not asserted.
Regulatory sources checked: .
For exchanges, insurers, financial institutions, public agencies and partners exploring investor protection in Korea and international markets.
START WITH YOUR QUESTION
Four services, each with a distinct job. Choose the question you’re working on to see where to start and what the process gives you.
CryptoDam
When an exchange disruption or stablecoin incident raises questions, CryptoDam brings the sources, coverage conditions and review history into one case. Subscribers can follow their eligibility and submit proof; partner and operations teams work through the decisions behind it.

The products share an approach while keeping their own responsibilities and access boundaries. A connected workflow does not imply automatic approval or movement of funds.
ASSISTANT CONNECTIONS
Find safety guides, check public-address formats, and discuss your own Hailey watchlist and alerts in the assistant you already use.
Explore the core plugin, download the package, or follow the custom-connection steps available to your account. The guide explains sign-in, permissions, and current limits.
ChatGPT connection guideAdd the existing CryptoDam connector from Claude, then sign in and review your consent. Follow a public setup guide without needing access to our private app repository.
Claude connection guideA place to start
“Summarize my Hailey watchlist and alerts without changing anything.”
THE PLATFORM GUIDE / 01—04
Investigate an incident. Understand a market. Govern an agent. Shape your next product. See the work each platform supports and how to get started.
Bring incident evidence, trigger checks, eligibility decisions, and payout review into one operational record. Cryptodam gives partner, operations, and compliance teams a shared place to investigate disruptions and follow each case through its next decision. Review the supporting sources, understand why a case qualifies, and keep the history available as the incident moves toward resolution.
Operations teams · Partners · Compliance reviewers
IN PRACTICE
Inspect source evidence and trigger checks in the context of each incident.
Follow coverage conditions, affected subscribers, and the reasons behind each result.
Work through reviewer decisions, holds, and settlement records with an audit trail.
THE WORKFLOW
Move between Korean equities, U.S. equities, and crypto without losing the research context. Silver Ocean Hailey brings asset discovery, market snapshots, published investment theses, and contributor profiles into one workspace. Start with a symbol, examine the available data and source freshness, then follow the ideas and people that matter to your own research process.
Market researchers · Individual investors · Contributors
IN PRACTICE
Browse Korean and U.S. stocks alongside crypto, with asset detail and available pricing.
Read a contributor’s thesis, stance, and symbol context before forming your own view.
Organize symbols, discover contributor profiles, and explore research rooms.
THE WORKFLOW
Define what an agent is allowed to do before an action reaches your systems. AgentGuard connects agent identities, mandates, policy evaluation, human review, and action receipts. Teams can examine the requested action against its limits, escalate decisions that need approval, and trace the resulting evidence back to the agent and policy involved in the decision.
AI product teams · Platform operators · Risk reviewers
IN PRACTICE
Set permitted assets, purposes, spending limits, expiry, and approval thresholds.
Evaluate proposed actions and route decisions through the applicable approval process.
Connect the authorization, action receipt, and incident history for later review.
THE WORKFLOW
Keep product context, research, implementation plans, and measured outcomes connected across development cycles. Genesis helps founders and product teams turn a question into a guided mission, develop an idea into a build packet, and bring the implementation result back for review. Human approval shapes the next step, while recorded lessons help inform the work that follows.
Founders · Product teams · Venture studios
IN PRACTICE
Capture the product brief, investigate opportunities, and organize research findings.
Turn an approved idea into structured prompts, implementation phases, and test checklists.
Record implementation outcomes, compare experiments, and decide what to iterate next.
THE WORKFLOW

THE WAY WE BUILD
Stupore builds tools for people investigating uncertain information, reviewing choices and preparing their next move. Our four products bring that approach to different kinds of work.
A result is more useful with its available sources, timing and context. We design the work around understanding the reasons behind it.
Research, policy evaluation and approval have different roles. Consequential decisions stay with the people authorized to make them.
A reviewed case or an approved brief should help the next person act with context. The record stays connected to the work.
BEFORE YOU BEGIN
Understand where to start, what to expect, and how to access the right workspace.
Talk to the teamChoose Cryptodam for incident operations, Silver Ocean Hailey for market research, AgentGuard for oversight of financial AI agents, or Genesis for supervised product development. Each has its own workspace and purpose.
The product overviews are public. The Hailey workspace requires sign-in. AgentGuard requires an authorized workspace role, and Genesis access is reviewed. You can explore each overview before requesting access.
Korean stocks, U.S. equities, and crypto. Symbol pages, market snapshots, analyst theses, and watchlists give different views of an asset. Coverage and available observations vary by asset and data provider.
On Hailey symbol pages, check the source, observation time, and available freshness label. A market snapshot can be older than a live quote, and availability varies by provider.
Genesis organizes research, scored ideas, build packets, implementation outcomes, and experiments. Teams review what to build and learn from the result. Deployment and other consequential actions remain supervised.
Each product has its own workspace, workflow, and access rules. They support complementary jobs: researching markets, handling incidents, supervising agents, and developing products. Choose the workflow you need from the product guide.
Explore the visual product map or inspect sourced market data.
CRYPTODAM / STUPORE
Explore the workspace, or talk with us about your team’s workflow.