A modular control plane for post-event operations.
Cryptodam is software infrastructure for digital-asset incident response — detection, decision, workflow, and record. Each layer is independently versioned, observable, and replaceable.
One control plane, four modular layers.
Cryptodam is software infrastructure, not custody, trading, or asset management. Each layer is independently versioned, observable, and replaceable.
Detection
Submitted operational evidence and configured market sources, with source and timestamp information where available.
- Multi-source ingestion
- Source availability
- Observation windows
Decision
Versioned trigger rules, deterministic evaluation, idempotent recomputation.
- Versioned trigger definitions
- Reason-coded eligibility
- Evidence digests
Workflow
Typed state machines for incident, eligibility, confirmation, and payout.
- Role-scoped review queues
- Approvals · holds · retries
- Recorded failure states
Record
Structured audit trail and optional XRPL settlement proof for downstream review.
- Diffable state log
- Evidence exports
- Optional Testnet proof
Infrastructure, not insurance UI
Cryptodam provides the software, monitoring, workflow orchestration, trigger logic, and auditability layer — not custody, trading, or asset management.
Multi-source signal ingestion
Combine submitted incident evidence with configured market-data sources. Availability, freshness and source labels depend on the provider and deployment configuration.
Deterministic trigger evaluation
Evaluate configured thresholds, observation windows and rule versions. Calculation records retain the inputs and results needed for review.
Configurable payout calculations
Configured payout tables and calculation rules produce amounts for eligibility and operator review. Results do not establish insurance coverage, a binding quote or guaranteed compensation.
State-machine enforced lifecycle
Incident and payout records follow defined transitions with role checks, approval requirements, holds and retry handling. Operators can inspect status and recorded actions.
Evidence and audit records
Review incident evidence, calculation traces and recorded workflow actions in the appropriate console. These records support an assessment; they are not a certification or regulatory approval.
White-label partner integration
Partner branding, scoped API keys, signed webhooks and synthetic sandbox runs support integration work. Delivery timing depends on configuration, testing, onboarding and partner approvals.
Hailey intelligence layer
Silver Ocean Hailey fuses a four-layer model — Doctrine (setup library), Trust (graph-weighted reputation), Crowd (stance dispersion + contagion decay), Machine (regime + forecast) — to produce a single auditable decision lean per symbol across KR equities, US equities, and crypto.
Configurable anomaly checks
Calculation rules compare supplied activity measures with reference values and flag exceptions for review. These checks require suitable inputs and do not independently establish manipulation or fraud.
Reproducible simulation engine
Run seeded synthetic scenarios with configured persona mixes and policy inputs. Compare modeled adoption, claims and payout exposure; outputs are assumptions-based simulations, not validated forecasts or production evidence.
Stablecoin depeg infrastructure
Predefined peg-deviation triggers, benchmark evidence, eligibility workflows, and payout-review operations for stablecoin stress events across supported USD-pegged assets.
Five-stage processing pipeline
A review workflow connects incident inputs, calculations, confirmation and recorded outcomes.
Signal ingestion
Cross-validated operational + market data with provenance
Configured sources · timestamps · submitted evidence
Trigger evaluation
Configured thresholds and rule conditions
Observation windows · trigger versions · calculation records
Eligibility engine
Subscription + plan + enrollment validation with reason codes
RLS-scoped queries · idempotent recomputation · structured exception taxonomy
Confirmation & evidence
User confirmation and available evidence records
Confirmation timestamps · evidence references · operator review
Payout workflow
Review, required approvals, processing and recorded outcomes
Approval checks · holds · failed-attempt handling · audit records
How Cryptodam evaluates and records an incident
Configured inputs and rules produce reviewable calculations. The methods below describe the implemented workflow, not validated actuarial models or automated underwriting.
Source and observation records
Configured data sources and submitted evidence provide observed values, timestamps and source references. Missing or stale data must be resolved before an operator relies on the result.
Configured trigger checks
Trigger definitions set thresholds and observation conditions. Reviewers inspect the recorded calculation and evidence before progressing the incident workflow.
Versioned amount calculations
Configured formulas and payout tables produce calculation records. Assumptions, plan inputs and approvals determine how a result may be used; the output is not a binding insurance quote.
Activity-based anomaly checks
The anomaly calculation compares supplied current activity with reference volume and frequency. Threshold flags support operator review and require interpretation in context.
What to confirm for a pilot
Agree on the inputs, people and limits before relying on a workflow result.
Workflow review
- Named roles and approval requirements
- Configured triggers and eligibility conditions
- Evidence, exceptions and recorded decisions
Data and integration
- Source availability and observation windows
- Partner API and webhook configuration
- Synthetic test scenarios and expected outcomes
Boundaries
- No guaranteed compensation or insurance offer
- Testnet proof does not move real funds
- Commercial reliance requires external review
Trusted benchmark inputs for trigger decisions
Cryptodam can connect predefined price-trigger rules to disclosed benchmark sources, observation windows, rule versions, fixed payout tables, and audit-ready evidence trails — so trigger decisions can be reviewed against an externally verifiable basis. Stablecoin depeg workflows extend the same approach using peg-value benchmarks, time-windowed price evidence, source agreement checks, and evidence hashing.
Pre-disclosed trigger basis
Predefined benchmark inputs and rule versions are recorded before any incident, not after.
Benchmark-linked observation window
Trigger evaluation references a disclosed observation window — not ad-hoc spot prices.
Audit-ready calculation trace
Each decision links back to source metadata, rule version, and observed values for review.
CME CF Bitcoin Reference Rate (BRR)
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.