One typed pipeline from market event to audit log.
Incident workflows connect intake, evidence, eligibility, partner review, settlement administration and audit records. Approvals, holds, failures and retries remain visible for authorized reviewers.
A practical example
A withdrawal delay is reported. What happens next?
A report does not automatically establish an incident or a payment obligation. CryptoDam separates facts to verify from decisions to review, so the responsible team can work through each in order.
- Establish the facts
- Record the affected service, timing, duration and supporting evidence. EventTruth remains the authority for the event determination.
- Apply the relevant rules
- Review the approved product version, applicable conditions and the users or exposures within scope.
- Preserve the decision
- Authorized people review and approve. Any next step stays within its approval boundary, with evidence and decision history kept together.
From integration to reviewed outcomes
- 01
Exchange integration
Partners configure scoped API access, signed webhooks, trigger definitions and payout tables. Integration and production access require partner onboarding.
- 02
Enrollment and eligibility records
Partner-managed subscription and plan records provide the basis for eligibility checks. Creating a website account alone does not activate protection or complete partner onboarding.
- 03
Incident detection and verification
Operators review submitted incidents against configured trigger conditions and available evidence. Source references, observed values and calculation records support the review.
- 04
Reviewed payout workflow
Eligible records proceed through confirmation and required operator approvals. Holds, failures and retries remain visible. XRPL execution produces Testnet proof only; it does not pay real compensation.
One place to review the operating picture.
Published service reports appear below. Open your workspace to review incidents, evidence and decisions available to your account.
Loading service reports…
Recorded reports describe the state at their timestamp. They do not establish current availability.
Controlled modules, predefined triggers.
Incident categories organize configurable trigger conditions, evidence and review workflows. Availability depends on the partner configuration and connected data sources; a listed category does not establish insurance coverage.
Exchange outage
Configurable duration thresholds and submitted outage evidence.
Withdrawal delay
Persistent withdrawal queue beyond disclosed SLA windows.
Hack or security incident
Confirmed loss event, public disclosure, and partner attestation.
Stablecoin depeg
Peg deviation against benchmark with multi-source agreement.
Abnormal volatility
Configured price-change thresholds and recorded observation windows.
External infrastructure failure
Upstream RPC, custody, or settlement-rail disruption.
Market data discrepancy
Benchmark drift, feed manipulation, or oracle desynchronization.
Cryptodam does not custody assets, issue stablecoins, guarantee redemption, or provide investment advice. Triggers, eligibility, and payout logic are defined in advance with partner and insurer review.
Control incidents.
Restore confidence.
Build trust that lasts.
Pilot Cryptodam with your incident families, evidence schemas, and payout logic. We work with your compliance and insurer partners from day one.