Auditable by default, reviewable on demand.
Review the versioned rules, evidence references and recorded decisions available to your role. Trace details depend on the module and the information recorded; audit access does not grant approval authority.
How to read the record
A result is only part of the story
A reviewable record distinguishes observed facts, applicable rules and decision authority. CryptoDam connects this context so an authorized reviewer can revisit the result.
- What does the evidence establish?
- Inspect the source, timing and event determination. Advisory reports or reviewer numbers alone do not prove an incident.
- Which rules were applied?
- Check the approved product version and its conditions. Product Studio retains its separate authority over product and version approval.
- Who made the decision?
- Review the role-appropriate approval history. An audit record explains that process; it does not promise a payment or legal protection.
Records that support a careful review.
Incident evidence, calculation records and workflow history help partners, insurers and compliance teams inspect the basis for operational decisions.
Auditability
Review source references, recorded inputs, rule versions and workflow actions. Available traces and exports depend on the module and the data recorded for that incident.
Role boundaries
Access checks and row-level policies control which records each role can view or change. Partner records are scoped to the relevant organization.
Operational resilience
Operator queues, explicit failure states and audit records support operational review. Independent security and compliance assessment remains necessary before commercial reliance.
Settlement proof
Optional XRPL Testnet anchor for incident proof, Payment, and Escrow references. No personal data on-chain.
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)
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.